| RFC Nummer und Titel Abstrakt | Datum Status Autor |
| RFC0001 Host Software | April 1969 Status: UNKNOWN Autor: S. Crocker |
| RFC0002 Host software | April 1969 Status: UNKNOWN Autor: B. Duvall |
| RFC0003 Documentation conventions | April 1969 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0004 Network timetable | March 1969 Status: UNKNOWN Autor: E.B. Shapiro |
| RFC0005 Decode Encode Language (DEL) | June 1969 Status: UNKNOWN Autor: J. Rulifson |
| RFC0006 Conversation with Bob Kahn | April 1969 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0007 Host-IMP interface | May 1969 Status: UNKNOWN Autor: G. Deloche |
| RFC0008 ARPA Network Functional Specifications | May 1969 Status: UNKNOWN Autor: G. Deloche |
| RFC0009 Host Software | May 1969 Status: UNKNOWN Autor: G. Deloche |
| RFC0010 Documentation conventions | July 1969 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0011 Implementation of the Host - Host Software Procedures in GORDO | August 1969 Status: UNKNOWN Autor: G. Deloche |
| RFC0012 IMP-Host interface flow diagrams | August 1969 Status: UNKNOWN Autor: M. Wingfield |
| RFC0013 Zero Text Length EOF Message | August 1969 Status: UNKNOWN Autor: V. Cerf |
| RFC0015 Network subsystem for time sharing hosts | September 1969 Status: UNKNOWN Autor: C.S. Carr |
| RFC0016 M.I.T | August 1969 Status: UNKNOWN Autor: S. Crocker |
| RFC0017 Some questions re: Host-IMP Protocol | August 1969 Status: UNKNOWN Autor: J.E. Kreznar |
| RFC0018 IMP-IMP and HOST-HOST Control Links | September 1969 Status: UNKNOWN Autor: V. Cerf |
| RFC0019 Two protocol suggestions to reduce congestion at swap bound nodes | October 1969 Status: UNKNOWN Autor: J.E. Kreznar |
| RFC0020 ASCII format for network interchange | October 1969 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0021 Network meeting | October 1969 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0022 Host-host control message formats | October 1969 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0023 Transmission of Multiple Control Messages | October 1969 Status: UNKNOWN Autor: G. Gregg |
| RFC0024 Documentation Conventions | November 1969 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0025 No High Link Numbers | October 1969 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0027 Documentation Conventions | December 1969 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0028 Time Standards | January 1970 Status: UNKNOWN Autor: W.K. English |
| RFC0029 Response to RFC 28 | January 1970 Status: UNKNOWN Autor: R.E. Kahn |
| RFC0030 Documentation Conventions | February 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0031 Binary Message Forms in Computer | February 1968 Status: UNKNOWN Autor: D. Bobrow, W.R. Sutherland |
| RFC0032 Some Thoughts on SRI's Proposed Real Time Clock | February 1970 Status: UNKNOWN Autor: J. Cole |
| RFC0033 New Host-Host Protocol | February 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0034 Some Brief Preliminary Notes on the Augmentation Research Center Clock | February 1970 Status: UNKNOWN Autor: W.K. English |
| RFC0035 Network Meeting | March 1970 Status: INFORMATIONAL Autor: S.D. Crocker |
| RFC0036 Protocol Notes | March 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0037 Network Meeting Epilogue, etc | March 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0038 Comments on Network Protocol from NWG/RFC #36 | March 1970 Status: UNKNOWN Autor: S.M. Wolfe |
| RFC0039 Comments on Protocol Re: NWG/RFC #36 | March 1970 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0040 More Comments on the Forthcoming Protocol | March 1970 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0041 IMP-IMP Teletype Communication | March 1970 Status: UNKNOWN Autor: J.T. Melvin |
| RFC0042 Message Data Types | March 1970 Status: UNKNOWN Autor: E. Ancona |
| RFC0043 Proposed Meeting | April 1970 Status: UNKNOWN Autor: A.G. Nemeth |
| RFC0044 Comments on NWG/RFC 33 and 36 | April 1970 Status: UNKNOWN Autor: A. Shoshani, R. Long, A. Landsberg |
| RFC0045 New Protocol is Coming | April 1970 Status: UNKNOWN Autor: J. Postel, S.D. Crocker |
| RFC0046 ARPA Network protocol notes | April 1970 Status: UNKNOWN Autor: E. Meyer |
| RFC0047 BBN's Comments on NWG/RFC #33 | April 1970 Status: UNKNOWN Autor: J. Postel, S. Crocker |
| RFC0048 Possible protocol plateau | April 1970 Status: UNKNOWN Autor: J. Postel, S.D. Crocker |
| RFC0049 Conversations with S. Crocker (UCLA) | April 1970 Status: UNKNOWN Autor: E. Meyer |
| RFC0050 Comments on the Meyer Proposal | April 1970 Status: UNKNOWN Autor: E. Harslen, J. Heafner |
| RFC0051 Proposal for a Network Interchange Language | May 1970 Status: UNKNOWN Autor: M. Elie |
| RFC0052 Updated distribution list | July 1970 Status: UNKNOWN Autor: J. Postel, S.D. Crocker |
| RFC0053 Official protocol mechanism | June 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0054 Official Protocol Proffering | June 1970 Status: UNKNOWN Autor: S.D. Crocker, J. Postel, J. Newkirk, M. Kraley |
| RFC0055 Prototypical implementation of the NCP | June 1970 Status: UNKNOWN Autor: J. Newkirk, M. Kraley, J. Postel, S.D. Crocker |
| RFC0056 Third Level Protocol: Logger Protocol | June 1970 Status: UNKNOWN Autor: E. Belove, D. Black, R. Flegal, L.G. Farquar |
| RFC0057 Thoughts and Reflections on NWG/RFC 54 | June 1970 Status: UNKNOWN Autor: M. Kraley, J. Newkirk |
| RFC0058 Logical Message Synchronization | June 1970 Status: UNKNOWN Autor: T.P. Skinner |
| RFC0059 Flow Control - Fixed Versus Demand Allocation | June 1970 Status: UNKNOWN Autor: E. Meyer |
| RFC0060 Simplified NCP Protocol | July 1970 Status: UNKNOWN Autor: R.B. Kalin |
| RFC0061 Note on Interprocess Communication in a Resource Sharing Computer Network | July 1970 Status: UNKNOWN Autor: D.C. Walden |
| RFC0062 Systems for Interprocess Communication in a Resource Sharing Computer Network | August 1970 Status: UNKNOWN Autor: D.C. Walden |
| RFC0063 Belated Network Meeting Report | July 1970 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0064 Getting rid of marking | July 1970 Status: UNKNOWN Autor: M. Elie |
| RFC0065 Comments on Host/Host Protocol document #1 | August 1970 Status: UNKNOWN Autor: D.C. Walden |
| RFC0066 NIC - third level ideas and other noise | August 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0067 Proposed Change to Host/IMP Spec to Eliminate Marking | January 1970 Status: UNKNOWN Autor: W.R. Crowther |
| RFC0068 Comments on Memory Allocation Control Commands: CEASE, ALL, GVB, RET, and RFNM | August 1970 Status: UNKNOWN Autor: M. Elie |
| RFC0069 Distribution List Change for MIT | September 1970 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0070 Note on Padding | October 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0071 Reallocation in Case of Input Error | September 1970 Status: UNKNOWN Autor: T. Schipper |
| RFC0072 Proposed Moratorium on Changes to Network Protocol | September 1970 Status: UNKNOWN Autor: R.D. Bressler |
| RFC0073 Response to NWG/RFC 67 | September 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0074 Specifications for Network Use of the UCSB On-Line System | October 1970 Status: UNKNOWN Autor: J.E. White |
| RFC0075 Network Meeting | October 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0076 Connection by name: User oriented protocol | October 1970 Status: UNKNOWN Autor: J. Bouknight, J. Madden, G.R. Grossman |
| RFC0077 Network meeting report | November 1970 Status: UNKNOWN Autor: J. Postel |
| RFC0078 NCP Status Report: UCSB/Rand | October 1970 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner, J.E. White |
| RFC0079 Logger Protocol error | November 1970 Status: UNKNOWN Autor: E. Meyer |
| RFC0080 Protocols and Data Formats | December 1970 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0081 Request for Reference Information | December 1970 Status: UNKNOWN Autor: J. Bouknight |
| RFC0082 Network Meeting Notes | December 1970 Status: UNKNOWN Autor: E. Meyer |
| RFC0083 Language-machine for data reconfiguration | December 1970 Status: UNKNOWN Autor: R.H. Anderson, E. Harslem, J.F. Heafner |
| RFC0084 List of NWG/RFC's 1-80 | December 1970 Status: UNKNOWN Autor: J.B. North |
| RFC0085 Network Working Group meeting | December 1970 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0086 Proposal for a Network Standard Format for a Data Stream to Control Graphics Display | January 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0087 Topic for Discussion at the Next Network Working Group Meeting | January 1971 Status: UNKNOWN Autor: A. Vezza |
| RFC0088 NETRJS: A third level protocol for Remote Job Entry | January 1971 Status: UNKNOWN Autor: R.T. Braden, S.M. Wolfe |
| RFC0089 Some historic moments in networking | January 1971 Status: UNKNOWN Autor: R.M. Metcalfe |
| RFC0090 CCN as a Network Service Center | January 1971 Status: UNKNOWN Autor: R.T. Braden |
| RFC0091 Proposed User-User Protocol | December 1970 Status: UNKNOWN Autor: G.H. Mealy |
| RFC0093 Initial Connection Protocol | January 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0094 Some thoughts on Network Graphics | February 1971 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0095 Distribution of NWG/RFC's through the NIC | February 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0096 An Interactive Network Experiment to Study Modes of Access the Network Information Center | February 1971 Status: INFORMATIONAL Autor: R.W. Watson |
| RFC0097 First Cut at a Proposed Telnet Protocol | February 1971 Status: UNKNOWN Autor: J.T. Melvin, R.W. Watson |
| RFC0098 Logger Protocol Proposal | February 1971 Status: UNKNOWN Autor: E. Meyer, T. Skinner |
| RFC0099 Network Meeting | February 1971 Status: UNKNOWN Autor: P.M. Karp |
| RFC0100 Categorization and guide to NWG/RFCs | February 1971 Status: UNKNOWN Autor: P.M. Karp |
| RFC0101 Notes on the Network Working Group meeting, Urbana, Illinois, February 17, 1971 | February 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0102 Output of the Host-Host Protocol glitch cleaning committee | February 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0103 Implementation of Interrupt Keys | February 1971 Status: UNKNOWN Autor: R.B. Kalin |
| RFC0104 Link 191 | February 1971 Status: UNKNOWN Autor: J.B. Postel, S.D. Crocker |
| RFC0105 Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB | March 1971 Status: UNKNOWN Autor: J.E. White |
| RFC0106 User/Server Site Protocol Network Host Questionnaire | March 1971 Status: UNKNOWN Autor: T.C. O'Sullivan |
| RFC0107 Output of the Host-Host Protocol Glitch Cleaning Committee | March 1971 Status: UNKNOWN Autor: R.D. Bressler, S.D. Crocker, W.R. Crowther, G.R. Grossman, R.S. Tomlinson, J.E. White |
| RFC0108 Attendance list at the Urbana NWG meeting, February 17-19, 1971 | March 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0109 Level III Server Protocol for the Lincoln Laboratory 360/67 Host | March 1971 Status: UNKNOWN Autor: J. Winett |
| RFC0110 Conventions for Using an IBM 2741 Terminal as a User Console for Access to Network Server Hosts | March 1971 Status: UNKNOWN Autor: J. Winett |
| RFC0111 Pressure from the Chairman | March 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0112 User/Server Site Protocol: Network Host Questionnaire | April 1971 Status: UNKNOWN Autor: T.C. O'Sullivan |
| RFC0113 Network activity report: UCSB Rand | April 1971 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner, J.E. White |
| RFC0114 File Transfer Protocol | April 1971 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0115 Some Network Information Center policies on handling documents | April 1971 Status: UNKNOWN Autor: R.W. Watson, J.B. North |
| RFC0116 Structure of the May NWG Meeting | April 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0117 Some comments on the official protocol | April 1971 Status: UNKNOWN Autor: J. Wong |
| RFC0118 Recommendations for facility documentation | April 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0119 Network Fortran Subprograms | April 1971 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0120 Network PL1 subprograms | April 1971 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0121 Network on-line operators | April 1971 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0122 Network specifications for UCSB's Simple-Minded File System | April 1971 Status: UNKNOWN Autor: J.E. White |
| RFC0123 Proffered Official ICP | April 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0124 Typographical error in RFC 107 | April 1971 Status: UNKNOWN Autor: J.T. Melvin |
| RFC0125 Response to RFC 86: Proposal for Network Standard Format for a Graphics Data Stream | April 1971 Status: UNKNOWN Autor: J. McConnell |
| RFC0126 Graphics Facilities at Ames Research Center | April 1971 Status: UNKNOWN Autor: J. McConnell |
| RFC0127 Comments on RFC 123 | April 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0128 Bytes | April 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0129 Request for comments on socket name structure | April 1971 Status: UNKNOWN Autor: E. Harslem, J. Heafner, E. Meyer |
| RFC0130 Response to RFC 111: Pressure from the chairman | April 1971 Status: UNKNOWN Autor: J.F. Heafner |
| RFC0131 Response to RFC 116: May NWG meeting | April 1971 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0132 Typographical Error in RFC 107 | April 1971 Status: UNKNOWN Autor: J.E. White |
| RFC0133 File Transfer and Error Recovery | April 1971 Status: UNKNOWN Autor: R.L. Sunberg |
| RFC0134 Network Graphics meeting | April 1971 Status: UNKNOWN Autor: A. Vezza |
| RFC0135 Response to NWG/RFC 110 | April 1971 Status: UNKNOWN Autor: W. Hathaway |
| RFC0136 Host accounting and administrative procedures | April 1971 Status: UNKNOWN Autor: R.E. Kahn |
| RFC0137 Telnet Protocol - a proposed document | April 1971 Status: UNKNOWN Autor: T.C. O'Sullivan |
| RFC0138 Status report on proposed Data Reconfiguration Service | April 1971 Status: UNKNOWN Autor: R.H. Anderson, V.G. Cerf, E. Harslem, J.F. Heafner, J. Madden, R.M. Metcalfe, A. Shoshani, J.E. White, D.C.M. Wood |
| RFC0139 Discussion of Telnet Protocol | May 1971 Status: UNKNOWN Autor: T.C. O'Sullivan |
| RFC0140 Agenda for the May NWG meeting | May 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0141 Comments on RFC 114: A File Transfer Protocol | April 1971 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0142 Time-Out Mechanism in the Host-Host Protocol | May 1971 Status: UNKNOWN Autor: C. Kline, J. Wong |
| RFC0143 Regarding proffered official ICP | May 1971 Status: UNKNOWN Autor: W. Naylor, J. Wong, C. Kline, J. Postel |
| RFC0144 Data sharing on computer networks | April 1971 Status: UNKNOWN Autor: A. Shoshani |
| RFC0145 Initial Connection Protocol Control Commands | May 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0146 Views on issues relevant to data sharing on computer networks | May 1971 Status: UNKNOWN Autor: P.M. Karp, D.B. McKay, D.C.M. Wood |
| RFC0147 Definition of a socket | May 1971 Status: UNKNOWN Autor: J.M. Winett |
| RFC0148 Comments on RFC 123 | May 1971 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0149 Best Laid Plans | May 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0150 Use of IPC Facilities: A Working Paper | May 1971 Status: UNKNOWN Autor: R.B. Kalin |
| RFC0151 Comments on a proffered official ICP: RFCs 123, 127 | May 1971 Status: UNKNOWN Autor: A. Shoshani |
| RFC0152 SRI Artificial Intelligence status report | May 1971 Status: UNKNOWN Autor: M. Wilber |
| RFC0153 SRI ARC-NIC status | May 1971 Status: UNKNOWN Autor: J.T. Melvin, R.W. Watson |
| RFC0154 Exposition Style | May 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0155 ARPA Network mailing lists | May 1971 Status: UNKNOWN Autor: J.B. North |
| RFC0156 Status of the Illinois site: Response to RFC 116 | April 1971 Status: UNKNOWN Autor: J. Bouknight |
| RFC0157 Invitation to the Second Symposium on Problems in the Optimization of Data Communications Systems | May 1971 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0158 Telnet Protocol: A Proposed Document | May 1971 Status: UNKNOWN Autor: T.C. O'Sullivan |
| RFC0160 RFC brief list | May 1971 Status: UNKNOWN Autor: Network Information Center. Stanford Research Institute |
| RFC0161 Solution to the race condition in the ICP | May 1971 Status: UNKNOWN Autor: A. Shoshani |
| RFC0162 NETBUGGER3 | May 1971 Status: UNKNOWN Autor: M. Kampe |
| RFC0163 Data transfer protocols | May 1971 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0164 Minutes of Network Working Group meeting, 5/16 through 5/19/71 | May 1971 Status: UNKNOWN Autor: J.F. Heafner |
| RFC0165 Proffered Official Initial Connection Protocol | May 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0166 Data Reconfiguration Service: An implementation specification | May 1971 Status: UNKNOWN Autor: R.H. Anderson, V.G. Cerf, E. Harslem, J.F. Heafner, J. Madden, R.M. Metcalfe, A. Shoshani, J.E. White, D.C.M. Wood |
| RFC0167 Socket conventions reconsidered | May 1971 Status: UNKNOWN Autor: A.K. Bhushan, R.M. Metcalfe, J.M. Winett |
| RFC0168 ARPA Network mailing lists | May 1971 Status: UNKNOWN Autor: J.B. North |
| RFC0169 COMPUTER NETWORKS | May 1971 Status: UNKNOWN Autor: S.D. Crocker |
| RFC0170 RFC List by Number | June 1971 Status: UNKNOWN Autor: Network Information Center. Stanford Research Institute |
| RFC0171 The Data Transfer Protocol | June 1971 Status: UNKNOWN Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, J. Melvin, B. Sundberg, D. Watson, J. White |
| RFC0172 The File Transfer Protocol | June 1971 Status: UNKNOWN Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White |
| RFC0173 Network Data Management Committee Meeting Announcement | June 1971 Status: UNKNOWN Autor: P.M. Karp, D.B. McKay |
| RFC0174 UCLA - Computer Science Graphics Overview | June 1971 Status: UNKNOWN Autor: J. Postel, V.G. Cerf |
| RFC0175 Comments on "Socket Conventions Reconsidered" | June 1971 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0176 Comments on "Byte size for connections" | June 1971 Status: UNKNOWN Autor: A.K. Bhushan, R. Kanodia, R.M. Metcalfe, J. Postel |
| RFC0177 Device independent graphical display description | June 1971 Status: UNKNOWN Autor: J. McConnell |
| RFC0178 Network graphic attention handling | June 1971 Status: UNKNOWN Autor: I.W. Cotton |
| RFC0179 Link Number Assignments | June 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0180 File system questionnaire | June 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0181 Modifications to RFC 177 | July 1971 Status: UNKNOWN Autor: J. McConnell |
| RFC0182 Compilation of list of relevant site reports | June 1971 Status: UNKNOWN Autor: J.B. North |
| RFC0183 EBCDIC Codes and Their Mapping to ASCII | July 1971 Status: UNKNOWN Autor: J.M. Winett |
| RFC0184 Proposed graphic display modes | July 1971 Status: UNKNOWN Autor: K.C. Kelley |
| RFC0185 NIC distribution of manuals and handbooks | July 1971 Status: UNKNOWN Autor: J.B. North |
| RFC0186 Network graphics loader | July 1971 Status: UNKNOWN Autor: J.C. Michener |
| RFC0187 Network/440 Protocol Concept | July 1971 Status: UNKNOWN Autor: D.B. McKay, D.P. Karp |
| RFC0188 Data management meeting announcement | January 1971 Status: UNKNOWN Autor: P.M. Karp, D.B. McKay |
| RFC0189 Interim NETRJS specifications | July 1971 Status: UNKNOWN Autor: R.T. Braden |
| RFC0190 DEC PDP-10-IMLAC communications system | July 1971 Status: UNKNOWN Autor: L.P. Deutsch |
| RFC0191 Graphics implementation and conceptualization at Augmentation Research Center | July 1971 Status: UNKNOWN Autor: C.H. Irby |
| RFC0192 Some factors which a Network Graphics Protocol must consider | July 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0193 NETWORK CHECKOUT | July 1971 Status: UNKNOWN Autor: E. Harslem, J.F. Heafner |
| RFC0194 The Data Reconfiguration Service -- Compiler/Interpreter Implementation Notes | July 1971 Status: UNKNOWN Autor: V. Cerf, E. Harslem, J. Heafner, B. Metcalfe, J. White |
| RFC0195 Data computers-data descriptions and access language | July 1971 Status: UNKNOWN Autor: G.H. Mealy |
| RFC0196 Mail Box Protocol | July 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0197 Initial Connection Protocol - Reviewed | July 1971 Status: UNKNOWN Autor: A. Shoshani, E. Harslem |
| RFC0198 Site Certification - Lincoln Labs 360/67 | July 1971 Status: UNKNOWN Autor: J.F. Heafner |
| RFC0199 Suggestions for a Network Data-Tablet Graphics Protocol | July 1971 Status: UNKNOWN Autor: T. Williams |
| RFC0200 RFC list by number | August 1971 Status: UNKNOWN Autor: J.B. North |
| RFC0202 Possible Deadlock in ICP | July 1971 Status: UNKNOWN Autor: S.M. Wolfe, J. Postel |
| RFC0203 Achieving reliable communication | August 1971 Status: UNKNOWN Autor: R.B. Kalin |
| RFC0204 Sockets in use | August 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0205 NETCRT - a character display protocol | August 1971 Status: UNKNOWN Autor: R.T. Braden |
| RFC0206 A User TELNET Description of an Initial Implementation | August 1971 Status: UNKNOWN Autor: J. White |
| RFC0207 September Network Working Group meeting | August 1971 Status: UNKNOWN Autor: A. Vezza |
| RFC0208 Address tables | August 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0209 Host/IMP interface documentation | August 1971 Status: UNKNOWN Autor: B. Cosell |
| RFC0210 Improvement of Flow Control | August 1971 Status: UNKNOWN Autor: W. Conrad |
| RFC0211 ARPA Network Mailing Lists | August 1971 Status: UNKNOWN Autor: J.B. North |
| RFC0212 NWG meeting on network usage | August 1971 Status: UNKNOWN Autor: Information Sciences Institute University of Southern California |
| RFC0213 IMP System change notification | August 1971 Status: UNKNOWN Autor: B. Cosell |
| RFC0214 Network checkpoint | August 1971 Status: UNKNOWN Autor: E. Harslem |
| RFC0215 NCP, ICP, and Telnet: The Terminal IMP implementation | August 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0216 Telnet Access to UCSB's On-Line System | September 1971 Status: UNKNOWN Autor: J.E. White |
| RFC0217 Specifications changes for OLS, RJE/RJOR, and SMFS | September 1971 Status: UNKNOWN Autor: J.E. White |
| RFC0218 Changing the IMP status reporting facility | September 1971 Status: UNKNOWN Autor: B. Cosell |
| RFC0219 User's View of the Datacomputer | September 1971 Status: UNKNOWN Autor: R. Winter |
| RFC0221 Mail Box Protocol: Version 2 | August 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0222 Subject: System programmer's workshop | September 1971 Status: UNKNOWN Autor: R.M. Metcalfe |
| RFC0223 Network Information Center schedule for network users | September 1971 Status: UNKNOWN Autor: J.T. Melvin, R.W. Watson |
| RFC0224 Comments on Mailbox Protocol | September 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0225 Rand/UCSB network graphics experiment | September 1971 Status: UNKNOWN Autor: E. Harslem, R. Stoughton |
| RFC0226 Standardization of host mnemonics | September 1971 Status: UNKNOWN Autor: P.M. Karp |
| RFC0227 Data transfer rates (Rand/UCLA) | September 1971 Status: UNKNOWN Autor: J.F. Heafner, E. Harslem |
| RFC0228 Clarification | September 1971 Status: UNKNOWN Autor: D.C. Walden |
| RFC0229 Standard host names | September 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0230 Toward reliable operation of minicomputer-based terminals on a TIP | September 1971 Status: UNKNOWN Autor: T. Pyke |
| RFC0231 Service center standards for remote usage: A user's view | September 1971 Status: UNKNOWN Autor: J.F. Heafner, E. Harslem |
| RFC0232 Postponement of network graphics meeting | September 1971 Status: UNKNOWN Autor: A. Vezza |
| RFC0233 Standardization of host call letters | September 1971 Status: UNKNOWN Autor: A. Bhushan, R. Metcalfe |
| RFC0234 Network Working Group meeting schedule | October 1971 Status: UNKNOWN Autor: A. Vezza |
| RFC0235 Site status | September 1971 Status: UNKNOWN Autor: E. Westheimer |
| RFC0236 Standard host names | September 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0237 NIC view of standard host names | October 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0238 Comments on DTP and FTP proposals | September 1971 Status: UNKNOWN Autor: R.T. Braden |
| RFC0239 Host mnemonics proposed in RFC 226 (NIC 7625) | September 1971 Status: UNKNOWN Autor: R.T. Braden |
| RFC0240 Site Status | September 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0241 Connecting computers to MLC ports | September 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0242 Data Descriptive Language for Shared Data | July 1971 Status: UNKNOWN Autor: L. Haibt, A.P. Mullery |
| RFC0243 Network and data sharing bibliography | October 1971 Status: UNKNOWN Autor: A.P. Mullery |
| RFC0245 Reservations for Network Group meeting | October 1971 Status: UNKNOWN Autor: C. Falls |
| RFC0246 Network Graphics meeting | October 1971 Status: UNKNOWN Autor: A. Vezza |
| RFC0247 Proffered set of standard host names | October 1971 Status: UNKNOWN Autor: P.M. Karp |
| RFC0249 Coordination of equipment and supplies purchase | October 1971 Status: UNKNOWN Autor: R.F. Borelli |
| RFC0250 Some thoughts on file transfer | October 1971 Status: UNKNOWN Autor: H. Brodie |
| RFC0251 Weather data | October 1971 Status: UNKNOWN Autor: D. Stern |
| RFC0252 Network host status | October 1971 Status: UNKNOWN Autor: E. Westheimer |
| RFC0253 Second Network Graphics meeting details | October 1971 Status: UNKNOWN Autor: J.A. Moorer |
| RFC0254 Scenarios for using ARPANET computers | October 1971 Status: UNKNOWN Autor: A. Bhushan |
| RFC0255 Status of network hosts | October 1971 Status: UNKNOWN Autor: E. Westheimer |
| RFC0256 IMPSYS change notification | November 1971 Status: UNKNOWN Autor: B. Cosell |
| RFC0263 "Very Distant" Host interface | December 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0264 The Data Transfer Protocol | January 1972 Status: UNKNOWN Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenize, B. Sundberg, D. Watson, J. White |
| RFC0265 The File Transfer Protocol | November 1971 Status: UNKNOWN Autor: A. Bhushan, B. Braden, W. Crowther, E. Harslem, J. Heafner, A. McKenzie, J. Melvin, B. Sundberg, D. Watson, J. White |
| RFC0266 Network host status | November 1971 Status: UNKNOWN Autor: E. Westheimer |
| RFC0267 Network Host Status | November 1971 Status: UNKNOWN Autor: E. Westheimer |
| RFC0268 Graphics facilities information | November 1971 Status: UNKNOWN Autor: J. Postel |
| RFC0269 Some Experience with File Transfer | December 1971 Status: UNKNOWN Autor: H. Brodie |
| RFC0270 Correction to BBN Report No. 1822 (NIC NO 7958) | January 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0271 IMP System change notifications | January 1972 Status: UNKNOWN Autor: B. Cosell |
| RFC0273 More on standard host names | October 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0274 Establishing a local guide for network usage | November 1971 Status: UNKNOWN Autor: E. Forman |
| RFC0276 NIC course | November 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0278 Revision of the Mail Box Protocol | November 1971 Status: UNKNOWN Autor: A.K. Bhushan, R.T. Braden, E. Harslem, J.F. Heafner, A.M. McKenzie, J.T. Melvin, R.L. Sundberg, R.W. Watson, J.E. White |
| RFC0280 A Draft of Host Names | November 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0281 Suggested addition to File Transfer Protocol | December 1971 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0282 Graphics meeting report | December 1971 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0283 NETRJT: Remote Job Service Protocol for TIPS | December 1971 Status: UNKNOWN Autor: R.T. Braden |
| RFC0285 Network graphics | December 1971 Status: UNKNOWN Autor: D. Huff |
| RFC0286 Network Library Information System | December 1971 Status: UNKNOWN Autor: E. Forman |
| RFC0287 Status of Network Hosts | December 1971 Status: UNKNOWN Autor: E. Westheimer |
| RFC0288 Network host status | January 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0289 What we hope is an official list of host names | December 1971 Status: UNKNOWN Autor: R.W. Watson |
| RFC0290 Computer networks and data sharing: A bibliography | January 1972 Status: UNKNOWN Autor: A.P. Mullery |
| RFC0291 Data Management Meeting Announcement | January 1972 Status: UNKNOWN Autor: D.B. McKay |
| RFC0292 Graphics Protocol: Level 0 only | January 1972 Status: UNKNOWN Autor: J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer |
| RFC0293 Network Host Status | January 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0294 The Use of "Set Data Type" Transaction in File Transfer Protocol | January 1972 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0295 Report of the Protocol Workshop, 12 October 1971 | January 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0296 DS-1 Display System | January 1972 Status: UNKNOWN Autor: D.E. Liddle |
| RFC0297 TIP Message Buffers | January 1972 Status: UNKNOWN Autor: D.C. Walden |
| RFC0298 Network host status | February 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0299 Information Management System | February 1972 Status: UNKNOWN Autor: D. Hopkin |
| RFC0300 ARPA Network mailing lists | January 1972 Status: UNKNOWN Autor: J.B. North |
| RFC0301 BBN IMP (#5) and NCC Schedule March 4, 1971 | February 1972 Status: UNKNOWN Autor: R. Alter |
| RFC0302 Exercising The ARPANET | February 1972 Status: UNKNOWN Autor: R.F. Bryan |
| RFC0303 ARPA Network mailing lists | March 1972 Status: UNKNOWN Autor: Network Information Center. Stanford Research Institute |
| RFC0304 Data Management System Proposal for the ARPA Network | February 1972 Status: UNKNOWN Autor: D.B. McKay |
| RFC0305 Unknown Host Numbers | February 1972 Status: UNKNOWN Autor: R. Alter |
| RFC0306 Network host status | February 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0307 Using network Remote Job Entry | February 1972 Status: UNKNOWN Autor: E. Harslem |
| RFC0308 ARPANET host availability data | March 1972 Status: UNKNOWN Autor: M. Seriff |
| RFC0309 Data and File Transfer Workshop Announcement | March 1972 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0310 Another Look at Data and File Transfer Protocols | April 1972 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0311 New Console Attachments to the USCB Host | February 1972 Status: UNKNOWN Autor: R.F. Bryan |
| RFC0312 Proposed Change in IMP-to-Host Protocol | March 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0313 Computer based instruction | March 1972 Status: UNKNOWN Autor: T.C. O'Sullivan |
| RFC0314 Network Graphics Working Group Meeting | March 1972 Status: UNKNOWN Autor: I.W. Cotton |
| RFC0315 Network Host Status | March 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0316 ARPA Network Data Management Working Group | February 1972 Status: UNKNOWN Autor: D.B. McKay, A.P. Mullery |
| RFC0317 Official Host-Host Protocol Modification: Assigned Link Numbers | March 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0318 Telnet Protocols | April 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0319 Network Host Status | March 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0320 Workshop on Hard Copy Line Graphics | March 1972 Status: UNKNOWN Autor: R. Reddy |
| RFC0321 CBI Networking Activity at MITRE | March 1972 Status: UNKNOWN Autor: P.M. Karp |
| RFC0322 Well known socket numbers | March 1972 Status: UNKNOWN Autor: V. Cerf, J. Postel |
| RFC0323 Formation of Network Measurement Group (NMG) | March 1972 Status: UNKNOWN Autor: V. Cerf |
| RFC0324 RJE Protocol meeting | April 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0325 Network Remote Job Entry program - NETRJS | April 1972 Status: UNKNOWN Autor: G. Hicks |
| RFC0326 Network Host Status | April 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0327 Data and File Transfer workshop notes | April 1972 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0328 Suggested Telnet Protocol Changes | April 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0329 ARPA Network Mailing Lists | May 1972 Status: UNKNOWN Autor: Network Information Center. Stanford Research Institute |
| RFC0330 Network Host Status | April 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0331 IMP System Change Notification | April 1972 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0332 Network Host Status | April 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0333 Proposed experiment with a Message Switching Protocol | May 1972 Status: UNKNOWN Autor: R.D. Bressler, D. Murphy, D.C. Walden |
| RFC0334 Network Use on May 8 | May 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0335 New Interface - IMP/360 | May 1972 Status: UNKNOWN Autor: R.F. Bryan |
| RFC0336 Level 0 Graphic Input Protocol | May 1972 Status: UNKNOWN Autor: I.W. Cotton |
| RFC0338 EBCDIC/ASCII Mapping for Network RJE | May 1972 Status: UNKNOWN Autor: R.T. Braden |
| RFC0339 MLTNET: A "Multi Telnet" Subsystem for Tenex | May 1972 Status: UNKNOWN Autor: R. Thomas |
| RFC0340 Proposed Telnet Changes | May 1972 Status: UNKNOWN Autor: T.C. O'Sullivan |
| RFC0342 Network Host Status | May 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0343 IMP System change notification | May 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0344 Network Host Status | May 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0345 Interest in Mixed Integer Programming (MPSX on NIC 360/91 at CCN) | May 1972 Status: UNKNOWN Autor: K.C. Kelley |
| RFC0346 Satellite Considerations | May 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0347 Echo process | May 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0348 Discard Process | May 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0349 Proposed Standard Socket Numbers | May 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0350 User Accounts for UCSB On-Line System | May 1972 Status: UNKNOWN Autor: R. Stoughton |
| RFC0351 Graphics information form for the ARPANET graphics resources notebook | June 1972 Status: UNKNOWN Autor: D. Crocker |
| RFC0352 TIP Site Information Form | June 1972 Status: UNKNOWN Autor: D. Crocker |
| RFC0353 Network host status | June 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0354 File Transfer Protocol | July 1972 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0355 Response to NWG/RFC 346 | June 1972 Status: UNKNOWN Autor: J. Davidson |
| RFC0356 ARPA Network Control Center | June 1972 Status: UNKNOWN Autor: R. Alter |
| RFC0357 Echoing strategy for satellite links | June 1972 Status: UNKNOWN Autor: J. Davidson |
| RFC0359 Status of the Release of the New IMP System (2600) | June 1972 Status: UNKNOWN Autor: D.C. Walden |
| RFC0360 Proposed Remote Job Entry Protocol | June 1972 Status: UNKNOWN Autor: C. Holland |
| RFC0361 Deamon Processes on Host 106 | July 1972 Status: UNKNOWN Autor: R.D. Bressler |
| RFC0362 Network Host Status | June 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0363 ARPA Network mailing lists | August 1972 Status: UNKNOWN Autor: Network Information Center. Stanford Research Institute |
| RFC0364 Serving remote users on the ARPANET | July 1972 Status: UNKNOWN Autor: M.D. Abrams |
| RFC0365 Letter to All TIP Users | July 1972 Status: UNKNOWN Autor: D.C. Walden |
| RFC0366 Network Host Status | July 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0367 Network host status | July 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0368 Comments on "Proposed Remote Job Entry Protocol" | July 1972 Status: UNKNOWN Autor: R.T. Braden |
| RFC0369 Evaluation of ARPANET services January-March, 1972 | July 1972 Status: UNKNOWN Autor: J.R. Pickens |
| RFC0370 Network Host Status | July 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0371 Demonstration at International Computer Communications Conference | July 1972 Status: UNKNOWN Autor: R.E. Kahn |
| RFC0372 Notes on a Conversation with Bob Kahn on the ICCC | July 1972 Status: UNKNOWN Autor: R.W. Watson |
| RFC0373 Arbitrary Character Sets | July 1972 Status: UNKNOWN Autor: J. McCarthy |
| RFC0374 IMP System Announcement | July 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0376 Network Host Status | August 1972 Status: UNKNOWN Autor: E. Westheimer |
| RFC0377 Using TSO via ARPA Network Virtual Terminal | August 1972 Status: UNKNOWN Autor: R.T. Braden |
| RFC0378 Traffic statistics (July 1972) | August 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0379 Using TSO at CCN | August 1972 Status: UNKNOWN Autor: R. Braden |
| RFC0381 Three aids to improved network operation | July 1972 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0382 Mathematical Software on the ARPA Network | August 1972 Status: UNKNOWN Autor: L. McDaniel |
| RFC0384 Official site idents for organizations in the ARPA Network | August 1972 Status: UNKNOWN Autor: J.B. North |
| RFC0385 Comments on the File Transfer Protocol | August 1972 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0386 Letter to TIP users-2 | August 1972 Status: UNKNOWN Autor: B. Cosell, D.C. Walden |
| RFC0387 Some experiences in implementing Network Graphics Protocol Level 0 | August 1972 Status: UNKNOWN Autor: K.C. Kelley, J. Meir |
| RFC0388 NCP statistics | August 1972 Status: UNKNOWN Autor: V. Cerf |
| RFC0389 UCLA Campus Computing Network Liaison Staff for ARPA Network | August 1972 Status: UNKNOWN Autor: B. Noble |
| RFC0390 TSO Scenario | September 1972 Status: UNKNOWN Autor: R.T. Braden |
| RFC0391 Traffic statistics (August 1972) | September 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0392 Measurement of host costs for transmitting network data | September 1972 Status: UNKNOWN Autor: G. Hicks, B.D. Wessler |
| RFC0393 Comments on Telnet Protocol Changes | October 1972 Status: UNKNOWN Autor: J.M. Winett |
| RFC0394 Two Proposed Changes to the IMP-Host Protocol | September 1972 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0395 Switch Settings on IMPs and TIPs | October 1972 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0396 Network Graphics Working Group Meeting - Second Iteration | November 1972 Status: UNKNOWN Autor: S. Bunch |
| RFC0398 ICP Sockets | September 1972 Status: UNKNOWN Autor: J.R. Pickens, E. Faeh |
| RFC0399 SMFS Login and Logout | September 1972 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0400 Traffic Statistics (September 1972) | October 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0401 Conversion of NGP-0 Coordinates to Device Specific Coordinates | October 1972 Status: UNKNOWN Autor: J. Hansen |
| RFC0402 ARPA Network Mailing Lists | October 1972 Status: UNKNOWN Autor: J.B. North |
| RFC0403 Desirability of a Network 1108 Service | January 1973 Status: UNKNOWN Autor: G. Hicks |
| RFC0404 Host Address Changes Involving Rand and ISI | October 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0405 Correction to RFC 404 | October 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0406 Scheduled IMP Software Releases | October 1972 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0407 Remote Job Entry Protocol | October 1972 Status: HISTORIC Autor: R.D. Bressler, R. Guida, A.M. McKenzie |
| RFC0408 NETBANK | October 1972 Status: UNKNOWN Autor: A.D. Owen, J. Postel |
| RFC0409 Tenex interface to UCSB's Simple-Minded File System | December 1972 Status: UNKNOWN Autor: J.E. White |
| RFC0410 Removal of the 30-Second Delay When Hosts Come Up | November 1972 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0411 New MULTICS Network Software Features | November 1972 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0412 User FTP Documentation | November 1972 Status: UNKNOWN Autor: G. Hicks |
| RFC0413 Traffic statistics (October 1972) | November 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0414 File Transfer Protocol (FTP) status and further comments | December 1972 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0415 Tenex bandwidth | November 1972 Status: UNKNOWN Autor: H. Murray |
| RFC0416 ARC System Will Be Unavailable for Use During Thanksgiving Week | November 1972 Status: UNKNOWN Autor: J.C. Norton |
| RFC0417 Link usage violation | December 1972 Status: UNKNOWN Autor: J. Postel, C. Kline |
| RFC0418 Server File Transfer Under TSS/360 At NASA-Ames Research Center | November 1972 Status: UNKNOWN Autor: W. Hathaway |
| RFC0419 To: Network liaisons and station agents | December 1972 Status: UNKNOWN Autor: A. Vezza |
| RFC0420 CCA ICCC weather demo | January 1973 Status: UNKNOWN Autor: H. Murray |
| RFC0421 Software Consulting Service for Network Users | November 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0422 Traffic statistics (November 1972) | December 1972 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0423 UCLA Campus Computing Network Liaison Staff for ARPANET | December 1972 Status: UNKNOWN Autor: B. Noble |
| RFC0425 "But my NCP costs $500 a day" | December 1972 Status: UNKNOWN Autor: R.D. Bressler |
| RFC0426 Reconnection Protocol | January 1973 Status: UNKNOWN Autor: R. Thomas |
| RFC0429 Character Generator Process | December 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0430 Comments on File Transfer Protocol | February 1973 Status: UNKNOWN Autor: R.T. Braden |
| RFC0431 Update on SMFS Login and Logout | December 1972 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0432 Network logical map | December 1972 Status: UNKNOWN Autor: N. Neigus |
| RFC0433 Socket number list | December 1972 Status: UNKNOWN Autor: J. Postel |
| RFC0434 IMP/TIP memory retrofit schedule | January 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0435 Telnet issues | January 1973 Status: UNKNOWN Autor: B. Cosell, D.C. Walden |
| RFC0436 Announcement of RJS at UCSB | January 1973 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0437 Data Reconfiguration Service at UCSB | June 1973 Status: UNKNOWN Autor: E. Faeh |
| RFC0438 FTP server-server interaction | January 1973 Status: UNKNOWN Autor: R. Thomas, R. Clements |
| RFC0439 PARRY encounters the DOCTOR | January 1973 Status: UNKNOWN Autor: V. Cerf |
| RFC0440 Scheduled network software maintenance | January 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0441 Inter-Entity Communication - an experiment | January 1973 Status: UNKNOWN Autor: R.D. Bressler, R. Thomas |
| RFC0442 Current flow-control scheme for IMPSYS | January 1973 Status: UNKNOWN Autor: V. Cerf |
| RFC0443 Traffic statistics (December 1972) | January 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0445 IMP/TIP preventive maintenance schedule | January 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0446 Proposal to consider a network program resource notebook | January 1973 Status: UNKNOWN Autor: L.P. Deutsch |
| RFC0447 IMP/TIP memory retrofit schedule | January 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0448 Print files in FTP | February 1973 Status: UNKNOWN Autor: R.T. Braden |
| RFC0449 Current flow-control scheme for IMPSYS | January 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0450 MULTICS sampling timeout change | February 1973 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0451 Tentative proposal for a Unified User Level Protocol | February 1973 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0452 TELNET Command at Host LL | February 1973 Status: UNKNOWN Autor: J. Winett |
| RFC0453 Meeting announcement to discuss a network mail system | February 1973 Status: UNKNOWN Autor: M.D. Kudlick |
| RFC0454 File Transfer Protocol - meeting announcement and a new proposed document | February 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0455 Traffic statistics (January 1973) | February 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0456 Memorandum: Date change of mail meeting | February 1973 Status: UNKNOWN Autor: M.D. Kudlick |
| RFC0457 TIPUG | February 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0458 Mail retrieval via FTP | February 1973 Status: UNKNOWN Autor: R.D. Bressler, R. Thomas |
| RFC0459 Network questionnaires | February 1973 Status: UNKNOWN Autor: W. Kantrowitz |
| RFC0460 NCP survey | February 1973 Status: UNKNOWN Autor: C. Kline |
| RFC0461 Telnet Protocol meeting announcement | February 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0462 Responding to user needs | February 1973 Status: UNKNOWN Autor: J. Iseli, D. Crocker |
| RFC0463 FTP comments and response to RFC 430 | February 1973 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0464 Resource notebook framework | February 1973 Status: UNKNOWN Autor: M.D. Kudlick |
| RFC0466 Telnet logger/server for host LL-67 | February 1973 Status: UNKNOWN Autor: J.M. Winett |
| RFC0467 Proposed change to Host-Host Protocol: Resynchronization of connection status | February 1973 Status: UNKNOWN Autor: J.D. Burchfiel, R.S. Tomlinson |
| RFC0468 FTP data compression | March 1973 Status: UNKNOWN Autor: R.T. Braden |
| RFC0469 Network mail meeting summary | March 1973 Status: UNKNOWN Autor: M.D. Kudlick |
| RFC0470 Change in socket for TIP news facility | March 1973 Status: UNKNOWN Autor: R. Thomas |
| RFC0471 Workshop on multi-site executive programs | March 1973 Status: UNKNOWN Autor: R. Thomas |
| RFC0472 Illinois' reply to Maxwell's request for graphics information (NIC 14925) | March 1973 Status: UNKNOWN Autor: S. Bunch |
| RFC0473 MIX and MIXAL? | February 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0474 Announcement of NGWG meeting: Call for papers | March 1973 Status: UNKNOWN Autor: S. Bunch |
| RFC0475 FTP and Network Mail System | March 1973 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0476 IMP/TIP memory retrofit schedule (rev 2) | March 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0477 Remote Job Service at UCSB | May 1973 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0478 FTP server-server interaction - II | March 1973 Status: UNKNOWN Autor: R.D. Bressler, R. Thomas |
| RFC0479 Use of FTP by the NIC Journal | March 1973 Status: UNKNOWN Autor: J.E. White |
| RFC0480 Host-dependent FTP parameters | March 1973 Status: UNKNOWN Autor: J.E. White |
| RFC0482 Traffic statistics (February 1973) | March 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0483 Cancellation of the resource notebook framework meeting | March 1973 Status: UNKNOWN Autor: M.D. Kudlick |
| RFC0485 MIX and MIXAL at UCSB | March 1973 Status: UNKNOWN Autor: J.R. Pickens |
| RFC0486 Data transfer revisited | March 1973 Status: UNKNOWN Autor: R.D. Bressler |
| RFC0487 Free file transfer | April 1973 Status: UNKNOWN Autor: R.D. Bressler |
| RFC0488 NLS classes at network sites | March 1973 Status: UNKNOWN Autor: M.F. Auerbach |
| RFC0489 Comment on resynchronization of connection status proposal | March 1973 Status: UNKNOWN Autor: J. Postel |
| RFC0490 Surrogate RJS for UCLA-CCN | March 1973 Status: UNKNOWN Autor: J.R. Pickens |
| RFC0491 What is "Free"? | April 1973 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0492 Response to RFC 467 | April 1973 Status: UNKNOWN Autor: E. Meyer |
| RFC0493 GRAPHICS PROTOCOL | April 1973 Status: UNKNOWN Autor: J.C. Michener, I.W. Cotton, K.C. Kelley, D.E. Liddle, E. Meyer |
| RFC0494 Availability of MIX and MIXAL in the Network | April 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0495 Telnet Protocol specifications | May 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0496 TNLS quick reference card is available | April 1973 Status: UNKNOWN Autor: M.F. Auerbach |
| RFC0497 Traffic Statistics (March 1973) | April 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0498 On mail service to CCN | April 1973 Status: UNKNOWN Autor: R.T. Braden |
| RFC0499 Harvard's network RJE | April 1973 Status: UNKNOWN Autor: B.R. Reussow |
| RFC0500 Integration of data management systems on a computer network | April 1973 Status: UNKNOWN Autor: A. Shoshani, I. Spiegler |
| RFC0501 Un-muddling "free file transfer" | May 1973 Status: UNKNOWN Autor: K.T. Pogran |
| RFC0503 Socket number list | April 1973 Status: UNKNOWN Autor: N. Neigus, J. Postel |
| RFC0504 Distributed resources workshop announcement | April 1973 Status: UNKNOWN Autor: R. Thomas |
| RFC0505 Two solutions to a file transfer access problem | June 1973 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0506 FTP command naming problem | June 1973 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0508 Real-time data transmission on the ARPANET | May 1973 Status: UNKNOWN Autor: L. Pfeifer, J. McAfee |
| RFC0509 Traffic statistics (April 1973) | April 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0510 Request for network mailbox addresses | May 1973 Status: UNKNOWN Autor: J.E. White |
| RFC0511 Enterprise phone service to NIC from ARPANET sites | May 1973 Status: UNKNOWN Autor: J.B. North |
| RFC0512 More on lost message detection | May 1973 Status: UNKNOWN Autor: W. Hathaway |
| RFC0513 Comments on the new Telnet specifications | May 1973 Status: UNKNOWN Autor: W. Hathaway |
| RFC0514 Network make-work | June 1973 Status: UNKNOWN Autor: W. Kantrowitz |
| RFC0515 Specifications for Datalanguage, Version 0/9 | June 1973 Status: UNKNOWN Autor: R. Winter |
| RFC0516 Lost message detection | May 1973 Status: UNKNOWN Autor: J. Postel |
| RFC0518 ARPANET accounts | June 1973 Status: UNKNOWN Autor: N. Vaughan, E.J. Feinler |
| RFC0519 Resource Evaluation | June 1973 Status: UNKNOWN Autor: J.R. Pickens |
| RFC0520 Memo to FTP group: Proposal for File Access Protocol | June 1973 Status: UNKNOWN Autor: J.D. Day |
| RFC0521 Restricted use of IMP DDT | May 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0522 Traffic Statistics (May 1973) | June 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0523 SURVEY is in operation again | June 1973 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0524 Proposed Mail Protocol | June 1973 Status: UNKNOWN Autor: J.E. White |
| RFC0525 MIT-MATHLAB meets UCSB-OLS -an example of resource sharing | June 1973 Status: UNKNOWN Autor: W. Parrish, J.R. Pickens |
| RFC0526 Technical meeting: Digital image processing software systems | June 1973 Status: UNKNOWN Autor: W.K. Pratt |
| RFC0527 ARPAWOCKY | May 1973 Status: UNKNOWN Autor: R. Merryman |
| RFC0528 Software checksumming in the IMP and network reliability | June 1973 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0529 Note on protocol synch sequences | June 1973 Status: UNKNOWN Autor: A.M. McKenzie, R. Thomas, R.S. Tomlinson, K.T. Pogran |
| RFC0530 Report on the Survey Project | June 1973 Status: UNKNOWN Autor: A.K. Bhushan |
| RFC0531 Feast or famine? A response to two recent RFC's about network information | June 1973 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0532 UCSD-CC Server-FTP facility | July 1973 Status: UNKNOWN Autor: R.G. Merryman |
| RFC0533 Message-ID numbers | July 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0534 Lost message detection | July 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0535 Comments on File Access Protocol | July 1973 Status: UNKNOWN Autor: R. Thomas |
| RFC0537 Announcement of NGG meeting July 16-17 | June 1973 Status: UNKNOWN Autor: S. Bunch |
| RFC0538 Traffic statistics (June 1973) | July 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0539 Thoughts on the mail protocol proposed in RFC 524 | July 1973 Status: UNKNOWN Autor: D. Crocker, J. Postel |
| RFC0542 File Transfer Protocol | August 1973 Status: UNKNOWN Autor: N. Neigus |
| RFC0543 Network journal submission and delivery | July 1973 Status: UNKNOWN Autor: N.D. Meyer |
| RFC0544 Locating on-line documentation at SRI-ARC | July 1973 Status: UNKNOWN Autor: N.D. Meyer, K. Kelley |
| RFC0545 Of what quality be the UCSB resources evaluators? | July 1973 Status: UNKNOWN Autor: J.R. Pickens |
| RFC0546 Tenex load averages for July 1973 | August 1973 Status: UNKNOWN Autor: R. Thomas |
| RFC0547 Change to the Very Distant Host specification | August 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0548 Hosts using the IMP Going Down message | August 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0549 Minutes of Network Graphics Group meeting, 15-17 July 1973 | July 1973 Status: UNKNOWN Autor: J.C. Michener |
| RFC0550 NIC NCP experiment | August 1973 Status: UNKNOWN Autor: L.P. Deutsch |
| RFC0551 NYU, ANL, and LBL Joining the Net | August 1973 Status: UNKNOWN Autor: Y. Feinroth, R. Fink |
| RFC0552 Single access to standard protocols | July 1973 Status: UNKNOWN Autor: A.D. Owen |
| RFC0553 Draft design for a text/graphics protocol | July 1973 Status: UNKNOWN Autor: C.H. Irby, K. Victor |
| RFC0555 Responses to critiques of the proposed mail protocol | July 1973 Status: UNKNOWN Autor: J.E. White |
| RFC0556 Traffic Statistics (July 1973) | August 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0557 REVELATIONS IN NETWORK HOST MEASUREMENTS | August 1973 Status: UNKNOWN Autor: B.D. Wessler |
| RFC0559 Comments on The New Telnet Protocol and its Implementation | August 1973 Status: UNKNOWN Autor: A.K. Bushan |
| RFC0560 Remote Controlled Transmission and Echoing Telnet option | August 1973 Status: UNKNOWN Autor: D. Crocker, J. Postel |
| RFC0561 Standardizing Network Mail Headers | September 1973 Status: UNKNOWN Autor: A.K. Bhushan, K.T. Pogran, R.S. Tomlinson, J.E. White |
| RFC0562 Modifications to the TELNET Specification | August 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0563 Comments on the RCTE Telnet option | August 1973 Status: UNKNOWN Autor: J. Davidson |
| RFC0565 Storing network survey data at the datacomputer | August 1973 Status: UNKNOWN Autor: D. Cantor |
| RFC0566 Traffic statistics (August 1973) | September 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0567 Cross Country Network Bandwidth | September 1973 Status: UNKNOWN Autor: L.P. Deutsch |
| RFC0568 Response to RFC 567 - cross country network bandwidth | September 1973 Status: UNKNOWN Autor: J.M. McQuillan |
| RFC0569 NETED: A Common Editor for the ARPA Network | October 1973 Status: HISTORIC Autor: M.A. Padlipsky |
| RFC0570 Experimental input mapping between NVT ASCII and UCSB On Line System | October 1973 Status: UNKNOWN Autor: J.R. Pickens |
| RFC0571 TENEX FTP PROBLEM | November 1973 Status: UNKNOWN Autor: R. Braden |
| RFC0573 DATA AND FILE TRANSFER - SOME MEASUREMENT RESULTS | September 1973 Status: UNKNOWN Autor: A. Bhushan |
| RFC0574 Announcement of a Mail Facility at UCSB | September 1973 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0576 Proposal for modifying linking | September 1973 Status: UNKNOWN Autor: K. Victor |
| RFC0577 Mail priority | October 1973 Status: UNKNOWN Autor: D. Crocker |
| RFC0578 Using MIT-Mathlab MACSYMA from MIT-DMS Muddle | October 1973 Status: UNKNOWN Autor: A.K. Bhushan, N.D. Ryan |
| RFC0579 Traffic statistics (September 1973) | November 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0580 Note to Protocol Designers and Implementers | October 1973 Status: UNKNOWN Autor: J. Postel |
| RFC0581 Corrections to RFC 560: Remote Controlled Transmission and Echoing Telnet Option | November 1973 Status: UNKNOWN Autor: D. Crocker, J. Postel |
| RFC0582 Comments on RFC 580: Machine readable protocols | November 1973 Status: UNKNOWN Autor: R. Clements |
| RFC0584 Charter for ARPANET Users Interest Working Group | November 1973 Status: UNKNOWN Autor: J. Iseli, D. Crocker, N. Neigus |
| RFC0585 ARPANET users interest working group meeting | November 1973 Status: UNKNOWN Autor: D. Crocker, N. Neigus, E.J. Feinler, J. Iseli |
| RFC0586 Traffic statistics (October 1973) | November 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0587 Announcing New Telnet Options | November 1973 Status: UNKNOWN Autor: J. Postel |
| RFC0588 London Node Is Now Up | October 1973 Status: UNKNOWN Autor: A. Stokes |
| RFC0589 CCN NETRJS server messages to remote user | November 1973 Status: UNKNOWN Autor: R.T. Braden |
| RFC0590 MULTICS address change | November 1973 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0591 Addition to the Very Distant Host specifications | November 1973 Status: UNKNOWN Autor: D.C. Walden |
| RFC0592 Some thoughts on system design to facilitate resource sharing | November 1973 Status: UNKNOWN Autor: R.W. Watson |
| RFC0593 Telnet and FTP implementation schedule change | November 1973 Status: UNKNOWN Autor: A.M. McKenzie, J. Postel |
| RFC0594 Speedup of Host-IMP interface | December 1973 Status: UNKNOWN Autor: J.D. Burchfiel |
| RFC0595 Second thoughts in defense of the Telnet Go-Ahead | December 1973 Status: UNKNOWN Autor: W. Hathaway |
| RFC0596 Second thoughts on Telnet Go-Ahead | December 1973 Status: UNKNOWN Autor: E.A. Taft |
| RFC0597 Host status | December 1973 Status: UNKNOWN Autor: N. Neigus, E.J. Feinler |
| RFC0598 RFC index - December 5, 1973 | December 1973 Status: UNKNOWN Autor: Network Information Center. Stanford Research Institute |
| RFC0599 Update on NETRJS | December 1973 Status: UNKNOWN Autor: R.T. Braden |
| RFC0600 Interfacing an Illinois plasma terminal to the ARPANET Discusses some unusual interface issues for the Plato terminal. | November 1973 Status: UNKNOWN Autor: A. Berggreen |
| RFC0601 Traffic statistics (November 1973) | December 1973 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0602 "The stockings were hung by the chimney with care" Susceptibility of ARPANET to security violations. | December 1973 Status: UNKNOWN Autor: R.M. Metcalfe |
| RFC0603 Response to RFC 597: Host status Questions about the ARPANET topology described in RFC 597. | December 1973 Status: UNKNOWN Autor: J.D. Burchfiel |
| RFC0604 Assigned link numbers Modifies official host-host protocol. Replaces RFC 377. | December 1973 Status: UNKNOWN Autor: J. Postel |
| RFC0606 Host names on-line Resolving differences in hostname-address mappings; see also RFCs 627, 625, 623 and 608. | December 1973 Status: UNKNOWN Autor: L.P. Deutsch |
| RFC0607 Comments on the File Transfer Protocol An old version; see RFC 624; see also RFCs 614, 542 and 640. | January 1974 Status: UNKNOWN Autor: M. Krilanovich, G. Gregg |
| RFC0608 Host names on-line Response to RFC 606; see also RFCs 627, 625 and 623. | January 1974 Status: UNKNOWN Autor: M.D. Kudlick |
| RFC0609 Statement of upcoming move of NIC/NLS service See also RFCs 621 and 620. | January 1974 Status: UNKNOWN Autor: B. Ferguson |
| RFC0610 Further datalanguage design concepts Preliminary results of the language design; a model for data languagea semantics; future considerations. | December 1973 Status: UNKNOWN Autor: R. Winter, J. Hill, W. Greiff |
| RFC0611 Two changes to the IMP/Host Protocol to improve user/network communications Expansion of Host-Going-Down and addition of Dead-Host-Status Message. | February 1974 Status: UNKNOWN Autor: D.C. Walden |
| RFC0612 Traffic statistics (December 1973) | January 1974 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0613 Network connectivity: A response to RFC 603 | January 1974 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0614 Response to RFC 607: "Comments on the File Transfer Protocol" See also RFCs 624, 542 and 640. | January 1974 Status: UNKNOWN Autor: K.T. Pogran, N. Neigus |
| RFC0615 Proposed Network Standard Data Pathname syntax | March 1974 Status: UNKNOWN Autor: D. Crocker |
| RFC0616 LATEST NETWORK MAPS | February 1973 Status: UNKNOWN Autor: D. Walden |
| RFC0617 Note on socket number assignment Danger of imposing more fixed socket number requirements; see also RFCs 542, 503 and 451. | February 1974 Status: UNKNOWN Autor: E.A. Taft |
| RFC0618 Few observations on NCP statistics Distribution of NCP and IMP message types by actual measurement. | February 1974 Status: UNKNOWN Autor: E.A. Taft |
| RFC0619 Mean round-trip times in the ARPANET Actual measurements of round-trip times. | March 1974 Status: UNKNOWN Autor: W. Naylor, H. Opderbeck |
| RFC0620 Request for monitor host table updates In conjunction with moving NIC users to OFFICE-1; see also RFCs 621 and 609. | March 1974 Status: UNKNOWN Autor: B. Ferguson |
| RFC0621 NIC user directories at SRI ARC See also RFCs 620 and 609. | March 1974 Status: UNKNOWN Autor: M.D. Kudlick |
| RFC0622 Scheduling IMP/TIP down time Modification of previous policy. | March 1974 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0623 Comments on on-line host name service See also RFCs 627, 625, 608 and 606. | February 1974 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0624 Comments on the File Transfer Protocol Design changes and slight modifications. Replaces RFC 607; see also RFCs 614, 542 and 640. | February 1974 Status: UNKNOWN Autor: M. Krilanovich, G. Gregg, W. Hathaway, J.E. White |
| RFC0625 On-line hostnames service See also RFCs 606, 608, 623 and 627. | March 1974 Status: UNKNOWN Autor: M.D. Kudlick, E.J. Feinler |
| RFC0626 On a possible lockup condition in IMP subnet due to message sequencing | March 1974 Status: UNKNOWN Autor: L. Kleinrock, H. Opderbeck |
| RFC0627 ASCII text file of hostnames See also RFCs 606, 608, 623 and 625. | March 1974 Status: UNKNOWN Autor: M.D. Kudlick, E.J. Feinler |
| RFC0628 Status of RFC numbers and a note on pre-assigned journal numbers | March 1974 Status: UNKNOWN Autor: M.L. Keeney |
| RFC0629 Scenario for using the Network Journal | March 1974 Status: UNKNOWN Autor: J.B. North |
| RFC0630 FTP error code usage for more reliable mail service Describes FTP reply-code usage in TENEX mail processing. | April 1974 Status: UNKNOWN Autor: J. Sussman |
| RFC0631 International meeting on minicomputers and data communication: Call for papers | April 1974 Status: UNKNOWN Autor: A. Danthine |
| RFC0632 Throughput degradations for single packet messages | May 1974 Status: UNKNOWN Autor: H. Opderbeck |
| RFC0633 IMP/TIP preventive maintenance schedule An old version; see RFC 638. | March 1974 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0634 Change in network address for Haskins Lab | April 1974 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0635 Assessment of ARPANET protocols Theoretical and practical motivation for redesign. Multipacket messages; host retransmission; duplicate detection; sequencing; acknowledgement. | April 1974 Status: UNKNOWN Autor: V. Cerf |
| RFC0636 TIP/Tenex reliability improvements Obtaining/maintaining connections; recovery from lost connections; connection-state changes. | June 1974 Status: UNKNOWN Autor: J.D. Burchfiel, B. Cosell, R.S. Tomlinson, D.C. Walden |
| RFC0637 Change of network address for SU-DSL | April 1974 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0638 IMP/TIP preventive maintenance schedule Corrects RFC 633. | April 1974 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0640 Revised FTP reply codes Updates RFC 542. | June 1974 Status: UNKNOWN Autor: J. Postel |
| RFC0642 Ready line philosophy and implementation | July 1974 Status: UNKNOWN Autor: J.D. Burchfiel |
| RFC0643 Network Debugging Protocol To be used in an implementation of a PDP-11 network bootstrap device and a cross-network debugger. | July 1974 Status: UNKNOWN Autor: E. Mader |
| RFC0644 On the problem of signature authentication for network mail | July 1974 Status: UNKNOWN Autor: R. Thomas |
| RFC0645 Network Standard Data Specification syntax Providing a mechanism for specifying all attributes of a collection of bits; see also RFC 615. | June 1974 Status: UNKNOWN Autor: D. Crocker |
| RFC0647 Proposed protocol for connecting host computers to ARPA-like networks via front end processors Approaches to Front-End protocol processing using available hardware and software. | November 1974 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0651 Revised Telnet status option | October 1974 Status: UNKNOWN Autor: D. Crocker |
| RFC0652 Telnet output carriage-return disposition option | October 1974 Status: HISTORIC Autor: D. Crocker |
| RFC0653 Telnet output horizontal tabstops option | October 1974 Status: HISTORIC Autor: D. Crocker |
| RFC0654 Telnet output horizontal tab disposition option | October 1974 Status: HISTORIC Autor: D. Crocker |
| RFC0655 Telnet output formfeed disposition option | October 1974 Status: HISTORIC Autor: D. Crocker |
| RFC0656 Telnet output vertical tabstops option | October 1974 Status: HISTORIC Autor: D. Crocker |
| RFC0657 Telnet output vertical tab disposition option | October 1974 Status: HISTORIC Autor: D. Crocker |
| RFC0658 Telnet output linefeed disposition | October 1974 Status: HISTORIC Autor: D. Crocker |
| RFC0659 Announcing additional Telnet options Options defined in RFCs 651-658. | October 1974 Status: UNKNOWN Autor: J. Postel |
| RFC0660 Some changes to the IMP and the IMP/Host interface Decoupling of message number sequences of hosts; host-host access control; message number window; messages outside normal mechanism; see also BBN 1822. | October 1974 Status: UNKNOWN Autor: D.C. Walden |
| RFC0661 Protocol information An old version; see RFC 694. | November 1974 Status: UNKNOWN Autor: J. Postel |
| RFC0662 Performance improvement in ARPANET file transfers from Multics Experimenting with host output buffers to improve throughput. | November 1974 Status: UNKNOWN Autor: R. Kanodia |
| RFC0663 Lost message detection and recovery protocol Proposed extension of host-host protocol; see also RFCs 534, 516, 512, 492 and 467. | November 1974 Status: UNKNOWN Autor: R. Kanodia |
| RFC0666 Specification of the Unified User-Level Protocol Discusses and proposes a common command language. | November 1974 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0667 Host Ports Approved scheme to connect host ports to the network. | December 1974 Status: UNKNOWN Autor: S.G. Chipman |
| RFC0669 November, 1974, survey of New-Protocol Telnet servers An earlier poll of Telnet server implementation status. Updates RFC 702; see also RFCs 703 and 679. | December 1974 Status: UNKNOWN Autor: D.W. Dodds |
| RFC0671 Note on Reconnection Protocol Experience with implementation in RSEXEC context. | December 1974 Status: UNKNOWN Autor: R. Schantz |
| RFC0672 Multi-site data collection facility Applicability of TIP/TENEX protocols beyond TIP accounting. | December 1974 Status: UNKNOWN Autor: R. Schantz |
| RFC0674 Procedure call documents: Version 2 Host level protocol used in the NSW--a slightly constrained version of ARPANET Host-to-Host protocol, affecting allocation, RFNM wait, and retransmission; see also RFC 684. | December 1974 Status: UNKNOWN Autor: J. Postel, J.E. White |
| RFC0675 Specification of Internet Transmission Control Program The first detailed specification of TCP; see RFC 793. | December 1974 Status: UNKNOWN Autor: V. Cerf, Y. Dalal, C. Sunshine |
| RFC0677 Maintenance of duplicate databases | January 1975 Status: UNKNOWN Autor: P.R. Johnson, R. Thomas |
| RFC0678 Standard file formats For transmission of documents across different environments. | December 1974 Status: UNKNOWN Autor: J. Postel |
| RFC0679 February, 1975, survey of New-Protocol Telnet servers An earlier poll of Telnet server implementation status. Updates RFCs 701, 702 and 669; see also RFC 703. | February 1975 Status: UNKNOWN Autor: D.W. Dodds |
| RFC0680 Message Transmission Protocol Extends message field definition beyond RFC 561 attempts to establish syntactic and semantic standards for ARPANET; see also RFCs 733 and 822. | April 1975 Status: UNKNOWN Autor: T.H. Myer, D.A. Henderson |
| RFC0681 Network UNIX Capabilities as an ARPANET Mini-Host: standard I/O, Telnet, NCP, Hardware/Software requirements, reliability, availability. | March 1975 Status: UNKNOWN Autor: S. Holmgren |
| RFC0683 FTPSRV - Tenex extension for paged files Defines an extension to FTP for page-mode transfers between TENEX systems; also discusses file transfer reliability. | April 1975 Status: UNKNOWN Autor: R. Clements |
| RFC0684 Commentary on procedure calling as a network protocol Issues in designing distributed computing systems. Shortcomings of RFC 674; see also RFCs 542 and 354. | April 1975 Status: UNKNOWN Autor: R. Schantz |
| RFC0685 Response time in cross network debugging The contribution of ARPANET communication to response time. | April 1975 Status: UNKNOWN Autor: M. Beeler |
| RFC0686 Leaving well enough alone Discusses difference between early and later versions of FTP; see also RFCs 691, 640, 630, 542, 454, 448, 414, 385 and 354. | May 1975 Status: UNKNOWN Autor: B. Harvey |
| RFC0687 IMP/Host and Host/IMP Protocol changes Addressing hosts on more than 63 IMPs, and other backwards compatible expansions; see also RFCs 690 and 692. | June 1975 Status: UNKNOWN Autor: D.C. Walden |
| RFC0688 Tentative schedule for the new Telnet implementation for the TIP | June 1975 Status: UNKNOWN Autor: D.C. Walden |
| RFC0689 Tenex NCP finite state machine for connections Describes the internal states of an NCP connection in the TENEX implementation. | May 1975 Status: UNKNOWN Autor: R. Clements |
| RFC0690 Comments on the proposed Host/IMP Protocol changes Comments on suggestions in RFC 687; see also RFCs 692 and 696. | June 1975 Status: UNKNOWN Autor: J. Postel |
| RFC0691 One more try on the FTP Slight revision of RFC 686, on the subject of print files; see also RFCs 640, 630, 542, 454, 448, 414, 385 and 354. | June 1975 Status: UNKNOWN Autor: B. Harvey |
| RFC0692 Comments on IMP/Host Protocol changes (RFCs 687 and 690) A proposed solution to the problem of combined length of IMP and Host leaders; see also RFCs 696, 690 and 687. | June 1975 Status: UNKNOWN Autor: S.M. Wolfe |
| RFC0694 Protocol information References to documents and contacts concerning the various protocols used in the ARPANET, as well as recent developments; updates RFC 661. | June 1975 Status: UNKNOWN Autor: J. Postel |
| RFC0695 Official change in Host-Host Protocol Corrects ambiguity concerning the ERR command; changes NIC 8246 and NIC 7104. | July 1975 Status: UNKNOWN Autor: M. Krilanovich |
| RFC0696 Comments on the IMP/Host and Host/IMP Protocol changes Observations on current international standards recommendations from IFIP working group 6.1; see also RFCs 692, 690, 687. | July 1975 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0697 CWD command of FTP Discusses FTP login access to "files only" directories. | July 1975 Status: UNKNOWN Autor: J. Lieb |
| RFC0698 Telnet extended ASCII option Describes an option to allow transmission of a special kind of extended ASCII used at the Stanford AI and MIT AI Labs. | July 1975 Status: PROPOSED STANDARD Autor: T. Mock |
| RFC0699 Request For Comments summary notes: 600-699 | November 1982 Status: INFORMATIONAL Autor: J. Postel, J. Vernon |
| RFC0700 Protocol experiment | August 1974 Status: UNKNOWN Autor: E. Mader, W.W. Plummer, R.S. Tomlinson |
| RFC0701 August, 1974, survey of New-Protocol Telnet servers | August 1974 Status: UNKNOWN Autor: D.W. Dodds |
| RFC0702 September, 1974, survey of New-Protocol Telnet servers | September 1974 Status: UNKNOWN Autor: D.W. Dodds |
| RFC0703 July, 1975, survey of New-Protocol Telnet Servers | July 1975 Status: UNKNOWN Autor: D.W. Dodds |
| RFC0704 IMP/Host and Host/IMP Protocol change | September 1975 Status: UNKNOWN Autor: P.J. Santos |
| RFC0705 Front-end Protocol B6700 version | November 1975 Status: UNKNOWN Autor: R.F. Bryan |
| RFC0706 On the junk mail problem | November 1975 Status: UNKNOWN Autor: J. Postel |
| RFC0707 High-level framework for network-based resource sharing | December 1975 Status: UNKNOWN Autor: J.E. White |
| RFC0708 Elements of a Distributed Programming System | January 1976 Status: UNKNOWN Autor: J.E. White |
| RFC0712 Distributed Capability Computing System (DCCS) | February 1976 Status: UNKNOWN Autor: J.E. Donnelley |
| RFC0713 MSDTP-Message Services Data Transmission Protocol | April 1976 Status: UNKNOWN Autor: J. Haverty |
| RFC0714 Host-Host Protocol for an ARPANET-Type Network | April 1976 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC0716 Interim Revision to Appendix F of BBN 1822 | May 1976 Status: UNKNOWN Autor: D.C. Walden, J. Levin |
| RFC0717 Assigned Network Numbers | July 1976 Status: HISTORIC Autor: J. Postel |
| RFC0718 Comments on RCTE from the Tenex Implementation Experience | June 1976 Status: UNKNOWN Autor: J. Postel |
| RFC0719 Discussion on RCTE | July 1976 Status: UNKNOWN Autor: J. Postel |
| RFC0720 Address Specification Syntax for Network Mail | August 1976 Status: UNKNOWN Autor: D. Crocker |
| RFC0721 Out-of-Band Control Signals in a Host-to-Host Protocol | September 1976 Status: UNKNOWN Autor: L.L. Garlick |
| RFC0722 Thoughts on Interactions in Distributed Services | September 1976 Status: UNKNOWN Autor: J. Haverty |
| RFC0724 Proposed official standard for the format of ARPA Network messages | May 1977 Status: UNKNOWN Autor: D. Crocker, K.T. Pogran, J. Vittal, D.A. Henderson |
| RFC0725 RJE protocol for a resource sharing network | March 1977 Status: UNKNOWN Autor: J.D. Day, G.R. Grossman |
| RFC0726 Remote Controlled Transmission and Echoing Telnet option | March 1977 Status: PROPOSED STANDARD Autor: J. Postel, D. Crocker |
| RFC0727 Telnet logout option | April 1977 Status: PROPOSED STANDARD Autor: M.R. Crispin |
| RFC0728 Minor pitfall in the Telnet Protocol | April 1977 Status: UNKNOWN Autor: J.D. Day |
| RFC0729 Telnet byte macro option | May 1977 Status: UNKNOWN Autor: D. Crocker |
| RFC0730 Extensible field addressing | May 1977 Status: UNKNOWN Autor: J. Postel |
| RFC0731 Telnet Data Entry Terminal option | June 1977 Status: UNKNOWN Autor: J.D. Day |
| RFC0732 Telnet Data Entry Terminal option | September 1977 Status: UNKNOWN Autor: J.D. Day |
| RFC0733 Standard for the format of ARPA network text messages | November 1977 Status: UNKNOWN Autor: D. Crocker, J. Vittal, K.T. Pogran, D.A. Henderson |
| RFC0734 SUPDUP Protocol | October 1977 Status: HISTORIC Autor: M.R. Crispin |
| RFC0735 Revised Telnet byte macro option | November 1977 Status: PROPOSED STANDARD Autor: D. Crocker, R.H. Gumpertz |
| RFC0736 Telnet SUPDUP option | October 1977 Status: PROPOSED STANDARD Autor: M.R. Crispin |
| RFC0737 FTP extension: XSEN | October 1977 Status: UNKNOWN Autor: K. Harrenstien |
| RFC0738 Time server | October 1977 Status: UNKNOWN Autor: K. Harrenstien |
| RFC0739 Assigned numbers | November 1977 Status: HISTORIC Autor: J. Postel |
| RFC0740 NETRJS Protocol | November 1977 Status: HISTORIC Autor: R.T. Braden |
| RFC0741 Specifications for the Network Voice Protocol (NVP) | November 1977 Status: UNKNOWN Autor: D. Cohen |
| RFC0742 NAME/FINGER Protocol | December 1977 Status: UNKNOWN Autor: K. Harrenstien |
| RFC0743 FTP extension: XRSQ/XRCP | December 1977 Status: UNKNOWN Autor: K. Harrenstien |
| RFC0744 MARS - a Message Archiving and Retrieval Service | January 1978 Status: UNKNOWN Autor: J. Sattley |
| RFC0745 JANUS interface specifications | March 1978 Status: UNKNOWN Autor: M. Beeler |
| RFC0746 SUPDUP graphics extension | March 1978 Status: UNKNOWN Autor: R. Stallman |
| RFC0747 Recent extensions to the SUPDUP Protocol | March 1978 Status: UNKNOWN Autor: M.R. Crispin |
| RFC0748 Telnet randomly-lose option | April 1978 Status: UNKNOWN Autor: M.R. Crispin |
| RFC0749 Telnet SUPDUP-Output option | September 1978 Status: PROPOSED STANDARD Autor: B. Greenberg |
| RFC0750 Assigned numbers | September 1978 Status: HISTORIC Autor: J. Postel |
| RFC0751 Survey of FTP mail and MLFL | December 1978 Status: UNKNOWN Autor: P.D. Lebling |
| RFC0752 Universal host table | January 1979 Status: UNKNOWN Autor: M.R. Crispin |
| RFC0753 Internet Message Protocol | March 1979 Status: UNKNOWN Autor: J. Postel |
| RFC0754 Out-of-net host addresses for mail | April 1979 Status: UNKNOWN Autor: J. Postel |
| RFC0755 Assigned numbers | May 1979 Status: HISTORIC Autor: J. Postel |
| RFC0756 NIC name server - a datagram-based information utility | July 1979 Status: UNKNOWN Autor: J.R. Pickens, E.J. Feinler, J.E. Mathis |
| RFC0757 Suggested solution to the naming, addressing, and delivery problem for ARPANET message systems | September 1979 Status: UNKNOWN Autor: D.P. Deutsch |
| RFC0758 Assigned numbers | August 1979 Status: HISTORIC Autor: J. Postel |
| RFC0759 Internet Message Protocol | August 1980 Status: HISTORIC Autor: J. Postel |
| RFC0760 DoD standard Internet Protocol | January 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0761 DoD standard Transmission Control Protocol | January 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0762 Assigned numbers | January 1980 Status: HISTORIC Autor: J. Postel |
| RFC0763 Role mailboxes | May 1980 Status: UNKNOWN Autor: M.D. Abrams |
| RFC0764 Telnet Protocol specification | June 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0765 File Transfer Protocol specification | June 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0766 Internet Protocol Handbook: Table of contents | July 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0767 Structured format for transmission of multi-media documents | August 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0768 User Datagram Protocol | August 1980 Status: STANDARD Autor: J. Postel |
| RFC0769 Rapicom 450 facsimile file format | September 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0770 Assigned numbers | September 1980 Status: HISTORIC Autor: J. Postel |
| RFC0771 Mail transition plan | September 1980 Status: UNKNOWN Autor: V.G. Cerf, J. Postel |
| RFC0772 Mail Transfer Protocol | September 1980 Status: UNKNOWN Autor: S. Sluizer, J. Postel |
| RFC0773 Comments on NCP/TCP mail service transition strategy | October 1980 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0774 Internet Protocol Handbook: Table of contents | October 1980 Status: UNKNOWN Autor: J. Postel |
| RFC0775 Directory oriented FTP commands | December 1980 Status: UNKNOWN Autor: D. Mankins, D. Franklin, A.D. Owen |
| RFC0776 Assigned numbers | January 1981 Status: HISTORIC Autor: J. Postel |
| RFC0777 Internet Control Message Protocol | April 1981 Status: UNKNOWN Autor: J. Postel |
| RFC0778 DCNET Internet Clock Service | April 1981 Status: HISTORIC Autor: D.L. Mills |
| RFC0779 Telnet send-location option | April 1981 Status: PROPOSED STANDARD Autor: E. Killian |
| RFC0780 Mail Transfer Protocol | May 1981 Status: UNKNOWN Autor: S. Sluizer, J. Postel |
| RFC0781 Specification of the Internet Protocol (IP) timestamp option | May 1981 Status: UNKNOWN Autor: Z. Su |
| RFC0782 Virtual Terminal management model | January 1981 Status: UNKNOWN Autor: J. Nabielsky, A.P. Skelton |
| RFC0783 TFTP Protocol (revision 2) | June 1981 Status: UNKNOWN Autor: K.R. Sollins |
| RFC0784 Mail Transfer Protocol: ISI TOPS20 implementation | July 1981 Status: UNKNOWN Autor: S. Sluizer, J. Postel |
| RFC0785 Mail Transfer Protocol: ISI TOPS20 file definitions | July 1981 Status: UNKNOWN Autor: S. Sluizer, J. Postel |
| RFC0786 Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface | July 1981 Status: UNKNOWN Autor: S. Sluizer, J. Postel |
| RFC0787 Connectionless data transmission survey/tutorial | July 1981 Status: UNKNOWN Autor: A.L. Chapin |
| RFC0788 Simple Mail Transfer Protocol | November 1981 Status: UNKNOWN Autor: J. Postel |
| RFC0789 Vulnerabilities of network control protocols: An example | July 1981 Status: UNKNOWN Autor: E.C. Rosen |
| RFC0790 Assigned numbers | September 1981 Status: HISTORIC Autor: J. Postel |
| RFC0791 Internet Protocol | September 1981 Status: STANDARD Autor: J. Postel |
| RFC0792 Internet Control Message Protocol | September 1981 Status: STANDARD Autor: J. Postel |
| RFC0793 Transmission Control Protocol | September 1981 Status: STANDARD Autor: J. Postel |
| RFC0794 Pre-emption | September 1981 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0795 Service mappings | September 1981 Status: UNKNOWN Autor: J. Postel |
| RFC0796 Address mappings | September 1981 Status: UNKNOWN Autor: J. Postel |
| RFC0797 Format for Bitmap files | September 1981 Status: UNKNOWN Autor: A.R. Katz |
| RFC0798 Decoding facsimile data from the Rapicom 450 | September 1981 Status: UNKNOWN Autor: A.R. Katz |
| RFC0799 Internet name domains | September 1981 Status: UNKNOWN Autor: D.L. Mills |
| RFC0800 Request For Comments summary notes: 700-799 This RFC is a slightly annotated list of the 100 RFCs from RFC 700 through RFC 799. This is a status report on these RFCs. | November 1982 Status: INFORMATIONAL Autor: J. Postel, J. Vernon |
| RFC0801 NCP/TCP transition plan This RFC discusses the conversion of hosts from NCP to TCP. And making available the principle services: Telnet, File Transfer, and Mail. These protocols allow all hosts in the ARPA community to share a common interprocess communication environment. | November 1981 Status: UNKNOWN Autor: J. Postel |
| RFC0802 ARPANET 1822L Host Access Protocol This document proposed two major changes to the current ARPANET host access protocol. The first change will allow hosts to use logical addressing (i.e., host addresses that are independent of their physical location on the ARPANET) to communicate with each other, and the second will allow a host to shorten the amount of time that it may be blocked by its IMP after it presents a message to the network (currently, the IMP can block further input from a host for up to 15 seconds). See RFCs 852 and 851. | November 1981 Status: UNKNOWN Autor: A.G. Malis |
| RFC0803 Dacom 450/500 facsimile data transcoding The first part of this RFC describes in detail the Dacom 450 data compression algorithms and is an update and correction to an earlier memorandum. The second part of this RFC describes briefly the Dacom 500 data compression algorithm as used by the INTELPOST electronic-mail network under development by the US Postal Service and several foreign administrators. | November 1981 Status: UNKNOWN Autor: A. Agarwal, M.J. O'Connor, D.L. Mills |
| RFC0804 CCITT draft recommendation T.4 This is the CCITT standard for group 3 facsimile encoding. This is useful for data compression of bit map data. | January 1981 Status: UNKNOWN Autor: International Telegraph and Telephone Consultative Committee of the International Telecommunication Union |
| RFC0805 Computer mail meeting notes This RFC consists of notes from a meeting that was held at USC Information Sciences Institute on 11 January 1982, to discuss addressing issues in computer mail. The major conclusion reached at the meeting is to extend the "username@hostname" mailbox format to "username@host.domain", where the domain itself can be further strutured. | February 1982 Status: UNKNOWN Autor: J. Postel |
| RFC0806 Proposed Federal Information Processing Standard: Specification for message format for computer based message systems This RFC deals with Computer Based Message systems which provides a basis for interaction between different CBMS by defining the format of messages passed between them. This RFC is replaced by RFC 841. | September 1981 Status: UNKNOWN Autor: National Bureau of Standards |
| RFC0807 Multimedia mail meeting notes This RFC consists of notes from a meeting held at USC Information Sciences Institute on the 12th of January to discuss common interests in multimedia computer mail issues and to agree on some specific initial experiments. | February 1982 Status: UNKNOWN Autor: J. Postel |
| RFC0808 Summary of computer mail services meeting held at BBN on 10 January 1979 This RFC is a very belated attempt to document a meeting that was held three years earlier to discuss the state of computer mail in the ARPA community and to reach some conclusions to guide the further development of computer mail systems such that a coherent total mail service would continue to be provided. | March 1982 Status: UNKNOWN Autor: J. Postel |
| RFC0809 UCL facsimile system This RFC describes the features of the computerised facsimile system developed in the Department of Computer Science at UCL. First its functions are considered and the related experimental work are reported. Then the disciplines for system design are discussed. Finally, the implementation of the system are described, while detailed description are given as appendices. | February 1982 Status: UNKNOWN Autor: T. Chang |
| RFC0810 DoD Internet host table specification This RFC specifies a new host table format applicable to both ARPANET and Internet needs. In addition to host name to host address translation and selected protocol information, we have also included network and gateway name to address correspondence, and host operating system information. This RFC obsoletes the host table described in RFC 608. | March 1982 Status: UNKNOWN Autor: E.J. Feinler, K. Harrenstien, Z. Su, V. White |
| RFC0811 Hostnames Server This RFC gives a description of what the Hostnames Server is and how to access it. The function of this particular server is to deliver machine-readable name/address information describing networks, gateways, hosts, and eventually domains, within the internet environment. | March 1982 Status: UNKNOWN Autor: K. Harrenstien, V. White, E.J. Feinler |
| RFC0812 NICNAME/WHOIS This RFC gives a description of what the NICNAME/WHOIS Server is and how to access it. This server together with the corresponding Identification Data Base provides online directory look-up equivalent to the ARPANET Directory. | March 1982 Status: UNKNOWN Autor: K. Harrenstien, V. White |
| RFC0813 Window and Acknowledgement Strategy in TCP This RFC describes implementation strategies to deal with two mechanisms in TCP, the window and the acknowledgement. It also presents a particular set of algorithms which have received testing in the field, and which appear to work properly with each other. With more experience, these algorithms may become part of the formal specification, until such time their use is recommended. | July 1982 Status: UNKNOWN Autor: D.D. Clark |
| RFC0814 Name, addresses, ports, and routes This RFC gives suggestions and guidance for the design of the tables and algorithms necessary to keep track of these various sorts of identifiers inside a host implementation of TCP/IP. | July 1982 Status: UNKNOWN Autor: D.D. Clark |
| RFC0815 IP datagram reassembly algorithms This RFC describes an alternate approach of dealing with reassembly which reduces the bookkeeping problem to a minimum, and requires only one buffer for storage equal in size to the final datagram being reassembled, which can reassemble a datagram from any number of fragments arriving in any order with any possible pattern of overlap and duplication, and which is appropriate for almost any sort of operating system. | July 1982 Status: UNKNOWN Autor: D.D. Clark |
| RFC0816 Fault isolation and recovery This RFC describes the portion of fault isolation and recovery which is the responsibility of the host. | July 1982 Status: UNKNOWN Autor: D.D. Clark |
| RFC0817 Modularity and efficiency in protocol implementation This RFC will discuss some of the commonly encountered reasons why protocol implementations seem to run slowly. | July 1982 Status: UNKNOWN Autor: D.D. Clark |
| RFC0818 Remote User Telnet service This RFC is the specification of an application protocol. Any host that implements this application level service must follow this protocol. | November 1982 Status: HISTORIC Autor: J. Postel |
| RFC0819 Domain naming convention for Internet user applications This RFC is an attempt to clarify the generalization of the Domain Naming Convention, the Internet Naming Convention, and to explore the implications of its adoption for Internet name service and user applications. | August 1982 Status: UNKNOWN Autor: Z. Su, J. Postel |
| RFC0820 Assigned numbers This RFC is an old version, see RFC 870. | August 1982 Status: HISTORIC Autor: J. Postel |
| RFC0821 Simple Mail Transfer Protocol The objective of Simple Mail Transfer Protocol (SMTP) is to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. Obsoletes RFC 788, 780, and 772. | August 1982 Status: STANDARD Autor: J. Postel |
| RFC0822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952. | August 1982 Status: STANDARD Autor: D. Crocker |
| RFC0823 DARPA Internet gateway This RFC is a status report on the Internet Gateway developed by BBN. It describes the Internet Gateway as of September 1982. This memo presents detailed descriptions of message formats and gateway procedures, however, this is not an implementation specification, and such details are subject to change. | September 1982 Status: HISTORIC Autor: R.M. Hinden, A. Sheltzer |
| RFC0824 CRONUS Virtual Local Network The purpose of this note is to describe the CRONUS Virtual Local Network, especially the addressing related features. These features include a method for mapping between Internet Addresses and Local Network addresses. This is a topic of current concern in the ARPA Internet community. This note is intended to stimulate discussion. This is not a specification of an Internet Standard. | August 1982 Status: UNKNOWN Autor: W.I. MacGregor, D.C. Tappan |
| RFC0825 Request for comments on Requests For Comments This RFC is intended to clarify the status of RFCs and to provide some guidance for the authors of RFCs in the future. It is in a sense a specification for RFCs. | November 1982 Status: UNKNOWN Autor: J. Postel |
| RFC0826 Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware The purpose of this RFC is to present a method of Converting Protocol Addresses (e.g., IP addresses) to Local Network Addresses (e.g., Ethernet addresses). This is an issue of general concern in the ARPA Internet Community at this time. The method proposed here is presented for your consideration and comment. This is not the specification of an Internet Standard. | November 1982 Status: STANDARD Autor: D. Plummer |
| RFC0827 Exterior Gateway Protocol (EGP) This RFC is proposed to establish a standard for Gateway to Gateway procedures that allow the Gateways to be mutually suspicious. This document is a DRAFT for that standard. Your comments are strongly encouraged. | October 1982 Status: UNKNOWN Autor: E.C. Rosen |
| RFC0828 Data communications: IFIP's international "network" of experts This RFC is distributed to inform the ARPA Internet community of the activities of the IFIP technical committee on Data Communications, and to encourage participation in those activities. | August 1982 Status: UNKNOWN Autor: K. Owen |
| RFC0829 Packet satellite technology reference sources This RFC describes briefly the packet satellite technology developed by the Defense Advanced Research Projects Agency and several other participating organizations in the U.K. and Norway and provides a bibliography of relevant papers for researchers interested in experimental and operational experience with this dynamic satellite-sharing technique. | November 1982 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0830 Distributed system for Internet name service This RFC proposes a distributed name service for DARPA Internet. Its purpose is to focus discussion on the subject. It is hoped that a general consensus will emerge leading eventually to the adoption of standards. | October 1982 Status: UNKNOWN Autor: Z. Su |
| RFC0831 Backup access to the European side of SATNET The purpose of this RFC is to focus discussion on a particular Internet problem: a backup path for software maintenance of the European sector of the Internet, for use when SATNET is partitioned. We propose a mechanism, based upon the Source Routing option of IP, to reach European Internet sites via the VAN Gateway and UCL. This proposal is not intended as a standard at this time. | December 1982 Status: UNKNOWN Autor: R.T. Braden |
| RFC0832 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 7-Dec-82. | December 1982 Status: UNKNOWN Autor: D. Smallberg |
| RFC0833 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 14-Dec-82. | December 1982 Status: UNKNOWN Autor: D. Smallberg |
| RFC0834 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 22-Dec-82. | December 1982 Status: UNKNOWN Autor: D. Smallberg |
| RFC0835 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 2-Dec-82. The tests were run on 28-Dec-82 through 5-Jan-83. | December 1982 Status: UNKNOWN Autor: D. Smallberg |
| RFC0836 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 20-Dec-82. The tests were run on 4-Jan-83 through 5-Jan-83. | January 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0837 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 11-Jan-83. | January 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0838 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 18-Jan-83. | January 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0839 Who talks TCP? This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 31-Dec-82. The tests were run on 25-Jan-83. | January 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0840 Official protocols This RFC has been revised, see RFC 880. | April 1983 Status: HISTORIC Autor: J. Postel |
| RFC0841 Specification for message format for Computer Based Message Systems This RFC is FIPS 98. The purpose of distributing this document as an RFC is to make it easily accessible to the ARPA research community. This RFC does not specify a standard for the ARPA Internet. Obsoletes RFC 806. | January 1983 Status: UNKNOWN Autor: National Bureau of Standards |
| RFC0842 Who talks TCP? - survey of 1 February 83 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 28-Jan-83. The tests were run on 1-Feb-83 and on 2-Feb-83 ISI-VAXA.ARPA. | February 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0843 Who talks TCP? - survey of 8 February 83 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 8-Feb-83 and on 9-Feb-83 from ISI-VAXA.ARPA. | February 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0844 Who talks ICMP, too? - Survey of 18 February 1983 This survey determines how many hosts are able to respond to TELENET connections from a user at a class C site. This requires, in addition to IP and TCP, participation in gateway routing via ICMP and handling of Class C addresses. The list of hosts was taken from RFC 843, extracting only those hosts which are listed there as accepting TELNET connection. The tests were run on 18-Feb-83. | February 1983 Status: UNKNOWN Autor: R. Clements |
| RFC0845 Who talks TCP? - survey of 15 February 1983 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 3-Feb-83. The tests were run on 15-Feb-83 from ISI-VAXA.ARPA. | February 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0846 Who talks TCP? - survey of 22 February 1983 This RFC is a survey of hosts to identify the implementation status of Telnet, FTP, and Mail on TCP. The list of hosts was taken from the NIC hostname table of 18-Feb-83. The tests were run on 22-Feb-83 from ISI-VAXA.ARPA. | February 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0847 Summary of Smallberg surveys This is a summary of the surveys of Telnet, FTP and Mail (SMTP) servers conducted by David Smallberg in December 1982, January and February 1983 as reported in RFC 832-843, 845-846. This memo extracts the number of hosts that accepted the connection to their server for each of Telnet, FTP, and SMTP, and compares it to the total host in the Internet (not counting TACs or ECHOS). | February 1983 Status: UNKNOWN Autor: A. Westine, D. Smallberg, J. Postel |
| RFC0848 Who provides the "little" TCP services? This RFC lists those hosts which provide any of these "little" TCP services: The list of hosts were taken from the NIC hostname table of 24-Feb-83. The tests were run on February 23 and 24, and March 3 and 5 from ISI-VAXA.ARPA. | March 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0849 Suggestions for improved host table distribution This RFC actually is a request for comments. The issue dealt with is that of a naming registry update procedure, both as exists currently and what could exist in the future. None of the proposed solutions are intended as standards at this time; rather it is hoped that a general consensus will emerge as the appropriate solution, leaving eventually to the adoption of standards. | May 1983 Status: UNKNOWN Autor: M.R. Crispin |
| RFC0850 Standard for interchange of USENET messages This memo is distributed as an RFC only to make this information easily accessible to researchers in the ARPA community. It does not specify an Internet standard. This RFC defines the standard format for interchange of Network News articles among USENET sites. It describes the format for articles themselves, and gives partial standards for transmission of news. The news transmission is not entirely standardized in order to give a good deal of flexibility to the individual hosts to choose transmission hardware and software, whether to batch news and so on. | June 1983 Status: UNKNOWN Autor: M.R. Horton |
| RFC0851 ARPANET 1822L Host Access Protocol This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822's physical port locations to address each other. This RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802. | April 1983 Status: UNKNOWN Autor: A.G. Malis |
| RFC0852 ARPANET short blocking feature This RFC specifies the ARPANET Short Blocking Feature, which will allow ARPANET hosts to optionally shorten the IMP's host blocking timer. This Feature is a replacement of the ARPANET non-blocking host interface, which was never implemented, and will be available to hosts using either the 1822 or 1822L Host Access Protocol. This RFC is also being presented as a solicitation of comments on the Short Blocking Feature, especially from host network software implementers and maintainers. | April 1983 Status: UNKNOWN Autor: A.G. Malis |
| RFC0854 Telnet Protocol Specification This is the specification of the Telnet protocol used for remote terminal access in the ARPA Internet. The purpose of the TELNET Protocol is to provide a fairly general, bi-directional, eight-bit byte oriented communications facility. Its primary goal is to allow a standard method of interfacing terminal devices and terminal-oriented processes to each other. It is envisioned that the protocol may also be used for terminal-terminal communication ("linking") and process-process communication (distributed computation). This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 18639. | May 1983 Status: STANDARD Autor: J. Postel, J.K. Reynolds |
| RFC0855 Telnet Option Specifications This memo specifies the general form for Telnet options and the directions for their specification. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651, NIC 18640. | May 1983 Status: STANDARD Autor: J. Postel, J.K. Reynolds |
| RFC0856 Telnet Binary Transmission This Telnet Option enables a binary data mode between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15389. | May 1983 Status: STANDARD Autor: J. Postel, J. Reynolds |
| RFC0857 Telnet Echo Option This Telnet Option enables remote echoing by the other Telnet module. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15390. | May 1983 Status: STANDARD Autor: J. Postel, J. Reynolds |
| RFC0858 Telnet Suppress Go Ahead Option This Telnet Option disables the exchange of go-ahead signals between the Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 15392. | May 1983 Status: STANDARD Autor: J. Postel, J. Reynolds |
| RFC0859 Telnet Status Option This Telnet Option provides a way to determine the other Telnet module's view of the status of options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes RFC 651 (NIC 31154). | May 1983 Status: STANDARD Autor: J. Postel, J. Reynolds |
| RFC0860 Telnet Timing Mark Option This Telnet Option provides a way to check the roundtrip path between two Telnet modules. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16238. | May 1983 Status: STANDARD Autor: J. Postel, J. Reynolds |
| RFC0861 Telnet Extended Options: List Option This Telnet Option provides a mechanism for extending the set of possible options. This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet are expected to adopt and implement this standard. Obsoletes NIC 16239. | May 1983 Status: STANDARD Autor: J. Postel, J. Reynolds |
| RFC0862 Echo Protocol This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Echo Protocol are expected to adopt and implement this standard. The Echo service simply sends back to the originating source any data it receives. | May 1983 Status: STANDARD Autor: J. Postel |
| RFC0863 Discard Protocol This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Discard Protocol are expected to adopt and implement this standard. The Discard service simply throws away any data it receives. | May 1983 Status: STANDARD Autor: J. Postel |
| RFC0864 Character Generator Protocol This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. The Character Generator service simply sends data without regard to the input. | May 1983 Status: STANDARD Autor: J. Postel |
| RFC0865 Quote of the Day Protocol This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Quote of the Day Protocol are expected to adopt and implement this standard. The Quote of the Day service simply sends a short message without regard to the input. | May 1983 Status: STANDARD Autor: J. Postel |
| RFC0866 Active users This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement an Active Users Protocol are expected to adopt and implement this standard. The Active Users service simply sends a list of the currently active users on the host without regard to the input. | May 1983 Status: STANDARD Autor: J. Postel |
| RFC0867 Daytime Protocol This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Daytime Protocol are expected to adopt and implement this standard. The Daytime service simply sends the current date and time as a character string without regard to the input. | May 1983 Status: STANDARD Autor: J. Postel |
| RFC0868 Time Protocol This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Time Protocol are expected to adopt and implement this standard. This protocol provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900. | May 1983 Status: STANDARD Autor: J. Postel, K. Harrenstien |
| RFC0869 Host Monitoring Protocol This RFC specifies the Host Monitoring Protocol used to collect information from various types of hosts in the Internet. Designers of Internet communications software are encouraged to consider this protocol as a means of monitoring the behavior of their creations. | December 1983 Status: HISTORIC Autor: R. Hinden |
| RFC0870 Assigned numbers This RFC documents the list of numbers assigned for networks, protocols, etc. Obsoletes RFCs 820, 790, 776, 770, 762, 758, 755, 750, 739, 604. | October 1983 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC0871 Perspective on the ARPANET reference model This RFC is primarily intended as a perspective on the ARM and points out some of the differences between the ARM and the ISORM which were expressed by members in NWG general meetings, NWG protocol design committee meetings, the ARPA Internet Working Group, and private conversations over the intervening years. Originally published as M82-47 by the MITRE Corporation, Bedford, Massachusetts. | September 1982 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0872 TCP-on-a-LAN This memo attacks the notion that TCP cannot be appropriate for use on a Local Area Network. Originally published as M82-48 by the MITRE Corporation, Bedford Massachusetts. | September 1982 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0873 Illusion of vendor support This memo takes issue with the claim that international standards in computer protocols presently provide a basis for low cost vendor supported protocol implementations. Originally published as M82-49 by the MITRE Corporation, Bedford, Massachusetts. | September 1982 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0874 Critique of X.25 This RFC is an analysis of X.25 pointing out some problems in the conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security, and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts. | September 1982 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0875 Gateways, architectures, and heffalumps This RFC is a discussion about the role of gateways in an internetwork, especially the problems of translating or mapping protocols between different protocol suites. The discussion notes possible functionality mis-matches, undesirable routing "singularity points", flow control issues, and high cost of translating gateways. Originally published as M82-51 by the MITRE Corporation, Bedford, Massachusetts. | September 1982 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0876 Survey of SMTP implementations This RFC is a survey of implementation status. It does not specify an official protocol, but rather notes the status of implementation of aspects of a protocol. It is expected that the status of the hosts reported on will change. This information must be treated as a snapshot of the state of these implemetations. | September 1983 Status: UNKNOWN Autor: D. Smallberg |
| RFC0877 Standard for the transmission of IP datagrams over public data networks This RFC specifies a standard adopted by CSNET, the VAN gateway, and other organizations for the transmission of IP datagrams over the X.25-based public data networks. | September 1983 Status: UNKNOWN Autor: J.T. Korb |
| RFC0878 ARPANET 1822L Host Access Protocol This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. The 1822L procedure allows ARPANET hosts to use logical identifiers as well as 1822 physical interface identifiers to address each other. | December 1983 Status: UNKNOWN Autor: A.G. Malis |
| RFC0879 TCP maximum segment size and related topics This RFC discusses the TCP Maximum Segment Size Option and related topics. The purposes is to clarify some aspects of TCP and its interaction with IP. This memo is a clarification to the TCP specification, and contains information that may be considered as "advice to implementers". | November 1983 Status: UNKNOWN Autor: J. Postel |
| RFC0880 Official protocols This RFC identifies the documents specifying the official protocols used in the ARPA Internet. Annotations identify any revisions or changes planned. Obsoletes RFC 840. | October 1983 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC0881 Domain names plan and schedule This RFC outlines a plan and schedule for the implementation of domain style names throughout the DDN/ARPA Internet community. The introduction of domain style names will impact all hosts on the DDN/ARPA Internet. | November 1983 Status: UNKNOWN Autor: J. Postel |
| RFC0882 Domain names: Concepts and facilities This RFC introduces domain style names, their use for ARPA Internet mail and host address support, and the protocol and servers used to implement domain name facilities. | November 1983 Status: UNKNOWN Autor: P.V. Mockapetris |
| RFC0883 Domain names: Implementation specification This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software. | November 1983 Status: UNKNOWN Autor: P.V. Mockapetris |
| RFC0884 Telnet terminal type option This RFC specifies a standard for the ARPA Internet community. It specifies a method for exchanging terminal type information in the Telnet protocol. | December 1983 Status: UNKNOWN Autor: M. Solomon, E. Wimmers |
| RFC0885 Telnet end of record option This RFC specifies a standard for the ARPA Internet community. It specifies a method for marking the end of records in data transmitted on Telnet connections. | December 1983 Status: PROPOSED STANDARD Autor: J. Postel |
| RFC0886 Proposed standard for message header munging This RFC specifies a draft standard for the ARPA Internet community. It describes the rules to be used when transforming mail from the conventions of one message system to those of another message system. In particular, the treatment of header fields, and recipient addresses is specified. | December 1983 Status: UNKNOWN Autor: M.T. Rose |
| RFC0887 Resource Location Protocol This RFC specifies a draft standard for the ARPA Internet community. It describes a resource location protocol for use in the ARPA Internet. It is most useful on networks employing technologies which support some method of broadcast addressing, however it may also be used on other types of networks. For maximum benefit, all hosts which provide significant resources or services to other hosts on the Internet should implement this protocol. Hosts failing to implement the Resource Location Protocol risk being ignored by other hosts which are attempting to locate resources on the Internet. | December 1983 Status: EXPERIMENTAL Autor: M. Accetta |
| RFC0888 "STUB" Exterior Gateway Protocol This RFC describes the Exterior Gateway Protocol used to connect Stub Gateways to an Autonomous System of core Gateways. This document specifies the working protocol, and defines an ARPA official protocol. All implementers of Gateways should carefully review this document. | January 1984 Status: UNKNOWN Autor: L. Seamonson, E.C. Rosen |
| RFC0889 Internet Delay Experiments This memo reports on some measurements of round-trip times in the Internet and suggests some possible improvements to the TCP retransmission timeout calculation. This memo is both a status report on the Internet and advice to TCP implementers. | December 1983 Status: UNKNOWN Autor: D.L. Mills |
| RFC0890 Exterior Gateway Protocol implementation schedule This memo is a policy statement on the implementation of the Exterior Gateway Protocol in the Internet. This is an official policy statement of ICCB and DARPA. After 1-Aug-84 there shall be no dumb gateways in the Internet. Every gateway must be a member of some autonomous system. Some gateway of each autonomous system must exchange routing information with some gateway of the core autonomous system using the Exterior Gateway Protocol. | February 1984 Status: UNKNOWN Autor: J. Postel |
| RFC0891 DCN Local-Network Protocols This RFC provides a description of the DCN protocols for maintaining connectivity, routing, and clock information in a local network. These procedures may be of interest to the designers and implementers of other local networks. | December 1983 Status: STANDARD Autor: D.L. Mills |
| RFC0892 ISO Transport Protocol specification This is a draft version of the transport protocol being standardized by the ISO. This version also appeared in the ACM SIGCOMM Computer Communication Review (V.12, N.3-4) July-October 1982. This version is now out of date. | December 1983 Status: UNKNOWN Autor: International Organization for Standardization |
| RFC0893 Trailer encapsulations This RFC discusses the motivation for use of "trailer encapsulations" on local-area networks and describes the implementation of such an encapsulation on various media. This document is for information only. This is NOT an official protocol for the ARPA Internet community. | April 1984 Status: UNKNOWN Autor: S. Leffler, M.J. Karels |
| RFC0894 A Standard for the Transmission of IP Datagrams over Ethernet Networks This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Ethernet. This RFC specifies a standard protocol for the ARPA-Internet community. | April 1984 Status: STANDARD Autor: C. Hornig |
| RFC0895 Standard for the transmission of IP datagrams over experimental Ethernet networks This RFC specifies a standard method of encapsulating Internet Protocol (IP) datagrams on an Experimental Ethernet. This RFC specifies a standard protocol for the ARPA Internet community. | April 1984 Status: STANDARD Autor: J. Postel |
| RFC0896 Congestion Control in IP/TCP Internetworks This memo discusses some aspects of congestion control in IP/TCP Internetworks. It is intended to stimulate thought and further discussion of this topic. While some specific suggestions are made for improved congestion control implementation, this memo does not specify any standards. | January 1984 Status: UNKNOWN Autor: J. Nagle |
| RFC0897 Domain name system implementation schedule This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is a partial update of RFC 881. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The names of hosts will be changed to domain style names. Hosts will begin to use domain style names on 14-Mar-84, and the use of old style names will be completely phased out before 2-May-84. This applies to both the ARPA research hosts and the DDN operational hosts. This is an official policy statement of the ICCB and the DARPA. | February 1984 Status: UNKNOWN Autor: J. Postel |
| RFC0898 Gateway special interest group meeting notes This memo is a report on the Gateway Special Interest Group Meeting that was held at ISI on 28 and 29 February 1984. Robert Hinden of BBNCC chaired, and Jon Postel of ISI hosted the meeting. Approximately 35 gateway designers and implementors attended. These notes are based on the recollections of Jon Postel and Mike Muuss. Under each topic area are Jon Postel's brief notes, and additional details from Mike Muuss. This memo is a report on a meeting. No conclusions, decisions, or policy statements are documented in this note. | April 1984 Status: UNKNOWN Autor: R.M. Hinden, J. Postel, M. Muuss, J.K. Reynolds |
| RFC0899 Request For Comments summary notes: 800-899 | May 1984 Status: INFORMATIONAL Autor: J. Postel, A. Westine |
| RFC0900 Assigned Numbers This RFC specifies parameter values use in the Internet family of protocols, such as network numbers, well known ports, protocol types, and version numbers. This memo is an official status report on the protocol parameters used in the Internet protocol system. See RFC-990 and 997. | June 1984 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC0901 Official ARPA-Internet protocols This RFC identifies the documents specifying the official protocols used in the ARPA-Internet. Annotations identify any revisions or changes planned. This memo is an official status report on the protocols used in the DARPA research community. See RFC-991. | June 1984 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC0902 ARPA Internet Protocol policy The purpose of this memo is to explain how protocol standards are adopted for the ARPA-Internet and the DARPA research community. There are three important aspects to be discussed: the process, the authority, and the complex relationship between the DARPA community and the DDN community. This memo is a policy statement on how protocols become official standards for the ARPA-Internet and the DARPA research community. This is an official policy statement of the ICCB and the DARPA. | July 1984 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC0903 A Reverse Address Resolution Protocol This RFC suggests a method for workstations to dynamically find their protocol address (e.g., their Internet Address), when they know only their hardware address (e.g., their attached physical network address). This RFC specifies a proposed protocol for the ARPA Internet community, and requests discussion and suggestions for improvements. | June 1984 Status: STANDARD Autor: R. Finlayson, T. Mann, J.C. Mogul, M. Theimer |
| RFC0904 Exterior Gateway Protocol formal specification RFC-904 is the specification of the Exterior Gateway Protocol (EGP). This memo updates portions of RFC-888 and RFC-827. This RFC specifies an official protocol of the DARPA community for use between gateways of different autonomous systems in the ARPA-Internet. | April 1984 Status: HISTORIC Autor: D.L. Mills |
| RFC0905 ISO Transport Protocol specification ISO DP 8073 This is the current specification of the ISO Transport Protocol. This document is the text of ISO/TC97/SC16/N1576 as corrected by ISO/TC97/SC16/N1695. This is the specification currently being voted on in ISO as a Draft International Standard (DIS). This document is distributed as an RFC for your information only, it does not specify a standard for the ARPA-Internet or DARPA research community. Our thanks to Alex McKenzie of BBN for making this online version available. Please note the size of this document, the file contains 258,729 characters. | April 1984 Status: UNKNOWN Autor: ISO |
| RFC0906 Bootstrap loading using TFTP It is often convenient to be able to bootstrap a computer system from a communications network. This RFC proposes the use of the IP TFTP protocol for bootstrap loading in this case. | June 1984 Status: UNKNOWN Autor: R. Finlayson |
| RFC0907 Host Access Protocol specification This document specifies the Host Access Protocol (HAP). Although HAP was originally designed as the network-access level protocol for the DARPA/DCA sponsored Wideband Packet Satellite Network, it is intended that it evolve into a standard interface SATNET and TACNET (aka MATNET) as well as the Wideband Network. HAP is an experimental protocol, and will undergo further revision as new capabilities are added and/or different satellite networks are suported. Implementations of HAP should be performed in coordination with satellite network development and operations personnel. | July 1984 Status: STANDARD Autor: Bolt Beranek and Newman Laboratories |
| RFC0908 Reliable Data Protocol The Reliable Data Protocol (RDP) is designed to provide a reliable data transport service for packet-based applications. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts. | July 1984 Status: EXPERIMENTAL Autor: D. Velten, R.M. Hinden, J. Sax |
| RFC0909 Loader Debugger Protocol The Loader Debugger Protocol (LDP) is an application layer protocol for loading, dumping, and debugging target machines from hosts in a network environment. This RFC specifies a proposed protocol for the ARPA-Internet and DARPA research community, and requests discussion and suggestions for improvemts. | July 1984 Status: EXPERIMENTAL Autor: C. Welles, W. Milliken |
| RFC0910 Multimedia mail meeting notes This memo is a report on a meeting about the experimental multimedia mail system (and in a sense a status report on that experiment). The meeting was held at Bolt Beranek and Newman on 23-24 July 1984 to discuss recent progress by groups who are building multimedia mail systems and to discuss a variety of issues related to the further development of multimedia systems. Representatives were present from BBN, ISI, SRI and Linkabit. | August 1984 Status: UNKNOWN Autor: H.C. Forsdick |
| RFC0911 EGP Gateway under Berkeley UNIX 4.2 This memo describes an implementation of the Exterior Gateway Protocol (EGP) (in that sense it is a status report). The memo also discusses some possible extentions and some design issues (in that sense it is an invitation for further discussion). | August 1984 Status: UNKNOWN Autor: P. Kirton |
| RFC0912 Authentication service This memo describes a proposed authentication protocol for verifying the identity of a user of a TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. Suggested uses include automatic identification and verification of a user during an FTP session, additional verification of a TAC dial up user, and access verification for a generalized network file server. | September 1984 Status: UNKNOWN Autor: M. St. Johns |
| RFC0913 Simple File Transfer Protocol This memo describes a proposed Simple File Transfer Protocol (SFTP). It fills the need of people wanting a protocol that is more useful than TFTP but easier to implement (and less powerful) than FTP. SFTP supports user access control, file transfers, directory listing, directory changing, file renaming and deleting. Discussion of this proposal is encouraged, and suggestions for improvements may be sent to the author. | September 1984 Status: HISTORIC Autor: M. Lottor |
| RFC0914 Thinwire protocol for connecting personal computers to the Internet This RFC focuses discussion on the particular problems in the ARPA-Internet of low speed network interconnection with personal computers, and possible methods of solution. None of the proposed solutions in this document are intended as standards for the ARPA-Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to the problems, leading eventually to the adoption of standards. | September 1984 Status: HISTORIC Autor: D.J. Farber, G. Delp, T.M. Conte |
| RFC0915 Network mail path service This RFC proposed a new service for the ARPA-Internet community and requests discussion and suggestions for improvements. The network mail path service fills the current need of people to determine mailbox addresses for hosts that are not part of the ARPA-Internet but can be reached by one or more relay hosts that have Unix to Unix Copy (UUCP) mail, CSNET mail, MAILNET mail, BITNET mail, etc. Anyone can use the service if they have TCP/TELENET to one of the hosts with a mail path server. | December 1984 Status: UNKNOWN Autor: M.A. Elvy, R. Nedved |
| RFC0916 Reliable Asynchronous Transfer Protocol (RATP) This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This paper proposes and specifies a protocol which allows two programs to reliably communicate over a communication link. It ensures that the data entering one end of the link if received arrives at the other end intact and unaltered. The protocol, named RATP, is designed to operate over a full duplex point-to-point connection. It contains some features which tailor it to the RS-232 links now in common use. | October 1984 Status: HISTORIC Autor: G.G. Finn |
| RFC0917 Internet subnets This memo discusses subnets and proposes procedures for the use of subnets, including approaches to solving the problems that arise, particularly that of routing. A subnet of an Internet network is a logically visible sub-section of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | October 1984 Status: UNKNOWN Autor: J.C. Mogul |
| RFC0918 Post Office Protocol This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. The intent of the Post Office Protocol (POP) is to allow a user's workstation to access mail from a mailbox server. It is expected that mail will be posted from the workstation to the mailbox server via the Simple Mail Transfer Protocol (SMTP). This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. The status of this protocol is experimental, and this protocol is dependent upon TCP. | October 1984 Status: UNKNOWN Autor: J.K. Reynolds |
| RFC0919 Broadcasting Internet Datagrams This RFC proposes simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | October 1984 Status: STANDARD Autor: J.C. Mogul |
| RFC0920 Domain requirements This memo states the requirements on establishing a Domain, and introduces the limited set of top level domains. This memo is a policy statement on the requirements of establishing a new domain in the ARPA-Internet and the DARPA research community. This is an official policy statement of the IAB and the DARPA. | October 1984 Status: UNKNOWN Autor: J. Postel, J.K. Reynolds |
| RFC0921 Domain name system implementation schedule - revised This memo is a policy statement on the implementation of the Domain Style Naming System in the Internet. This memo is an update of RFC-881, and RFC-897. This is an official policy statement of the IAB and the DARPA. The intent of this memo is to detail the schedule for the implementation for the Domain Style Naming System. The explanation of how this system works is to be found in the references. | October 1984 Status: UNKNOWN Autor: J. Postel |
| RFC0922 Broadcasting Internet datagrams in the presence of subnets We propose simple rules for broadcasting Internet datagrams on local networks that support broadcast, for addressing broadcasts, and for how gateways should handle them. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | October 1984 Status: STANDARD Autor: J.C. Mogul |
| RFC0923 Assigned numbers This RFC documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers obsoletes RFC-900 and earlier editions. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990, and 997. | October 1984 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC0924 Official ARPA-Internet protocols for connecting personal computers to the Internet This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-900 and earlier editions. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991. | October 1984 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC0925 Multi-LAN address resolution The problem of treating a set of local area networks (LANs) as one Internet network has generated some interest and concern. It is inappropriate to give each LAN within an site a distinct Internet network number. It is desirable to hide the details of the interconnections between the LANs within an site from people, gateways, and hosts outside the site. The question arises on how to best do this, and even how to do it at all. In RFC-917 Jeffery Mogul makes a case for the use of "explicit subnets" in a multi-LAN environment. The explicit subnet scheme is a call to recursively apply the mechanisms the Internet uses to manage networks to the problem of managing LANs within one network. In this note I urge another approach: the use of "transparent subnets" supported by a multi-LAN extension of the Address Resolution Protocol. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | October 1984 Status: UNKNOWN Autor: J. Postel |
| RFC0926 Protocol for providing the connectionless mode network services This note is the draft ISO protocol roughly similar to the DOD Internet Protocol. This document has been prepared by retyping the text of ISO DIS 8473 of May 1984, which is currently undergoing voting within ISO as a Draft International Standard (DIS). This document is distributred as an RFC for information only. It does not specify a standard for the ARPA-Internet. | December 1984 Status: UNKNOWN Autor: International Organization for Standardization |
| RFC0927 TACACS user identification Telnet option The following is the description of a TELNET option designed to facilitate double login avoidance. It is intended primarily for TAC connections to target hosts on behalf of TAC users, but it can be used between any two consenting hosts. For example, all hosts at one site (e.g., BBN) can use this option to avoid double login when TELNETing to one another. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | December 1984 Status: PROPOSED STANDARD Autor: B.A. Anderson |
| RFC0928 Introduction to proposed DoD standard H-FP The broad outline of the Host-Front End Protocol introduced here and described in RFC-929 is the result of the deliberations of a number of experienced H-FP designers, who sat as a committee of the DoD Protocol Standards Technical Panel. It is the intent of the designers that the protocol be subjected to multiple test implementations and probable iteration before being agreed upon as any sort of "standard". Therefore, the first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | December 1984 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0929 Proposed Host-Front End Protocol The Host-Front End Protocol introduced in RFC-928 is described in detail in this memo. The first order of business is to declare that THIS IS A PROPOSAL, NOT A FINAL STANDARD, and the second order of business is to request that any readers of these documents who are able to do test implementations (a) do so and (b) coordinate their efforts with the author. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | December 1984 Status: HISTORIC Autor: J. Lilienkamp, R. Mandell, M.A. Padlipsky |
| RFC0930 Telnet terminal type option This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC-884. The only change is to specify that the TERMINAL-TYPE IS sub-negotiation should be sent only in response to the TERMINAL-TYPE SEND sub-negotiation. | January 1985 Status: UNKNOWN Autor: M. Solomon, E. Wimmers |
| RFC0931 Authentication server This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is the second draft of this proposal (superseding RFC-912) and incorporates a more formal description of the syntax for the request and response dialog, as well as a change to specify the type of user identification returned. | January 1985 Status: UNKNOWN Autor: M. St. Johns |
| RFC0932 Subnetwork addressing scheme This RFC proposes an alternative addressing scheme for subnets which, in most cases, requires no modification to host software whatsoever. The drawbacks of this scheme are that the total number of subnets in any one network are limited, and that modification is required to all gateways. | January 1985 Status: UNKNOWN Autor: D.D. Clark |
| RFC0933 Output marking Telnet option This proposed option would allow a Server-Telnet to send a banner to a User-Telnet so that this banner would be displayed on the workstation screen independently of the application software running in the Server-Telnet. | January 1985 Status: PROPOSED STANDARD Autor: S. Silverman |
| RFC0934 Proposed standard for message encapsulation This memo concerns itself with message forwarding. Forwarding can be thought of as encapsulating one or more messages inside another. Although this is useful for transfer of past correspondence to new recipients, without a decapsulation process (which this memo terms "bursting"), the forwarded messages are of little use to the recipients because they can not be distributed, forwarded, replied-to, or otherwise processed as separate individual messages. In order to burst a message it is necessary to know how the component messages were encapsulated in the draft. At present there is no unambiguous standard for interest group digests. This RFC proposes a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | January 1985 Status: UNKNOWN Autor: M.T. Rose, E.A. Stefferud |
| RFC0935 Reliable link layer protocols This RFC discusses protocols proposed recently in RFCs 914 and 916, and suggests a proposed protocol that could meet the same needs addressed in those memos. The stated need is reliable communication between two programs over a full-duplex, point-to-point communication link, and in particular the RFCs address the need for such communication over an asynchronous link at relatively low speeds. The suggested protocol uses the methods of existing national and international data link layer standards. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | January 1985 Status: UNKNOWN Autor: J.G. Robinson |
| RFC0936 Another Internet subnet addressing scheme There have been several proposals for schemes to allow the use of a single Internet network number to refer to a collection of physical networks under common administration which are reachable from the rest of the Internet by a common route. Such schemes allow a simplified view of an otherwise complicated topology from hosts and gateways outside of this collection. They allow the complexity of the number and type of these networks, and routing to them, to be localized. Additions and changes in configuration thus cause no detectable change, and no interruption of service, due to slow propagation of routing and other information outside of the local environment. These schemes also simplify the administration of the network, as changes do not require allocation of new network numbers for each new cable installed. This proposal discusses an alternative scheme, one that has been in use at the University of California, Berkeley since April 1984. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | February 1985 Status: UNKNOWN Autor: M.J. Karels |
| RFC0937 Post Office Protocol: Version 2 This RFC suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvement. This memo is a revision of RFC-918. | February 1985 Status: HISTORIC Autor: M. Butler, J. Postel, D. Chase, J. Goldberger, J.K. Reynolds |
| RFC0938 Internet Reliable Transaction Protocol functional and interface specification This RFC is being distributed to members of the DARPA research community in order to solicit their reactions to the proposals contained in it. While the issues discussed may not be directly relevant to the research problems of the DARPA community, they may be interesting to a number of researchers and implementors. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | February 1985 Status: EXPERIMENTAL Autor: T. Miller |
| RFC0939 Executive summary of the NRC report on transport protocols for Department of Defense data networks This RFC reproduces the material from the "front pages" of the National Research Council report resulting from a study of the DOD Internet Protocol (IP) and Transmission Control Protocol (TCP) in comparison with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). The point of this RFC is to make the text of the Executive Summary widely available in a timely way. The order of presentation has been altered, and the pagination changed. This RFC is distributed for information only. This RFC does not establish any policy for the DARPA research community or the DDN operational community. | February 1985 Status: UNKNOWN Autor: National Research Council |
| RFC0940 Toward an Internet standard scheme for subnetting Several sites now contain a complex of local links connected to the Internet via a gateway. The details of the internal connectivity are of little interest to the rest of the Internet. One way of organizing these local complexes of links is to use the same strategy as the Internet uses to organize networks, that is, to declare each link to be an entity (like a network) and to interconnect the links with devices that perform routing functions (like gateways). This general scheme is called subnetting, the individual links are called subnets, and the connecting devices are called subgateways (or bridges, or gateways). This RFC discusses standardizing the protocol used in subnetted environments in the ARPA-Internet. | April 1985 Status: UNKNOWN Autor: Gateway Algorithms and Data Structures Task Force |
| RFC0941 Addendum to the network service definition covering network layer addressing This Addendum to the Network Service Definition Standard, ISO 8348, defines the abstract syntax and semantics of the Network Address (Network Service Access Point Address). The Network Address defined in this Addendum is the address that appears in the primitives of the connection-mode Network Service as the calling address, called address, and responding address parameters, and in the primitives of the connectionless-mode Network Service as the source address and destination address parameters. This document is distributed as an RFC for information only. It does not specify a standard for the ARPA-Internet. | April 1985 Status: UNKNOWN Autor: International Organization for Standardization |
| RFC0942 Transport protocols for Department of Defense data networks This RFC reproduces the National Research Council report resulting from a study of the DoD Internet Protocol (IP) and Transmission Control Protocol (TCP) in comparison with the ISO Internet Protocol (ISO-IP) and Transport Protocol level 4 (TP-4). | February 1985 Status: UNKNOWN Autor: National Research Council |
| RFC0943 Assigned numbers This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This RFC will be updated periodically, and in any case current information can be obtained from Joyce Reynolds. The assignment of numbers is also handled by Joyce. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, network number, etc., please contact Joyce to receive a number assignment. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997. | April 1985 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC0944 Official ARPA-Internet protocols This RFC identifies the documents specifying the official protocols used in the Internet. This edition of Official ARPA-Internet Protocols obsoletes RFC-924 and earlier editions. This RFC will be updated periodically, and current information can be obtained from Joyce Reynolds. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991. | April 1985 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC0945 DoD statement on the NRC report In May 1983 the National Research Council (NRC) was asked jointly by DoD and NBS to study the issues and recommend a course of action. The final report of the NRC committee was published in February 1985 (see RFC-942). The enclosed letter is from Donald C. Latham (ASDC3I) to DCA transmitting the NRC report and requesting specific actions relative to the recommendations of the report. This RFC reproduces a letter from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC3I) to the Director of the Defense Communications Agency (DCA). This letter is distributed for information only. | May 1985 Status: UNKNOWN Autor: J. Postel |
| RFC0946 Telnet terminal location number option Many systems provide a mechanism for finding out where a user is logged in from usually including information about telephone extension and office occupants names. The information is useful for physically locating people and/or calling them on the phone. In 1982 CMU designed and implemented a terminal location database and modified existing network software to handle a 64-bit number called the Terminal Location Number (or TTYLOC). It now seems appropriate to incorporate this mechanism into the TCP-based network protocol family. The mechanism is not viewed as a replacement for the Terminal Location Telnet Option (SEND-LOCATION) but as a shorthand mechansim for communicating terminal location information between hosts in a localized community. This RFC proposes a new option for Telnet for the ARPA-Internet community, and requests discussion and suggestions for improvements. | May 1985 Status: PROPOSED STANDARD Autor: R. Nedved |
| RFC0947 Multi-network broadcasting within the Internet This RFC describes the extension of a network's broadcast domain to include more than one physical network through the use of a broadcast packet repeater. | June 1985 Status: UNKNOWN Autor: K. Lebowitz, D. Mankins |
| RFC0948 Two methods for the transmission of IP datagrams over IEEE 802.3 networks This RFC describes two methods of encapsulating Internet Protocol (IP) datagrams on an IEEE 802.3 network. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | June 1985 Status: UNKNOWN Autor: I. Winston |
| RFC0949 FTP unique-named store command There are various contexts in which it would be desirable to have an FTP command that had the effect of the present STOR but rather than requiring the sender to specify a file name istead caused the resultant file to have a unique name relative to the current directory. This RFC proposes an extension to the File Transfer Protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. See RFC-959. | July 1985 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0950 Internet Standard Subnetting Procedure This memo discusses the utility of "subnets" of Internet networks, which are logically visible sub-sections of a single Internet network. For administrative or technical reasons, many organizations have chosen to divide one Internet network into several subnets, instead of acquiring a set of Internet network numbers. This memo specifies procedures for the use of subnets. These procedures are for hosts (e.g., workstations). The procedures used in and between subnet gateways are not fully described. Important motivation and background information for a subnetting standard is provided in RFC-940. This RFC specifies a protocol for the ARPA-Internet community. If subnetting is implemented it is strongly recommended that these procedures be followed. | August 1985 Status: STANDARD Autor: J.C. Mogul, J. Postel |
| RFC0951 Bootstrap Protocol This RFC describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed. The bootstrap operation can be thought of as consisting of TWO PHASES. This RFC describes the first phase, which could be labeled `address determination and bootfile selection'. After this address and filename information is obtained, control passes to the second phase of the bootstrap where a file transfer occurs. The file transfer will typically use the TFTP protocol, since it is intended that both phases reside in PROM on the client. However BOOTP could also work with other protocols such as SFTP or FTP. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | September 1985 Status: DRAFT STANDARD Autor: W.J. Croft, J. Gilmore |
| RFC0952 DoD Internet host table specification This RFC is the official specification of the format of the Internet Host Table. This edition of the specification includes minor revisions to RFC-810 which brings it up to date. | October 1985 Status: UNKNOWN Autor: K. Harrenstien, M.K. Stahl, E.J. Feinler |
| RFC0953 Hostname Server This RFC is the official specification of the Hostname Server Protocol. This edition of the specification includes minor revisions to RFC-811 which brings it up to date. | October 1985 Status: HISTORIC Autor: K. Harrenstien, M.K. Stahl, E.J. Feinler |
| RFC0954 NICNAME/WHOIS This RFC is the official specification of the NICNAME/WHOIS protocol. This memo describes the protocol and the service. This is an update of RFC-812. | October 1985 Status: DRAFT STANDARD Autor: K. Harrenstien, M.K. Stahl, E.J. Feinler |
| RFC0955 Towards a transport service for transaction processing applications The DoD Internet protocol suite includes two alternative transport service protocols, TCP and UDP, which provide virtual circuit and datagram service, respectively. These two protocols represent points in the space of possible transport service attributes which are quite "far apart". We want to examine an important class of applications, those which perform what is often called "transaction processing". We will see that the communication needs for these applications fall into the gap "between" TCP and UDP -- neither protocol is very appropriate. This RFC is concerned with the possible design of one or more new protocols for the ARPA-Internet, to support kinds of applications which are not well supported at present. The RFC is intended to spur discussion in the Internet research community towards the development of new protocols and/or concepts, in order to meet these unmet application requirements. It does not represent a standard, nor even a concrete protocol proposal. | September 1985 Status: UNKNOWN Autor: R.T. Braden |
| RFC0956 Algorithms for synchronizing network clocks This RFC discussed clock synchronization algorithms for the ARPA-Internet community, and requests discussion and suggestions for improvements. The recent interest within the Internet community in determining accurate time from a set of mutually suspicious network clocks has been prompted by several occasions in which errors were found in usually reliable, accurate clock servers after thunderstorms which disrupted their power supply. To these sources of error should be added those due to malfunctioning hardware, defective software and operator mistakes, as well as random errors in the mechanism used to set and synchronize clocks. This report suggests a stochastic model and algorithms for computing a good estimator from time-offset samples measured between clocks connected via network links. Included in this report are descriptions of certain experiments which give an indication of the effectiveness of the algorithms. | September 1985 Status: UNKNOWN Autor: D.L. Mills |
| RFC0957 Experiments in network clock synchronization This RFC discusses some experiments in clock synchronization in the ARPA-Internet community, and requests discussion and suggestions for improvements. One of the services frequently neglected in computer network design is a high-quality, time-of-day clock capable of generating accurate timestamps with small errors compared to one-way network delays. Such a service would be useful for tracing the progress of complex transactions, synchronizing cached data bases, monitoring network performance and isolating problems. In this memo one such clock service design will be described and its performance assessed. This design has been incorporated as an integral part of the network routing and control protocols of the Distributed Computer Network (DCnet) architecture. | September 1985 Status: UNKNOWN Autor: D.L. Mills |
| RFC0958 Network Time Protocol (NTP) This document describes the Network Time Protocol (NTP), a protocol for synchronizing a set of network clocks using a set of distributed clients and servers. NTP is built on the User Datagram Protocol (UDP), which provides a connectionless transport mechanism. It is evolved from the Time Protocol and the ICMP Timestamp message and is a suitable replacement for both. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | September 1985 Status: UNKNOWN Autor: D.L. Mills |
| RFC0959 File Transfer Protocol This memo is the official specification of the File Transfer Protocol (FTP) for the DARPA Internet community. The primary intent is to clarify and correct the documentation of the FTP specification, not to change the protocol. The following new optional commands are included in this edition of the specification: Change to Parent Directory (CDUP), Structure Mount (SMNT), Store Unique (STOU), Remove Directory (RMD), Make Directory (MKD), Print Directory (PWD), and System (SYST). Note that this specification is compatible with the previous edition. | October 1985 Status: STANDARD Autor: J. Postel, J. Reynolds |
| RFC0960 Assigned numbers This memo documents the currently assigned values from several series of numbers used in network protocol implementations. This edition of Assigned Numbers updates and obsoletes RFC-943. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-990 and 997. | December 1985 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC0961 Official ARPA-Internet protocols This memo identifies the documents specifying the official protocols used in the Internet, and comments on any revisions or changes planned. This edition of the Official Protocols updates and obsoletes RFC-944. This memo is an official status report on the protocols used in the ARPA-Internet community. See RFC-991. | December 1985 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC0962 TCP-4 prime This memo is in response to Bob Braden's call for a transaction oriented protocol (RFC-955), and continues the discussion of a possible transaction oriented transport protocol. This memo does not propose a standard. | November 1985 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0963 Some problems with the specification of the Military Standard Internet Protocol The purpose of this RFC is to provide helpful information on the Military Standard Internet Protocol (MIL-STD-1777) so that one can obtain a reliable implementation of this protocol. This paper points out several problems in this specification. This note also proposes solutions to these problems. | November 1985 Status: UNKNOWN Autor: D.P. Sidhu |
| RFC0964 Some problems with the specification of the Military Standard Transmission Control Protocol The purpose of this RFC is to provide helpful information on the Military Standard Transmission Control Protocol (MIL-STD-1778) so that one can obtain a reliable implementation of this protocol standard. This note points out three errors with this specification. This note also proposes solutions to these problems. | November 1985 Status: UNKNOWN Autor: D.P. Sidhu, T. Blumer |
| RFC0965 Format for a graphical communication protocol This RFC describes the requirements for a graphical format on which to base a graphical on-line communication protocol, and proposes an Interactive Graphical Communication Format using the GKSM session metafile. We hope this contribution will encourage the discussion of multimedia data exchange and the proposal of solutions. | December 1985 Status: UNKNOWN Autor: L. Aguilar |
| RFC0966 Host groups: A multicast extension to the Internet Protocol This RFC defines a model of service for Internet multicasting and proposes an extension to the Internet Protocol (IP) to support such a multicast service. Discussion and suggestions for improvements are requested. See RFC-988. | December 1985 Status: UNKNOWN Autor: S.E. Deering, D.R. Cheriton |
| RFC0967 All victims together This RFC proposes a new set of RFCs on how the networking code is integrated with various operating systems. It appears that this topic has not received enough exposure in the literature. Comments and suggestions are encouraged. | December 1985 Status: UNKNOWN Autor: M.A. Padlipsky |
| RFC0968 Twas the night before start-up This memo discusses problems that arise and debugging techniques used in bringing a new network into operation. | December 1985 Status: UNKNOWN Autor: V.G. Cerf |
| RFC0969 NETBLT: A bulk data transfer protocol This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. This is a preliminary discussion of the Network Block Transfer (NETBLT) protocol. NETBLT is intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is structured to provide maximum throughput over a wide variety of networks. This description is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-998. | December 1985 Status: UNKNOWN Autor: D.D. Clark, M.L. Lambert, L. Zhang |
| RFC0970 On Packet Switches With Infinite Storage The purpose of this RFC is to focus discussion on a particular problem in the ARPA-Internet and possible methods of solution. Most prior work on congestion in datagram systems focuses on buffer management. In this memo the case of a packet switch with infinite storage is considered. Such a packet switch can never run out of buffers. It can, however, still become congested. The meaning of congestion in an infinite-storage system is explored. An unexpected result is found that shows a datagram network with infinite storage, first-in-first-out queuing, at least two packet switches, and a finite packet lifetime will, under overload, drop all packets. By attacking the problem of congestion for the infinite-storage case, new solutions applicable to switches with finite storage may be found. No proposed solutions this document are intended as standards for the ARPA-Internet at this time. | December 1985 Status: UNKNOWN Autor: J. Nagle |
| RFC0971 Survey of data representation standards This RFC is a comparison of several data representation standards that are currently in use. The standards discussed are the CCITT X.409 recommendation, the NBS Computer Based Message System (CBMS) standard, DARPA Multimedia Mail system, the Courier remote procedure call protocol, and the SUN Remote Procedure Call package. No proposals in this document are intended as standards for the ARPA-Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate approach to a data representation standard, leading eventually to the adoption of an ARPA-Internet standard. | January 1986 Status: UNKNOWN Autor: A.L. DeSchon |
| RFC0972 Password Generator Protocol This RFC specifies a standard for the ARPA Internet community. The Password Generator Service (PWDGEN) provides a set of six randomly generated eight-character "words" with a reasonable level of pronounceability, using a multi-level algorithm. Hosts on the ARPA Internet that choose to implement a password generator service are expected to adopt and implement this standard. | January 1986 Status: UNKNOWN Autor: F.J. Wancho |
| RFC0973 Domain system changes and observations This RFC documents updates to Domain Name System specifications RFC-882 and RFC-883, suggests some operational guidelines, and discusses some experiences and problem areas in the present system. | January 1986 Status: UNKNOWN Autor: P.V. Mockapetris |
| RFC0974 Mail routing and the domain system This RFC presents a description of how mail systems on the Internet are expected to route messages based on information from the domain system. This involves a discussion of how mailers interpret MX RRs, which are used for message routing. | January 1986 Status: HISTORIC Autor: C. Partridge |
| RFC0975 Autonomous confederations This RFC proposes enhancements to the Exterior Gateway Protocol (EGP) to support a simple, multiple-level routing capability while preserving the robustness features of the current EGP model. The enhancements generalize the concept of core system to include multiple communities of autonomous systems, called autonomous confederations. Discussion and suggestions for improvement are requested. | February 1986 Status: UNKNOWN Autor: D.L. Mills |
| RFC0976 UUCP mail interchange format standard This document defines the standard format for the transmission of mail messages between computers in the UUCP Project. It does not however, address the format for storage of messages on one machine, nor the lower level transport mechanisms used to get the date from one machine to the next. It represents a standard for conformance by hosts in the UUCP zone. | February 1986 Status: UNKNOWN Autor: M.R. Horton |
| RFC0977 Network News Transfer Protocol NNTP specifies a protocol for the distribution, inquiry, retrieval, and posting of news articles using a reliable stream-based transmission of news among the ARPA-Internet community. NNTP is designed so that news articles are stored in a central database allowing a subscriber to select only those items he wishes to read. Indexing, cross-referencing, and expiration of aged messages are also provided. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | February 1986 Status: PROPOSED STANDARD Autor: B. Kantor, P. Lapsley |
| RFC0978 Voice File Interchange Protocol (VFIP) The purpose of the Voice File Interchange Protocol (VFIP) is to permit the interchange of various types of speech files between different systems in the ARPA-Internet community. Suggestions for improvement are encouraged. | February 1986 Status: UNKNOWN Autor: J.K. Reynolds, R. Gillman, W.A. Brackenridge, A. Witkowski, J. Postel |
| RFC0979 PSN End-to-End functional specification This memo is an updated version of BBN Report 5775, "End-to-End Functional Specification and describes important changes to the functionality of the interface between a Host and the PSN, and should be carefully reviewed by anyone involved in supporting a host on either the ARPANET or MILNET". The new End-to-End protocol (EE) is being developed in order to correct a number of deficiencies in the old EE, to improve its performance and overall throughput, and to better equip the Packet Switch Node (PSN, also known as the IMP) to support its current and anticipated host population. | March 1986 Status: UNKNOWN Autor: A.G. Malis |
| RFC0980 Protocol document order information This RFC indicates how to obtain various protocol documents used in the DARPA research community. Included is an overview of the new 1985 DDN Protocol Handbook and available sources for obtaining related documents (such as DOD, ISO, and CCITT). | March 1986 Status: UNKNOWN Autor: O.J. Jacobsen, J. Postel |
| RFC0981 Experimental multiple-path routing algorithm This document introduces wiretap algorithms, a class of experimental, multiple routing algorithms that compute quasi-optimum routes for stations sharing a packet-radio broadcast channel. The primary route (a minimum-distance path), and additional paths ordered by distance, which serve as alternate routes should the primary route fail, are computed. This prototype is presented as an example of a class of routing algorithms and data-base management techniques that may find wider application in the Internet community. Discussions and suggestions for improvements are welcomed. | March 1986 Status: UNKNOWN Autor: D.L. Mills |
| RFC0982 Guidelines for the specification of the structure of the Domain Specific Part (DSP) of the ISO standard NSAP address This RFC is a draft working document of the ANSI "Guidelines for the Specification of the Structure of the Domain Specific Part (DSP) of the ISO Standard NSAP Address". It provides guidance to private address administration authorities on preferred formats and semantics for the Domain Specific Part (DSP) of an NSAP address. This RFC specifies the way in which the DSP may be constructed so as to facilitate efficient address assignment. This RFC is for informational purposes only and its distribution is unlimited and does not specify a standard of the ARPA-Internet. | April 1986 Status: UNKNOWN Autor: H.W. Braun |
| RFC0983 ISO transport arrives on top of the TCP This memo describes a proposed protocol standard for the ARPA Internet community. The CCITT and the ISO have defined various session, presentation, and application recommendations which have been adopted by the international community and numerous vendors. To the largest extent possible, it is desirable to offer these higher level services directly in the ARPA Internet, without disrupting existing facilities. This permits users to develop expertise with ISO and CCITT applications which previously were not available in the ARPA Internet. The intention is that hosts in the ARPA-Internet that choose to implement ISO TSAP services on top of the TCP be expected to adopt and implement this standard. Suggestions for improvement are encouraged. | April 1986 Status: UNKNOWN Autor: D.E. Cass, M.T. Rose |
| RFC0984 PCMAIL: A distributed mail system for personal computers This document is a preliminary discussion of the design of a personal-computer-based distributed mail system. Pcmail is a distributed mail system that provides mail service to an arbitrary number of users, each of which owns one or more personal computers (PCs). The system is divided into two halves. The first consists of a single entity called the "repository". The repository is a storage center for incoming mail. Mail for a Pcmail user can arrive externally from the Internet or internally from other repository users. The repository also maintains a stable copy of each user's mail state. The repository is therefore typically a computer with a large amount of disk storage. It is published for discussion and comment, and does not constitute a standard. As the proposal may change, implementation of this document is not advised. See RFC-993. | May 1986 Status: UNKNOWN Autor: D.D. Clark, M.L. Lambert |
| RFC0985 Requirements for Internet gateways - draft This RFC summarizes the requirements for gateways to be used on networks supporting the DARPA Internet protocols. While it applies specifically to National Science Foundation research programs, the requirements are stated in a general context and are believed applicable throughout the Internet community. The purpose of this document is to present guidance for vendors offering products that might be used or adapted for use in an Internet application. It enumerates the protocols required and gives references to RFCs and other documents describing the current specification. | May 1986 Status: UNKNOWN Autor: National Science Foundation, Network Technical Advisory Group |
| RFC0986 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol This RFC suggests a method to allow the existing IP addressing, including the IP protocol field, to be used for the ISO Connectionless Network Protocol (CLNP). This is a draft solution to one of the problems inherent in the use of "ISO-grams" in the DOD Internet. Related issues will be discussed in subsequent RFCs. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | June 1986 Status: UNKNOWN Autor: R.W. Callon, H.W. Braun |
| RFC0987 Mapping between X.400 and RFC 822 The X.400 series protocols have been defined by CCITT to provide an Interpersonal Messaging Service (IPMS), making use of a store and forward Message Transfer Service. It is expected that this standard will be implemented very widely. This document describes a set of mappings which will enable interworking between systems operating the X.400 protocols and systems using RFC-822 mail protocol or protocols derived from RFC-822. This RFC suggests a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements. | June 1986 Status: UNKNOWN Autor: S.E. Kille |
| RFC0988 Host extensions for IP multicasting This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support internetwork multicasting. This specification supersedes that given in RFC-966, and constitutes a proposed protocol standard for IP multicasting in the ARPA-Internet. The reader is directed to RFC-966 for a discussion of the motivation and rationale behind the multicasting extension specified here. | July 1986 Status: UNKNOWN Autor: S.E. Deering |
| RFC0989 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures This RFC suggests a proposed protocol for the Internet community and requests discussion and suggestions for improvements. This RFC is the outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This RFC defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. It is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or authentication is anticipated. | February 1987 Status: UNKNOWN Autor: J. Linn |
| RFC0990 Assigned numbers This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. See RFC-997. Obsoletes RFC-960, 943, 923 and 900. | November 1986 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC0991 Official ARPA-Internet protocols This RFC identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. This memo is an official status report on the numbers used in protocols in the ARPA-Internet community. Obsoletes RFC-961, 944 and 924. | November 1986 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC0992 On communication support for fault tolerant process groups This memo describes a collection of multicast communication primitives integrated with a mechanism for handling process failure and recovery. These primitives facilitate the implementation of fault-tolerant process groups, which can be used to provide distributed services in an environment subject to non-malicious crash failures. | November 1986 Status: UNKNOWN Autor: K.P. Birman, T.A. Joseph |
| RFC0993 PCMAIL: A distributed mail system for personal computers This document is a discussion of the Pcmail workstation-based distributed mail system. It is a revision of the design published in NIC RFC-984. The revision is based on discussion and comment fromm a variety of sources, as well as further research into the design of interactive Pcmail clients and the use of client code on machines other than IBM PCs. As this design may change, implementation of this document is not advised. Obsoletes RFC-984. | December 1986 Status: UNKNOWN Autor: D.D. Clark, M.L. Lambert |
| RFC0994 Final text of DIS 8473, Protocol for Providing the Connectionless-mode Network Service This Protocol Standard is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of standards covers the services and protocols required to achieve such interconnection. This Protocol Standard is positioned with respect to other related standards by the layers defined in the Reference Model for Open Systems Interconnection (ISO 7498). In particular, it is a protocol of the Network Layer. This Protocol may be used between network-entities in end systems or in Network Layer relay systems (or both). It provides the Connectionless-mode Network Service as defined in Addendum 1 to the Network Service Definition Covering Connectionless-mode Transmission (ISO 8348/AD1). | March 1986 Status: UNKNOWN Autor: International Organization for Standardization |
| RFC0995 End System to Intermediate System Routing Exchange Protocol for use in conjunction with ISO 8473 This Protocol is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of standards covers the services and protocols required to achieve such interconnection. This Protocol is positioned with respect to other related standards by the layers defined in the Reference Model for Open Systems Interconnection (ISO 7498) and by the structure defined in the Internal Organization of the Network Layer (DIS 8648). In particular, it is a protocol of the Network Layer. This Protocol permits End Systems and Intermediate Systems to exchange configuration and routing information to facilitate the operation of the routing and relaying functions of the Network Layer. | April 1986 Status: UNKNOWN Autor: International Organization for Standardization |
| RFC0996 Statistics server This RFC specifies a standard for the ARPA Internet community. Hosts and gateways on the DARPA Internet that choose to implement a remote statistics monitoring facility may use this protocol to send statistics data upon request to a monitoring center or debugging host. | February 1987 Status: HISTORIC Autor: D.L. Mills |
| RFC0997 Internet numbers This memo is an official status report on the network numbers used in the Internet community. As of 1-Mar-87 the Network Information Center (NIC) at SRI International has assumed responsibility for assignment of Network Numbers and Autonomous System Numbers. This RFC documents the current assignments of these numbers at the time of this transfer of responsibility. Obsoletes RFC-990, 960, 943, 923 and 900. | March 1987 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC0998 NETBLT: A bulk data transfer protocol This document is a description of, and a specification for, the NETBLT protocol. It is a revision of the specification published in RFC-969. NETBLT (NETwork BLock Transfer) is a transport level protocol intended for the rapid transfer of a large quantity of data between computers. It provides a transfer that is reliable and flow controlled, and is designed to provide maximum throughput over a wide variety of networks. Although NETBLT currently runs on top of the Internet Protocol (IP), it should be able to operate on top of any datagram protocol similar in function to IP. This document is published for discussion and comment, and does not constitute a standard. The proposal may change and certain parts of the protocol have not yet been specified; implementation of this document is therefore not advised. Obsoletes RFC-969. | March 1987 Status: EXPERIMENTAL Autor: D.D. Clark, M.L. Lambert, L. Zhang |
| RFC0999 Requests For Comments summary notes: 900-999 | April 1987 Status: UNKNOWN Autor: A. Westine, J. Postel |
| RFC1000 Request For Comments reference guide This RFC Reference Guide is intended to provide a historical account by categorizing and summarizing of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. These documents have been crossed referenced to indicate which RFCs are current, obsolete, or revised. | August 1987 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC1001 Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC describes the NetBIOS-over-TCP protocols in a general manner, emphasizing the underlying ideas and techniques. Detailed specifications are found in a companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications". | March 1987 Status: STANDARD Autor: NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force |
| RFC1002 Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC gives the detailed specifications of the netBIOS-over-TCP packets, protocols, and defined constants and variables. A more general overview is found in a companion RFC, "Protocol Standard For NetBIOS Service on TCP/UDP Transport: Concepts and Methods". | March 1987 Status: STANDARD Autor: NetBIOS Working Group in the Defense Advanced Research Projects Agency, Internet Activities Board, End-to-End Services Task Force |
| RFC1003 Issues in defining an equations representation standard This memo is intended to identify and explore issues in defining a standard for the exchange of mathematical equations. No attempt is made at a complete definition and more questions are asked than are answered. Questions about the user interface are only addressed to the extent that they affect interchange issues. | March 1987 Status: UNKNOWN Autor: A.R. Katz |
| RFC1004 Distributed-protocol authentication scheme The purpose of this RFC is to focus discussion on authentication problems in the Internet and possible methods of solution. The proposed solutions this document are not intended as standards for the Internet at this time. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to authentication problems, leading eventually to the adoption of standards. This document suggests mediated access-control and authentication procedures suitable for those cases when an association is to be set up between users belonging to different trust environments. | April 1987 Status: EXPERIMENTAL Autor: D.L. Mills |
| RFC1005 ARPANET AHIP-E Host Access Protocol (enhanced AHIP) This RFC is a proposed specification for the encoding of Class A IP addresses for use on ARPANET-style networks such as the Milnet and Arpanet, and for enhancements to the ARPANET AHIP Host Access Protocol (AHIP; formerly known as 1822). These enhancements increase the size of the PSN field, allow ARPANET hosts to use logical names to address each other, allow for the communication of type-of-service information from the host to the PSN and enable the PSN to provide congestion feedback to the host on a connection basis. | May 1987 Status: UNKNOWN Autor: A. Khanna, A.G. Malis |
| RFC1006 ISO Transport Service on top of the TCP Version: 3 This memo specifies a standard for the Internet community. Hosts on the Internet that choose to implement ISO transport services on top of the TCP are expected to adopt and implement this standard. TCP port 102 is reserved for hosts which implement this standard. This memo specifies version 3 of the protocol and supersedes RFC-983. Changes between the protocol is described in RFC-983 and this memo are minor, but unfortunately incompatible. | May 1987 Status: STANDARD Autor: M.T. Rose, D.E. Cass |
| RFC1007 Military supplement to the ISO Transport Protocol This document supplements the Transport Service and Protocol of the International Standards Organization (ISO), IS 8072 and IS 8073, respectively, and their formal descriptions by providing conventions, option selections and parameter values. This RFC is being distributed to members of the Internet community in order to solicit comments on the Draft Military Supplement. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. | June 1987 Status: UNKNOWN Autor: W. McCoy |
| RFC1008 Implementation guide for the ISO Transport Protocol This RFC is being distributed to members of the Internet community in order to solicit comments on the Implementors Guide. While this document may not be directly relevant to the research problems of the Internet, it may be of some interest to a number of researchers and implementors. | June 1987 Status: UNKNOWN Autor: W. McCoy |
| RFC1009 Requirements for Internet gateways This RFC summarizes the requirements for gateways to be used between networks supporting the Internet protocols. This document is a formal statement of the requirements to be met by gateways used in the Internet system. As such, it is an official specification for the Internet community. | June 1987 Status: HISTORIC Autor: R.T. Braden, J. Postel |
| RFC1010 Assigned numbers This memo is an official status report on the numbers used in protocols in the Internet community. It documents the currently assigned values from several series of numbers including link, socket, port, and protocol, used in network protocol implementations. | May 1987 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC1011 Official Internet protocols This memo is an official status report on the protocols used in the Internet community. It identifies the documents specifying the official protocols used in the Internet. Comments indicate any revisions or changes planned. | May 1987 Status: UNKNOWN Autor: J.K. Reynolds, J. Postel |
| RFC1012 Bibliography of Request For Comments 1 through 999 This RFC is a reference guide for the Internet community which provides a bibliographic summary of the Request for Comments numbers 1 through 999 issued between the years 1969-1987. | June 1987 Status: INFORMATIONAL Autor: J.K. Reynolds, J. Postel |
| RFC1013 X Window System Protocol, version 11: Alpha update April 1987 This RFC is distributed to the Internet community for information only. It does not establish an Internet standard. The X window system has been widely reviewed and tested. The Internet community is encouraged to experiment with it. | June 1987 Status: UNKNOWN Autor: R.W. Scheifler |
| RFC1014 XDR: External Data Representation standard XDR is a standard for the description and encoding of data. It is useful for transferring data between different computer architectures. XDR fits into ISO presentation layer, and is roughly analogous in purpose to X.409, ISO Abstract Syntax Notation. The major difference between these two is that XDR uses implicit typing, while X.409 uses explicit typing. This RFC is distributed for information only, it does not establish a Internet standard. | June 1987 Status: UNKNOWN Autor: Sun Microsystems |
| RFC1015 Implementation plan for interagency research Internet This RFC proposes an Interagency Research Internet as the natural outgrowth of the current Internet. This is an "idea paper" and discussion is strongly encouraged. | July 1987 Status: UNKNOWN Autor: B.M. Leiner |
| RFC1016 Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID) The memo is intended to explore the issue of what a host could do with a source quench. The proposal is for each source host IP module to introduce some delay between datagrams sent to the same destination host. This is a "crazy idea paper" and discussion is essential. | July 1987 Status: UNKNOWN Autor: W. Prue, J. Postel |
| RFC1017 Network requirements for scientific research: Internet task force on scientific computing This RFC identifies the requirements on communication networks for supporting scientific research. It proposes some specific areas for near term work, as well as some long term goals. This is an "idea" paper and discussion is strongly encouraged. | August 1987 Status: UNKNOWN Autor: B.M. Leiner |
| RFC1018 Some comments on SQuID This memo is a discussion of some of the ideas expressed in RFC-1016 on Source Quench. This memo introduces the distinction of the cause of congestion in a gateway between the effects of "Funneling" and Mismatch". It is offered in the same spirit as RFC-1016; to stimulate discussion. The opinions offered are personal, not corporate, opinions. | August 1987 Status: UNKNOWN Autor: A.M. McKenzie |
| RFC1019 Report of the Workshop on Environments for Computational Mathematics This memo is a report on the discussion of the representation of equations in a workshop at the ACM SIGGRAPH Conference held in Anaheim, California on 30 July 1987. | September 1987 Status: UNKNOWN Autor: D. Arnon |
| RFC1020 Internet numbers This RFC is a list of the Assigned IP Network Numbers and EGP Autonomous System Numbers. This RFC obsoletes RFC-997. | November 1987 Status: UNKNOWN Autor: S. Romano, M.K. Stahl |
| RFC1021 High-level Entity Management System (HEMS) This memo provides a general overview of the High-level Entity management system (HEMS). This system is experimental, and is currently being tested in portions of the Internet. | October 1987 Status: HISTORIC Autor: C. Partridge, G. Trewitt |
| RFC1022 High-level Entity Management Protocol (HEMP) This memo presents an application protocol for managing network entities such as hosts, gateways, and front end machines. This protocol is a component of the High-level Entity Management System HEMS), described is RFC-1021. This memo also assumes a knowledge of the ISO data encoding standard, ASN.1. | October 1987 Status: UNKNOWN Autor: C. Partridge, G. Trewitt |
| RFC1023 HEMS monitoring and control language This RFC specifies the High-Level Entity Management System (HEMS) Monitoring and Control Language. This language defines the requests and replies used in HEMS. This memo assumes knowledge of the HEMS system described in RFC-1021, and of the ISO data encoding standard, ASN.1. | October 1987 Status: UNKNOWN Autor: G. Trewitt, C. Partridge |
| RFC1024 HEMS variable definitions This memo assigns instruction codes, defines object formats and object semantics for use with the High-Level Monitoring and Control Language, defined in RFC-1023. A general system has been described in previous memos (RFC-1021, RFC-1022). This system is called the High-Level Entity Management System (HEMS). This memo is provisional and the definitions are subject to change. Readers should confirm with the authors that they have the most recent version. This RFC assumes a working knowledge of the ISO data encoding standard, ASN.1, and a general understanding of the IP protocol suite. | October 1987 Status: UNKNOWN Autor: C. Partridge, G. Trewitt |
| RFC1025 TCP and IP bake off This memo describes some of the procedures, scoring and tests used in the TCP and IP bake offs held in the early development of these protocols. These procedures and tests may still be of use in testing newly implemented TCP and IP modules. | September 1987 Status: UNKNOWN Autor: J. Postel |
| RFC1026 Addendum to RFC 987: (Mapping between X.400 and RFC-822) This memo suggest a proposed protocol for the Internet community, and request discussion and suggestions for improvements. | September 1987 Status: UNKNOWN Autor: S.E. Kille |
| RFC1027 Using ARP to implement transparent subnet gateways This RFC describes the use of the Address Resolution Protocol (ARP) by subnet gateways to permit hosts on the connected subnets to communicate without being aware of the existence of subnets, using the technique of "Proxy ARP". | October 1987 Status: UNKNOWN Autor: S. Carl-Mitchell, J.S. Quarterman |
| RFC1028 Simple Gateway Monitoring Protocol This memo defines a simple application-layer protocol by which management information for a gateway may be inspected or altered by remote users. This proposal is intended only as an interim response to immediate gateway monitoring needs. | November 1987 Status: HISTORIC Autor: J. Davin, J.D. Case, M. Fedor, M.L. Schoffstall |
| RFC1029 More fault tolerant approach to address resolution for a Multi-LAN system of Ethernets This memo discusses an extension to a Bridge Protocol to detect and disclose changes in heighbouring host address parameters in a Multi-Lan system of Ethernets. The problem is one which is appearing more and more regularly as the interconnected systems grow larger on Campuses and in Commercial Institutions. This RFC suggests a protocol enhancement for the Internet community, and requests discussion and suggestions for improvements. | May 1988 Status: UNKNOWN Autor: G. Parr |
| RFC1030 On testing the NETBLT Protocol over divers networks This memo describes the results gathered from testing NETBLT over three networks of different bandwidths and round-trip delays. The results are not complete, but the information gathered so far has not been promising. The NETBLT protocol is specified in RFC-998; this document assumes an understanding of the specification as described in RFC-998. | November 1987 Status: UNKNOWN Autor: M.L. Lambert |
| RFC1031 MILNET name domain transition This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community. The introduction of domain style names will impact all hosts in the DDN/MILNET Internet. This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system. | November 1987 Status: UNKNOWN Autor: W.D. Lazear |
| RFC1032 Domain administrators guide Domains are administrative entities that provide decentralized management of host naming and addressing. The domain-naming system is distributed and hierarchical. This memo describes procedures for registering a domain with the Network Information Center (NIC) of Defense Data Network (DDN), and offers guidelines on the establishment and administration of a domain in accordance with the requirements specified in RFC-920. It is recommended that the guidelines described in this document be used by domain administrators in the establishment and control of second-level domains. The role of the domain administrator (DA) is that of coordinator, manager, and technician. If his domain is established at the second level or lower in the tree, the domain administrator must register by interacting with the management of the domain directly above this. | November 1987 Status: UNKNOWN Autor: M.K. Stahl |
| RFC1033 Domain Administrators Operations Guide This RFC provides guidelines for domain administrators in operating a domain server and maintaining their portion of the hierarchical database. Familiarity with the domain system is assumed (see RFCs 1031, 1032, 1034, and 1035). | November 1987 Status: UNKNOWN Autor: M. Lottor |
| RFC1034 Domain names - concepts and facilities This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them. | November 1987 Status: STANDARD Autor: P.V. Mockapetris |
| RFC1035 Domain names - implementation and specification This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. | November 1987 Status: STANDARD Autor: P.V. Mockapetris |
| RFC1036 Standard for interchange of USENET messages This RFC defines the standard format for the interchange of network News messages among USENET hosts. It updates and replaces RFC-850, reflecting version B2.11 of the News program. This memo is distributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard. | December 1987 Status: UNKNOWN Autor: M.R. Horton, R. Adams |
| RFC1037 NFILE - a file access protocol This document includes a specification of the NFILE file access protocol and its underlying levels of protocol, the Token List Transport Layer and Byte Stream with Mark. The goal of this specification is to promote discussion of the ideas described here, and to encourage designers of future file protocols to take advantage of these ideas. A secondary goal is to make the specification available to sites that might benefit from implementing NFILE. | December 1987 Status: HISTORIC Autor: B. Greenberg, S. Keene |
| RFC1038 Draft revised IP security option This memo is a pre-publication draft of the revised Internet Protocol Security Option. This RFC reflects the version as approved by the Protocol Standards Steering group, and is provided for informational purposes only. The final version of this document will be available from Navy publications and should not differ from this document in any major fashion. This document will be published as a change to the MIL- STD 1777, "Internet Protocol". | January 1988 Status: UNKNOWN Autor: M. St. Johns |
| RFC1039 DoD statement on Open Systems Interconnection protocols This RFC reproduces a memorandum issued on 2-JUL-87 from the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (ASDC31) to the Director of the Defense Communications Agency (DCA). This memo is distributed for information only. | January 1988 Status: UNKNOWN Autor: D. Latham |
| RFC1040 Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This memo defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. Detailed key management mechanisms to support these procedures will be defined in a subsequent RFC. As a goal of this initial phase, it is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated. | January 1988 Status: UNKNOWN Autor: J. Linn |
| RFC1041 Telnet 3270 regime option This RFC specifies a proposed standard for the Internet community. Hosts on the Internet that want to support 3270 data stream within the Telnet protocol, are expected to adopt and implement this standard. | January 1988 Status: PROPOSED STANDARD Autor: Y. Rekhter |
| RFC1042 Standard for the transmission of IP datagrams over IEEE 802 networks This RFC specifies a standard method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on IEEE 802 Networks to allow compatible and interoperable implementations. This RFC specifies a protocol standard for the Internet community. | February 1988 Status: STANDARD Autor: J. Postel, J.K. Reynolds |
| RFC1043 Telnet Data Entry Terminal option: DODIIS implementation This RFC suggests a proposed protocol on the TELNET Data Entry Terminal (DET) Option - DODIIS Implementation for the Internet community. It is intended that this specification be capatible with the specification of DET Option in RFC-732. Discussion and suggests for improvements are encouraged. | February 1988 Status: PROPOSED STANDARD Autor: A. Yasuda, T. Thompson |
| RFC1044 Internet Protocol on Network System's HYPERchannel: Protocol Specification This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols. | February 1988 Status: STANDARD Autor: K. Hardwick, J. Lekashman |
| RFC1045 VMTP: Versatile Message Transaction Protocol: Protocol specification This memo specifies the Versatile Message Transaction Protocol (VMTP) [Version 0.7 of 19-Feb-88], a transport protocol specifically designed to support the transaction model of communication, as exemplified by remote procedure call (RPC). The full function of VMTP, including support for security, real-time, asynchronous message exchanges, streaming, multicast and idempotency, provides a rich selection to the VMTP user level. Subsettability allows the VMTP module for particular clients and servers to be specialized and simplified to the services actually required. Examples of such simple clients and servers include PROM network bootload programs, network boot servers, data sensors and simple controllers, to mention but a few examples. This RFC describes a protocol proposed as a standard for the Internet community. | February 1988 Status: EXPERIMENTAL Autor: D.R. Cheriton |
| RFC1046 Queuing algorithm to provide type-of-service for IP links This memo is intended to explore how Type-of-Service might be implemented in the Internet. The proposal describes a method of queuing which can provide the different classes of service. The technique also prohibits one class of service from consuming excessive resources or excluding other classes of service. This is an "idea paper" and discussion is strongly encouraged. | February 1988 Status: UNKNOWN Autor: W. Prue, J. Postel |
| RFC1047 Duplicate messages and SMTP An examination of a synchronization problem in the Simple Mail Transfer Protocol (SMTP) is presented. This synchronization problem can cause a message to be delivered multiple times. A method for avoiding this problem is suggested. Nodding familiarity with the SMTP specification, RFC-821, is required. | February 1988 Status: UNKNOWN Autor: C. Partridge |
| RFC1048 BOOTP vendor information extensions This memo proposes an addition to the Bootstrap Protocol (BOOTP). Comments and suggestions for improvements are sought. | February 1988 Status: UNKNOWN Autor: P.A. Prindeville |
| RFC1049 Content-type header field for Internet messages This memo suggests proposed additions to the Internet Mail Protocol, RFC-822, for the Internet community, and requests discussion and suggestions for improvements. | March 1988 Status: HISTORIC Autor: M.A. Sirbu |
| RFC1050 RPC: Remote Procedure Call Protocol specification This memo specifies a message protocol used in implementing Sun's Remote Procedure Call (RPC) package. This RFC describes a standard that Sun Microsystems and others are using and is one they wish to propose for the Internet's consideration. It is not an Internet standard at this time. | April 1988 Status: HISTORIC Autor: Sun Microsystems |
| RFC1051 Standard for the transmission of IP datagrams and ARP packets over ARCNET networks This memo specifies a standard method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams on an ARCNET. This RFC is a standard protocol for the Internet community. | March 1988 Status: HISTORIC Autor: P.A. Prindeville |
| RFC1052 IAB recommendations for the development of Internet network management standards This RFC is intended to convey to the Internet community and other interested parties the recommendations of the Internet Activities Board (IAB) for the development of network management protocols for use in the TCP/IP environment. This memo does NOT, in and of itself, define or propose an Official Internet Protocol. It does reflect, however, the policy of the IAB with respect to further network management development in the short and long term. | April 1988 Status: UNKNOWN Autor: V.G. Cerf |
| RFC1053 Telnet X.3 PAD option This RFC proposes a new option to Telnet for the Internet community, and requests discussion and suggestions for improvements. | April 1988 Status: PROPOSED STANDARD Autor: S. Levy, T. Jacobson |
| RFC1054 Host extensions for IP multicasting This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. IP multicasting is the transmission of an IP datagram to a "host group", a set hosts identified by a single IP destination address. A multicast datagram is delivered to all members of its destination host group with the same "best-efforts" reliability as regular unicast IP datagrams. It is proposed as a standard for IP multicasting in the Internet. This specification is a major revision of RFC-988. | May 1988 Status: UNKNOWN Autor: S.E. Deering |
| RFC1055 Nonstandard for transmission of IP datagrams over serial lines: SLIP The TCP/IP protocol family runs over a variety of network media: IEEE 802.3 (ethernet) and 802.5 (token ring) LAN's, X.25 lines, satellite links, and serial lines. There are standard encapsulations for IP packets defined for many of these networks, but there is no standard for serial lines. SLIP, Serial Line IP, is a currently a de facto standard, commonly used for point-to-point serial connections running TCP/IP. It is not an Internet standard. | June 1988 Status: STANDARD Autor: J.L. Romkey |
| RFC1056 PCMAIL: A distributed mail system for personal computers This memo is a discussion of the Pcmail workstation based distributed mail system. It is identical to the discussion in RFC-993, save that a new, much simpler mail transport protocol is described. The new transport protocol is the result of continued research into ease of protocol implementation and use issues. | June 1988 Status: INFORMATIONAL Autor: M.L. Lambert |
| RFC1057 RPC: Remote Procedure Call Protocol specification: Version 2 This RFC describes a standard that Sun Microsystems and others are using, and is one we wish to propose for the Internet's consideration. This memo is not an Internet standard at this time. | June 1988 Status: INFORMATIONAL Autor: Sun Microsystems |
| RFC1058 Routing Information Protocol This RFC describes an existing protocol for exchanging routing information among gateways and other hosts. It is intended to be used as a basis for developing gateway software for use in the Internet community. | June 1988 Status: HISTORIC Autor: C.L. Hedrick |
| RFC1059 Network Time Protocol (version 1) specification and implementation This memo describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical master-slave configuration synchronizes logical clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. The NTP architectures, algorithms and protocols which have evolved over several years of implementation and refinement are described in this document. The prototype system, which has been in regular operation in the Internet for the last two years, is described in an Appendix along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even the cases of failure or disruption of clocks, time servers or nets. This is a Draft Standard for an Elective protocol. | July 1988 Status: UNKNOWN Autor: D.L. Mills |
| RFC1060 Assigned numbers This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited. | March 1990 Status: HISTORIC Autor: J.K. Reynolds, J. Postel |
| RFC1062 Internet numbers This memo is an official status report on the network numbers and gateway autonomous system numbers used in the Internet community. | August 1988 Status: UNKNOWN Autor: S. Romano, M.K. Stahl, M. Recker |
| RFC1063 IP MTU discovery options A pair of IP options that can be used to learn the minimum MTU of a path through an internet is described, along with its possible uses. This is a proposal for an Experimental protocol. | July 1988 Status: UNKNOWN Autor: J.C. Mogul, C.A. Kent, C. Partridge, K. McCloghrie |
| RFC1064 Interactive Mail Access Protocol: Version 2 This memo suggests a method for workstations to dynamically access mail from a mailbox server ("respository"). This RFC specifies a standard for the SUMEX-AIM community and a proposed experimental protocol for the Internet community. Discussion and suggestions for improvement are requested. | July 1988 Status: UNKNOWN Autor: M.R. Crispin |
| RFC1065 Structure and identification of management information for TCP/IP-based internets This RFC provides the common definitions for the structure and identification of management information for TCP/IP-based internets. In particular, together with its companion memos, which describe the initial management information base along with the initial network management protocol, these documents provide a simple, working architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementation in the Internet which are network manageable are expected to adopt and implement this specification. | August 1988 Status: STANDARD Autor: K. McCloghrie, M.T. Rose |
| RFC1066 Management Information Base for network management of TCP/IP-based internets This RFC provides the initial version of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets in the short-term. In particular, together with its companion memos which describe the structure of management information along with the initial network management protocol, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets, and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification. | August 1988 Status: UNKNOWN Autor: K. McCloghrie, M.T. Rose |
| RFC1067 Simple Network Management Protocol This RFC defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular, the Internet. This memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification. | August 1988 Status: UNKNOWN Autor: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin |
| RFC1068 Background File Transfer Program (BFTP) This RFC describes an Internet background file transfer service that is built upon the third-party transfer model of FTP. No new protocols are involved. The purpose of this memo is to stimulate discussions on new Internet service modes. | August 1988 Status: UNKNOWN Autor: A.L. DeSchon, R.T. Braden |
| RFC1069 Guidelines for the use of Internet-IP addresses in the ISO Connectionless-Mode Network Protocol This RFC suggests an addressing scheme for use with the ISO Connectionless Network Protocol (CLNP) in the Internet. This is a solution to one of the problems inherent in the use of "ISO-grams" in the Internet. This memo is a revision of RFC 986. This RFC suggests a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. | February 1989 Status: UNKNOWN Autor: R.W. Callon, H.W. Braun |
| RFC1070 Use of the Internet as a subnetwork for experimentation with the OSI network layer This RFC proposes a scenario for experimentation with the International Organization for Standardization (ISO) Open Systems Interconnection (OSI) network layer protocols over the Internet and requests discussion and suggestions for improvements to this scenario. This RFC also proposes the creation of an experimental OSI internet. To participate in the experimental OSI internet, a system must abide by the agreements set forth in this RFC. | February 1989 Status: UNKNOWN Autor: R.A. Hagens, N.E. Hall, M.T. Rose |
| RFC1071 Computing the Internet checksum This RFC summarizes techniques and algorithms for efficiently computing the Internet checksum. It is not a standard, but a set of useful implementation techniques. | September 1988 Status: UNKNOWN Autor: R.T. Braden, D.A. Borman, C. Partridge |
| RFC1072 TCP extensions for long-delay paths This RFC proposes a set of extensions to the TCP protocol to provide efficient operation over a path with a high bandwidth*delay product. These extensions are not proposed as an Internet standard at this time. Instead, they are intended as a basis for further experimentation and research on transport protocol performance. | October 1988 Status: HISTORIC Autor: V. Jacobson, R.T. Braden |
| RFC1073 Telnet window size option This RFC describes a proposed Telnet option to allow a client to convey window size to a Telnet server. | October 1988 Status: PROPOSED STANDARD Autor: D. Waitzman |
| RFC1074 NSFNET backbone SPF based Interior Gateway Protocol This RFC is an implementation description of the standard ANSI IS-IS and ISO ES-IS routing protocols within the NSFNET backbone network. | October 1988 Status: UNKNOWN Autor: J. Rekhter |
| RFC1075 Distance Vector Multicast Routing Protocol This RFC describes a distance-vector-style routing protocol for routing multicast datagrams through an internet. It is derived from the Routing Information Protocol (RIP), and implements multicasting as described in RFC-1054. This is an experimental protocol, and its implementation is not recommended at this time. | November 1988 Status: EXPERIMENTAL Autor: D. Waitzman, C. Partridge, S.E. Deering |
| RFC1076 HEMS monitoring and control language This RFC specifies a query language for monitoring and control of network entities. This RFC supercedes RFC 1023, extending the query language and providing more discussion of the underlying issues. This language is a component of the High-Level Entity Monitoring System (HEMS) described in RFC 1021 and RFC 1022. Readers may wish to consult these RFCs when reading this memo. RFC 1024 contains detailed assignments of numbers and structures used in this system. Portions of RFC 1024 that define query language structures are superceded by definitions in this memo. This memo assumes a knowledge of the ISO data encoding standard, ASN.1. | November 1988 Status: UNKNOWN Autor: G. Trewitt, C. Partridge |
| RFC1077 Critical issues in high bandwidth networking This memo presents the results of a working group on High Bandwidth Networking. This RFC is for your information and you are encouraged to comment on the issues presented. | November 1988 Status: UNKNOWN Autor: B.M. Leiner |
| RFC1078 TCP port service Multiplexer (TCPMUX) This RFC proposes an Internet standard which can be used by future TCP services instead of using 'well-known ports'. | November 1988 Status: UNKNOWN Autor: M. Lottor |
| RFC1079 Telnet terminal speed option This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal speed information within the Telnet protocol are expected to adopt and implement this standard. | December 1988 Status: PROPOSED STANDARD Autor: C.L. Hedrick |
| RFC1080 Telnet remote flow control option This RFC specifies a standard for the Internet community. Hosts on the Internet that do remote flow control within the Telnet protocol are expected to adopt and implement this standard. | November 1988 Status: UNKNOWN Autor: C.L. Hedrick |
| RFC1081 Post Office Protocol: Version 3 This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. | November 1988 Status: UNKNOWN Autor: M.T. Rose |
| RFC1082 Post Office Protocol: Version 3: Extended service offerings This memo suggests a simple method for workstations to dynamically access mail from a discussion group server, as an extension to an earlier memo which dealt with dynamically accessing mail from a mailbox server using the Post Office Protocol - Version 3 (POP3). This RFC specifies a proposed protocol for the Internet community, and requests discussion and suggestions for improvements. All of the extensions described in this memo to the POP3 are OPTIONAL. | November 1988 Status: UNKNOWN Autor: M.T. Rose |
| RFC1083 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. | December 1988 Status: HISTORIC Autor: Defense Advanced Research Projects Agency, Internet Activities Board |
| RFC1084 BOOTP vendor information extensions This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville. This memo will be updated as additional tags are are defined. This edition introduces Tag 13 for Boot File Size. Comments and suggestions for improvements are sought. | December 1988 Status: UNKNOWN Autor: J.K. Reynolds |
| RFC1085 ISO presentation services on top of TCP/IP based internets RFC 1006 describes a mechanism for providing the ISO transport service on top of TCP/IP. Once this method is applied, one may implement "real" ISO applications on top of TCP/IP-based internets, by simply implementing OSI session, presentation, and application services on top of the transport service access point which is provided on top of the TCP. Although straight-forward, there are some environments in which the richness provided by the OSI application layer is desired, but it is nonetheless impractical to implement the underlying OSI infrastructure (i.e., the presentation, session, and transport services on top of the TCP). This memo describes an approach for providing "stream-lined" support of OSI application services on top of TCP/IP-based internets for such constrained environments. This memo proposes a standard for the Internet community. | December 1988 Status: UNKNOWN Autor: M.T. Rose |
| RFC1086 ISO-TP0 bridge between TCP and X.25 This memo proposes a standard for the Internet community. Hosts on the Internet that choose to implement ISO TP0 transport connectivity between TCP and X.25 based hosts are expected to experiment with this proposal. TCP port 146 is reserved for this proposal. | December 1988 Status: UNKNOWN Autor: J.P. Onions, M.T. Rose |
| RFC1087 Ethics and the Internet This memo is a statement of policy by the Internet Activities Board (IAB) concerning the proper use of the resources of the Internet. | January 1989 Status: UNKNOWN Autor: Defense Advanced Research Projects Agency, Internet Activities Board |
| RFC1088 Standard for the transmission of IP datagrams over NetBIOS networks This document specifies a standard method of encapsulating the Internet Protocol (IP) datagrams on NetBIOS networks. | February 1989 Status: STANDARD Autor: L.J. McLaughlin |
| RFC1089 SNMP over Ethernet This memo describes an experimental method by which the Simple Network Management Protocol (SNMP) can be used over Ethernet MAC layer framing instead of the Internet UDP/IP protocol stack. This specification is useful for LAN based network elements that support no higher layer protocols beyond the MAC sub-layer. | February 1989 Status: UNKNOWN Autor: M. Schoffstall, C. Davin, M. Fedor, J. Case |
| RFC1090 SMTP on X.25 This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT. | February 1989 Status: UNKNOWN Autor: R. Ullmann |
| RFC1091 Telnet terminal-type option This RFC specifies a standard for the Internet community. Hosts on the Internet that exchange terminal type information within the Telnet protocol are expected to adopt and implement this standard. This standard supersedes RFC 930. A change is made to permit cycling through a list of possible terminal types and selecting the most appropriate | February 1989 Status: PROPOSED STANDARD Autor: J. VanBokkelen |
| RFC1092 EGP and policy based routing in the new NSFNET backbone This memo discusses implementation decisions for routing issues in the NSFNET, especially in the NSFNET Backbone. Of special concern is the restriction of routing information to advertize the best route as established by a policy decision. | February 1989 Status: UNKNOWN Autor: J. Rekhter |
| RFC1093 NSFNET routing architecture This document describes the routing architecture for the NSFNET centered around the new NSFNET Backbone, with specific emphasis on the interface between the backbone and its attached networks. | February 1989 Status: UNKNOWN Autor: H.W. Braun |
| RFC1094 NFS: Network File System Protocol specification This RFC describes a protocol that Sun Microsystems, Inc., and others are using. A new version of the protocol is under development, but others may benefit from the descriptions of the current protocol, and discussion of some of the design issues. | March 1989 Status: INFORMATIONAL Autor: B. Nowicki |
| RFC1095 Common Management Information Services and Protocol over TCP/IP (CMOT) This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in a TCP/IP environment. This architecture provides a means by which control and monitoring information can be exchanged between a manager and a remote network element. In particular, this memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard. Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP- based internets, and in particular the Internet. | April 1989 Status: UNKNOWN Autor: U.S. Warrier, L. Besaw |
| RFC1096 Telnet X display location option This RFC specifies a standard for the Internet community. Hosts on the Internet that transmit the X display location within the Telnet protocol are expected to adopt and implement this standard. | March 1989 Status: PROPOSED STANDARD Autor: G.A. Marcy |
| RFC1097 Telnet subliminal-message option This RFC specifies a standard for the Internet community. Hosts on the Internet that display subliminal messages within the Telnet protocol are expected to adopt and implement this standard. | April 1989 Status: UNKNOWN Autor: B. Miller |
| RFC1098 Simple Network Management Protocol (SNMP) This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet. | April 1989 Status: UNKNOWN Autor: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin |
| RFC1099 Request for Comments Summary: RFC Numbers 1000-1099 | December 1991 Status: INFORMATIONAL Autor: J. Reynolds |
| RFC1100 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority (see the contact information at the end of this memo). Do not use this memo after 31-July-89. | April 1989 Status: HISTORIC Autor: Defense Advanced Research Projects Agency, Internet Activities Board |
| RFC1101 DNS encoding of network names and other types This RFC proposes two extensions to the Domain Name System: - A specific method for entering and retrieving RRs which map between network names and numbers. - Ideas for a general method for describing mappings between arbitrary identifiers and numbers. The method for mapping between network names and addresses is a proposed standard, the ideas for a general method are experimental. | April 1989 Status: UNKNOWN Autor: P.V. Mockapetris |
| RFC1102 Policy routing in Internet protocols The purpose of this RFC is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. | May 1989 Status: UNKNOWN Autor: D.D. Clark |
| RFC1103 Proposed standard for the transmission of IP datagrams over FDDI Networks This RFC specifies a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] | June 1989 Status: UNKNOWN Autor: D. Katz |
| RFC1104 Models of policy based routing The purpose of this RFC is to outline a variety of models for policy based routing. The relative benefits of the different approaches are reviewed. Discussions and comments are explicitly encouraged to move toward the best policy based routing model that scales well within a large internetworking environment. | June 1989 Status: UNKNOWN Autor: H.W. Braun |
| RFC1105 Border Gateway Protocol (BGP) This RFC outlines a specific approach for the exchange of network reachability information between Autonomous Systems. Updated by RFCs 1163 and 1164. [STANDARDS-TRACK] | June 1989 Status: EXPERIMENTAL Autor: K. Lougheed, Y. Rekhter |
| RFC1106 TCP big window and NAK options This memo discusses two extensions to the TCP protocol to provide a more efficient operation over a network with a high bandwidth*delay product. The extensions described in this document have been implemented and shown to work using resources at NASA. This memo describes an Experimental Protocol, these extensions are not proposed as an Internet standard, but as a starting point for further research. | June 1989 Status: HISTORIC Autor: R. Fox |
| RFC1107 Plan for Internet directory services This memo proposes a program to develop a directory service for the Internet. It reports the results of a meeting held in February 1989, which was convened to review requirements and options for such a service. This proposal is offered for comment, and does not represent a committed research activity of the Internet community. | July 1989 Status: INFORMATIONAL Autor: K.R. Sollins |
| RFC1108 U.S. Department of Defense Security Options for the Internet Protocol This RFC specifies the U.S. Department of Defense Basic Security Option and the top-level description of the Extended Security Option for use with the Internet Protocol. This RFC obsoletes RFC 1038, "Revised IP Security Option", dated January 1988. [STANDARDS-TRACK] | November 1991 Status: HISTORIC Autor: S. Kent |
| RFC1109 Report of the second Ad Hoc Network Management Review Group This RFC reports an official Internet Activities Board (IAB) policy position on the treatment of Network Management in the Internet. This RFC presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989. The results of the first such meeting were reported in RFC 1052. | August 1989 Status: UNKNOWN Autor: V.G. Cerf |
| RFC1110 Problem with the TCP big window option This memo comments on the TCP Big Window option described in RFC 1106. | August 1989 Status: HISTORIC Autor: A.M. McKenzie |
| RFC1111 Request for comments on Request for Comments: Instructions to RFC authors This RFC specifies a standard for the Internet community. Authors of RFCs are expected to adopt and implement this standard. | August 1989 Status: INFORMATIONAL Autor: J. Postel |
| RFC1112 Host extensions for IP multicasting This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Recommended procedure for IP multicasting in the Internet. This RFC obsoletes RFCs 998 and 1054. [STANDARDS-TRACK] | August 1989 Status: STANDARD Autor: S.E. Deering |
| RFC1113 Privacy enhancement for Internet electronic mail: Part I - message encipherment and authentication procedures This RFC specifies features for private electronic mail based on encryption technology. [STANDARDS-TRACK] | August 1989 Status: HISTORIC Autor: J. Linn |
| RFC1114 Privacy enhancement for Internet electronic mail: Part II - certificate-based key management This RFC specifies the key management aspects of Privacy Enhanced Mail. [STANDARDS-TRACK] | August 1989 Status: HISTORIC Autor: S.T. Kent, J. Linn |
| RFC1115 Privacy enhancement for Internet electronic mail: Part III - algorithms, modes, and identifiers This RFC provides definitions, references, and citations for algorithms, usage modes, and associated identifiers used in RFC-1113 and RFC-1114 in support of privacy-enhanced electronic mail. [STANDARDS-TRACK] | August 1989 Status: HISTORIC Autor: J. Linn |
| RFC1116 Telnet Linemode option Hosts on the Internet that support Linemode within the Telnet protocol are expected to adopt and implement this protocol. Obsoleted by RFC 1184. [STANDARDS-TRACK] | August 1989 Status: PROPOSED STANDARD Autor: D.A. Borman |
| RFC1117 Internet numbers This memo is an official status report on the network numbers and the autonomous system numbers used in the Internet community. | August 1989 Status: INFORMATIONAL Autor: S. Romano, M.K. Stahl, M. Recker |
| RFC1118 Hitchhikers guide to the Internet This RFC is being distributed to members of the Internet community in order to make available some "hints" which will allow new network participants to understand how the direction of the Internet is set, how to acquire online information and how to be a good Internet neighbor. While the information discussed may not be relevant to the research problems of the Internet, it may be interesting to a number of researchers and implementors. No standards are defined or specified in this memo. | September 1989 Status: INFORMATIONAL Autor: E. Krol |
| RFC1119 Network Time Protocol (version 2) specification and implementation This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self- organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. [STANDARDS-TRACK] | September 1989 Status: STANDARD Autor: D.L. Mills |
| RFC1120 Internet Activities Board This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard. | September 1989 Status: INFORMATIONAL Autor: V. Cerf |
| RFC1121 Act one - the poems This RFC presents a collection of poems that were presented at "Act One", a symposium held partially in celebration of the 20th anniversary of the ARPANET. | September 1989 Status: INFORMATIONAL Autor: J. Postel, L. Kleinrock, V.G. Cerf, B. Boehm |
| RFC1122 Requirements for Internet Hosts - Communication Layers This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] | October 1989 Status: STANDARD Autor: R. Braden |
| RFC1123 Requirements for Internet Hosts - Application and Support This RFC is an official specification for the Internet community. It incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts. [STANDARDS-TRACK] | October 1989 Status: STANDARD Autor: R. Braden |
| RFC1124 Policy issues in interconnecting networks To support the activities of the Federal Research Internet Coordinating Committee (FRICC) in creating an interconnected set of networks to serve the research community, two workshops were held to address the technical support of policy issues that arise when interconnecting such networks. Held under the suspices of the Internet Activities Board at the request of the FRICC, and sponsored by NASA through RIACS, the workshops addressed the required and feasible technologies and architectures that could be used to satisfy the desired policies for interconnection. The purpose of this RFC is to report the results of these workshops. | September 1989 Status: UNKNOWN Autor: B.M. Leiner |
| RFC1125 Policy requirements for inter Administrative Domain routing The purpose of this memo is to focus discussion on particular problems in the Internet and possible methods of solution. No proposed solutions in this document are intended as standards for the Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to such problems, leading eventually to the development and adoption of standards. | November 1989 Status: UNKNOWN Autor: D. Estrin |
| RFC1126 Goals and functional requirements for inter-autonomous system routing This document describes the functional requirements for a routing protocol to be used between autonomous systems. This document is intended as a necessary precursor to the design of a new inter- autonomous system routing protocol and specifies requirements for the Internet applicable for use with the current DoD IP, the ISO IP, and future Internet Protocols. It is intended that these requirements will form the basis for the future development of a new inter-autonomous systems routing architecture and protocol. This memo does not specify a standard. | October 1989 Status: UNKNOWN Autor: M. Little |
| RFC1127 Perspective on the Host Requirements RFCs This RFC is for information only; it does not constitute a standard, draft standard, or proposed standard, and it does not define a protocol. | October 1989 Status: INFORMATIONAL Autor: R.T. Braden |
| RFC1128 Measured performance of the Network Time Protocol in the Internet system This paper describes a series of experiments involving over 100,000 hosts of the Internet system and located in the U.S., Europe and the Pacific. The experiments are designed to evaluate the availability, accuracy and reliability of international standard time distribution using the DARPA/NSF Internet and the Network Time Protocol (NTP), which is specified in RFC-1119. NTP is designed specifically for use in a large, diverse internet system operating at speeds from mundane to lightwave. In NTP a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration exchange precision timestamps in order to synchronize subnet clocks to each other and national time standards via wire or radio. The experiments are designed to locate Internet hosts and gateways that provide time by one of three time distribution protocols and evaluate the accuracy of their indications. For those hosts that support NTP, the experiments determine the distribution of errors and other statistics over paths spanning major portions of the globe. Finally, the experiments evaluate the accuracy and reliability of precision timekeeping using NTP and typical Internet paths involving DARPA, NSFNET and other agency networks. The experiments demonstrate that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo does not specify a standard. | October 1989 Status: UNKNOWN Autor: D.L. Mills |
| RFC1129 Internet Time Synchronization: The Network Time Protocol This memo describes the Network Time Protocol (NTP) designed to distribute time information in a large, diverse internet system operating at speeds from mundane to lightwave. It uses a returnable- time architecture in which a distributed subnet of time servers operating in a self-organizing, hierarchical, master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute time information within a network via local routing algorithms and time daemons. The architectures, algorithms and protocols which have evolved to NTP over several years of implementation and refinement are described in this paper. The synchronization subnet which has been in regular operation in the Internet for the last several years is described along with performance data which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few tens of milliseconds, even in cases of failure or disruption of clocks, time servers or networks. This memo describes the Network Time Protocol in RFC-1119. | October 1989 Status: INFORMATIONAL Autor: D.L. Mills |
| RFC1130 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). | October 1989 Status: HISTORIC Autor: Defense Advanced Research Projects Agency, Internet Activities Board |
| RFC1131 OSPF specification This RFC is the specification of the Open Shortest Path First (OSPF) Internet routing protocol. OSPF is in the class of Internal Gateway Protocols (IGPs) for distributing routing information between gateways of a single Autonomous System. This routing protocol is based on the link-state approach (in contrast to the distance-vector approach). This specification was developed by the OSPF Working Group of the Internet Engineering Task Force. [STANDARDS-TRACK] | October 1989 Status: PROPOSED STANDARD Autor: J. Moy |
| RFC1132 Standard for the transmission of 802.2 packets over IPX networks This document specifies a standard method of encapsulating 802.2 packets on networks supporting Novell's Internet Packet Exchange Protocol (IPX). It obsoletes earlier documents detailing the transmission of Internet packets over IPX networks. It differs from these earlier documents in that it allows for the transmission of multiple network protocols over IPX and for the transmission of packets through IPX bridges. | November 1989 Status: STANDARD Autor: L.J. McLaughlin |
| RFC1133 Routing between the NSFNET and the DDN This document is a case study of the implementation of routing between the NSFNET and the DDN components (the MILNET and the ARPANET). We hope that it can be used to expand towards interconnection of other Administrative Domains. We would welcome discussion and suggestions about the methods employed for the interconnections. No standards are specified in this memo. | November 1989 Status: INFORMATIONAL Autor: J.Y. Yu, H.W. Braun |
| RFC1134 Point-to-Point Protocol: A proposal for multi-protocol transmission of datagrams over Point-to-Point links This proposal is the product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments on this memo should be submitted to the IETF Point-to-Point Protocol Working Group chair by January 15, 1990. Comments will be reviewed at the February 1990 IETF meeting, with the goal of advancing PPP to draft standard status. [STANDARDS-TRACK] | November 1989 Status: PROPOSED STANDARD Autor: D. Perkins |
| RFC1135 Helminthiasis of the Internet This memo takes a look back at the helminthiasis (infestation with, or disease caused by parasitic worms) of the Internet that was unleashed the evening of 2 November 1988. This RFC provides information about an event that occurred in the life of the Internet. This memo does not specify any standard. This document provides a glimpse at the infection, its festering, and cure. The impact of the worm on the Internet community, ethics statements, the role of the news media, crime in the computer world, and future prevention is discussed. A documentation review presents four publications that describe in detail this particular parasitic computer program. Reference and bibliography sections are also included. | December 1989 Status: INFORMATIONAL Autor: J.K. Reynolds |
| RFC1136 Administrative Domains and Routing Domains: A model for routing in the Internet This RFC proposes a model for describing routing within the Internet. The model is an adaptation of the "OSI Routeing Framework". This memo does not specify an Internet standard. | December 1989 Status: INFORMATIONAL Autor: S. Hares, D. Katz |
| RFC1137 Mapping between full RFC 822 and RFC 822 with restricted encoding This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. | December 1989 Status: HISTORIC Autor: S. Kille |
| RFC1138 Mapping between X.400(1988) / ISO 10021 and RFC 822 Ths RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This memo updates RFCs 822, 987, and 1026. | December 1989 Status: EXPERIMENTAL Autor: S.E. Kille |
| RFC1139 Echo function for ISO 8473 This memo defines an echo function for the connection-less network layer protocol. Two mechanisms are introduced that may be used to implement the echo function. The first mechanism is recommended as an interim solution for the Internet community. The second mechanism will be progressed to the ANSI X3S3.3 working group for consideration as a work item. When an ISO standard is adopted that provides functionality similar to that described by this memo, then this memo will become obsolete and superceded by the ISO standard. This memo is not intended to compete with an ISO standard. [STANDARDS-TRACK] | January 1990 Status: PROPOSED STANDARD Autor: R.A. Hagens |
| RFC1140 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo is issued quarterly, please be sure the copy you are reading is dated within the last three months. Current copies may be obtained from the Network Information Center or from the Internet Assigned Numbers Authority. Do not use this edition after 31-Aug-90. | May 1990 Status: HISTORIC Autor: Defense Advanced Research Projects Agency, Internet Activities Board |
| RFC1141 Incremental updating of the Internet checksum This memo correctly describes the incremental update procedure for use with the standard Internet checksum. It is intended to replace the description of Incremental Update in RFC 1071. This is not a standard but rather, an implementation technique. | January 1990 Status: INFORMATIONAL Autor: T. Mallory, A. Kullberg |
| RFC1142 OSI IS-IS Intra-domain Routing Protocol This RFC is a republication of ISO DP 10589 as a service to the Internet community. This is not an Internet standard. | February 1990 Status: INFORMATIONAL Autor: D. Oran |
| RFC1143 The Q Method of Implementing TELNET Option Negotiation This is RFC discusses an implementation approach to option negotiation in the Telnet protocol (RFC 854). It does not propose any changes to the TELNET protocol. Rather, it discusses the implementation of the protocol of one feature, only. This is not a protocol specification. This is an experimental method of implementing a protocol. | February 1990 Status: EXPERIMENTAL Autor: D.J. Bernstein |
| RFC1144 Compressing TCP/IP Headers for Low-Speed Serial Links This RFC describes a method for compressing the headers of TCP/IP datagrams to improve performance over low speed serial links. The motivation, implementation and performance of the method are described. C code for a sample implementation is given for reference. [STANDARDS-TRACK] | February 1990 Status: PROPOSED STANDARD Autor: V. Jacobson |
| RFC1145 TCP alternate checksum options This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. | February 1990 Status: HISTORIC Autor: J. Zweig, C. Partridge |
| RFC1146 TCP alternate checksum options This memo is suggests a pair of TCP options to allow use of alternate data checksum algorithms in the TCP header. The use of these options is experimental, and not recommended for production use. Note: This RFC corrects errors introduced in the editing process in RFC 1145. | March 1990 Status: HISTORIC Autor: J. Zweig, C. Partridge |
| RFC1147 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices The goal of this FYI memo is to provide practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. [Also FYI 2.] This catalog contains descriptions of several tools available to assist network managers in debugging and maintaining TCP/IP internets and interconnected communications resources. Entries in the catalog tell what a tool does, how it works, and how it can be obtained. | April 1990 Status: INFORMATIONAL Autor: R.H. Stine |
| RFC1148 Mapping between X.400(1988) / ISO 10021 and RFC 822 This RFC suggests an electronic mail protocol mapping for the Internet community and UK Academic Community, and requests discussion and suggestions for improvements. This memo does not specify an Internet standard. This edition includes material lost in editing. | March 1990 Status: EXPERIMENTAL Autor: S.E. Kille |
| RFC1149 Standard for the transmission of IP datagrams on avian carriers This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard. | April 1990 Status: EXPERIMENTAL Autor: D. Waitzman |
| RFC1150 FYI on FYI: Introduction to the FYI Notes This memo is the first in a new sub-series of RFCs called FYIs (For Your Information). This memo provides information for the Internet community. It does not specify any standard. [Also FYI 1.] | March 1990 Status: HISTORIC Autor: G.S. Malkin, J.K. Reynolds |
| RFC1151 Version 2 of the Reliable Data Protocol (RDP) This RFC suggests several updates to the specification of the Reliable Data Protocol (RDP) in RFC-908 based on experience with the protocol. This revised version of the protocol is experimental. | April 1990 Status: EXPERIMENTAL Autor: C. Partridge, R.M. Hinden |
| RFC1152 Workshop report: Internet research steering group workshop on very-high-speed networks This memo is a report on a workshop sponsored by the Internet Research Steering Group. This memo is for information only. This RFC does not specify an Internet standard. | April 1990 Status: INFORMATIONAL Autor: C. Partridge |
| RFC1153 Digest message format This memo describes the de facto standard Digest Message Format. This is an elective experimental protocol. | April 1990 Status: EXPERIMENTAL Autor: F.J. Wancho |
| RFC1154 Encoding header field for internet messages This RFC proposes an elective experimental Encoding header field to permit the mailing of multi-part, multi-structured messages. The use of Encoding updates RFC 1049 (Content-Type), and is a suggested update to RFCs 1113, 1114, and 1115 (Privacy Enhancement). | April 1990 Status: EXPERIMENTAL Autor: D. Robinson, R. Ullmann |
| RFC1155 Structure and identification of management information for TCP/IP-based internets This RFC is a re-release of RFC 1065, with a changed "Status of this Memo", plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1065. [STANDARDS-TRACK] | May 1990 Status: STANDARD Autor: M.T. Rose, K. McCloghrie |
| RFC1156 Management Information Base for network management of TCP/IP-based internets This RFC is a re-release of RFC 1066, with a changed "Status of this Memo", "IAB Policy Statement", and "Introduction" sections plus a few minor typographical corrections. The technical content of the document is unchanged from RFC 1066. [STANDARDS-TRACK] | May 1990 Status: HISTORIC Autor: K. McCloghrie, M.T. Rose |
| RFC1157 Simple Network Management Protocol (SNMP) This RFC is a re-release of RFC 1098, with a changed "Status of this Memo" section plus a few minor typographical corrections. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. [STANDARDS-TRACK] | May 1990 Status: HISTORIC Autor: J.D. Case, M. Fedor, M.L. Schoffstall, J. Davin |
| RFC1158 Management Information Base for network management of TCP/IP-based internets: MIB-II This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP- based internets. In particular, together with its companion memos which describe the structure of management information (RFC 1155) along with the network management protocol (RFC 1157) for TCP/IP- based internets, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet community. This document on MIB-II incorporates all of the technical content of RFC 1156 on MIB-I and extends it, without loss of compatibilty. [STANDARDS-TRACK] | May 1990 Status: PROPOSED STANDARD Autor: M.T. Rose |
| RFC1159 Message Send Protocol This RFC suggests an Experimental Protocol for the Internet community. Hosts on the Internet that choose to implement a Message Send Protocol may experiment with this protocol. | June 1990 Status: EXPERIMENTAL Autor: R. Nelson |
| RFC1160 Internet Activities Board This RFC provides a history and description of the Internet Activities Board (IAB) and its subsidiary organizations. This memo is for informational use and does not constitute a standard. This is a revision of RFC 1120. | May 1990 Status: INFORMATIONAL Autor: V. Cerf |
| RFC1161 SNMP over OSI This memo defines an experimental means for running the Simple Network Management Protocol (SNMP) over OSI transports. This memo does not specify a standard for the Internet community, | June 1990 Status: EXPERIMENTAL Autor: M.T. Rose |
| RFC1162 Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) Management Information Base This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This memo does not specify a standard for the Internet community. | June 1990 Status: EXPERIMENTAL Autor: G. Satz |
| RFC1163 Border Gateway Protocol (BGP) This RFC, together with its companion RFC-1164, "Application of the Border Gateway Protocol in the Internet", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] | June 1990 Status: HISTORIC Autor: K. Lougheed, Y. Rekhter |
| RFC1164 Application of the Border Gateway Protocol in the Internet This RFC, together with its companion RFC-1163, "A Border Gateway Protocol (BGP)", specify an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] | June 1990 Status: HISTORIC Autor: J.C. Honig, D. Katz, M. Mathis, Y. Rekhter, J.Y. Yu |
| RFC1165 Network Time Protocol (NTP) over the OSI Remote Operations Service This memo suggests an Experimental Protocol for the OSI and Internet communities. Hosts in either community, and in particular those on both are encouraged to experiment with this mechanism. | June 1990 Status: EXPERIMENTAL Autor: J. Crowcroft, J.P. Onions |
| RFC1166 Internet numbers This memo is a status report on the network numbers and autonomous system numbers used in the Internet community. | July 1990 Status: INFORMATIONAL Autor: S. Kirkpatrick, M.K. Stahl, M. Recker |
| RFC1167 Thoughts on the National Research and Education Network The memo provides a brief outline of a National Research and Education Network (NREN). This memo provides information for the Internet community. It does not specify any standard. It is not a statement of IAB policy or recommendations. | July 1990 Status: INFORMATIONAL Autor: V.G. Cerf |
| RFC1168 Intermail and Commercial Mail Relay services This RFC discusses the history and evolution of the Intermail and Commercial mail systems. The problems encountered in operating a store-and-forward mail relay between commercial systems such as Telemail, MCI Mail and Dialcom are also discussed. This RFC provides information for the Internet community, and does not specify any standard. | July 1990 Status: INFORMATIONAL Autor: A. Westine, A.L. DeSchon, J. Postel, C.E. Ward |
| RFC1169 Explaining the role of GOSIP This informational RFC represents the official view of the Internet Activities Board (IAB), after coordination with the Federal Networking Council (FNC). This RFC does not specify a standard. | August 1990 Status: INFORMATIONAL Autor: V.G. Cerf, K.L. Mills |
| RFC1170 Public key standards and licenses This RFC is a public statement by Public Key Partners regarding Public Key Standards and Licenses. This memo is for informational use only, and does not constitute an Internet standard. | January 1991 Status: INFORMATIONAL Autor: R.B. Fougner |
| RFC1171 Point-to-Point Protocol for the transmission of multi-protocol datagrams over Point-to-Point links This memo specifies the Point-to-Point Protocol (PPP) as a Draft Standard Protocol for the Internet community. When it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links. | July 1990 Status: DRAFT STANDARD Autor: D. Perkins |
| RFC1172 Point-to-Point Protocol (PPP) initial configuration options This memo specifies the Point-to-Point Protocol (PPP) Initial Configuration Options as a Proposed Standard Protocol for the Internet community. When it becomes a full Standard, this protocol will be recommended for all TCP/IP implementations that communicate over serial links. | July 1990 Status: PROPOSED STANDARD Autor: D. Perkins, R. Hobby |
| RFC1173 Responsibilities of host and network managers: A summary of the "oral tradition" of the Internet This informational RFC describes the conventions to be followed by those in charge of networks and hosts in the Internet. It is a summary of the "oral tradition" of the Internet on this subject. [RFC Editor's note: This memo is a contribution by the author of his view of these conventions. It is expected that this RFC will provide a basis for the development of official policies in the future.] These conventions may be supplemented or amended by the policies of specific local and regional components of the Internet. This RFC does not specify a standard, or a policy of the IAB. | August 1990 Status: INFORMATIONAL Autor: J. VanBokkelen |
| RFC1174 IAB recommended policy on distributing internet identifier assignment and IAB recommended policy change to internet "connected" status This informational RFC represents the official view of the Internet Activities Board (IAB), and describes the recommended policies and procedures on distributing Internet identifier assignments and dropping the connected status requirement. This RFC does not specify a standard. | August 1990 Status: INFORMATIONAL Autor: V.G. Cerf |
| RFC1175 FYI on where to start: A bibliography of internetworking information This FYI RFC is a bibliography of information about TCP/IP internetworking, prepared by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify any standard. [Also FYI 3.] | August 1990 Status: INFORMATIONAL Autor: K.L. Bowers, T.L. LaQuey, J.K. Reynolds, K. Roubicek, M.K. Stahl, A. Yuan |
| RFC1176 Interactive Mail Access Protocol: Version 2 This RFC suggests a method for personal computers and workstations to dynamically access mail from a mailbox server ("repository"). It obosoletes RFC 1064. This RFC specifies an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. | August 1990 Status: EXPERIMENTAL Autor: M.R. Crispin |
| RFC1177 FYI on Questions and Answers: Answers to commonly asked "new internet user" questions This FYI RFC is one of three FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group (USWG) of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 4.] | August 1990 Status: INFORMATIONAL Autor: G.S. Malkin, A.N. Marine, J.K. Reynolds |
| RFC1178 Choosing a name for your computer This FYI RFC is a republication of a Communications of the ACM article on guidelines on what to do and what not to do when naming your computer. This memo provides information for the Internet community. It does not specify any standard. [Also FYI 5.] | August 1990 Status: INFORMATIONAL Autor: D. Libes |
| RFC1179 Line printer daemon protocol This RFC describes an existing print server protocol widely used on the Internet for communicating between line printer daemons (both clients and servers). This memo is for informational purposes only, and does not specify an Internet standard. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. | August 1990 Status: INFORMATIONAL Autor: L. McLaughlin |
| RFC1180 TCP/IP tutorial This RFC is a tutorial on the TCP-IP protocol suite, focusing particularly on the steps in forwarding an IP datagram from source host to destination host through a router. It does not specify an Internet standard. | January 1991 Status: INFORMATIONAL Autor: T.J. Socolofsky, C.J. Kale |
| RFC1181 RIPE Terms of Reference This RFC describes the Terms of Reference of RIPE (Reseaux IP Europeens), the cooperation of European IP networks. This memo provides information for the Internet community. It does not specify any standard. | September 1990 Status: INFORMATIONAL Autor: R. Blokzijl |
| RFC1183 New DNS RR Definitions This memo defines five new DNS types for experimental purposes. This RFC describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. | October 1990 Status: EXPERIMENTAL Autor: C.F. Everhart, L.A. Mamakos, R. Ullmann, P.V. Mockapetris |
| RFC1184 Telnet Linemode Option This RFC specifies a procedure for line at a time terminal interaction based on the Telnet Protocol. It obsoletes RFC 1116. [STANDARDS-TRACK] | October 1990 Status: DRAFT STANDARD Autor: D.A. Borman |
| RFC1185 TCP Extension for High-Speed Paths This memo describes an Experimental Protocol extension to TCP for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. | October 1990 Status: EXPERIMENTAL Autor: V. Jacobson, R.T. Braden, L. Zhang |
| RFC1186 MD4 Message Digest Algorithm This RFC is the specification of the MD4 Digest Algorithm. If you are going to implement MD4, it is suggested you do it this way. This memo is for informational use and does not constitute a standard. | October 1990 Status: INFORMATIONAL Autor: R.L. Rivest |
| RFC1187 Bulk Table Retrieval with the SNMP This memo reports an interesting family of algorithms for bulk table retrieval using the Simple Network Management Protocol (SNMP). This memo describes an Experimental Protocol for the Internet community, and requests discussion and suggestions for improvements. This memo does not specify a standard for the Internet community. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. | October 1990 Status: EXPERIMENTAL Autor: M.T. Rose, K. McCloghrie, J.R. Davin |
| RFC1188 Proposed Standard for the Transmission of IP Datagrams over FDDI Networks This memo defines a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] | October 1990 Status: DRAFT STANDARD Autor: D. Katz |
| RFC1189 Common Management Information Services and Protocols for the Internet (CMOT and CMIP) This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in the Internet. [STANDARDS-TRACK] | October 1990 Status: HISTORIC Autor: U.S. Warrier, L. Besaw, L. LaBarre, B.D. Handspicker |
| RFC1190 Experimental Internet Stream Protocol: Version 2 (ST-II) This memo defines a revised version of the Internet Stream Protocol, originally defined in IEN-119 [8], based on results from experiments with the original version, and subsequent requests, discussion, and suggestions for improvements. This is a Limited-Use Experimental Protocol. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. | October 1990 Status: EXPERIMENTAL Autor: C. Topolcic |
| RFC1191 Path MTU discovery This memo describes a technique for dynamically discovering the maximum transmission unit (MTU) of an arbitrary internet path. It specifies a small change to the way routers generate one type of ICMP message. For a path that passes through a router that has not been so changed, this technique might not discover the correct Path MTU, but it will always choose a Path MTU as accurate as, and in many cases more accurate than, the Path MTU that would be chosen by current practice. [STANDARDS-TRACK] | November 1990 Status: DRAFT STANDARD Autor: J.C. Mogul, S.E. Deering |
| RFC1192 Commercialization of the Internet summary report This memo is based on a workshop held by the Science, Technology and Public Policy Program of the John F. Kennedy School of Government, Harvard University, March 1-3, 1990. This memo provides information for the Internet community. It does not specify any standard. | November 1990 Status: INFORMATIONAL Autor: B. Kahin |
| RFC1193 Client requirements for real-time communication services This memo describes client requirements for real-time communication services. This memo provides information for the Internet community, and requests discussion and suggestions for improvements. It does not specify any standard. | November 1990 Status: INFORMATIONAL Autor: D. Ferrari |
| RFC1194 Finger User Information Protocol This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. [STANDARDS-TRACK] | November 1990 Status: DRAFT STANDARD Autor: D.P. Zimmerman |
| RFC1195 Use of OSI IS-IS for routing in TCP/IP and dual environments This memo specifies an integrated routing protocol, based on the OSI Intra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a single routing protocol to be used to support pure IP environments, pure OSI environments, and dual environments. This specification was developed by the IS-IS working group of the Internet Engineering Task Force. [STANDARDS-TRACK] | December 1990 Status: PROPOSED STANDARD Autor: R.W. Callon |
| RFC1196 Finger User Information Protocol This memo describes the Finger User Information Protocol. This is a simple protocol which provides an interface to a remote user information program. Based on RFC 742, a description of the original Finger protocol, this memo attempts to clarify the expected communication between the two ends of a Finger connection. It also tries not to invalidate the many existing implementations or add unnecessary restrictions to the original protocol definition. This edition corrects and clarifies in a minor way, RFC 1194. [STANDARDS-TRACK] | December 1990 Status: DRAFT STANDARD Autor: D.P. Zimmerman |
| RFC1197 Using ODA for translating multimedia information The purpose of this RFC is to inform implementors of multimedia systems about our experiences using ISO 8613: Office Document Architecture (ODA). Because ODA is being proposed as an encoding format for use in multimedia mail and file exchange, implementors wishing to use ODA in an open systems environment may profit from our experiences. This memo provides information for the Internet community. It does not specify any standard. | December 1990 Status: INFORMATIONAL Autor: M. Sherman |
| RFC1198 FYI on the X window system This FYI RFC provides pointers to the published standards of the MIT X Consortium. This memo provides information for the Internet community. It does not specify any Internet standard. | January 1991 Status: INFORMATIONAL Autor: R.W. Scheifler |
| RFC1199 Request for Comments Summary Notes: 1100-1199 | December 1991 Status: INFORMATIONAL Autor: J. Reynolds |
| RFC1200 IAB official protocol standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). An overview of the standards procedures is presented first, followed by discussions of the standardization process and the RFC document series, then the explanation of the terms is presented, the lists of protocols in each stage of standardization follows, and finally pointers to references and contacts for further information. | April 1991 Status: HISTORIC Autor: Defense Advanced Research Projects Agency, Internet Activities Board |
| RFC1201 Transmitting IP traffic over ARCNET networks This memo defines a protocol for the transmission of IP and ARP packets over the ARCnet Local Area Network.This memo specifies a method of encapsulating Internet Protocol (IP) and Address Resolution Protocol (ARP) datagrams for transmission across ARCNET using the "ARCNET Packet Header Definition Standard". [STANDARDS-TRACK] | February 1991 Status: STANDARD Autor: D. Provan |
| RFC1202 Directory Assistance service This document defines a mechanism by which a user-interface may access a textual DAP-like interface over a TCP/IP connection. This is a local mechanism. This memo provides information for the Internet community. It does not specify any standard. | February 1991 Status: INFORMATIONAL Autor: M.T. Rose |
| RFC1203 Interactive Mail Access Protocol: Version 3 This RFC suggests a method for workstations to access mail dynamically from a mailbox server ("repository"). The following document is a modified version of RFC 1064, the definition of the IMAP2 protocol. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard. | February 1991 Status: HISTORIC Autor: J. Rice |
| RFC1204 Message Posting Protocol (MPP) This memo describes a protocol for posting messages from workstations (e.g., PCs) to a mail service host. This RFC specifies an Experimental Protocol for the Internet community. It does not specify any standard. | February 1991 Status: EXPERIMENTAL Autor: S. Yeh, D. Lee |
| RFC1205 5250 Telnet interface This RFC is being distributed in order to document the interface to the IBM 5250 Telnet implementation. This memo provides information for the Internet community. It does not specify any standard. | February 1991 Status: INFORMATIONAL Autor: P. Chmielewski |
| RFC1206 FYI on Questions and Answers: Answers to commonly asked "new Internet user" questions This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. [FYI 4] | February 1991 Status: INFORMATIONAL Autor: G.S. Malkin, A.N. Marine |
| RFC1207 FYI on Questions and Answers: Answers to commonly asked "experienced Internet user" questions This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify any standard. | February 1991 Status: INFORMATIONAL Autor: G.S. Malkin, A.N. Marine, J.K. Reynolds |
| RFC1208 A Glossary of Networking Terms This RFC is a glossary adapted from "The INTEROP Pocket Glossary of Networking Terms" distributed at Interop '90. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1991 Status: INFORMATIONAL Autor: O.J. Jacobsen, D.C. Lynch |
| RFC1209 The Transmission of IP Datagrams over the SMDS Service This memo defines a protocol for the transmission of IP and ARP packets over a Switched Multi-megabit Data Service Network configured as a logical IP subnetwork. [STANDARDS-TRACK] | March 1991 Status: STANDARD Autor: D. Piscitello, J. Lawrence |
| RFC1210 Network and infrastructure user requirements for transatlantic research collaboration: Brussels, July 16-18, and Washington July 24-25, 1990 This report complements a shorter printed version which appeared in a summary report of all the committees which met in Brussels and Washington last July, 1990. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1991 Status: INFORMATIONAL Autor: V.G. Cerf, P.T. Kirstein, B. Randell |
| RFC1211 Problems with the maintenance of large mailing lists This RFC discusses problems with maintaining large mailing lists, especially the processing of error reports. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1991 Status: INFORMATIONAL Autor: A. Westine, J. Postel |
| RFC1212 Concise MIB definitions This memo describes a straight-forward approach toward producing concise, yet descriptive, MIB modules. This memo defines a format for producing MIB modules. [STANDARDS-TRACK] | March 1991 Status: STANDARD Autor: M.T. Rose, K. McCloghrie |
| RFC1213 Management Information Base for Network Management of TCP/IP-based internets:MIB-II This memo defines the second version of the Management Information Base (MIB-II) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] | March 1991 Status: STANDARD Autor: K. McCloghrie, M. Rose |
| RFC1214 OSI internet management: Management Information Base This RFC documents a MIB for use with CMIP, either over pure OSI stacks or with the CMIP over TCP specification. It redefines objects comprised by the second revision of the Management Information Base for Network Management of TCP/IP-based internets: MIB-II so as to conform to the OSI structure of management information. [STANDARDS-TRACK] | April 1991 Status: HISTORIC Autor: L. LaBarre |
| RFC1215 Convention for defining traps for use with the SNMP This memo suggests a straight-forward approach towards defining traps used with the SNMP. This memo provides information for the Internet community. It does not specify any standard. | March 1991 Status: INFORMATIONAL Autor: M.T. Rose |
| RFC1216 Gigabit network economics and paradigm shifts This memo proposes a new standard paradigm for the Internet Activities Board (IAB) standardization track. [STANDARDS-TRACK] | April 1991 Status: INFORMATIONAL Autor: P. Richard, P. Kynikos |
| RFC1217 Memo from the Consortium for Slow Commotion Research (CSCR) This RFC is in response to RFC 1216, "Gigabit Network Economics and Paradigm Shifts". This memo provides information for the Internet community. It does not specify an Internet standard. | April 1991 Status: INFORMATIONAL Autor: V.G. Cerf |
| RFC1218 Naming scheme for c=US This RFC is a near-verbatim copy of a document, known as NADF-123, which has been produced by the North American Directory Forum (NADF). As a part of its charter, the NADF must reach agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1991 Status: INFORMATIONAL Autor: North American Directory Forum |
| RFC1219 On the assignment of subnet numbers This memo suggests a new procedure for assigning subnet numbers. Use of this assignment technique within a network would be a purely local matter, and would not effect other networks. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1991 Status: INFORMATIONAL Autor: P.F. Tsuchiya |
| RFC1220 Point-to-Point Protocol extensions for bridging This document defines an extension of the Internet Point-to-Point Protocol (PPP) described in RFC 1171, targeting the use of Point-to- Point lines for Remote Bridging. [STANDARDS-TRACK] | April 1991 Status: PROPOSED STANDARD Autor: F. Baker |
| RFC1221 Host Access Protocol (HAP) specification: Version 2 This memo describes the Host Access Protocol implemented in the Terrestrial Wideband Network (TWBNET). This memo provides information for the Internet community. It does not specify an Internet standard. | April 1991 Status: INFORMATIONAL Autor: W. Edmond |
| RFC1222 Advancing the NSFNET routing architecture This RFC suggests improvements in the NSFNET routing architecture to accommodate a more flexible interface to the Backbone clients. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1991 Status: INFORMATIONAL Autor: H.W. Braun, Y. Rekhter |
| RFC1223 OSI CLNS and LLC1 protocols on Network Systems HYPERchannel The intent of this document is to provide a complete discussion of the protocols and techniques used to transmit OSI CLNS and LLC1 datagrams (and any associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment.This memo provides information for the Internet community. It does not specify an Internet standard. | May 1991 Status: INFORMATIONAL Autor: J.M. Halpern |
| RFC1224 Techniques for managing asynchronously generated alerts This memo defines common mechanisms for managing asynchronously produced alerts in a manner consistent with current network management protocols. This memo specifies an Experimental Protocol for the Internet community. It does not specify an Internet standard. | May 1991 Status: EXPERIMENTAL Autor: L. Steinberg |
| RFC1225 Post Office Protocol: Version 3 This memo suggests a simple method for workstations to dynamically access mail from a mailbox server. [STANDARDS-TRACK] | May 1991 Status: DRAFT STANDARD Autor: M.T. Rose |
| RFC1226 Internet protocol encapsulation of AX.25 frames This memo describes a method for the encapsulation of AX.25 (the Amateur Packet-Radio Link-Layer Protocol) frames within IP packets. This technique is an Experimental Protocol for the Internet community. It does not specify an Internet standard. | May 1991 Status: EXPERIMENTAL Autor: B. Kantor |
| RFC1227 SNMP MUX protocol and MIB This memo suggests a mechanism by which a user process may associate itself with the local SNMP agent on a host, in order to implement portions of the MIB. This mechanism would be local to the host.This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. | May 1991 Status: HISTORIC Autor: M.T. Rose |
| RFC1228 SNMP-DPI: Simple Network Management Protocol Distributed Program Interface This RFC describes a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. | May 1991 Status: EXPERIMENTAL Autor: G. Carpenter, B. Wijnen |
| RFC1229 Extensions to the generic-interface MIB This RFC contains definitions of managed objects used as experimental extensions to the generic interfaces structure of MIB-II. [STANDARDS-TRACK] | May 1991 Status: PROPOSED STANDARD Autor: K. McCloghrie |
| RFC1230 IEEE 802.4 Token Bus MIB This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.4 Token Bus technology described in 802.4 Token-Passing Bus Access Method and Physical Layer Specifications, IEEE Standard 802.4. [STANDARDS-TRACK] | May 1991 Status: HISTORIC Autor: K. McCloghrie, R. Fox |
| RFC1231 IEEE 802.5 Token Ring MIB This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK] | May 1991 Status: PROPOSED STANDARD Autor: K. McCloghrie, R. Fox, E. Decker |
| RFC1232 Definitions of managed objects for the DS1 Interface type | May 1991 Status: PROPOSED STANDARD Autor: F. Baker, C.P. Kolb |
| RFC1233 Definitions of managed objects for the DS3 Interface type This memo defines objects for managing DS3 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK] | May 1991 Status: PROPOSED STANDARD Autor: T.A. Cox, K. Tesink |
| RFC1234 Tunneling IPX traffic through IP networks This memo describes a method of encapsulating IPX datagrams within UDP packets so that IPX traffic can travel across an IP internet. [STANDARDS-TRACK] This memo defines objects for managing DS1 Interface objects for use with the SNMP protocol. [STANDARDS-TRACK] | June 1991 Status: HISTORIC Autor: D. Provan |
| RFC1235 Coherent File Distribution Protocol This memo describes the Coherent File Distribution Protocol (CFDP). This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. | June 1991 Status: EXPERIMENTAL Autor: J. Ioannidis, G. Maguire |
| RFC1236 IP to X.121 address mapping for DDN This memo defines a standard way of converting IP addresses to CCITT X.121 addresses and is the recommended standard for use on the Internet, specifically for the Defense Data Network (DDN). This memo provides information for the Internet community. It does not specify an Internet standard. | June 1991 Status: INFORMATIONAL Autor: L. Morales, P. Hasse |
| RFC1237 Guidelines for OSI NSAP Allocation in the Internet This paper provides guidelines for allocating NSAPs in the Internet.[STANDARDS-TRACK] | July 1991 Status: PROPOSED STANDARD Autor: R. Colella, E. Gardner, R. Callon |
| RFC1238 CLNS MIB for use with Connectionless Network Protocol (ISO 8473) and End System to Intermediate System (ISO 9542) This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. This is an Experimental Protocol for the Internet community. It does not specify an Internet standard. | June 1991 Status: EXPERIMENTAL Autor: G. Satz |
| RFC1239 Reassignment of experimental MIBs to standard MIBs This memo specifically updates RFC 1229, RFC 1230, RFC 1231, RFC 1232 and RFC 1233 with new codes. [STANDARDS-TRACK] | June 1991 Status: HISTORIC Autor: J.K. Reynolds |
| RFC1240 OSI connectionless transport services on top of UDP: Version 1 This document describes a protocol for running OSI Connectionless service on UDP. [STANDARDS-TRACK] | June 1991 Status: HISTORIC Autor: C. Shue, W. Haggerty, K. Dobbins |
| RFC1241 Scheme for an internet encapsulation protocol: Version 1 This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | July 1991 Status: EXPERIMENTAL Autor: R.A. Woodburn, D.L. Mills |
| RFC1242 Benchmarking Terminology for Network Interconnection Devices This memo discusses and defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. This memo provides information for the Internet community. It does not specify an Internet standard. | July 1991 Status: INFORMATIONAL Autor: S. Bradner |
| RFC1243 AppleTalk Management Information Base This memo defines objects for managing AppleTalk objects for use with the SNMP protocol. [STANDARDS-TRACK] | July 1991 Status: PROPOSED STANDARD Autor: S. Waldbusser |
| RFC1244 Site Security Handbook This FYI RFC is a first attempt at providing Internet users guidance on how to deal with security issues in the Internet. This FYI RFC provides information for the Internet community. It does not specify an Internet standard. [FYI 8] | July 1991 Status: INFORMATIONAL Autor: J.P. Holbrook, J.K. Reynolds |
| RFC1245 OSPF Protocol Analysis This report attempts to summarize the key features of OSPF V2. It also attempts to analyze how the protocol will perform and scale in the Internet. This memo provides information for the Internet community. It does not specify any Internet standard. | July 1991 Status: INFORMATIONAL Autor: J. Moy |
| RFC1246 Experience with the OSPF Protocol This report documents experience with OSPF V2. This includes reports on interoperability testing, field experience, simulations and the current state of OSPF implementations. This memo provides information for the Internet community. It does not specify any Internet standard. | July 1991 Status: INFORMATIONAL Autor: J. Moy |
| RFC1247 OSPF Version 2 This memo documents version 2 of the OSPF protocol. OSPF is a link- state based routing protocol. [STANDARDS-TRACK] | July 1991 Status: DRAFT STANDARD Autor: J. Moy |
| RFC1248 OSPF Version 2 Management Information Base This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK] | July 1991 Status: PROPOSED STANDARD Autor: F. Baker, R. Coltun |
| RFC1249 DIXIE Protocol Specification This RFC defines a mechanism by which TCP/UDP based clients can access OSI Directory Service without the overhead of the ISO transport and presentation protocols required to implement full-blown DAP. This memo provides information for the Internet community. It does not specify any standard. | August 1991 Status: INFORMATIONAL Autor: T. Howes, M. Smith, B. Beecher |
| RFC1250 IAB Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard. | August 1991 Status: HISTORIC Autor: J. Postel |
| RFC1251 Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 9] | August 1991 Status: INFORMATIONAL Autor: G. Malkin |
| RFC1252 OSPF Version 2 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK] | August 1991 Status: PROPOSED STANDARD Autor: F. Baker, R. Coltun |
| RFC1253 OSPF Version 2 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK] | August 1991 Status: PROPOSED STANDARD Autor: F. Baker, R. Coltun |
| RFC1254 Gateway Congestion Control Survey The purpose of this paper is to present a review of the congestion control approaches, as a way of encouraging new discussion and experimentation. Included in the survey are Source Quench, Random Drop, Congestion Indication (DEC Bit), and Fair Queueing. | August 1991 Status: INFORMATIONAL Autor: A. Mankin, K. Ramakrishnan |
| RFC1255 A Naming Scheme for c=US This memo documents the NADF's agreement as to how entries are named in the public portions of the North American Directory. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1991 Status: INFORMATIONAL Autor: The North American Directory Forum |
| RFC1256 ICMP Router Discovery Messages This document specifies an extension of the Internet Control Message Protocol (ICMP) to enable hosts attached to multicast or broadcast networks to discover the IP addresses of their neighboring routers. [STANDARDS-TRACK] | September 1991 Status: PROPOSED STANDARD Autor: S. Deering |
| RFC1257 Isochronous applications do not require jitter-controlled networks This memo argues that jitter control is not required for networks to support isochronous applications. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1991 Status: INFORMATIONAL Autor: C. Partridge |
| RFC1258 BSD Rlogin The rlogin facility provides a remote-echoed, locally flow-controlled virtual terminal with proper flushing of output.This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1991 Status: INFORMATIONAL Autor: B. Kantor |
| RFC1259 Building the open road: The NREN as test-bed for the national public network This memo discusses the background and importance of NREN. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1991 Status: INFORMATIONAL Autor: M. Kapor |
| RFC1261 Transition of Nic Services This memo outlines the transition of NIC Services. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1991 Status: INFORMATIONAL Autor: S. Williamson, L. Nobile |
| RFC1262 Guidelines for Internet Measurement Activities This RFC represents IAB guidance for researchers considering measurement experiments on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1991 Status: INFORMATIONAL Autor: V.G. Cerf |
| RFC1263 TCP Extensions Considered Harmful This RFC comments on recent proposals to extend TCP. It argues that the backward compatible extensions proposed in RFC's 1072 and 1185 should not be pursued, and proposes an alternative way to evolve the Internet protocol suite. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1991 Status: INFORMATIONAL Autor: S. O'Malley, L.L. Peterson |
| RFC1264 Internet Engineering Task Force Internet Routing Protocol Standardization Criteria This informational RFC presents procedures for creating and documenting Internet standards on routing protocols. These procedures have been established by the Internet Activities Board (IAB) in consultation with the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. It does not specifiy an Internet standard. | October 1991 Status: HISTORIC Autor: R.M. Hinden |
| RFC1265 BGP Protocol Analysis This report summarizes the key feature of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1991 Status: INFORMATIONAL Autor: Y. Rekhter |
| RFC1266 Experience with the BGP Protocol The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol (BGP). This memo provides information for the Internet community. It does not specify an Internet standard. | October 1991 Status: INFORMATIONAL Autor: Y. Rekhter |
| RFC1267 Border Gateway Protocol 3 (BGP-3) This memo, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] | October 1991 Status: HISTORIC Autor: K. Lougheed, Y. Rekhter |
| RFC1268 Application of the Border Gateway Protocol in the Internet This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK] | October 1991 Status: HISTORIC Autor: Y. Rekhter, P. Gross |
| RFC1269 Definitions of Managed Objects for the Border Gateway Protocol: Version 3 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Border Gateway Protocol. [STANDARDS-TRACK] | October 1991 Status: PROPOSED STANDARD Autor: S. Willis, J.W. Burruss |
| RFC1270 SNMP Communications Services This document discusses various issues to be considered when determining the underlying communications services to be used by an SNMP implementation. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1991 Status: INFORMATIONAL Autor: F. Kastenholz |
| RFC1271 Remote Network Monitoring Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK] | November 1991 Status: PROPOSED STANDARD Autor: S. Waldbusser |
| RFC1272 Internet Accounting: Background This document provides background information for the "Internet Accounting Architecture". This memo provides information for the Internet community. It does not specify an Internet standard. | November 1991 Status: INFORMATIONAL Autor: C. Mills, D. Hirsh, G.R. Ruth |
| RFC1273 Measurement Study of Changes in Service-Level Reachability in the Global TCP/IP Internet: Goals, Experimental Design, Implementation, and Policy Considerations This memo describes plans to carry out a longitudinal measurement study of changes in service-level reachability in the global TCP/IP Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | November 1991 Status: INFORMATIONAL Autor: M.F. Schwartz |
| RFC1274 The COSINE and Internet X.500 Schema This document suggests an X.500 Directory Schema, or Naming Architecture, for use in the COSINE and Internet X.500 pilots. [STANDARDS-TRACK] | November 1991 Status: PROPOSED STANDARD Autor: P. Barker, S. Kille |
| RFC1275 Replication Requirements to provide an Internet Directory using X.500 This RFC considers certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective open Internet Directory can be established using these protocols and services [CCI88]. This memo provides information for the Internet community. It does not specify an Internet standard. | November 1991 Status: INFORMATIONAL Autor: S.E. Hardcastle-Kille |
| RFC1276 Replication and Distributed Operations extensions to provide an Internet Directory using X.500 Some requirements on extensions to X.500 are described in the RFC[HK91b], in order to build an Internet Directory using X.500(1988). This document specifies a set of solutions to the problems raised. [STANDARDS-TRACK] | November 1991 Status: HISTORIC Autor: S.E. Hardcastle-Kille |
| RFC1277 Encoding Network Addresses to Support Operation over Non-OSI Lower Layers This document defines a new network address format, and rules for using some existing network address formats. [STANDARDS-TRACK] | November 1991 Status: PROPOSED STANDARD Autor: S.E. Hardcastle-Kille |
| RFC1278 A string encoding of Presentation Address There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. This memo provides information for the Internet community. It does not specify an Internet standard. | November 1991 Status: INFORMATIONAL Autor: S.E. Hardcastle-Kille |
| RFC1279 X.500 and Domains This RFC considers X.500 in relation to Internet and UK Domains. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | November 1991 Status: EXPERIMENTAL Autor: S.E. Hardcastle-Kille |
| RFC1280 IAB Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). This memo provides information for the Internet community. It does not specify an Internet standard. | March 1992 Status: HISTORIC Autor: J. Postel |
| RFC1281 Guidelines for the Secure Operation of the Internet The purpose of this document is to provide a set of guidelines to aid in the secure operation of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | November 1991 Status: INFORMATIONAL Autor: R. Pethia, S. Crocker, B. Fraser |
| RFC1282 BSD Rlogin This memo documents an existing protocol and common implementation that is extensively used on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | December 1991 Status: INFORMATIONAL Autor: B. Kantor |
| RFC1283 SNMP over OSI This memo describes mappings from the SNMP onto both the COTS and the CLTS. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet Standard. | December 1991 Status: EXPERIMENTAL Autor: M. Rose |
| RFC1284 Definitions of Managed Objects for the Ethernet-like Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK] | December 1991 Status: PROPOSED STANDARD Autor: J. Cook |
| RFC1285 FDDI Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI. [STANDARDS-TRACK] | January 1992 Status: HISTORIC Autor: J. Case |
| RFC1286 Definitions of Managed Objects for Bridges This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing bridges based on the IEEE 802.1d draft standard between Local Area Network (LAN) segments. This memo is an extension to the SNMP MIB. [STANDARDS-TRACK] | December 1991 Status: PROPOSED STANDARD Autor: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie |
| RFC1287 Towards the Future Internet Architecture This informational RFC discusses important directions for possible future evolution of the Internet architecture, and suggests steps towards the desired goals. This memo provides information for the Internet community. It does not specify an Internet standard. | December 1991 Status: INFORMATIONAL Autor: D. Clark, L. Chapin, V. Cerf, R. Braden, R. Hobby |
| RFC1288 The Finger User Information Protocol This memo describes the Finger user information protocol.This is a simple protocol which provides an interface to a remote user information program. [STANDARDS-TRACK] | December 1991 Status: DRAFT STANDARD Autor: D. Zimmerman |
| RFC1289 DECnet Phase IV MIB Extensions This memo is an extension to the SNMP MIB. This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. [STANDARDS-TRACK] | December 1991 Status: PROPOSED STANDARD Autor: J. Saperia |
| RFC1290 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places This paper will present some of the "gold nuggets" of information and file repositories on the network that could be of use to end users. This RFC provides information for the Internet community. It does not specify an Internet standard. | December 1991 Status: INFORMATIONAL Autor: J. Martin |
| RFC1291 Mid-Level Networks Potential Technical Services This document proposes a set of technical services that each Internet mid-level network can offer within the mid-level network itself and and to its peer networks. This RFC provides information for the Internet community. It does not specify an Internet standard. | December 1991 Status: INFORMATIONAL Autor: V. Aggarwal |
| RFC1292 A Catalog of Available X.500 Implementations The goal of this document is to provide information regarding the availability and capability of implementations of X.500. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1992 Status: INFORMATIONAL Autor: R. Lang, R. Wright |
| RFC1293 Inverse Address Resolution Protocol This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK] | January 1992 Status: PROPOSED STANDARD Autor: T. Bradley, C. Brown |
| RFC1294 Multiprotocol Interconnect over Frame Relay This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK] | January 1992 Status: PROPOSED STANDARD Autor: T. Bradley, C. Brown, A. Malis |
| RFC1295 User Bill of Rights for entries and listings in the Public Directory This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) objects. This document is a companion document with Definitions of Managed Objects for the DS1/E1 and DS3/E3 Interface Types, RFC1406 and RFC1407. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1992 Status: INFORMATIONAL Autor: The North American Directory Forum |
| RFC1296 Internet Growth (1981-1991) This document illustrates the growth of the Internet by examination of entries in the Domain Name System (DNS) and pre-DNS host tables. This memo provides information for the Internet community. It does not specify an Internet standard. This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. [STANDARDS-TRACK] | January 1992 Status: INFORMATIONAL Autor: M. Lottor |
| RFC1297 NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS") This document explores competing uses, architectures, and desirable features of integrated internal trouble ticket systems for Network and other Operations Centers. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1992 Status: INFORMATIONAL Autor: D. Johnson |
| RFC1298 SNMP over IPX This memo defines a convention for encapsulating Simple Network Management Protocol (SNMP) packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1992 Status: INFORMATIONAL Autor: R. Wormley, S. Bostock |
| RFC1299 Summary of 1200-1299 | January 1997 Status: INFORMATIONAL Autor: M. Kennedy |
| RFC1300 Remembrances of Things Past Poem. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1992 Status: INFORMATIONAL Autor: S. Greenfield |
| RFC1301 Multicast Transport Protocol This memo describes a protocol for reliable transport that utilizes the multicast capability of applicable lower layer networking architectures. The transport definition permits an arbitrary number of transport providers to perform realtime collaborations without requiring networking clients (aka, applications) to possess detailed knowledge of the population or geographical dispersion of the participating members. It is not network architectural specific, but does implicitly require some form of multicasting (or broadcasting) at the data link level, as well as some means of communicating that capability up through the layers to the transport. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1992 Status: INFORMATIONAL Autor: S. Armstrong, A. Freier, K. Marzullo |
| RFC1302 Building a Network Information Services Infrastructure This FYI RFC document is intended for existing Internet Network Information Center (NIC) personnel, people interested in establishing a new NIC, Internet Network Operations Centers (NOCs), and funding agencies interested in contributing to user support facilities. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1992 Status: INFORMATIONAL Autor: D. Sitzler, P. Smith, A. Marine |
| RFC1303 A Convention for Describing SNMP-based Agents This memo suggests a straight-forward approach towards describing SNMP- based agents. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1992 Status: INFORMATIONAL Autor: K. McCloghrie, M. Rose |
| RFC1304 Definitions of Managed Objects for the SIP Interface Type This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing SIP (SMDS Interface Protocol) objects. [STANDARDS-TRACK] | February 1992 Status: PROPOSED STANDARD Autor: T. Cox, K. Tesink |
| RFC1305 Network Time Protocol (Version 3) Specification, Implementation and Analysis This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. [STANDARDS-TRACK] | March 1992 Status: DRAFT STANDARD Autor: D. Mills |
| RFC1306 Experiences Supporting By-Request Circuit-Switched T3 Networks This memo describes the experiences of a project team at Cray Research, Inc., in implementing support for circuit-switched T3 services. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementers. This RFC provides information for the Internet community. It does not specify an Internet standard. | March 1992 Status: INFORMATIONAL Autor: A. Nicholson, J. Young |
| RFC1307 Dynamically Switched Link Control Protocol This memo describes an experimental protocol developed by a project team at Cray Research, Inc., in implementing support for circuit-switched T3 services. The protocol is used for the control of network connections external to a host, but known to the host. This memo defines an Experimental Protocol for the Internet community. | March 1992 Status: EXPERIMENTAL Autor: J. Young, A. Nicholson |
| RFC1308 Executive Introduction to Directory Services Using the X.500 Protocol This document is an Executive Introduction to Directory Services using the X.500 protocol. It briefly discusses the deficiencies in currently deployed Internet Directory Services, and then illustrates the solutions provided by X.500. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1992 Status: INFORMATIONAL Autor: C. Weider, J. Reynolds |
| RFC1309 Technical Overview of Directory Services Using the X.500 Protocol This document is an overview of the X.500 standard for people not familiar with the technology. It compares and contrasts Directory Services based on X.500 with several of the other Directory services currently in use in the Internet. This paper also describes the status of the standard and provides references for further information on X.500 implementations and technical information. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1992 Status: INFORMATIONAL Autor: C. Weider, J. Reynolds, S. Heker |
| RFC1310 The Internet Standards Process This memo documents the process currently used for the standardization of Internet protocols and procedures. [STANDARDS-TRACK] | March 1992 Status: INFORMATIONAL Autor: L. Chapin |
| RFC1311 Introduction to the STD Notes The STDs are a subseries of notes within the RFC series that are the Internet standards. The intent is to identify clearly for the Internet community those RFCs which document Internet standards. [STANDARDS-TRACK] | March 1992 Status: INFORMATIONAL Autor: J. Postel |
| RFC1312 Message Send Protocol 2 The Message Send Protocol is used to send a short message to a given user on a given terminal on a given host. This memo defines an Experimental Protocol for the Internet community. | April 1992 Status: EXPERIMENTAL Autor: R. Nelson, G. Arnold |
| RFC1313 Today's Programming for KRFC AM 1313 Internet Talk Radio Hi and welcome to KRFC Internet Talk Radio, your place on the AM dial for lively talk and just-breaking news on internetworking. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1992 Status: INFORMATIONAL Autor: C. Partridge |
| RFC1314 A File Format for the Exchange of Images in the Internet This document defines a standard file format for the exchange of fax- like black and white images within the Internet. [STANDARDS-TRACK] | April 1992 Status: HISTORIC Autor: A. Katz, D. Cohen |
| RFC1315 Management Information Base for Frame Relay DTEs This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Frame Relay. [STANDARDS-TRACK] | April 1992 Status: PROPOSED STANDARD Autor: C. Brown, F. Baker, C. Carvalho |
| RFC1316 Definitions of Managed Objects for Character Stream Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for the management of character stream devices. [STANDARDS-TRACK] | April 1992 Status: PROPOSED STANDARD Autor: B. Stewart |
| RFC1317 Definitions of Managed Objects for RS-232-like Hardware Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK] | April 1992 Status: PROPOSED STANDARD Autor: B. Stewart |
| RFC1318 Definitions of Managed Objects for Parallel-printer-like Hardware Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for the management of parallel-printer- like devices. [STANDARDS-TRACK] | April 1992 Status: PROPOSED STANDARD Autor: B. Stewart |
| RFC1319 The MD2 Message-Digest Algorithm This document describes the MD2 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1992 Status: HISTORIC Autor: B. Kaliski |
| RFC1320 The MD4 Message-Digest Algorithm This document describes the MD4 message-digest algorithm [1]. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1992 Status: HISTORIC Autor: R. Rivest |
| RFC1321 The MD5 Message-Digest Algorithm This document describes the MD5 message-digest algorithm. The algorithm takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1992 Status: INFORMATIONAL Autor: R. Rivest |
| RFC1322 A Unified Approach to Inter-Domain Routing This memo is an informational RFC which outlines one potential approach for inter-domain routing in future global internets. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: D. Estrin, Y. Rekhter, S. Hotz |
| RFC1323 TCP Extensions for High Performance This memo presents a set of TCP extensions to improve performance over large bandwidth*delay product paths and to provide reliable operation over very high-speed paths. It defines new TCP options for scaled windows and timestamps, which are designed to provide compatible interworking with TCP's that do not implement the extensions. [STANDARDS-TRACK] | May 1992 Status: PROPOSED STANDARD Autor: V. Jacobson, R. Braden, D. Borman |
| RFC1324 A Discussion on Computer Network Conferencing This memo is intended to make more people aware of the present developments in the Computer Conferencing field as well as put forward ideas on what should be done to formalize this work so that there is a common standard for programmers and others who are involved in this field to work with. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: D. Reed |
| RFC1325 FYI on Questions and Answers Answers to Commonly asked "New Internet User" Questions This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), produced by the User Services Working Group of the Internet Engineering Task Force (IETF). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: G. Malkin, A. Marine |
| RFC1326 Mutual Encapsulation Considered Dangerous This memo describes a packet explosion problem that can occur with mutual encapsulation of protocols (A encapsulates B and B encapsulates A). This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: P. Tsuchiya |
| RFC1327 Mapping between X.400(1988) / ISO 10021 and RFC 822 This document specifies a mapping between two protocols. This specification should be used when this mapping is performed on the DARPA Internet or in the UK Academic Community. This specification may be modified in the light of implementation experience, but no substantial changes are expected. [STANDARDS-TRACK] | May 1992 Status: PROPOSED STANDARD Autor: S. Hardcastle-Kille |
| RFC1328 X.400 1988 to 1984 downgrading This document considers issues of downgrading from X.400(1988) to X.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies some downgrading rules [MHS88b], but these are not sufficient for provision of service in an environment containing both 1984 and 1988 components. This document defines a number of extensions to this annexe. [STANDARDS-TRACK] | May 1992 Status: HISTORIC Autor: S. Hardcastle-Kille |
| RFC1329 Thoughts on Address Resolution for Dual MAC FDDI Networks In this document an idea is submitted how IP and ARP can be used on inhomogeneous FDDI networks (FDDI networks with single MAC and dual MAC stations) by introducing a new protocol layer in the protocol suite of the dual MAC stations. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: P. Kuehn |
| RFC1330 Recommendations for the Phase I Deployment of OSI Directory Services (X.500) and OSI Message Handling Services (X.400) within the ESNET Community This RFC is a near verbatim copy of the whitepaper produced by the ESnet Site Coordinating Committee's X.500/X.400 Task Force. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: ESCC X.500/X.400 Task Force, ESnet Site Coordinating Comittee (ESCC), Energy Sciences Network (ESnet) |
| RFC1331 The Point-to-Point Protocol (PPP) for the Transmission of Multi-protocol Datagrams over Point-to-Point Links This document defines the PPP encapsulation scheme, together with the PPP Link Control Protocol (LCP), an extensible option negotiation protocol which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK] | May 1992 Status: PROPOSED STANDARD Autor: W. Simpson |
| RFC1332 The PPP Internet Protocol Control Protocol (IPCP) The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. [STANDARDS-TRACK] | May 1992 Status: PROPOSED STANDARD Autor: G. McGregor |
| RFC1333 PPP Link Quality Monitoring The Point-to-Point Protocol (PPP) [1] provides a standard method of encapsulating Network Layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of a Quality Protocol for continuous monitoring of the viability of the link. [STANDARDS-TRACK] | May 1992 Status: PROPOSED STANDARD Autor: W. Simpson |
| RFC1334 PPP Authentication Protocols This document defines two protocols for Authentication: the Password Authentication Protocol and the Challenge-Handshake Authentication Protocol. [STANDARDS-TRACK] | October 1992 Status: PROPOSED STANDARD Autor: B. Lloyd, W. Simpson |
| RFC1335 A Two-Tier Address Structure for the Internet: A Solution to the Problem of Address Space Exhaustion This RFC presents a solution to problem of address space exhaustion in the Internet. It proposes a two-tier address structure for the Internet. This is an "idea" paper and discussion is strongly encouraged. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: Z. Wang, J. Crowcroft |
| RFC1336 Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members This FYI RFC contains biographical information about members of the Internet Activities Board (IAB), the Internet Engineering Steering Group (IESG) of the Internet Engineering Task Force (IETF), and the the Internet Research Steering Group (IRSG) of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify any standard. | May 1992 Status: INFORMATIONAL Autor: G. Malkin |
| RFC1337 TIME-WAIT Assassination Hazards in TCP This note describes some theoretically-possible failure modes for TCP connections and discusses possible remedies. In particular, one very simple fix is identified. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1992 Status: INFORMATIONAL Autor: R. Braden |
| RFC1338 Supernetting: an Address Assignment and Aggregation Strategy This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers run by transit routing domain providers. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1992 Status: INFORMATIONAL Autor: V. Fuller, T. Li, J. Yu, K. Varadhan |
| RFC1339 Remote Mail Checking Protocol This RFC defines a protocol to provide a mail checking service to be used between a client and server pair. Typically, a small program on a client workstation would use the protocol to query a server in order to find out whether new mail has arrived for a specified user. This memo defines an Experimental Protocol for the Internet community. | June 1992 Status: EXPERIMENTAL Autor: S. Dorner, P. Resnick |
| RFC1340 Assigned Numbers This Network Working Group Request for Comments documents the currently assigned values from several series of numbers used in network protocol implementations. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. | July 1992 Status: HISTORIC Autor: J. Reynolds, J. Postel |
| RFC1341 MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. [STANDARDS-TRACK] | June 1992 Status: PROPOSED STANDARD Autor: N. Borenstein, N. Freed |
| RFC1342 Representation of Non-ASCII Text in Internet Message Headers This memo describes an extension to the message format defined in [1] (known to the IETF Mail Extensions Working Group as "RFC 1341"), to allow the representation of character sets other than ASCII in RFC 822 message headers. [STANDARDS-TRACK] | June 1992 Status: PROPOSED STANDARD Autor: K. Moore |
| RFC1343 A User Agent Configuration Mechanism for Multimedia Mail Format Information This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1992 Status: INFORMATIONAL Autor: N. Borenstein |
| RFC1344 Implications of MIME for Internet Mail Gateways While MIME was carefully designed so that it does not require any changes to Internet electronic message transport facilities, there are several ways in which message transport systems may want to take advantage of MIME. These opportunities are the subject of this memo. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1992 Status: INFORMATIONAL Autor: N. Borenstein |
| RFC1345 Character Mnemonics and Character Sets This memo lists a selection of characters and their presence in some coded character sets. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1992 Status: INFORMATIONAL Autor: K. Simonsen |
| RFC1346 Resource Allocation, Control, and Accounting for the Use of Network Resources The purpose of this RFC is to focus discussion on particular challenges in large service networks in general, and the International IP Internet in particular. No solution discussed in this document is intended as a standard. Rather, it is hoped that a general consensus will emerge as to the appropriate solutions, leading eventually to the adoption of standards. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1992 Status: INFORMATIONAL Autor: P. Jones |
| RFC1347 TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing This paper describes a simple proposal which provides a long-term solution to Internet addressing, routing, and scaling. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1992 Status: INFORMATIONAL Autor: R. Callon |
| RFC1348 DNS NSAP RRs This RFC defines the format of two new Resource Records (RRs) for the Domain Name System (DNS), and reserves corresponding DNS type mnemonic and numerical codes. This memo defines an Experimental Protocol for the Internet community. | July 1992 Status: EXPERIMENTAL Autor: B. Manning |
| RFC1349 Type of Service in the Internet Protocol Suite This memo changes and clarifies some aspects of the semantics of the Type of Service octet in the Internet Protocol (IP) header. [STANDARDS-TRACK] | July 1992 Status: PROPOSED STANDARD Autor: P. Almquist |
| RFC1350 The TFTP Protocol (Revision 2) TFTP is a very simple protocol used to transfer files. It is from this that its name comes, Trivial File Transfer Protocol or TFTP. Each nonterminal packet is acknowledged separately. This document describes the protocol and its types of packets. The document also explains the reasons behind some of the design decisions. [STANDARDS-TRACK] | July 1992 Status: STANDARD Autor: K. Sollins |
| RFC1351 SNMP Administrative Model This memo presents an elaboration of the SNMP administrative model set forth in [1]. This model provides a unified conceptual basis for administering SNMP protocol entities to support: authenticaiton and integrity, privacy, access control, and cooperation of protocol entities. [STANDARDS-TRACK] | July 1992 Status: HISTORIC Autor: J. Davin, J. Galvin, K. McCloghrie |
| RFC1352 SNMP Security Protocols The Simple Network Management Protocol (SNMP) specification [1] allows for the protection of network management operations by a variety of security protocols. The SNMP administrative model described in [2] provides a framework for securing SNMP network management. In the context of that framework, this memo defines protocols to support the following three security services: data integrity, data origin authentication and data confidentiality. [STANDARDS-TRACK] | July 1992 Status: HISTORIC Autor: J. Galvin, K. McCloghrie, J. Davin |
| RFC1353 Definitions of Managed Objects for Administration of SNMP Parties This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes a representation of the SNMP parties defined in [8] as objects defined according to the Internet Standard SMI [1]. [STANDARDS-TRACK] | July 1992 Status: HISTORIC Autor: K. McCloghrie, J. Davin, J. Galvin |
| RFC1354 IP Forwarding Table MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing routes in the IP Internet. [STANDARDS-TRACK] | July 1992 Status: PROPOSED STANDARD Autor: F. Baker |
| RFC1355 Privacy and Accuracy Issues in Network Information Center Databases This document provides a set of guidelines for the administration and operation of public Network Information Center (NIC) databases. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1992 Status: INFORMATIONAL Autor: J. Curran, A. Marine |
| RFC1356 Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode This document specifies the encapsulation of IP and other network layer protocols over X.25 networks, in accordance and alignment with ISO/IEC and CCITT standards. It is a replacement for RFC 877, "A Standard for the Transmission of IP Datagrams Over Public Data Networks" [1]. [STANDARDS-TRACK] | August 1992 Status: DRAFT STANDARD Autor: A. Malis, D. Robinson, R. Ullmann |
| RFC1357 A Format for E-mailing Bibliographic Records This memo defines a format for E-mailing bibliographic records of technical reports. It is intended to accelerate the dissemination of information about new Computer Science Technical Reports (CS-TR). This memo provides information for the Internet community. It does not specify an Internet standard. | July 1992 Status: INFORMATIONAL Autor: D. Cohen |
| RFC1358 Charter of the Internet Architecture Board (IAB) The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1992 Status: INFORMATIONAL Autor: L. Chapin |
| RFC1359 Connecting to the Internet - What Connecting Institutions Should Anticipate This FYI RFC outlines the major issues an institution should consider in the decision and implementation of a campus connection to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1992 Status: INFORMATIONAL Autor: ACM SIGUCCS |
| RFC1360 IAB Official Protocol Standards | September 1992 Status: HISTORIC Autor: J. Postel |
| RFC1361 Simple Network Time Protocol (SNTP) This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memorandum does not obsolete or update any RFC. This memo provides information for the Internet community. It does not specify an Internet standard. Discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.9 contain the lists of protocols in each stage of standardization. Finally come pointers to references and contacts for further information. [STANDARDS-TRACK] | August 1992 Status: INFORMATIONAL Autor: D. Mills |
| RFC1362 Novell IPX over Various WAN Media (IPXWAN) This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1992 Status: INFORMATIONAL Autor: M. Allen |
| RFC1363 A Proposed Flow Specification | September 1992 Status: INFORMATIONAL Autor: C. Partridge |
| RFC1364 BGP OSPF Interaction | September 1992 Status: PROPOSED STANDARD Autor: K. Varadhan |
| RFC1365 An IP Address Extension Proposal | September 1992 Status: INFORMATIONAL Autor: K. Siyan |
| RFC1366 Guidelines for Management of IP Address Space This document has been reviewed by the Federal Engineering Task Force (FEPG) on behalf of the Federal Networking Council (FNC), the co-chairs of the International Engineering Planning Group (IEPG), and the Reseaux IP Europeens (RIPE). There was general consensus by those groups to support the recommendations proposed in this document for management of the IP address space. This memo provides information for the Internet community. It does not specify an Internet standard. This RFC suggests an extension to the IP protocol to solve the shortage of IP address problem, and requests discussion and suggestions for improvements. This memo provides information for the Internet community. It does not specify an Internet standard. This memo defines the various criteria to be used when designing Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] 1363 Partridge Spt 92 A Proposed Flow Specification The flow specification defined in this memo is intended for information and possible experimentation (i.e., experimental use by consenting routers and applications only). This RFC is a product of the Internet Research Task Force (IRTF). This memo provides information for the Internet community. It does not specify an Internet standard. | October 1992 Status: INFORMATIONAL Autor: E. Gerich |
| RFC1367 Schedule for IP Address Space Management Guidelines This memo suggests a schedule for the implementation of the IP network number allocation plan described in RFC 1366. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1992 Status: INFORMATIONAL Autor: C. Topolcic |
| RFC1368 Definition of Managed Objects for IEEE 802.3 Repeater Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes referred to as "hubs". [STANDARDS-TRACK] | October 1992 Status: PROPOSED STANDARD Autor: D. McMaster, K. McCloghrie |
| RFC1369 Implementation Notes and Experience for the Internet Ethernet MIB This document reflects the currently known status of 11 different implementations of the MIB by 7 different vendors on 7 different Ethernet interface chips. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1992 Status: INFORMATIONAL Autor: F. Kastenholz |
| RFC1370 Applicability Statement for OSPF This Applicability Statement places a requirement on vendors claiming conformance to this standard, in order to assure that users will have the option of deploying OSPF when they need a multivendor, interoperable IGP in their environment. [STANDARDS-TRACK] | October 1992 Status: HISTORIC Autor: Internet Architecture Board, L. Chapin |
| RFC1371 Choosing a Common IGP for the IP Internet This memo presents motivation, rationale and other surrounding background information leading to the IESG's recommendation to the IAB for a single "common IGP" for the IP portions of the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1992 Status: INFORMATIONAL Autor: P. Gross |
| RFC1372 Telnet Remote Flow Control Option This document specifies an extended version of the Telnet Remote Flow Control Option, RFC 1080, with the addition of the RESTART-ANY and RESTART-XON suboptions. [STANDARDS-TRACK] | October 1992 Status: PROPOSED STANDARD Autor: C. Hedrick, D. Borman |
| RFC1373 Portable DUAs This document comes in two parts. The first part is for regular people who wish to set up their own DUAs (Directory User Interfaces) to access the Directory. The second part is for ISODE-maintainers wishing to provide portable DUAs to users. This part gives instructions in a similar but longer, step-by-step format. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1992 Status: INFORMATIONAL Autor: T. Tignor |
| RFC1374 IP and ARP on HIPPI The ANSI X3T9.3 committee has drafted a proposal for the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. Another X3T9.3 draft describes the operation of HIPPI physical switches. X3T9.3 chose to leave HIPPI networking issues largely outside the scope of their standards; this document discusses methods of using of ANSI standard HIPPI hardware and protocols in the context of the Internet, including the use of HIPPI switches as LANs and interoperation with other networks. This memo is intended to become an Internet Standard. [STANDARDS-TRACK] | October 1992 Status: PROPOSED STANDARD Autor: J. Renwick, A. Nicholson |
| RFC1375 Suggestion for New Classes of IP Addresses This RFC suggests a change in the method of specifying the IP address to add new classes of networks to be called F, G, H, and K, to reduce the amount of wasted address space, and to increase the available IP address number space, especially for smaller organizations or classes of connectors that do not need or do not want a full Class C IP address. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1992 Status: INFORMATIONAL Autor: P. Robinson |
| RFC1376 The PPP DECnet Phase IV Control Protocol (DNCP) This document defines the NCP for establishing and configuring Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc.). [STANDARDS-TRACK] | November 1992 Status: PROPOSED STANDARD Autor: S. Senum |
| RFC1377 The PPP OSI Network Layer Control Protocol (OSINLCP) This document defines the NCP for establishing and configuring OSI Network Layer Protocols. [STANDARDS-TRACK] | November 1992 Status: PROPOSED STANDARD Autor: D. Katz |
| RFC1378 The PPP AppleTalk Control Protocol (ATCP) This document defines the NCP for establishing and configuring the AppleTalk Protocol [3] over PPP. [STANDARDS-TRACK] | November 1992 Status: HISTORIC Autor: B. Parker |
| RFC1379 Extending TCP for Transactions -- Concepts This memo discusses extension of TCP to provide transaction-oriented service, without altering its virtual-circuit operation. This memo provides information for the Internet community. It does not specify an Internet standard. | November 1992 Status: HISTORIC Autor: R. Braden |
| RFC1380 IESG Deliberations on Routing and Addressing This memo summarizes issues surrounding the routing and addressing scaling problems in the IP architecture, and it provides a brief background of the ROAD group and related activities in the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard. | November 1992 Status: INFORMATIONAL Autor: P. Gross, P. Almquist |
| RFC1381 SNMP MIB Extension for X.25 LAPB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Link Layer of X.25, LAPB. [STANDARDS-TRACK] | November 1992 Status: PROPOSED STANDARD Autor: D. Throop, F. Baker |
| RFC1382 SNMP MIB Extension for the X.25 Packet Layer This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] | November 1992 Status: PROPOSED STANDARD Autor: D. Throop |
| RFC1383 An Experiment in DNS Based IP Routing Potential solutions to the routing explosion. This memo defines an Experimental Protocol for the Internet community. | December 1992 Status: EXPERIMENTAL Autor: C. Huitema |
| RFC1384 Naming Guidelines for Directory Pilots This document defines a number of naming guidelines. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: P. Barker, S.E. Hardcastle-Kille |
| RFC1385 EIP: The Extended Internet Protocol EIP can substantially reduce the amount of modifications needed to the current Internet systems and greatly ease the difficulties of transition. This is an "idea" paper and discussion is strongly encouraged on Big-Internet@munnari.oz.au. This memo provides information for the Internet community. It does not specify an Internet standard. | November 1992 Status: INFORMATIONAL Autor: Z. Wang |
| RFC1386 The US Domain This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | December 1992 Status: INFORMATIONAL Autor: A. Cooper, J. Postel |
| RFC1387 RIP Version 2 Protocol Analysis As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: G. Malkin |
| RFC1388 RIP Version 2 Carrying Additional Information This document specifies an extension of the Routing Information Protocol (RIP), as defined in [STANDARDS-TRACK] | January 1993 Status: PROPOSED STANDARD Autor: G. Malkin |
| RFC1389 RIP Version 2 MIB Extensions This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK] | January 1993 Status: PROPOSED STANDARD Autor: G. Malkin, F. Baker |
| RFC1390 Transmission of IP and ARP over FDDI Networks This memo defines a method of encapsulating the Internet Protocol (IP) datagrams and Address Resolution Protocol (ARP) requests and replies on Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK] | January 1993 Status: STANDARD Autor: D. Katz |
| RFC1391 The Tao of the IETF: A Guide for New Attendees of the Internet Engineering Task Force The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This will give them a warm, fuzzy feeling and enable them to make the meeting more productive for everyone. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: G. Malkin |
| RFC1392 Internet Users' Glossary There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: G. Malkin, T. LaQuey Parker |
| RFC1393 Traceroute Using an IP Option This document specifies a new IP option and ICMP message type which duplicates the functionality of the existing traceroute method while generating fewer packets and completing in a shorter time. This memo defines an Experimental Protocol for the Internet community. | January 1993 Status: EXPERIMENTAL Autor: G. Malkin |
| RFC1394 Relationship of Telex Answerback Codes to Internet Domains This RFC gives the list, as best known, of all common Internet domains and the conversion between specific country telex answerback codes and Internet country domain identifiers. It also lists the telex code and international dialing code, wherever it is available. It will also list major Internet "Public" E-Mail addresses. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: P. Robinson |
| RFC1395 BOOTP Vendor Information Extensions This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo will be updated as additional tags are defined. This edition introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16 for Swap Server and Tag 17 for Root Path. This memo is a status report on the vendor information extensions used int the Bootstrap Protocol (BOOTP). | January 1993 Status: DRAFT STANDARD Autor: J. Reynolds |
| RFC1396 The Process for Organization of Internet Standards Working Group (POISED) This report provides a summary of the POISED Working Group (WG), starting from the events leading to the formation of the WG to the end of 1992. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: S. Crocker |
| RFC1397 Default Route Advertisement In BGP2 and BGP3 Version of The Border Gateway Protocol This document speficies the recommendation of the BGP Working Group on default route advertisement support in BGP2 [1] and BGP3 [2] versions of the Border Gateway Protocol. [STANDARDS-TRACK] | January 1993 Status: HISTORIC Autor: D. Haskin |
| RFC1398 Definitions of Managed Objects for the Ethernet-Like Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing ehternet-like objects. [STANDARDS-TRACK] | January 1993 Status: DRAFT STANDARD Autor: F. Kastenholz |
| RFC1399 Summary of 1300-1399 | January 1997 Status: INFORMATIONAL Autor: J. Elliott |
| RFC1400 Transition and Modernization of the Internet Registration Service As a result of the NREN NIS award by National Science Foundation, non- DDN registration services will soon be transferred from the DDN NIC to the new Internet Registration Service, which is a part of an entity referred to as the InterNIC. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1993 Status: INFORMATIONAL Autor: S. Williamson |
| RFC1401 Correspondence between the IAB and DISA on the use of DNS This memo reproduces three letters exchanged between the Internet Activities Board (IAB) and the Defense Information Systems Agency (DISA) regarding the importance of using the Domain Name System (DNS) throughout the Internet, and phasing out the use of older host name to address tables, such as "hosts.txt". This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: Internet Architecture Board |
| RFC1402 There's Gold in them thar Networks! or Searching for Treasure in all the Wrong Places The ultimate goal is to make the route to these sources of information invisible to you. At present, this is not easy to do. I will explain some of the techniques that can be used to make these nuggets easier to pick up so that we all can be richer. This RFC provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: J. Martin |
| RFC1403 BGP OSPF Interaction This memo defines the various criteria to be used when designing an Autonomous System Border Routers (ASBR) that will run BGP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] | January 1993 Status: HISTORIC Autor: K. Varadhan |
| RFC1404 A Model for Common Operational Statistics This memo describes a model for operational statistics in the Internet. It gives recommendations for metrics, measurements, polling periods, storage formats and presentation formats. This memo provides information for the Internet community. It does not specify an Internet standard. | January 1993 Status: INFORMATIONAL Autor: B. Stockman |
| RFC1405 Mapping between X.400(1984/1988) and Mail-11 (DECnet mail) This document describes a set of mappings which will enable inter working between systems operating the CCITT X.400 ( 1984 / 1988 ) Recommendations on Message Handling Systems, and systems running the Mail-11 (also known as DECnet mail) protocol. This memo defines an Experimental Protocol for the Internet community. | January 1993 Status: EXPERIMENTAL Autor: C. Allocchio |
| RFC1406 Definitions of Managed Objects for the DS1 and E1 Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS1 Interfaces -- including both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links. [STANDARDS-TRACK] | January 1993 Status: PROPOSED STANDARD Autor: F. Baker, J. Watt |
| RFC1407 Definitions of Managed Objects for the DS3/E3 Interface Type This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing DS3 and E3 Interfaces. [STANDARDS-TRACK] | January 1993 Status: PROPOSED STANDARD Autor: T. Cox, K. Tesink |
| RFC1408 Telnet Environment Option This document specifies a mechanism for passing environment information between a telnet client and server. [STANDARDS-TRACK] | January 1993 Status: HISTORIC Autor: D. Borman |
| RFC1409 Telnet Authentication Option This memo defines an Experimental Protocol for the Internet community. | January 1993 Status: EXPERIMENTAL Autor: D. Borman |
| RFC1410 IAB Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). | March 1993 Status: HISTORIC Autor: J. Postel |
| RFC1411 Telnet Authentication: Kerberos Version 4 This memo defines an Experimental Protocol for the Internet community. | January 1993 Status: EXPERIMENTAL Autor: D. Borman |
| RFC1412 Telnet Authentication: SPX This memo defines an Experimental Protocol for the Internet community. | January 1993 Status: EXPERIMENTAL Autor: K. Alagappan |
| RFC1413 Identification Protocol The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. [STANDARDS-TRACK] | February 1993 Status: PROPOSED STANDARD Autor: M. St. Johns |
| RFC1414 Identification MIB This memo defines a MIB for use with identifying the users associated with TCP connections. It provides functionality approximately equivalent to that provided by the protocol defined in RFC 1413 [1]. [STANDARDS-TRACK] | February 1993 Status: HISTORIC Autor: M. St. Johns, M. Rose |
| RFC1415 FTP-FTAM Gateway Specification This memo describes a dual protocol stack application layer gateway that performs protocol translation, in an interactive environment, between the FTP and FTAM file transfer protocols. [STANDARDS-TRACK] | January 1993 Status: HISTORIC Autor: J. Mindel, R. Slaski |
| RFC1416 Telnet Authentication Option This RFC 1416 replaces RFC 1409, which has an important typographical error in the example on page 6 (one occurance of "REPLY" should be "IS"). This memo defines an Experimental Protocol for the Internet community. | February 1993 Status: EXPERIMENTAL Autor: D. Borman |
| RFC1417 NADF Standing Documents: A Brief Overview The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1993 Status: INFORMATIONAL Autor: The North American Directory Forum |
| RFC1418 SNMP over OSI This memo addresses some concerns by defining a framework for running the SNMP in an environment which supports the OSI connectionless-mode transport service. [STANDARDS-TRACK] | March 1993 Status: HISTORIC Autor: M. Rose |
| RFC1419 SNMP over AppleTalk This memo describes the method by which the Simple Network Management Protocol (SNMP) as specified in [1] can be used over AppleTalk protocols [2] instead of the Internet UDP/IP protocol stack. [STANDARDS-TRACK] | March 1993 Status: HISTORIC Autor: G. Minshall, M. Ritter |
| RFC1420 SNMP over IPX This document defines a convention for encapsulating Simple Network Management Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2]. [STANDARDS-TRACK] | March 1993 Status: PROPOSED STANDARD Autor: S. Bostock |
| RFC1421 Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures This document defines message encryption and authentication procedures, in order to provide privacy-enhanced mail (PEM) services for electronic mail transfer in the Internet. [STANDARDS-TRACK] | February 1993 Status: HISTORIC Autor: J. Linn |
| RFC1422 Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management This is one of a series of documents defining privacy enhancement mechanisms for electronic mail transferred using Internet mail protocols. [STANDARDS-TRACK] | February 1993 Status: HISTORIC Autor: S. Kent |
| RFC1423 Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers This document provides definitions, formats, references, and citations for cryptographic algorithms, usage modes, and associated identifiers and parameters used in support of Privacy Enhanced Mail (PEM) in the Internet community. [STANDARDS-TRACK] | February 1993 Status: HISTORIC Autor: D. Balenson |
| RFC1424 Privacy Enhancement for Internet Electronic Mail: Part IV: Key Certification and Related Services This document describes three types of service in support of Internet Privacy-Enhanced Mail (PEM) [1-3]: key certification, certificate- revocation list (CRL) storage, and CRL retrieval. [STANDARDS-TRACK] | February 1993 Status: HISTORIC Autor: B. Kaliski |
| RFC1425 SMTP Service Extensions This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK] | February 1993 Status: PROPOSED STANDARD Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker |
| RFC1426 SMTP Service Extension for 8bit-MIMEtransport This memo defines an extension to the SMTP service whereby an SMTP content body containing octets outside of the US ASCII octet range (hex | February 1993 Status: PROPOSED STANDARD Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker |
| RFC1427 SMTP Service Extension for Message Size Declaration This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK] | February 1993 Status: PROPOSED STANDARD Autor: J. Klensin, N. Freed, K. Moore |
| RFC1428 Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME This document outlines the problems in this environment and an approach to minimizing the cost of transition from current usage of non-MIME 8bit messages to MIME. This RFC provides information for the Internet community. It does not specify an Internet standard. | February 1993 Status: INFORMATIONAL Autor: G. Vaudreuil |
| RFC1429 Listserv Distribute Protocol This memo specifies a subset of the distribution protocol used by the BITNET LISTSERV to deliver mail messages to large amounts of recipients. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1993 Status: INFORMATIONAL Autor: E. Thomas |
| RFC1430 A Strategic Plan for Deploying an Internet X.500 Directory Service This document describes an overall strategy for deploying a Directory Service on the Internet, based on the OSI X.500 Directory Service. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1993 Status: INFORMATIONAL Autor: S. Hardcastle-Kille, E. Huizer, V. Cerf, R. Hobby, S. Kent |
| RFC1431 DUA Metrics (OSI-DS 33 (v2)) This document defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. This memo provides information for the Internet community. It does not specify an Internet standard. | February 1993 Status: INFORMATIONAL Autor: P. Barker |
| RFC1432 Recent Internet Books Here is a list of books related to using the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1993 Status: INFORMATIONAL Autor: J. Quarterman |
| RFC1433 Directed ARP Directed ARP is a dynamic address resolution procedure that enables hosts and routers to resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses. This memo defines an Experimental Protocol for the Internet community. | March 1993 Status: EXPERIMENTAL Autor: J. Garrett, J. Hagan, J. Wong |
| RFC1434 Data Link Switching: Switch-to-Switch Protocol This RFC describes IBM's support of Data Link Switching over TCP/IP. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1993 Status: INFORMATIONAL Autor: R. Dixon, D. Kushi |
| RFC1435 IESG Advice from Experience with Path MTU Discovery In the course of reviewing the MTU Discovery protocol for possible elevation to Draft Standard, a specific operational problem was uncovered. The problem results from the optional suppression of ICMP messages implemented in some routers. This memo outlines a modification to this practice to allow the correct functioning of MTU Discovery. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1993 Status: INFORMATIONAL Autor: S. Knowles |
| RFC1436 The Internet Gopher Protocol (a distributed document search and retrieval protocol) This document describes the protocol, lists some of the implementations currently available, and has an overview of how to implement new client and server applications. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1993 Status: INFORMATIONAL Autor: F. Anklesaria, M. McCahill, P. Lindner, D. Johnson, D. Torrey, B. Albert |
| RFC1437 The Extension of MIME Content-Types to a New Medium This document defines one particular type of MIME data, the matter- transport/sentient-life-form type. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1993 Status: INFORMATIONAL Autor: N. Borenstein, M. Linimon |
| RFC1438 Internet Engineering Task Force Statements Of Boredom (SOBs) This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). This memo provides information for the Internet community. It does not specify an Internet standard. | April 1993 Status: INFORMATIONAL Autor: A. Lyman Chapin, C. Huitema |
| RFC1439 The Uniqueness of Unique Identifiers This RFC provides information that may be useful when selecting a method to use for assigning unique identifiers to people. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1993 Status: INFORMATIONAL Autor: C. Finseth |
| RFC1440 SIFT/UFT: Sender-Initiated/Unsolicited File Transfer This document describes a Sender-Initiated File Transfer (SIFT) protocol, also commonly called Unsolicited File Transfer (UFT) protocol. This memo defines an Experimental Protocol for the Internet community. | July 1993 Status: EXPERIMENTAL Autor: R. Troth |
| RFC1441 Introduction to version 2 of the Internet-standard Network Management Framework The purpose of this document is to provide an overview of version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2). [STANDARDS-TRACK] | April 1993 Status: HISTORIC Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1442 Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2) Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1]. It is the purpose of this document, the Structure of Management Information (SMI), to define that subset. [STANDARDS-TRACK] | April 1993 Status: PROPOSED STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1443 Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] | April 1993 Status: PROPOSED STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1444 Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2) It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK] | April 1993 Status: PROPOSED STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1445 Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document, the Administrative Model for SNMPv2, to define how the administrative framework is applied to realize effective network management in a variety of configurations and environments. [STANDARDS-TRACK] | April 1993 Status: HISTORIC Autor: J. Galvin, K. McCloghrie |
| RFC1446 Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document, Security Protocols for SNMPv2, to define one such authentication and one such privacy protocol. [STANDARDS-TRACK] | April 1993 Status: HISTORIC Autor: J. Galvin, K. McCloghrie |
| RFC1447 Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2) The Administrative Model for SNMPv2 document [3] defines the properties associated with SNMPv2 parties, SNMPv2 contexts, and access control policies. It is the purpose of this document, the Party MIB for SNMPv2, to define managed objects which correspond to these properties. [STANDARDS-TRACK] | April 1993 Status: HISTORIC Autor: K. McCloghrie, J. Galvin |
| RFC1448 Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK] | April 1993 Status: PROPOSED STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1449 Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK] | April 1993 Status: PROPOSED STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1450 Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK] | April 1993 Status: PROPOSED STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1451 Manager-to-Manager Management Information Base It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity acting in both a manager role and an agent role. [STANDARDS-TRACK] | April 1993 Status: HISTORIC Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1452 Coexistence between version 1 and version 2 of the Internet-standard Network Management Framework The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2) [1], and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS-TRACK] | April 1993 Status: PROPOSED STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1453 A Comment on Packet Video Remote Conferencing and the Transport/Network Layers This RFC is a vehicle to inform the Internet community about XTP as it benefits from past Internet activity and targets general-purpose applications and multimedia applications with the emerging ATM networks in mind. This memo provides information for the Internet community. It does not specify an Internet standard. | April 1993 Status: INFORMATIONAL Autor: W. Chimiak |
| RFC1454 Comparison of Proposals for Next Version of IP This is a slightly edited reprint of RARE Technical Report (RTC(93)004). This memo provides information for the Internet community. It does not specify an Internet standard. | May 1993 Status: INFORMATIONAL Autor: T. Dixon |
| RFC1455 Physical Link Security Type of Service This RFC documents an experimental protocol providing a Type of Service (TOS) to request maximum physical link security. This is an addition to the types of service enumerated in RFC 1349: Type of Service in the Internet Protocol Suite. This memo defines an Experimental Protocol for the Internet community. | May 1993 Status: EXPERIMENTAL Autor: D. Eastlake 3rd |
| RFC1456 Conventions for Encoding the Vietnamese Language VISCII: VIetnamese Standard Code for Information Interchange VIQR: VIetnamese Quoted-Readable Specification This document provides information to the Internet community on the currently used conventions for encoding Vietnamese characters into 7-bit US ASCII and in an 8-bit form. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1993 Status: INFORMATIONAL Autor: Vietnamese Standardization Working Group |
| RFC1457 Security Label Framework for the Internet This memo presents a security labeling framework for the Internet. The framework is intended to help protocol designers determine what, if any, security labeling should be supported by their protocols. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1993 Status: INFORMATIONAL Autor: R. Housley |
| RFC1458 Requirements for Multicast Protocols This memo discusses some of these unresolved issues, and provides a high-level design for a new multicast transport protocol, group address and membership authority, and modifications to existing routing protocols. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1993 Status: INFORMATIONAL Autor: R. Braudes, S. Zabele |
| RFC1459 Internet Relay Chat Protocol The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. This memo defines an Experimental Protocol for the Internet community. | May 1993 Status: EXPERIMENTAL Autor: J. Oikarinen, D. Reed |
| RFC1460 Post Office Protocol - Version 3 This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS-TRACK] | June 1993 Status: DRAFT STANDARD Autor: M. Rose |
| RFC1461 SNMP MIB extension for Multiprotocol Interconnect over X.25 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Multiprotocol Interconnect (including IP) traffic carried over X.25. [STANDARDS-TRACK] | May 1993 Status: HISTORIC Autor: D. Throop |
| RFC1462 FYI on "What is the Internet?" This FYI RFC answers the question, "What is the Internet?" and is produced by the User Services Working Group of the Internet Engineering Task Force (IETF). This memo provides information for the Internet community. It does not specify an Internet standard. | May 1993 Status: INFORMATIONAL Autor: E. Krol, E. Hoffman |
| RFC1463 FYI on Introducing the Internet-- A Short Bibliography of Introductory Internetworking Readings This bibliography offers a short list of recent information resources that will help the network novice become familiar with the Internet, including its associated networks, resources, protocols, and history. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1993 Status: INFORMATIONAL Autor: E. Hoffman, L. Jackson |
| RFC1464 Using the Domain Name System To Store Arbitrary String Attributes This paper describes a simple means to associate arbitrary string information (ASCII text) with attributes that have not been defined by the DNS. This memo defines an Experimental Protocol for the Internet community. | May 1993 Status: EXPERIMENTAL Autor: R. Rosenbaum |
| RFC1465 Routing Coordination for X.400 MHS Services Within a Multi Protocol / Multi Network Environment Table Format V3 for Static Routing This document proposes short term solutions for maintaining and distributing routing information and shows how messages can travel over different networks by using multi stack MTAs as relays. This memo defines an Experimental Protocol for the Internet community. | May 1993 Status: EXPERIMENTAL Autor: D. Eppenberger |
| RFC1466 Guidelines for Management of IP Address Space This document proposes a plan which will forward the implementation of RFC 1174 and which defines the allocation and assignment of the network number space. This memo provides information for the Internet community. It does not specify an Internet standard. | May 1993 Status: INFORMATIONAL Autor: E. Gerich |
| RFC1467 Status of CIDR Deployment in the Internet This document describes the current status of the development and deployment of CIDR technology into the Internet. This document replaces RFC 1367, which was a schedule for the deployment of IP address space management procedures to support route aggregation. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1993 Status: HISTORIC Autor: C. Topolcic |
| RFC1468 Japanese Character Encoding for Internet Messages This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1993 Status: INFORMATIONAL Autor: J. Murai, M. Crispin, E. van der Poel |
| RFC1469 IP Multicast over Token-Ring Local Area Networks This document specifies a method for the transmission of IP multicast datagrams over Token-Ring Local Area Networks. [STANDARDS-TRACK] | June 1993 Status: HISTORIC Autor: T. Pusateri |
| RFC1470 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices The goal of this FYI memo is to provide an update to FYI 2, RFC 1147 [1], which provided practical information to site administrators and network managers. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1993 Status: INFORMATIONAL Autor: R. Enger, J. Reynolds |
| RFC1471 The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Link Control Protocol and Link Quality Monitoring on subnetwork interfaces that use the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] | June 1993 Status: PROPOSED STANDARD Autor: F. Kastenholz |
| RFC1472 The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Security Protocols on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] | June 1993 Status: PROPOSED STANDARD Autor: F. Kastenholz |
| RFC1473 The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the IP Network Control Protocol on subnetwork interfaces using the family of Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK] | June 1993 Status: PROPOSED STANDARD Autor: F. Kastenholz |
| RFC1474 The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the bridge Network Control Protocol [10] on subnetwork interfaces using the family of Point-to-Point Protocols. [STANDARDS-TRACK] | June 1993 Status: HISTORIC Autor: F. Kastenholz |
| RFC1475 TP/IX: The Next Internet This memo presents the specification for version 7 of the Internet Protocol, as well as version 7 of the TCP and the user datagram protocol. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | June 1993 Status: EXPERIMENTAL Autor: R. Ullmann |
| RFC1476 RAP: Internet Route Access Protocol This RFC describes an open distance vector routing protocol for use at all levels of the internet, from isolated LANs to the major routers of an international commercial network provider. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | June 1993 Status: EXPERIMENTAL Autor: R. Ullmann |
| RFC1477 IDPR as a Proposed Standard This document contains a discussion of inter-domain policy routing (IDPR), including an overview of functionality and a discussion of experiments. This memo provides information for the Internet community. It does not specify an Internet standard. | July 1993 Status: INFORMATIONAL Autor: M. Steenstrup |
| RFC1478 An Architecture for Inter-Domain Policy Routing We present an architecture for inter-domain policy routing (IDPR). [STANDARDS-TRACK] | June 1993 Status: HISTORIC Autor: M. Steenstrup |
| RFC1479 Inter-Domain Policy Routing Protocol Specification: Version 1 We present the set of protocols and procedures that constitute Inter- Domain Policy Routing (IDPR). [STANDARDS-TRACK] | July 1993 Status: HISTORIC Autor: M. Steenstrup |
| RFC1480 The US Domain This is a description of the US Top Level Domains on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1993 Status: INFORMATIONAL Autor: A. Cooper, J. Postel |
| RFC1481 IAB Recommendation for an Intermediate Strategy to Address the Issue of Scaling CIDR is proposed as an immediate term strategy to extend the life of the current 32 bit IP address space. This memo provides information for the Internet community. It does not specify an Internet standard. | July 1993 Status: HISTORIC Autor: C. Huitema |
| RFC1482 Aggregation Support in the NSFNET Policy-Based Routing Database This document describes plans for support of route aggregation, as specified in the descriptions of Classless Inter-Domain Routing (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network Service. This memo provides information for the Internet community. It does not specify an Internet standard. | June 1993 Status: HISTORIC Autor: M. Knopper, S. Richardson |
| RFC1483 Multiprotocol Encapsulation over ATM Adaptation Layer 5 This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. [STANDARDS-TRACK] | July 1993 Status: PROPOSED STANDARD Autor: Juha Heinanen |
| RFC1484 Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2)) This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | July 1993 Status: HISTORIC Autor: S. Hardcastle-Kille |
| RFC1485 A String Representation of Distinguished Names (OSI-DS 23 (v5)) When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. [STANDARDS-TRACK] | July 1993 Status: HISTORIC Autor: S. Hardcastle-Kille |
| RFC1486 An Experiment in Remote Printing This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | July 1993 Status: EXPERIMENTAL Autor: M. Rose, C. Malamud |
| RFC1487 X.500 Lightweight Directory Access Protocol The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK] | July 1993 Status: HISTORIC Autor: W. Yeong, T. Howes, S. Kille |
| RFC1488 The X.500 String Representation of Standard Attribute Syntaxes This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3]. [STANDARDS-TRACK] | July 1993 Status: PROPOSED STANDARD Autor: T. Howes, S. Kille, W. Yeong, C. Robbins |
| RFC1489 Registration of a Cyrillic Character Set Though the proposed character set "koi8-r" is not currently an international standard, there is very large user community (including Relcom Net) supporting it. Factually, "koi8-r" is de-facto standard for Unix and global network applications in the former Soviet Union. This is the reason the Society of Unix User Groups (SUUG) believes "koi8-r" should be registered. This memo provides information for the Internet community. It does not specify an Internet standard. | July 1993 Status: INFORMATIONAL Autor: A. Chernov |
| RFC1490 Multiprotocol Interconnect over Frame Relay This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU. [STANDARDS-TRACK] | July 1993 Status: DRAFT STANDARD Autor: T. Bradley, C. Brown, A. Malis |
| RFC1491 A Survey of Advanced Usages of X.500 This document is the result of a survey asking people to detail their advanced usages of X.500. It is intended to show how various organizations are using X.500 in ways which extend the view of X.500 as a "White Pages" service. This RFC is a product of the Integrated Directory Services Working Group of the Application and User Services Areas of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard. | July 1993 Status: INFORMATIONAL Autor: C. Weider, R. Wright |
| RFC1492 An Access Control Protocol, Sometimes Called TACACS This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard. | July 1993 Status: INFORMATIONAL Autor: C. Finseth |
| RFC1493 Definitions of Managed Objects for Bridges This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments. [STANDARDS-TRACK] | July 1993 Status: DRAFT STANDARD Autor: E. Decker, P. Langille, A. Rijsinghani, K. McCloghrie |
| RFC1494 Equivalences between 1988 X.400 and RFC-822 Message Bodies This document describes the content of the "IANA MHS/MIME Equivalence table", and defines the initial configuration of this table. Mappings for new MIME content-types and/or X.400 body part types should be registered with the IANA to minimize redundancy and promote interoperability. [STANDARDS-TRACK] | August 1993 Status: HISTORIC Autor: H. Alvestrand, S. Thompson |
| RFC1495 Mapping between X.400 and RFC-822 Message Bodies Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK] | August 1993 Status: PROPOSED STANDARD Autor: H. Alvestrand, S. Kille, R. Miles, M. Rose, S. Thompson |
| RFC1496 Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages This document describes how RFC-1328 must be modified in order to provide adequate support for the scenarios: It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT obsoleted. [STANDARDS-TRACK] | August 1993 Status: HISTORIC Autor: H. Alvestrand, J. Romaguera, K. Jordan |
| RFC1497 BOOTP Vendor Information Extensions This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP). | August 1993 Status: DRAFT STANDARD Autor: J. Reynolds |
| RFC1498 On the Naming and Binding of Network Destinations This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas: First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1993 Status: INFORMATIONAL Autor: J. Saltzer |
| RFC1499 Summary of 1400-1499 | January 1997 Status: INFORMATIONAL Autor: J. Elliott |
| RFC1500 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK] | August 1993 Status: HISTORIC Autor: J. Postel |
| RFC1501 OS/2 User Group Memo soliciting reactions to the proposal of a OS/2 User Group. This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind. | August 1993 Status: INFORMATIONAL Autor: E. Brunsen |
| RFC1502 X.400 Use of Extended Character Sets This RFC defines a suggested method of using "GeneralText" in order to harmonize as much as possible the usage of this body part. [STANDARDS-TRACK] | August 1993 Status: HISTORIC Autor: H. Alvestrand |
| RFC1503 Algorithms for Automating Administration in SNMPv2 Managers When a user invokes an SNMPv2 management application, it may be desirable for the user to specify the minimum amount of information necessary to establish and maintain SNMPv2 communications. This memo suggests an approach to achieve this goal. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1993 Status: INFORMATIONAL Autor: K. McCloghrie, M. Rose |
| RFC1504 Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing This document provides detailed information about the AppleTalk Update- based Routing Protocol (AURP) and wide area routing. AURP provides wide area routing enhancements to the AppleTalk routing protocols and is fully compatible with AppleTalk Phase 2. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1993 Status: INFORMATIONAL Autor: A. Oppenheimer |
| RFC1505 Encoding Header Field for Internet Messages This document expands upon the elective experimental Encoding header field which permits the mailing of multi-part, multi-structured messages. It replaces RFC 1154. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | August 1993 Status: EXPERIMENTAL Autor: A. Costanzo, D. Robinson, R. Ullmann |
| RFC1506 A Tutorial on Gatewaying between X.400 and Internet Mail This tutorial was produced especially to help new gateway managers find their way into the complicated subject of mail gatewaying according to RFC 1327. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1993 Status: INFORMATIONAL Autor: J. Houttuin |
| RFC1507 DASS - Distributed Authentication Security Service The goal of DASS is to provide authentication services in a distributed environment which are both more secure and easier to use than existing mechanisms. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | September 1993 Status: EXPERIMENTAL Autor: C. Kaufman |
| RFC1508 Generic Security Service Application Program Interface This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. [STANDARDS-TRACK] | September 1993 Status: PROPOSED STANDARD Autor: J. Linn |
| RFC1509 Generic Security Service API : C-bindings This document specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents. [STANDARDS-TRACK] | September 1993 Status: PROPOSED STANDARD Autor: J. Wray |
| RFC1510 The Kerberos Network Authentication Service (V5) This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. [STANDARDS-TRACK] | September 1993 Status: PROPOSED STANDARD Autor: J. Kohl, C. Neuman |
| RFC1511 Common Authentication Technology Overview This memo provides information for the Internet community. It does not specify an Internet standard. | September 1993 Status: INFORMATIONAL Autor: J. Linn |
| RFC1512 FDDI Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing devices which implement the FDDI based on the ANSI FDDI SMT 7.3 draft standard, which has been forwarded for publication by the X3T9.5 committee. | September 1993 Status: HISTORIC Autor: J. Case, A. Rijsinghani |
| RFC1513 Token Ring Extensions to the Remote Network Monitoring MIB This memo defines extensions to the Remote Network Monitoring MIB for managing 802.5 Token Ring networks. [STANDARDS-TRACK] | September 1993 Status: HISTORIC Autor: S. Waldbusser |
| RFC1514 Host Resources MIB This memo defines a MIB for use with managing host systems. [STANDARDS-TRACK] | September 1993 Status: PROPOSED STANDARD Autor: P. Grillo, S. Waldbusser |
| RFC1515 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). [STANDARDS-TRACK] | September 1993 Status: PROPOSED STANDARD Autor: D. McMaster, K. McCloghrie, S. Roberts |
| RFC1516 Definitions of Managed Objects for IEEE 802.3 Repeater Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 10 Mb/second baseband repeaters, sometimes referred to as "hubs." [STANDARDS-TRACK] | September 1993 Status: DRAFT STANDARD Autor: D. McMaster, K. McCloghrie |
| RFC1517 Applicability Statement for the Implementation of Classless Inter-Domain Routing (CIDR) Classless Inter-Domain Routing (CIDR) defines a mechanism to slow the growth of routing tables and reduce the need to allocate new IP network numbers. [STANDARDS-TRACK] | September 1993 Status: HISTORIC Autor: Internet Engineering Steering Group, R. Hinden |
| RFC1518 An Architecture for IP Address Allocation with CIDR This paper provides an architecture and a plan for allocating IP addresses in the Internet. This architecture and the plan are intended to play an important role in steering the Internet towards the Address Assignment and Aggregating Strategy. [STANDARDS-TRACK] | September 1993 Status: HISTORIC Autor: Y. Rekhter, T. Li |
| RFC1519 Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy This memo discusses strategies for address assignment of the existing IP address space with a view to conserve the address space and stem the explosive growth of routing tables in default-route-free routers. [STANDARDS-TRACK] | September 1993 Status: PROPOSED STANDARD Autor: V. Fuller, T. Li, J. Yu, K. Varadhan |
| RFC1520 Exchanging Routing Information Across Provider Boundaries in the CIDR Environment The purpose of this document is twofold. First, it describes various alternatives for exchanging inter-domain routing information across domain boundaries, where one of the peering domain is CIDR-capable and another is not. Second, it addresses the implications of running CIDR- capable inter-domain routing protocols (e.g., BGP-4, IDRP) on intra- domain routing. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1993 Status: HISTORIC Autor: Y. Rekhter, C. Topolcic |
| RFC1521 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. This is based on earlier work documented in RFC 934 and STD 11, RFC 1049, but extends and revises that work. [STANDARDS-TRACK] | September 1993 Status: DRAFT STANDARD Autor: N. Borenstein, N. Freed |
| RFC1522 MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text This memo describes an extension to the message format defined in RFC 1521, to allow the representation of character sets other than ASCII in RFC 822 (STD 11) message headers. The extensions described were designed to be highly compatible with existing Internet mail handling software, and to be easily implemented in mail readers that support RFC 1521. | September 1993 Status: DRAFT STANDARD Autor: K. Moore |
| RFC1523 The text/enriched MIME Content-type MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1993 Status: INFORMATIONAL Autor: N. Borenstein |
| RFC1524 A User Agent Configuration Mechanism For Multimedia Mail Format Information This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1993 Status: INFORMATIONAL Autor: N. Borenstein |
| RFC1525 Definitions of Managed Objects for Source Routing Bridges This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing source routing and source routing transparent bridges. These bridges are also required to implement relevant groups in the Bridge MIB. [STANDARDS-TRACK] | September 1993 Status: HISTORIC Autor: E. Decker, K. McCloghrie, P. Langille, A. Rijsinghani |
| RFC1526 Assignment of System Identifiers for TUBA/CLNP Hosts This document describes conventions whereby the system identifier portion of an RFC 1237 style NSAP address may be guaranteed uniqueness within a routing domain for the purpose of autoconfiguration in TUBA/CLNP internets. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1993 Status: INFORMATIONAL Autor: D. Piscitello |
| RFC1527 What Should We Plan Given the Dilemma of the Network? The Internet community needs to be asking what the most important policy issues facing the network are. And given agreement on any particular set of policy issues, the next thing we should be asking is, what would be some of the political choices that would follow for Congress to make? This memo is a shortened version of the suggested policy draft. This memo provides information for the Internet community. It does not specify an Internet standard. | September 1993 Status: INFORMATIONAL Autor: G. Cook |
| RFC1528 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. | October 1993 Status: EXPERIMENTAL Autor: C. Malamud, M. Rose |
| RFC1529 Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies This document defines the administrative policies for the operation of remote printer facilities within the context of the tpc.int subdomain. The document describes different approaches to resource recovery for remote printer server sites and includes discussions of issues pertaining to auditing, security, and denial of access. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1993 Status: INFORMATIONAL Autor: C. Malamud, M. Rose |
| RFC1530 Principles of Operation for the TPC.INT Subdomain: General Principles and Policy This document defines the initial principles of operation for the tpc.int subdomain, a collection of service listings accessible over the Internet infrastructure through an administered namespace contained within the Domain Name System. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1993 Status: INFORMATIONAL Autor: C. Malamud, M. Rose |
| RFC1531 Dynamic Host Configuration Protocol The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. [STANDARDS-TRACK] | October 1993 Status: PROPOSED STANDARD Autor: R. Droms |
| RFC1532 Clarifications and Extensions for the Bootstrap Protocol Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK] | October 1993 Status: PROPOSED STANDARD Autor: W. Wimer |
| RFC1533 DHCP Options and BOOTP Vendor Extensions This document specifies the current set of DHCP options. [STANDARDS-TRACK] | October 1993 Status: PROPOSED STANDARD Autor: S. Alexander, R. Droms |
| RFC1534 Interoperation Between DHCP and BOOTP DHCP provides a superset of the functions provided by BOOTP. This document describes the interactions between DHCP and BOOTP network participants. [STANDARDS-TRACK] | October 1993 Status: DRAFT STANDARD Autor: R. Droms |
| RFC1535 A Security Problem and Proposed Correction With Widely Deployed DNS Software This document discusses a flaw in some of the currently distributed name resolver clients. The flaw exposes a security weakness related to the search heuristic invoked by these same resolvers when users provide a partial domain name, and which is easy to exploit. This document points out the flaw, a case in point, and a solution. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1993 Status: INFORMATIONAL Autor: E. Gavron |
| RFC1536 Common DNS Implementation Errors and Suggested Fixes This memo describes common errors seen in DNS implementations and suggests some fixes. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1993 Status: INFORMATIONAL Autor: A. Kumar, J. Postel, C. Neuman, P. Danzig, S. Miller |
| RFC1537 Common DNS Data File Configuration Errors This memo describes errors often found in DNS data files. It points out common mistakes system administrators tend to make and why they often go unnoticed for long periods of time. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1993 Status: INFORMATIONAL Autor: P. Beertema |
| RFC1538 Advanced SNA/IP : A Simple SNA Transport Protocol This RFC provides information for the Internet community about a method for establishing and maintaining SNA sessions over an IP internet. This memo provides information for the Internet community. It does not specify an Internet standard. | October 1993 Status: INFORMATIONAL Autor: W. Behl, B. Sterling, W. Teskey |
| RFC1539 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17] | October 1993 Status: INFORMATIONAL Autor: G. Malkin |
| RFC1540 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Activities Board (IAB). [STANDARDS-TRACK] | October 1993 Status: HISTORIC Autor: J. Postel |
| RFC1541 Dynamic Host Configuration Protocol The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCP/IP network. DHCP is based on the Bootstrap Protocol (BOOTP) adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK] | October 1993 Status: PROPOSED STANDARD Autor: R. Droms |
| RFC1542 Clarifications and Extensions for the Bootstrap Protocol Some aspects of the BOOTP protocol were rather loosely defined in its original specification. In particular, only a general description was provided for the behavior of "BOOTP relay agents" (originally called BOOTP forwarding agents"). The client behavior description also suffered in certain ways. This memo attempts to clarify and strengthen the specification in these areas. [STANDARDS-TRACK] | October 1993 Status: DRAFT STANDARD Autor: W. Wimer |
| RFC1543 Instructions to RFC Authors This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1993 Status: INFORMATIONAL Autor: J. Postel |
| RFC1544 The Content-MD5 Header Field This memo defines the use of an optional header field, Content-MD5, which may be used as a message integrity check (MIC), to verify that the decoded data are the same data that were initially sent. [STANDARDS-TRACK] | November 1993 Status: PROPOSED STANDARD Autor: M. Rose |
| RFC1545 FTP Operation Over Big Address Records (FOOBAR) This RFC specifies a method for assigning long addresses in the HOST- PORT specification for the data port to be used in establishing a data connection for File Transfer Protocol, FTP (STD 9, RFC 959). This is a general solution, applicable for all "next generation" IP alternatives, and can also be extended to allow FTP operation over transport interfaces other than TCP. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | November 1993 Status: EXPERIMENTAL Autor: D. Piscitello |
| RFC1546 Host Anycasting Service This RFC describes an internet anycasting service for IP. The primary purpose of this memo is to establish the semantics of an anycasting service within an IP internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1993 Status: INFORMATIONAL Autor: C. Partridge, T. Mendez, W. Milliken |
| RFC1547 Requirements for an Internet Standard Point-to-Point Protocol This document discusses the evaluation criteria for an Internet Standard Data Link Layer protocol to be used with point-to-point links. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: D. Perkins |
| RFC1548 The Point-to-Point Protocol (PPP) This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK] | December 1993 Status: DRAFT STANDARD Autor: W. Simpson |
| RFC1549 PPP in HDLC Framing This document describes the use of HDLC for framing PPP encapsulated packets. [STANDARDS-TRACK] | December 1993 Status: DRAFT STANDARD Autor: W. Simpson |
| RFC1550 IP: Next Generation (IPng) White Paper Solicitation This memo solicits white papers on topics related to the IPng requirements and selection criteria. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: S. Bradner, A. Mankin |
| RFC1551 Novell IPX Over Various WAN Media (IPXWAN) This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: M. Allen |
| RFC1552 The PPP Internetworking Packet Exchange Control Protocol (IPXCP) This document defines the Network Control Protocol for establishing and configuring the IPX protocol over PPP. [STANDARDS-TRACK] | December 1993 Status: HISTORIC Autor: W. Simpson |
| RFC1553 Compressing IPX Headers Over WAN Media (CIPX) This document describes a method for compressing the headers of IPX datagrams (CIPX). [STANDARDS-TRACK] | December 1993 Status: HISTORIC Autor: S. Mathur, M. Lewis |
| RFC1554 ISO-2022-JP-2: Multilingual Extension of ISO-2022-JP This memo describes a text encoding scheme: "ISO-2022-JP-2", which is used experimentally for electronic mail [RFC822] and network news [RFC1036] messages in several Japanese networks. The encoding is a multilingual extension of "ISO-2022-JP", the existing encoding for Japanese [2022JP]. The encoding is supported by an Emacs based multilingual text editor: MULE [MULE]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: M. Ohta, K. Handa |
| RFC1555 Hebrew Character Encoding for Internet Messages This document describes the encoding used in electronic mail [RFC822] for transferring Hebrew. The standard devised makes use of MIME [RFC1521] and ISO-8859-8. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: H. Nussbacher, Y. Bourvine |
| RFC1556 Handling of Bi-directional Texts in MIME This document describes the format and syntax of the "direction" keyword to be used with bi-directional texts in MIME. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: H. Nussbacher |
| RFC1557 Korean Character Encoding for Internet Messages This document describes the encoding method being used to represent Korean characters in both header and body part of the Internet mail messages [RFC822]. This encoding method was specified in 1991, and has since then been used. It has now widely being used in Korean IP networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: U. Choi, K. Chon, H. Park |
| RFC1558 A String Representation of LDAP Search Filters The Lightweight Directory Access Protocol (LDAP) defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: T. Howes |
| RFC1559 DECnet Phase IV MIB Extensions This memo defines a set of DECnet Phase IV extensions that have been created for the Internet MIB. It reflects changes which are the result of operational experience based on RFC 1289. [STANDARDS-TRACK] | December 1993 Status: DRAFT STANDARD Autor: J. Saperia |
| RFC1560 The MultiProtocol Internet There has recently been considerable discussion on two topics: MultiProtocol approaches in the Internet and the selection of a next generation Internet Protocol. This document suggests a strawman position for goals and approaches for the IETF/IESG/IAB in these areas. It takes the view that these two topics are related, and proposes directions for the IETF/IESG/IAB to pursue. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: B. Leiner, Y. Rekhter |
| RFC1561 Use of ISO CLNP in TUBA Environments This memo specifies a profile of the ISO/IEC 8473 Connectionless-mode Network Layer Protocol for use in conjunction with RFC 1347, TCP/UDP over Bigger Addresses. It describes the use of CLNP to provide the lower-level service expected by Transmission Control Protocol and User Datagram Protocol. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: EXPERIMENTAL Autor: D. Piscitello |
| RFC1562 Naming Guidelines for the AARNet X.500 Directory Service This document is an AARNet (Australian Academic and Research Network) Engineering Note (AEN-001). AARNet Engineering Notes are engineering documents of the AARNet Engineering Working Group, and record current or proposed operational practices related to the provision of Internetworking services within Australia, and AARNet in particular. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1993 Status: INFORMATIONAL Autor: G. Michaelson, M. Prior |
| RFC1563 The text/enriched MIME Content-type MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1994 Status: INFORMATIONAL Autor: N. Borenstein |
| RFC1564 DSA Metrics (OSI-DS 34 (v3)) This document defines a set of criteria by which a DSA implementation may be judged. Particular issues covered include conformance to standards; performance; demonstrated interoperability. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1994 Status: INFORMATIONAL Autor: P. Barker, R. Hedberg |
| RFC1565 Network Services Monitoring MIB This document defines a MIB which contains the elements common to the monitoring of any network service application. This information includes a table of all monitorable network service applications, a count of the associations (connections) to each application, and basic information about the parameters and status of each application-related association. [STANDARDS-TRACK] | January 1994 Status: PROPOSED STANDARD Autor: S. Kille, N. Freed |
| RFC1566 Mail Monitoring MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, this memo extends the basic Network Services Monitoring MIB to allow monitoring of Message Transfer Agents (MTAs). It may also be used to monitor MTA components within gateways. [STANDARDS-TRACK] | January 1994 Status: PROPOSED STANDARD Autor: S. Kille, N. Freed |
| RFC1567 X.500 Directory Monitoring MIB This document defines a portion of the Management Information Base (MIB). It defines the MIB for monitoring Directory System Agents (DSA), a component of the OSI Directory. This MIB will be used in conjunction with the APPLICATION-MIB for monitoring DSAs. [STANDARDS-TRACK] | January 1994 Status: PROPOSED STANDARD Autor: G. Mansfield, S. Kille |
| RFC1568 Simple Network Paging Protocol - Version 1(b) This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1994 Status: INFORMATIONAL Autor: A. Gwinn |
| RFC1569 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures This memo describes a technique for radio paging using the Internet mail infrastructure. In particular, this memo focuses on the case in which radio pagers are identified via the international telephone network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1994 Status: INFORMATIONAL Autor: M. Rose |
| RFC1570 PPP LCP Extensions The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. This document defines several additional LCP features which have been suggested over the past few years. [STANDARDS-TRACK] | January 1994 Status: PROPOSED STANDARD Autor: W. Simpson |
| RFC1571 Telnet Environment Option Interoperability Issues This document describes a method for allowing implementors to ensure that their implementation of the Environment option will be interoperable with as many other implementations as possible, by providing a set of heuristics that can be used to help identify which definitions for VAR and VALUE are being used by the other side of the connection. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1994 Status: INFORMATIONAL Autor: D. Borman |
| RFC1572 Telnet Environment Option This document specifies a mechanism for passing environment information between a telnet client and server. Use of this mechanism enables a telnet user to propagate configuration information to a remote host when connecting. [STANDARDS-TRACK] | January 1994 Status: PROPOSED STANDARD Autor: S. Alexander |
| RFC1573 Evolution of the Interfaces Group of MIB-II This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Network Interfaces. [STANARDS-TRACK] | January 1994 Status: PROPOSED STANDARD Autor: K. McCloghrie, F. Kastenholz |
| RFC1574 Essential Tools for the OSI Internet This document specifies the following three necessary tools to debug problems in the deployment and maintenance of networks using ISO 8473 (CLNP): ping or OSI Echo function, traceroute function which uses the OSI Echo function, and routing table dump function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1994 Status: INFORMATIONAL Autor: S. Hares, C. Wittbrodt |
| RFC1575 An Echo Function for CLNP (ISO 8473) This memo defines an echo function for the connection-less network layer protocol. The mechanism that is mandated here is in the final process of being standardized by ISO as "Amendment X: Addition of an Echo function to ISO 8473" an integral part of Version 2 of ISO 8473. [STANDARDS-TRACK] | February 1994 Status: DRAFT STANDARD Autor: S. Hares, C. Wittbrodt |
| RFC1576 TN3270 Current Practices This document describes the existing implementation of transferring 3270 display terminal data using currently available telnet capabilities. The name traditionally associated with this implementation is TN3270. This memo provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1994 Status: INFORMATIONAL Autor: J. Penner |
| RFC1577 Classical IP and ARP over ATM This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK] | January 1994 Status: PROPOSED STANDARD Autor: M. Laubach |
| RFC1578 FYI on Questions and Answers - Answers to Commonly Asked "Primary and Secondary School Internet User" Questions The goal of this FYI RFC is to document the questions most commonly asked about the Internet by those in the primary and secondary school community, and to provide pointers to sources which answer those questions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 22] | February 1994 Status: INFORMATIONAL Autor: J. Sellers |
| RFC1579 Firewall-Friendly FTP This memo describes a suggested change to the behavior of FTP client programs. This document provides information for the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1994 Status: INFORMATIONAL Autor: S. Bellovin |
| RFC1580 Guide to Network Resource Tools The purpose of this guide is to supply the basic information that anyone on the network needs to try out and begin using tools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 23] | March 1994 Status: INFORMATIONAL Autor: EARN Staff |
| RFC1581 Protocol Analysis for Extensions to RIP to Support Demand Circuits As required by Routing Protocol Criteria, this report documents the key features of Routing over Demand Circuits on Wide Area Networks - RIP and the current implementation experience. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1994 Status: INFORMATIONAL Autor: G. Meyer |
| RFC1582 Extensions to RIP to Support Demand Circuits This memo defines a generalized modification which can be applied to Bellman-Ford (or distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK] | February 1994 Status: PROPOSED STANDARD Autor: G. Meyer |
| RFC1583 OSPF Version 2 This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK] | March 1994 Status: DRAFT STANDARD Autor: J. Moy |
| RFC1584 Multicast Extensions to OSPF This memo documents enhancements to the OSPF protocol enabling the routing of IP multicast datagrams. [STANDARDS-TRACK] | March 1994 Status: HISTORIC Autor: J. Moy |
| RFC1585 MOSPF: Analysis and Experience This memo documents how the MOSPF protocol satisfies the requirements imposed on Internet routing protocols by "Internet Engineering Task Force internet routing protocol standardization criteria" ([RFC 1264]). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: J. Moy |
| RFC1586 Guidelines for Running OSPF Over Frame Relay Networks This memo specifies guidelines for implementors and users of the Open Shortest Path First (OSPF) routing protocol to bring about improvements in how the protocol runs over frame relay networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: O. deSouza, M. Rodrigues |
| RFC1587 The OSPF NSSA Option This document describes a new optional type of OSPF area, somewhat humorously referred to as a "not-so-stubby" area (or NSSA). NSSAs are similar to the existing OSPF stub area configuration option but have the additional capability of importing AS external routes in a limited fashion. [STANDARDS-TRACK] | March 1994 Status: PROPOSED STANDARD Autor: R. Coltun, V. Fuller |
| RFC1588 White Pages Meeting Report This report describes the results of a meeting held at the November IETF (Internet Engineering Task Force) in Houston, TX, on November 2, 1993, to discuss the future of and approaches to a white pages directory services for the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1994 Status: INFORMATIONAL Autor: J. Postel, C. Anderson |
| RFC1589 A Kernel Model for Precision Timekeeping This memorandum describes an engineering model which implements a precision time-of-day function for a generic operating system. The model is based on the principles of disciplined oscillators and phase-lock loops (PLL) often found in the engineering literature. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: D. Mills |
| RFC1590 Media Type Registration Procedure Several questions have been raised about the requirements and administrative procedure for registering MIME content-type and subtypes, and the use of these Media Types for other applications. This document addresses these issues and specifies a procedure for the registration of new Media Types (content-type/subtypes). It also generalizes the scope of use of these Media Types to make it appropriate to use the same registrations and specifications with other applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: J. Postel |
| RFC1591 Domain Name System Structure and Delegation This memo provides some information on the structure of the names in the Domain Name System (DNS), specifically the top-level domain names; and on the administration of domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: J. Postel |
| RFC1592 Simple Network Management Protocol Distributed Protocol Interface Version 2.0 This RFC describes version 2.0 of a protocol that International Business Machines Corporation (IBM) has been implementing in most of its SNMP agents to allow dynamic extension of supported MIBs. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: EXPERIMENTAL Autor: B. Wijnen, G. Carpenter, K. Curran, A. Sehgal, G. Waters |
| RFC1593 SNA APPN Node MIB This RFC describes IBM's SNMP support for SNA Advanced Peer-to-Peer Networking (APPN) nodes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: W. McKenzie, J. Cheng |
| RFC1594 FYI on Questions and Answers - Answers to Commonly asked "New Internet User" Questions This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). The goal is to document the most commonly asked questions and answers in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. [FYI 4] | March 1994 Status: INFORMATIONAL Autor: A. Marine, J. Reynolds, G. Malkin |
| RFC1595 Definitions of Managed Objects for the SONET/SDH Interface Type | March 1994 Status: PROPOSED STANDARD Autor: T. Brown, K. Tesink |
| RFC1596 Definitions of Managed Objects for Frame Relay Service | March 1994 Status: PROPOSED STANDARD Autor: T. Brown |
| RFC1597 Address Allocation for Private Internets This RFC describes methods to preserve IP address space by not allocating globally unique IP addresses to hosts private to an enterprise while still permitting full network layer connectivity between all hosts inside an enterprise as well as between all public hosts of different enterprises. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: Y. Rekhter, B. Moskowitz, D. Karrenberg, G. de Groot |
| RFC1598 PPP in X.25 The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of X.25 for framing PPP encapsulated packets. [STANDARDS-TRACK] | March 1994 Status: PROPOSED STANDARD Autor: W. Simpson |
| RFC1599 Summary of 1500-1599 | January 1997 Status: INFORMATIONAL Autor: M. Kennedy |
| RFC1600 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] | March 1994 Status: HISTORIC Autor: J. Postel |
| RFC1601 Charter of the Internet Architecture Board (IAB) This memo documents the composition, selection, roles, and organization of the Internet Architecture Board and its subsidiary organizations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: C. Huitema |
| RFC1602 The Internet Standards Process -- Revision 2 This document is a revision of RFC 1310, which defined the official procedures for creating and documenting Internet Standards. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: Internet Architecture Board, Internet Engineering Steering Group |
| RFC1603 IETF Working Group Guidelines and Procedures This document describes the guidelines and procedures for formation and operation of IETF working groups. It describes the formal relationship between IETF participants WG and the Internet Engineering Steering Group (IESG). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1994 Status: INFORMATIONAL Autor: E. Huizer, D. Crocker |
| RFC1604 Definitions of Managed Objects for Frame Relay Service This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service. [STANDARDS-TRACK] | March 1994 Status: PROPOSED STANDARD Autor: T. Brown |
| RFC1605 SONET to Sonnet Translation Because Synchronous Optical Network (SONET) transmits data in frames of bytes, it is fairly easy to envision ways to compress SONET frames to yield higher bandwidth over a given fiber optic link. This memo describes a particular method, SONET Over Novel English Translation (SONNET). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1994 Status: INFORMATIONAL Autor: W. Shakespeare |
| RFC1606 A Historical Perspective On The Usage Of IP Version 9 This paper reviews the usages of the old IP version protocol. It considers some of its successes and its failures. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1994 Status: INFORMATIONAL Autor: J. Onions |
| RFC1607 A VIEW FROM THE 21ST CENTURY This document is a composition of letters discussing a possible future. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1994 Status: INFORMATIONAL Autor: V. Cerf |
| RFC1608 Representing IP Information in the X.500 Directory This document describes the objects necessary to include information about IP networks and IP numbers in the X.500 Directory. It extends the work "Charting networks in the X.500 Directory" [1] where a general framework is presented for representing networks in the Directory by applying it to IP networks. This memo defines an Experimental Protocol for the Internet community. | March 1994 Status: EXPERIMENTAL Autor: T. Johannsen, G. Mansfield, M. Kosters, S. Sataluri |
| RFC1609 Charting Networks in the X.500 Directory This document presents a model in which a communication network with all its related details and descriptions can be represented in the X.500 Directory. This memo defines an Experimental Protocol for the Internet community. | March 1994 Status: EXPERIMENTAL Autor: G. Mansfield, T. Johannsen, M. Knopper |
| RFC1610 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] | July 1994 Status: HISTORIC Autor: J. Postel |
| RFC1611 DNS Server MIB Extensions This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of extensions which instrument DNS name server functions. This memo was produced by the DNS working group. [STANDARDS-TRACK] | May 1994 Status: HISTORIC Autor: R. Austein, J. Saperia |
| RFC1612 DNS Resolver MIB Extensions This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of extensions which instrument DNS resolver functions. This memo was produced by the DNS working group. [STANDARDS-TRACK] | May 1994 Status: HISTORIC Autor: R. Austein, J. Saperia |
| RFC1613 cisco Systems X.25 over TCP (XOT) This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: J. Forster, G. Satz, G. Glick, R. Day |
| RFC1614 Network Access to Multimedia Information This report summarises the requirements of research and academic network users for network access to multimedia information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: C. Adie |
| RFC1615 Migrating from X.400(84) to X.400(88) This document compares X.400(88) to X.400(84) and describes what problems can be anticipated in the migration, especially considering the migration from the existing X.400(84) infrastructure created by the COSINE MHS project to an X.400(88) infrastructure. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: J. Houttuin, J. Craigie |
| RFC1616 X.400(1988) for the Academic and Research Community in Europe The report documents the results of a task force on X.400(1988) deployment of the RARE Mails and Messaging Work Group during the period from November 1992 until October 1993. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: RARE WG-MSG Task Force 88, E. Huizer, J. Romaguera |
| RFC1617 Naming and Structuring Guidelines for X.500 Directory Pilots This document defines a number of naming and structuring guidelines focused on White Pages usage. Alignment to these guidelines is recommended for directory pilots. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: P. Barker, S. Kille, T. Lenggenhager |
| RFC1618 PPP over ISDN This document describes the use of PPP over Integrated Services Digital Network (ISDN) switched circuits. [STANDARDS-TRACK] | May 1994 Status: PROPOSED STANDARD Autor: W. Simpson |
| RFC1619 PPP over SONET/SDH This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Heirarchy (SDH) circuits. [STANDARDS-TRACK] | May 1994 Status: PROPOSED STANDARD Autor: W. Simpson |
| RFC1620 Internet Architecture Extensions for Shared Media This memo discusses alternative approaches to extending the Internet architecture to eliminate some or all unnecessary hops. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: B. Braden, J. Postel, Y. Rekhter |
| RFC1621 Pip Near-term Architecture The purpose of this RFC and the companion RFC "Pip Header Processing" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: P. Francis |
| RFC1622 Pip Header Processing The purpose of this RFC and the companion RFC "Pip Near-term Architecture" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: P. Francis |
| RFC1623 Definitions of Managed Objects for the Ethernet-like Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK] | May 1994 Status: HISTORIC Autor: F. Kastenholz |
| RFC1624 Computation of the Internet Checksum via Incremental Update This memo describes an updated technique for incremental computation of the standard Internet checksum. It updates the method described in RFC 1141. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: A. Rijsinghani |
| RFC1625 WAIS over Z39.50-1988 The purpose of this memo is to initiate a discussion for a migration path of the WAIS technology from Z39.50-1988 Information Retrieval Service Definitions and Protocol Specification for Library Applications [1] to Z39.50-1992 [2] and then to Z39.50-1994 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1994 Status: INFORMATIONAL Autor: M. St. Pierre, J. Fullton, K. Gamiel, J. Goldman, B. Kahle, J. Kunze, H. Morris, F. Schiettecatte |
| RFC1626 Default IP MTU for use over ATM AAL5 There are a number of good reasons to have a reasonably large default MTU value for IP over ATM AAL5. This paper presents the default IP MIU for use over ATM AAL5. [STANDARDS-TRACK] | May 1994 Status: PROPOSED STANDARD Autor: R. Atkinson |
| RFC1627 Network 10 Considered Harmful (Some Practices Shouldn't be Codified) This document restates the arguments for maintaining a unique address space. Concerns for Internet architecture and operations, as well as IETF procedure, are explored. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1994 Status: INFORMATIONAL Autor: E. Lear, E. Fair, D. Crocker, T. Kessler |
| RFC1628 UPS Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing uninterruptible power supply (UPS) systems. [STANDARDS-TRACK] | May 1994 Status: INFORMATIONAL Autor: J. Case |
| RFC1629 Guidelines for OSI NSAP Allocation in the Internet This paper provides guidelines for allocating NSAP addresses in the Internet. The guidelines provided in this paper have been the basis for initial deployment of CLNP in the Internet, and have proven very valuable both as an aid to scaling of CLNP routing, and for address administration. [STANDARDS-TRACK] | May 1994 Status: DRAFT STANDARD Autor: R. Colella, R. Callon, E. Gardner, Y. Rekhter |
| RFC1630 Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web This document defines the syntax used by the World-Wide Web initiative to encode the names and addresses of objects on the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1994 Status: INFORMATIONAL Autor: T. Berners-Lee |
| RFC1631 The IP Network Address Translator (NAT) This memo proposes another short-term solution, address reuse, that complements CIDR or even makes it unnecessary. The address reuse solution is to place Network Address Translators (NAT) at the borders of stub domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: K. Egevang, P. Francis |
| RFC1632 A Revised Catalog of Available X.500 Implementations This document is the result of a survey that gathered new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. This document is a revision of RFC 1292. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: A. Getchell, S. Sataluri |
| RFC1633 Integrated Services in the Internet Architecture: an Overview This memo discusses a proposed extension to the Internet architecture and protocols to provide integrated services, i.e., to support real-time as well as the current non-real-time service of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1994 Status: INFORMATIONAL Autor: R. Braden, D. Clark, S. Shenker |
| RFC1634 Novell IPX Over Various WAN Media (IPXWAN) This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: M. Allen |
| RFC1635 How to Use Anonymous FTP This document provides information for the novice Internet user about using the File Transfer Protocol (FTP). It explains what FTP is, what anonymous FTP is, and what an anonymous FTP archive site is. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1994 Status: INFORMATIONAL Autor: P. Deutsch, A. Emtage, A. Marine |
| RFC1636 Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994 This document is a report on an Internet architecture workshop, initiated by the IAB and held at USC Information Sciences Institute on February 8-10, 1994. This workshop generally focused on security issues in the Internet architecture. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1994 Status: INFORMATIONAL Autor: R. Braden, D. Clark, S. Crocker, C. Huitema |
| RFC1637 DNS NSAP Resource Records This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. This memo defines an Experimental Protocol for the Internet community. | June 1994 Status: EXPERIMENTAL Autor: B. Manning, R. Colella |
| RFC1638 PPP Bridging Control Protocol (BCP) This document defines the Network Control Protocol for establishing and configuring Remote Bridging for PPP links. [STANDARDS-TRACK] | June 1994 Status: PROPOSED STANDARD Autor: F. Baker, R. Bowen |
| RFC1639 FTP Operation Over Big Address Records (FOOBAR) This RFC specifies a method for assigning addresses other than 32-bit IPv4 addresses to data ports through the specification of a "long Port (LPRT)" command and "Long Passive (LPSV)" reply, each having as its argument a <long-host-port>, which allows for additional address families, variable length network addresses and variable length port numbers. This memo defines an Experimental Protocol for the Internet community. | June 1994 Status: EXPERIMENTAL Autor: D. Piscitello |
| RFC1640 The Process for Organization of Internet Standards Working Group (POISED) This report, originally prepared in January 1993 provides a summary of the POISED WG, starting from the events leading to the formation of the WG to the end of 1992. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1994 Status: INFORMATIONAL Autor: S. Crocker |
| RFC1641 Using Unicode with MIME This document specifies the usage of Unicode within MIME. This memo defines an Experimental Protocol for the Internet community. | July 1994 Status: EXPERIMENTAL Autor: D. Goldsmith, M. Davis |
| RFC1642 UTF-7 - A Mail-Safe Transformation Format of Unicode This document describes a new transformation format of Unicode that contains only 7-bit ASCII characters and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. This memo defines an Experimental Protocol for the Internet community. | July 1994 Status: EXPERIMENTAL Autor: D. Goldsmith, M. Davis |
| RFC1643 Definitions of Managed Objects for the Ethernet-like Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK] | July 1994 Status: HISTORIC Autor: F. Kastenholz |
| RFC1644 T/TCP -- TCP Extensions for Transactions Functional Specification This memo specifies T/TCP, an experimental TCP extension for efficient transaction-oriented (request/response) service. This memo describes an Experimental Protocol for the Internet community. | July 1994 Status: HISTORIC Autor: R. Braden |
| RFC1645 Simple Network Paging Protocol - Version 2 This RFC suggests a simple way for delivering both alphanumeric and numeric pages (one-way) to radio paging terminals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1994 Status: INFORMATIONAL Autor: A. Gwinn |
| RFC1646 TN3270 Extensions for LUname and Printer Selection This document describes protocol extensions to TN3270. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1994 Status: INFORMATIONAL Autor: C. Graves, T. Butts, M. Angel |
| RFC1647 TN3270 Enhancements This document describes a protocol that more fully supports 3270 devices than do the existing tn3270 practices. [STANDARDS-TRACK] | July 1994 Status: PROPOSED STANDARD Autor: B. Kelly |
| RFC1648 Postmaster Convention for X.400 Operations This paper extends this concept to X.400 mail domains which have registered RFC 1327 mapping rules, and which therefore appear to have normal RFC822-style addresses. [STANDARDS-TRACK] | July 1994 Status: HISTORIC Autor: A. Cargille |
| RFC1649 Operational Requirements for X.400 Management Domains in the GO-MHS Community The goal of this document is to unite regionally operated X.400 services on the various continents into one GO-MHS Community (as seen from an end-user's point of view). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1994 Status: INFORMATIONAL Autor: R. Hagens, A. Hansen |
| RFC1650 Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing ethernet-like objects. [STANDARDS-TRACK] | August 1994 Status: PROPOSED STANDARD Autor: F. Kastenholz |
| RFC1651 SMTP Service Extensions This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK] | July 1994 Status: DRAFT STANDARD Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker |
| RFC1652 SMTP Service Extension for 8bit-MIMEtransport This memo defines an extension to the SMTP service whereby an SMTP content body consisting of text containing octets outside of the US- ASCII octet range (hex 00-7F) may be relayed using SMTP. [STANDARDS-TRACK] | July 1994 Status: DRAFT STANDARD Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker |
| RFC1653 SMTP Service Extension for Message Size Declaration This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK] | July 1994 Status: DRAFT STANDARD Autor: J. Klensin, N. Freed, K. Moore |
| RFC1654 A Border Gateway Protocol 4 (BGP-4) This document defines an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] | July 1994 Status: PROPOSED STANDARD Autor: Y. Rekhter, T. Li |
| RFC1655 Application of the Border Gateway Protocol in the Internet This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] | July 1994 Status: PROPOSED STANDARD Autor: Y. Rekhter, P. Gross |
| RFC1656 BGP-4 Protocol Document Roadmap and Implementation Experience Border Gateway Protocol v4 (BGP-4) [1] is an inter-Autonomous System routing protocol. It is built on experience gained with BGP as defined in RFC-1267 [2] and BGP usage in the connected Internet as described in RFC-1268 [3]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1994 Status: INFORMATIONAL Autor: P. Traina |
| RFC1657 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing the Border Gateway Protocol Version 4 or lower [1, 2]. [STANDARDS-TRACK] | July 1994 Status: DRAFT STANDARD Autor: S. Willis, J. Burruss, J. Chu |
| RFC1658 Definitions of Managed Objects for Character Stream Devices using SMIv2 This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of character stream devices. [STANDARDS-TRACK] | July 1994 Status: DRAFT STANDARD Autor: B. Stewart |
| RFC1659 Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2 This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of RS-232-like devices. [STANDARDS-TRACK] | July 1994 Status: DRAFT STANDARD Autor: B. Stewart |
| RFC1660 Definitions of Managed Objects for Parallel-printer-like Hardware Devices using SMIv2 This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of Parallel-printer- like devices. [STANDARDS-TRACK] | July 1994 Status: DRAFT STANDARD Autor: B. Stewart |
| RFC1661 The Point-to-Point Protocol (PPP) This document defines the PPP organization and methodology, and the PPP encapsulation, together with an extensible option negotiation mechanism which is able to negotiate a rich assortment of configuration parameters and provides additional management functions. [STANDARDS-TRACK] | July 1994 Status: STANDARD Autor: W. Simpson |
| RFC1662 PPP in HDLC-like Framing This document describes the use of HDLC-like framing for PPP encapsulated packets. [STANDARDS-TRACK] | July 1994 Status: STANDARD Autor: W. Simpson |
| RFC1663 PPP Reliable Transmission This document defines a method for negotiating and using Numbered-Mode, as defined by ISO 7776 [2], to provide a reliable serial link. [STANDARDS-TRACK] | July 1994 Status: PROPOSED STANDARD Autor: D. Rand |
| RFC1664 Using the Internet DNS to Distribute RFC1327 Mail Address Mapping Tables This memo defines how to store in the Internet Domain Name System the mapping information needed by e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. This memo defines an Experimental Protocol for the Internet community. | August 1994 Status: EXPERIMENTAL Autor: C. Allocchio, A. Bonito, B. Cole, S. Giordano, R. Hagens |
| RFC1665 Definitions of Managed Objects for SNA NAUs using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK] | July 1994 Status: PROPOSED STANDARD Autor: Z. Kielczewski, D. Kostick, K. Shih |
| RFC1666 Definitions of Managed Objects for SNA NAUs using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. [STANDARDS-TRACK] | August 1994 Status: HISTORIC Autor: Z. Kielczewski, D. Kostick, K. Shih |
| RFC1667 Modeling and Simulation Requirements for IPng This white paper summarizes the Distributed Interactive Simulation environment that is under development, with regard to its real-time nature, scope and magnitude of networking requirements. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: S. Symington, D. Wood, M. Pullen |
| RFC1668 Unified Routing Requirements for IPng The document provides requirements on the IPng from the perspective of the Unified Routing Architecture, as described in RFC 1322. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: D. Estrin, T. Li, Y. Rekhter |
| RFC1669 Market Viability as a IPng Criteria "Viability in the Marketplace" is an important requirement for any IPng candidate and this paper is an attempt to summarize some important factors in determing market viability of IPng proposals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: J. Curran |
| RFC1670 Input to IPng Engineering Considerations This white paper expresses some personal opinions on IPng engineering considerations, based on experience with DECnet Phase V transition. It suggests breaking down the IPng decisions and transition tasks into smaller parts so they can be tackled early by the relevant experts. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: D. Heagerty |
| RFC1671 IPng White Paper on Transition and Other Considerations This white paper outlines some general requirements for IPng in selected areas. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: B. Carpenter |
| RFC1672 Accounting Requirements for IPng This white paper discusses accounting requirements for IPng. It recommends that all IPng packets carry accounting tags, which would vary in size. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: N. Brownlee |
| RFC1673 Electric Power Research Institute Comments on IPng This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: R. Skelton |
| RFC1674 A Cellular Industry View of IPng This is a draft of the requirements for IPng as envisioned by representatives of the Cellular Digital Packet Data (CDPD) consortium of service providers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: M. Taylor |
| RFC1675 Security Concerns for IPng A number of the candidates for IPng have some features that are somewhat worrisome from a security perspective. While it is not necessary that IPng be an improvement over IPv4, it is mandatory that it not make things worse. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: S. Bellovin |
| RFC1676 INFN Requirements for an IPng With this paper we would like to emphasize the key points that we would to consider if charged with IPng plan. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: A. Ghiselli, D. Salomoni, C. Vistoli |
| RFC1677 Tactical Radio Frequency Communication Requirements for IPng This paper describes requirements for Internet Protocol next generation (IPng) candidates with respect to their application to military tactical radio frequency (RF) communication networks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: B. Adamson |
| RFC1678 IPng Requirements of Large Corporate Networks This draft summarizes some of the requirements of large corporate networks for the next generation of the Internet protcol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: E. Britton, J. Tavs |
| RFC1679 HPN Working Group Input to the IPng Requirements Solicitation The purpose of this document is to provide what the HPN working group perceives as requirements for an IPng protocol set. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: D. Green, P. Irey, D. Marlow, K. O'Donoghue |
| RFC1680 IPng Support for ATM Services This white paper describes engineering considerations for IPng as solicited by RFC 1550 [1]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: C. Brazdziunas |
| RFC1681 On Many Addresses per Host This document was submitted to the IETF IPng area in response to RFC 1550.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: S. Bellovin |
| RFC1682 IPng BSD Host Implementation Analysis This IPng white paper, IPng BSD Host Implementation Analysis, was submitted to the IPng Directorate to provide a BSD host point of reference to assist with the engineering considerations during the IETF process to select an IPng proposal. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: J. Bound |
| RFC1683 Multiprotocol Interoperability In IPng In this document, we identify several features that affect a protocol's ability to operate in a multiprotocol environment and propose the incorporation of these features into IPng. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: R. Clark, M. Ammar, K. Calvert |
| RFC1684 Introduction to White Pages Services based on X.500 The document provides an introduction to the international ITU-T (formerly CCITT) X.500 and ISO 9594 standard, which is particularly suited for providing an integrated local and global electronic White Pages Service. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: P. Jurg |
| RFC1685 Writing X.400 O/R Names There is a need for human beings who use X.400 systems to be able to write down O/R names in a uniform way. This memo is a discussion of this topic. This memo provides information for the Internet Community. It does not specify an Internet Standard of any kind. | August 1994 Status: INFORMATIONAL Autor: H. Alvestrand |
| RFC1686 IPng Requirements: A Cable Television Industry Viewpoint This paper provides comments on topics related to the IPng requirements and selection criteria from a cable television industry viewpoint. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: M. Vecchi |
| RFC1687 A Large Corporate User's View of IPng The goal of this paper is to examine the implications of IPng from the point of view of Fortune 100 corporations which have heavily invested in TCP/IP technology in order to achieve their (non-computer related) business goals.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: E. Fleischman |
| RFC1688 IPng Mobility Considerations This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: W. Simpson |
| RFC1689 A Status Report on Networked Information Retrieval: Tools and Groups The purpose of this report is to increase the awareness of Networked Information Retrieval by bringing together in one place information about the various networked information retrieval tools, their developers, interested organisations, and other activities that relate to the production, dissemination, and support of NIR tools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: J. Foster |
| RFC1690 Introducing the Internet Engineering and Planning Group (IEPG) This memo introduces the IEPG to the Internet Community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: G. Huston |
| RFC1691 The Document Architecture for the Cornell Digital Library This memo defines an architecture for the storage and retrieval of the digital representations for books, journals, photographic images, etc., which are collected in a large organized digital library. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1994 Status: INFORMATIONAL Autor: W. Turner |
| RFC1692 Transport Multiplexing Protocol (TMux) This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1994 Status: HISTORIC Autor: P. Cameron, D. Crocker, D. Cohen, J. Postel |
| RFC1693 An Extension to TCP : Partial Order Service This RFC introduces a new transport mechanism for TCP based upon partial ordering. The aim is to present the concepts of partial ordering and promote discussions on its usefulness in network communications. This memo defines an Experimental Protocol for the Internet community. | November 1994 Status: HISTORIC Autor: T. Connolly, P. Amer, P. Conrad |
| RFC1694 Definitions of Managed Objects for SMDS Interfaces using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing objects for SMDS access interfaces. [STANDARDS-TRACK] | August 1994 Status: DRAFT STANDARD Autor: T. Brown, K. Tesink |
| RFC1695 Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK] | August 1994 Status: PROPOSED STANDARD Autor: M. Ahmed, K. Tesink |
| RFC1696 Modem Management Information Base (MIB) using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing dial-up modems and similar dial-up devices. [STANDARDS-TRACK] | August 1994 Status: HISTORIC Autor: J. Barnes, L. Brown, R. Royston, S. Waldbusser |
| RFC1697 Relational Database Management System (RDBMS) Management Information Base (MIB) using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing relational database (RDBMS) implementations. [STANDARDS-TRACK] | August 1994 Status: PROPOSED STANDARD Autor: D. Brower, B. Purvy, A. Daniel, M. Sinykin, J. Smith |
| RFC1698 Octet Sequences for Upper-Layer OSI to Support Basic Communications Applications This document states particular octet sequences that comprise the OSI upper-layer protocols (Session, Presentation and ACSE) when used to support applications with "basic communications requirements". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: P. Furniss |
| RFC1699 Summary of 1600-1699 | January 1997 Status: INFORMATIONAL Autor: J. Elliott |
| RFC1700 Assigned Numbers This RFC is a snapshot of the ongoing process of the assignment of protocol parameters for the Internet protocol suite. To make the current information readily available the assignments are kept up-to- date in a set of online text files. This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. | October 1994 Status: HISTORIC Autor: J. Reynolds, J. Postel |
| RFC1701 Generic Routing Encapsulation (GRE) This document specifies a protocol for performing encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: S. Hanks, T. Li, D. Farinacci, P. Traina |
| RFC1702 Generic Routing Encapsulation over IPv4 networks This memo addresses the case of using IP as the delivery protocol or the payload protocol and the special case of IP as both the delivery and payload. This memo also describes using IP addresses and autonomous system numbers as part of a GRE source route. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: S. Hanks, T. Li, D. Farinacci, P. Traina |
| RFC1703 Principles of Operation for the TPC.INT Subdomain: Radio Paging -- Technical Procedures This memo describes a technique for radio paging using the Internet mail infrastructure. In particular, this memo focuses on the case in which radio pagers are identified via the international telephone network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: M. Rose |
| RFC1704 On Internet Authentication This document describes a spectrum of authentication technologies and provides suggestions to protocol developers on what kinds of authentication might be suitable for some kinds of protocols and applications used in the Internet. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: N. Haller, R. Atkinson |
| RFC1705 Six Virtual Inches to the Left: The Problem with IPng This document was submitted to the IETF IPng area in response to RFC 1550. This RFC suggests that a new version of TCP (TCPng), and UDP, be developed and deployed. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: R. Carlson, D. Ficarella |
| RFC1706 DNS NSAP Resource Records This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. The RR may be used with any NSAP address format. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: B. Manning, R. Colella |
| RFC1707 CATNIP: Common Architecture for the Internet This document was submitted to the IETF IPng area in response to RFC 1550. This paper describes a common architecture for the network layer protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: M. McGovern, R. Ullmann |
| RFC1708 NTP PICS PROFORMA - For the Network Time Protocol Version 3 This RFC describes a PICS Proforma translated into an Internet acceptable form. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: D. Gowin |
| RFC1709 K-12 Internetworking Guidelines The K-12 community traditionally has not had this level of staffing available for telecommunications planning. This document is intended to bridge that gap and provides a recommended technical direction, an introduction to the role the Internet now plays in K-12 education and technical guidelines for building a campus data communications infrastructure that provides internetworking services and connections to the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1994 Status: INFORMATIONAL Autor: J. Gargano, D. Wasley |
| RFC1710 Simple Internet Protocol Plus White Paper This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: R. Hinden |
| RFC1711 Classifications in E-mail Routing This paper presents a classification for e-mail routing issues. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1994 Status: INFORMATIONAL Autor: J. Houttuin |
| RFC1712 DNS Encoding of Geographical Location This document defines the format of a new Resource Record (RR) for the Domain Naming System (DNS), and reserves a corresponding DNS type mnemonic and numerical code. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | November 1994 Status: EXPERIMENTAL Autor: C. Farrell, M. Schulze, S. Pleitner, D. Baldoni |
| RFC1713 Tools for DNS debugging Although widely used (and most of the times unnoticed), DNS (Domain Name System) is too much overlooked, in the sense that people, especially administrators, tend to ignore possible anomalies as long as applications that need name-to-address mapping continue to work. This document presents some tools available for domain administrators to detect and correct those anomalies. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1994 Status: INFORMATIONAL Autor: A. Romao |
| RFC1714 Referral Whois Protocol (RWhois) This memo describes version 1.0 of the client/server interaction of RWhois. RWhois provides a distributed system for the display of hierarchical information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1994 Status: INFORMATIONAL Autor: S. Williamson, M. Kosters |
| RFC1715 The H Ratio for Address Assignment Efficiency This document was submitted to the IETF IPng area in response to RFC 1550. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1994 Status: INFORMATIONAL Autor: C. Huitema |
| RFC1716 Towards Requirements for IP Routers The goal of this work is to replace RFC-1009, Requirements for Internet Gateways ([INTRO:1]) with a new document. It defines and discusses requirements for devices which perform the network layer forwarding function of the Internet protocol suite. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1994 Status: INFORMATIONAL Autor: P. Almquist, F. Kastenholz |
| RFC1717 The PPP Multilink Protocol (MP) This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. [STANDARDS-TRACK] | November 1994 Status: PROPOSED STANDARD Autor: K. Sklower, B. Lloyd, G. McGregor, D. Carr |
| RFC1718 The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17] | November 1994 Status: INFORMATIONAL Autor: IETF Secretariat, G. Malkin |
| RFC1719 A Direction for IPng This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: P. Gross |
| RFC1720 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] | November 1994 Status: HISTORIC Autor: J. Postel |
| RFC1721 RIP Version 2 Protocol Analysis As required by Routing Protocol Criteria (RFC 1264), this report documents the key features of the RIP-2 protocol and the current implementation experience. This report is a prerequisite to advancing RIP-2 on the standards track. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1994 Status: INFORMATIONAL Autor: G. Malkin |
| RFC1722 RIP Version 2 Protocol Applicability Statement As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIP-2 protocol within the Internet. This report is a prerequisite to advancing RIP-2 on the standards track. [STANDARDS-TRACK] | November 1994 Status: STANDARD Autor: G. Malkin |
| RFC1723 RIP Version 2 - Carrying Additional Information This document specifies an extension of the Routing Information Protocol (RIP), o expand the amount of useful information carried in RIP messages and to add a measure of security. This memo obsoletes RFC 1388, which specifies an update to the "Routing Information Protocol" STD 34, RFC 1058. [STANDARDS-TRACK] | November 1994 Status: STANDARD Autor: G. Malkin |
| RFC1724 RIP Version 2 MIB Extension This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing RIP Version 2. [STANDARDS-TRACK] | November 1994 Status: DRAFT STANDARD Autor: G. Malkin, F. Baker |
| RFC1725 Post Office Protocol - Version 3 This memo is a revision to RFC 1460, a Draft Standard. [STANDARDS-TRACK] | November 1994 Status: STANDARD Autor: J. Myers, M. Rose |
| RFC1726 Technical Criteria for Choosing IP The Next Generation (IPng) This RFC specifies criteria related to mobility for consideration in design and selection of the Next Generation of IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: C. Partridge, F. Kastenholz |
| RFC1727 A Vision of an Integrated Internet Information Service This paper lays out a vision of how Internet information services might be integrated over the next few years, and discusses in some detail what steps will be needed to achieve this integration. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: C. Weider, P. Deutsch |
| RFC1728 Resource Transponders This paper describes an automatic mechanism, the resource transponder, for maintaining resource location information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: C. Weider |
| RFC1729 Using the Z39.50 Information Retrieval Protocol This memo describes an approach to the implementation of the ANSI/NISO Z39.50-1992 Standard for Information Retrieval in the TCP/IP environment which is currently in wide use by the Z39.50 implementor community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: C. Lynch |
| RFC1730 Internet Message Access Protocol - Version 4 The Internet Message Access Protocol, Version 4 (IMAP4) allows a client to access and manipulate electronic mail messages on a server. IMAP4 permits manipulation of remote message folders, called "mailboxes", in a way that is functionally equivalent to local mailboxes. IMAP4 also provides the capability for an offline client to resynchronize with the server. [STANDARDS-TRACK] | December 1994 Status: PROPOSED STANDARD Autor: M. Crispin |
| RFC1731 IMAP4 Authentication Mechanisms The Internet Message Access Protocol, Version 4 [IMAP4] contains the AUTHENTICATE command, for identifying and authenticating a user to an IMAP4 server and for optionally negotiating a protection mechanism for subsequent protocol interactions. This document describes several authentication mechanisms for use by the IMAP4 AUTHENTICATE command. [STANDARDS-TRACK] | December 1994 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC1732 IMAP4 Compatibility with IMAP2 and IMAP2bis This is a summary of hints and recommendations to enable an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: M. Crispin |
| RFC1733 Distributed Electronic Mail Models in IMAP4 There are three fundamental models of client/server email: offline, online, and disconnected use. IMAP4 can be used in any one of these three models. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: M. Crispin |
| RFC1734 POP3 AUTHentication command This document describes the optional AUTH command, for indicating an authentication mechanism to the server, performing an authentication protocol exchange, and optionally negotiating a protection mechanism for subsequent protocol interactions. [STANDARDS-TRACK] | December 1994 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC1735 NBMA Address Resolution Protocol (NARP) This document describes the NBMA Address Resolution Protocol (NARP). NARP can be used by a source terminal (host or router) connected to a Non-Broadcast, Multi-Access link layer (NBMA) network to find out the NBMA addresses of the a destination terminal provided that the destination terminal is connected to the same NBMA network. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: EXPERIMENTAL Autor: J. Heinanen, R. Govindan |
| RFC1736 Functional Recommendations for Internet Resource Locators This document specifies a minimum set of requirements for Internet resource locators, which convey location and access information for resources. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1995 Status: INFORMATIONAL Autor: J. Kunze |
| RFC1737 Functional Requirements for Uniform Resource Names This document specifies a minimum set of requirements for a kind of Internet resource identifier known as Uniform Resource Names (URNs). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: K. Sollins, L. Masinter |
| RFC1738 Uniform Resource Locators (URL) This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet. [STANDARDS-TRACK] | December 1994 Status: PROPOSED STANDARD Autor: T. Berners-Lee, L. Masinter, M. McCahill |
| RFC1739 A Primer On Internet and TCP/IP Tools This memo is an introductory guide to some of the TCP/IP and Internet tools and utilities that allow users to access the wide variety of information on the network, from determining if a particular host is up to viewing a multimedia thesis on foreign policy. It also describes discussion lists accessible from the Internet, ways to obtain Internet documents, and resources that help users weave their way through the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: G. Kessler, S. Shepard |
| RFC1740 MIME Encapsulation of Macintosh Files - MacMIME This memo describes the format to use when sending Apple Macintosh files via MIME [BORE93]. [STANDARDS-TRACK] | December 1994 Status: PROPOSED STANDARD Autor: P. Faltstrom, D. Crocker, E. Fair |
| RFC1741 MIME Content Type for BinHex Encoded Files This memo describes the format to use when sending BinHex4.0 files via MIME [BORE93]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: P. Faltstrom, D. Crocker, E. Fair |
| RFC1742 AppleTalk Management Information Base II This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing AppleTalk networks. [STANDARDS-TRACK] | January 1995 Status: HISTORIC Autor: S. Waldbusser, K. Frisa |
| RFC1743 IEEE 802.5 MIB using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK] | December 1994 Status: DRAFT STANDARD Autor: K. McCloghrie, E. Decker |
| RFC1744 Observations on the Management of the Internet Address Space This memo examines some of the issues associated with the current management practices of the Internet IPv4 address space, and examines the potential outcomes of these practices as the unallocated address pool shrinks in size. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: G. Huston |
| RFC1745 BGP4/IDRP for IP---OSPF Interaction This memo defines the various criteria to be used when designing an Autonomous System Border Router (ASBR) that will run either BGP4 or IDRP for IP with other ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK] | December 1994 Status: HISTORIC Autor: K. Varadhan, S. Hares, Y. Rekhter |
| RFC1746 Ways to Define User Expectations This paper covers basic fundamentals that must be understood when one defines, interprets, or implements methods to control user expectations on or over the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: B. Manning, D. Perkins |
| RFC1747 Definitions of Managed Objects for SNA Data Link Control (SDLC) using SMIv2 This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for managing the configuration, monitoring and control of data link controls in an SNA environment. [STANDARDS-TRACK] | January 1995 Status: HISTORIC Autor: J. Hilgeman, S. Nix, A. Bartky, W. Clark |
| RFC1748 IEEE 802.5 MIB using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing subnetworks which use the IEEE 802.5 Token Ring technology described in 802.5 Token Ring Access Method and Physical Layer Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK] | December 1994 Status: DRAFT STANDARD Autor: K. McCloghrie, E. Decker |
| RFC1749 IEEE 802.5 Station Source Routing MIB using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used by IEEE 802.5 end-stations for managing source routes on a Token Ring network where IEEE source- routing is in use. [STANDARDS-TRACK] | December 1994 Status: HISTORIC Autor: K. McCloghrie, F. Baker, E. Decker |
| RFC1750 Randomness Recommendations for Security Choosing random quantities to foil a resourceful and motivated adversary is surprisingly difficult. This paper points out many pitfalls in using traditional pseudo-random number generation techniques for choosing such quantities. It recommends the use of truly random hardware techniques and shows that the existing hardware on many systems can be used for this purpose. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: D. Eastlake 3rd, S. Crocker, J. Schiller |
| RFC1751 A Convention for Human-Readable 128-bit Keys This memo proposes a convention for use with Internet applications & protocols using 128-bit cryptographic keys. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: D. McDonald |
| RFC1752 The Recommendation for the IP Next Generation Protocol This document presents the recommendation of the IPng Area Directors on what should be used to replace the current version of the Internet Protocol. [STANDARDS-TRACK] | January 1995 Status: PROPOSED STANDARD Autor: S. Bradner, A. Mankin |
| RFC1753 IPng Technical Requirements Of the Nimrod Routing and Addressing Architecture This document presents the requirements that the Nimrod routing and addressing architecture has upon the internetwork layer protocol. To be most useful to Nimrod, any protocol selected as the IPng should satisfy these requirements. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1994 Status: INFORMATIONAL Autor: N. Chiappa |
| RFC1754 IP over ATM Working Group's Recommendations for the ATM Forum's Multiprotocol BOF Version 1 This document represents an initial list of requirements submitted to the ATM Forum's Multiprotocol BOF for the operation of IP over ATM networks as determined by the IETF IP over ATM Working Group and other working groups. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1995 Status: INFORMATIONAL Autor: M. Laubach |
| RFC1755 ATM Signaling Support for IP over ATM This memo describes the ATM call control signaling exchanges needed to support Classical IP over ATM implementations as described in RFC 1577. [STANDARDS-TRACK] | February 1995 Status: PROPOSED STANDARD Autor: M. Perez, F. Liaw, A. Mankin, E. Hoffman, D. Grossman, A. Malis |
| RFC1756 Remote Write Protocol - Version 1.0 This document describes a simple Remote Write Protocol (RWP). This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | January 1995 Status: EXPERIMENTAL Autor: T. Rinne |
| RFC1757 Remote Network Monitoring Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK] | February 1995 Status: DRAFT STANDARD Autor: S. Waldbusser |
| RFC1758 NADF Standing Documents: A Brief Overview The purpose of this document is to provide a brief overview of the NADF's Standing Document series. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1995 Status: INFORMATIONAL Autor: The North American Directory Forum |
| RFC1759 Printer MIB A printer is the physical device that takes media from an input source, produces marks on that media according to some page description or page control language and puts the result in some output destination, possibly with finishing applied. The information needed in the management of the physical printer and the management of a printing job overlap highly and many of the tasks in each management area require the same or similar information. [STANDARDS-TRACK] | March 1995 Status: PROPOSED STANDARD Autor: R. Smith, F. Wright, T. Hastings, S. Zilles, J. Gyllenskog |
| RFC1760 The S/KEY One-Time Password System This document describes the S/KEY* One-Time Password system as released for public use by Bellcore. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1995 Status: INFORMATIONAL Autor: N. Haller |
| RFC1761 Snoop Version 2 Packet Capture File Format This paper describes the file format used by "snoop", a packet monitoring and capture program developed by Sun. This paper is provided so that people can write compatible programs to generate and interpret snoop packet capture files. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1995 Status: INFORMATIONAL Autor: B. Callaghan, R. Gilligan |
| RFC1762 The PPP DECnet Phase IV Control Protocol (DNCP) This document defines the NCP for establishing and configuring Digital's DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This document applies only to DNA Phase IV Routing messages (both data and control), and not to other DNA Phase IV protocols (MOP, LAT, etc). [STANDARDS-TRACK] | March 1995 Status: DRAFT STANDARD Autor: S. Senum |
| RFC1763 The PPP Banyan Vines Control Protocol (BVCP) This document defines the Network Control Protocol for establishing and configuring the Banyan VINES protocol over PPP. [STANDARDS-TRACK] | March 1995 Status: HISTORIC Autor: S. Senum |
| RFC1764 The PPP XNS IDP Control Protocol (XNSCP) This document defines the Network Control Protocol for establishing and configuring the Xerox Network Systems (XNS) Internet Datagram Protocol (IDP) over PPP. [STANDARDS-TRACK] | March 1995 Status: HISTORIC Autor: S. Senum |
| RFC1765 OSPF Database Overflow This memo details a way of gracefully handling unanticipated database overflows. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: EXPERIMENTAL Autor: J. Moy |
| RFC1766 Tags for the Identification of Languages This document describes a language tag for use in cases where it is desired to indicate the language used in an information object. [STANDARDS-TRACK] | March 1995 Status: PROPOSED STANDARD Autor: H. Alvestrand |
| RFC1767 MIME Encapsulation of EDI Objects Since there are many different EDI specifications, the current document defines three distinct categories as three different MIME content-types. [STANDARDS-TRACK] | March 1995 Status: PROPOSED STANDARD Autor: D. Crocker |
| RFC1768 Host Group Extensions for CLNP Multicasting This memo provides a specification for multicast extensions to the CLNP protocol similar to those provided to IP by RFC1112. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: EXPERIMENTAL Autor: D. Marlow |
| RFC1769 Simple Network Time Protocol (SNTP) This memorandum describes the Simple Network Time Protocol (SNTP), which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: INFORMATIONAL Autor: D. Mills |
| RFC1770 IPv4 Option for Sender Directed Multi-Destination Delivery This memo defines an IPv4 option to provide a sender directed multi- destination delivery mechanism called Selective Directed Broadcast Mode (SDBM). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: INFORMATIONAL Autor: C. Graff |
| RFC1771 A Border Gateway Protocol 4 (BGP-4) This document, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK] | March 1995 Status: DRAFT STANDARD Autor: Y. Rekhter, T. Li |
| RFC1772 Application of the Border Gateway Protocol in the Internet This document, together with its companion document, "A Border Gateway Protocol 4 (BGP-4)", define an inter-autonomous system routing protocol for the Internet. This document describes the usage of the BGP in the Internet. [STANDARDS-TRACK] | March 1995 Status: DRAFT STANDARD Autor: Y. Rekhter, P. Gross |
| RFC1773 Experience with the BGP-4 protocol The purpose of this memo is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). This report documents experience with BGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: INFORMATIONAL Autor: P. Traina |
| RFC1774 BGP-4 Protocol Analysis The purpose of this report is to document how the requirements for advancing a routing protocol to Draft Standard have been satisfied by the Border Gateway Protocol version 4 (BGP-4). This report summarizes the key features of BGP, and analyzes the protocol with respect to scaling and performance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: INFORMATIONAL Autor: P. Traina |
| RFC1775 To Be "On" the Internet The Internet permits different levels of access for consumers and providers of service. The nature of those differences is quite important in the capabilities They afford. Hence, it is appropriate to provide terminology that distinguishes among the range, so that the Internet community can gain some clarity when distinguishing whether a user (or an organization) is "on" the Internet. This document suggests four terms, for distinguishing the major classes of access. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: INFORMATIONAL Autor: D. Crocker |
| RFC1776 The Address is the Message Declaring that the address is the message, the IPng WG has selected a packet format which includes 1696 bytes of address space. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1995 Status: INFORMATIONAL Autor: S. Crocker |
| RFC1777 Lightweight Directory Access Protocol The protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP).This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself. [STANDARDS-TRACK] | March 1995 Status: HISTORIC Autor: W. Yeong, T. Howes, S. Kille |
| RFC1778 The String Representation of Standard Attribute Syntaxes The Lightweight Directory Access Protocol (LDAP) requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render X.500 Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes. [STANDARDS-TRACK] | March 1995 Status: HISTORIC Autor: T. Howes, S. Kille, W. Yeong, C. Robbins |
| RFC1779 A String Representation of Distinguished Names The OSI Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1. When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. This specification defines a string format for representing names, which is designed to give a clean representation of commonly used names, whilst being able to represent any distinguished name. [STANDARDS-TRACK] | March 1995 Status: HISTORIC Autor: S. Kille |
| RFC1780 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] | March 1995 Status: HISTORIC Autor: J. Postel |
| RFC1781 Using the OSI Directory to Achieve User Friendly Naming This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. [STANDARDS-TRACK] | March 1995 Status: HISTORIC Autor: S. Kille |
| RFC1782 TFTP Option Extension The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer. | March 1995 Status: PROPOSED STANDARD Autor: G. Malkin, A. Harkin |
| RFC1783 TFTP Blocksize Option This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK] | March 1995 Status: PROPOSED STANDARD Autor: G. Malkin, A. Harkin |
| RFC1784 TFTP Timeout Interval and Transfer Size Options This document describes two TFTP options. The first allows the client and server to negotiate the Timeout Interval. The second allows the side receiving the file to determine the ultimate size of the transfer before it begins. [STANDARDS-TRACK] | March 1995 Status: PROPOSED STANDARD Autor: G. Malkin, A. Harkin |
| RFC1785 TFTP Option Negotiation Analysis This document was written to allay concerns that the presence of options in a TFTP Request packet might cause pathological behavior on servers which do not support TFTP option negotiation. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: INFORMATIONAL Autor: G. Malkin, A. Harkin |
| RFC1786 Representation of IP Routing Policies in a Routing Registry (ripe-81++) This document is an update to the original `ripe-81' proposal for representing and storing routing polices within the RIPE database. It incorporates several extensions proposed by Merit Inc. and gives details of a generalized IP routing policy representation to be used by all Internet routing registries. It acts as both tutorial and provides details of database objects and attributes that use and make up a routing registry. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1995 Status: INFORMATIONAL Autor: T. Bates, E. Gerich, L. Joncheray, J-M. Jouanigot, D. Karrenberg, M. Terpstra, J. Yu |
| RFC1787 Routing in a Multi-provider Internet This document presents some of the issues related to network layer routing in a multi-provider Internet, and specifically to the unicast routing. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1995 Status: INFORMATIONAL Autor: Y. Rekhter |
| RFC1788 ICMP Domain Name Messages This document specifies ICMP messages for learning the Fully Qualified Domain Name associated with an IP address. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. | April 1995 Status: EXPERIMENTAL Autor: W. Simpson |
| RFC1789 INETPhone: Telephone Services and Servers on Internet This RFC presents a true telephone service, called INETPhone, which supports voice communication through the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1995 Status: INFORMATIONAL Autor: C. Yang |
| RFC1790 An Agreement between the Internet Society and Sun Microsystems, Inc. in the Matter of ONC RPC and XDR Protocols This RFC is an official public record of an agreement between SUN Microsystems and the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1995 Status: INFORMATIONAL Autor: V. Cerf |
| RFC1791 TCP And UDP Over IPX Networks With Fixed Path MTU TCP/IPX allows TCP/IP applications to run over IPX networks by letting TCP and UDP run over IPX. And this memo specifies the packet format and operational procedures for running TCP and UDP over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. | April 1995 Status: EXPERIMENTAL Autor: T. Sung |
| RFC1792 TCP/IPX Connection Mib Specification New MIB objects, tcpIpxConnTable, udpIpxTable, tcpUnspecConnTable and udpUnspecTable are presented in this paper, to be used in place of tcpConnTable and udpListenerTable when TCP and UDP are running over IPX. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. | April 1995 Status: EXPERIMENTAL Autor: T. Sung |
| RFC1793 Extending OSPF to Support Demand Circuits This memo defines enhancements to the OSPF protocol that allow efficient operation over "demand circuits". [STANDARDS-TRACK] | April 1995 Status: PROPOSED STANDARD Autor: J. Moy |
| RFC1794 DNS Support for Load Balancing This RFC is meant to first chronicle a foray into the IETF DNS Working Group, discuss other possible alternatives to provide/simulate load balancing support for DNS, and to provide an ultimate, flexible solution for providing DNS support for balancing loads of many types. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1995 Status: INFORMATIONAL Autor: T. Brisco |
| RFC1795 Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1 This RFC describes use of Data Link Switching over TCP/IP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1995 Status: INFORMATIONAL Autor: L. Wells, A. Bartky |
| RFC1796 Not All RFCs are Standards This document discusses the relationship of the Request for Comments (RFCs) notes to Internet Standards. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1995 Status: INFORMATIONAL Autor: C. Huitema, J. Postel, S. Crocker |
| RFC1797 Class A Subnet Experiment There appears to be some interest in experimenting with subnetting the class A addresses. It is suggested that conducting an experiment now to identify and fix any software that does not properly handle subnetted class A addresses would be useful and important. This document defines an Experimental Protocol for the Internet community. This does not specify an Internet standard of any kind. | April 1995 Status: EXPERIMENTAL Autor: Internet Assigned Numbers Authority (IANA) |
| RFC1798 Connection-less Lightweight X.500 Directory Access Protocol The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK] | June 1995 Status: HISTORIC Autor: A. Young |
| RFC1799 Request for Comments Summary RFC Numbers 1700-1799 | January 1997 Status: INFORMATIONAL Autor: M. Kennedy |
| RFC1800 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] | July 1995 Status: HISTORIC Autor: J. Postel |
| RFC1801 MHS use of the X.500 Directory to support MHS Routing The key problem in routing is to map from an O/R Address onto an MTA (next hop). This shall be an MTA which in some sense is "nearer" to the destination UA. This is done repeatedly until the message can be directly delivered to the recipient UA. This memo defines an Experimental Protocol for the Internet community. | June 1995 Status: EXPERIMENTAL Autor: S. Kille |
| RFC1802 Introducing Project Long Bud: Internet Pilot Project for the Deployment of X.500 Directory Information in Support of X.400 Routing This memo describes a proposed Internet Pilot Project that seeks to prove the MHS-DS approach on a larger scale. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: H. Alvestrand, K. Jordan, S. Langlois, J. Romaguera |
| RFC1803 Recommendations for an X.500 Production Directory Service This document contains a set of basic recommendations for a country- level X.500 DSA. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: R. Wright, A. Getchell, T. Howes, S. Sataluri, P. Yee, W. Yeong |
| RFC1804 Schema Publishing in X.500 Directory In this document we propose a solution using the existing mechanisms of the directory [1] itself. We present a naming scheme for naming schema objects and a meta-schema for storing schema objects in the directory. This memo defines an Experimental Protocol for the Internet community. | June 1995 Status: EXPERIMENTAL Autor: G. Mansfield, P. Rajeev, S. Raghavan, T. Howes |
| RFC1805 Location-Independent Data/Software Integrity Protocol This memo describes a protocol for adding integrity assurance to files that are distributed across the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: A. Rubin |
| RFC1806 Communicating Presentation Information in Internet Messages: The Content-Disposition Header This memo provides a mechanism whereby messages conforming to the [RFC 1521] ("MIME") specification can convey presentational information. This memo defines an Experimental Protocol for the Internet community. | June 1995 Status: EXPERIMENTAL Autor: R. Troost, S. Dorner |
| RFC1807 A Format for Bibliographic Records This RFC defines a format for bibliographic records describing technical reports. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: R. Lasher, D. Cohen |
| RFC1808 Relative Uniform Resource Locators In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance. This document defines the syntax and semantics for such Relative Uniform Resource Locators. [STANDARDS-TRACK] | June 1995 Status: PROPOSED STANDARD Autor: R. Fielding |
| RFC1809 Using the Flow Label Field in IPv6 The purpose of this memo is to distill various opinions and suggestions of the End-to-End Research Group regarding the handling of Flow Labels into a set of suggestions for IPv6. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: C. Partridge |
| RFC1810 Report on MD5 Performance This RFC addresses how fast MD5 can be implemented in software and hardware, and whether it supports currently available IP bandwidth. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: J. Touch |
| RFC1811 U.S. Government Internet Domain Names This document describes the registration policies for the top-level domain ".GOV". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: Federal Networking Council |
| RFC1812 Requirements for IP Version 4 Routers This memo defines and discusses requirements for devices that perform the network layer forwarding function of the Internet protocol suite. [STANDARDS-TRACK] | June 1995 Status: PROPOSED STANDARD Autor: F. Baker |
| RFC1813 NFS Version 3 Protocol Specification This paper describes the NFS version 3 protocol. This paper is provided so that people can write compatible implementations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: B. Callaghan, B. Pawlowski, P. Staubach |
| RFC1814 Unique Addresses are Good The IAB suggests that while RFC 1597 establishes reserved IP address space for the use of private networks which are isolated and will remain isolated from the Internet, any enterprise which anticipates external connectivity to the Internet should apply for a globally unique address from an Internet registry or service provider. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1995 Status: INFORMATIONAL Autor: E. Gerich |
| RFC1815 Character Sets ISO-10646 and ISO-10646-J-1 For the practical use of ISO 10646, a lot of external profiling such as restriction of characters, restriction of combination of characters and addition of language information is necessary. This memo provides information on such profiling, along with charset names to each profiled instance. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1995 Status: INFORMATIONAL Autor: M. Ohta |
| RFC1816 U.S. Government Internet Domain Names This memo provides an update and clarification to RFC 1811. This document describes the registration policies for the top-level domain ".GOV". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: Federal Networking Council |
| RFC1817 CIDR and Classful Routing This document represents the IAB's (Internet Architecture Board) evaluation of the current and near term implications of CIDR on organizations that use Classful routing technology. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: HISTORIC Autor: Y. Rekhter |
| RFC1818 Best Current Practices This document describes a new series of documents which describe best current practices for the Internet community. Documents in this series carry the endorsement of the Internet Engineering Steering Group (IESG). | August 1995 Status: HISTORIC Autor: J. Postel, T. Li, Y. Rekhter |
| RFC1819 Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+ This memo contains a revised specification of the Internet STream Protocol Version 2 (ST2). This memo defines an Experimental Protocol for the Internet community. | August 1995 Status: EXPERIMENTAL Autor: L. Delgrossi, L. Berger |
| RFC1820 Multimedia E-mail (MIME) User Agent Checklist This document presents a checklist to facilitate evaluation of MIME capable User Agents. Access to a MIME test-responder, that generates test-messages is described. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: E. Huizer |
| RFC1821 Integration of Real-time Services in an IP-ATM Network Architecture The purpose of this paper is to provide a clear statement of what issues need to be addressed in interfacing the IP integrated services environment with an ATM service environment so as to create a seamless interface between the two in support of end users desiring real-time networking services. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: M. Borden, E. Crawley, B. Davie, S. Batsell |
| RFC1822 A Grant of Rights to Use a Specific IBM patent with Photuris This Request for Comments records a grant by IBM Corporation to permit the conditional free use of one of its patents. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: J. Lowe |
| RFC1823 The LDAP Application Program Interface This document defines a C language application program interface to the lightweight directory access protocol (LDAP). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: T. Howes, M. Smith |
| RFC1824 The Exponential Security System TESS: An Identity-Based Cryptographic Protocol for Authenticated Key-Exchange (E.I.S.S.-Report 1995/4) This informational RFC describes the basic mechanisms and functions of an identity based system for the secure authenticated exchange of cryptographic keys, the generation of signatures, and the authentic distribution of public keys. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: H. Danisch |
| RFC1825 Security Architecture for the Internet Protocol This memo describes the security mechanisms for IP version 4 (IPv4) and IP version 6 (IPv6) and the services that they provide. [STANDARDS-TRACK] | August 1995 Status: PROPOSED STANDARD Autor: R. Atkinson |
| RFC1826 IP Authentication Header This document describes a mechanism for providing cryptographic authentication for IPv4 and IPv6 datagrams. [STANDARDS-TRACK] | August 1995 Status: PROPOSED STANDARD Autor: R. Atkinson |
| RFC1827 IP Encapsulating Security Payload (ESP) This document describes the IP Encapsulating Security Payload (ESP). ESP is a mechanism for providing integrity and confidentiality to IP datagrams. [STANDARDS-TRACK] | August 1995 Status: PROPOSED STANDARD Autor: R. Atkinson |
| RFC1828 IP Authentication using Keyed MD5 This document describes the use of keyed MD5 with the IP Authentication Header. [STANDARDS-TRACK] | August 1995 Status: HISTORIC Autor: P. Metzger, W. Simpson |
| RFC1829 The ESP DES-CBC Transform This document describes the DES-CBC security transform for the IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK] | August 1995 Status: PROPOSED STANDARD Autor: P. Karn, P. Metzger, W. Simpson |
| RFC1830 SMTP Service Extensions for Transmission of Large and Binary MIME Messages This memo defines two extensions to the SMTP service. The first service enables a SMTP client and server to negotiate the use of an alternate DATA command "BDAT" for efficiently sending large MIME messages. The second extension takes advantage of the BDAT command to permit the negotiated sending of unencoded binary data. This memo defines an Experimental Protocol for the Internet community. | August 1995 Status: EXPERIMENTAL Autor: G. Vaudreuil |
| RFC1831 RPC: Remote Procedure Call Protocol Specification Version 2 This document describes the ONC Remote Procedure Call (ONC RPC Version 2) protocol as it is currently deployed and accepted. [STANDARDS-TRACK] | August 1995 Status: PROPOSED STANDARD Autor: R. Srinivasan |
| RFC1832 XDR: External Data Representation Standard This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted. [STANDARDS-TRACK] | August 1995 Status: DRAFT STANDARD Autor: R. Srinivasan |
| RFC1833 Binding Protocols for ONC RPC Version 2 This document describes the binding protocols used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocols. [STANDARDS-TRACK] | August 1995 Status: PROPOSED STANDARD Autor: R. Srinivasan |
| RFC1834 Whois and Network Information Lookup Service, Whois++ This memo describes new features for WHOIS. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: J. Gargano, K. Weiss |
| RFC1835 Architecture of the WHOIS++ service This document describes WHOIS++, an extension to the trivial WHOIS service described in RFC 954 to permit WHOIS-like servers to make available more structured information to the Internet. [STANDARDS-TRACK] | August 1995 Status: HISTORIC Autor: P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider |
| RFC1836 Representing the O/R Address hierarchy in the X.500 Directory Information Tree This document defines a representation of the O/R Address hierarchy in the Directory Information Tree [6, 1]. This memo defines an Experimental Protocol for the Internet community. | August 1995 Status: EXPERIMENTAL Autor: S. Kille |
| RFC1837 Representing Tables and Subtrees in the X.500 Directory This document defines techniques for representing two types of information mapping in the OSI Directory. This memo defines an Experimental Protocol for the Internet community. | August 1995 Status: EXPERIMENTAL Autor: S. Kille |
| RFC1838 Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses This document defines how to use directory to support the mapping between X.400 O/R Addresses and mailboxes defined in RFC 1327 [2]. This memo defines an Experimental Protocol for the Internet community. | August 1995 Status: EXPERIMENTAL Autor: S. Kille |
| RFC1841 PPP Network Control Protocol for LAN Extension | September 1995 Status: INFORMATIONAL Autor: J. Chapman, D. Coli, A. Harvey, B. Jensen, K. Rowett |
| RFC1842 ASCII Printable Characters-Based Chinese Character Encoding for Internet Messages This document describes the encoding used in electronic mail [RFC822] and network news [RFC1036] messages over the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Telecommunications infrastructure is improving to offer higher bandwidth connections at lower cost. Access to the network is changing from modems to more intelligent devices. This informational RFC discusses a PPP Network Control Protocol for one such intelligent device. The protocol is the LAN extension interface protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: Y. Wei, Y. Zhang, J. Li, J. Ding, Y. Jiang |
| RFC1843 HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters The content of this memo is identical to an article of the same title written by the author on September 4, 1989. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: F. Lee |
| RFC1844 Multimedia E-mail (MIME) User Agent Checklist This document presents a checklist to facilitate evaluation of MIME capable User Agents. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1995 Status: INFORMATIONAL Autor: E. Huizer |
| RFC1845 SMTP Service Extension for Checkpoint/Restart | September 1995 Status: EXPERIMENTAL Autor: D. Crocker, N. Freed, A. Cargille |
| RFC1846 SMTP 521 Reply Code | September 1995 Status: EXPERIMENTAL Autor: A. Durand, F. Dupont |
| RFC1847 Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted This document defines a framework within which security services may be applied to MIME body parts. [STANDARDS-TRACK] This memo defines a new Simple Mail Transfer Protocol (SMTP) [1] reply code, 521, which one may use to indicate that an Internet host does not accept incoming mail. This memo defines an Experimental Protocol for the Internet community. This memo defines an extension to the SMTP service whereby an interrupted SMTP transaction can be restarted at a later time without having to repeat all of the commands and message content sent prior to the interruption. This memo defines an Experimental Protocol for the Internet community. | October 1995 Status: PROPOSED STANDARD Autor: J. Galvin, S. Murphy, S. Crocker, N. Freed |
| RFC1848 MIME Object Security Services This document defines MIME Object Security Services (MOSS), a protocol that uses the multipart/signed and multipart/encrypted framework [7] to apply digital signature and encryption services to MIME objects. [STANDARDS-TRACK] | October 1995 Status: HISTORIC Autor: S. Crocker, N. Freed, J. Galvin, S. Murphy |
| RFC1849 "Son of 1036": News Article Format and Transmission By the early 1990s, it had become clear that RFC 1036, then the specification for the Interchange of USENET Messages, was badly in need of repair. This "Internet-Draft-to-be", though never formally published at that time, was widely circulated and became the de facto standard for implementors of News Servers and User Agents, rapidly acquiring the nickname "Son of 1036". Indeed, under that name, it could fairly be described as the best-known Internet Draft (n)ever published, and it formed the starting point for the recently adopted Proposed Standards for Netnews. | March 2010 Status: HISTORIC Autor: H. Spencer |
| RFC1850 OSPF Version 2 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Open Shortest Path First Routing Protocol. [STANDARDS-TRACK] | November 1995 Status: DRAFT STANDARD Autor: F. Baker, R. Coltun |
| RFC1851 The ESP Triple DES Transform | September 1995 Status: EXPERIMENTAL Autor: P. Karn, P. Metzger, W. Simpson |
| RFC1852 IP Authentication using Keyed SHA | September 1995 Status: EXPERIMENTAL Autor: P. Metzger, W. Simpson |
| RFC1853 IP in IP Tunneling This document discusses implementation techniques for using IP Protocol/Payload number 4 Encapsulation for tunneling with IP Security and other protocols. This memo provides information for the Internet community. It does not specify an Internet standard. This document describes the use of keyed SHA with the IP Authentication Header. This document defines an Experimental Protocol for the Internet community. This document describes the Triple DES-CBC security transform for the IP Encapsulating Security Payload (ESP). This document defines an Experimental Protocol for the Internet community. | October 1995 Status: INFORMATIONAL Autor: W. Simpson |
| RFC1854 SMTP Service Extension for Command Pipelining This memo defines an extension to the SMTP service whereby a server can indicate the extent of its ability to accept multiple commands in a single TCP send operation. [STANDARDS-TRACK] | October 1995 Status: PROPOSED STANDARD Autor: N. Freed |
| RFC1855 Netiquette Guidelines This document provides a minimum set of guidelines for Network Etiquette (Netiquette) which organizations may take and adapt for their own use. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1995 Status: INFORMATIONAL Autor: S. Hambridge |
| RFC1856 The Opstat Client-Server Model for Statistics Retrieval | September 1995 Status: INFORMATIONAL Autor: H. Clark |
| RFC1857 A Model for Common Operational Statistics This memo describes a model for operational statistics in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. This document defines a model and protocol for a set of tools which could be used by NSPs and Network Operation Centers (NOCs) to share data among themselves and with customers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1995 Status: INFORMATIONAL Autor: M. Lambert |
| RFC1858 Security Considerations for IP Fragment Filtering IP fragmentation can be used to disguise TCP packets from IP filters used in routers and hosts. This document describes two methods of attack as well as remedies to prevent them. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1995 Status: INFORMATIONAL Autor: G. Ziemba, D. Reed, P. Traina |
| RFC1859 ISO Transport Class 2 Non-use of Explicit Flow Control over TCP RFC1006 extension This document is an extension to STD35, RFC1006, a standard for the Internet community. The document does not duplicate the protocol definitions contained in RFC1006 and in International Standard ISO 8073. It supplements that information with the description of how to implement ISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1995 Status: INFORMATIONAL Autor: Y. Pouffary |
| RFC1860 Variable Length Subnet Table For IPv4 This document itemizes the potential values for IPv4 subnets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1995 Status: INFORMATIONAL Autor: T. Pummill, B. Manning |
| RFC1861 Simple Network Paging Protocol - Version 3 -Two-Way Enhanced This RFC suggests a simple way for delivering wireless messages, both one and two-way, to appropriate receiving devices. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1995 Status: INFORMATIONAL Autor: A. Gwinn |
| RFC1862 Report of the IAB Workshop on Internet Information Infrastructure, October 12-14, 1994 This document is a report on an Internet architecture workshop, initiated by the IAB and held at MCI on October 12-14, 1994. This workshop generally focused on aspects of the information infrastructure on the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1995 Status: INFORMATIONAL Autor: M. McCahill, J. Romkey, M. Schwartz, K. Sollins, T. Verschuren, C. Weider |
| RFC1863 A BGP/IDRP Route Server alternative to a full mesh routing This document describes the use and detailed design of Route Servers for dissemination of routing information among BGP/IDRP speaking routers. This memo defines an Experimental Protocol for the Internet community. | October 1995 Status: HISTORIC Autor: D. Haskin |
| RFC1864 The Content-MD5 Header Field This memo specifies an optional header field, Content-MD5, for use with MIME-conformant messages. [STANDARDS-TRACK] | October 1995 Status: DRAFT STANDARD Autor: J. Myers, M. Rose |
| RFC1865 EDI Meets the Internet Frequently Asked Questions about Electronic Data Interchange (EDI) on the Internet This memo is targeted towards the EDI community that is unfamiliar with the Internet, including EDI software developers, users, and service providers. The memo introduces the Internet and assumes a basic knowledge of EDI. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1996 Status: INFORMATIONAL Autor: W. Houser, J. Griffin, C. Hage |
| RFC1866 Hypertext Markup Language - 2.0 This document defines a HTML 2.0 (to distinguish it from the previous informal specifications). [STANDARDS-TRACK] | November 1995 Status: HISTORIC Autor: T. Berners-Lee, D. Connolly |
| RFC1867 Form-based File Upload in HTML Since file-upload is a feature that will benefit many applications, this proposes an extension to HTML to allow information providers to express file upload requests uniformly, and a MIME compatible representation for file upload responses. This memo defines an Experimental Protocol for the Internet community. | November 1995 Status: HISTORIC Autor: E. Nebel, L. Masinter |
| RFC1868 ARP Extension - UNARP This document specifies a trivial modification to the ARP mechanism, not the packet format, which allows a node to announce that it is leaving the network and that all other nodes should modify their ARP tables accordingly. This memo defines an Experimental Protocol for the Internet community. | November 1995 Status: EXPERIMENTAL Autor: G. Malkin |
| RFC1869 SMTP Service Extensions This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK] | November 1995 Status: STANDARD Autor: J. Klensin, N. Freed, M. Rose, E. Stefferud, D. Crocker |
| RFC1870 SMTP Service Extension for Message Size Declaration This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to decline to accept a message (perhaps temporarily) based on the client's estimate of the message size. [STANDARDS-TRACK] | November 1995 Status: STANDARD Autor: J. Klensin, N. Freed, K. Moore |
| RFC1871 Addendum to RFC 1602 -- Variance Procedure This document describes a modification to the IETF procedures to allow an escape from a situation where the existing procedures are not working or do not seem to apply. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | November 1995 Status: HISTORIC Autor: J. Postel |
| RFC1872 The MIME Multipart/Related Content-type The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. This memo defines an Experimental Protocol for the Internet community. | December 1995 Status: EXPERIMENTAL Autor: E. Levinson |
| RFC1873 Message/External-Body Content-ID Access Type The existing MIME Content-Type Message/External-Body access-types allow a MIME entity (body-part) to refer to an object that is not in the message by specifying how to access that object. The Content-ID access method described in this document provides the capability to refer to an object within the message. This memo defines an Experimental Protocol for the Internet community. | December 1995 Status: EXPERIMENTAL Autor: E. Levinson |
| RFC1874 SGML Media Types This document proposes new media sub-types of Text/SGML and Application/SGML. This memo defines an Experimental Protocol for the Internet community. | December 1995 Status: EXPERIMENTAL Autor: E. Levinson |
| RFC1875 UNINETT PCA Policy Statements This document provides information about policy statements submitted by the UNINETT Policy Certification Authority (UNINETT PCA). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1995 Status: INFORMATIONAL Autor: N. Berge |
| RFC1876 A Means for Expressing Location Information in the Domain Name System This memo defines a new DNS RR type for experimental purposes. This RFC describes a mechanism to allow the DNS to carry location information about hosts, networks, and subnets. This memo defines an Experimental Protocol for the Internet community. | January 1996 Status: EXPERIMENTAL Autor: C. Davis, P. Vixie, T. Goodwin, I. Dickinson |
| RFC1877 PPP Internet Protocol Control Protocol Extensions for Name Server Addresses This document extends the NCP for establishing and configuring the Internet Protocol over PPP [2], defining the negotiation of primary and secondary Domain Name System (DNS) [3] and NetBIOS Name Server (NBNS) [4] addresses. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1995 Status: INFORMATIONAL Autor: S. Cobb |
| RFC1878 Variable Length Subnet Table For IPv4 This memo clarifies issues surrounding subnetting IP networks by providing a standard subnet table. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1995 Status: HISTORIC Autor: T. Pummill, B. Manning |
| RFC1879 Class A Subnet Experiment Results and Recommendations This memo documents some experiences with the RFC 1797 [1] subnet A experiment (performed by the Net39 Test Group (see credits)) and provides a number of recommendations on future direction for both the Internet Registries and the Operations community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1996 Status: INFORMATIONAL Autor: B. Manning |
| RFC1880 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] | November 1995 Status: HISTORIC Autor: J. Postel |
| RFC1881 IPv6 Address Allocation Management The IPv6 address space will be managed by the IANA for the good of the Internet community, with advice from the IAB and the IESG, by delegation to the regional registries. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1995 Status: INFORMATIONAL Autor: IAB, IESG |
| RFC1882 The 12-Days of Technology Before Christmas This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1995 Status: INFORMATIONAL Autor: B. Hancock |
| RFC1883 Internet Protocol, Version 6 (IPv6) Specification This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK] | December 1995 Status: PROPOSED STANDARD Autor: S. Deering, R. Hinden |
| RFC1884 IP Version 6 Addressing Architecture This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK] | December 1995 Status: HISTORIC Autor: R. Hinden, S. Deering |
| RFC1885 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). [STANDARDS-TRACK] | December 1995 Status: PROPOSED STANDARD Autor: A. Conta, S. Deering |
| RFC1886 DNS Extensions to support IP version 6 This document defines the changes that need to be made to the Domain Name System to support hosts running IP version 6 (IPv6). [STANDARDS-TRACK] | December 1995 Status: PROPOSED STANDARD Autor: S. Thomson, C. Huitema |
| RFC1887 An Architecture for IPv6 Unicast Address Allocation This document provides an architecture for allocating IPv6 [1] unicast addresses in the Internet. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1995 Status: INFORMATIONAL Autor: Y. Rekhter, T. Li |
| RFC1888 OSI NSAPs and IPv6 This document recommends that network implementors who have planned or deployed an OSI NSAP addressing plan, and who wish to deploy or transition to IPv6, should redesign a native IPv6 addressing plan to meet their needs. This memo defines an Experimental Protocol for the Internet community. | August 1996 Status: HISTORIC Autor: J. Bound, B. Carpenter, D. Harrington, J. Houldsworth, A. Lloyd |
| RFC1889 RTP: A Transport Protocol for Real-Time Applications This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. [STANDARDS-TRACK] | January 1996 Status: PROPOSED STANDARD Autor: Audio-Video Transport Working Group, H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson |
| RFC1890 RTP Profile for Audio and Video Conferences with Minimal Control This memo describes a profile for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. [STANDARDS-TRACK] | January 1996 Status: PROPOSED STANDARD Autor: Audio-Video Transport Working Group, H. Schulzrinne |
| RFC1891 SMTP Service Extension for Delivery Status Notifications This memo defines an extension to the SMTP service, which allows an SMTP client to specify (a) that delivery status notifications (DSNs) should be generated under certain conditions, (b) whether such notifications should return the contents of the message, and (c) additional information, to be returned with a DSN, that allows the sender to identify both the recipient(s) for which the DSN was issued, and the transaction in which the original message was sent. [STANDARDS-TRACK] | January 1996 Status: PROPOSED STANDARD Autor: K. Moore |
| RFC1892 The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages The Multipart/Report MIME content-type is a general "family" or "container" type for electronic mail reports of any kind. Although this memo defines only the use of the Multipart/Report content-type with respect to delivery status reports, mail processing programs will benefit if a single content-type is used to for all kinds of reports. [STANDARDS-TRACK] | January 1996 Status: PROPOSED STANDARD Autor: G. Vaudreuil |
| RFC1893 Enhanced Mail System Status Codes There currently is not a standard mechanism for the reporting of mail system errors except for the limited set offered by SMTP and the system specific text descriptions sent in mail messages. There is a pressing need for a rich machine readable status code for use in delivery status notifications [DSN]. This document proposes a new set of status codes for this purpose. [STANDARDS-TRACK] | January 1996 Status: PROPOSED STANDARD Autor: G. Vaudreuil |
| RFC1894 An Extensible Message Format for Delivery Status Notifications This memo defines a MIME content-type that may be used by a message transfer agent (MTA) or electronic mail gateway to report the result of an attempt to deliver a message to one or more recipients. [STANDARDS-TRACK] | January 1996 Status: PROPOSED STANDARD Autor: K. Moore, G. Vaudreuil |
| RFC1895 The Application/CALS-1840 Content-type This memorandum provides guidelines for using the United States Department of Defense Military Standard MIL-STD-1840, "Automated Interchange of Technical Information," with the Internet electronic mail standards, RFC 822 and RFC 1521. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1996 Status: INFORMATIONAL Autor: E. Levinson |
| RFC1896 The text/enriched MIME Content-type This document defines one particular type of MIME data, the text/enriched MIME type. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1996 Status: INFORMATIONAL Autor: P. Resnick, A. Walker |
| RFC1897 IPv6 Testing Address Allocation This document describes an allocation plan for IPv6 addresses to be used in testing IPv6 prototype software. This document specifies an Experimental protocol for the Internet community. | January 1996 Status: EXPERIMENTAL Autor: R. Hinden, J. Postel |
| RFC1898 CyberCash Credit Card Protocol Version 0.8 This document covers only the current CyberCash system which is one of the few operational systems in the rapidly evolving area of Internet payments. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1996 Status: INFORMATIONAL Autor: D. Eastlake 3rd, B. Boesch, S. Crocker, M. Yesil |
| RFC1899 Request for Comments Summary RFC Numbers 1800-1899 | January 1997 Status: INFORMATIONAL Autor: J. Elliott |
| RFC1900 Renumbering Needs Work Hosts in an IP network are identified by IP addresses, and the IP address prefixes of subnets are advertised by routing protocols. A change in such IP addressing information associated with a host or subnet is known as "renumbering". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1996 Status: INFORMATIONAL Autor: B. Carpenter, Y. Rekhter |
| RFC1901 Introduction to Community-based SNMPv2 The purpose of this document is to define the Community-based Administrative Framework for the SNMP version 2 framework (SNMPv2). This document specifies an Experimental protocol for the Internet community. | January 1996 Status: HISTORIC Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1902 Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document, the Structure of Management Information (SMI), to define that adapted subset, and to assign a set of associated administrative values. [STANDARDS-TRACK] | January 1996 Status: DRAFT STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1903 Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] | January 1996 Status: DRAFT STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1904 Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2) It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK] | January 1996 Status: DRAFT STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1905 Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK] | January 1996 Status: DRAFT STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1906 Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK] | January 1996 Status: DRAFT STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1907 Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK] | January 1996 Status: DRAFT STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1908 Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework [1-6], termed the SNMP version 2 framework (SNMPv2), and the original Internet- standard Network Management Framework (SNMPv1). [STANDARDS-TRACK] | January 1996 Status: DRAFT STANDARD Autor: J. Case, K. McCloghrie, M. Rose, S. Waldbusser |
| RFC1909 An Administrative Infrastructure for SNMPv2 It is the purpose of this document, An Administrative Infrastructure for SNMPv2, to define an administrative framework which realizes effective management in a variety of configurations and environments. This memo defines an Experimental Protocol for the Internet community. | February 1996 Status: HISTORIC Autor: K. McCloghrie |
| RFC1910 User-based Security Model for SNMPv2 In this administrative framework, a security model defines the mechanisms used to achieve an administratively-defined level of security for protocol interactions. Although many such security models might be defined, it is the purpose of this document, User-based Security Model for SNMPv2, to define the first, and, as of this writing, only, security model for this administrative framework. This memo defines an Experimental Protocol for the Internet community. | February 1996 Status: HISTORIC Autor: G. Waters |
| RFC1911 Voice Profile for Internet Mail The following document is a profile of the Internet standard MIME and ESMTP protocols for use as a digital voice networking protocol. This memo defines an Experimental Protocol for the Internet community. | February 1996 Status: EXPERIMENTAL Autor: G. Vaudreuil |
| RFC1912 Common DNS Operational and Configuration Errors This memo describes errors often found in both the operation of Domain Name System (DNS) servers, and in the data that these DNS servers contain. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1996 Status: INFORMATIONAL Autor: D. Barr |
| RFC1913 Architecture of the Whois++ Index Service The authors describe an architecture for indexing in distributed databases, and apply this to the WHOIS++ protocol. [STANDARDS-TRACK] | February 1996 Status: HISTORIC Autor: C. Weider, J. Fullton, S. Spero |
| RFC1914 How to Interact with a Whois++ Mesh In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client, since each server 'refers' the client to the next appropriate server(s). [STANDARDS-TRACK] | February 1996 Status: HISTORIC Autor: P. Faltstrom, R. Schoultz, C. Weider |
| RFC1915 Variance for The PPP Compression Control Protocol and The PPP Encryption Control Protocol The PPP Working group has developed two protocols, one to control compression on PPP links; the Compression Control Protocol (CCP), documented in draft-ietf-pppext-compression-04.txt. The second is the Encryption Control Protocol (ECP), used to control encryption on serial links, documented in draft-ietf-pppext-encryption-03.txt. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 1996 Status: BEST CURRENT PRACTICE Autor: F. Kastenholz |
| RFC1916 Enterprise Renumbering: Experience and Information Solicitation Because of the urgent need for, and substantial difficulty in, renumbering IP networks, the PIER working group is compiling a series of documents to assist sites in their renumbering efforts. The intent of these documents is to provide both educational and practical information to the Internet community. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1996 Status: INFORMATIONAL Autor: H. Berkowitz, P. Ferguson, W. Leland, P. Nesser |
| RFC1917 An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA This document is an appeal to the Internet community to return unused address space, i.e. any block of consecutive IP prefixes, to the Internet Assigned Numbers Authority (IANA) or any of the delegated registries, for reapportionment. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 1996 Status: BEST CURRENT PRACTICE Autor: P. Nesser II |
| RFC1918 Address Allocation for Private Internets This document describes address allocation for private internets. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 1996 Status: BEST CURRENT PRACTICE Autor: Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, E. Lear |
| RFC1919 Classical versus Transparent IP Proxies This document explains "classical" and "transparent" proxy techniques and attempts to provide rules to help determine when each proxy system may be used without causing problems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1996 Status: INFORMATIONAL Autor: M. Chatel |
| RFC1920 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK] | March 1996 Status: HISTORIC Autor: J. Postel |
| RFC1921 TNVIP Protocol The goal of this document specifies a Telnet profile to support VIP terminal emulation allowing the access to the BULL hosts applications through a TCP/IP network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1996 Status: INFORMATIONAL Autor: J. Dujonc |
| RFC1922 Chinese Character Encoding for Internet Messages This memo describes methods of transporting Chinese characters in Internet services which transport text, such as electronic mail [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World Wide Web [RFC-1866]. This memo provides information for the Internet community. It does not specify an Internet standard. | March 1996 Status: INFORMATIONAL Autor: HF. Zhu, DY. Hu, ZG. Wang, TC. Kao, WCH. Chang, M. Crispin |
| RFC1923 RIPv1 Applicability Statement for Historic Status RIP Version 1 [RFC-1058] has been declared an historic document. This Applicability statement provides the supporting motivation for that declaration. The primary reason, as described below, is the Classful nature of RIPv1. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1996 Status: INFORMATIONAL Autor: J. Halpern, S. Bradner |
| RFC1924 A Compact Representation of IPv6 Addresses This document specifies a more compact representation of IPv6 addresses, which permits encoding in a mere 20 bytes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: R. Elz |
| RFC1925 The Twelve Networking Truths This memo documents the fundamental truths of networking for the Internet community. This memo does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: R. Callon |
| RFC1926 An Experimental Encapsulation of IP Datagrams on Top of ATM This RFC describes a method of encapsulating IP datagrams on top of Acoustical Transmission Media (ATM). This is a non-recommended standard. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: J. Eriksson |
| RFC1927 Suggested Additional MIME Types for Associating Documents Seven new types of MIME types are suggested in this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: C. Rogers |
| RFC1928 SOCKS Protocol Version 5 This memo describes a protocol that is an evolution of the previous version of the protocol, version 4 [1]. This new protocol stems from active discussions and prototype implementations. [STANDARDS-TRACK] | March 1996 Status: PROPOSED STANDARD Autor: M. Leech, M. Ganis, Y. Lee, R. Kuris, D. Koblas, L. Jones |
| RFC1929 Username/Password Authentication for SOCKS V5 The protocol specification for SOCKS Version 5 specifies a generalized framework for the use of arbitrary authentication protocols in the initial socks connection setup. This document describes one of those protocols, as it fits into the SOCKS Version 5 authentication "subnegotiation". [STANDARDS-TRACK] | March 1996 Status: PROPOSED STANDARD Autor: M. Leech |
| RFC1930 Guidelines for creation, selection, and registration of an Autonomous System (AS) This memo discusses when it is appropriate to register and utilize an Autonomous System (AS), and lists criteria for such. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | March 1996 Status: BEST CURRENT PRACTICE Autor: J. Hawkinson, T. Bates |
| RFC1931 Dynamic RARP Extensions for Automatic Network Address Acquisition This memo describes extensions to the Reverse Address Resolution Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-RARP). This memo provides information for the Internet community. This memo does not define an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: D. Brownell |
| RFC1932 IP over ATM: A Framework Document It is hoped that this document, in classifying ATM approaches and issues will help to focus the IP over ATM working group's direction.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: R. Cole, D. Shur, C. Villamizar |
| RFC1933 Transition Mechanisms for IPv6 Hosts and Routers This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK] | April 1996 Status: PROPOSED STANDARD Autor: R. Gilligan, E. Nordmark |
| RFC1934 Ascend's Multilink Protocol Plus (MP+) This document proposes an extension to the PPP Multilink Protocol (MP) [1]. Multilink Protocol Plus (MP+) is a new control protocol for managing multiple data links that are bundled by MP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: K. Smith |
| RFC1935 What is the Internet, Anyway? This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: J. Quarterman, S. Carl-Mitchell |
| RFC1936 Implementing the Internet Checksum in Hardware This memo presents a techniques for efficiently implementing the Internet Checksum in hardware. It includes PLD code for programming a single, low cost part to perform checksumming at 1.26 Gbps. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1996 Status: INFORMATIONAL Autor: J. Touch, B. Parham |
| RFC1937 "Local/Remote" Forwarding Decision in Switched Data Link Subnetworks This document describes extensions to the IP architecture that relaxes these constraints, thus enabling the full utilization of the services provided by SVC-based Data Link subnetworks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: Y. Rekhter, D. Kandlur |
| RFC1938 A One-Time Password System This document describes a one-time password authentication system (OTP). [STANDARDS-TRACK] | May 1996 Status: PROPOSED STANDARD Autor: N. Haller, C. Metz |
| RFC1939 Post Office Protocol - Version 3 The Post Office Protocol - Version 3 (POP3) is intended to permit a workstation to dynamically access a maildrop on a server host in a useful fashion. [STANDARDS-TRACK] | May 1996 Status: STANDARD Autor: J. Myers, M. Rose |
| RFC1940 Source Demand Routing: Packet Format and Forwarding Specification (Version 1) The purpose of SDRP is to support source-initiated selection of routes to complement the route selection provided by existing routing protocols for both inter-domain and intra-domain routes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: D. Estrin, T. Li, Y. Rekhter, K. Varadhan, D. Zappala |
| RFC1941 Frequently Asked Questions for Schools The goal of this FYI document, produced by the Internet School Networking (ISN) group in the User Services Area of the Internet Engineering Task Force (IETF), is to act as an introduction to the Internet for faculty, administration, and other school personnel in primary and secondary schools. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: J. Sellers, J. Robichaux |
| RFC1942 HTML Tables This specification extends HTML to support a wide variety of tables. This memo defines an Experimental Protocol for the Internet community. | May 1996 Status: HISTORIC Autor: D. Raggett |
| RFC1943 Building an X.500 Directory Service in the US This document provides definition and recommends considerations that must be undertaken to operate a X.500 Directory Service in the United States. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: B. Jennings |
| RFC1944 Benchmarking Methodology for Network Interconnect Devices This document discusses and defines a number of tests that may be used to describe the performance characteristics of a network interconnecting device. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: S. Bradner, J. McQuaid |
| RFC1945 Hypertext Transfer Protocol -- HTTP/1.0 The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: T. Berners-Lee, R. Fielding, H. Frystyk |
| RFC1946 Native ATM Support for ST2+ This memo describes a working implementation which enables applications to directly invoke ATM services in the following environments: ATM to internet, internet to ATM, and internet to internet across ATM. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: S. Jackowski |
| RFC1947 Greek Character Encoding for Electronic Mail Messages This document describes a standard encoding for electronic mail [RFC822] containing Greek text and provides implementation guide-lines. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: D. Spinellis |
| RFC1948 Defending Against Sequence Number Attacks IP spoofing attacks based on sequence number spoofing have become a serious threat on the Internet (CERT Advisory CA-95:01). While ubiquitous crypgraphic authentication is the right answer, we propose a simple modification to TCP implementations that should be a very substantial block to the current wave of attacks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: S. Bellovin |
| RFC1949 Scalable Multicast Key Distribution This memo provides a scalable solution to the multicast key distribution problem. This memo defines an Experimental Protocol for the Internet community. | May 1996 Status: EXPERIMENTAL Autor: A. Ballardie |
| RFC1950 ZLIB Compressed Data Format Specification version 3.3 This specification defines a lossless compressed data format. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: P. Deutsch, J-L. Gailly |
| RFC1951 DEFLATE Compressed Data Format Specification version 1.3 This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: P. Deutsch |
| RFC1952 GZIP file format specification version 4.3 This specification defines a lossless compressed data format that is compatible with the widely used GZIP utility. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: P. Deutsch |
| RFC1953 Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0 The Ipsilon Flow Management Protocol (IFMP), is a protocol for allowing a node to instruct an adjacent node to attach a layer 2 label to a specified IP flow. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall |
| RFC1954 Transmission of Flow Labelled IPv4 on ATM Data Links Ipsilon Version 1.0 This document specifies the manner for transmitting IPv4 datagrams over an ATM data link, both in a default manner and in the presence of flow labelling via Ipsilon Flow Management Protocol [IFMP]. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1996 Status: INFORMATIONAL Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall |
| RFC1955 New Scheme for Internet Routing and Addressing (ENCAPS) for IPNG This paper proposes a new scheme which I believe is a good medium term solution to the routing and address problems of the internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1996 Status: INFORMATIONAL Autor: R. Hinden |
| RFC1956 Registration in the MIL Domain This RFC describes the policy for the registration of second level domains under the ".MIL" domain. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1996 Status: INFORMATIONAL Autor: D. Engebretson, R. Plzak |
| RFC1957 Some Observations on Implementations of the Post Office Protocol (POP3) This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1996 Status: INFORMATIONAL Autor: R. Nelson |
| RFC1958 Architectural Principles of the Internet The Internet and its architecture have grown in evolutionary fashion from modest beginnings, rather than from a Grand Plan. While this process of evolution is one of the main reasons for the technology's success, it nevertheless seems useful to record a snapshot of the current principles of the Internet architecture. This is intended for general guidance and general interest, and is in no way intended to be a formal or invariant reference model. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1996 Status: INFORMATIONAL Autor: B. Carpenter |
| RFC1959 An LDAP URL Format This document describes a format for an LDAP Uniform Resource Locator which will allow Internet clients to have direct access to the LDAP protocol. [STANDARDS-TRACK] | June 1996 Status: PROPOSED STANDARD Autor: T. Howes, M. Smith |
| RFC1960 A String Representation of LDAP Search Filters The Lightweight Directory Access Protocol (LDAP) [1] defines a network representation of a search filter transmitted to an LDAP server. Some applications may find it useful to have a common way of representing these search filters in a human-readable form. This document defines a human-readable string format for representing LDAP search filters. [STANDARDS-TRACK] | June 1996 Status: PROPOSED STANDARD Autor: T. Howes |
| RFC1961 GSS-API Authentication Method for SOCKS Version 5 This document provides the specification for the SOCKS V5 GSS-API authentication protocol, and defines a GSS-API-based encapsulation for provision of integrity, authentication and optional confidentiality. [STANDARDS-TRACK] | June 1996 Status: PROPOSED STANDARD Autor: P. McMahon |
| RFC1962 The PPP Compression Control Protocol (CCP) This document defines a method for negotiating data compression over PPP links. [STANDARDS-TRACK] | June 1996 Status: PROPOSED STANDARD Autor: D. Rand |
| RFC1963 PPP Serial Data Transport Protocol (SDTP) This document describes a new Network level protocol (from the PPP point of view), PPP Serial Data Transport Protocol, that provides encapsulation and an associated control protocol for transporting serial data streams over a PPP link. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: K. Schneider, S. Venters |
| RFC1964 The Kerberos Version 5 GSS-API Mechanism This specification defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) when using Kerberos Version 5 technology (as specified in RFC 1510). [STANDARDS-TRACK] | June 1996 Status: PROPOSED STANDARD Autor: J. Linn |
| RFC1965 Autonomous System Confederations for BGP This document describes an extension to BGP which may be used to create a confederation of autonomous systems which is represented as one single autonomous system to BGP peers external to the confederation. This memo defines an Experimental Protocol for the Internet community. | June 1996 Status: EXPERIMENTAL Autor: P. Traina |
| RFC1966 BGP Route Reflection An alternative to full mesh IBGP This document describes the use and design of a method known as "Route Reflection" to alleviate the the need for "full mesh" IBGP. This memo defines an Experimental Protocol for the Internet community. | June 1996 Status: EXPERIMENTAL Autor: T. Bates, R. Chandra |
| RFC1967 PPP LZS-DCP Compression Protocol (LZS-DCP) This document describes the use of the Stac LZS data compression algorithm for compressing PPP encapsulated packets, using a DCP header [6]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: K. Schneider, R. Friend |
| RFC1968 The PPP Encryption Control Protocol (ECP) This document defines a method for negotiating data encryption over PPP links. [STANDARDS-TRACK] | June 1996 Status: PROPOSED STANDARD Autor: G. Meyer |
| RFC1969 The PPP DES Encryption Protocol (DESE) This document provides specific details for the use of the DES standard [5, 6] for encrypting PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1996 Status: INFORMATIONAL Autor: K. Sklower, G. Meyer |
| RFC1970 Neighbor Discovery for IP Version 6 (IPv6) This document specifies the Neighbor Discovery protocol for IP Version 6. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: T. Narten, E. Nordmark, W. Simpson |
| RFC1971 IPv6 Stateless Address Autoconfiguration This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: S. Thomson, T. Narten |
| RFC1972 A Method for the Transmission of IPv6 Packets over Ethernet Networks This memo specifies the frame format for transmission of IPv6 [IPV6] packets and the method of forming IPv6 link-local addresses on Ethernet networks. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: M. Crawford |
| RFC1973 PPP in Frame Relay This document describes the use of Frame Relay for framing PPP encapsulated packets. [STANDARDS-TRACK] | June 1996 Status: PROPOSED STANDARD Autor: W. Simpson |
| RFC1974 PPP Stac LZS Compression Protocol This document describes the use of the Stac LZS data compression algorithm, with single or multiple compression histories, for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: R. Friend, W. Simpson |
| RFC1975 PPP Magnalink Variable Resource Compression The Magnalink Variable Resource Compression Algorithm (MVRCA) allows a wide range of interoperable compression implementations whose performance characteristics are a function of available CPU and memory resources. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: D. Schremp, J. Black, J. Weiss |
| RFC1976 PPP for Data Compression in Data Circuit-Terminating Equipment (DCE) This document defines a specific set of parameters for these protocols and an LCP extension to define a standard way of using PPP for data compression of serial data in Data Circuit-Terminating Equipment (DCE). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: K. Schneider, S. Venters |
| RFC1977 PPP BSD Compression Protocol This document describes the use of the Unix Compress compression protocol for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: V. Schryver |
| RFC1978 PPP Predictor Compression Protocol This document describes the use of the Predictor data compression algorithm for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: D. Rand |
| RFC1979 PPP Deflate Protocol This document describes the use of the PPP Deflate compression protocol for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: J. Woods |
| RFC1980 A Proposed Extension to HTML : Client-Side Image Maps This document specifies an extension to the HTML language, referred to as "Client-Side Image Maps," which resolves some limitations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: HISTORIC Autor: J. Seidman |
| RFC1981 Path MTU Discovery for IP version 6 This document describes Path MTU Discovery for IP version 6. It is largely derived from RFC 1191, which describes Path MTU Discovery for IP version 4. [STANDARDS-TRACK] | August 1996 Status: DRAFT STANDARD Autor: J. McCann, S. Deering, J. Mogul |
| RFC1982 Serial Number Arithmetic The DNS has long relied upon serial number arithmetic, a concept which has never really been defined, certainly not in an IETF document, though which has been widely understood. This memo supplies the missing definition. It is intended to update RFC1034 and RFC1035. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: R. Elz, R. Bush |
| RFC1983 Internet Users' Glossary There are many networking glossaries in existence. This glossary concentrates on terms which are specific to the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: G. Malkin |
| RFC1984 IAB and IESG Statement on Cryptographic Technology and the Internet The Internet Architecture Board (IAB) and the Internet Engineering Steering Group (IESG), the bodies which oversee architecture and standards for the Internet, are concerned by the need for increased protection of international commercial transactions on the Internet, and by the need to offer all Internet users an adequate degree of privacy. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: IAB, IESG |
| RFC1985 SMTP Service Extension for Remote Message Queue Starting This memo defines an extension to the SMTP service whereby an SMTP client and server may interact to give the server an opportunity to start the processing of its queues for messages to go to a given host. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: J. De Winter |
| RFC1986 Experiments with a Simple File Transfer Protocol for Radio Links using Enhanced Trivial File Transfer Protocol (ETFTP) This document is a description of the Enhanced Trivial File Transfer Protocol (ETFTP). This protocol is an experimental implementation of the NETwork BLock Transfer Protocol (NETBLT), RFC 998 [1], as a file transfer application program. This memo defines an Experimental Protocol for the Internet community. | August 1996 Status: EXPERIMENTAL Autor: W. Polites, W. Wollman, D. Woo, R. Langan |
| RFC1987 Ipsilon's General Switch Management Protocol Specification Version 1.1 The General Switch Management Protocol (GSMP), is a general purpose protocol to control an ATM switch. GSMP allows a controller to establish and release connections across the switch; add and delete leaves on a point-to-multipoint connection; manage switch ports; request configuration information; and request statistics. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall |
| RFC1988 Conditional Grant of Rights to Specific Hewlett-Packard Patents In Conjunction With the Internet Engineering Task Force's Internet-Standard Network Management Framework This grant is made to help facilitate inclusion of certain patented search address technology covering network device mapping in IETF standards-track Management Information Base (MIB) modules. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: G. McAnally, D. Gilbert, J. Flick |
| RFC1989 PPP Link Quality Monitoring This document defines a protocol for generating Link-Quality-Reports. [STANDARDS-TRACK] | August 1996 Status: DRAFT STANDARD Autor: W. Simpson |
| RFC1990 The PPP Multilink Protocol (MP) This document proposes a method for splitting, recombining and sequencing datagrams across multiple logical data links. [STANDARDS-TRACK] | August 1996 Status: DRAFT STANDARD Autor: K. Sklower, B. Lloyd, G. McGregor, D. Carr, T. Coradetti |
| RFC1991 PGP Message Exchange Formats This document describes the format of "PGP files", i.e., messages that have been encrypted and/or signed with PGP. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: D. Atkins, W. Stallings, P. Zimmermann |
| RFC1992 The Nimrod Routing Architecture Nimrod is a scalable routing architecture designed to accommodate a continually expanding and diversifying internetwork. First suggested by Noel Chiappa, the Nimrod architecture has undergone revision and refinement through the efforts of the Nimrod working group of the IETF. In this document, we present a detailed description of this architecture. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1996 Status: INFORMATIONAL Autor: I. Castineyra, N. Chiappa, M. Steenstrup |
| RFC1993 PPP Gandalf FZA Compression Protocol This document describes the use of the Gandalf FZA data compression algorithm [3] for compressing PPP encapsulated packets. This memo provides information for the Internet community. It does not specify an Internet standard. | August 1996 Status: INFORMATIONAL Autor: A. Barbir, D. Carr, W. Simpson |
| RFC1994 PPP Challenge Handshake Authentication Protocol (CHAP) This document defines a method for Authentication using PPP, which uses a random Challenge, with a cryptographically hashed Response which depends upon the Challenge and a secret key. [STANDARDS-TRACK] | August 1996 Status: DRAFT STANDARD Autor: W. Simpson |
| RFC1995 Incremental Zone Transfer in DNS This document proposes extensions to the DNS protocols to provide an incremental zone transfer (IXFR) mechanism. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: M. Ohta |
| RFC1996 A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY) This memo describes the NOTIFY opcode for DNS, by which a master server advises a set of slave servers that the master's data has been changed and that a query should be initiated to discover the new data. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: P. Vixie |
| RFC1997 BGP Communities Attribute This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. [STANDARDS-TRACK] | August 1996 Status: PROPOSED STANDARD Autor: R. Chandra, P. Traina, T. Li |
| RFC1998 An Application of the BGP Community Attribute in Multi-home Routing This document presents an application of the BGP community attribute [2] in simplifying the implementation and configuration of routing policies in the multi-provider Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | August 1996 Status: INFORMATIONAL Autor: E. Chen, T. Bates |
| RFC1999 Request for Comments Summary RFC Numbers 1900-1999 | January 1997 Status: INFORMATIONAL Autor: J. Elliott |
| RFC2000 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). This memo is an Internet Standard. | February 1997 Status: HISTORIC Autor: J. Postel |
| RFC2001 TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms Modern implementations of TCP contain four intertwined algorithms that have never been fully documented as Internet standards: slow start, congestion avoidance, fast retransmit, and fast recovery. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: W. Stevens |
| RFC2002 IP Mobility Support This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC2003 IP Encapsulation within IP This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC2004 Minimal Encapsulation within IP This document specifies a method by which an IP datagram may be encapsulated (carried as payload) within an IP datagram, with less overhead than "conventional" IP encapsulation that adds a second IP header to each encapsulated datagram. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC2005 Applicability Statement for IP Mobility Support As required by [RFC 1264], this report discusses the applicability of Mobile IP to provide host mobility in the Internet. In particular, this document describes the key features of Mobile IP and shows how the requirements for advancement to Proposed Standard RFC have been satisfied. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: J. Solomon |
| RFC2006 The Definitions of Managed Objects for IP Mobility Support using SMIv2 This memo defines the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: D. Cong, M. Hamlen, C. Perkins |
| RFC2007 Catalogue of Network Training Materials The purpose of this document is to provide a catalogue of quality Network Training Materials for use by Internet trainers in training their users. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: J. Foster, M. Isaacs, M. Prior |
| RFC2008 Implications of Various Address Allocation Policies for Internet Routing The purpose of this document is to articulate certain relevant fundamental technical issues that must be considered in formulating unicast address allocation and management policies for the Public Internet, and to provide recommendations with respect to these policies. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1996 Status: BEST CURRENT PRACTICE Autor: Y. Rekhter, T. Li |
| RFC2009 GPS-Based Addressing and Routing This document describes a possible experiment with geographic addresses. It uses several specific IP addresses and domain names in the discussion as concrete examples to aid in understanding the concepts. This memo defines an Experimental Protocol for the Internet community. | November 1996 Status: EXPERIMENTAL Autor: T. Imielinski, J. Navas |
| RFC2010 Operational Criteria for Root Name Servers This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: B. Manning, P. Vixie |
| RFC2011 SNMPv2 Management Information Base for the Internet Protocol using SMIv2 This document is the MIB module which defines managed objects for managing implementations of the Internet Protocol (IP) and its associated Internet Control Message Protocol (ICMP). [STANDARDS-TRACK] | November 1996 Status: PROPOSED STANDARD Autor: K. McCloghrie |
| RFC2012 SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2 This document is the MIB module which defines managed objects for managing implementations of the Transmission Control Protocol (TCP). [STANDARDS-TRACK] | November 1996 Status: PROPOSED STANDARD Autor: K. McCloghrie |
| RFC2013 SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2 This document is the MIB module which defines managed objects for managing implementations of the User Datagram Protocol (UDP). [STANDARDS-TRACK] | November 1996 Status: PROPOSED STANDARD Autor: K. McCloghrie |
| RFC2014 IRTF Research Group Guidelines and Procedures This document describes the guidelines and procedures for formation and operation of IRTF Research Groups. It describes the relationship between IRTF participants, Research Groups, the Internet Research Steering Group (IRSG) and the Internet Architecture Board (IAB). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1996 Status: BEST CURRENT PRACTICE Autor: A. Weinrib, J. Postel |
| RFC2015 MIME Security with Pretty Good Privacy (PGP) This document describes how Pretty Good Privacy (PGP) can be used to provide privacy and authentication using the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC1847. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: M. Elkins |
| RFC2016 Uniform Resource Agents (URAs) This paper presents an experimental architecture for an agent system that provides sophisticated Internet information access and management. This memo defines an Experimental Protocol for the Internet community. | October 1996 Status: EXPERIMENTAL Autor: L. Daigle, P. Deutsch, B. Heelan, C. Alpaugh, M. Maclachlan |
| RFC2017 Definition of the URL MIME External-Body Access-Type This memo defines a new access-type for message/external-body MIME parts for Uniform Resource Locators (URLs). [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: N. Freed, K. Moore, A. Cargille |
| RFC2018 TCP Selective Acknowledgment Options This memo proposes an implementation of SACK and discusses its performance and related issues. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: M. Mathis, J. Mahdavi, S. Floyd, A. Romanow |
| RFC2019 Transmission of IPv6 Packets Over FDDI This memo specifies the MTU and frame format for transmission of IPv6 [IPV6] packets on FDDI networks, including a method for MTU determination in the presence of 802.1d bridges to other media. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: M. Crawford |
| RFC2020 IEEE 802.12 Interface MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing network interfaces based on IEEE 802.12. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: J. Flick |
| RFC2021 Remote Network Monitoring Management Information Base Version 2 using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: S. Waldbusser |
| RFC2022 Support for Multicast over UNI 3.0/3.1 based ATM Networks This memo describes a mechanism to support the multicast needs of Layer 3 protocols in general, and describes its application to IP multicasting in particular. [STANDARDS-TRACK] | November 1996 Status: PROPOSED STANDARD Autor: G. Armitage |
| RFC2023 IP Version 6 over PPP This document defines the method for transmission of IP Version 6 [2] packets over PPP links as well as the Network Control Protocol (NCP) for establishing and configuring the IPv6 over PPP. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: D. Haskin, E. Allen |
| RFC2024 Definitions of Managed Objects for Data Link Switching using SMIv2 This specification defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling Data Link Switches (DLSw). [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: D. Chen, P. Gayek, S. Nix |
| RFC2025 The Simple Public-Key GSS-API Mechanism (SPKM) This specification defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (as specified in RFCs 1508 and 1509) when using the Simple Public-Key Mechanism. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: C. Adams |
| RFC2026 The Internet Standards Process -- Revision 3 This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1996 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC2027 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees The process by which the members of the IAB and IESG are selected, confirmed, and recalled has been exercised four times since its formal creation. The evolution of the process has relied principally on oral tradition as a means by which the lessons learned could be passed on to successive committees. This document is a self-consistent, organized compilation of the process as it is known today. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1996 Status: INFORMATIONAL Autor: J. Galvin |
| RFC2028 The Organizations Involved in the IETF Standards Process This document describes the individuals and organizations involved in the IETF. This includes descriptions of the IESG, the IETF Working Groups and the relationship between the IETF and the Internet Society. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1996 Status: BEST CURRENT PRACTICE Autor: R. Hovey, S. Bradner |
| RFC2029 RTP Payload Format of Sun's CellB Video Encoding This memo describes a packetization scheme for the CellB video encoding. The scheme proposed allows applications to transport CellB video flows over protocols used by RTP. This document is meant for implementors of video applications that want to use RTP and CellB. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: M. Speer, D. Hoffman |
| RFC2030 Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI This memorandum describes the Simple Network Time Protocol (SNTP) Version 4, which is an adaptation of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: D. Mills |
| RFC2031 IETF-ISOC relationship This memo summarises the issues on IETF - ISOC relationships as the have been discussed by the Poised Working Group. The purpose of the document is to gauge consensus on these issues. And to allow further discussions where necessary. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: E. Huizer |
| RFC2032 RTP Payload Format for H.261 Video Streams This memo describes a scheme to packetize an H.261 video stream for transport using the Real-time Transport Protocol, RTP, with any of the underlying protocols that carry RTP. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: T. Turletti, C. Huitema |
| RFC2033 Local Mail Transfer Protocol SMTP [SMTP] [HOST-REQ] and its service extensions [ESMTP] provide a mechanism for transferring mail reliably and efficiently. The design of the SMTP protocol effectively requires the server to manage a mail delivery queue. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: J. Myers |
| RFC2034 SMTP Service Extension for Returning Enhanced Error Codes This memo defines an extension to the SMTP service [RFC-821, RFC-1869] whereby an SMTP server augments its responses with the enhanced mail system status codes defined in RFC 1893. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: N. Freed |
| RFC2035 RTP Payload Format for JPEG-compressed Video This memo describes the RTP payload format for JPEG video streams. The packet format is optimized for real-time video streams where codec parameters change rarely from frame to frame. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: L. Berc, W. Fenner, R. Frederick, S. McCanne |
| RFC2036 Observations on the use of Components of the Class A Address Space within the Internet This document is a commentary on the recommendation that IANA commence allocation of the presently unallocated components of the Class A address space to registries, for deployment within the Internet as class-less address blocks. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: HISTORIC Autor: G. Huston |
| RFC2037 Entity MIB using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: K. McCloghrie, A. Bierman |
| RFC2038 RTP Payload Format for MPEG1/MPEG2 Video This memo describes a packetization scheme for MPEG video and audio streams. The scheme proposed can be used to transport such a video or audio flow over the transport protocols supported by RTP. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: D. Hoffman, G. Fernando, V. Goyal |
| RFC2039 Applicability of Standards Track MIBs to Management of World Wide Web Servers This document was produced at the request of the Network Management Area Director following the HTTP-MIB BOF at the 35th IETF meeting to report on the applicability of the existing standards track MIBs to management of WWW servers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1996 Status: INFORMATIONAL Autor: C. Kalbfleisch |
| RFC2040 The RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms This document defines four ciphers with enough detail to ensure interoperability between different implementations. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: R. Baldwin, R. Rivest |
| RFC2041 Mobile Network Tracing This RFC argues that mobile network tracing provides both tools to improve our understanding of wireless channels, as well as to build realistic, repeatable testbeds for mobile software and systems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: B. Noble, G. Nguyen, M. Satyanarayanan, R. Katz |
| RFC2042 Registering New BGP Attribute Types This document describes the process for creating new BGP attribute type codes. Basic attribute type codes are described in RFC 1771, pages 12 through 15. These, and new attribute type codes that are used in the Internet are registered with the IANA. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: B. Manning |
| RFC2043 The PPP SNA Control Protocol (SNACP) This document defines the Network Control Protocols for establishing and configuring Systems Network Architecture (SNA) over PPP and SNA over LLC 802.2 over PPP. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: A. Fuqua |
| RFC2044 UTF-8, a transformation format of Unicode and ISO 10646 The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 jointly define a 16 bit character set which encompasses most of the world's writing systems. UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: F. Yergeau |
| RFC2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies This initial document specifies the various headers used to describe the structure of MIME messages. [STANDARDS-TRACK] | November 1996 Status: DRAFT STANDARD Autor: N. Freed, N. Borenstein |
| RFC2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types This second document defines the general structure of the MIME media typing system and defines an initial set of media types. [STANDARDS-TRACK] | November 1996 Status: DRAFT STANDARD Autor: N. Freed, N. Borenstein |
| RFC2047 MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text This particular document is the third document in the series. It describes extensions to RFC 822 to allow non-US-ASCII text data in Internet mail header fields. [STANDARDS-TRACK] | November 1996 Status: DRAFT STANDARD Autor: K. Moore |
| RFC2048 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fourth document, RFC 2048, specifies various IANA registration procedures for some MIME facilities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | November 1996 Status: BEST CURRENT PRACTICE Autor: N. Freed, J. Klensin, J. Postel |
| RFC2049 Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fifth and final document describes MIME conformance criteria as well as providing some illustrative examples of MIME message formats, acknowledgements, and the bibliography. [STANDARDS-TRACK] | November 1996 Status: DRAFT STANDARD Autor: N. Freed, N. Borenstein |
| RFC2050 Internet Registry IP Allocation Guidelines This document describes the registry system for the distribution of globally unique Internet address space and registry operations. Particularly this document describes the rules and guidelines governing the distribution of this address space. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | November 1996 Status: BEST CURRENT PRACTICE Autor: K. Hubbard, M. Kosters, D. Conrad, D. Karrenberg, J. Postel |
| RFC2051 Definitions of Managed Objects for APPC using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and controlling of network devices with APPC (Advanced Program-to-Program Communications) capabilities. This memo identifies managed objects for the SNA LU6.2 protocols. [STANDARDS-TRACK] | October 1996 Status: PROPOSED STANDARD Autor: M. Allen, B. Clouston, Z. Kielczewski, W. Kwan, B. Moore |
| RFC2052 A DNS RR for specifying the location of services (DNS SRV) This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain (like a more general form of MX). This memo defines an Experimental Protocol for the Internet community. | October 1996 Status: EXPERIMENTAL Autor: A. Gulbrandsen, P. Vixie |
| RFC2053 The AM (Armenia) Domain The AM Domain is an official Internet top-level domain of Armenia. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: E. Der-Danieliantz |
| RFC2054 WebNFS Client Specification This document describes a lightweight binding mechanism that allows NFS clients to obtain service from WebNFS-enabled servers with a minimum of protocol overhead. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: B. Callaghan |
| RFC2055 WebNFS Server Specification This document describes the specifications for a server of WebNFS clients. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1996 Status: INFORMATIONAL Autor: B. Callaghan |
| RFC2056 Uniform Resource Locators for Z39.50 Z39.50 is an information retrieval protocol that does not fit neatly into a retrieval model designed primarily around the stateless fetch of data. Instead, it models a general user inquiry as a session-oriented, multi-step task, any step of which may be suspended temporarily while the server requests additional parameters from the client before continuing. [STANDARDS-TRACK] | November 1996 Status: PROPOSED STANDARD Autor: R. Denenberg, J. Kunze, D. Lynch |
| RFC2057 Source Directed Access Control on the Internet This memo was developed from a deposition that I submitted as part of a challenge to the Communications Decency Act of 1996, part of the Telecommunications Reform Act of 1996. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | November 1996 Status: INFORMATIONAL Autor: S. Bradner |
| RFC2058 Remote Authentication Dial In User Service (RADIUS) This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: C. Rigney, A. Rubens, W. Simpson, S. Willens |
| RFC2059 RADIUS Accounting This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: C. Rigney |
| RFC2060 Internet Message Access Protocol - Version 4rev1 The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. [STANDARDS-TRACK] | December 1996 Status: PROPOSED STANDARD Autor: M. Crispin |
| RFC2061 IMAP4 Compatibility with IMAP2bis This document is intended to be read along with RFC 1176 and the most recent IMAP4 specification (RFC 2060) to assist implementors in creating an IMAP4 implementation to interoperate with implementations that conform to earlier specifications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1996 Status: INFORMATIONAL Autor: M. Crispin |
| RFC2062 Internet Message Access Protocol - Obsolete Syntax This document describes obsolete syntax which may be encountered by IMAP4 implementations which deal with older versions of the Internet Mail Access Protocol. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | December 1996 Status: INFORMATIONAL Autor: M. Crispin |
| RFC2063 Traffic Flow Measurement: Architecture This document describes an architecture for the measurement and reporting of network traffic flows, discusses how this relates to an overall network traffic flow architecture, and describes how it can be used within the Internet. This memo defines an Experimental Protocol for the Internet community. | January 1997 Status: EXPERIMENTAL Autor: N. Brownlee, C. Mills, G. Ruth |
| RFC2064 Traffic Flow Measurement: Meter MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this memo defines managed objects used for obtaining traffic flow information from network traffic meters. This memo defines an Experimental Protocol for the Internet community. | January 1997 Status: EXPERIMENTAL Autor: N. Brownlee |
| RFC2065 Domain Name System Security Extensions The Domain Name System (DNS) has become a critical operational part of the Internet infrastructure yet it has no strong security mechanisms to assure data integrity or authentication. Extensions to the DNS are described that provide these services to security aware resolvers or applications through the use of cryptographic digital signatures. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd, C. Kaufman |
| RFC2066 TELNET CHARSET Option This document specifies a mechanism for passing character set and translation information between a TELNET client and server. This memo defines an Experimental Protocol for the Internet community. | January 1997 Status: EXPERIMENTAL Autor: R. Gellens |
| RFC2067 IP over HIPPI ANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. This memo is a revision of RFC 1374, "IP and ARP on HIPPI", and is intended to replace it in the Standards Track. [STANDARDS-TRACK] | January 1997 Status: DRAFT STANDARD Autor: J. Renwick |
| RFC2068 Hypertext Transfer Protocol -- HTTP/1.1 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-Lee |
| RFC2069 An Extension to HTTP : Digest Access Authentication The protocol referred to as "HTTP/1.0" includes the specification for a Basic Access Authentication scheme. This scheme is not considered to be a secure method of user authentication, as the user name and password are passed over the network as clear text. A specification for a different authentication scheme is needed to address this severe limitation. This document provides specification for such a scheme, referred to as "Digest Access Authentication". [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: J. Franks, P. Hallam-Baker, J. Hostetler, P. Leach, A. Luotonen, E. Sink, L. Stewart |
| RFC2070 Internationalization of the Hypertext Markup Language This document is meant to address the issue of the internationalization (i18n, i followed by 18 letters followed by n) of HTML by extending the specification of HTML and giving additional recommendations for proper internationalization support. [STANDARDS-TRACK] | January 1997 Status: HISTORIC Autor: F. Yergeau, G. Nicol, G. Adams, M. Duerst |
| RFC2071 Network Renumbering Overview: Why would I want it and what is it anyway? This document attempts to clearly define the concept of network renumbering and discuss some of the more pertinent reasons why an organization would have a need to do so. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: P. Ferguson, H. Berkowitz |
| RFC2072 Router Renumbering Guide Routers interact with numerous network infrastructure servers, including DNS and SNMP. These interactions, not just the pure addressing and routing structure, must be considered as part of router renumbering. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: H. Berkowitz |
| RFC2073 An IPv6 Provider-Based Unicast Address Format This document defines an IPv6 provider-based unicast address format for use in the Internet. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: Y. Rekhter, P. Lothberg, R. Hinden, S. Deering, J. Postel |
| RFC2074 Remote Network Monitoring MIB Protocol Identifiers This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes the algorithms required to identify different protocol encapsulations managed with the Remote Network Monitoring MIB Version 2 [RMON2]. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: A. Bierman, R. Iddon |
| RFC2075 IP Echo Host Service This memo describes how to implement an IP echo host. IP echo hosts send back IP datagrams after exchanging the source and destination IP addresses. This memo defines an Experimental Protocol for the Internet community. | January 1997 Status: EXPERIMENTAL Autor: C. Partridge |
| RFC2076 Common Internet Message Headers This memo contains a table of commonly occurring headers in headings of e-mail messages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: J. Palme |
| RFC2077 The Model Primary Content Type for Multipurpose Internet Mail Extensions The purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as "model". [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: S. Nelson, C. Parks, Mitra |
| RFC2078 Generic Security Service Application Program Interface, Version 2 The Generic Security Service Application Program Interface (GSS-API), as defined in RFC-1508, provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: J. Linn |
| RFC2079 Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs) This document builds on the experimentation to date and defines a new attribute type and an auxiliary object class to allow URIs, including URLs, to be stored in directory entries in a standard way. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: M. Smith |
| RFC2080 RIPng for IPv6 This document specifies a routing protocol for an IPv6 internet. It is based on protocols and algorithms currently in wide use in the IPv4 Internet [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: G. Malkin, R. Minnear |
| RFC2081 RIPng Protocol Applicability Statement As required by Routing Protocol Criteria (RFC 1264), this report defines the applicability of the RIPng protocol within the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: G. Malkin |
| RFC2082 RIP-2 MD5 Authentication Growth in the Internet has made us aware of the need for improved authentication of routing information. RIP-2 provides for unauthenticated service (as in classical RIP), or password authentication. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: F. Baker, R. Atkinson |
| RFC2083 PNG (Portable Network Graphics) Specification Version 1.0 This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1997 Status: INFORMATIONAL Autor: T. Boutell |
| RFC2084 Considerations for Web Transaction Security This document specifies the requirements for the provision of security services to the HyperText Transport Protocol. These services include confidentiality, integrity, user authentication, and authentication of servers/services, including proxied or gatewayed services. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: G. Bossert, S. Cooper, W. Drummond |
| RFC2085 HMAC-MD5 IP Authentication with Replay Prevention This document describes a keyed-MD5 transform to be used in conjunction with the IP Authentication Header [RFC-1826]. The particular transform is based on [HMAC-MD5]. An option is also specified to guard against replay attacks. [STANDARDS-TRACK] | February 1997 Status: PROPOSED STANDARD Autor: M. Oehler, R. Glenn |
| RFC2086 IMAP4 ACL extension The ACL extension of the Internet Message Access Protocol [IMAP4] permits access control lists to be manipulated through the IMAP protocol. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC2087 IMAP4 QUOTA extension The QUOTA extension of the Internet Message Access Protocol [IMAP4] permits administrative limits on resource usage (quotas) to be manipulated through the IMAP protocol. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC2088 IMAP4 non-synchronizing literals The Internet Message Access Protocol [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC2089 V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent The goal of this memo is to document a common way of mapping an SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP agent (one that supports both SNMPv1 and SNMPv2). This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: B. Wijnen, D. Levi |
| RFC2090 TFTP Multicast Option This document describes a new TFTP option. This new option will allow the multiple clients to receive the same file concurrently through the use of Multicast packets. This memo defines an Experimental Protocol for the Internet community. | February 1997 Status: EXPERIMENTAL Autor: A. Emberson |
| RFC2091 Triggered Extensions to RIP to Support Demand Circuits This document defines a modification which can be applied to Bellman- Ford (distance vector) algorithm information broadcasting protocols. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: G. Meyer, S. Sherry |
| RFC2092 Protocol Analysis for Triggered RIP As required by Routing Protocol Criteria [1], this report documents the key features of Triggered Extensions to RIP to Support Demand Circuits [2] and the current implementation experience. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | January 1997 Status: INFORMATIONAL Autor: S. Sherry, G. Meyer |
| RFC2093 Group Key Management Protocol (GKMP) Specification This specification proposes a protocol to create grouped symmetric keys and distribute them amongst communicating peers. This memo defines an Experimental Protocol for the Internet community. | July 1997 Status: EXPERIMENTAL Autor: H. Harney, C. Muckenhirn |
| RFC2094 Group Key Management Protocol (GKMP) Architecture This specification proposes a protocol to create grouped symmetric keys and distribute them amongst communicating peers. This memo defines an Experimental Protocol for the Internet community. | July 1997 Status: EXPERIMENTAL Autor: H. Harney, C. Muckenhirn |
| RFC2095 IMAP/POP AUTHorize Extension for Simple Challenge/Response This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: J. Klensin, R. Catoe, P. Krumviede |
| RFC2096 IP Forwarding Table MIB This memo defines an update to RFC 1354. The significant difference between this MIB and RFC 1354 is the recognition (explicitly discussed but by consensus left to future work) that CIDR routes may have the same network number but different network masks. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: F. Baker |
| RFC2097 The PPP NetBIOS Frames Control Protocol (NBFCP) This document defines the Network Control Protocol for establishing and configuring the NBF protocol over PPP. The NBFCP protocol is only applicable for an end system to connect to a peer system or the LAN that peer system is connected to. [STANDARDS-TRACK] | January 1997 Status: PROPOSED STANDARD Autor: G. Pall |
| RFC2098 Toshiba's Router Architecture Extensions for ATM : Overview This memo describes a new internetworking architecture which makes better use of the property of ATM. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: Y. Katsube, K. Nagami, H. Esaki |
| RFC2099 Request for Comments Summary RFC Numbers 2000-2099 | March 1997 Status: INFORMATIONAL Autor: J. Elliott |
| RFC2100 The Naming of Hosts This RFC is a commentary on the difficulty of deciding upon an acceptably distinctive hostname for one's computer, a problem which grows in direct proportion to the logarithmically increasing size of the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: J. Ashworth |
| RFC2101 IPv4 Address Behaviour Today The main purpose of this note is to clarify the current interpretation of the 32-bit IP version 4 address space, whose significance has changed substantially since it was originally defined. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: B. Carpenter, J. Crowcroft, Y. Rekhter |
| RFC2102 Multicast Support for Nimrod : Requirements and Solution Approaches Nimrod does not specify a particular solution for multicasting. Rather, Nimrod may use any of a number of emerging multicast techniques. We identify the requirements that Nimrod has of a solution for multicast support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: R. Ramanathan |
| RFC2103 Mobility Support for Nimrod : Challenges and Solution Approaches We discuss the issue of mobility in Nimrod. While a mobility solution is not part of the Nimrod architecture, Nimrod does require that the solution have certain characteristics. We identify the requirements that Nimrod has of any solution for mobility support. We also classify and compare existing approaches for supporting mobility within an internetwork and discuss their advantages and disadvantages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: R. Ramanathan |
| RFC2104 HMAC: Keyed-Hashing for Message Authentication This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind | February 1997 Status: INFORMATIONAL Autor: H. Krawczyk, M. Bellare, R. Canetti |
| RFC2105 Cisco Systems' Tag Switching Architecture Overview This document provides an overview of a novel approach to network layer packet forwarding, called tag switching. The two main components of the tag switching architecture - forwarding and control - are described. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: Y. Rekhter, B. Davie, D. Katz, E. Rosen, G. Swallow |
| RFC2106 Data Link Switching Remote Access Protocol This memo describes the Data Link Switching Remote Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: S. Chiang, J. Lee, H. Yasuda |
| RFC2107 Ascend Tunnel Management Protocol - ATMP This document specifies a generic tunnel management protocol that allows remote dial-in users to access their home network as if they were directly attached to the home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: K. Hamzeh |
| RFC2108 Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 10 and 100 Mb/second baseband repeaters based on IEEE Std 802.3 Section 30, "10 & | February 1997 Status: PROPOSED STANDARD Autor: K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie |
| RFC2109 HTTP State Management Mechanism This document specifies a way to create a stateful session with HTTP requests and responses. It describes two new headers, Cookie and Set- Cookie, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal, but it can interoperate with HTTP/1.0 user agents that use Netscape's method. [STANDARDS-TRACK] | February 1997 Status: HISTORIC Autor: D. Kristol, L. Montulli |
| RFC2110 MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML) This document describes a set of guidelines that will allow conforming mail user agents to be able to send, deliver and display these objects, such as HTML objects, that can contain links represented by URIs. [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: J. Palme, A. Hopmann |
| RFC2111 Content-ID and Message-ID Uniform Resource Locators The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: E. Levinson |
| RFC2112 The MIME Multipart/Related Content-type The Multipart/Related content-type provides a common mechanism for representing objects that are aggregates of related MIME body parts. This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: E. Levinson |
| RFC2113 IP Router Alert Option This memo describes a new IP Option type that alerts transit routers to more closely examine the contents of an IP packet. [STANDARDS-TRACK] | February 1997 Status: PROPOSED STANDARD Autor: D. Katz |
| RFC2114 Data Link Switching Client Access Protocol This memo describes the Data Link Switching Client Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | February 1997 Status: INFORMATIONAL Autor: S. Chiang, J. Lee, H. Yasuda |
| RFC2115 Management Information Base for Frame Relay DTEs Using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP- based internets. In particular, it defines objects for managing Frame Relay interfaces on DTEs. [STANDARDS-TRACK] | September 1997 Status: DRAFT STANDARD Autor: C. Brown, F. Baker |
| RFC2116 X.500 Implementations Catalog-96 This document is a revision to [RFC 1632]: A Revised Catalog of Available X.500 Implementations and is based on the results of data collection via a WWW home page that enabled implementors to submit new or updated descriptions of currently available implementations of X.500, including commercial products and openly available offerings. [RFC 1632] is a revision of [RFC 1292]. This document contains detailed description of 31 X.500 implementations - DSAs, DUAs, and DUA interfaces. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: C. Apple, K. Rossen |
| RFC2117 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification This document describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This memo defines an Experimental Protocol for the Internet community. | June 1997 Status: EXPERIMENTAL Autor: D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei |
| RFC2118 Microsoft Point-To-Point Compression (MPPC) Protocol This document describes the use of the Microsoft Point to Point Compression protocol (also referred to as MPPC in this document) for compressing PPP encapsulated packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1997 Status: INFORMATIONAL Autor: G. Pall |
| RFC2119 Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | March 1997 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC2120 Managing the X.500 Root Naming Context This document describes the use of 1993 ISO X.500 Standard protocols for managing the root context. Whilst the ASN.1 is compatible with that of the X.500 Standard, the actual settings of the parameters are supplementary to that of the X.500 Standard. This memo defines an Experimental Protocol for the Internet community. | March 1997 Status: EXPERIMENTAL Autor: D. Chadwick |
| RFC2121 Issues affecting MARS Cluster Size This document provides a qualitative look at the issues constraining a MARS Cluster's size, including the impact of VC limits in switches and NICs, geographical distribution of cluster members, and the use of VC Mesh or MCS modes to support multicast groups. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1997 Status: INFORMATIONAL Autor: G. Armitage |
| RFC2122 VEMMI URL Specification A new URL scheme, "vemmi" is defined. VEMMI is a new international standard for on-line multimedia services, that is both an ITU-T (International Telecommunications Union, ex. CCITT) International Standard (T.107) and an European Standard (ETSI European Telecommunications Standard Institute) standard (ETS 300 382, obsoleted by ETS 300 709). [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: D. Mavrakis, H. Layec, K. Kartmann |
| RFC2123 Traffic Flow Measurement: Experiences with NeTraMet This memo records experiences in implementing and using the Traffic Flow Measurement Architecture and Meter MIB. It discusses the implementation of NeTraMet (a traffic meter) and NeMaC (a combined manager and meter reader), considers the writing of meter rule sets and gives some guidance on setting up a traffic flow measurement system using NeTraMet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1997 Status: INFORMATIONAL Autor: N. Brownlee |
| RFC2124 Cabletron's Light-weight Flow Admission Protocol Specification Version 1.0 This document specifies the protocol between the switch Connection Control Entity (CCE) and the external FAS. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | March 1997 Status: INFORMATIONAL Autor: P. Amsden, J. Amweg, P. Calato, S. Bensley, G. Lyons |
| RFC2125 The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP) This document proposes a method to manage the dynamic bandwidth allocation of implementations supporting the PPP multilink protocol. This is done by defining the Bandwidth Allocation Protocol (BAP), as well as its associated control protocol, the Bandwidth Allocation Control Protocol (BACP). [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: C. Richards, K. Smith |
| RFC2126 ISO Transport Service on top of TCP (ITOT) This document is a revision to STD35, RFC1006. This document describes the mechanism to allow ISO Transport Services to run over TCP over IPv4 or IPv6. It also defines a number of new features, which are not provided in RFC1006. [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: Y. Pouffary, A. Young |
| RFC2127 ISDN Management Information Base using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a minimal set of managed objects for SNMP-based management of ISDN terminal interfaces. [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: G. Roeck |
| RFC2128 Dial Control Management Information Base using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing demand access circuits, including ISDN. [STANDARDS-TRACK] | March 1997 Status: PROPOSED STANDARD Autor: G. Roeck |
| RFC2129 Toshiba's Flow Attribute Notification Protocol (FANP) Specification This memo discusses Flow Attribute Notification Protocol (FANP), which is a protocol between neighbor nodes for the management of cut-through packet forwarding functionalities. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: K. Nagami, Y. Katsube, Y. Shobatake, A. Mogi, S. Matsuzawa, T. Jinmei, H. Esaki |
| RFC2130 The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996 This report details the conclusions of an IAB-sponsored invitational workshop held 29 February - 1 March, 1996, to discuss the use of character sets on the Internet. It motivates the need to have character set handling in Internet protocols which transmit text, provides a conceptual framework for specifying character sets, recommends the use of MIME tagging for transmitted text, recommends a default character set *without* stating that there is no need for other character sets, and makes a series of recommendations to the IAB, IANA, and the IESG for furthering the integration of the character set framework into text transmission protocols. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: C. Weider, C. Preston, K. Simonsen, H. Alvestrand, R. Atkinson, M. Crispin, P. Svanberg |
| RFC2131 Dynamic Host Configuration Protocol The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts on a TCPIP network. DHCP is based on the Bootstrap Protocol (BOOTP), adding the capability of automatic allocation of reusable network addresses and additional configuration options. [STANDARDS-TRACK] | March 1997 Status: DRAFT STANDARD Autor: R. Droms |
| RFC2132 DHCP Options and BOOTP Vendor Extensions This document specifies the current set of DHCP options. Future options will be specified in separate RFCs. The current list of valid options is also available in ftp://ftp.isi.edu/in-notes/iana/assignments. [STANDARDS-TRACK] | March 1997 Status: DRAFT STANDARD Autor: S. Alexander, R. Droms |
| RFC2133 Basic Socket Interface Extensions for IPv6 This memo defines a set of extensions to the socket interface to support the larger address size and new features of IPv6. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: R. Gilligan, S. Thomson, J. Bound, W. Stevens |
| RFC2134 Articles of Incorporation of Internet Society These are the articles of incorporation of the Internet Society. They are published for the information of the IETF community at the request of the poisson working group. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: ISOC Board of Trustees |
| RFC2135 Internet Society By-Laws These are the by-laws of the Internet Society, as amended, as of June 1996. They are published for the information of the IETF community at the request of the poisson working group. Please refer to the ISOC web page (www.isoc.org) for the current version of the by-laws. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: ISOC Board of Trustees |
| RFC2136 Dynamic Updates in the Domain Name System (DNS UPDATE) Using this specification of the UPDATE opcode, it is possible to add or delete RRs or RRsets from a specified zone. Prerequisites are specified separately from update operations, and can specify a dependency upon either the previous existence or nonexistence of an RRset, or the existence of a single RR. [STANDARDS-TRACK] | April 1997 Status: PROPOSED STANDARD Autor: P. Vixie, S. Thomson, Y. Rekhter, J. Bound |
| RFC2137 Secure Domain Name System Dynamic Update This memo describes how to use DNSSEC digital signatures covering requests and data to secure updates and restrict updates to those authorized to perform them as indicated by the updater's possession of cryptographic keys. [STANDARDS-TRACK] | April 1997 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC2138 Remote Authentication Dial In User Service (RADIUS) This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK] | April 1997 Status: PROPOSED STANDARD Autor: C. Rigney, A. Rubens, W. Simpson, S. Willens |
| RFC2139 RADIUS Accounting This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: C. Rigney |
| RFC2140 TCP Control Block Interdependence This memo makes the case for interdependent TCP control blocks, where part of the TCP state is shared among similar concurrent connections, or across similar connection instances. TCP state includes a combination of parameters, such as connection state, current round-trip time estimates, congestion control information, and process information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | April 1997 Status: INFORMATIONAL Autor: J. Touch |
| RFC2141 URN Syntax Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers. This document sets forward the canonical syntax for URNs. [STANDARDS-TRACK] | May 1997 Status: PROPOSED STANDARD Autor: R. Moats |
| RFC2142 Mailbox Names for Common Services, Roles and Functions This specification enumerates and describes Internet mail addresses (mailbox name @ host reference) to be used when contacting personnel at an organization. [STANDARDS-TRACK] | May 1997 Status: PROPOSED STANDARD Autor: D. Crocker |
| RFC2143 Encapsulating IP with the Small Computer System Interface This document outlines a protocol for connecting hosts running the TCP/IP protocol suite over a Small Computer System Interface (SCSI) bus. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. | May 1997 Status: EXPERIMENTAL Autor: B. Elliston |
| RFC2144 The CAST-128 Encryption Algorithm There is a need in the Internet community for an unencumbered encryption algorithm with a range of key sizes that can provide security for a variety of cryptographic applications and protocols. This document describes an existing algorithm that can be used to satisfy this requirement. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1997 Status: INFORMATIONAL Autor: C. Adams |
| RFC2145 Use and Interpretation of HTTP Version Numbers HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1997 Status: INFORMATIONAL Autor: J. C. Mogul, R. Fielding, J. Gettys, H. Frystyk |
| RFC2146 U.S. Government Internet Domain Names This memo provides an update and clarification to RFC 1816. This document describes the registration policies for the top-level domain ".GOV". The purpose of the domain is to provide naming conventions that identify US Federal government agencies in order to facilitate access to their electronic resources. This memo provides guidance for registrations by Federal Agencies that avoids name duplication and facilitates responsiveness to the public. It restricts registrations to coincide with the approved structure of the US government and the advice of its Chief Information Officers. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1997 Status: INFORMATIONAL Autor: Federal Networking Council |
| RFC2147 TCP and UDP over IPv6 Jumbograms IPv6 supports datagrams larger than 65535 bytes long, often referred to as jumbograms, through use of the Jumbo Payload hop-by-hop option. The UDP protocol has a 16-bit length field that keeps it from being able to make use of jumbograms, and though TCP does not have a length field, both the MSS option and the Urgent field are constrained by 16-bits. This document describes some simple changes that can be made to allow TCP and UDP to make use of IPv6 jumbograms. [STANDARDS-TRACK] | May 1997 Status: PROPOSED STANDARD Autor: D. Borman |
| RFC2148 Deployment of the Internet White Pages Service This document describes the way in which the Internet White Pages Service is best exploited using today's experience, today's protocols, today's products and today's procedures. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 1997 Status: BEST CURRENT PRACTICE Autor: H. Alvestrand, P. Jurg |
| RFC2149 Multicast Server Architectures for MARS-based ATM multicasting This memo provides details on the design and implementation of an MCS, building on the core mechanisms defined in RFC 2022. It also provides a mechanism for using multiple MCSs per group for providing fault tolerance. This approach can be used with RFC 2022 based MARS server and clients, without needing any change in their functionality. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1997 Status: INFORMATIONAL Autor: R. Talpade, M. Ammar |
| RFC2150 Humanities and Arts: Sharing Center Stage on the Internet The purpose of this document is to provide members of the Arts and Humanities communities with an introduction to the Internet as a valuable tool, resource, and medium for the creation, presentation, and preservation of Arts and Humanities-based content. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | October 1997 Status: INFORMATIONAL Autor: J. Max, W. Stickle |
| RFC2151 A Primer On Internet and TCP/IP Tools and Utilities This memo is an introductory guide to many of the most commonly- available TCP/IP and Internet tools and utilities. It also describes discussion lists accessible from the Internet, ways to obtain Internet and TCP/IP documents, and some resources that help users weave their way through the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: G. Kessler, S. Shepard |
| RFC2152 UTF-7 A Mail-Safe Transformation Format of Unicode This document describes a transformation format of Unicode that contains only 7-bit ASCII octets and is intended to be readable by humans in the limiting case that the document consists of characters from the US-ASCII repertoire. It also specifies how this transformation format is used in the context of MIME and RFC 1641, "Using Unicode with MIME". This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | May 1997 Status: INFORMATIONAL Autor: D. Goldsmith, M. Davis |
| RFC2153 PPP Vendor Extensions The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection; and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This document provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1997 Status: INFORMATIONAL Autor: W. Simpson |
| RFC2154 OSPF with Digital Signatures This memo describes the extensions to OSPF required to add digital signature authentication to Link State data, and to provide a certification mechanism for router data. Added LSA processing and key management is detailed. A method for migration from, or co-existence with, standard OSPF V2 is described. This memo defines an Experimental Protocol for the Internet community. | June 1997 Status: EXPERIMENTAL Autor: S. Murphy, M. Badger, B. Wellington |
| RFC2155 Definitions of Managed Objects for APPN using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with APPN (Advanced Peer-to-Peer Networking) capabilities. This memo identifies managed objects for the APPN protocol. [STANDARDS-TRACK] | June 1997 Status: PROPOSED STANDARD Autor: B. Clouston, B. Moore |
| RFC2156 MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME This document relates primarily to the ITU-T 1988 and 1992 X.400 Series Recommendations / ISO IEC 10021 International Standard. This ISO/ITU-T standard is referred to in this document as "X.400", which is a convenient shorthand. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: S. Kille |
| RFC2157 Mapping between X.400 and RFC-822/MIME Message Bodies This document defines how to map body parts of X.400 messages into MIME entities and vice versa, including the handling of multipart messages and forwarded messages. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: H. Alvestrand |
| RFC2158 X.400 Image Body Parts This document contains the body parts defined in RFC 1495 for carrying image formats that were originally defined in MIME through an X.400 system. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: H. Alvestrand |
| RFC2159 A MIME Body Part for FAX This document contains the definitions, originally contained in RFC 1494, on how to carry CCITT G3Fax in MIME, and how to translate it to its X.400 representation. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: H. Alvestrand |
| RFC2160 Carrying PostScript in X.400 and MIME This document describes methods for carrying PostScript information in the two standard mail systems MIME and X.400, and the conversion between them. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: H. Alvestrand |
| RFC2161 A MIME Body Part for ODA This document contains the definitions, originally contained in RFC 1495 and RFC 1341, on how to carry ODA in MIME, and how to translate it to its X.400 representation. This memo defines an Experimental Protocol for the Internet community. | January 1998 Status: EXPERIMENTAL Autor: H. Alvestrand |
| RFC2162 MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail The standard referred shortly into this document as "X.400" relates to the ISO/IEC 10021 - CCITT 1984, 1988 and 1992 X.400 Series Recommendations covering the Message Oriented Text Interchange Service (MOTIS). This document covers the Inter Personal Messaging System (IPMS) only. This memo defines an Experimental Protocol for the Internet community. | January 1998 Status: EXPERIMENTAL Autor: C. Allocchio |
| RFC2163 Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM) This memo is the complete technical specification to store in the Internet Domain Name System (DNS) the mapping information (MCGAM) needed by MIXER conformant e-mail gateways and other tools to map RFC822 domain names into X.400 O/R names and vice versa. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: C. Allocchio |
| RFC2164 Use of an X.500/LDAP directory to support MIXER address mapping This specification defines how to represent and maintain these mappings (MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAP directory. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: S. Kille |
| RFC2165 Service Location Protocol The Service Location Protocol provides a scalable framework for the discovery and selection of network services. Using this protocol, computers using the Internet no longer need so much static configuration of network services for network based applications. This is especially important as computers become more portable, and users less tolerant or able to fulfill the demands of network system administration. [STANDARDS-TRACK] | June 1997 Status: PROPOSED STANDARD Autor: J. Veizades, E. Guttman, C. Perkins, S. Kaplan |
| RFC2166 APPN Implementer's Workshop Closed Pages Document DLSw v2.0 Enhancements This document specifies a set of extensions to RFC 1795 designed to improve the scalability of DLSw clarifications to RFC 1795 in the light of the implementation experience to-date. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: D. Bryant, P. Brittain |
| RFC2167 Referral Whois (RWhois) Protocol V1.5 This memo describes Version 1.5 of the client/server interaction of RWhois. RWhois provides a distributed system for the discovery, retrieval, and maintenance of directory information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: S. Williamson, M. Kosters, D. Blacka, J. Singh, K. Zeilstra |
| RFC2168 Resolution of Uniform Resource Identifiers using the Domain Name System The requirements document for URN resolution systems defines the concept of a "resolver discovery service". This document describes the first, experimental, RDS. It is implemented by a new DNS Resource Record, NAPTR (Naming Authority PoinTeR), that provides rules for mapping parts of URIs to domain names. This memo defines an Experimental Protocol for the Internet community. | June 1997 Status: EXPERIMENTAL Autor: R. Daniel, M. Mealling |
| RFC2169 A Trivial Convention for using HTTP in URN Resolution This document specifies the "THTTP" resolution protocol - a trivial convention for encoding resolution service requests and responses as HTTP 1.0 or 1.1 requests and responses. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | June 1997 Status: EXPERIMENTAL Autor: R. Daniel |
| RFC2170 Application REQuested IP over ATM (AREQUIPA) This document specifies a method for allowing ATM-attached hosts that have direct ATM connectivity to set up end-to-end IP over ATM connections within the reachable ATM cloud, on request from applications, and for the exclusive use by the requesting applications. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1997 Status: INFORMATIONAL Autor: W. Almesberger, J. Le Boudec, P. Oechslin |
| RFC2171 MAPOS - Multiple Access Protocol over SONET/SDH Version 1 This memo documents a multiple access protocol for transmission of network-protocol datagrams, encapsulated in High-Level Data Link Control (HDLC) frames, over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: K. Murakami, M. Maruyama |
| RFC2172 MAPOS Version 1 Assigned Numbers This memo documents the parameters used in the Multiple Access Protocol over SONET/SDH Version 1. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: M. Maruyama, K. Murakami |
| RFC2173 A MAPOS version 1 Extension - Node Switch Protocol This document describes a MAPOS extension, Node Switch Protocol, for automatic node address assignment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: K. Murakami, M. Maruyama |
| RFC2174 A MAPOS version 1 Extension - Switch-Switch Protocol This memo documents a MAPOS (Multiple Access Protocol over SONET/SDH) version 1 extension, Switch Switch Protocol which provides dynamic routing for unicast, broadcast, and multicast. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: K. Murakami, M. Maruyama |
| RFC2175 MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing This memo documents MAPOS 16, a multiple access protocol for transmission of network-protocol datagrams, encapsulated in HDLC frames with 16 bit addressing, over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: K. Murakami, M. Maruyama |
| RFC2176 IPv4 over MAPOS Version 1 This memo documents a mechanism for supporting Version 4 of the Internet Protocol (IPv4) on Version 1 of the Multiple Access Protocol over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1997 Status: INFORMATIONAL Autor: K. Murakami, M. Maruyama |
| RFC2177 IMAP4 IDLE command This document specifies the syntax of an IDLE command, which will allow a client to tell the server that it's ready to accept such real-time updates. [STANDARDS-TRACK] | June 1997 Status: PROPOSED STANDARD Autor: B. Leiba |
| RFC2178 OSPF Version 2 This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest-path tree. | July 1997 Status: DRAFT STANDARD Autor: J. Moy |
| RFC2179 Network Security For Trade Shows This document is designed to assist vendors and other participants in trade shows, such as Networld+Interop, in designing effective protection against network and system attacks by unauthorized individuals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1997 Status: INFORMATIONAL Autor: A. Gwinn |
| RFC2180 IMAP4 Multi-Accessed Mailbox Practice The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1997 Status: INFORMATIONAL Autor: M. Gahrns |
| RFC2181 Clarifications to the DNS Specification This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. [STANDARDS-TRACK] | July 1997 Status: PROPOSED STANDARD Autor: R. Elz, R. Bush |
| RFC2182 Selection and Operation of Secondary DNS Servers This document discusses the selection of secondary servers for DNS zones.The number of servers appropriate for a zone is also discussed, and some general secondary server maintenance issues considered. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | July 1997 Status: BEST CURRENT PRACTICE Autor: R. Elz, R. Bush, S. Bradner, M. Patton |
| RFC2183 Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field This memo provides a mechanism whereby messages conforming to the MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can convey presentational information. It specifies the "Content- Disposition" header field, which is optional and valid for any MIME entity ("message" or "body part"). [STANDARDS-TRACK] | August 1997 Status: PROPOSED STANDARD Autor: R. Troost, S. Dorner, K. Moore |
| RFC2184 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. [STANDARDS-TRACK] | August 1997 Status: PROPOSED STANDARD Autor: N. Freed, K. Moore |
| RFC2185 Routing Aspects of IPv6 Transition This document gives an overview of the routing aspects of the IPv6 transition. It is based on the protocols defined in the document "Transition Mechanisms for IPv6 Hosts and Routers." Readers should be familiar with the transition mechanisms before reading this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: R. Callon, D. Haskin |
| RFC2186 Internet Cache Protocol (ICP), version 2 This document describes version 2 of the Internet Cache Protocol (ICPv2) as currently implemented in two World-Wide Web proxy cache packages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: D. Wessels, K. Claffy |
| RFC2187 Application of Internet Cache Protocol (ICP), version 2 This document describes the application of ICPv2 (Internet Cache Protocol version 2, RFC2186) to Web caching. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: D. Wessels, K. Claffy |
| RFC2188 AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2 This document specifies the service model, the notation and protocol for Efficient Short Remote Operations (ESRO). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: M. Banan, M. Taylor, J. Cheng |
| RFC2189 Core Based Trees (CBT version 2) Multicast Routing -- Protocol Specification -- This document describes the Core Based Tree (CBT version 2) network layer multicast routing protocol. CBT builds a shared multicast distribution tree per group, and is suited to inter- and intra-domain multicast routing. This memo defines an Experimental Protocol for the Internet community. | September 1997 Status: HISTORIC Autor: A. Ballardie |
| RFC2190 RTP Payload Format for H.263 Video Streams This document specifies the payload format for encapsulating an H.263 bitstream in the Real-Time Transport Protocol (RTP). [STANDARDS-TRACK] | September 1997 Status: HISTORIC Autor: C. Zhu |
| RFC2191 VENUS - Very Extensive Non-Unicast Service This document focuses exclusively on the problems associated with extending the MARS model to cover multiple clusters or clusters spanning more than one subnet. It describes a hypothetical solution, dubbed "Very Extensive NonUnicast Service" (VENUS), and shows how complex such a service would be. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: G. Armitage |
| RFC2192 IMAP URL Scheme This document defines a URL scheme for referencing objects on an IMAP server. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: C. Newman |
| RFC2193 IMAP4 Mailbox Referrals Mailbox referrals allow clients to seamlessly access mailboxes that are distributed across several IMAP4 servers. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: M. Gahrns |
| RFC2194 Review of Roaming Implementations This document reviews the design and functionality of existing roaming implementations. Examples of cases where roaming capability might be required include ISP "confederations" and ISP-provided corporate network access support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: B. Aboba, J. Lu, J. Alsop, J. Ding, W. Wang |
| RFC2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: J. Klensin, R. Catoe, P. Krumviede |
| RFC2196 Site Security Handbook This handbook is a guide to developing computer security policies and procedures for sites that have systems on the Internet. The purpose of this handbook is to provide practical guidance to administrators trying to secure their information and services. The subjects covered include policy content and formation, a broad range of technical system and network security topics, and security incident response. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: B. Fraser |
| RFC2197 SMTP Service Extension for Command Pipelining This memo defines an extension to the SMTP service whereby a server can indicate the extent of its ability to accept multiple commands in a single TCP send operation. [STANDARDS-TRACK] | September 1997 Status: DRAFT STANDARD Autor: N. Freed |
| RFC2198 RTP Payload for Redundant Audio Data This document describes a payload format for use with the real-time transport protocol (RTP), version 2, for encoding redundant audio data. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: C. Perkins, I. Kouvelas, O. Hodson, V. Hardman, M. Handley, J.C. Bolot, A. Vega-Garcia, S. Fosse-Parisis |
| RFC2199 Request for Comments Summary RFC Numbers 2100-2199 | January 1998 Status: INFORMATIONAL Autor: A. Ramos |
| RFC2200 Internet Official Protocol Standards A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. [STANDARDS-TRACK] | June 1997 Status: HISTORIC Autor: J. Postel |
| RFC2201 Core Based Trees (CBT) Multicast Routing Architecture CBT is a multicast routing architecture that builds a single delivery tree per group which is shared by all of the group's senders and receivers. This memo defines an Experimental Protocol for the Internet community. | September 1997 Status: HISTORIC Autor: A. Ballardie |
| RFC2202 Test Cases for HMAC-MD5 and HMAC-SHA-1 This document provides two sets of test cases for HMAC-MD5 and HMAC- SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of the HMAC [HMAC] message authentication function using the MD5 [MD5] hash function and the SHA-1 [SHA] hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: P. Cheng, R. Glenn |
| RFC2203 RPCSEC_GSS Protocol Specification This memo describes an ONC/RPC security flavor that allows RPC protocols to access the Generic Security Services Application Programming Interface (referred to henceforth as GSS-API). [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: M. Eisler, A. Chiu, L. Ling |
| RFC2204 ODETTE File Transfer Protocol This memo describes a file transfer protocol to facilitate electronic data interchange between trading partners. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: D. Nash |
| RFC2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification This memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet. RSVP provides receiver-initiated setup of resource reservations for multicast or unicast data flows, with good scaling and robustness properties. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: R. Braden, L. Zhang, S. Berson, S. Herzog, S. Jamin |
| RFC2206 RSVP Management Information Base using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Resource Reservation Protocol (RSVP) within the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: F. Baker, J. Krawczyk, A. Sastry |
| RFC2207 RSVP Extensions for IPSEC Data Flows This document presents extensions to Version 1 of RSVP. These extensions permit support of individual data flows using RFC 1826, IP Authentication Header (AH) or RFC 1827, IP Encapsulating Security Payload (ESP). [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: L. Berger, T. O'Malley |
| RFC2208 Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment This document describes the applicability of RSVP along with the Integrated Services protocols and other components of resource reservation and offers guidelines for deployment of resource reservation at this time. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: A. Mankin, F. Baker, B. Braden, S. Bradner, M. O'Dell, A. Romanow, A. Weinrib, L. Zhang |
| RFC2209 Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules This memo contains an algorithmic description of the rules used by an RSVP implementation for processing messages. It is intended to clarify the version 1 RSVP protocol specification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: R. Braden, L. Zhang |
| RFC2210 The Use of RSVP with IETF Integrated Services This note describes the use of the RSVP resource reservation protocol with the Controlled-Load and Guaranteed QoS control services. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: J. Wroclawski |
| RFC2211 Specification of the Controlled-Load Network Element Service This memo specifies the network element behavior required to deliver Controlled-Load service in the Internet. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: J. Wroclawski |
| RFC2212 Specification of Guaranteed Quality of Service This memo describes the network element behavior required to deliver a guaranteed service (guaranteed delay and bandwidth) in the Internet. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: S. Shenker, C. Partridge, R. Guerin |
| RFC2213 Integrated Services Management Information Base using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: F. Baker, J. Krawczyk, A. Sastry |
| RFC2214 Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the the interface attributes defined in the Guaranteed Service of the Integrated Services Model. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: F. Baker, J. Krawczyk, A. Sastry |
| RFC2215 General Characterization Parameters for Integrated Service Network Elements This memo defines a set of general control and characterization parameters for network elements supporting the IETF integrated services QoS control framework. [STANDARDS-TRACK] | September 1997 Status: PROPOSED STANDARD Autor: S. Shenker, J. Wroclawski |
| RFC2216 Network Element Service Specification Template This document defines a framework for specifying services provided by network elements, and available to applications, in an internetwork which offers multiple qualities of service. The document first provides some necessary context -- including relevant definitions and suggested data formats -- and then specifies a "template" which service specification documents should follow. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1997 Status: INFORMATIONAL Autor: S. Shenker, J. Wroclawski |
| RFC2217 Telnet Com Port Control Option This memo proposes a protocol to allow greater use of modems attached to a network for outbound dialing purposes. This memo defines an Experimental Protocol for the Internet community. | October 1997 Status: EXPERIMENTAL Autor: G. Clark |
| RFC2218 A Common Schema for the Internet White Pages Service This document specifies the minimum set of core attributes of a White Pages entry for an individual and describes how new objects with those attributes can be defined and published. [STANDARDS-TRACK] | October 1997 Status: PROPOSED STANDARD Autor: T. Genovese, B. Jennings |
| RFC2219 Use of DNS Aliases for Network Services It has become a common practice to use symbolic names (usually CNAMEs) in the Domain Name Service (DNS - [RFC-1034, RFC-1035]) to refer to network services such as anonymous FTP [RFC-959] servers, Gopher [RFC- 1436] servers, and most notably World-Wide Web HTTP [RFC-1945] servers. This is desirable for a number of reasons. It provides a way of moving services from one machine to another transparently, and a mechanism by which people or agents may programmatically discover that an organization runs, say, a World-Wide Web server. Although this approach has been almost universally adopted, there is no standards document or similar specification for these commonly used names. This document seeks to rectify this situation by gathering together the extant 'folklore' on naming conventions, and proposes a mechanism for accommodating new protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1997 Status: BEST CURRENT PRACTICE Autor: M. Hamilton, R. Wright |
| RFC2220 The Application/MARC Content-type This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | October 1997 Status: INFORMATIONAL Autor: R. Guenther |
| RFC2221 IMAP4 Login Referrals When dealing with large amounts of users and many IMAP4 [RFC-2060] servers, it is often necessary to move users from one IMAP4 server to another. Login referrals allow clients to transparently connect to an alternate IMAP4 server, if their home IMAP4 server has changed. [STANDARDS-TRACK] | October 1997 Status: PROPOSED STANDARD Autor: M. Gahrns |
| RFC2222 Simple Authentication and Security Layer (SASL) This document describes a method for adding authentication support to connection-based protocols. [STANDARDS-TRACK] | October 1997 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC2223 Instructions to RFC Authors This Request for Comments (RFC) provides information about the preparation of RFCs, and certain policies relating to the publication of RFCs. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | October 1997 Status: INFORMATIONAL Autor: J. Postel, J. Reynolds |
| RFC2224 NFS URL Scheme A new URL scheme, 'nfs' is defined. It is used to refer to files and directories on NFS servers using the general URL syntax defined in RFC 1738, "Uniform Resource Locators (URL)". This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | October 1997 Status: INFORMATIONAL Autor: B. Callaghan |
| RFC2225 Classical IP and ARP over ATM This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: M. Laubach, J. Halpern |
| RFC2226 IP Broadcast over ATM Networks This memo describes how the IP multicast service being developed by the IP over ATM working group may be used to support IP broadcast transmission. [STANDARDS-TRACK] | October 1997 Status: PROPOSED STANDARD Autor: T. Smith, G. Armitage |
| RFC2227 Simple Hit-Metering and Usage-Limiting for HTTP This document proposes a simple extension to HTTP, using a new "Meter" header. [STANDARDS-TRACK] | October 1997 Status: PROPOSED STANDARD Autor: J. Mogul, P. Leach |
| RFC2228 FTP Security Extensions This document defines extensions to the FTP specification STD 9, RFC | October 1997 Status: PROPOSED STANDARD Autor: M. Horowitz, S. Lunt |
| RFC2229 A Dictionary Server Protocol The Dictionary Server Protocol (DICT) is a TCP transaction based query/response protocol that allows a client to access dictionary definitions from a set of natural language dictionary databases. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | October 1997 Status: INFORMATIONAL Autor: R. Faith, B. Martin |
| RFC2230 Key Exchange Delegation Record for the DNS This note describes a mechanism whereby authorisation for one node to act as key exchanger for a second node is delegated and made available via the Secure DNS. This mechanism is intended to be used only with the Secure DNS. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | November 1997 Status: INFORMATIONAL Autor: R. Atkinson |
| RFC2231 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. This memo also defines an extension to the encoded words defined in RFC 2047 to allow the specification of the language to be used for display as well as the character set. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: N. Freed, K. Moore |
| RFC2232 Definitions of Managed Objects for DLUR using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with DLUR (Dependent LU Requester) capabilities. This memo identifies managed objects for the DLUR protocol. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: B. Clouston, B. Moore |
| RFC2233 The Interfaces Group MIB using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing Network Interfaces. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: K. McCloghrie, F. Kastenholz |
| RFC2234 Augmented BNF for Syntax Specifications: ABNF In the early days of the Arpanet, each specification contained its own definition of ABNF. This included the email specifications, RFC733 and then RFC822 which have come to be the common citations for defining ABNF. The current document separates out that definition, to permit selective reference. Predictably, it also provides some modifications and enhancements. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: D. Crocker, P. Overell |
| RFC2235 Hobbes' Internet Timeline This document presents a history of the Internet in timeline fashion, highlighting some of the key events and technologies which helped shape the Internet as we know it today. A growth summary of the Internet and some associated technologies is also included. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | November 1997 Status: INFORMATIONAL Autor: R. Zakon |
| RFC2236 Internet Group Management Protocol, Version 2 This memo documents IGMPv2, used by IP hosts to report their multicast group memberships to routers. It updates STD 5, RFC 1112. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: W. Fenner |
| RFC2237 Japanese Character Encoding for Internet Messages This memo defines an encoding scheme for the Japanese Characters, describes "ISO-2022-JP-1", which is used in electronic mail [RFC-822], and network news [RFC 1036]. Also this memo provides a listing of the Japanese Character Set that can be used in this encoding scheme. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | November 1997 Status: INFORMATIONAL Autor: K. Tamaru |
| RFC2238 Definitions of Managed Objects for HPR using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with HPR (High Performance Routing) capabilities. This memo identifies managed objects for the HPR protocol. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: B. Clouston, B. Moore |
| RFC2239 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing 10 and 100 Mb/second Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie, S. Roberts |
| RFC2240 A Legal Basis for Domain Name Allocation The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | November 1997 Status: INFORMATIONAL Autor: O. Vaughan |
| RFC2241 DHCP Options for Novell Directory Services This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. This document defines three new DHCP options for delivering configuration information to clients of the Novell Directory Services. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: D. Provan |
| RFC2242 NetWare/IP Domain Name and Information This document defines options that carry NetWare/IP domain name and NetWare/IP sub-options to DHCP clients. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: R. Droms, K. Fong |
| RFC2243 OTP Extended Responses This document provides a specification for a type of response to an OTP [RFC 1938] challenge that carries explicit indication of the response's encoding. This document also provides a specification for a response that allows an OTP generator to request that a server re-initialize a sequence and change parameters such as the secret pass phrase. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: C. Metz |
| RFC2244 ACAP -- Application Configuration Access Protocol The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: C. Newman, J. G. Myers |
| RFC2245 Anonymous SASL Mechanism As plaintext login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the SASL [SASL] framework. [STANDARDS-TRACK] | November 1997 Status: PROPOSED STANDARD Autor: C. Newman |
| RFC2246 The TLS Protocol Version 1.0 This document specifies Version 1.0 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications privacy over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. [STANDARDS-TRACK] | January 1999 Status: PROPOSED STANDARD Autor: T. Dierks, C. Allen |
| RFC2247 Using Domains in LDAP/X.500 Distinguished Names This document defines an algorithm by which a name registered with the Internet Domain Name Service [2] can be represented as an LDAP distinguished name. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: S. Kille, M. Wahl, A. Grimstad, R. Huber, S. Sataluri |
| RFC2248 Network Services Monitoring MIB This MIB may be used on its own for any application, and for most simple applications this will suffice. This MIB is also designed to serve as a building block which can be used in conjunction with application- specific monitoring and management. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: N. Freed, S. Kille |
| RFC2249 Mail Monitoring MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this memo extends the basic Network Services Monitoring MIB [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: N. Freed, S. Kille |
| RFC2250 RTP Payload Format for MPEG1/MPEG2 Video This memo describes a packetization scheme for MPEG video and audio streams. [STANDARDS-TRACK] The purpose of this document is to express the general Internet community's expectations of Computer Security Incident Response Teams (CSIRTs). It is not possible to define a set of requirements that would be appropriate for all teams, but it is possible and helpful to list and describe the general set of topics and issues which are of concern and interest to constituent communities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | January 1998 Status: PROPOSED STANDARD Autor: D. Hoffman, G. Fernando, V. Goyal, M. Civanlar |
| RFC2251 Lightweight Directory Access Protocol (v3) The protocol described in this document is designed to provide access to directories supporting the X.500 models, while not incurring the resource requirements of the X.500 Directory Access Protocol (DAP). [STANDARDS-TRACK] | December 1997 Status: PROPOSED STANDARD Autor: M. Wahl, T. Howes, S. Kille |
| RFC2252 Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP protocol. [STANDARDS-TRACK] | December 1997 Status: PROPOSED STANDARD Autor: M. Wahl, A. Coulbeck, T. Howes, S. Kille |
| RFC2253 Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names This specification defines the string format for representing names, which is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name. [STANDARDS-TRACK] | December 1997 Status: PROPOSED STANDARD Autor: M. Wahl, S. Kille, T. Howes |
| RFC2254 The String Representation of LDAP Search Filters This document defines a human-readable string format for representing LDAP search filters. [STANDARDS-TRACK] | December 1997 Status: PROPOSED STANDARD Autor: T. Howes |
| RFC2255 The LDAP URL Format This document describes a format for an LDAP Uniform Resource Locator. [STANDARDS-TRACK] | December 1997 Status: PROPOSED STANDARD Autor: T. Howes, M. Smith |
| RFC2256 A Summary of the X.500(96) User Schema for use with LDAPv3 This document provides an overview of the attribute types and object classes defined by the ISO and ITU-T committees in the X.500 documents, in particular those intended for use by directory clients. [STANDARDS-TRACK] | December 1997 Status: PROPOSED STANDARD Autor: M. Wahl |
| RFC2257 Agent Extensibility (AgentX) Protocol Version 1 This memo defines a standardized framework for extensible SNMP agents. It defines processing entities called master agents and subagents, a protocol (AgentX) used to communicate between them, and the elements of procedure by which the extensible agent processes SNMP protocol messages. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: M. Daniele, B. Wijnen, D. Francisco |
| RFC2258 Internet Nomenclator Project The goal of the Internet Nomenclator Project is to integrate the hundreds of publicly available CCSO servers from around the world. This document provides an overview of the Nomenclator system, describes how to register a CCSO server in the Internet Nomenclator Project, and how to use the Nomenclator search engine to find people on the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | January 1998 Status: INFORMATIONAL Autor: J. Ordille |
| RFC2259 Simple Nomenclator Query Protocol (SNQP) The Simple Nomenclator Query Protocol (SNQP) allows a client to communicate with a descriptive name service or other relational-style query service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind | January 1998 Status: INFORMATIONAL Autor: J. Elliott, J. Ordille |
| RFC2260 Scalable Support for Multi-homed Multi-provider Connectivity This document describes addressing and routing strategies for multi- homed enterprises attached to multiple Internet Service Providers (ISPs) that are intended to reduce the routing overhead due to these enterprises in the global Internet routing system. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | January 1998 Status: INFORMATIONAL Autor: T. Bates, Y. Rekhter |
| RFC2261 An Architecture for Describing SNMP Management Frameworks This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: D. Harrington, R. Presuhn, B. Wijnen |
| RFC2262 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2261]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: J. Case, D. Harrington, R. Presuhn, B. Wijnen |
| RFC2263 SNMPv3 Applications This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: D. Levi, P. Meyer, B. Stewart |
| RFC2264 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: U. Blumenthal, B. Wijnen |
| RFC2265 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: B. Wijnen, R. Presuhn, K. McCloghrie |
| RFC2266 Definitions of Managed Objects for IEEE 802.12 Repeater Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing network repeaters based on IEEE 802.12. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: J. Flick |
| RFC2267 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS attacks which use forged IP addresses to be propagated from 'behind' an Internet Service Provider's (ISP) aggregation point. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | January 1998 Status: INFORMATIONAL Autor: P. Ferguson, D. Senie |
| RFC2268 A Description of the RC2(r) Encryption Algorithm This memo describes a conventional (secret-key) block encryption algorithm, called RC2, which may be considered as a proposal for a DES replacement. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: R. Rivest |
| RFC2269 Using the MARS Model in non-ATM NBMA Networks This document is intended to state the obvious equivalences, and explain the less obvious implications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | January 1998 Status: INFORMATIONAL Autor: G. Armitage |
| RFC2270 Using a Dedicated AS for Sites Homed to a Single Provider With the increased growth of the Internet, the number of customers using BGP4 has grown significantly. RFC1930 outlines a set of guidelines for when one needs and should use an AS. However, the customer and service provider (ISP) are left with a problem as a result of this in that while there is no need for an allocated AS under the guidelines, certain conditions make the use of BGP4 a very pragmatic and perhaps only way to connect a customer homed to a single ISP. This paper proposes a solution to this problem in line with recommendations set forth in RFC1930. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | January 1998 Status: INFORMATIONAL Autor: J. Stewart, T. Bates, R. Chandra, E. Chen |
| RFC2271 An Architecture for Describing SNMP Management Frameworks This document describes an architecture for describing SNMP Management Frameworks. The architecture is designed to be modular to allow the evolution of the SNMP protocol standards over time. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: D. Harrington, R. Presuhn, B. Wijnen |
| RFC2272 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture [RFC2271]. It defines the procedures for dispatching potentially multiple versions of SNMP messages to the proper SNMP Message Processing Models, and for dispatching PDUs to SNMP applications. This document also describes one Message Processing Model - the SNMPv3 Message Processing Model. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: J. Case, D. Harrington, R. Presuhn, B. Wijnen |
| RFC2273 SNMPv3 Applications This memo describes five types of SNMP applications which make use of an SNMP engine as described in [RFC2261]. The types of application described are Command Generators, Command Responders, Notification Originators, Notification Receivers, and Proxy Forwarders. This memo also defines MIB modules for specifying targets of management operations, for notification filtering, and for proxy forwarding. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: D. Levi, P. Meyer, B. Stewart |
| RFC2274 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for providing SNMP message level security. This document also includes a MIB for remotely monitoring/managing the configuration parameters for this Security Model. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: U. Blumenthal, B. Wijnen |
| RFC2275 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) This document describes the View-based Access Control Model for use in the SNMP architecture [RFC2261]. It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: B. Wijnen, R. Presuhn, K. McCloghrie |
| RFC2276 Architectural Principles of Uniform Resource Name Resolution This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | January 1998 Status: INFORMATIONAL Autor: K. Sollins |
| RFC2277 IETF Policy on Character Sets and Languages This document is the current policies being applied by the Internet Engineering Steering Group (IESG) towards the standardization efforts in the Internet Engineering Task Force (IETF) in order to help Internet protocols fulfill these requirements. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | January 1998 Status: BEST CURRENT PRACTICE Autor: H. Alvestrand |
| RFC2278 IANA Charset Registration Procedures MIME [RFC-2045, RFC-2046, RFC-2047, RFC-2184] and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | January 1998 Status: INFORMATIONAL Autor: N. Freed, J. Postel |
| RFC2279 UTF-8, a transformation format of ISO 10646 UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo updates and replaces RFC 2044, in particular addressing the question of versions of the relevant standards. [STANDARDS-TRACK] | January 1998 Status: DRAFT STANDARD Autor: F. Yergeau |
| RFC2280 Routing Policy Specification Language (RPSL) This memo is the reference document for the Routing Policy Specification Language (RPSL). RPSL allows a network operator to be able to specify routing policies at various levels in the Internet hierarchy; for example at the Autonomous System (AS) level. At the same time, policies can be specified with sufficient detail in RPSL so that low level router configurations can be generated from them. RPSL is extensible; new routing protocols and new protocol features can be introduced at any time. [STANDARDS-TRACK] | January 1998 Status: PROPOSED STANDARD Autor: C. Alaettinoglu, T. Bates, E. Gerich, D. Karrenberg, D. Meyer, M. Terpstra, C. Villamizar |
| RFC2281 Cisco Hot Standby Router Protocol (HSRP) The memo specifies the Hot Standby Router Protocol (HSRP). The goal of the protocol is to allow hosts to appear to use a single router and to maintain connectivity even if the actual first hop router they are using fails. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: T. Li, B. Cole, P. Morton, D. Li |
| RFC2282 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 1998 Status: INFORMATIONAL Autor: J. Galvin |
| RFC2283 Multiprotocol Extensions for BGP-4 This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK] | February 1998 Status: PROPOSED STANDARD Autor: T. Bates, R. Chandra, D. Katz, Y. Rekhter |
| RFC2284 PPP Extensible Authentication Protocol (EAP) The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP also defines an extensible Link Control Protocol, which allows negotiation of an Authentication Protocol for authenticating its peer before allowing Network Layer protocols to transmit over the link. This document defines the PPP Extensible Authentication Protocol. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: L. Blunk, J. Vollbrecht |
| RFC2285 Benchmarking Terminology for LAN Switching Devices This document is intended to provide terminology for the benchmarking of local area network (LAN) switching devices. It extends the terminology already defined for benchmarking network interconnect devices in RFCs 1242 and 1944 to switching devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | February 1998 Status: INFORMATIONAL Autor: R. Mandeville |
| RFC2286 Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128 This document provides two sets of test cases for HMAC-RIPEMD160 and HMAC-RIPEMD128. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | February 1998 Status: INFORMATIONAL Autor: J. Kapp |
| RFC2287 Definitions of System-Level Managed Objects for Applications This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a basic set of managed objects for fault, configuration and performance management of applications from a systems perspective. [STANDARDS-TRACK] | February 1998 Status: PROPOSED STANDARD Autor: C. Krupczak, J. Saperia |
| RFC2288 Using Existing Bibliographic Identifiers as Uniform Resource Names This document discusses how three major bibliographic identifiers (the ISBN, ISSN and SICI) can be supported within the URN framework and the currently proposed syntax for URNs. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | February 1998 Status: INFORMATIONAL Autor: C. Lynch, C. Preston, R. Daniel |
| RFC2289 A One-Time Password System This document describes a one-time password authentication system (OTP). The system provides authentication for system access (login) and other applications requiring authentication that is secure against passive attacks based on replaying captured reusable passwords. [STANDARDS-TRACK] | February 1998 Status: STANDARD Autor: N. Haller, C. Metz, P. Nesser, M. Straw |
| RFC2290 Mobile-IPv4 Configuration Option for PPP IPCP Mobile IP [RFC 2002] defines media-independent procedures by which a Mobile Node can maintain existing transport and application-layer connections despite changing its point-of-attachment to the Internet and without changing its IP address. PPP [RFC 1661] provides a standard method for transporting multi-protocol packets over point-to-point links. As currently specified, Mobile IP Foreign Agents which support Mobile Node connections via PPP can do so only by first assigning unique addresses to those Mobile Nodes, defeating one of the primary advantages of Foreign Agents. This documents corrects this problem by defining the Mobile-IPv4 Configuration Option to the Internet Protocol Control Protocol (IPCP) [RFC 1332]. Using this option, two peers can communicate their support for Mobile IP during the IPCP phase of PPP. Familiarity with Mobile IP [RFC 2002], IPCP [RFC 1332], and PPP [RFC 1661] is assumed. [STANDARDS-TRACK] | February 1998 Status: PROPOSED STANDARD Autor: J. Solomon, S. Glass |
| RFC2291 Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web This document presents a list of features in the form of requirements for a Web Distributed Authoring and Versioning protocol which, if implemented, would improve the efficiency of common remote editing operations, provide a locking mechanism to prevent overwrite conflicts, improve link management support between non-HTML data types, provide a simple attribute-value metadata facility, provide for the creation and reading of container data types, and integrate versioning into the WWW. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | February 1998 Status: INFORMATIONAL Autor: J. Slein, F. Vitali, E. Whitehead, D. Durand |
| RFC2292 Advanced Sockets API for IPv6 The current document defines some the "advanced" features of the sockets API that are required for applications to take advantage of additional features of IPv6. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | February 1998 Status: INFORMATIONAL Autor: W. Stevens, M. Thomas |
| RFC2293 Representing Tables and Subtrees in the X.500 Directory This document defines techniques for representing two types of information mapping in the OSI Directory: Mapping from a key to a value (or set of values), as might be done in a table lookup, and mapping from a distinguished name to an associated value (or values), where the values are not defined by the owner of the entry. This is achieved by use of a directory subtree. [STANDARDS-TRCK] | March 1998 Status: PROPOSED STANDARD Autor: S. Kille |
| RFC2294 Representing the O/R Address hierarchy in the X.500 Directory Information Tree This document defines a representation of the O/R Address hierarchy in the Directory Information Tree. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: S. Kille |
| RFC2295 Transparent Content Negotiation in HTTP HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | March 1998 Status: EXPERIMENTAL Autor: K. Holtman, A. Mutz |
| RFC2296 HTTP Remote Variant Selection Algorithm -- RVSA/1.0 HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is a mechanism for automatically selecting the best version when the URL is accessed. A remote variant selection algorithm can be used to speed up the transparent negotiation process. This document defines the remote variant selection algorithm with the version number 1.0. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | March 1998 Status: EXPERIMENTAL Autor: K. Holtman, A. Mutz |
| RFC2297 Ipsilon's General Switch Management Protocol Specification Version 2.0 This memo specifies enhancements to the General Switch Management Protocol (GSMP) [RFC1987]. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: P. Newman, W. Edwards, R. Hinden, E. Hoffman, F. Ching Liaw, T. Lyon, G. Minshall |
| RFC2298 An Extensible Message Format for Message Disposition Notifications This memo defines a MIME content-type that may be used by a mail user agent (UA) or electronic mail gateway to report the disposition of a message after it has been sucessfully delivered to a recipient. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: R. Fajman |
| RFC2299 Request for Comments Summary | January 1999 Status: INFORMATIONAL Autor: A. Ramos |
| RFC2300 Internet Official Protocol Standards A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. [STANDARDS-TRACK] | May 1998 Status: HISTORIC Autor: J. Postel |
| RFC2301 File Format for Internet Fax This document describes the TIFF (Tag Image File Format) representation of image data specified by the ITU-T Recommendations for black-and-white and color facsimile. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: L. McIntyre, S. Zilles, R. Buckley, D. Venable, G. Parsons, J. Rafferty |
| RFC2302 Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration This document describes the registration of the MIME sub-type image/tiff. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: G. Parsons, J. Rafferty, S. Zilles |
| RFC2303 Minimal PSTN address format in Internet Mail This memo describes the MINIMAL addressing method to encode PSTN addresses into e-mail addresses and the standard extension mechanism to allow definition of further standard elements. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: C. Allocchio |
| RFC2304 Minimal FAX address format in Internet Mail This memo describes the MINIMAL addressing method and standard extensions to encode FAX addresses in e-mail addresses. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: C. Allocchio |
| RFC2305 A Simple Mode of Facsimile Using Internet Mail This specification provides for "simple mode" carriage of facsimile data over the Internet. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: K. Toyoda, H. Ohno, J. Murai, D. Wing |
| RFC2306 Tag Image File Format (TIFF) - F Profile for Facsimile This document describes in detail the definition of TIFF-F that is used to store facsimile images. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: G. Parsons, J. Rafferty |
| RFC2307 An Approach for Using LDAP as a Network Information Service This document describes an experimental mechanism for mapping entities related to TCP/IP and the UNIX system into X.500 entries so that they may be resolved with the Lightweight Directory Access Protocol [RFC2251]. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | March 1998 Status: EXPERIMENTAL Autor: L. Howard |
| RFC2308 Negative Caching of DNS Queries (DNS NCACHE) RFC1034 provided a description of how to cache negative responses. It however had a fundamental flaw in that it did not allow a name server to hand out those cached responses to other resolvers, thereby greatly reducing the effect of the caching. This document addresses issues raise in the light of experience and replaces RFC1034 Section 4.3.4. [STANDARDS-TRACK] | March 1998 Status: PROPOSED STANDARD Autor: M. Andrews |
| RFC2309 Recommendations on Queue Management and Congestion Avoidance in the Internet This memo presents two recommendations to the Internet community concerning measures to improve and preserve Internet performance. It presents a strong recommendation for testing, standardization, and widespread deployment of active queue management in routers, to improve the performance of today's Internet. It also urges a concerted effort of research, measurement, and ultimate deployment of router mechanisms to protect the Internet from flows that are not sufficiently responsive to congestion notification. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: B. Braden, D. Clark, J. Crowcroft, B. Davie, S. Deering, D. Estrin, S. Floyd, V. Jacobson, G. Minshall, C. Partridge, L. Peterson, K. Ramakrishnan, S. Shenker, J. Wroclawski, L. Zhang |
| RFC2310 The Safe Response Header Field This document defines a HTTP response header field called Safe, which can be used to indicate that repeating a HTTP request is safe. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | April 1998 Status: EXPERIMENTAL Autor: K. Holtman |
| RFC2311 S/MIME Version 2 Message Specification This document describes a protocol for adding cryptographic signature and encryption services to MIME data. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: HISTORIC Autor: S. Dusse, P. Hoffman, B. Ramsdell, L. Lundblade, L. Repka |
| RFC2312 S/MIME Version 2 Certificate Handling This memo describes the mechanisms S/MIME uses to create and validate keys using certificates. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: HISTORIC Autor: S. Dusse, P. Hoffman, B. Ramsdell, J. Weinstein |
| RFC2313 PKCS #1: RSA Encryption Version 1.5 This document describes a method for encrypting data using the RSA public-key cryptosystem. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: B. Kaliski |
| RFC2314 PKCS #10: Certification Request Syntax Version 1.5 This document describes a syntax for certification requests. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: B. Kaliski |
| RFC2315 PKCS #7: Cryptographic Message Syntax Version 1.5 This document describes a general syntax for data that may have cryptography applied to it, such as digital signatures and digital envelopes. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: B. Kaliski |
| RFC2316 Report of the IAB Security Architecture Workshop On 3-5 March 1997, the IAB held a security architecture workshop at Bell Labs in Murray Hill, NJ. We identified the core security components of the architecture, and specified several documents that need to be written. Most importantly, we agreed that security was not optional, and that it needed to be designed in from the beginning. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: S. Bellovin |
| RFC2317 Classless IN-ADDR.ARPA delegation This document describes a way to do IN-ADDR.ARPA delegation on non-octet boundaries for address spaces covering fewer than 256 addresses. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | March 1998 Status: BEST CURRENT PRACTICE Autor: H. Eidnes, G. de Groot, P. Vixie |
| RFC2318 The text/css Media Type This memo provides information about the text/css Media Type. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | March 1998 Status: INFORMATIONAL Autor: H. Lie, B. Bos, C. Lilley |
| RFC2319 Ukrainian Character Set KOI8-U This document provides information about character encoding KOI8-U (KOI8 Ukrainian) wich is a de-facto standard in Ukrainian Internet community. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: KOI8-U Working Group |
| RFC2320 Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB) The purpose of this memo is to define the Management Information Base (MIB) for supporting Classical IP and ARP over ATM as specified in Classical IP and ARP over ATM. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: M. Greene, J. Luciani, K. White, T. Kuo |
| RFC2321 RITA -- The Reliable Internetwork Troubleshooting Agent A Description of the usage of Nondeterministic Troubleshooting and Diagnostic Methodologies as applied to today's complex nondeterministic networks and environments. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: A. Bressen |
| RFC2322 Management of IP numbers by peg-dhcp This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don't necessarily have a clear organisational body. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: K. van den Hout, A. Koopal, R. van Mook |
| RFC2323 IETF Identification and Security Guidelines This RFC is meant to represent a guideline by which the IETF conferences may run more effeciently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis". This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: A. Ramos |
| RFC2324 Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: L. Masinter |
| RFC2325 Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2 This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for the management of coffee-brewing and maintenance devices. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: M. Slavitch |
| RFC2326 Real Time Streaming Protocol (RTSP) The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: H. Schulzrinne, A. Rao, R. Lanphier |
| RFC2327 SDP: Session Description Protocol This document defines the Session Description Protocol, SDP. SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: M. Handley, V. Jacobson |
| RFC2328 OSPF Version 2 This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK] | April 1998 Status: STANDARD Autor: J. Moy |
| RFC2329 OSPF Standardization Report This memo documents how the requirements for advancing a routing protocol to Full Standard have been met for OSPFv2. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | April 1998 Status: INFORMATIONAL Autor: J. Moy |
| RFC2330 Framework for IP Performance Metrics The purpose of this memo is to define a general framework for particular metrics to be developed by the IETF's IP Performance Metrics effort. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: INFORMATIONAL Autor: V. Paxson, G. Almes, J. Mahdavi, M. Mathis |
| RFC2331 ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update This memo describes how to efficiently use the ATM call control signalling procedures defined in UNI Signalling 4.0 to support IP over ATM environments as described in RFC 2225 and in RFC 2332. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: M. Maher |
| RFC2332 NBMA Next Hop Resolution Protocol (NHRP) This document describes the NBMA Next Hop Resolution Protocol (NHRP). NHRP can be used by a source station (host or router) connected to a Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the internetworking layer address and NBMA subnetwork addresses of the "NBMA next hop" towards a destination station. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: J. Luciani, D. Katz, D. Piscitello, B. Cole, N. Doraswamy |
| RFC2333 NHRP Protocol Applicability Statement As required by the Routing Protocol Criteria [RFC 1264], this memo discusses the applicability of the Next Hop Resolution Protocol (NHRP) in routing of IP datagrams over Non-Broadcast Multiple Access (NBMA) networks, such as ATM, SMDS and X.25. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: D. Cansever |
| RFC2334 Server Cache Synchronization Protocol (SCSP) This document describes the Server Cache Synchronization Protocol (SCSP) and is written in terms of SCSP's use within Non Broadcast Multiple Access (NBMA) networks; although, a somewhat straight forward usage is applicable to BMA networks. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: J. Luciani, G. Armitage, J. Halpern, N. Doraswamy |
| RFC2335 A Distributed NHRP Service Using SCSP This document describes a method for distributing an NHRP service within a LIS. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: J. Luciani |
| RFC2336 Classical IP to NHRP Transition This document describes methods and procedures for the graceful transition from an ATMARP LIS to an NHRP LIS network model over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | July 1998 Status: INFORMATIONAL Autor: J. Luciani |
| RFC2337 Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM This document describes how intra-LIS IP multicast can be efficiently supported among routers over ATM without using the Multicast Address Resolution Server (MARS). This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | April 1998 Status: EXPERIMENTAL Autor: D. Farinacci, D. Meyer, Y. Rekhter |
| RFC2338 Virtual Router Redundancy Protocol This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. [STANDARDS-TRACK] | April 1998 Status: PROPOSED STANDARD Autor: S. Knight, D. Weaver, D. Whipple, R. Hinden, D. Mitzel, P. Hunt, P. Higginson, M. Shand, A. Lindem |
| RFC2339 An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 Protocols This Request for Comments records an agreement between Sun Microsystems, Inc. and the Internet Society to permit the flow of Sun's Network File System specifications into the Internet Standards process conducted by the Internet Engineering Task Force. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: INFORMATIONAL Autor: The Internet Society, Sun Microsystems |
| RFC2340 Nortel's Virtual Network Switching (VNS) Overview This document provides an overview of Virtual Network Switching (VNS). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: INFORMATIONAL Autor: B. Jamoussi, D. Jamieson, D. Williston, S. Gabe |
| RFC2341 Cisco Layer Two Forwarding (Protocol) "L2F" This document describes the Layer Two Forwarding protocol (L2F) which permits the tunneling of the link layer (i.e., HDLC, async HDLC, or SLIP frames) of higher level protocols. This memo describes a historic protocol for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: HISTORIC Autor: A. Valencia, M. Littlewood, T. Kolar |
| RFC2342 IMAP4 Namespace This document defines a NAMESPACE command that allows a client to discover the prefixes of namespaces used by a server for personal mailboxes, other users' mailboxes, and shared mailboxes. [STANDARDS-TRACK] | May 1998 Status: PROPOSED STANDARD Autor: M. Gahrns, C. Newman |
| RFC2343 RTP Payload Format for Bundled MPEG This document describes a payload type for bundled, MPEG-2 encoded video and audio data that may be used with RTP, version 2. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | May 1998 Status: EXPERIMENTAL Autor: M. Civanlar, G. Cash, B. Haskell |
| RFC2344 Reverse Tunneling for Mobile IP This document proposes backwards-compatible extensions to Mobile IP in order to support topologically correct reverse tunnels. [STANDARDS-TRACK] | May 1998 Status: PROPOSED STANDARD Autor: G. Montenegro |
| RFC2345 Domain Names and Company Name Retrieval This document proposes a company name to URL mapping service based on the oldest and least complex of Internet directory protocols, whois, in order to explore whether an extremely simple and widely-deployed protocol can succeed where more complex and powerful options have failed or been excessively delayed. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | May 1998 Status: EXPERIMENTAL Autor: J. Klensin, T. Wolf, G. Oglesby |
| RFC2346 Making Postscript and PDF International Certain text formats, for example Postscript (MIME-Type: application/postscript; file extension .ps) and Portable Document Format (MIME-Type: application/pdf; file extension .pdf) specify exactly the page layout of the printed document. The commonly used paper format is different in North America and the rest of the world. North America uses the 'Letter' format, while the rest of the world mostly uses the ISO-standard 'A4' format. This means that documents formatted on one continent may not be easily printable on another continent. This memo gives advice on how to produce documents which are equally well printable with the Letter and the A4 formats. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: INFORMATIONAL Autor: J. Palme |
| RFC2347 TFTP Option Extension The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a simple extension to TFTP to allow option negotiation prior to the file transfer. [STANDARDS-TRACK] | May 1998 Status: DRAFT STANDARD Autor: G. Malkin, A. Harkin |
| RFC2348 TFTP Blocksize Option The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes a TFTP option which allows the client and server to negotiate a blocksize more applicable to the network medium. [STANDARDS-TRACK] | May 1998 Status: DRAFT STANDARD Autor: G. Malkin, A. Harkin |
| RFC2349 TFTP Timeout Interval and Transfer Size Options The Trivial File Transfer Protocol is a simple, lock-step, file transfer protocol which allows a client to get or put a file onto a remote host. This document describes two TFTP options. [STANDARDS-TRACK] | May 1998 Status: DRAFT STANDARD Autor: G. Malkin, A. Harkin |
| RFC2350 Expectations for Computer Security Incident Response | June 1998 Status: BEST CURRENT PRACTICE Autor: N. Brownlee, E. Guttman |
| RFC2351 Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP This memo specifies a protocol for the encapsulation of the airline specific protocol over IP. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: INFORMATIONAL Autor: A. Robert |
| RFC2352 A Convention For Using Legal Names as Domain Names The purpose of this memo is to focus discussion on the particular problems with the exhaustion of the top level domain space in the Internet and the possible conflicts that can occur when multiple organisations are vying for the same name. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: INFORMATIONAL Autor: O. Vaughan |
| RFC2353 APPN/HPR in IP Networks APPN Implementers' Workshop Closed Pages Document This memo defines a method with which HPR nodes can use IP networks for communication, and the enhancements to APPN required by this method. This memo also describes an option set that allows the use of the APPN connection network model to allow HPR nodes to use IP networks for communication without having to predefine link connections. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | May 1998 Status: INFORMATIONAL Autor: G. Dudley |
| RFC2354 Options for Repair of Streaming Media This document summarizes a range of possible techniques for the repair of continuous media streams subject to packet loss. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1998 Status: INFORMATIONAL Autor: C. Perkins, O. Hodson |
| RFC2355 TN3270 Enhancements This document describes a protocol that more fully supports 3270 devices than do traditional tn3270 practices. [STANDARDS-TRACK] | June 1998 Status: DRAFT STANDARD Autor: B. Kelly |
| RFC2356 Sun's SKIP Firewall Traversal for Mobile IP The Mobile IP specification establishes the mechanisms that enable a mobile host to maintain and use the same IP address as it changes its point of attachment to the network. The mechanisms described in this document allow a mobile node out on a public sector of the internet to negotiate access past a SKIP firewall, and construct a secure channel into its home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. | June 1998 Status: INFORMATIONAL Autor: G. Montenegro, V. Gupta |
| RFC2357 IETF Criteria for Evaluating Reliable Multicast Transport and Application Protocols This memo describes the procedures and criteria for reviewing reliable multicast protocols within the Transport Area (TSV) of the IETF. Within today's Internet, important applications exist for a reliable multicast service. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | June 1998 Status: INFORMATIONAL Autor: A. Mankin, A. Romanow, S. Bradner, V. Paxson |
| RFC2358 Definitions of Managed Objects for the Ethernet-like Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 1650 "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2". This memo extends that specification by including management information useful for the management of 100 Mb/s Ethernet interfaces. [STANDARDS-TRACK] | June 1998 Status: PROPOSED STANDARD Autor: J. Flick, J. Johnson |
| RFC2359 IMAP4 UIDPLUS extension The UIDPLUS extension of the Internet Message Access Protocol [IMAP4] provides a set of features intended to reduce the amount of time and resources used by some client operations. [STANDARDS-TRACK] | June 1998 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC2360 Guide for Internet Standards Writers This document is a guide for Internet standard writers. It defines those characteristics that make standards coherent, unambiguous, and easy to interpret. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 1998 Status: BEST CURRENT PRACTICE Autor: G. Scott |
| RFC2361 WAVE and AVI Codec Registries The purpose of this paper is to establish a mechanism by which codecs registered within Microsoft's WAVE and AVI Registries may be referenced within the IANA Namespace by Internet applications. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | June 1998 Status: INFORMATIONAL Autor: E. Fleischman |
| RFC2362 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification This document describes a protocol for efficiently routing to multicast groups that may span wide-area (and inter-domain) internets. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. | June 1998 Status: EXPERIMENTAL Autor: D. Estrin, D. Farinacci, A. Helmy, D. Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Wei |
| RFC2363 PPP Over FUNI This document describes the use of ATM Frame User Network Interface (FUNI) for framing PPP encapsulated packets. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: G. Gross, M. Kaycee, A. Li, A. Malis, J. Stephens |
| RFC2364 PPP Over AAL5 This document describes the use of ATM Adaptation Layer 5 (AAL5) for framing PPP encapsulated packets. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: G. Gross, M. Kaycee, A. Li, A. Malis, J. Stephens |
| RFC2365 Administratively Scoped IP Multicast This document defines the "administratively scoped IPv4 multicast space" to be the range 239.0.0.0 to 239.255.255.255. In addition, it describes a simple set of semantics for the implementation of Administratively Scoped IP Multicast. Finally, it provides a mapping between the IPv6 multicast address classes [RFC1884] and IPv4 multicast address classes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | July 1998 Status: BEST CURRENT PRACTICE Autor: D. Meyer |
| RFC2366 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for IP hosts and routers that use a Multicast Address Resolution Server (MARS) to support IP multicast over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based ATM Networks'. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: C. Chung, M. Greene |
| RFC2367 PF_KEY Key Management API, Version 2 A generic key management API that can be used not only for IP Security but also for other network security services is presented in this document. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | July 1998 Status: INFORMATIONAL Autor: D. McDonald, C. Metz, B. Phan |
| RFC2368 The mailto URL scheme This document defines the format of Uniform Resource Locators (URL) for designating electronic mail addresses. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: P. Hoffman, L. Masinter, J. Zawinski |
| RFC2369 The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields The mailing list command specification header fields are a set of structured fields to be added to email messages sent by email distribution lists. By including these header fields, list servers can make it possible for mail clients to provide automated tools for users to perform list functions. This could take the form of a menu item, push button, or other user interface element. The intent is to simplify the user experience, providing a common interface to the often cryptic and varied mailing list manager commands. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: G. Neufeld, J. Baer |
| RFC2370 The OSPF Opaque LSA Option This memo defines enhancements to the OSPF protocol to support a new class of link-state advertisements (LSA) called Opaque LSAs. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: R. Coltun |
| RFC2371 Transaction Internet Protocol Version 3.0 In many applications where different nodes cooperate on some work, there is a need to guarantee that the work happens atomically. That is, each node must reach the same conclusion as to whether the work is to be completed, even in the face of failures. This document proposes a simple, easily-implemented protocol for achieving this end. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: J. Lyon, K. Evans, J. Klein |
| RFC2372 Transaction Internet Protocol - Requirements and Supplemental Information This document describes the purpose (usage scenarios), and requirements for the Transaction Internet Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | July 1998 Status: INFORMATIONAL Autor: K. Evans, J. Klein, J. Lyon |
| RFC2373 IP Version 6 Addressing Architecture This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK] | July 1998 Status: PROPOSED STANDARD Autor: R. Hinden, S. Deering |
| RFC2374 An IPv6 Aggregatable Global Unicast Address Format This document defines an IPv6 aggregatable global unicast address format for use in the Internet. [STANDARDS-TRACK] | July 1998 Status: HISTORIC Autor: R. Hinden, M. O'Dell, S. Deering |
| RFC2375 IPv6 Multicast Address Assignments This document defines the initial assignment of IPv6 multicast addresses. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | July 1998 Status: INFORMATIONAL Autor: R. Hinden, S. Deering |
| RFC2376 XML Media Types This document proposes two new media subtypes, text/xml and application/xml, for use in exchanging network entities which are conforming Extensible Markup Language (XML). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | July 1998 Status: INFORMATIONAL Autor: E. Whitehead, M. Murata |
| RFC2377 Naming Plan for Internet Directory-Enabled Applications Application of the conventional X.500 approach to naming has heretofore, in the experience of the authors, proven to be an obstacle to the wide deployment of directory-enabled applications on the Internet. We propose a new directory naming plan that leverages the strengths of the most popular and successful Internet naming schemes for naming objects in a hierarchical directory. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1998 Status: INFORMATIONAL Autor: A. Grimstad, R. Huber, S. Sataluri, M. Wahl |
| RFC2378 The CCSO Nameserver (Ph) Architecture The Ph Nameserver from the Computing and Communications Services Office (CCSO), University of Illinois at Urbana-Champaign has for some time now been used by several organizations as their choice of publicly available database for information about people as well as other things. This document provides a formal definition of the client-server protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | September 1998 Status: INFORMATIONAL Autor: R. Hedberg, P. Pomes |
| RFC2379 RSVP over ATM Implementation Guidelines This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 1998 Status: BEST CURRENT PRACTICE Autor: L. Berger |
| RFC2380 RSVP over ATM Implementation Requirements This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: L. Berger |
| RFC2381 Interoperation of Controlled-Load Service and Guaranteed Service with ATM This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: M. Garrett, M. Borden |
| RFC2382 A Framework for Integrated Services and RSVP over ATM This document outlines the issues and framework related to providing IP Integrated Services with RSVP over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | August 1998 Status: INFORMATIONAL Autor: E. Crawley, L. Berger, S. Berson, F. Baker, M. Borden, J. Krawczyk |
| RFC2383 ST2+ over ATM Protocol Specification - UNI 3.1 Version This document specifies an ATM-based protocol for communication between ST2+ agents. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | August 1998 Status: INFORMATIONAL Autor: M. Suzuki |
| RFC2384 POP URL Scheme This memo defines a URL scheme for referencing a POP mailbox. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: R. Gellens |
| RFC2385 Protection of BGP Sessions via the TCP MD5 Signature Option This memo describes a TCP extension to enhance security for BGP. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: A. Heffernan |
| RFC2386 A Framework for QoS-based Routing in the Internet This document describes some of the QoS-based routing issues and requirements, and proposes a framework for QoS-based routing in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | August 1998 Status: INFORMATIONAL Autor: E. Crawley, R. Nair, B. Rajagopalan, H. Sandick |
| RFC2387 The MIME Multipart/Related Content-type This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: E. Levinson |
| RFC2388 Returning Values from Forms: multipart/form-data This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: L. Masinter |
| RFC2389 Feature negotiation mechanism for the File Transfer Protocol This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: P. Hethmon, R. Elz |
| RFC2390 Inverse Address Resolution Protocol This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK] | September 1998 Status: DRAFT STANDARD Autor: T. Bradley, C. Brown, A. Malis |
| RFC2391 Load Sharing using IP Network Address Translation (LSNAT) In this document, we extend the use of NATs to offer Load share feature, where session load can be distributed across a pool of servers, instead of directing to a single server. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | August 1998 Status: INFORMATIONAL Autor: P. Srisuresh, D. Gan |
| RFC2392 Content-ID and Message-ID Uniform Resource Locators The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: E. Levinson |
| RFC2393 IP Payload Compression Protocol (IPComp) This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK] | December 1998 Status: PROPOSED STANDARD Autor: A. Shacham, R. Monsour, R. Pereira, M. Thomas |
| RFC2394 IP Payload Compression Using DEFLATE This document describes a compression method based on the DEFLATE compression algorithm. This document defines the application of the DEFLATE algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | December 1998 Status: INFORMATIONAL Autor: R. Pereira |
| RFC2395 IP Payload Compression Using LZS This document describes a compression method based on the LZS compression algorithm. This document defines the application of the LZS algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | December 1998 Status: INFORMATIONAL Autor: R. Friend, R. Monsour |
| RFC2396 Uniform Resource Identifiers (URI): Generic Syntax This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. [STANDARDS-TRACK] | August 1998 Status: DRAFT STANDARD Autor: T. Berners-Lee, R. Fielding, L. Masinter |
| RFC2397 The "data" URL scheme A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK] | August 1998 Status: PROPOSED STANDARD Autor: L. Masinter |
| RFC2398 Some Testing Tools for TCP Implementors This document lists only tools which can evaluate one or more TCP implementations, or which can privde some specific results which describe or evaluate the TCP being tested. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. | August 1998 Status: INFORMATIONAL Autor: S. Parker, C. Schmechel |
| RFC2399 Request for Comments Summary | January 1999 Status: INFORMATIONAL Autor: A. Ramos |
| RFC2400 Internet Official Protocol Standards This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). This memo is an Internet Standard. [STANDARDS-TRACK] | September 1998 Status: HISTORIC Autor: J. Postel, J. Reynolds |
| RFC2401 Security Architecture for the Internet Protocol This memo specifies the base architecture for IPsec compliant systems. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: S. Kent, R. Atkinson |
| RFC2402 IP Authentication Header The IP Authentication Header (AH) is used to provide connectionless integrity and data origin authentication for IP datagrams (hereafter referred to as just "authentication"), and to provide protection against replays. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: S. Kent, R. Atkinson |
| RFC2403 The Use of HMAC-MD5-96 within ESP and AH This memo describes the use of the HMAC algorithm in conjunction with the MD5 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: C. Madson, R. Glenn |
| RFC2404 The Use of HMAC-SHA-1-96 within ESP and AH This memo describes the use of the HMAC algorithm in conjunction with the SHA-1 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: C. Madson, R. Glenn |
| RFC2405 The ESP DES-CBC Cipher Algorithm With Explicit IV This document describes the use of the DES Cipher algorithm in Cipher Block Chaining Mode, with an explicit IV, as a confidentiality mechanism within the context of the IPSec Encapsulating Security Payload (ESP). [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: C. Madson, N. Doraswamy |
| RFC2406 IP Encapsulating Security Payload (ESP) The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: S. Kent, R. Atkinson |
| RFC2407 The Internet IP Security Domain of Interpretation for ISAKMP This document defines the Internet IP Security DOI (IPSEC DOI), which instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate security associations. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: D. Piper |
| RFC2408 Internet Security Association and Key Management Protocol (ISAKMP) This memo describes a protocol utilizing security concepts necessary for establishing Security Associations (SA) and cryptographic keys in an Internet environment. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: D. Maughan, M. Schertler, M. Schneider, J. Turner |
| RFC2409 The Internet Key Exchange (IKE) This memo describes a hybrid protocol. The purpose is to negotiate, and provide authenticated keying material for, security associations in a protected manner. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: D. Harkins, D. Carrel |
| RFC2410 The NULL Encryption Algorithm and Its Use With IPsec This memo defines the NULL encryption algorithm and its use with the IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: R. Glenn, S. Kent |
| RFC2411 IP Security Document Roadmap This document is intended to provide guidelines for the development of collateral specifications describing the use of new encryption and authentication algorithms with the ESP protocol, described in and new authentication algorithms used with the AH protocol. This memo provides information for the Internet community. | November 1998 Status: INFORMATIONAL Autor: R. Thayer, N. Doraswamy, R. Glenn |
| RFC2412 The OAKLEY Key Determination Protocol This document describes a protocol, named OAKLEY, by which two authenticated parties can agree on secure and secret keying material. The basic mechanism is the Diffie-Hellman key exchange algorithm. This memo provides information for the Internet community. | November 1998 Status: INFORMATIONAL Autor: H. Orman |
| RFC2413 Dublin Core Metadata for Resource Discovery This is the first of a set of Informational RFCs describing the Dublin Core. Its purpose is to introduce the Dublin Core and to describe the consensus reached on the semantics of each of the 15 elements. This memo provides information for the Internet community. | September 1998 Status: INFORMATIONAL Autor: S. Weibel, J. Kunze, C. Lagoze, M. Wolf |
| RFC2414 Increasing TCP's Initial Window This document specifies an increase in the permitted initial window for TCP from one segment to roughly 4K bytes. This memo defines an Experimental Protocol for the Internet community. | September 1998 Status: EXPERIMENTAL Autor: M. Allman, S. Floyd, C. Partridge |
| RFC2415 Simulation Studies of Increased Initial TCP Window Size This document covers some simulation studies of the effects of increasing the initial window size of TCP. This memo provides information for the Internet community. | September 1998 Status: INFORMATIONAL Autor: K. Poduri, K. Nichols |
| RFC2416 When TCP Starts Up With Four Packets Into Only Three Buffers This memo is to document a simple experiment. The experiment showed that in the case of a TCP receiver behind a 9600 bps modem link at the edge of a fast Internet where there are only 3 buffers before the modem (and the fourth packet of a four-packet start will surely be dropped), no significant degradation in performance is experienced by a TCP sending with a four-packet start when compared with a normal slow start (which starts with just one packet). This memo provides information for the Internet community. | September 1998 Status: INFORMATIONAL Autor: T. Shepard, C. Partridge |
| RFC2417 Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: C. Chung, M. Greene |
| RFC2418 IETF Working Group Guidelines and Procedures This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 1998 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC2419 The PPP DES Encryption Protocol, Version 2 (DESE-bis) This document provides specific details for the use of the DES standard for encrypting PPP encapsulated packets. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: K. Sklower, G. Meyer |
| RFC2420 The PPP Triple-DES Encryption Protocol (3DESE) This document provides specific details for the use of the Triple-DES standard (3DES) for encrypting PPP encapsulated packets. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: H. Kummert |
| RFC2421 Voice Profile for Internet Mail - version 2 This document profiles Internet mail for voice messaging. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: G. Vaudreuil, G. Parsons |
| RFC2422 Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration This document describes the registration of the MIME sub-type audio/32KADPCM for toll quality audio. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: G. Vaudreuil, G. Parsons |
| RFC2423 VPIM Voice Message MIME Sub-type Registration This document describes the registration of the MIME sub-type multipart/voice-message for use with the Voice Profile for Internet Mail (VPIM). [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: G. Vaudreuil, G. Parsons |
| RFC2424 Content Duration MIME Header Definition This document describes the MIME header Content-Duration that is intended for use with any timed media content (typically audio/* or video/*). [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: G. Vaudreuil, G. Parsons |
| RFC2425 A MIME Content-Type for Directory Information This document defines a MIME Content-Type for holding directory information. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: T. Howes, M. Smith, F. Dawson |
| RFC2426 vCard MIME Directory Profile This memo defines the profile of the MIME Content-Type for directory information for a white-pages person object, based on a vCard electronic business card. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: F. Dawson, T. Howes |
| RFC2427 Multiprotocol Interconnect over Frame Relay This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK] | September 1998 Status: STANDARD Autor: C. Brown, A. Malis |
| RFC2428 FTP Extensions for IPv6 and NATs This paper specifies extensions to FTP that will allow the protocol to work over IPv4 and IPv6. [STANDARDS-TRACK] | September 1998 Status: PROPOSED STANDARD Autor: M. Allman, S. Ostermann, C. Metz |
| RFC2429 RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+) This document specifies an RTP payload header format applicable to the transmission of video streams generated based on the 1998 version of ITU-T Recommendation H.263. [STANDARDS-TRACK] | October 1998 Status: PROPOSED STANDARD Autor: C. Bormann, L. Cline, G. Deisher, T. Gardos, C. Maciocco, D. Newell, J. Ott, G. Sullivan, S. Wenger, C. Zhu |
| RFC2430 A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) This document describes the Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) for Internet Service Providers (ISPs). This memo provides information for the Internet community. | October 1998 Status: INFORMATIONAL Autor: T. Li, Y. Rekhter |
| RFC2431 RTP Payload Format for BT.656 Video Encoding This document specifies the RTP payload format for encapsulating ITU Recommendation BT.656-3 video streams in the Real-Time Transport Protocol (RTP). [STANDARDS-TRACK] | October 1998 Status: PROPOSED STANDARD Autor: D. Tynan |
| RFC2432 Terminology for IP Multicast Benchmarking The purpose of this document is to define terminology specific to the benchmarking of multicast IP forwarding devices. This memo provides information for the Internet community. | October 1998 Status: INFORMATIONAL Autor: K. Dubray |
| RFC2433 Microsoft PPP CHAP Extensions The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This memo provides information for the Internet community. | October 1998 Status: INFORMATIONAL Autor: G. Zorn, S. Cobb |
| RFC2434 Guidelines for Writing an IANA Considerations Section in RFCs This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1998 Status: BEST CURRENT PRACTICE Autor: T. Narten, H. Alvestrand |
| RFC2435 RTP Payload Format for JPEG-compressed Video This memo describes the RTP payload format for JPEG video streams. [STANDARDS-TRACK] | October 1998 Status: PROPOSED STANDARD Autor: L. Berc, W. Fenner, R. Frederick, S. McCanne, P. Stewart |
| RFC2436 Collaboration between ISOC/IETF and ITU-T This document describes the collaboration process between the ITU-T and ISOC/IETF. This memo provides information for the Internet community. | October 1998 Status: INFORMATIONAL Autor: R. Brett, S. Bradner, G. Parsons |
| RFC2437 PKCS #1: RSA Cryptography Specifications Version 2.0 This memo is the successor to RFC 2313. This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm. This memo provides information for the Internet community. | October 1998 Status: INFORMATIONAL Autor: B. Kaliski, J. Staddon |
| RFC2438 Advancement of MIB specifications on the IETF Standards Track This document specifies the process which the IESG will use to determine if a MIB specification document meets these requirements. It also discusses the rationale for this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 1998 Status: BEST CURRENT PRACTICE Autor: M. O'Dell, H. Alvestrand, B. Wijnen, S. Bradner |
| RFC2439 BGP Route Flap Damping A usage of the BGP routing protocol is described which is capable of reducing the routing traffic passed on to routing peers and therefore the load on these peers without adversely affecting route convergence time for relatively stable routes. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: C. Villamizar, R. Chandra, R. Govindan |
| RFC2440 OpenPGP Message Format This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: J. Callas, L. Donnerhacke, H. Finney, R. Thayer |
| RFC2441 Working with Jon, Tribute delivered at UCLA, October 30, 1998 This memo provides information for the Internet community. | November 1998 Status: INFORMATIONAL Autor: D. Cohen |
| RFC2442 The Batch SMTP Media Type This document defines a MIME content type suitable for tunneling an ESMTP transaction through any MIME-capable transport. This memo provides information for the Internet community | November 1998 Status: INFORMATIONAL Autor: N. Freed, D. Newman, J. Belissent, M. Hoy |
| RFC2443 A Distributed MARS Service Using SCSP This document describes a method for distributing a MARS service within a LIS. This method uses the Server Cache Synchronization Protocol (SCSP) to synchronize the MARS Server databases within a LIS. When SCSP is used to synchronize the caches of MARS Servers in a LIS, the LIS defines the boundary of an SCSP Server Group (SG). [STANDARDS-TRACK] | November 1998 Status: EXPERIMENTAL Autor: J. Luciani, A. Gallo |
| RFC2444 The One-Time-Password SASL Mechanism 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] | October 1998 Status: PROPOSED STANDARD Autor: C. Newman |
| RFC2445 Internet Calendaring and Scheduling Core Object Specification (iCalendar) 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] | November 1998 Status: PROPOSED STANDARD Autor: F. Dawson, D. Stenerson |
| RFC2446 iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries 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] | November 1998 Status: PROPOSED STANDARD Autor: S. Silverberg, S. Mansour, F. Dawson, R. Hopson |
| RFC2447 iCalendar Message-Based Interoperability Protocol (iMIP) This document specifies a binding from the iCalendar Transport- independent Interoperability Protocol (iTIP) to Internet email-based transports. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: F. Dawson, S. Mansour, S. Silverberg |
| RFC2448 AT&T's Error Resilient Video Transmission Technique 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. | November 1998 Status: INFORMATIONAL Autor: M. Civanlar, G. Cash, B. Haskell |
| RFC2449 POP3 Extension Mechanism This memo updates RFC 1939 to define a mechanism to announce support for optional commands, extensions, and unconditional server behavior. [STANDARDS-TRACK] | November 1998 Status: PROPOSED STANDARD Autor: R. Gellens, C. Newman, L. Lundblade |
| RFC2450 Proposed TLA and NLA Assignment Rule 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. | December 1998 Status: INFORMATIONAL Autor: R. Hinden |
| RFC2451 The ESP CBC-Mode Cipher Algorithms 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] | November 1998 Status: PROPOSED STANDARD Autor: R. Pereira, R. Adams |
| RFC2452 IP Version 6 Management Information Base for the Transmission Control Protocol 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] | December 1998 Status: PROPOSED STANDARD Autor: M. Daniele |
| RFC2453 RIP Version 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] | November 1998 Status: STANDARD Autor: G. Malkin |
| RFC2454 IP Version 6 Management Information Base for the User Datagram Protocol 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] | December 1998 Status: HISTORIC Autor: M. Daniele |
| RFC2455 Definitions of Managed Objects for APPN 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] | November 1998 Status: PROPOSED STANDARD Autor: B. Clouston, B. Moore |
| RFC2456 Definitions of Managed Objects for APPN TRAPS 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] | November 1998 Status: PROPOSED STANDARD Autor: B. Clouston, B. Moore |
| RFC2457 Definitions of Managed Objects for Extended Border Node 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] | November 1998 Status: PROPOSED STANDARD Autor: B. Clouston, B. Moore |
| RFC2458 Toward the PSTN/Internet Inter-Networking--Pre-PINT Implementations 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. | November 1998 Status: INFORMATIONAL Autor: H. Lu, M. Krishnaswamy, L. Conroy, S. Bellovin, F. Burg, A. DeSimone, K. Tewani, P. Davidson, H. Schulzrinne, K. Vishwanathan |
| RFC2459 Internet X.509 Public Key Infrastructure Certificate and CRL Profile This memo profiles the X.509 v3 certificate and X.509 v2 CRL for use in the Internet. [STANDARDS-TRACK] | January 1999 Status: PROPOSED STANDARD Autor: R. Housley, W. Ford, W. Polk, D. Solo |
| RFC2460 Internet Protocol, Version 6 (IPv6) Specification This document specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK] | December 1998 Status: DRAFT STANDARD Autor: S. Deering, R. Hinden |
| RFC2461 Neighbor Discovery for IP Version 6 (IPv6) This document specifies the Neighbor Discovery protocol for IP Version 6. [STANDARDS-TRACK] | December 1998 Status: DRAFT STANDARD Autor: T. Narten, E. Nordmark, W. Simpson |
| RFC2462 IPv6 Stateless Address Autoconfiguration This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. [STANDARDS-TRACK] | December 1998 Status: DRAFT STANDARD Autor: S. Thomson, T. Narten |
| RFC2463 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification This document specifies a set of Internet Control Message Protocol (ICMP) messages for use with version 6 of the Internet Protocol (IPv6). [STANDARDS-TRACK] | December 1998 Status: DRAFT STANDARD Autor: A. Conta, S. Deering |
| RFC2464 Transmission of IPv6 Packets over Ethernet Networks 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] | December 1998 Status: PROPOSED STANDARD Autor: M. Crawford |
| RFC2465 Management Information Base for IP Version 6: Textual Conventions and General Group 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] | December 1998 Status: PROPOSED STANDARD Autor: D. Haskin, S. Onishi |
| RFC2466 Management Information Base for IP Version 6: ICMPv6 Group 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] | December 1998 Status: PROPOSED STANDARD Autor: D. Haskin, S. Onishi |
| RFC2467 Transmission of IPv6 Packets over FDDI Networks 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] | December 1998 Status: PROPOSED STANDARD Autor: M. Crawford |
| RFC2468 I REMEMBER IANA A long time ago, in a network, far far away, a great adventure took place!. This memo provides information for the Internet community. | October 1998 Status: INFORMATIONAL Autor: V. Cerf |
| RFC2469 A Caution On The Canonical Ordering Of Link-Layer Addresses 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. | December 1998 Status: INFORMATIONAL Autor: T. Narten, C. Burton |
| RFC2470 Transmission of IPv6 Packets over Token Ring Networks This memo specifies the MTU and frame format for transmission of IPv6 packets on Token Ring networks. [STANDARDS-TRACK] | December 1998 Status: PROPOSED STANDARD Autor: M. Crawford, T. Narten, S. Thomas |
| RFC2471 IPv6 Testing Address Allocation 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. | December 1998 Status: HISTORIC Autor: R. Hinden, R. Fink, J. Postel |
| RFC2472 IP Version 6 over PPP 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] | December 1998 Status: PROPOSED STANDARD Autor: D. Haskin, E. Allen |
| RFC2473 Generic Packet Tunneling in IPv6 Specification This document defines the model and generic mechanisms for IPv6 encapsulation of Internet packets, such as IPv6 and IPv4. [STANDARDS-TRACK] | December 1998 Status: PROPOSED STANDARD Autor: A. Conta, S. Deering |
| RFC2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers This document defines the IP header field, called the DS (for differentiated services) field. [STANDARDS-TRACK] | December 1998 Status: PROPOSED STANDARD Autor: K. Nichols, S. Blake, F. Baker, D. Black |
| RFC2475 An Architecture for Differentiated Service This document defines an architecture for implementing scalable service differentiation in the Internet. This memo provides information for the Internet community. | December 1998 Status: INFORMATIONAL Autor: S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss |
| RFC2476 Message Submission 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] | December 1998 Status: PROPOSED STANDARD Autor: R. Gellens, J. Klensin |
| RFC2477 Criteria for Evaluating Roaming Protocols 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. | January 1999 Status: INFORMATIONAL Autor: B. Aboba, G. Zorn |
| RFC2478 The Simple and Protected GSS-API Negotiation Mechanism This document specifies a Security Negotiation Mechanism for the Generic Security Service Application Program Interface (GSS-API). [STANDARDS-TRACK] | December 1998 Status: PROPOSED STANDARD Autor: E. Baize, D. Pinkas |
| RFC2479 Independent Data Unit Protection Generic Security Service Application Program Interface (IDUP-GSS-API) 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. | December 1998 Status: INFORMATIONAL Autor: C. Adams |
| RFC2480 Gateways and MIME Security Multiparts This document examines the problems associated with use of MIME security multiparts and gateways to non-MIME environments. [STANDARDS-TRACK] | January 1999 Status: PROPOSED STANDARD Autor: N. Freed |
| RFC2481 A Proposal to add Explicit Congestion Notification (ECN) to IP This note describes a proposed addition of ECN (Explicit Congestion Notification) to IP. This memo defines an Experimental Protocol for the Internet community. | January 1999 Status: EXPERIMENTAL Autor: K. Ramakrishnan, S. Floyd |
| RFC2482 Language Tagging in Unicode Plain Text This document proposed a mechanism for language tagging in plain text. This memo provides information for the Internet community. | January 1999 Status: HISTORIC Autor: K. Whistler, G. Adams |
| RFC2483 URI Resolution Services Necessary for URN Resolution 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. | January 1999 Status: EXPERIMENTAL Autor: M. Mealling, R. Daniel |
| RFC2484 PPP LCP Internationalization Configuration Option 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] | January 1999 Status: PROPOSED STANDARD Autor: G. Zorn |
| RFC2485 DHCP Option for The Open Group's User Authentication Protocol 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] | January 1999 Status: PROPOSED STANDARD Autor: S. Drach |
| RFC2486 The Network Access Identifier This document proposes syntax for the Network Access Identifier (NAI), the userID submitted by the client during PPP authentication. [STANDARDS-TRACK] | January 1999 Status: PROPOSED STANDARD Autor: B. Aboba, M. Beadles |
| RFC2487 SMTP Service Extension for Secure SMTP over TLS 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] | January 1999 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC2488 Enhancing TCP Over Satellite Channels using Standard Mechanisms 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. | January 1999 Status: BEST CURRENT PRACTICE Autor: M. Allman, D. Glover, L. Sanchez |
| RFC2489 Procedure for Defining New DHCP Options 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. | January 1999 Status: BEST CURRENT PRACTICE Autor: R. Droms |
| RFC2490 A Simulation Model for IP Multicast with RSVP 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. | January 1999 Status: INFORMATIONAL Autor: M. Pullen, R. Malghan, L. Lavu, G. Duan, J. Ma, H. Nah |
| RFC2491 IPv6 over Non-Broadcast Multiple Access (NBMA) networks This document describes a general architecture for IPv6 over NBMA networks. [STANDARDS-TRACK] | January 1999 Status: PROPOSED STANDARD Autor: G. Armitage, P. Schulter, M. Jork, G. Harter |
| RFC2492 IPv6 over ATM Networks 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] | January 1999 Status: PROPOSED STANDARD Autor: G. Armitage, P. Schulter, M. Jork |
| RFC2493 Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals 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] | January 1999 Status: PROPOSED STANDARD Autor: K. Tesink |
| RFC2494 Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type 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] | January 1999 Status: PROPOSED STANDARD Autor: D. Fowler |
| RFC2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it 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] | January 1999 Status: PROPOSED STANDARD Autor: D. Fowler |
| RFC2496 Definitions of Managed Object for the DS3/E3 Interface Type 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] | January 1999 Status: PROPOSED STANDARD Autor: D. Fowler |
| RFC2497 Transmission of IPv6 Packets over ARCnet Networks 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] | January 1999 Status: PROPOSED STANDARD Autor: I. Souvatzis |
| RFC2498 IPPM Metrics for Measuring Connectivity 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. | January 1999 Status: EXPERIMENTAL Autor: J. Mahdavi, V. Paxson |
| RFC2499 Request for Comments Summary | July 1999 Status: INFORMATIONAL Autor: A. Ramos |
| RFC2500 Internet Official Protocol Standards This memo summarizes the status of Internet protocols and specifications. [STANDARDS-TRACK] | June 1999 Status: HISTORIC Autor: J. Reynolds, R. Braden |
| RFC2501 Mobile Ad hoc Networking (MANET): Routing Protocol Performance Issues and Evaluation Considerations 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. | January 1999 Status: INFORMATIONAL Autor: S. Corson, J. Macker |
| RFC2502 Limitations of Internet Protocol Suite for Distributed Simulation the Large Multicast Environment 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. | February 1999 Status: INFORMATIONAL Autor: M. Pullen, M. Myjak, C. Bouwens |
| RFC2503 MIME Types for Use with the ISO ILL Protocol 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. | February 1999 Status: INFORMATIONAL Autor: R. Moulton, M. Needleman |
| RFC2504 Users' Security Handbook 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. | February 1999 Status: INFORMATIONAL Autor: E. Guttman, L. Leong, G. Malkin |
| RFC2505 Anti-Spam Recommendations for SMTP MTAs 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. | February 1999 Status: BEST CURRENT PRACTICE Autor: G. Lindberg |
| RFC2506 Media Feature Tag Registration Procedure 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. | March 1999 Status: BEST CURRENT PRACTICE Autor: K. Holtman, A. Mutz, T. Hardie |
| RFC2507 IP Header Compression This document describes how to compress multiple IP headers and TCP and UDP headers per hop over point to point links. [STANDARDS-TRACK] | February 1999 Status: PROPOSED STANDARD Autor: M. Degermark, B. Nordgren, S. Pink |
| RFC2508 Compressing IP/UDP/RTP Headers for Low-Speed Serial Links This document describes a method for compressing the headers of IP/UDP/RTP datagrams to reduce overhead on low-speed serial links. [STANDARDS-TRACK] | February 1999 Status: PROPOSED STANDARD Autor: S. Casner, V. Jacobson |
| RFC2509 IP Header Compression over PPP 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] | February 1999 Status: PROPOSED STANDARD Autor: M. Engan, S. Casner, C. Bormann |
| RFC2510 Internet X.509 Public Key Infrastructure Certificate Management Protocols This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocols. [STANDARDS-TRACK] | March 1999 Status: PROPOSED STANDARD Autor: C. Adams, S. Farrell |
| RFC2511 Internet X.509 Certificate Request Message Format This document describes the Certificate Request Message Format (CRMF). [STANDARDS-TRACK] | March 1999 Status: PROPOSED STANDARD Autor: M. Myers, C. Adams, D. Solo, D. Kemp |
| RFC2512 Accounting Information for ATM Networks 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] | February 1999 Status: PROPOSED STANDARD Autor: K. McCloghrie, J. Heinanen, W. Greene, A. Prasad |
| RFC2513 Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for controlling the collection and storage of accounting information for connection-oriented networks such as ATM. [STANDARDS-TRACK] | February 1999 Status: PROPOSED STANDARD Autor: K. McCloghrie, J. Heinanen, W. Greene, A. Prasad |
| RFC2514 Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management This memo describes Textual Conventions and OBJECT-IDENTITIES used for managing ATM-based interfaces, devices, networks and services. [STANDARDS-TRACK] | February 1999 Status: PROPOSED STANDARD Autor: M. Noto, E. Spiegel, K. Tesink |
| RFC2515 Definitions of Managed Objects for ATM Management 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] | February 1999 Status: PROPOSED STANDARD Autor: K. Tesink, Ed |
| RFC2516 A Method for Transmitting PPP Over Ethernet (PPPoE) This document describes how to build PPP sessions and encapsulate PPP packets over Ethernet. This memo provides information for the Internet community. | February 1999 Status: INFORMATIONAL Autor: L. Mamakos, K. Lidl, J. Evarts, D. Carrel, D. Simone, R. Wheeler |
| RFC2517 Building Directories from DNS: Experiences from WWWSeeker 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. | February 1999 Status: INFORMATIONAL Autor: R. Moats, R. Huber |
| RFC2518 HTTP Extensions for Distributed Authoring -- WEBDAV 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] | February 1999 Status: PROPOSED STANDARD Autor: Y. Goland, E. Whitehead, A. Faizi, S. Carter, D. Jensen |
| RFC2519 A Framework for Inter-Domain Route Aggregation 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 | February 1999 Status: INFORMATIONAL Autor: E. Chen, J. Stewart |
| RFC2520 NHRP with Mobile NHCs 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. | February 1999 Status: EXPERIMENTAL Autor: J. Luciani, H. Suzuki, N. Doraswamy, D. Horton |
| RFC2521 ICMP Security Failures Messages 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. | March 1999 Status: EXPERIMENTAL Autor: P. Karn, W. Simpson |
| RFC2522 Photuris: Session-Key Management Protocol This document defines the basic protocol mechanisms. This document defines an Experimental Protocol for the Internet community. | March 1999 Status: EXPERIMENTAL Autor: P. Karn, W. Simpson |
| RFC2523 Photuris: Extended Schemes and Attributes 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. | March 1999 Status: EXPERIMENTAL Autor: P. Karn, W. Simpson |
| RFC2524 Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1.3 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. | February 1999 Status: INFORMATIONAL Autor: M. Banan |
| RFC2525 Known TCP Implementation Problems This memo catalogs a number of known TCP implementation problems. This memo provides information for the Internet community. | March 1999 Status: INFORMATIONAL Autor: V. Paxson, M. Allman, S. Dawson, W. Fenner, J. Griner, I. Heavens, K. Lahey, J. Semke, B. Volz |
| RFC2526 Reserved IPv6 Subnet Anycast Addresses 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] | March 1999 Status: PROPOSED STANDARD Autor: D. Johnson, S. Deering |
| RFC2527 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework 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. | March 1999 Status: INFORMATIONAL Autor: S. Chokhani, W. Ford |
| RFC2528 Internet X.509 Public Key Infrastructure Representation of Key Exchange Algorithm (KEA) Keys in Internet X.509 Public Key Infrastructure Certificates 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. | March 1999 Status: INFORMATIONAL Autor: R. Housley, W. Polk |
| RFC2529 Transmission of IPv6 over IPv4 Domains without Explicit Tunnels 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] | March 1999 Status: PROPOSED STANDARD Autor: B. Carpenter, C. Jung |
| RFC2530 Indicating Supported Media Features Using Extensions to DSN and MDN This memo describes a format for generating Message Disposition Notifications and Delivery Status Notifications which contain such information. [STANDARDS-TRACK] | March 1999 Status: PROPOSED STANDARD Autor: D. Wing |
| RFC2531 Content Feature Schema for Internet Fax 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] | March 1999 Status: PROPOSED STANDARD Autor: G. Klyne, L. McIntyre |
| RFC2532 Extended Facsimile Using Internet Mail 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] | March 1999 Status: PROPOSED STANDARD Autor: L. Masinter, D. Wing |
| RFC2533 A Syntax for Describing Media Feature Sets 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] | March 1999 Status: PROPOSED STANDARD Autor: G. Klyne |
| RFC2534 Media Features for Display, Print, and Fax 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] | March 1999 Status: PROPOSED STANDARD Autor: L. Masinter, D. Wing, A. Mutz, K. Holtman |
| RFC2535 Domain Name System Security Extensions This document incorporates feedback on RFC 2065 from early implementers and potential users. [STANDARDS-TRACK] | March 1999 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC2536 DSA KEYs and SIGs in the Domain Name System (DNS) 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] | March 1999 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC2537 RSA/MD5 KEYs and SIGs in the Domain Name System (DNS) 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] | March 1999 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC2538 Storing Certificates in the Domain Name System (DNS) 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] | March 1999 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd, O. Gudmundsson |
| RFC2539 Storage of Diffie-Hellman Keys in the Domain Name System (DNS) A standard method for storing Diffie-Hellman keys in the Domain Name System is described which utilizes DNS KEY resource records. [STANDARDS-TRACK] | March 1999 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC2540 Detached Domain Name System (DNS) Information 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. | March 1999 Status: EXPERIMENTAL Autor: D. Eastlake 3rd |
| RFC2541 DNS Security Operational Considerations 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. | March 1999 Status: INFORMATIONAL Autor: D. Eastlake 3rd |
| RFC2542 Terminology and Goals for Internet Fax 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. | March 1999 Status: INFORMATIONAL Autor: L. Masinter |
| RFC2543 SIP: Session Initiation Protocol 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] | March 1999 Status: PROPOSED STANDARD Autor: M. Handley, H. Schulzrinne, E. Schooler, J. Rosenberg |
| RFC2544 Benchmarking Methodology for Network Interconnect Devices 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. | March 1999 Status: INFORMATIONAL Autor: S. Bradner, J. McQuaid |
| RFC2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain 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] | March 1999 Status: PROPOSED STANDARD Autor: P. Marques, F. Dupont |
| RFC2546 6Bone Routing Practice 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. | March 1999 Status: INFORMATIONAL Autor: A. Durand, B. Buclin |
| RFC2547 BGP/MPLS VPNs 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. | March 1999 Status: INFORMATIONAL Autor: E. Rosen, Y. Rekhter |
| RFC2548 Microsoft Vendor-specific RADIUS Attributes This document describes the set of Microsoft vendor-specific RADIUS attributes. This memo provides information for the Internet community. | March 1999 Status: INFORMATIONAL Autor: G. Zorn |
| RFC2549 IP over Avian Carriers with Quality of Service 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. | April 1999 Status: INFORMATIONAL Autor: D. Waitzman |
| RFC2550 Y10K and Beyond 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. | April 1999 Status: INFORMATIONAL Autor: S. Glassman, M. Manasse, J. Mogul |
| RFC2551 The Roman Standards Process -- Revision III 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. | April 1999 Status: INFORMATIONAL Autor: S. Bradner |
| RFC2552 Architecture for the Information Brokerage in the ACTS Project GAIA 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. | April 1999 Status: INFORMATIONAL Autor: M. Blinov, M. Bessonov, C. Clissmann |
| RFC2553 Basic Socket Interface Extensions for IPv6 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. | March 1999 Status: INFORMATIONAL Autor: R. Gilligan, S. Thomson, J. Bound, W. Stevens |
| RFC2554 SMTP Service Extension for Authentication 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] | March 1999 Status: PROPOSED STANDARD Autor: J. Myers |
| RFC2555 30 Years of RFCs 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. | April 1999 Status: INFORMATIONAL Autor: RFC Editor, et al. |
| RFC2556 OSI connectionless transport services on top of UDP Applicability Statement for Historic Status 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. | March 1999 Status: INFORMATIONAL Autor: S. Bradner |
| RFC2557 MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) 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] | March 1999 Status: PROPOSED STANDARD Autor: J. Palme, A. Hopmann, N. Shelness |
| RFC2558 Definitions of Managed Objects for the SONET/SDH Interface Type This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing 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] | March 1999 Status: PROPOSED STANDARD Autor: K. Tesink |
| RFC2559 Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2 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] | April 1999 Status: HISTORIC Autor: S. Boeyen, T. Howes, P. Richard |
| RFC2560 X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP This document specifies a protocol useful in determining the current status of a digital certificate without requiring CRLs. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: M. Myers, R. Ankney, A. Malpani, S. Galperin, C. Adams |
| RFC2561 Base Definitions of Managed Objects for TN3270E Using SMIv2 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] | April 1999 Status: PROPOSED STANDARD Autor: K. White, R. Moore |
| RFC2562 Definitions of Protocol and Managed Objects for TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB) 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] | April 1999 Status: PROPOSED STANDARD Autor: K. White, R. Moore |
| RFC2563 DHCP Option to Disable Stateless Auto-Configuration in IPv4 Clients 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] | May 1999 Status: PROPOSED STANDARD Autor: R. Troll |
| RFC2564 Application Management MIB 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] | May 1999 Status: PROPOSED STANDARD Autor: C. Kalbfleisch, C. Krupczak, R. Presuhn, J. Saperia |
| RFC2565 Internet Printing Protocol/1.0: Encoding and Transport 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. | April 1999 Status: EXPERIMENTAL Autor: R. Herriot, S. Butler, P. Moore, R. Turner |
| RFC2566 Internet Printing Protocol/1.0: Model and Semantics 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. | April 1999 Status: EXPERIMENTAL Autor: R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell |
| RFC2567 Design Goals for an Internet Printing Protocol 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. | April 1999 Status: EXPERIMENTAL Autor: F. Wright |
| RFC2568 Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol 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. | April 1999 Status: EXPERIMENTAL Autor: S. Zilles |
| RFC2569 Mapping between LPD and IPP Protocols 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. | April 1999 Status: EXPERIMENTAL Autor: R. Herriot, T. Hastings, N. Jacobs, J. Martin |
| RFC2570 Introduction to Version 3 of the Internet-standard Network Management Framework 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. | April 1999 Status: INFORMATIONAL Autor: J. Case, R. Mundy, D. Partain, B. Stewart |
| RFC2571 An Architecture for Describing SNMP Management Frameworks This document describes an architecture for describing SNMP Management Frameworks. [STANDARDS-TRACK] | April 1999 Status: DRAFT STANDARD Autor: B. Wijnen, D. Harrington, R. Presuhn |
| RFC2572 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) This document describes the Message Processing and Dispatching for SNMP messages within the SNMP architecture. 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] | April 1999 Status: DRAFT STANDARD Autor: J. Case, D. Harrington, R. Presuhn, B. Wijnen |
| RFC2573 SNMP Applications 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] | April 1999 Status: DRAFT STANDARD Autor: D. Levi, P. Meyer, B. Stewart |
| RFC2574 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) This document describes the User-based Security Model (USM) for SNMP version 3 for use in the SNMP architecture. 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] | April 1999 Status: DRAFT STANDARD Autor: U. Blumenthal, B. Wijnen |
| RFC2575 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) This document describes the View-based Access Control Model for use in the SNMP architecture (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] | April 1999 Status: DRAFT STANDARD Autor: B. Wijnen, R. Presuhn, K. McCloghrie |
| RFC2576 Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework 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] | March 2000 Status: PROPOSED STANDARD Autor: R. Frye, D. Levi, S. Routhier, B. Wijnen |
| RFC2577 FTP Security Considerations 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. | May 1999 Status: INFORMATIONAL Autor: M. Allman, S. Ostermann |
| RFC2578 Structure of Management Information Version 2 (SMIv2) 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] | April 1999 Status: STANDARD Autor: K. McCloghrie, D. Perkins, J. Schoenwaelder |
| RFC2579 Textual Conventions for SMIv2 It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK] | April 1999 Status: STANDARD Autor: K. McCloghrie, D. Perkins, J. Schoenwaelder |
| RFC2580 Conformance Statements for SMIv2 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] | April 1999 Status: STANDARD Autor: K. McCloghrie, D. Perkins, J. Schoenwaelder |
| RFC2581 TCP Congestion Control 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] | April 1999 Status: PROPOSED STANDARD Autor: M. Allman, V. Paxson, W. Stevens |
| RFC2582 The NewReno Modification to TCP's Fast Recovery Algorithm 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. | April 1999 Status: EXPERIMENTAL Autor: S. Floyd, T. Henderson |
| RFC2583 Guidelines for Next Hop Client (NHC) Developers 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. | May 1999 Status: INFORMATIONAL Autor: R. Carlson, L. Winkler |
| RFC2584 Definitions of Managed Objects for APPN/HPR in IP Networks This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it 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] | May 1999 Status: PROPOSED STANDARD Autor: B. Clouston, B. Moore |
| RFC2585 Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP 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] | May 1999 Status: PROPOSED STANDARD Autor: R. Housley, P. Hoffman |
| RFC2586 The Audio/L16 MIME content type 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. | May 1999 Status: INFORMATIONAL Autor: J. Salsman, H. Alvestrand |
| RFC2587 Internet X.509 Public Key Infrastructure LDAPv2 Schema 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] | June 1999 Status: PROPOSED STANDARD Autor: S. Boeyen, T. Howes, P. Richard |
| RFC2588 IP Multicast and Firewalls 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. | May 1999 Status: INFORMATIONAL Autor: R. Finlayson |
| RFC2589 Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services 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] | May 1999 Status: PROPOSED STANDARD Autor: Y. Yaacovi, M. Wahl, T. Genovese |
| RFC2590 Transmission of IPv6 Packets over Frame Relay Networks Specification This memo describes mechanisms for the transmission of IPv6 packets over Frame Relay networks. [STANDARDS-TRACK] | May 1999 Status: PROPOSED STANDARD Autor: A. Conta, A. Malis, M. Mueller |
| RFC2591 Definitions of Managed Objects for Scheduling Management Operations This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] | May 1999 Status: PROPOSED STANDARD Autor: D. Levi, J. Schoenwaelder |
| RFC2592 Definitions of Managed Objects for the Delegation of Management Script 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] | May 1999 Status: PROPOSED STANDARD Autor: D. Levi, J. Schoenwaelder |
| RFC2593 Script MIB Extensibility Protocol Version 1.0 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. | May 1999 Status: EXPERIMENTAL Autor: J. Schoenwaelder, J. Quittek |
| RFC2594 Definitions of Managed Objects for WWW Services 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] | May 1999 Status: PROPOSED STANDARD Autor: H. Hazewinkel, C. Kalbfleisch, J. Schoenwaelder |
| RFC2595 Using TLS with IMAP, POP3 and ACAP 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] | June 1999 Status: PROPOSED STANDARD Autor: C. Newman |
| RFC2596 Use of Language Codes in LDAP This document describes how language codes are carried in LDAP and are to be interpreted by LDAP servers. [STANDARDS-TRACK] | May 1999 Status: PROPOSED STANDARD Autor: M. Wahl, T. Howes |
| RFC2597 Assured Forwarding PHB Group This document defines a general use Differentiated Services (DS) Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: J. Heinanen, F. Baker, W. Weiss, J. Wroclawski |
| RFC2598 An Expedited Forwarding PHB 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] | June 1999 Status: PROPOSED STANDARD Autor: V. Jacobson, K. Nichols, K. Poduri |
| RFC2599 Request for Comments Summary RFC Numbers 2500-2599 | March 2000 Status: INFORMATIONAL Autor: A. DeLaCruz |
| RFC2600 Internet 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] | March 2000 Status: HISTORIC Autor: J. Reynolds, R. Braden |
| RFC2601 ILMI-Based Server Discovery for ATMARP 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] | June 1999 Status: PROPOSED STANDARD Autor: M. Davison |
| RFC2602 ILMI-Based Server Discovery for MARS 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] | June 1999 Status: PROPOSED STANDARD Autor: M. Davison |
| RFC2603 ILMI-Based Server Discovery for NHRP 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] | June 1999 Status: PROPOSED STANDARD Autor: M. Davison |
| RFC2604 Wireless Device Configuration (OTASP/OTAPA) via ACAP 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. | June 1999 Status: INFORMATIONAL Autor: R. Gellens |
| RFC2605 Directory Server Monitoring MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: G. Mansfield, S. Kille |
| RFC2606 Reserved Top Level DNS Names 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. | June 1999 Status: BEST CURRENT PRACTICE Autor: D. Eastlake 3rd, A. Panitz |
| RFC2607 Proxy Chaining and Policy Implementation in Roaming This document describes how proxy chaining and policy implementation can be supported in roaming systems. This memo provides information for the Internet community. | June 1999 Status: INFORMATIONAL Autor: B. Aboba, J. Vollbrecht |
| RFC2608 Service Location Protocol, Version 2 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] | June 1999 Status: PROPOSED STANDARD Autor: E. Guttman, C. Perkins, J. Veizades, M. Day |
| RFC2609 Service Templates and Service: Schemes This document describes a formal procedure for defining and standardizing new service types and attributes for use with the "service:" scheme. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: E. Guttman, C. Perkins, J. Kempf |
| RFC2610 DHCP Options for Service Location 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] | June 1999 Status: PROPOSED STANDARD Autor: C. Perkins, E. Guttman |
| RFC2611 URN Namespace Definition Mechanisms 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. | June 1999 Status: BEST CURRENT PRACTICE Autor: L. Daigle, D. van Gulik, R. Iannella, P. Falstrom |
| RFC2612 The CAST-256 Encryption Algorithm 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. | June 1999 Status: INFORMATIONAL Autor: C. Adams, J. Gilchrist |
| RFC2613 Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0 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] | June 1999 Status: DRAFT STANDARD Autor: R. Waterman, B. Lahaye, D. Romascanu, S. Waldbusser |
| RFC2614 An API for Service Location This document describes standardized APIs for SLP in C and Java. This memo provides information for the Internet community. | June 1999 Status: INFORMATIONAL Autor: J. Kempf, E. Guttman |
| RFC2615 PPP over SONET/SDH This document describes the use of PPP over Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) circuits. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: A. Malis, W. Simpson |
| RFC2616 Hypertext Transfer Protocol -- HTTP/1.1 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] | June 1999 Status: DRAFT STANDARD Autor: R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee |
| RFC2617 HTTP Authentication: Basic and Digest Access Authentication 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] | June 1999 Status: DRAFT STANDARD Autor: J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart |
| RFC2618 RADIUS Authentication Client MIB This memo defines a set of extensions which instrument RADIUS authentication client functions. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: B. Aboba, G. Zorn |
| RFC2619 RADIUS Authentication Server MIB This memo defines a set of extensions which instrument RADIUS authentication server functions. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: G. Zorn, B. Aboba |
| RFC2620 RADIUS Accounting Client MIB This memo defines a set of extensions which instrument RADIUS accounting client functions. This memo provides information for the Internet community. | June 1999 Status: INFORMATIONAL Autor: B. Aboba, G. Zorn |
| RFC2621 RADIUS Accounting Server MIB This memo defines a set of extensions which instrument RADIUS accounting server functions. This memo provides information for the Internet community. | June 1999 Status: INFORMATIONAL Autor: G. Zorn, B. Aboba |
| RFC2622 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] | June 1999 Status: PROPOSED STANDARD Autor: C. Alaettinoglu, C. Villamizar, E. Gerich, D. Kessens, D. Meyer, T. Bates, D. Karrenberg, M. Terpstra |
| RFC2623 NFS Version 2 and Version 3 Security Issues and the NFS Protocol's Use of RPCSEC_GSS and Kerberos V5 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] | June 1999 Status: PROPOSED STANDARD Autor: M. Eisler |
| RFC2624 NFS Version 4 Design Considerations 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. | June 1999 Status: INFORMATIONAL Autor: S. Shepler |
| RFC2625 IP and ARP over Fibre Channel 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] | June 1999 Status: PROPOSED STANDARD Autor: M. Rajagopal, R. Bhagwat, W. Rickard |
| RFC2626 The Internet and the Millennium Problem (Year 2000) 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. | June 1999 Status: INFORMATIONAL Autor: P. Nesser II |
| RFC2627 Key Management for Multicast: Issues and Architectures 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. | June 1999 Status: INFORMATIONAL Autor: D. Wallner, E. Harder, R. Agee |
| RFC2628 Simple Cryptographic Program Interface (Crypto API) This document describes a simple Application Program Interface to cryptographic functions. This memo provides information for the Internet community. | June 1999 Status: INFORMATIONAL Autor: V. Smyslov |
| RFC2629 Writing I-Ds and RFCs using XML 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. | June 1999 Status: INFORMATIONAL Autor: M. Rose |
| RFC2630 Cryptographic Message Syntax This document describes the Cryptographic Message Syntax. This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary messages. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC2631 Diffie-Hellman Key Agreement Method This document standardizes one particular Diffie-Hellman variant, based on the ANSI X9.42 draft, developed by the ANSI X9F1 working group. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: E. Rescorla |
| RFC2632 S/MIME Version 3 Certificate Handling 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] | June 1999 Status: PROPOSED STANDARD Autor: B. Ramsdell |
| RFC2633 S/MIME Version 3 Message Specification This document describes a protocol for adding cryptographic signature and encryption services to MIME data. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: B. Ramsdell |
| RFC2634 Enhanced Security Services for S/MIME This document describes four optional security service extensions for S/MIME. [STANDARDS-TRACK] | June 1999 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC2635 DON'T SPEW A Set of Guidelines for Mass Unsolicited Mailings and Postings (spam*) This document explains why mass unsolicited electronic mail messages are harmful in the Internetworking community. This memo provides information for the Internet community. | June 1999 Status: INFORMATIONAL Autor: S. Hambridge, A. Lunde |
| RFC2636 Wireless Device Configuration (OTASP/OTAPA) via ACAP 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. | July 1999 Status: INFORMATIONAL Autor: R. Gellens |
| RFC2637 Point-to-Point Tunneling Protocol (PPTP) 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. | July 1999 Status: INFORMATIONAL Autor: K. Hamzeh, G. Pall, W. Verthein, J. Taarud, W. Little, G. Zorn |
| RFC2638 A Two-bit Differentiated Services Architecture for the Internet This document presents a differentiated services architecture for the internet. This memo provides information for the Internet community. | July 1999 Status: INFORMATIONAL Autor: K. Nichols, V. Jacobson, L. Zhang |
| RFC2639 Internet Printing Protocol/1.0: Implementer's Guide 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. | July 1999 Status: INFORMATIONAL Autor: T. Hastings, C. Manros |
| RFC2640 Internationalization of the File Transfer Protocol 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] | July 1999 Status: PROPOSED STANDARD Autor: B. Curtin |
| RFC2641 Cabletron's VlanHello Protocol Specification Version 4 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. | August 1999 Status: INFORMATIONAL Autor: D. Hamilton, D. Ruffen |
| RFC2642 Cabletron's VLS Protocol Specification 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. | August 1999 Status: INFORMATIONAL Autor: L. Kane |
| RFC2643 Cabletron's SecureFast VLAN Operational Model 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. | August 1999 Status: INFORMATIONAL Autor: D. Ruffen, T. Len, J. Yanacek |
| RFC2644 Changing the Default for Directed Broadcasts in Routers 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. | August 1999 Status: BEST CURRENT PRACTICE Autor: D. Senie |
| RFC2645 ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP Addresses 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] | August 1999 Status: PROPOSED STANDARD Autor: R. Gellens |
| RFC2646 The Text/Plain Format Parameter 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] | August 1999 Status: PROPOSED STANDARD Autor: R. Gellens |
| RFC2647 Benchmarking Terminology for Firewall Performance 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] | August 1999 Status: INFORMATIONAL Autor: D. Newman |
| RFC2648 A URN Namespace for IETF Documents 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] | August 1999 Status: INFORMATIONAL Autor: R. Moats |
| RFC2649 An LDAP Control and Schema for Holding Operation Signatures 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. | August 1999 Status: EXPERIMENTAL Autor: B. Greenblatt, P. Richard |
| RFC2650 Using RPSL in Practice 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. | August 1999 Status: INFORMATIONAL Autor: D. Meyer, J. Schmitz, C. Orange, M. Prior, C. Alaettinoglu |
| RFC2651 The Architecture of the Common Indexing Protocol (CIP) This document describes the CIP framework, including its architecture and the protocol specifics of exchanging indices. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: J. Allen, M. Mealling |
| RFC2652 MIME Object Definitions for the Common Indexing Protocol (CIP) This document describes the definitions of those objects as well as the methods and requirements needed to define a new index type. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: J. Allen, M. Mealling |
| RFC2653 CIP Transport Protocols This document specifies three protocols for transporting CIP requests, responses and index objects, utilizing TCP, mail, and HTTP. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: J. Allen, P. Leach, R. Hedberg |
| RFC2654 A Tagged Index Object for use in the Common Indexing Protocol 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. | August 1999 Status: EXPERIMENTAL Autor: R. Hedberg, B. Greenblatt, R. Moats, M. Wahl |
| RFC2655 CIP Index Object Format for SOIF Objects 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. | August 1999 Status: EXPERIMENTAL Autor: T. Hardie, M. Bowman, D. Hardy, M. Schwartz, D. Wessels |
| RFC2656 Registration Procedures for SOIF Template Types The registration procedure described in this document is specific to SOIF template types. This memo defines an Experimental Protocol for the Internet community. | August 1999 Status: EXPERIMENTAL Autor: T. Hardie |
| RFC2657 LDAPv2 Client vs. the Index Mesh 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. | August 1999 Status: EXPERIMENTAL Autor: R. Hedberg |
| RFC2658 RTP Payload Format for PureVoice(tm) Audio This document describes the RTP payload format for PureVoice(tm) Audio. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: K. McKay |
| RFC2659 Security Extensions For HTML This memo describes a syntax for embedding S-HTTP negotiation parameters in HTML documents. This memo defines an Experimental Protocol for the Internet community. | August 1999 Status: EXPERIMENTAL Autor: E. Rescorla, A. Schiffman |
| RFC2660 The Secure HyperText Transfer Protocol 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. | August 1999 Status: EXPERIMENTAL Autor: E. Rescorla, A. Schiffman |
| RFC2661 Layer Two Tunneling Protocol "L2TP" This document describes the Layer Two Tunneling Protocol (L2TP). [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: W. Townsley, A. Valencia, A. Rubens, G. Pall, G. Zorn, B. Palter |
| RFC2662 Definitions of Managed Objects for the ADSL Lines This document defines a standard SNMP MIB for ADSL lines based on the ADSL Forum standard data model. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: G. Bathrick, F. Ly |
| RFC2663 IP Network Address Translator (NAT) Terminology and Considerations 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. | August 1999 Status: INFORMATIONAL Autor: P. Srisuresh, M. Holdrege |
| RFC2664 FYI on Questions and Answers - Answers to Commonly Asked "New Internet User" Questions 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. | August 1999 Status: INFORMATIONAL Autor: R. Plzak, A. Wells, E. Krol |
| RFC2665 Definitions of Managed Objects for the Ethernet-like Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: J. Flick, J. Johnson |
| RFC2666 Definitions of Object Identifiers for Identifying Ethernet Chip Sets This memo defines OBJECT IDENTIFIER values for use with network management protocols in the Internet community. This memo provides information for the Internet community. | August 1999 Status: INFORMATIONAL Autor: J. Flick |
| RFC2667 IP Tunnel MIB 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] | August 1999 Status: PROPOSED STANDARD Autor: D. Thaler |
| RFC2668 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: A. Smith, J. Flick, K. de Graaf, D. Romascanu, D. McMaster, K. McCloghrie, S. Roberts |
| RFC2669 DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems 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] | August 1999 Status: PROPOSED STANDARD Autor: M. St. Johns |
| RFC2670 Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces 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] | August 1999 Status: PROPOSED STANDARD Autor: M. St. Johns |
| RFC2671 Extension Mechanisms for DNS (EDNS0) 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] | August 1999 Status: PROPOSED STANDARD Autor: P. Vixie |
| RFC2672 Non-Terminal DNS Name Redirection 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] | August 1999 Status: PROPOSED STANDARD Autor: M. Crawford |
| RFC2673 Binary Labels in the Domain Name System 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] | August 1999 Status: EXPERIMENTAL Autor: M. Crawford |
| RFC2674 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: E. Bell, A. Smith, P. Langille, A. Rijhsinghani, K. McCloghrie |
| RFC2675 IPv6 Jumbograms 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] | August 1999 Status: PROPOSED STANDARD Autor: D. Borman, S. Deering, R. Hinden |
| RFC2676 QoS Routing Mechanisms and OSPF Extensions 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. | August 1999 Status: EXPERIMENTAL Autor: G. Apostolopoulos, S. Kama, D. Williams, R. Guerin, A. Orda, T. Przygienda |
| RFC2677 Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP) This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK] | August 1999 Status: PROPOSED STANDARD Autor: M. Greene, J. Cucchiara, J. Luciani |
| RFC2678 IPPM Metrics for Measuring Connectivity This memo defines a series of metrics for connectivity between a pair of Internet hosts. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: J. Mahdavi, V. Paxson |
| RFC2679 A One-way Delay Metric for IPPM This memo defines a metric for one-way delay of packets across Internet paths. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: G. Almes, S. Kalidindi, M. Zekauskas |
| RFC2680 A One-way Packet Loss Metric for IPPM This memo defines a metric for one-way packet loss across Internet paths. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: G. Almes, S. Kalidindi, M. Zekauskas |
| RFC2681 A Round-trip Delay Metric for IPPM This memo defines a metric for round-trip delay of packets across Internet paths. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: G. Almes, S. Kalidindi, M. Zekauskas |
| RFC2682 Performance Issues in VC-Merge Capable ATM LSRs 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. | September 1999 Status: INFORMATIONAL Autor: I. Widjaja, A. Elwalid |
| RFC2683 IMAP4 Implementation Recommendations 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. | September 1999 Status: INFORMATIONAL Autor: B. Leiba |
| RFC2684 Multiprotocol Encapsulation over ATM Adaptation Layer 5 This memo replaces RFC 1483. It describes two encapsulations methods for carrying network interconnect traffic over AAL type 5 over ATM. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: D. Grossman, J. Heinanen |
| RFC2685 Virtual Private Networks Identifier This document proposes a format for a globally unique VPN identifier. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: B. Fox, B. Gleeson |
| RFC2686 The Multi-Class Extension to Multi-Link PPP This document proposes the fragment-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: C. Bormann |
| RFC2687 PPP in a Real-time Oriented HDLC-like Framing This document proposes the suspend/resume-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: C. Bormann |
| RFC2688 Integrated Services Mappings for Low Speed Networks This document defines the service mappings of the IETF Integrated Services for low-bitrate links, specifically the controlled load and guaranteed services. [STANDARDS-TRACK] | September 1999 Status: PROPOSED STANDARD Autor: S. Jackowski, D. Putzolu, E. Crawley, B. Davie |
| RFC2689 Providing Integrated Services over Low-bitrate Links 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. | September 1999 Status: INFORMATIONAL Autor: C. Bormann |
| RFC2690 A Proposal for an MOU-Based ICANN Protocol Support Organization 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. | September 1999 Status: INFORMATIONAL Autor: S. Bradner |
| RFC2691 A Memorandum of Understanding for an ICANN Protocol Support Organization 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. | September 1999 Status: INFORMATIONAL Autor: S. Bradner |
| RFC2692 SPKI Requirements 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. | September 1999 Status: EXPERIMENTAL Autor: C. Ellison |
| RFC2693 SPKI Certificate Theory 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. | September 1999 Status: EXPERIMENTAL Autor: C. Ellison, B. Frantz, B. Lampson, R. Rivest, B. Thomas, T. Ylonen |
| RFC2694 DNS extensions to Network Address Translators (DNS_ALG) 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. | September 1999 Status: INFORMATIONAL Autor: P. Srisuresh, G. Tsirtsis, P. Akkiraju, A. Heffernan |
| RFC2695 Authentication Mechanisms for ONC RPC 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. | September 1999 Status: INFORMATIONAL Autor: A. Chiu |
| RFC2696 LDAP Control Extension for Simple Paged Results Manipulation This document describes an LDAPv3 control extension for simple paging of search results. This memo provides information for the Internet community. | September 1999 Status: INFORMATIONAL Autor: C. Weider, A. Herron, A. Anantha, T. Howes |
| RFC2697 A Single Rate Three Color Marker 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. | September 1999 Status: INFORMATIONAL Autor: J. Heinanen, R. Guerin |
| RFC2698 A Two Rate Three Color Marker 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. | September 1999 Status: INFORMATIONAL Autor: J. Heinanen, R. Guerin |
| RFC2699 Request for Comments Summary RFC Numbers 2600-2699 | May 2000 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC2700 Internet Official Protocol Standards 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] | August 2000 Status: HISTORIC Autor: J. Reynolds, R. Braden |
| RFC2701 Nortel Networks Multi-link Multi-node PPP Bundle Discovery Protocol This document specifies a standard way for Multi-link PPP to operate across multiple nodes. This memo provides information for the Internet community. | September 1999 Status: INFORMATIONAL Autor: G. Malkin |
| RFC2702 Requirements for Traffic Engineering Over MPLS 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. | September 1999 Status: INFORMATIONAL Autor: D. Awduche, J. Malcolm, J. Agogbua, M. O'Dell, J. McManus |
| RFC2703 Protocol-independent Content Negotiation Framework 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. | September 1999 Status: INFORMATIONAL Autor: G. Klyne |
| RFC2704 The KeyNote Trust-Management System Version 2 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. | September 1999 Status: INFORMATIONAL Autor: M. Blaze, J. Feigenbaum, J. Ioannidis, A. Keromytis |
| RFC2705 Media Gateway Control Protocol (MGCP) Version 1.0 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. | October 1999 Status: INFORMATIONAL Autor: M. Arango, A. Dugan, I. Elliott, C. Huitema, S. Pickett |
| RFC2706 ECML v1: Field Names for E-Commerce 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. | October 1999 Status: INFORMATIONAL Autor: D. Eastlake 3rd, T. Goldstein |
| RFC2707 Job Monitoring MIB - V1.0 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. | November 1999 Status: INFORMATIONAL Autor: R. Bergman, T. Hastings, S. Isaacson, H. Lewis |
| RFC2708 Job Submission Protocol Mapping Recommendations for the Job Monitoring MIB 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. | November 1999 Status: INFORMATIONAL Autor: R. Bergman |
| RFC2709 Security Model with Tunnel-mode IPsec for NAT Domains 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. | October 1999 Status: INFORMATIONAL Autor: P. Srisuresh |
| RFC2710 Multicast Listener Discovery (MLD) for IPv6 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] | October 1999 Status: PROPOSED STANDARD Autor: S. Deering, W. Fenner, B. Haberman |
| RFC2711 IPv6 Router Alert Option 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] | October 1999 Status: PROPOSED STANDARD Autor: C. Partridge, A. Jackson |
| RFC2712 Addition of Kerberos Cipher Suites to Transport Layer Security (TLS) This document proposes the addition of new cipher suites to the TLS protocol to support Kerberos-based authentication. [STANDARDS-TRACK] | October 1999 Status: PROPOSED STANDARD Autor: A. Medvinsky, M. Hur |
| RFC2713 Schema for Representing Java(tm) Objects in an LDAP Directory This document defines the schema for representing Java(tm) objects in an LDAP directory. This memo provides information for the Internet community. | October 1999 Status: INFORMATIONAL Autor: V. Ryan, S. Seligman, R. Lee |
| RFC2714 Schema for Representing CORBA Object References in an LDAP Directory This document defines the schema for representing CORBA object references in an LDAP directory. This memo provides information for the Internet community. | October 1999 Status: INFORMATIONAL Autor: V. Ryan, R. Lee, S. Seligman |
| RFC2715 Interoperability Rules for Multicast Routing Protocols The rules described in this document will allow efficient interoperation among multiple independent multicast routing domains. This memo provides information for the Internet community. | October 1999 Status: INFORMATIONAL Autor: D. Thaler |
| RFC2716 PPP EAP TLS Authentication Protocol 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. | October 1999 Status: EXPERIMENTAL Autor: B. Aboba, D. Simon |
| RFC2717 Registration Procedures for URL Scheme Names 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. | November 1999 Status: BEST CURRENT PRACTICE Autor: R. Petke, I. King |
| RFC2718 Guidelines for new URL Schemes This document provides guidelines for the definition of new URL schemes. This memo provides information for the Internet community. | November 1999 Status: INFORMATIONAL Autor: L. Masinter, H. Alvestrand, D. Zigmond, R. Petke |
| RFC2719 Framework Architecture for Signaling Transport This document defines an architecture framework and functional requirements for transport of signaling information over IP. This memo provides information for the Internet community. | October 1999 Status: INFORMATIONAL Autor: L. Ong, I. Rytina, M. Garcia, H. Schwarzbauer, L. Coene, H. Lin, I. Juhasz, M. Holdrege, C. Sharp |
| RFC2720 Traffic Flow Measurement: Meter MIB 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] | October 1999 Status: PROPOSED STANDARD Autor: N. Brownlee |
| RFC2721 RTFM: Applicability Statement 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. | October 1999 Status: INFORMATIONAL Autor: N. Brownlee |
| RFC2722 Traffic Flow Measurement: Architecture 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. | October 1999 Status: INFORMATIONAL Autor: N. Brownlee, C. Mills, G. Ruth |
| RFC2723 SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow Groups 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. | October 1999 Status: INFORMATIONAL Autor: N. Brownlee |
| RFC2724 RTFM: New Attributes for Traffic Flow Measurement 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. | October 1999 Status: EXPERIMENTAL Autor: S. Handelman, S. Stibler, N. Brownlee, G. Ruth |
| RFC2725 Routing Policy System Security 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] | December 1999 Status: PROPOSED STANDARD Autor: C. Villamizar, C. Alaettinoglu, D. Meyer, S. Murphy |
| RFC2726 PGP Authentication for RIPE Database Updates This document presents the proposal for a stronger authentication method of the updates of the RIPE database based on digital signatures. [STANDARDS-TRACK] | December 1999 Status: PROPOSED STANDARD Autor: J. Zsako |
| RFC2727 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document 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. | February 2000 Status: BEST CURRENT PRACTICE Autor: J. Galvin |
| RFC2728 The Transmission of IP Over the Vertical Blanking Interval of a Television Signal This document describes a method for broadcasting IP data in a unidirectional manner using the vertical blanking interval of television signals. [STANDARDS-TRACK] | November 1999 Status: PROPOSED STANDARD Autor: R. Panabaker, S. Wegerif, D. Zigmond |
| RFC2729 Taxonomy of Communication Requirements for Large-scale Multicast Applications 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. | December 1999 Status: INFORMATIONAL Autor: P. Bagnall, R. Briscoe, A. Poppitt |
| RFC2730 Multicast Address Dynamic Client Allocation Protocol (MADCAP) 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] | December 1999 Status: PROPOSED STANDARD Autor: S. Hanna, B. Patel, M. Shah |
| RFC2731 Encoding Dublin Core Metadata in HTML 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. | December 1999 Status: INFORMATIONAL Autor: J. Kunze |
| RFC2732 Format for Literal IPv6 Addresses in URL's This document defines the format for literal IPv6 Addresses in URL's for implementation in World Wide Web browsers. [STANDARDS-TRACK] | December 1999 Status: PROPOSED STANDARD Autor: R. Hinden, B. Carpenter, L. Masinter |
| RFC2733 An RTP Payload Format for Generic Forward Error Correction This document specifies a payload format for generic forward error correction of media encapsulated in RTP. [STANDARDS-TRACK] | December 1999 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne |
| RFC2734 IPv4 over IEEE 1394 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] | December 1999 Status: PROPOSED STANDARD Autor: P. Johansson |
| RFC2735 NHRP Support for Virtual Private Networks 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] | December 1999 Status: PROPOSED STANDARD Autor: B. Fox, B. Petri |
| RFC2736 Guidelines for Writers of RTP Payload Format Specifications 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. | December 1999 Status: BEST CURRENT PRACTICE Autor: M. Handley, C. Perkins |
| RFC2737 Entity MIB (Version 2) 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] | December 1999 Status: PROPOSED STANDARD Autor: K. McCloghrie, A. Bierman |
| RFC2738 Corrections to "A Syntax for Describing Media Feature Sets" 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] | December 1999 Status: PROPOSED STANDARD Autor: G. Klyne |
| RFC2739 Calendar Attributes for vCard and LDAP This memo defines three mechanisms for obtaining a URI to a user's calendar and free/busy time. [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: T. Small, D. Hennessy, F. Dawson |
| RFC2740 OSPF for IPv6 This document describes the modifications to OSPF to support version 6 of the Internet Protocol (IPv6). [STANDARDS-TRACK] | December 1999 Status: PROPOSED STANDARD Autor: R. Coltun, D. Ferguson, J. Moy |
| RFC2741 Agent Extensibility (AgentX) Protocol Version 1 This memo defines a standardized framework for extensible SNMP agents. [STANDARDS-TRACK] | January 2000 Status: DRAFT STANDARD Autor: M. Daniele, B. Wijnen, M. Ellison, D. Francisco |
| RFC2742 Definitions of Managed Objects for Extensible SNMP Agents 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] | January 2000 Status: DRAFT STANDARD Autor: L. Heintz, S. Gudur, M. Ellison |
| RFC2743 Generic Security Service Application Program Interface Version 2, Update 1 This memo obsoletes [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: J. Linn |
| RFC2744 Generic Security Service API Version 2 : C-bindings 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] | January 2000 Status: PROPOSED STANDARD Autor: J. Wray |
| RFC2745 RSVP Diagnostic Messages This document specifies the RSVP diagnostic facility, which allows a user to collect information about the RSVP state along a path. [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: A. Terzis, B. Braden, S. Vincent, L. Zhang |
| RFC2746 RSVP Operation Over IP Tunnels This document describes an approach for providing RSVP protocol services over IP tunnels. [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: A. Terzis, J. Krawczyk, J. Wroclawski, L. Zhang |
| RFC2747 RSVP Cryptographic Authentication 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] | January 2000 Status: PROPOSED STANDARD Autor: F. Baker, B. Lindell, M. Talwar |
| RFC2748 The COPS (Common Open Policy Service) Protocol This document describes a simple client/server model for supporting policy control over QoS signaling protocols. [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: D. Durham, J. Boyle, R. Cohen, S. Herzog, R. Rajan, A. Sastry |
| RFC2749 COPS usage for RSVP This document describes usage directives for supporting COPS policy services in RSVP environments. [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: S. Herzog, J. Boyle, R. Cohen, D. Durham, R. Rajan, A. Sastry |
| RFC2750 RSVP Extensions for Policy Control This memo presents a set of extensions for supporting generic policy based admission control in RSVP. [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: S. Herzog |
| RFC2751 Signaled Preemption Priority Policy Element This document describes a preemption priority policy element for use by signaled policy based admission protocols (such as RSVP and COPS). [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: S. Herzog |
| RFC2752 Identity Representation for RSVP This document describes the representation of identity information in POLICY_DATA object for supporting policy based admission control in RSVP. [STANDARDS-TRACK] | January 2000 Status: PROPOSED STANDARD Autor: S. Yadav, R. Yavatkar, R. Pabbati, P. Ford, T. Moore, S. Herzog |
| RFC2753 A Framework for Policy-based Admission Control 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. | January 2000 Status: INFORMATIONAL Autor: R. Yavatkar, D. Pendarakis, R. Guerin |
| RFC2754 RPS IANA Issues 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. | January 2000 Status: HISTORIC Autor: C. Alaettinoglu, C. Villamizar, R. Govindan |
| RFC2755 Security Negotiation for WebNFS 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. | January 2000 Status: INFORMATIONAL Autor: A. Chiu, M. Eisler, B. Callaghan |
| RFC2756 Hyper Text Caching Protocol (HTCP/0.0) 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. | January 2000 Status: EXPERIMENTAL Autor: P. Vixie, D. Wessels |
| RFC2757 Long Thin Networks 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. | January 2000 Status: INFORMATIONAL Autor: G. Montenegro, S. Dawkins, M. Kojo, V. Magret, N. Vaidya |
| RFC2758 Definitions of Managed Objects for Service Level Agreements Performance Monitoring 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. | February 2000 Status: EXPERIMENTAL Autor: K. White |
| RFC2759 Microsoft PPP CHAP Extensions, Version 2 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. | January 2000 Status: INFORMATIONAL Autor: G. Zorn |
| RFC2760 Ongoing TCP Research Related to Satellites 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. | February 2000 Status: INFORMATIONAL Autor: M. Allman, S. Dawkins, D. Glover, J. Griner, D. Tran, T. Henderson, J. Heidemann, J. Touch, H. Kruse, S. Ostermann, K. Scott, J. Semke |
| RFC2761 Terminology for ATM Benchmarking 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. | February 2000 Status: INFORMATIONAL Autor: J. Dunn, C. Martin |
| RFC2762 Sampling of the Group Membership in RTP 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. | February 2000 Status: EXPERIMENTAL Autor: J. Rosenberg, H. Schulzrinne |
| RFC2763 Dynamic Hostname Exchange Mechanism for IS-IS 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. | February 2000 Status: INFORMATIONAL Autor: N. Shen, H. Smit |
| RFC2764 A Framework for IP Based Virtual Private Networks This document describes a framework for Virtual Private Networks (VPNs) running across IP backbones. This memo provides information for the Internet community. | February 2000 Status: INFORMATIONAL Autor: B. Gleeson, A. Lin, J. Heinanen, G. Armitage, A. Malis |
| RFC2765 Stateless IP/ICMP Translation Algorithm (SIIT) This document specifies a transition mechanism algorithm in addition to the mechanisms already specified. [STANDARDS-TRACK] | February 2000 Status: PROPOSED STANDARD Autor: E. Nordmark |
| RFC2766 Network Address Translation - Protocol Translation (NAT-PT) This document specifies an IPv4-to-IPv6 transition mechanism, in addition to those already specified. [STANDARDS-TRACK] | February 2000 Status: HISTORIC Autor: G. Tsirtsis, P. Srisuresh |
| RFC2767 Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS) 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. | February 2000 Status: INFORMATIONAL Autor: K. Tsuchiya, H. Higuchi, Y. Atarashi |
| RFC2768 Network Policy and Services: A Report of a Workshop on Middleware 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. | February 2000 Status: INFORMATIONAL Autor: B. Aiken, J. Strassner, B. Carpenter, I. Foster, C. Lynch, J. Mambretti, R. Moore, B. Teitelbaum |
| RFC2769 Routing Policy System Replication 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] | February 2000 Status: PROPOSED STANDARD Autor: C. Villamizar, C. Alaettinoglu, R. Govindan, D. Meyer |
| RFC2770 GLOP Addressing in 233/8 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. | February 2000 Status: EXPERIMENTAL Autor: D. Meyer, P. Lothberg |
| RFC2771 An Abstract API for Multicast Address Allocation 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. | February 2000 Status: INFORMATIONAL Autor: R. Finlayson |
| RFC2772 6Bone Backbone Routing Guidelines 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. | February 2000 Status: INFORMATIONAL Autor: R. Rockell, R. Fink |
| RFC2773 Encryption using KEA and SKIPJACK This document defines a method to encrypt a file transfer using the FTP specification STD 9, RFC 959, "File Transfer Protocol (FTP)", (October | February 2000 Status: EXPERIMENTAL Autor: R. Housley, P. Yee, W. Nace |
| RFC2774 An HTTP Extension Framework 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. | February 2000 Status: EXPERIMENTAL Autor: H. Nielsen, P. Leach, S. Lawrence |
| RFC2775 Internet Transparency This document describes the current state of the Internet from the architectural viewpoint, concentrating on issues of end-to-end connectivity and transparency. | February 2000 Status: INFORMATIONAL Autor: B. Carpenter |
| RFC2776 Multicast-Scope Zone Announcement Protocol (MZAP) 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] | February 2000 Status: HISTORIC Autor: M. Handley, D. Thaler, R. Kermode |
| RFC2777 Publicly Verifiable Nomcom Random Selection 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. | February 2000 Status: INFORMATIONAL Autor: D. Eastlake 3rd |
| RFC2778 A Model for Presence and Instant Messaging 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. | February 2000 Status: INFORMATIONAL Autor: M. Day, J. Rosenberg, H. Sugano |
| RFC2779 Instant Messaging / Presence Protocol Requirements This document defines a minimal set of requirements that IMPP must meet. This memo provides information for the Internet community. | February 2000 Status: INFORMATIONAL Autor: M. Day, S. Aggarwal, G. Mohr, J. Vincent |
| RFC2780 IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers 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. | March 2000 Status: BEST CURRENT PRACTICE Autor: S. Bradner, V. Paxson |
| RFC2781 UTF-16, an encoding of ISO 10646 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. | February 2000 Status: INFORMATIONAL Autor: P. Hoffman, F. Yergeau |
| RFC2782 A DNS RR for specifying the location of services (DNS SRV) This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain. [STANDARDS-TRACK] | February 2000 Status: PROPOSED STANDARD Autor: A. Gulbrandsen, P. Vixie, L. Esibov |
| RFC2783 Pulse-Per-Second API for UNIX-like Operating Systems, Version 1.0 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. | March 2000 Status: INFORMATIONAL Autor: J. Mogul, D. Mills, J. Brittenson, J. Stone, U. Windl |
| RFC2784 Generic Routing Encapsulation (GRE) This document specifies a protocol for encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol. [STANDARDS-TRACK] | March 2000 Status: PROPOSED STANDARD Autor: D. Farinacci, T. Li, S. Hanks, D. Meyer, P. Traina |
| RFC2785 Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIME 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. | March 2000 Status: INFORMATIONAL Autor: R. Zuccherato |
| RFC2786 Diffie-Helman USM Key Management Information Base and Textual Convention 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. | March 2000 Status: EXPERIMENTAL Autor: M. St. Johns |
| RFC2787 Definitions of Managed Objects for the Virtual Router Redundancy Protocol 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] | March 2000 Status: PROPOSED STANDARD Autor: B. Jewell, D. Chuang |
| RFC2788 Network Services Monitoring MIB This document defines a MIB which contains the elements common to the monitoring of any network service application. [STANDARDS-TRACK] | March 2000 Status: PROPOSED STANDARD Autor: N. Freed, S. Kille |
| RFC2789 Mail Monitoring MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this memo extends the basic Network Services Monitoring MIB defined in RFC 2788 [STANDARDS-TRACK] | March 2000 Status: PROPOSED STANDARD Autor: N. Freed, S. Kille |
| RFC2790 Host Resources MIB 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] | March 2000 Status: DRAFT STANDARD Autor: S. Waldbusser, P. Grillo |
| RFC2791 Scalable Routing Design Principles 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. | July 2000 Status: INFORMATIONAL Autor: J. Yu |
| RFC2792 DSA and RSA Key and Signature Encoding for the KeyNote Trust Management System 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. | March 2000 Status: INFORMATIONAL Autor: M. Blaze, J. Ioannidis, A. Keromytis |
| RFC2793 RTP Payload for Text Conversation 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] | May 2000 Status: PROPOSED STANDARD Autor: G. Hellstrom |
| RFC2794 Mobile IP Network Access Identifier Extension for IPv4 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] | March 2000 Status: PROPOSED STANDARD Autor: P. Calhoun, C. Perkins |
| RFC2795 The Infinite Monkey Protocol Suite (IMPS) 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. | April 2000 Status: INFORMATIONAL Autor: S. Christey |
| RFC2796 BGP Route Reflection - An Alternative to Full Mesh IBGP This document describes the use and design of a method known as "Route Reflection" to alleviate the the need for "full mesh" IBGP. [STANDARDS-TRACK] | April 2000 Status: PROPOSED STANDARD Autor: T. Bates, R. Chandra, E. Chen |
| RFC2797 Certificate Management Messages over CMS This document defines a Certificate Management protocol using CMS (CMC). [STANDARDS-TRACK] | April 2000 Status: PROPOSED STANDARD Autor: M. Myers, X. Liu, J. Schaad, J. Weinstein |
| RFC2798 Definition of the inetOrgPerson LDAP Object Class 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. | April 2000 Status: INFORMATIONAL Autor: M. Smith |
| RFC2799 Request for Comments Summary RFC Numbers 2700-2799 | September 2000 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC2800 Internet Official Protocol Standards 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] | May 2001 Status: HISTORIC Autor: J. Reynolds, R. Braden, S. Ginoza |
| RFC2801 Internet Open Trading Protocol - IOTP Version 1.0 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. | April 2000 Status: INFORMATIONAL Autor: D. Burdett |
| RFC2802 Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP) 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. | April 2000 Status: INFORMATIONAL Autor: K. Davidson, Y. Kawatsura |
| RFC2803 Digest Values for DOM (DOMHASH) 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. | April 2000 Status: INFORMATIONAL Autor: H. Maruyama, K. Tamura, N. Uramoto |
| RFC2804 IETF Policy on Wiretapping 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. | May 2000 Status: INFORMATIONAL Autor: IAB, IESG |
| RFC2805 Media Gateway Control Protocol Architecture and Requirements 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. | April 2000 Status: INFORMATIONAL Autor: N. Greene, M. Ramalho, B. Rosen |
| RFC2806 URLs for Telephone Calls 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] | April 2000 Status: PROPOSED STANDARD Autor: A. Vaha-Sipila |
| RFC2807 XML Signature Requirements 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. | July 2000 Status: INFORMATIONAL Autor: J. Reagle |
| RFC2808 The SecurID(r) SASL Mechanism 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. | April 2000 Status: INFORMATIONAL Autor: M. Nystrom |
| RFC2809 Implementation of L2TP Compulsory Tunneling via RADIUS 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. | April 2000 Status: INFORMATIONAL Autor: B. Aboba, G. Zorn |
| RFC2810 Internet Relay Chat: Architecture 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. | April 2000 Status: INFORMATIONAL Autor: C. Kalt |
| RFC2811 Internet Relay Chat: Channel Management This document specifies how channels, their characteristics and properties are managed by IRC servers. This memo provides information for the Internet community. | April 2000 Status: INFORMATIONAL Autor: C. Kalt |
| RFC2812 Internet Relay Chat: Client Protocol 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. | April 2000 Status: INFORMATIONAL Autor: C. Kalt |
| RFC2813 Internet Relay Chat: Server Protocol This document defines the protocol used by servers to talk to each other. This memo provides information for the Internet community. | April 2000 Status: INFORMATIONAL Autor: C. Kalt |
| RFC2814 SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networks This document describes a signaling method and protocol for RSVP-based admission control over IEEE 802-style LANs. [STANDARDS-TRACK] | May 2000 Status: PROPOSED STANDARD Autor: R. Yavatkar, D. Hoffman, Y. Bernet, F. Baker, M. Speer |
| RFC2815 Integrated Service Mappings on IEEE 802 Networks 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] | May 2000 Status: PROPOSED STANDARD Autor: M. Seaman, A. Smith, E. Crawley, J. Wroclawski |
| RFC2816 A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies This memo describes a framework for supporting IETF Integrated Services on shared and switched LAN infrastructure. This memo provides information for the Internet community. | May 2000 Status: INFORMATIONAL Autor: A. Ghanwani, J. Pace, V. Srinivasan, A. Smith, M. Seaman |
| RFC2817 Upgrading to TLS Within HTTP/1.1 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] | May 2000 Status: PROPOSED STANDARD Autor: R. Khare, S. Lawrence |
| RFC2818 HTTP Over TLS 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. | May 2000 Status: INFORMATIONAL Autor: E. Rescorla |
| RFC2819 Remote Network Monitoring Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing remote network monitoring devices. [STANDARDS-TRACK] | May 2000 Status: STANDARD Autor: S. Waldbusser |
| RFC2820 Access Control Requirements for LDAP 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. | May 2000 Status: INFORMATIONAL Autor: E. Stokes, D. Byrne, B. Blakley, P. Behera |
| RFC2821 Simple Mail Transfer Protocol This document is a self-contained specification of the basic protocol for the Internet electronic mail transport. [STANDARDS-TRACK] | April 2001 Status: PROPOSED STANDARD Autor: J. Klensin |
| RFC2822 Internet Message Format This document specifies a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. [STANDARDS-TRACK] | April 2001 Status: PROPOSED STANDARD Autor: P. Resnick |
| RFC2823 PPP over Simple Data Link (SDL) using SONET/SDH with ATM-like framing 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. | May 2000 Status: EXPERIMENTAL Autor: J. Carlson, P. Langner, E. Hernandez-Valencia, J. Manchester |
| RFC2824 Call Processing Language Framework and Requirements 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. | May 2000 Status: INFORMATIONAL Autor: J. Lennox, H. Schulzrinne |
| RFC2825 A Tangled Web: Issues of I18N, Domain Names, and the Other Internet protocols 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. | May 2000 Status: INFORMATIONAL Autor: IAB, L. Daigle |
| RFC2826 IAB Technical Comment on the Unique DNS Root 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. | May 2000 Status: INFORMATIONAL Autor: Internet Architecture Board |
| RFC2827 Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing This paper discusses a simple, effective, and straightforward method for using ingress traffic filtering to prohibit DoS (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. | May 2000 Status: BEST CURRENT PRACTICE Autor: P. Ferguson, D. Senie |
| RFC2828 Internet Security Glossary This Glossary provides abbreviations, explanations, and recommendations for use of information system security terminology. This memo provides information for the Internet community. | May 2000 Status: INFORMATIONAL Autor: R. Shirey |
| RFC2829 Authentication Methods for LDAP This document specifies particular combinations of security mechanisms which are required and recommended in LDAP implementations. [STANDARDS-TRACK] | May 2000 Status: PROPOSED STANDARD Autor: M. Wahl, H. Alvestrand, J. Hodges, R. Morgan |
| RFC2830 Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security This document defines the "Start Transport Layer Security (TLS) Operation" for LDAP. [STANDARDS-TRACK] | May 2000 Status: PROPOSED STANDARD Autor: J. Hodges, R. Morgan, M. Wahl |
| RFC2831 Using Digest Authentication as a SASL Mechanism 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] | May 2000 Status: HISTORIC Autor: P. Leach, C. Newman |
| RFC2832 NSI Registry Registrar Protocol (RRP) Version 1.1.0 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. | May 2000 Status: INFORMATIONAL Autor: S. Hollenbeck, M. Srivastava |
| RFC2833 RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals This memo describes how to carry dual-tone multifrequency (DTMF) signaling, other tone signals and telephony events in RTP packets. [STANDARDS-TRACK] | May 2000 Status: PROPOSED STANDARD Autor: H. Schulzrinne, S. Petrack |
| RFC2834 ARP and IP Broadcast over HIPPI-800 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] | May 2000 Status: PROPOSED STANDARD Autor: J.-M. Pittet |
| RFC2835 IP and ARP over HIPPI-6400 (GSN) 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] | May 2000 Status: PROPOSED STANDARD Autor: J.-M. Pittet |
| RFC2836 Per Hop Behavior Identification Codes This document defines a binary encoding to uniquely identify PHBs (Per Hop Behaviors) and/or sets of PHBs in protocol messages. [STANDARDS-TRACK] | May 2000 Status: PROPOSED STANDARD Autor: S. Brim, B. Carpenter, F. Le Faucheur |
| RFC2837 Definitions of Managed Objects for the Fabric Element in Fibre Channel 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 the objects for managing the operations of the Fabric Element portion of the Fibre Channel Standards. [STANDARDS-TRACK] | May 2000 Status: PROPOSED STANDARD Autor: K. Teow |
| RFC2838 Uniform Resource Identifiers for Television Broadcasts 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. | May 2000 Status: INFORMATIONAL Autor: D. Zigmond, M. Vickers |
| RFC2839 Internet Kermit 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. | May 2000 Status: INFORMATIONAL Autor: F. da Cruz, J. Altman |
| RFC2840 TELNET KERMIT OPTION 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. | May 2000 Status: INFORMATIONAL Autor: J. Altman, F. da Cruz |
| RFC2841 IP Authentication using Keyed SHA1 with Interleaved Padding (IP-MAC) 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. | November 2000 Status: HISTORIC Autor: P. Metzger, W. Simpson |
| RFC2842 Capabilities Advertisement with BGP-4 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] | May 2000 Status: PROPOSED STANDARD Autor: R. Chandra, J. Scudder |
| RFC2843 Proxy-PAR The intention of this document is to provide general information about Proxy-PAR (PNNI Augmented Routing). [STANDARDS-TRACK] | May 2000 Status: INFORMATIONAL Autor: P. Droz, T. Przygienda |
| RFC2844 OSPF over ATM and Proxy-PAR 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. | May 2000 Status: EXPERIMENTAL Autor: T. Przygienda, P. Droz, R. Haas |
| RFC2845 Secret Key Transaction Authentication for DNS (TSIG) 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] | May 2000 Status: PROPOSED STANDARD Autor: P. Vixie, O. Gudmundsson, D. Eastlake 3rd, B. Wellington |
| RFC2846 GSTN Address Element Extensions in E-mail Services 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] | June 2000 Status: PROPOSED STANDARD Autor: C. Allocchio |
| RFC2847 LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKM 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] | June 2000 Status: PROPOSED STANDARD Autor: M. Eisler |
| RFC2848 The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services 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] | June 2000 Status: PROPOSED STANDARD Autor: S. Petrack, L. Conroy |
| RFC2849 The LDAP Data Interchange Format (LDIF) - Technical Specification This document describes a file format suitable for describing directory information or modifications made to directory information. [STANDARDS-TRACK] | June 2000 Status: PROPOSED STANDARD Autor: G. Good |
| RFC2850 Charter of the Internet Architecture Board (IAB) 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. | May 2000 Status: BEST CURRENT PRACTICE Autor: Internet Architecture Board, B. Carpenter |
| RFC2851 Textual Conventions for Internet Network Addresses This MIB module defines textual conventions to represent commonly used Internet network layer addressing information. [STANDARDS-TRACK] | June 2000 Status: PROPOSED STANDARD Autor: M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder |
| RFC2852 Deliver By SMTP Service Extension 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] | June 2000 Status: PROPOSED STANDARD Autor: D. Newman |
| RFC2853 Generic Security Service API Version 2 : Java Bindings 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] | June 2000 Status: PROPOSED STANDARD Autor: J. Kabat, M. Upadhyay |
| RFC2854 The 'text/html' Media Type 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. | June 2000 Status: INFORMATIONAL Autor: D. Connolly, L. Masinter |
| RFC2855 DHCP for IEEE 1394 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] | June 2000 Status: PROPOSED STANDARD Autor: K. Fujisawa |
| RFC2856 Textual Conventions for Additional High Capacity Data Types 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] | June 2000 Status: PROPOSED STANDARD Autor: A. Bierman, K. McCloghrie, R. Presuhn |
| RFC2857 The Use of HMAC-RIPEMD-160-96 within ESP and AH 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] | June 2000 Status: PROPOSED STANDARD Autor: A. Keromytis, N. Provos |
| RFC2858 Multiprotocol Extensions for BGP-4 This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). [STANDARDS-TRACK] | June 2000 Status: PROPOSED STANDARD Autor: T. Bates, Y. Rekhter, R. Chandra, D. Katz |
| RFC2859 A Time Sliding Window Three Colour Marker (TSWTCM) 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. | June 2000 Status: EXPERIMENTAL Autor: W. Fang, N. Seddigh, B. Nandy |
| RFC2860 Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority 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. | June 2000 Status: INFORMATIONAL Autor: B. Carpenter, F. Baker, M. Roberts |
| RFC2861 TCP Congestion Window Validation 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. | June 2000 Status: EXPERIMENTAL Autor: M. Handley, J. Padhye, S. Floyd |
| RFC2862 RTP Payload Format for Real-Time Pointers This document describes an RTP payload format for transporting the coordinates of a dynamic pointer that may be used during a presentation. [STANDARDS-TRACK] | June 2000 Status: PROPOSED STANDARD Autor: M. Civanlar, G. Cash |
| RFC2863 The Interfaces Group MIB 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] | June 2000 Status: DRAFT STANDARD Autor: K. McCloghrie, F. Kastenholz |
| RFC2864 The Inverted Stack Table Extension to the Interfaces Group 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 which provide an inverted mapping of the interface stack table used for managing network interfaces. [STANDARDS-TRACK] | June 2000 Status: PROPOSED STANDARD Autor: K. McCloghrie, G. Hanson |
| RFC2865 Remote Authentication Dial In User Service (RADIUS) This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK] | June 2000 Status: DRAFT STANDARD Autor: C. Rigney, S. Willens, A. Rubens, W. Simpson |
| RFC2866 RADIUS Accounting This document describes a protocol for carrying accounting information between a Network Access Server and a shared Accounting Server. This memo provides information for the Internet community. | June 2000 Status: INFORMATIONAL Autor: C. Rigney |
| RFC2867 RADIUS Accounting Modifications for Tunnel Protocol Support 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. | June 2000 Status: INFORMATIONAL Autor: G. Zorn, B. Aboba, D. Mitton |
| RFC2868 RADIUS Attributes for Tunnel Protocol Support 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. | June 2000 Status: INFORMATIONAL Autor: G. Zorn, D. Leifer, A. Rubens, J. Shriver, M. Holdrege, I. Goyret |
| RFC2869 RADIUS Extensions 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. | June 2000 Status: INFORMATIONAL Autor: C. Rigney, W. Willats, P. Calhoun |
| RFC2870 Root Name Server Operational Requirements 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. | June 2000 Status: BEST CURRENT PRACTICE Autor: R. Bush, D. Karrenberg, M. Kosters, R. Plzak |
| RFC2871 A Framework for Telephony Routing over IP 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. | June 2000 Status: INFORMATIONAL Autor: J. Rosenberg, H. Schulzrinne |
| RFC2872 Application and Sub Application Identity Policy Element for Use with RSVP 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] | June 2000 Status: PROPOSED STANDARD Autor: Y. Bernet, R. Pabbati |
| RFC2873 TCP Processing of the IPv4 Precedence Field 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] | June 2000 Status: PROPOSED STANDARD Autor: X. Xiao, A. Hannan, V. Paxson, E. Crabbe |
| RFC2874 DNS Extensions to Support IPv6 Address Aggregation and Renumbering This document defines changes to the Domain Name System to support renumberable and aggregatable IPv6 addressing. [STANDARDS-TRACK] | July 2000 Status: HISTORIC Autor: M. Crawford, C. Huitema |
| RFC2875 Diffie-Hellman Proof-of-Possession Algorithms This document describes two methods for producing an integrity check value from a Diffie-Hellman key pair. [STANDARDS-TRACK] | July 2000 Status: PROPOSED STANDARD Autor: H. Prafullchandra, J. Schaad |
| RFC2876 Use of the KEA and SKIPJACK Algorithms in CMS 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. | July 2000 Status: INFORMATIONAL Autor: J. Pawling |
| RFC2877 5250 Telnet Enhancements 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. | July 2000 Status: INFORMATIONAL Autor: T. Murphy Jr., P. Rieth, J. Stevens |
| RFC2878 PPP Bridging Control Protocol (BCP) This document defines the Network Control Protocol for establishing and configuring Remote Bridging for PPP links. [STANDARDS-TRACK] | July 2000 Status: PROPOSED STANDARD Autor: M. Higashiyama, F. Baker |
| RFC2879 Content Feature Schema for Internet Fax (V2) This document defines a content media feature schema for Internet fax. [STANDARDS-TRACK] | August 2000 Status: PROPOSED STANDARD Autor: G. Klyne, L. McIntyre |
| RFC2880 Internet Fax T.30 Feature Mapping 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. | August 2000 Status: INFORMATIONAL Autor: L. McIntyre, G. Klyne |
| RFC2881 Network Access Server Requirements Next Generation (NASREQNG) NAS Model This document describes the terminology and gives a model of typical Network Access Server (NAS). This memo provides information for the Internet community. | July 2000 Status: INFORMATIONAL Autor: D. Mitton, M. Beadles |
| RFC2882 Network Access Servers Requirements: Extended RADIUS Practices 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. | July 2000 Status: INFORMATIONAL Autor: D. Mitton |
| RFC2883 An Extension to the Selective Acknowledgement (SACK) Option for TCP This note defines an extension of the Selective Acknowledgement (SACK) Option for TCP. [STANDARDS-TRACK] | July 2000 Status: PROPOSED STANDARD Autor: S. Floyd, J. Mahdavi, M. Mathis, M. Podolsky |
| RFC2884 Performance Evaluation of Explicit Congestion Notification (ECN) in IP Networks 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. | July 2000 Status: INFORMATIONAL Autor: J. Hadi Salim, U. Ahmed |
| RFC2885 Megaco Protocol version 0.8 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] | August 2000 Status: HISTORIC Autor: F. Cuervo, N. Greene, C. Huitema, A. Rayhan, B. Rosen, J. Segers |
| RFC2886 Megaco Errata 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] | August 2000 Status: HISTORIC Autor: T. Taylor |
| RFC2887 The Reliable Multicast Design Space for Bulk Data Transfer 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. | August 2000 Status: INFORMATIONAL Autor: M. Handley, S. Floyd, B. Whetten, R. Kermode, L. Vicisano, M. Luby |
| RFC2888 Secure Remote Access with L2TP 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. | August 2000 Status: INFORMATIONAL Autor: P. Srisuresh |
| RFC2889 Benchmarking Methodology for LAN Switching Devices 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. | August 2000 Status: INFORMATIONAL Autor: R. Mandeville, J. Perser |
| RFC2890 Key and Sequence Number Extensions to GRE This document describes extensions by which two fields, Key and Sequence Number, can be optionally carried in the GRE Header. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: G. Dommety |
| RFC2891 LDAP Control Extension for Server Side Sorting of Search Results 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] | August 2000 Status: PROPOSED STANDARD Autor: T. Howes, M. Wahl, A. Anantha |
| RFC2892 The Cisco SRP MAC Layer Protocol 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. | August 2000 Status: INFORMATIONAL Autor: D. Tsiang, G. Suwala |
| RFC2893 Transition Mechanisms for IPv6 Hosts and Routers This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK] | August 2000 Status: PROPOSED STANDARD Autor: R. Gilligan, E. Nordmark |
| RFC2894 Router Renumbering for IPv6 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] | August 2000 Status: PROPOSED STANDARD Autor: M. Crawford |
| RFC2895 Remote Network Monitoring MIB Protocol Identifier Reference 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] | August 2000 Status: DRAFT STANDARD Autor: A. Bierman, C. Bucci, R. Iddon |
| RFC2896 Remote Network Monitoring MIB Protocol Identifier Macros 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. | August 2000 Status: INFORMATIONAL Autor: A. Bierman, C. Bucci, R. Iddon |
| RFC2897 Proposal for an MGCP Advanced Audio Package 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. | August 2000 Status: INFORMATIONAL Autor: D. Cromwell |
| RFC2898 PKCS #5: Password-Based Cryptography Specification Version 2.0 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. | September 2000 Status: INFORMATIONAL Autor: B. Kaliski |
| RFC2899 Request for Comments Summary RFC Numbers 2800-2899 | May 2001 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC2900 Internet Official Protocol Standards 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. | August 2001 Status: HISTORIC Autor: J. Reynolds, R. Braden, S. Ginoza |
| RFC2901 Guide to Administrative Procedures of the Internet Infrastructure This document describes the administrative procedures for networks seeking to connect to the global Internet. This memo provides information for the Internet community. | August 2000 Status: INFORMATIONAL Autor: Z. Wenzel, J. Klensin, R. Bush, S. Huter |
| RFC2902 Overview of the 1998 IAB Routing Workshop 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. | August 2000 Status: INFORMATIONAL Autor: S. Deering, S. Hares, C. Perkins, R. Perlman |
| RFC2903 Generic AAA Architecture 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. | August 2000 Status: EXPERIMENTAL Autor: C. de Laat, G. Gross, L. Gommans, J. Vollbrecht, D. Spence |
| RFC2904 AAA Authorization Framework 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. | August 2000 Status: INFORMATIONAL Autor: J. Vollbrecht, P. Calhoun, S. Farrell, L. Gommans, G. Gross, B. de Bruijn, C. de Laat, M. Holdrege, D. Spence |
| RFC2905 AAA Authorization Application Examples This memo describes several examples of applications requiring authorization. This memo provides information for the Internet community. | August 2000 Status: INFORMATIONAL Autor: J. Vollbrecht, P. Calhoun, S. Farrell, L. Gommans, G. Gross, B. de Bruijn, C. de Laat, M. Holdrege, D. Spence |
| RFC2906 AAA Authorization Requirements 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. | August 2000 Status: INFORMATIONAL Autor: S. Farrell, J. Vollbrecht, P. Calhoun, L. Gommans, G. Gross, B. de Bruijn, C. de Laat, M. Holdrege, D. Spence |
| RFC2907 MADCAP Multicast Scope Nesting State Option This document defines a new option to the Multicast Address Dynamic Client Allocation Protocol (MADCAP) to support nested scoping. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: R. Kermode |
| RFC2908 The Internet Multicast Address Allocation Architecture This document proposes a multicast address allocation architecture (MALLOC) for the Internet. This memo provides information for the Internet community. | September 2000 Status: HISTORIC Autor: D. Thaler, M. Handley, D. Estrin |
| RFC2909 The Multicast Address-Set Claim (MASC) Protocol 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. | September 2000 Status: HISTORIC Autor: P. Radoslavov, D. Estrin, R. Govindan, M. Handley, S. Kumar, D. Thaler |
| RFC2910 Internet Printing Protocol/1.1: Encoding and Transport This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: R. Herriot, S. Butler, P. Moore, R. Turner, J. Wenn |
| RFC2911 Internet Printing Protocol/1.1: Model and Semantics This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: T. Hastings, R. Herriot, R. deBry, S. Isaacson, P. Powell |
| RFC2912 Indicating Media Features for MIME Content 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] | September 2000 Status: PROPOSED STANDARD Autor: G. Klyne |
| RFC2913 MIME Content Types in Media Feature Expressions This memo defines a media feature tag whose value is a Multipurpose Internet Mail Extensions (MIME) content type. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: G. Klyne |
| RFC2914 Congestion Control Principles 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. | September 2000 Status: BEST CURRENT PRACTICE Autor: S. Floyd |
| RFC2915 The Naming Authority Pointer (NAPTR) DNS Resource Record 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] | September 2000 Status: PROPOSED STANDARD Autor: M. Mealling, R. Daniel |
| RFC2916 E.164 number and DNS This document discusses the use of the Domain Name System (DNS) for storage of E.164 numbers. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: P. Faltstrom |
| RFC2917 A Core MPLS IP VPN Architecture 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. | September 2000 Status: INFORMATIONAL Autor: K. Muthukrishnan, A. Malis |
| RFC2918 Route Refresh Capability for BGP-4 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] | September 2000 Status: PROPOSED STANDARD Autor: E. Chen |
| RFC2919 List-Id: A Structured Field and Namespace for the Identification of Mailing Lists 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] | March 2001 Status: PROPOSED STANDARD Autor: R. Chandhok, G. Wenger |
| RFC2920 SMTP Service Extension for Command Pipelining 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] | September 2000 Status: STANDARD Autor: N. Freed |
| RFC2921 6BONE pTLA and pNLA Formats (pTLA) 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. | September 2000 Status: INFORMATIONAL Autor: B. Fink |
| RFC2922 Physical Topology 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 physical topology identification and discovery. This memo provides information for the Internet community. | September 2000 Status: INFORMATIONAL Autor: A. Bierman, K. Jones |
| RFC2923 TCP Problems with Path MTU Discovery 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. | September 2000 Status: INFORMATIONAL Autor: K. Lahey |
| RFC2924 Accounting Attributes and Record Formats 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. | September 2000 Status: INFORMATIONAL Autor: N. Brownlee, A. Blount |
| RFC2925 Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations This memo defines Management Information Bases (MIBs) for performing remote ping, traceroute and lookup operations at a remote host. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: K. White |
| RFC2926 Conversion of LDAP Schemas to and from SLP Templates 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. | September 2000 Status: INFORMATIONAL Autor: J. Kempf, R. Moats, P. St. Pierre |
| RFC2927 MIME Directory Profile for LDAP Schema 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. | September 2000 Status: INFORMATIONAL Autor: M. Wahl |
| RFC2928 Initial IPv6 Sub-TLA ID Assignments 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. | September 2000 Status: INFORMATIONAL Autor: R. Hinden, S. Deering, R. Fink, T. Hain |
| RFC2929 Domain Name System (DNS) IANA Considerations 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. | September 2000 Status: BEST CURRENT PRACTICE Autor: D. Eastlake 3rd, E. Brunner-Williams, B. Manning |
| RFC2930 Secret Key Establishment for DNS (TKEY RR) 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] | September 2000 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC2931 DNS Request and Transaction Signatures ( SIG(0)s ) 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] | September 2000 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC2932 IPv4 Multicast Routing 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 IP Multicast Routing for IPv4, independent of the specific multicast routing protocol in use. [STANDARDS-TRACK] | October 2000 Status: PROPOSED STANDARD Autor: K. McCloghrie, D. Farinacci, D. Thaler |
| RFC2933 Internet Group 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 objects used for managing the Internet Group Management Protocol (IGMP). [STANDARDS-TRACK] | October 2000 Status: PROPOSED STANDARD Autor: K. McCloghrie, D. Farinacci, D. Thaler |
| RFC2934 Protocol Independent Multicast MIB for IPv4 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. | October 2000 Status: EXPERIMENTAL Autor: K. McCloghrie, D. Farinacci, D. Thaler, B. Fenner |
| RFC2935 Internet Open Trading Protocol (IOTP) HTTP Supplement 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] | September 2000 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd, C. Smith |
| RFC2936 HTTP MIME Type Handler Detection 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. | September 2000 Status: INFORMATIONAL Autor: D. Eastlake 3rd, C. Smith, D. Soroka |
| RFC2937 The Name Service Search Option for DHCP 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] | September 2000 Status: PROPOSED STANDARD Autor: C. Smith |
| RFC2938 Identifying Composite Media Features 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] | September 2000 Status: PROPOSED STANDARD Autor: G. Klyne, L. Masinter |
| RFC2939 Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types 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. | September 2000 Status: BEST CURRENT PRACTICE Autor: R. Droms |
| RFC2940 Definitions of Managed Objects for Common Open Policy Service (COPS) Protocol Clients 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] | October 2000 Status: PROPOSED STANDARD Autor: A. Smith, D. Partain, J. Seligson |
| RFC2941 Telnet Authentication Option 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] | September 2000 Status: PROPOSED STANDARD Autor: T. Ts'o, J. Altman |
| RFC2942 Telnet Authentication: Kerberos Version 5 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] | September 2000 Status: PROPOSED STANDARD Autor: T. Ts'o |
| RFC2943 TELNET Authentication Using DSA This document defines a telnet authentication mechanism using the Digital Signature Algorithm (DSA). It relies on the Telnet Authentication Option. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: R. Housley, T. Horting, P. Yee |
| RFC2944 Telnet Authentication: SRP 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] | September 2000 Status: PROPOSED STANDARD Autor: T. Wu |
| RFC2945 The SRP Authentication and Key Exchange System This document describes a cryptographically strong network authentication mechanism known as the Secure Remote Password (SRP) protocol. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: T. Wu |
| RFC2946 Telnet Data Encryption Option This document describes a the telnet encryption option as a generic method of providing data confidentiality services for the telnet data stream. [STANDARDS-TRACK] | September 2000 Status: PROPOSED STANDARD Autor: T. Ts'o |
| RFC2947 Telnet Encryption: DES3 64 bit Cipher Feedback 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] | September 2000 Status: PROPOSED STANDARD Autor: J. Altman |
| RFC2948 Telnet Encryption: DES3 64 bit Output Feedback 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] | September 2000 Status: PROPOSED STANDARD Autor: J. Altman |
| RFC2949 Telnet Encryption: CAST-128 64 bit Output Feedback 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] | September 2000 Status: PROPOSED STANDARD Autor: J. Altman |
| RFC2950 Telnet Encryption: CAST-128 64 bit Cipher Feedback 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] | September 2000 Status: PROPOSED STANDARD Autor: J. Altman |
| RFC2951 TELNET Authentication Using KEA and SKIPJACK 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. | September 2000 Status: INFORMATIONAL Autor: R. Housley, T. Horting, P. Yee |
| RFC2952 Telnet Encryption: DES 64 bit Cipher Feedback 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. | September 2000 Status: INFORMATIONAL Autor: T. Ts'o |
| RFC2953 Telnet Encryption: DES 64 bit Output Feedback 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. | September 2000 Status: INFORMATIONAL Autor: T. Ts'o |
| RFC2954 Definitions of Managed Objects for Frame Relay Service This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets. In particular, it defines objects for managing the frame relay service. [STANDARDS-TRACK] | October 2000 Status: PROPOSED STANDARD Autor: K. Rehbehn, D. Fowler |
| RFC2955 Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function 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] | October 2000 Status: PROPOSED STANDARD Autor: K. Rehbehn, O. Nicklass, G. Mouradian |
| RFC2956 Overview of 1999 IAB Network Layer Workshop 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. | October 2000 Status: INFORMATIONAL Autor: M. Kaat |
| RFC2957 The application/whoispp-query Content-Type 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. | October 2000 Status: INFORMATIONAL Autor: L. Daigle, P. Faltstrom |
| RFC2958 The application/whoispp-response Content-type 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. | October 2000 Status: INFORMATIONAL Autor: L. Daigle, P. Faltstrom |
| RFC2959 Real-Time Transport 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. [STANDARDS-TRACK] | October 2000 Status: PROPOSED STANDARD Autor: M. Baugher, B. Strahm, I. Suconick |
| RFC2960 Stream Control Transmission Protocol This document describes the Stream Control Transmission Protocol (SCTP). [STANDARDS-TRACK] | October 2000 Status: PROPOSED STANDARD Autor: R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. Paxson |
| RFC2961 RSVP Refresh Overhead Reduction Extensions 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] | April 2001 Status: PROPOSED STANDARD Autor: L. Berger, D. Gan, G. Swallow, P. Pan, F. Tommasi, S. Molendini |
| RFC2962 An SNMP Application Level Gateway for Payload Address Translation 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. | October 2000 Status: INFORMATIONAL Autor: D. Raz, J. Schoenwaelder, B. Sugla |
| RFC2963 A Rate Adaptive Shaper for Differentiated Services 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. | October 2000 Status: INFORMATIONAL Autor: O. Bonaventure, S. De Cnodder |
| RFC2964 Use of HTTP State Management 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. | October 2000 Status: BEST CURRENT PRACTICE Autor: K. Moore, N. Freed |
| RFC2965 HTTP State Management Mechanism This document specifies a way to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. [STANDARDS-TRACK] | October 2000 Status: HISTORIC Autor: D. Kristol, L. Montulli |
| RFC2966 Domain-wide Prefix Distribution with Two-Level IS-IS 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. | October 2000 Status: INFORMATIONAL Autor: T. Li, T. Przygienda, H. Smit |
| RFC2967 TISDAG - Technical Infrastructure for Swedish Directory Access Gateways 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. | October 2000 Status: INFORMATIONAL Autor: L. Daigle, R. Hedberg |
| RFC2968 Mesh of Multiple DAG servers - Results from TISDAG 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. | October 2000 Status: INFORMATIONAL Autor: L. Daigle, T. Eklof |
| RFC2969 Wide Area Directory Deployment - Experiences from TISDAG 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. | October 2000 Status: INFORMATIONAL Autor: T. Eklof, L. Daigle |
| RFC2970 Architecture for Integrated Directory Services - Result from TISDAG 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. | October 2000 Status: INFORMATIONAL Autor: L. Daigle, T. Eklof |
| RFC2971 IMAP4 ID extension 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] | October 2000 Status: PROPOSED STANDARD Autor: T. Showalter |
| RFC2972 Context and Goals for Common Name Resolution This document establishes the context and goals for a Common Name Resolution Protocol. This memo provides information for the Internet community. | October 2000 Status: INFORMATIONAL Autor: N. Popp, M. Mealling, L. Masinter, K. Sollins |
| RFC2973 IS-IS Mesh Groups 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. | October 2000 Status: INFORMATIONAL Autor: R. Balay, D. Katz, J. Parker |
| RFC2974 Session Announcement Protocol 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. | October 2000 Status: EXPERIMENTAL Autor: M. Handley, C. Perkins, E. Whelan |
| RFC2975 Introduction to Accounting Management 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. | October 2000 Status: INFORMATIONAL Autor: B. Aboba, J. Arkko, D. Harrington |
| RFC2976 The SIP INFO Method 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] | October 2000 Status: PROPOSED STANDARD Autor: S. Donovan |
| RFC2977 Mobile IP Authentication, Authorization, and Accounting Requirements 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. | October 2000 Status: INFORMATIONAL Autor: S. Glass, T. Hiller, S. Jacobs, C. Perkins |
| RFC2978 IANA Charset Registration Procedures 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. | October 2000 Status: BEST CURRENT PRACTICE Autor: N. Freed, J. Postel |
| RFC2979 Behavior of and Requirements for Internet Firewalls This memo defines behavioral characteristics of and interoperability requirements for Internet firewalls. This memo provides information for the Internet community. | October 2000 Status: INFORMATIONAL Autor: N. Freed |
| RFC2980 Common NNTP Extensions 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. | October 2000 Status: INFORMATIONAL Autor: S. Barber |
| RFC2981 Event 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 that can be used to manage and monitor MIB objects and take action through events. [STANDARDS-TRACK] | October 2000 Status: PROPOSED STANDARD Autor: R. Kavasseri |
| RFC2982 Distributed Management Expression 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 expressions of MIB objects. [STANDARDS-TRACK] | October 2000 Status: PROPOSED STANDARD Autor: R. Kavasseri |
| RFC2983 Differentiated Services and Tunnels This document considers the interaction of Differentiated Services (diffserv) with IP tunnels of various forms. This memo provides information for the Internet community. | October 2000 Status: INFORMATIONAL Autor: D. Black |
| RFC2984 Use of the CAST-128 Encryption Algorithm in CMS 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] | October 2000 Status: PROPOSED STANDARD Autor: C. Adams |
| RFC2985 PKCS #9: Selected Object Classes and Attribute Types Version 2.0 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. | November 2000 Status: INFORMATIONAL Autor: M. Nystrom, B. Kaliski |
| RFC2986 PKCS #10: Certification Request Syntax Specification Version 1.7 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. | November 2000 Status: INFORMATIONAL Autor: M. Nystrom, B. Kaliski |
| RFC2987 Registration of Charset and Languages Media Features Tags This document contains the registration for two media feature tags: "charset" and "language". [STANDARDS-TRACK] | November 2000 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC2988 Computing TCP's Retransmission Timer 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] | November 2000 Status: PROPOSED STANDARD Autor: V. Paxson, M. Allman |
| RFC2989 Criteria for Evaluating AAA Protocols for Network Access This document represents a summary of Authentication, Authorization, Accounting (AAA) protocol requirements for network access. This memo provides information for the Internet community. | November 2000 Status: INFORMATIONAL Autor: B. Aboba, P. Calhoun, S. Glass, T. Hiller, P. McCann, H. Shiino, P. Walsh, G. Zorn, G. Dommety, C. Perkins, B. Patil, D. Mitton, S. Manning, M. Beadles, X. Chen, S. Sivalingham, A. Hameed, M. Munson, S. Jacobs, B. Lim, B. Hirschman, R. Hsu, H. Koo, M. Lipford, E. Campbell, Y. Xu, S. Baba, E. Jaques |
| RFC2990 Next Steps for the IP QoS Architecture 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. | November 2000 Status: INFORMATIONAL Autor: G. Huston |
| RFC2991 Multipath Issues in Unicast and Multicast Next-Hop Selection 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. | November 2000 Status: INFORMATIONAL Autor: D. Thaler, C. Hopps |
| RFC2992 Analysis of an Equal-Cost Multi-Path Algorithm 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. | November 2000 Status: INFORMATIONAL Autor: C. Hopps |
| RFC2993 Architectural Implications of NAT 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. | November 2000 Status: INFORMATIONAL Autor: T. Hain |
| RFC2994 A Description of the MISTY1 Encryption Algorithm 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. | November 2000 Status: INFORMATIONAL Autor: H. Ohta, M. Matsui |
| RFC2995 Pre-Spirits Implementations of PSTN-initiated Services 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. | November 2000 Status: INFORMATIONAL Autor: H. Lu, I. Faynberg, J. Voelker, M. Weissman, W. Zhang, S. Rhim, J. Hwang, S. Ago, S. Moeenuddin, S. Hadvani, S. Nyckelgard, J. Yoakum, L. Robart |
| RFC2996 Format of the RSVP DCLASS Object This document specifies the format of the DCLASS object and briefly discusses its use. [STANDARDS-TRACK] | November 2000 Status: PROPOSED STANDARD Autor: Y. Bernet |
| RFC2997 Specification of the Null Service Type 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] | November 2000 Status: PROPOSED STANDARD Autor: Y. Bernet, A. Smith, B. Davie |
| RFC2998 A Framework for Integrated Services Operation over Diffserv Networks This document describes a framework by which Integrated Services may be supported over Diffserv networks. This memo provides information for the Internet community. | November 2000 Status: INFORMATIONAL Autor: Y. Bernet, P. Ford, R. Yavatkar, F. Baker, L. Zhang, M. Speer, R. Braden, B. Davie, J. Wroclawski, E. Felstaine |
| RFC2999 Request for Comments Summary RFC Numbers 2900-2999 | August 2001 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC3000 Internet Official Protocol Standards 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] | November 2001 Status: HISTORIC Autor: J. Reynolds, R. Braden, S. Ginoza, L. Shiota |
| RFC3001 A URN Namespace of Object Identifiers This document describes a Uniform Resource Names (URN) namespace that contains Object Identifiers (OIDs). This memo provides information for the Internet community. | November 2000 Status: INFORMATIONAL Autor: M. Mealling |
| RFC3002 Overview of 2000 IAB Wireless Internetworking Workshop 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. | December 2000 Status: INFORMATIONAL Autor: D. Mitzel |
| RFC3003 The audio/mpeg Media Type 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] | November 2000 Status: PROPOSED STANDARD Autor: M. Nilsson |
| RFC3004 The User Class Option for DHCP 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] | November 2000 Status: PROPOSED STANDARD Autor: G. Stump, R. Droms, Y. Gu, R. Vyaghrapuri, A. Demirtjis, B. Beser, J. Privat |
| RFC3005 IETF Discussion List Charter 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. | November 2000 Status: BEST CURRENT PRACTICE Autor: S. Harris |
| RFC3006 Integrated Services in the Presence of Compressible Flows 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] | November 2000 Status: PROPOSED STANDARD Autor: B. Davie, C. Iturralde, D. Oran, S. Casner, J. Wroclawski |
| RFC3007 Secure Domain Name System (DNS) Dynamic Update This document proposes a method for performing secure Domain Name System (DNS) dynamic updates. [STANDARDS-TRACK] | November 2000 Status: PROPOSED STANDARD Autor: B. Wellington |
| RFC3008 Domain Name System Security (DNSSEC) Signing Authority 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] | November 2000 Status: PROPOSED STANDARD Autor: B. Wellington |
| RFC3009 Registration of parityfec MIME types 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] | November 2000 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne |
| RFC3010 NFS version 4 Protocol NFS (Network File System) version 4 is a distributed file system protocol which owes heritage to NFS protocol versions 2 [STANDARDS-TRACK] | December 2000 Status: PROPOSED STANDARD Autor: S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, C. Beame, M. Eisler, D. Noveck |
| RFC3011 The IPv4 Subnet Selection Option for DHCP This memo defines a new Dynamic Host Configuration Protocol (DHCP) option for selecting the subnet on which to allocate an address. [STANDARDS-TRACK] | November 2000 Status: PROPOSED STANDARD Autor: G. Waters |
| RFC3012 Mobile IPv4 Challenge/Response Extensions 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] | November 2000 Status: PROPOSED STANDARD Autor: C. Perkins, P. Calhoun |
| RFC3013 Recommended Internet Service Provider Security Services and Procedures 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. | November 2000 Status: BEST CURRENT PRACTICE Autor: T. Killalea |
| RFC3014 Notification Log 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 logging Simple Network Management Protocol (SNMP) Notifications. [STANDARDS-TRACK] | November 2000 Status: PROPOSED STANDARD Autor: R. Kavasseri |
| RFC3015 Megaco Protocol Version 1.0 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] | November 2000 Status: PROPOSED STANDARD Autor: F. Cuervo, N. Greene, A. Rayhan, C. Huitema, B. Rosen, J. Segers |
| RFC3016 RTP Payload Format for MPEG-4 Audio/Visual Streams 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] | November 2000 Status: PROPOSED STANDARD Autor: Y. Kikuchi, T. Nomura, S. Fukunaga, Y. Matsui, H. Kimata |
| RFC3017 XML DTD for Roaming Access Phone Book 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] | December 2000 Status: PROPOSED STANDARD Autor: M. Riegel, G. Zorn |
| RFC3018 Unified Memory Space Protocol Specification 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. | December 2000 Status: EXPERIMENTAL Autor: A. Bogdanov |
| RFC3019 IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol 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 [STANDARDS-TRACK] | January 2001 Status: PROPOSED STANDARD Autor: B. Haberman, R. Worzella |
| RFC3020 Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function 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] | December 2000 Status: PROPOSED STANDARD Autor: P. Pate, B. Lynch, K. Rehbehn |
| RFC3021 Using 31-Bit Prefixes on IPv4 Point-to-Point Links 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] | December 2000 Status: PROPOSED STANDARD Autor: A. Retana, R. White, V. Fuller, D. McPherson |
| RFC3022 Traditional IP Network Address Translator (Traditional NAT) 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. | January 2001 Status: INFORMATIONAL Autor: P. Srisuresh, K. Egevang |
| RFC3023 XML Media Types 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] | January 2001 Status: PROPOSED STANDARD Autor: M. Murata, S. St. Laurent, D. Kohn |
| RFC3024 Reverse Tunneling for Mobile IP, revised 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] | January 2001 Status: PROPOSED STANDARD Autor: G. Montenegro |
| RFC3025 Mobile IP Vendor/Organization-Specific Extensions 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] | February 2001 Status: PROPOSED STANDARD Autor: G. Dommety, K. Leung |
| RFC3026 Liaison to IETF/ISOC on ENUM 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. | January 2001 Status: INFORMATIONAL Autor: R. Blane |
| RFC3027 Protocol Complications with the IP 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. | January 2001 Status: INFORMATIONAL Autor: M. Holdrege, P. Srisuresh |
| RFC3028 Sieve: A Mail Filtering Language This document describes a language for filtering e-mail messages at time of final delivery. [STANDARDS-TRACK] | January 2001 Status: PROPOSED STANDARD Autor: T. Showalter |
| RFC3029 Internet X.509 Public Key Infrastructure Data Validation and Certification Server Protocols 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. | February 2001 Status: EXPERIMENTAL Autor: C. Adams, P. Sylvester, M. Zolotarev, R. Zuccherato |
| RFC3030 SMTP Service Extensions for Transmission of Large and Binary MIME Messages This memo defines two extensions to the SMTP (Simple Mail Transfer Protocol) service. [STANDARDS-TRACK] | December 2000 Status: PROPOSED STANDARD Autor: G. Vaudreuil |
| RFC3031 Multiprotocol Label Switching Architecture This document specifies the architecture for Multiprotocol Label Switching (MPLS). [STANDARDS-TRACK] | January 2001 Status: PROPOSED STANDARD Autor: E. Rosen, A. Viswanathan, R. Callon |
| RFC3032 MPLS Label Stack Encoding 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] | January 2001 Status: PROPOSED STANDARD Autor: E. Rosen, D. Tappan, G. Fedorkow, Y. Rekhter, D. Farinacci, T. Li, A. Conta |
| 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 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] | January 2001 Status: PROPOSED STANDARD Autor: M. Suzuki |
| RFC3034 Use of Label Switching on Frame Relay Networks Specification This document defines the model and generic mechanisms for Multiprotocol Label Switching on Frame Relay networks. [STANDARDS-TRACK] | January 2001 Status: PROPOSED STANDARD Autor: A. Conta, P. Doolan, A. Malis |
| RFC3035 MPLS using LDP and ATM VC Switching 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] | January 2001 Status: PROPOSED STANDARD Autor: B. Davie, J. Lawrence, K. McCloghrie, E. Rosen, G. Swallow, Y. Rekhter, P. Doolan |
| RFC3036 LDP Specification 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] | January 2001 Status: PROPOSED STANDARD Autor: L. Andersson, P. Doolan, N. Feldman, A. Fredette, B. Thomas |
| RFC3037 LDP Applicability 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. | January 2001 Status: INFORMATIONAL Autor: B. Thomas, E. Gray |
| RFC3038 VCID Notification over ATM link for LDP 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] | January 2001 Status: PROPOSED STANDARD Autor: K. Nagami, Y. Katsube, N. Demizu, H. Esaki, P. Doolan |
| RFC3039 Internet X.509 Public Key Infrastructure Qualified Certificates Profile 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] | January 2001 Status: PROPOSED STANDARD Autor: S. Santesson, W. Polk, P. Barzin, M. Nystrom |
| RFC3040 Internet Web Replication and Caching Taxonomy 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. | January 2001 Status: INFORMATIONAL Autor: I. Cooper, I. Melve, G. Tomlinson |
| RFC3041 Privacy Extensions for Stateless Address Autoconfiguration in IPv6 This document describes an extension to IPv6 stateless address autoconfiguration for interfaces whose interface identifier is derived from an IEEE identifier. [STANDARDS-TRACK] | January 2001 Status: PROPOSED STANDARD Autor: T. Narten, R. Draves |
| RFC3042 Enhancing TCP's Loss Recovery Using Limited Transmit 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] | January 2001 Status: PROPOSED STANDARD Autor: M. Allman, H. Balakrishnan, S. Floyd |
| RFC3043 The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations 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. | January 2001 Status: INFORMATIONAL Autor: M. Mealling |
| RFC3044 Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace 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. | January 2001 Status: INFORMATIONAL Autor: S. Rozenfeld |
| RFC3045 Storing Vendor Information in the LDAP root DSE 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. | January 2001 Status: INFORMATIONAL Autor: M. Meredith |
| RFC3046 DHCP Relay Agent Information Option 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] | January 2001 Status: PROPOSED STANDARD Autor: M. Patrick |
| RFC3047 RTP Payload Format for ITU-T Recommendation G.722.1 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] | January 2001 Status: PROPOSED STANDARD Autor: P. Luthi |
| RFC3048 Reliable Multicast Transport Building Blocks for One-to-Many Bulk-Data Transfer This document describes a framework for the standardization of bulk-data reliable multicast transport. This memo provides information for the Internet community. | January 2001 Status: INFORMATIONAL Autor: B. Whetten, L. Vicisano, R. Kermode, M. Handley, S. Floyd, M. Luby |
| RFC3049 TN3270E Service Location and Session Balancing 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] | January 2001 Status: PROPOSED STANDARD Autor: J. Naugle, K. Kasthurirangan, G. Ledford |
| RFC3050 Common Gateway Interface for SIP This document defines a SIP CGI interface for providing SIP services on a SIP server. This memo provides information for the Internet community. | January 2001 Status: INFORMATIONAL Autor: J. Lennox, H. Schulzrinne, J. Rosenberg |
| RFC3051 IP Payload Compression Using ITU-T V.44 Packet Method 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. | January 2001 Status: INFORMATIONAL Autor: J. Heath, J. Border |
| RFC3052 Service Management Architectures Issues and Review 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. | January 2001 Status: INFORMATIONAL Autor: M. Eder, S. Nag |
| RFC3053 IPv6 Tunnel Broker 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. | January 2001 Status: INFORMATIONAL Autor: A. Durand, P. Fasano, I. Guardini, D. Lento |
| RFC3054 Megaco IP Phone Media Gateway Application Profile 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. | January 2001 Status: INFORMATIONAL Autor: P. Blatherwick, R. Bell, P. Holland |
| RFC3055 Management Information Base for the PINT Services Architecture This memo describes a proposed Management Information Base (MIB) for the PSTN/Internet Interworking (PINT) Services Architecture. [STANDARDS-TRACK] | February 2001 Status: PROPOSED STANDARD Autor: M. Krishnaswamy, D. Romascanu |
| RFC3056 Connection of IPv6 Domains via IPv4 Clouds 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] | February 2001 Status: PROPOSED STANDARD Autor: B. Carpenter, K. Moore |
| RFC3057 ISDN Q.921-User Adaptation Layer 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] | February 2001 Status: PROPOSED STANDARD Autor: K. Morneault, S. Rengasami, M. Kalla, G. Sidebottom |
| RFC3058 Use of the IDEA Encryption Algorithm in CMS 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. | February 2001 Status: INFORMATIONAL Autor: S. Teiwes, P. Hartmann, D. Kuenzi |
| RFC3059 Attribute List Extension for the Service Location Protocol 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] | February 2001 Status: PROPOSED STANDARD Autor: E. Guttman |
| RFC3060 Policy Core Information Model -- Version 1 Specification 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] | February 2001 Status: PROPOSED STANDARD Autor: B. Moore, E. Ellesson, J. Strassner, A. Westerinen |
| RFC3061 A URN Namespace of Object Identifiers This document describes a Uniform Resource Name (URN) namespace that contains Object Identifiers (OIDs). This memo provides information for the Internet community. | February 2001 Status: INFORMATIONAL Autor: M. Mealling |
| RFC3062 LDAP Password Modify Extended Operation 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] | February 2001 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3063 MPLS Loop Prevention Mechanism 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. | February 2001 Status: EXPERIMENTAL Autor: Y. Ohba, Y. Katsube, E. Rosen, P. Doolan |
| RFC3064 MGCP CAS Packages 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. | February 2001 Status: INFORMATIONAL Autor: B. Foster |
| RFC3065 Autonomous System Confederations for BGP 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] | February 2001 Status: PROPOSED STANDARD Autor: P. Traina, D. McPherson, J. Scudder |
| RFC3066 Tags for the Identification of Languages This document describes a language tag for use in cases where it is desired to indicate the language used in an information object, 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. | January 2001 Status: BEST CURRENT PRACTICE Autor: H. Alvestrand |
| RFC3067 TERENA'S Incident Object Description and Exchange Format Requirements 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. | February 2001 Status: INFORMATIONAL Autor: J. Arvidsson, A. Cormack, Y. Demchenko, J. Meijer |
| RFC3068 An Anycast Prefix for 6to4 Relay Routers 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] | June 2001 Status: PROPOSED STANDARD Autor: C. Huitema |
| RFC3069 VLAN Aggregation for Efficient IP Address Allocation 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. | February 2001 Status: INFORMATIONAL Autor: D. McPherson, B. Dykes |
| RFC3070 Layer Two Tunneling Protocol (L2TP) over Frame Relay This document describes how L2TP is implemented over Frame Relay Permanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs). [STANDARDS-TRACK] | February 2001 Status: PROPOSED STANDARD Autor: V. Rawat, R. Tio, S. Nanji, R. Verma |
| RFC3071 Reflections on the DNS, RFC 1591, and Categories of Domains 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. | February 2001 Status: INFORMATIONAL Autor: J. Klensin |
| RFC3072 Structured Data Exchange Format (SDXF) 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. | March 2001 Status: INFORMATIONAL Autor: M. Wildgrube |
| RFC3073 Portable Font Resource (PFR) - application/font-tdpfr MIME Sub-type Registration 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. | March 2001 Status: INFORMATIONAL Autor: J. Collins |
| RFC3074 DHC Load Balancing Algorithm This document proposes a method of algorithmic load balancing. [STANDARDS-TRACK] | February 2001 Status: PROPOSED STANDARD Autor: B. Volz, S. Gonczi, T. Lemon, R. Stevens |
| RFC3075 XML-Signature Syntax and Processing This document specifies XML (Extensible Markup Language) digital signature processing rules and syntax. [STANDARDS-TRACK] | March 2001 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd, J. Reagle, D. Solo |
| RFC3076 Canonical XML Version 1.0 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. | March 2001 Status: INFORMATIONAL Autor: J. Boyer |
| RFC3077 A Link-Layer Tunneling Mechanism for Unidirectional Links This document describes a mechanism to emulate full bidirectional connectivity between all nodes that are directly connected by a unidirectional link. [STANDARDS-TRACK] | March 2001 Status: PROPOSED STANDARD Autor: E. Duros, W. Dabbous, H. Izumiyama, N. Fujii, Y. Zhang |
| RFC3078 Microsoft Point-To-Point Encryption (MPPE) Protocol 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. | March 2001 Status: INFORMATIONAL Autor: G. Pall, G. Zorn |
| RFC3079 Deriving Keys for use with Microsoft Point-to-Point Encryption (MPPE) 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. | March 2001 Status: INFORMATIONAL Autor: G. Zorn |
| RFC3080 The Blocks Extensible Exchange Protocol Core This memo describes a generic application protocol kernel for connection-oriented, asynchronous interactions called the BEEP (Blocks Extensible Exchange Protocol) core. [STANDARDS-TRACK] | March 2001 Status: PROPOSED STANDARD Autor: M. Rose |
| RFC3081 Mapping the BEEP Core onto TCP This memo describes how a BEEP (Blocks Extensible Exchange Protocol) session is mapped onto a single TCP (Transmission Control Protocol) connection. [STANDARDS-TRACK] | March 2001 Status: PROPOSED STANDARD Autor: M. Rose |
| RFC3082 Notification and Subscription for SLP 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. | March 2001 Status: EXPERIMENTAL Autor: J. Kempf, J. Goldschmidt |
| RFC3083 Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems 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. | March 2001 Status: INFORMATIONAL Autor: R. Woundy |
| RFC3084 COPS Usage for Policy Provisioning (COPS-PR) This document describes the use of the Common Open Policy Service (COPS) protocol for support of policy provisioning (COPS-PR). [STANDARDS-TRACK] | March 2001 Status: PROPOSED STANDARD Autor: K. Chan, J. Seligson, D. Durham, S. Gai, K. McCloghrie, S. Herzog, F. Reichmeyer, R. Yavatkar, A. Smith |
| RFC3085 URN Namespace for NewsML Resources This document describes a URN (Uniform Resource Name) namespace for identifying NewsML NewsItems. This memo provides information for the Internet community. | March 2001 Status: INFORMATIONAL Autor: A. Coates, D. Allen, D. Rivers-Moore |
| RFC3086 Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification 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. | April 2001 Status: INFORMATIONAL Autor: K. Nichols, B. Carpenter |
| RFC3087 Control of Service Context using SIP Request-URI 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. | April 2001 Status: INFORMATIONAL Autor: B. Campbell, R. Sparks |
| RFC3088 OpenLDAP Root Service An experimental LDAP referral service 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. | April 2001 Status: EXPERIMENTAL Autor: K. Zeilenga |
| RFC3089 A SOCKS-based IPv6/IPv4 Gateway Mechanism 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. | April 2001 Status: INFORMATIONAL Autor: H. Kitamura |
| RFC3090 DNS Security Extension Clarification on Zone Status 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] | March 2001 Status: PROPOSED STANDARD Autor: E. Lewis |
| RFC3091 Pi Digit Generation Protocol 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. | April 2001 Status: INFORMATIONAL Autor: H. Kennedy |
| RFC3092 Etymology of "Foo" 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. | April 2001 Status: INFORMATIONAL Autor: D. Eastlake 3rd, C. Manros, E. Raymond |
| RFC3093 Firewall Enhancement Protocol (FEP) 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. | April 2001 Status: INFORMATIONAL Autor: M. Gaynor, S. Bradner |
| RFC3094 Tekelec's Transport Adapter Layer Interface 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. | April 2001 Status: INFORMATIONAL Autor: D. Sprague, R. Benedyk, D. Brendes, J. Keller |
| RFC3095 RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed 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] | July 2001 Status: PROPOSED STANDARD Autor: 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 |
| RFC3096 Requirements for robust IP/UDP/RTP header compression 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. | July 2001 Status: INFORMATIONAL Autor: M. Degermark |
| RFC3097 RSVP Cryptographic Authentication -- Updated Message Type Value 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] | April 2001 Status: PROPOSED STANDARD Autor: R. Braden, L. Zhang |
| RFC3098 How to Advertise Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE ENEMIES FAST! $$$$$ 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. | April 2001 Status: INFORMATIONAL Autor: T. Gavin, D. Eastlake 3rd, S. Hambridge |
| RFC3099 Request for Comments Summary RFC Numbers 3000-3099 | November 2001 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC3101 The OSPF Not-So-Stubby Area (NSSA) Option 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] | January 2003 Status: PROPOSED STANDARD Autor: P. Murphy |
| RFC3102 Realm Specific IP: Framework 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. | October 2001 Status: EXPERIMENTAL Autor: M. Borella, J. Lo, D. Grabelsky, G. Montenegro |
| RFC3103 Realm Specific IP: Protocol Specification 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. | October 2001 Status: EXPERIMENTAL Autor: M. Borella, D. Grabelsky, J. Lo, K. Taniguchi |
| RFC3104 RSIP Support for End-to-end IPsec 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. | October 2001 Status: EXPERIMENTAL Autor: G. Montenegro, M. Borella |
| RFC3105 Finding an RSIP Server with SLP 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. | October 2001 Status: EXPERIMENTAL Autor: J. Kempf, G. Montenegro |
| RFC3106 ECML v1.1: Field Specifications for E-Commerce 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. | April 2001 Status: INFORMATIONAL Autor: D. Eastlake 3rd, T. Goldstein |
| RFC3107 Carrying Label Information in BGP-4 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] | May 2001 Status: PROPOSED STANDARD Autor: Y. Rekhter, E. Rosen |
| RFC3108 Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections 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] | May 2001 Status: PROPOSED STANDARD Autor: R. Kumar, M. Mostafa |
| RFC3109 Request to Move STD 39 to Historic Status 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. | May 2001 Status: INFORMATIONAL Autor: R. Braden, R. Bush, J. Klensin |
| RFC3110 RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS) 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] | May 2001 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC3111 Service Location Protocol Modifications for IPv6 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] | May 2001 Status: PROPOSED STANDARD Autor: E. Guttman |
| RFC3112 LDAP Authentication Password Schema 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. | May 2001 Status: INFORMATIONAL Autor: K. Zeilenga |
| RFC3113 3GPP-IETF Standardization Collaboration This document describes the standardization collaboration between 3GPP and IETF. This memo provides information for the Internet community. | June 2001 Status: INFORMATIONAL Autor: K. Rosenbrock, R. Sanmugam, S. Bradner, J. Klensin |
| RFC3114 Implementing Company Classification Policy with the S/MIME Security Label 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. | May 2002 Status: INFORMATIONAL Autor: W. Nicolls |
| RFC3115 Mobile IP Vendor/Organization-Specific Extensions 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] | April 2001 Status: PROPOSED STANDARD Autor: G. Dommety, K. Leung |
| RFC3116 Methodology for ATM Benchmarking 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. | June 2001 Status: INFORMATIONAL Autor: J. Dunn, C. Martin |
| RFC3117 On the Design of Application Protocols This memo describes the design principles for the Blocks eXtensible eXchange Protocol (BXXP). This memo provides information for the Internet community. | November 2001 Status: INFORMATIONAL Autor: M. Rose |
| RFC3118 Authentication for DHCP Messages 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] | June 2001 Status: PROPOSED STANDARD Autor: R. Droms, W. Arbaugh |
| RFC3119 A More Loss-Tolerant RTP Payload Format for MP3 Audio 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] | June 2001 Status: PROPOSED STANDARD Autor: R. Finlayson |
| RFC3120 A URN Namespace for XML.org 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. | June 2001 Status: INFORMATIONAL Autor: K. Best, N. Walsh |
| RFC3121 A URN Namespace for OASIS 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. | June 2001 Status: INFORMATIONAL Autor: K. Best, N. Walsh |
| RFC3122 Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification 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] | June 2001 Status: PROPOSED STANDARD Autor: A. Conta |
| RFC3123 A DNS RR Type for Lists of Address Prefixes (APL RR) 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. | June 2001 Status: EXPERIMENTAL Autor: P. Koch |
| RFC3124 The Congestion Manager 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] | June 2001 Status: PROPOSED STANDARD Autor: H. Balakrishnan, S. Seshan |
| RFC3125 Electronic Signature Policies 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. | September 2001 Status: EXPERIMENTAL Autor: J. Ross, D. Pinkas, N. Pope |
| RFC3126 Electronic Signature Formats for long term electronic signatures 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. | September 2001 Status: INFORMATIONAL Autor: D. Pinkas, J. Ross, N. Pope |
| RFC3127 Authentication, Authorization, and Accounting: Protocol Evaluation 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. | June 2001 Status: INFORMATIONAL Autor: D. Mitton, M. St.Johns, S. Barkley, D. Nelson, B. Patil, M. Stevens, B. Wolff |
| RFC3128 Protection Against a Variant of the Tiny Fragment Attack (RFC 1858) 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. | June 2001 Status: INFORMATIONAL Autor: I. Miller |
| RFC3129 Requirements for Kerberized Internet Negotiation of Keys 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. | June 2001 Status: INFORMATIONAL Autor: M. Thomas |
| RFC3130 Notes from the State-Of-The-Technology: DNSSEC This is a memo of a DNSSEC (Domain Name System Security Extensions) status meeting. This memo provides information for the Internet community. | June 2001 Status: INFORMATIONAL Autor: E. Lewis |
| RFC3131 3GPP2-IETF Standardization Collaboration This document describes the standardization collaboration between 3GPP2 and IETF. This memo provides information for the Internet community. | June 2001 Status: INFORMATIONAL Autor: S. Bradner, P. Calhoun, H. Cuschieri, S. Dennett, G. Flynn, M. Lipford, M. McPheters |
| RFC3132 Dormant Mode Host Alerting ("IP Paging") Problem Statement 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. | June 2001 Status: INFORMATIONAL Autor: J. Kempf |
| RFC3133 Terminology for Frame Relay Benchmarking 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. | June 2001 Status: INFORMATIONAL Autor: J. Dunn, C. Martin |
| RFC3134 Terminology for ATM ABR Benchmarking 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. | June 2001 Status: INFORMATIONAL Autor: J. Dunn, C. Martin |
| RFC3135 Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations 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. | June 2001 Status: INFORMATIONAL Autor: J. Border, M. Kojo, J. Griner, G. Montenegro, Z. Shelby |
| RFC3136 The SPIRITS Architecture 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. | June 2001 Status: INFORMATIONAL Autor: L. Slutsman, I. Faynberg, H. Lu, M. Weissman |
| RFC3137 OSPF Stub Router Advertisement 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. | June 2001 Status: INFORMATIONAL Autor: A. Retana, L. Nguyen, R. White, A. Zinin, D. McPherson |
| RFC3138 Extended Assignments in 233/8 This memo provides describes the mapping of the GLOP addresses corresponding to the private AS space. This memo provides information for the Internet community. | June 2001 Status: INFORMATIONAL Autor: D. Meyer |
| RFC3139 Requirements for Configuration Management of IP-based Networks 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. | June 2001 Status: INFORMATIONAL Autor: L. Sanchez, K. McCloghrie, J. Saperia |
| RFC3140 Per Hop Behavior Identification Codes 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] | June 2001 Status: PROPOSED STANDARD Autor: D. Black, S. Brim, B. Carpenter, F. Le Faucheur |
| RFC3141 CDMA2000 Wireless Data Requirements for AAA 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. | June 2001 Status: INFORMATIONAL Autor: 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 |
| RFC3142 An IPv6-to-IPv4 Transport Relay Translator The document describes an IPv6-to-IPv4 transport relay translator (TRT). This memo provides information for the Internet community. | June 2001 Status: INFORMATIONAL Autor: J. Hagino, K. Yamamoto |
| RFC3143 Known HTTP Proxy/Caching Problems 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. | June 2001 Status: INFORMATIONAL Autor: I. Cooper, J. Dilley |
| RFC3144 Remote Monitoring MIB Extensions for Interface Parameters Monitoring 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] | August 2001 Status: PROPOSED STANDARD Autor: D. Romascanu |
| RFC3145 L2TP Disconnect Cause Information This document provides an extension to the Layer 2 Tunneling Protocol ("L2TP"), a mechanism for tunneling Point-to-Point Protocol (PPP) sessions. [STANDARDS-TRACK] | July 2001 Status: PROPOSED STANDARD Autor: R. Verma, M. Verma, J. Carlson |
| RFC3146 Transmission of IPv6 Packets over IEEE 1394 Networks 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] | October 2001 Status: PROPOSED STANDARD Autor: K. Fujisawa, A. Onoe |
| RFC3147 Generic Routing Encapsulation over CLNS Networks 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. | July 2001 Status: INFORMATIONAL Autor: P. Christian |
| RFC3148 A Framework for Defining Empirical Bulk Transfer Capacity Metrics 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. | July 2001 Status: INFORMATIONAL Autor: M. Mathis, M. Allman |
| RFC3149 MGCP Business Phone 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. | September 2001 Status: INFORMATIONAL Autor: A. Srinath, G. Levendel, K. Fritz, R. Kalyanaram |
| RFC3150 End-to-end Performance Implications of Slow Links 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. | July 2001 Status: BEST CURRENT PRACTICE Autor: S. Dawkins, G. Montenegro, M. Kojo, V. Magret |
| RFC3151 A URN Namespace for Public Identifiers 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. | August 2001 Status: INFORMATIONAL Autor: N. Walsh, J. Cowan, P. Grosso |
| RFC3152 Delegation of IP6.ARPA 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. | August 2001 Status: BEST CURRENT PRACTICE Autor: R. Bush |
| RFC3153 PPP Multiplexing 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] | August 2001 Status: PROPOSED STANDARD Autor: R. Pazhyannur, I. Ali, C. Fox |
| RFC3154 Requirements and Functional Architecture for an IP Host Alerting Protocol 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. | August 2001 Status: INFORMATIONAL Autor: J. Kempf, C. Castelluccia, P. Mutaf, N. Nakajima, Y. Ohba, R. Ramjee, Y. Saifullah, B. Sarikaya, X. Xu |
| RFC3155 End-to-end Performance Implications of Links with Errors 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. | August 2001 Status: BEST CURRENT PRACTICE Autor: S. Dawkins, G. Montenegro, M. Kojo, V. Magret, N. Vaidya |
| RFC3156 MIME Security with OpenPGP 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] | August 2001 Status: PROPOSED STANDARD Autor: M. Elkins, D. Del Torto, R. Levien, T. Roessler |
| RFC3157 Securely Available Credentials - Requirements This document describes requirements to be placed on Securely Available Credentials (SACRED) protocols. This memo provides information for the Internet community. | August 2001 Status: INFORMATIONAL Autor: A. Arsenault, S. Farrell |
| RFC3158 RTP Testing Strategies This memo describes a possible testing strategy for RTP (real-time transport protocol) implementations. This memo provides information for the Internet community. | August 2001 Status: INFORMATIONAL Autor: C. Perkins, J. Rosenberg, H. Schulzrinne |
| RFC3159 Structure of Policy Provisioning Information (SPPI) 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] | August 2001 Status: PROPOSED STANDARD Autor: K. McCloghrie, M. Fine, J. Seligson, K. Chan, S. Hahn, R. Sahita, A. Smith, F. Reichmeyer |
| RFC3160 The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force 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. | August 2001 Status: INFORMATIONAL Autor: S. Harris |
| RFC3161 Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) 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] | August 2001 Status: PROPOSED STANDARD Autor: C. Adams, P. Cain, D. Pinkas, R. Zuccherato |
| RFC3162 RADIUS and IPv6 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] | August 2001 Status: PROPOSED STANDARD Autor: B. Aboba, G. Zorn, D. Mitton |
| RFC3163 ISO/IEC 9798-3 Authentication SASL Mechanism 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. | August 2001 Status: EXPERIMENTAL Autor: R. Zuccherato, M. Nystrom |
| RFC3164 The BSD Syslog Protocol This document describes the observed behavior of the syslog protocol. This memo provides information for the Internet community. | August 2001 Status: INFORMATIONAL Autor: C. Lonvick |
| RFC3165 Definitions of Managed Objects for the Delegation of Management Scripts 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] | August 2001 Status: PROPOSED STANDARD Autor: D. Levi, J. Schoenwaelder |
| RFC3166 Request to Move RFC 1403 to Historic Status 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. | August 2001 Status: INFORMATIONAL Autor: D. Meyer, J. Scudder |
| RFC3167 Request to Move RFC 1745 to Historic Status 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. | August 2001 Status: INFORMATIONAL Autor: D. Meyer, J. Scudder |
| RFC3168 The Addition of Explicit Congestion Notification (ECN) to IP 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] | September 2001 Status: PROPOSED STANDARD Autor: K. Ramakrishnan, S. Floyd, D. Black |
| RFC3169 Criteria for Evaluating Network Access Server Protocols This document defines requirements for protocols used by Network Access Servers (NAS). This memo provides information for the Internet community. | September 2001 Status: INFORMATIONAL Autor: M. Beadles, D. Mitton |
| RFC3170 IP Multicast Applications: Challenges and Solutions 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. | September 2001 Status: INFORMATIONAL Autor: B. Quinn, K. Almeroth |
| RFC3171 IANA Guidelines for IPv4 Multicast Address Assignments 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. | August 2001 Status: BEST CURRENT PRACTICE Autor: Z. Albanna, K. Almeroth, D. Meyer, M. Schipper |
| RFC3172 Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa") 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. | September 2001 Status: BEST CURRENT PRACTICE Autor: G. Huston |
| RFC3173 IP Payload Compression Protocol (IPComp) This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK] | September 2001 Status: PROPOSED STANDARD Autor: A. Shacham, B. Monsour, R. Pereira, M. Thomas |
| RFC3174 US Secure Hash Algorithm 1 (SHA1) 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. | September 2001 Status: INFORMATIONAL Autor: D. Eastlake 3rd, P. Jones |
| RFC3175 Aggregation of RSVP for IPv4 and IPv6 Reservations 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] | September 2001 Status: PROPOSED STANDARD Autor: F. Baker, C. Iturralde, F. Le Faucheur, B. Davie |
| RFC3176 InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks 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. | September 2001 Status: INFORMATIONAL Autor: P. Phaal, S. Panchen, N. McKee |
| RFC3177 IAB/IESG Recommendations on IPv6 Address Allocations to Sites 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. | September 2001 Status: INFORMATIONAL Autor: IAB, IESG |
| RFC3178 IPv6 Multihoming Support at Site Exit Routers The document describes a mechanism for basic IPv6 multihoming support, and its operational requirements. This memo provides information for the Internet community. | October 2001 Status: INFORMATIONAL Autor: J. Hagino, H. Snyder |
| RFC3179 Script MIB Extensibility Protocol Version 1.1 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. | October 2001 Status: EXPERIMENTAL Autor: J. Schoenwaelder, J. Quittek |
| RFC3180 GLOP Addressing in 233/8 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. | September 2001 Status: BEST CURRENT PRACTICE Autor: D. Meyer, P. Lothberg |
| RFC3181 Signaled Preemption Priority Policy Element 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] | October 2001 Status: PROPOSED STANDARD Autor: S. Herzog |
| RFC3182 Identity Representation for RSVP 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] | October 2001 Status: PROPOSED STANDARD Autor: S. Yadav, R. Yavatkar, R. Pabbati, P. Ford, T. Moore, S. Herzog, R. Hess |
| RFC3183 Domain Security Services using S/MIME 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. | October 2001 Status: EXPERIMENTAL Autor: T. Dean, W. Ottaway |
| RFC3184 IETF Guidelines for Conduct 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. | October 2001 Status: BEST CURRENT PRACTICE Autor: S. Harris |
| RFC3185 Reuse of CMS Content Encryption Keys 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] | October 2001 Status: PROPOSED STANDARD Autor: S. Farrell, S. Turner |
| RFC3186 MAPOS/PPP Tunneling mode 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. | December 2001 Status: INFORMATIONAL Autor: S. Shimizu, T. Kawano, K. Murakami, E. Beier |
| RFC3187 Using International Standard Book Numbers as Uniform Resource Names 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. | October 2001 Status: INFORMATIONAL Autor: J. Hakala, H. Walravens |
| RFC3188 Using National Bibliography Numbers as Uniform Resource Names 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. | October 2001 Status: INFORMATIONAL Autor: J. Hakala |
| RFC3189 RTP Payload Format for DV (IEC 61834) Video 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] | January 2002 Status: PROPOSED STANDARD Autor: K. Kobayashi, A. Ogawa, S. Casner, C. Bormann |
| RFC3190 RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio 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] | January 2002 Status: PROPOSED STANDARD Autor: K. Kobayashi, A. Ogawa, S. Casner, C. Bormann |
| RFC3191 Minimal GSTN address format in Internet Mail 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] | October 2001 Status: DRAFT STANDARD Autor: C. Allocchio |
| RFC3192 Minimal FAX address format in Internet Mail 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] | October 2001 Status: DRAFT STANDARD Autor: C. Allocchio |
| RFC3193 Securing L2TP using IPsec 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] | November 2001 Status: PROPOSED STANDARD Autor: B. Patel, B. Aboba, W. Dixon, G. Zorn, S. Booth |
| RFC3194 The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio 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. | November 2001 Status: INFORMATIONAL Autor: A. Durand, C. Huitema |
| RFC3195 Reliable Delivery for syslog 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] | November 2001 Status: PROPOSED STANDARD Autor: D. New, M. Rose |
| RFC3196 Internet Printing Protocol/1.1: Implementor's Guide 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. | November 2001 Status: INFORMATIONAL Autor: T. Hastings, C. Manros, P. Zehler, C. Kugler, H. Holst |
| RFC3197 Applicability Statement for DNS MIB Extensions 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. | November 2001 Status: INFORMATIONAL Autor: R. Austein |
| RFC3198 Terminology for Policy-Based Management 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. | November 2001 Status: INFORMATIONAL Autor: A. Westerinen, J. Schnizlein, J. Strassner, M. Scherling, B. Quinn, S. Herzog, A. Huynh, M. Carlson, J. Perry, S. Waldbusser |
| RFC3199 Request for Comments Summary RFC Numbers 3100-3199 | February 2003 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC3201 Definitions of Managed Objects for Circuit to Interface Translation 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] | January 2002 Status: PROPOSED STANDARD Autor: R. Steinberger, O. Nicklass |
| RFC3202 Definitions of Managed Objects for Frame Relay Service Level Definitions 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] | January 2002 Status: PROPOSED STANDARD Autor: R. Steinberger, O. Nicklass |
| RFC3203 DHCP reconfigure extension 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] | December 2001 Status: PROPOSED STANDARD Autor: Y. T'Joens, C. Hublet, P. De Schrijver |
| RFC3204 MIME media types for ISUP and QSIG Objects 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] | December 2001 Status: PROPOSED STANDARD Autor: E. Zimmerer, J. Peterson, A. Vemuri, L. Ong, F. Audet, M. Watson, M. Zonoun |
| RFC3205 On the use of HTTP as a Substrate 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. | February 2002 Status: BEST CURRENT PRACTICE Autor: K. Moore |
| RFC3206 The SYS and AUTH POP Response Codes 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] | February 2002 Status: PROPOSED STANDARD Autor: R. Gellens |
| RFC3207 SMTP Service Extension for Secure SMTP over Transport Layer Security 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] | February 2002 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC3208 PGM Reliable Transport Protocol Specification 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. | December 2001 Status: EXPERIMENTAL Autor: 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 |
| RFC3209 RSVP-TE: Extensions to RSVP for LSP Tunnels 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] | December 2001 Status: PROPOSED STANDARD Autor: D. Awduche, L. Berger, D. Gan, T. Li, V. Srinivasan, G. Swallow |
| RFC3210 Applicability Statement for Extensions to RSVP for LSP-Tunnels 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. | December 2001 Status: INFORMATIONAL Autor: D. Awduche, A. Hannan, X. Xiao |
| RFC3211 Password-based Encryption for CMS 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] | December 2001 Status: PROPOSED STANDARD Autor: P. Gutmann |
| RFC3212 Constraint-Based LSP Setup using LDP 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] | January 2002 Status: PROPOSED STANDARD Autor: B. Jamoussi, 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 |
| RFC3213 Applicability Statement for CR-LDP 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. | January 2002 Status: INFORMATIONAL Autor: J. Ash, M. Girish, E. Gray, B. Jamoussi, G. Wright |
| RFC3214 LSP Modification Using CR-LDP 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] | January 2002 Status: PROPOSED STANDARD Autor: J. Ash, Y. Lee, P. Ashwood-Smith, B. Jamoussi, D. Fedyk, D. Skalecki, L. Li |
| RFC3215 LDP State Machine 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. | January 2002 Status: INFORMATIONAL Autor: C. Boscher, P. Cheval, L. Wu, E. Gray |
| RFC3216 SMIng Objectives 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. | December 2001 Status: INFORMATIONAL Autor: C. Elliott, D. Harrington, J. Jason, J. Schoenwaelder, F. Strauss, W. Weiss |
| RFC3217 Triple-DES and RC2 Key Wrapping 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. | December 2001 Status: INFORMATIONAL Autor: R. Housley |
| RFC3218 Preventing the Million Message Attack on Cryptographic Message Syntax This memo describes a strategy for resisting the Million Message Attack. This memo provides information for the Internet community. | January 2002 Status: INFORMATIONAL Autor: E. Rescorla |
| RFC3219 Telephony Routing over IP (TRIP) 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] | January 2002 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Salama, M. Squire |
| RFC3220 IP Mobility Support for IPv4 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] | January 2002 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC3221 Commentary on Inter-Domain Routing in the Internet 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. | December 2001 Status: INFORMATIONAL Autor: G. Huston |
| RFC3222 Terminology for Forwarding Information Base (FIB) based Router Performance 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. | December 2001 Status: INFORMATIONAL Autor: G. Trotter |
| RFC3224 Vendor Extensions for Service Location Protocol, Version 2 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] | January 2002 Status: PROPOSED STANDARD Autor: E. Guttman |
| RFC3225 Indicating Resolver Support of DNSSEC 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] | December 2001 Status: PROPOSED STANDARD Autor: D. Conrad |
| RFC3226 DNSSEC and IPv6 A6 aware server/resolver message size requirements 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] | December 2001 Status: PROPOSED STANDARD Autor: O. Gudmundsson |
| RFC3227 Guidelines for Evidence Collection and Archiving 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. | February 2002 Status: BEST CURRENT PRACTICE Autor: D. Brezinski, T. Killalea |
| RFC3228 IANA Considerations for IPv4 Internet Group Management Protocol (IGMP) 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. | February 2002 Status: BEST CURRENT PRACTICE Autor: B. Fenner |
| RFC3229 Delta encoding in HTTP This document describes how delta encoding can be supported as a compatible extension to HTTP/1.1. [STANDARDS-TRACK] | January 2002 Status: PROPOSED STANDARD Autor: J. Mogul, B. Krishnamurthy, F. Douglis, A. Feldmann, Y. Goland, A. van Hoff, D. Hellerstein |
| RFC3230 Instance Digests in HTTP 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] | January 2002 Status: PROPOSED STANDARD Autor: J. Mogul, A. Van Hoff |
| RFC3231 Definitions of Managed Objects for Scheduling Management Operations 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] | January 2002 Status: PROPOSED STANDARD Autor: D. Levi, J. Schoenwaelder |
| RFC3232 Assigned Numbers: RFC 1700 is Replaced by an On-line Database 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. | January 2002 Status: INFORMATIONAL Autor: J. Reynolds |
| RFC3233 Defining the IETF 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. | February 2002 Status: BEST CURRENT PRACTICE Autor: P. Hoffman, S. Bradner |
| RFC3234 Middleboxes: Taxonomy and Issues 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. | February 2002 Status: INFORMATIONAL Autor: B. Carpenter, S. Brim |
| RFC3235 Network Address Translator (NAT)-Friendly Application Design Guidelines 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. | January 2002 Status: INFORMATIONAL Autor: D. Senie |
| RFC3236 The 'application/xhtml+xml' Media Type 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. | January 2002 Status: INFORMATIONAL Autor: M. Baker, P. Stark |
| RFC3237 Requirements for Reliable Server Pooling This document defines a basic set of requirements for reliable server pooling. This memo provides information for the Internet community. | January 2002 Status: INFORMATIONAL Autor: M. Tuexen, Q. Xie, R. Stewart, M. Shore, L. Ong, J. Loughney, M. Stillman |
| RFC3238 IAB Architectural and Policy Considerations for Open Pluggable Edge Services 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. | January 2002 Status: INFORMATIONAL Autor: S. Floyd, L. Daigle |
| RFC3239 Internet Printing Protocol (IPP): Requirements for Job, Printer, and Device Administrative Operations 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. | February 2002 Status: INFORMATIONAL Autor: C. Kugler, H. Lewis, T. Hastings |
| RFC3240 Digital Imaging and Communications in Medicine (DICOM) - Application/dicom MIME Sub-type Registration 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. | February 2002 Status: INFORMATIONAL Autor: D. Clunie, E. Cordonnier |
| RFC3241 Robust Header Compression (ROHC) over PPP 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] | April 2002 Status: PROPOSED STANDARD Autor: C. Bormann |
| RFC3242 RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP 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] | April 2002 Status: PROPOSED STANDARD Autor: L-E. Jonsson, G. Pelletier |
| RFC3243 RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression 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. | April 2002 Status: INFORMATIONAL Autor: L-E. Jonsson |
| RFC3244 Microsoft Windows 2000 Kerberos Change Password and Set Password Protocols 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. | February 2002 Status: INFORMATIONAL Autor: M. Swift, J. Trostle, J. Brezak |
| RFC3245 The History and Context of Telephone Number Mapping (ENUM) Operational Decisions: Informational Documents Contributed to ITU-T Study Group 2 (SG2) 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. | March 2002 Status: INFORMATIONAL Autor: J. Klensin, IAB |
| RFC3246 An Expedited Forwarding PHB (Per-Hop Behavior) 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] | March 2002 Status: PROPOSED STANDARD Autor: B. Davie, A. Charny, J.C.R. Bennet, K. Benson, J.Y. Le Boudec, W. Courtney, S. Davari, V. Firoiu, D. Stiliadis |
| RFC3247 Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior) 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. | March 2002 Status: INFORMATIONAL Autor: A. Charny, J. Bennet, K. Benson, J. Boudec, A. Chiu, W. Courtney, S. Davari, V. Firoiu, C. Kalmanek, K. Ramakrishnan |
| RFC3248 A Delay Bound alternative revision of RFC 2598 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. | March 2002 Status: INFORMATIONAL Autor: G. Armitage, B. Carpenter, A. Casati, J. Crowcroft, J. Halpern, B. Kumar, J. Schnizlein |
| RFC3249 Implementers Guide for Facsimile Using Internet Mail 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. | September 2002 Status: INFORMATIONAL Autor: V. Cancio, M. Moldovan, H. Tamura, D. Wing |
| RFC3250 Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration 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] | September 2002 Status: PROPOSED STANDARD Autor: L. McIntyre, G. Parsons, J. Rafferty |
| RFC3251 Electricity over IP 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. | April 2002 Status: INFORMATIONAL Autor: B. Rajagopalan |
| RFC3252 Binary Lexical Octet Ad-hoc Transport 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. | April 2002 Status: INFORMATIONAL Autor: H. Kennedy |
| RFC3253 Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning) 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] | March 2002 Status: PROPOSED STANDARD Autor: G. Clemm, J. Amsden, T. Ellison, C. Kaler, J. Whitehead |
| RFC3254 Definitions for talking about directories 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. | April 2002 Status: INFORMATIONAL Autor: H. Alvestrand |
| 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 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] | April 2002 Status: PROPOSED STANDARD Autor: N. Jones, C. Murton |
| RFC3256 The DOCSIS (Data-Over-Cable Service Interface Specifications) Device Class DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Sub-option This document proposes a new sub-option to the DHCP (Dynamic Host Configuration Protocol) Relay Agent Information Option. [STANDARDS-TRACK] | April 2002 Status: PROPOSED STANDARD Autor: D. Jones, R. Woundy |
| RFC3257 Stream Control Transmission Protocol Applicability Statement 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. | April 2002 Status: INFORMATIONAL Autor: L. Coene |
| RFC3258 Distributing Authoritative Name Servers via Shared Unicast Addresses 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. | April 2002 Status: INFORMATIONAL Autor: T. Hardie |
| RFC3259 A Message Bus for Local Coordination 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. | April 2002 Status: INFORMATIONAL Autor: J. Ott, C. Perkins, D. Kutscher |
| RFC3260 New Terminology and Clarifications for Diffserv 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. | April 2002 Status: INFORMATIONAL Autor: D. Grossman |
| RFC3261 SIP: Session Initiation Protocol 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] | June 2002 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, E. Schooler |
| RFC3262 Reliability of Provisional Responses in Session Initiation Protocol (SIP) 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] | June 2002 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne |
| RFC3263 Session Initiation Protocol (SIP): Locating SIP Servers 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] | June 2002 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne |
| RFC3264 An Offer/Answer Model with Session Description Protocol (SDP) 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] | June 2002 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne |
| RFC3265 Session Initiation Protocol (SIP)-Specific Event Notification 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] | June 2002 Status: PROPOSED STANDARD Autor: A. B. Roach |
| RFC3266 Support for IPv6 in Session Description Protocol (SDP) 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] | June 2002 Status: PROPOSED STANDARD Autor: S. Olson, G. Camarillo, A. B. Roach |
| 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 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] | June 2002 Status: PROPOSED STANDARD Autor: J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie |
| RFC3268 Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS) 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] | June 2002 Status: PROPOSED STANDARD Autor: P. Chown |
| RFC3269 Author Guidelines for Reliable Multicast Transport (RMT) Building Blocks and Protocol Instantiation documents 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. | April 2002 Status: INFORMATIONAL Autor: R. Kermode, L. Vicisano |
| RFC3270 Multi-Protocol Label Switching (MPLS) Support of Differentiated Services This document defines a flexible solution for support of Differentiated Services (Diff-Serv) over Multi-Protocol Label Switching (MPLS) networks. [STANDARDS-TRACK] | May 2002 Status: PROPOSED STANDARD Autor: F. Le Faucheur, L. Wu, B. Davie, S. Davari, P. Vaananen, R. Krishnan, P. Cheval, J. Heinanen |
| RFC3271 The Internet is for Everyone 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. | April 2002 Status: INFORMATIONAL Autor: V. Cerf |
| RFC3272 Overview and Principles of Internet Traffic Engineering 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. | May 2002 Status: INFORMATIONAL Autor: D. Awduche, A. Chiu, A. Elwalid, I. Widjaja, X. Xiao |
| RFC3273 Remote Network Monitoring Management Information Base for High Capacity 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] | July 2002 Status: PROPOSED STANDARD Autor: S. Waldbusser |
| RFC3274 Compressed Data Content Type for Cryptographic Message Syntax (CMS) 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] | June 2002 Status: PROPOSED STANDARD Autor: P. Gutmann |
| RFC3275 (Extensible Markup Language) XML-Signature Syntax and Processing This document specifies XML (Extensible Markup Language) digital signature processing rules and syntax. [STANDARDS-TRACK] | March 2002 Status: DRAFT STANDARD Autor: D. Eastlake 3rd, J. Reagle, D. Solo |
| RFC3276 Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines Processing 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] | May 2002 Status: PROPOSED STANDARD Autor: B. Ray, R. Abbi |
| RFC3277 Intermediate System to Intermediate System (IS-IS) Transient Blackhole Avoidance 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. | April 2002 Status: INFORMATIONAL Autor: D. McPherson |
| RFC3278 Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) 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. | April 2002 Status: INFORMATIONAL Autor: S. Blake-Wilson, D. Brown, P. Lambert |
| RFC3279 Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile 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] | April 2002 Status: PROPOSED STANDARD Autor: L. Bassham, W. Polk, R. Housley |
| RFC3280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile This memo profiles the X.509 v3 certificate and X.509 v2 Certificate Revocation List (CRL) for use in the Internet. [STANDARDS-TRACK] | April 2002 Status: PROPOSED STANDARD Autor: R. Housley, W. Polk, W. Ford, D. Solo |
| RFC3281 An Internet Attribute Certificate Profile for Authorization 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] | April 2002 Status: PROPOSED STANDARD Autor: S. Farrell, R. Housley |
| RFC3282 Content Language Headers 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] | May 2002 Status: DRAFT STANDARD Autor: H. Alvestrand |
| RFC3283 Guide to Internet Calendaring 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. | June 2002 Status: INFORMATIONAL Autor: B. Mahoney, G. Babics, A. Taler |
| RFC3284 The VCDIFF Generic Differencing and Compression Data Format 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] | June 2002 Status: PROPOSED STANDARD Autor: D. Korn, J. MacDonald, J. Mogul, K. Vo |
| RFC3285 Using Microsoft Word to create Internet Drafts and RFCs 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. | May 2002 Status: INFORMATIONAL Autor: M. Gahrns, T. Hain |
| RFC3286 An Introduction to the Stream Control Transmission Protocol (SCTP) 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. | May 2002 Status: INFORMATIONAL Autor: L. Ong, J. Yoakum |
| RFC3287 Remote Monitoring MIB Extensions for Differentiated Services 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] | July 2002 Status: PROPOSED STANDARD Autor: A. Bierman |
| RFC3288 Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) 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] | June 2002 Status: PROPOSED STANDARD Autor: E. O'Tuathail, M. Rose |
| RFC3289 Management Information Base for the Differentiated Services 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] | May 2002 Status: PROPOSED STANDARD Autor: F. Baker, K. Chan, A. Smith |
| RFC3290 An Informal Management Model for Diffserv Routers 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. | May 2002 Status: INFORMATIONAL Autor: Y. Bernet, S. Blake, D. Grossman, A. Smith |
| RFC3291 Textual Conventions for Internet Network Addresses 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] | May 2002 Status: PROPOSED STANDARD Autor: M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder |
| RFC3292 General Switch Management Protocol (GSMP) V3 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] | June 2002 Status: PROPOSED STANDARD Autor: A. Doria, F. Hellstrand, K. Sundell, T. Worster |
| RFC3293 General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP) 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] | June 2002 Status: PROPOSED STANDARD Autor: T. Worster, A. Doria, J. Buerkle |
| RFC3294 General Switch Management Protocol (GSMP) Applicability 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. | June 2002 Status: INFORMATIONAL Autor: A. Doria, K. Sundell |
| RFC3295 Definitions of Managed Objects for the General Switch Management Protocol (GSMP) 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] | June 2002 Status: PROPOSED STANDARD Autor: H. Sjostrand, J. Buerkle, B. Srinivasan |
| RFC3296 Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories This document details schema and protocol elements for representing and managing named subordinate references in Lightweight Directory Access Protocol (LDAP) Directories. [STANDARDS-TRACK] | July 2002 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3297 Content Negotiation for Messaging Services based on Email This memo describes a content negotiation mechanism for facsimile, voice and other messaging services that use Internet email. [STANDARDS-TRACK] | July 2002 Status: PROPOSED STANDARD Autor: G. Klyne, R. Iwazaki, D. Crocker |
| RFC3298 Service in the Public Switched Telephone Network/Intelligent Network (PSTN/IN) Requesting InTernet Service (SPIRITS) Protocol Requirements 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. | August 2002 Status: INFORMATIONAL Autor: I. Faynberg, J. Gato, H. Lu, L. Slutsman |
| RFC3299 Request for Comments Summary RFC Numbers 3200-3299 | December 2003 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC3300 Internet Official Protocol Standards | November 2002 Status: HISTORIC Autor: J. Reynolds, R. Braden, S. Ginoza, A. De La Cruz |
| RFC3301 Layer Two Tunnelling Protocol (L2TP): ATM access network extensions | June 2002 Status: PROPOSED STANDARD Autor: Y. T'Joens, P. Crivellari, B. Sales |
| RFC3302 Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration | September 2002 Status: DRAFT STANDARD Autor: G. Parsons, J. Rafferty |
| RFC3303 Middlebox communication architecture and framework | August 2002 Status: INFORMATIONAL Autor: P. Srisuresh, J. Kuthan, J. Rosenberg, A. Molitor, A. Rayhan |
| RFC3304 Middlebox Communications (midcom) Protocol Requirements | August 2002 Status: INFORMATIONAL Autor: R. P. Swale, P. A. Mart, P. Sijben, S. Brim, M. Shore |
| RFC3305 Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations | August 2002 Status: INFORMATIONAL Autor: M. Mealling, R. Denenberg |
| RFC3306 Unicast-Prefix-based IPv6 Multicast Addresses | August 2002 Status: PROPOSED STANDARD Autor: B. Haberman, D. Thaler |
| RFC3307 Allocation Guidelines for IPv6 Multicast Addresses | August 2002 Status: PROPOSED STANDARD Autor: B. Haberman |
| RFC3308 Layer Two Tunneling Protocol (L2TP) Differentiated Services Extension | November 2002 Status: PROPOSED STANDARD Autor: P. Calhoun, W. Luo, D. McPherson, K. Peirce |
| RFC3309 Stream Control Transmission Protocol (SCTP) Checksum Change | September 2002 Status: PROPOSED STANDARD Autor: J. Stone, R. Stewart, D. Otis |
| RFC3310 Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) | September 2002 Status: INFORMATIONAL Autor: A. Niemi, J. Arkko, V. Torvinen |
| RFC3311 The Session Initiation Protocol (SIP) UPDATE Method | October 2002 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC3312 Integration of Resource Management and Session Initiation Protocol (SIP) | October 2002 Status: PROPOSED STANDARD Autor: G. Camarillo, W. Marshall, J. Rosenberg |
| RFC3313 Private Session Initiation Protocol (SIP) Extensions for Media Authorization | January 2003 Status: INFORMATIONAL Autor: W. Marshall |
| RFC3314 Recommendations for IPv6 in Third Generation Partnership Project (3GPP) Standards | September 2002 Status: INFORMATIONAL Autor: M. Wasserman |
| RFC3315 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | July 2003 Status: PROPOSED STANDARD Autor: R. Droms, J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney |
| RFC3316 Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular Hosts | April 2003 Status: INFORMATIONAL Autor: J. Arkko, G. Kuijpers, H. Soliman, J. Loughney, J. Wiljakka |
| RFC3317 Differentiated Services Quality of Service Policy Information Base | March 2003 Status: INFORMATIONAL Autor: K. Chan, R. Sahita, S. Hahn, K. McCloghrie |
| RFC3318 Framework Policy Information Base | March 2003 Status: INFORMATIONAL Autor: R. Sahita, S. Hahn, K. Chan, K. McCloghrie |
| RFC3319 Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers | July 2003 Status: PROPOSED STANDARD Autor: H. Schulzrinne, B. Volz |
| RFC3320 Signaling Compression (SigComp) | January 2003 Status: PROPOSED STANDARD Autor: R. Price, C. Bormann, J. Christoffersson, H. Hannu, Z. Liu, J. Rosenberg |
| RFC3321 Signaling Compression (SigComp) - Extended Operations | January 2003 Status: PROPOSED STANDARD Autor: H. Hannu, J. Christoffersson, S. Forsgren, K.-C. Leung, Z. Liu, R. Price |
| RFC3322 Signaling Compression (SigComp) Requirements & Assumptions | January 2003 Status: INFORMATIONAL Autor: H. Hannu |
| RFC3323 A Privacy Mechanism for the Session Initiation Protocol (SIP) | November 2002 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3324 Short Term Requirements for Network Asserted Identity | November 2002 Status: INFORMATIONAL Autor: M. Watson |
| RFC3325 Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks | November 2002 Status: INFORMATIONAL Autor: C. Jennings, J. Peterson, M. Watson |
| RFC3326 The Reason Header Field for the Session Initiation Protocol (SIP) 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] | December 2002 Status: PROPOSED STANDARD Autor: H. Schulzrinne, D. Oran, G. Camarillo |
| RFC3327 Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts | December 2002 Status: PROPOSED STANDARD Autor: D. Willis, B. Hoeneisen |
| RFC3329 Security Mechanism Agreement for the Session Initiation Protocol (SIP) | January 2003 Status: PROPOSED STANDARD Autor: J. Arkko, V. Torvinen, G. Camarillo, A. Niemi, T. Haukka |
| RFC3330 Special-Use IPv4 Addresses | September 2002 Status: INFORMATIONAL Autor: IANA |
| RFC3331 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer | September 2002 Status: PROPOSED STANDARD Autor: K. Morneault, R. Dantu, G. Sidebottom, B. Bidulock, J. Heitz |
| RFC3332 Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA) | September 2002 Status: PROPOSED STANDARD Autor: G. Sidebottom, K. Morneault, J. Pastor-Balbas |
| RFC3334 Policy-Based Accounting | October 2002 Status: EXPERIMENTAL Autor: T. Zseby, S. Zander, C. Carle |
| RFC3335 MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet | September 2002 Status: PROPOSED STANDARD Autor: T. Harding, R. Drummond, C. Shih |
| RFC3336 PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2) | December 2002 Status: PROPOSED STANDARD Autor: B. Thompson, T. Koren, B. Buffam |
| RFC3337 Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2 | December 2002 Status: PROPOSED STANDARD Autor: B. Thompson, T. Koren, B. Buffam |
| RFC3338 Dual Stack Hosts Using "Bump-in-the-API" (BIA) | October 2002 Status: EXPERIMENTAL Autor: S. Lee, M-K. Shin, Y-J. Kim, E. Nordmark, A. Durand |
| RFC3339 Date and Time on the Internet: Timestamps | July 2002 Status: PROPOSED STANDARD Autor: G. Klyne, C. Newman |
| RFC3340 The Application Exchange Core | July 2002 Status: PROPOSED STANDARD Autor: M. Rose, G. Klyne, D. Crocker |
| RFC3341 The Application Exchange (APEX) Access Service | July 2002 Status: PROPOSED STANDARD Autor: M. Rose, G. Klyne, D. Crocker |
| RFC3342 The Application Exchange (APEX) Option Party Pack, Part Deux! | July 2002 Status: PROPOSED STANDARD Autor: E. Dixon, H. Franklin, J. Kint, G. Klyne, D. New, S. Pead, M. Rose, M. Schwartz |
| RFC3343 The Application Exchange (APEX) Presence Service | April 2003 Status: EXPERIMENTAL Autor: M. Rose, G. Klyne, D. Crocker |
| RFC3344 IP Mobility Support for IPv4 | August 2002 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC3345 Border Gateway Protocol (BGP) Persistent Route Oscillation Condition | August 2002 Status: INFORMATIONAL Autor: D. McPherson, V. Gill, D. Walton, A. Retana |
| RFC3346 Applicability Statement for Traffic Engineering with MPLS | August 2002 Status: INFORMATIONAL Autor: J. Boyle, V. Gill, A. Hannan, D. Cooper, D. Awduche, B. Christian, W.S. Lai |
| RFC3347 Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations | July 2002 Status: PROPOSED STANDARD Autor: M. Krueger, R. Haagens |
| RFC3348 The Internet Message Action Protocol (IMAP4) Child Mailbox Extension | July 2002 Status: INFORMATIONAL Autor: M. Gahrns, R. Cheng |
| RFC3349 A Transient Prefix for Identifying Profiles under Development by the Working Groups of the Internet Engineering Task Force | July 2002 Status: BEST CURRENT PRACTICE Autor: M. Rose |
| RFC3351 User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals | August 2002 Status: INFORMATIONAL Autor: N. Charlton, M. Gasson, G. Gybels, M. Spanner, A. van Wijk |
| RFC3352 Connection-less Lightweight Directory Access Protocol (CLDAP) to Historic Status | March 2003 Status: INFORMATIONAL Autor: K. Zeilenga |
| RFC3353 Overview of IP Multicast in a Multi-Protocol Label Switching (MPLS) Environment | August 2002 Status: INFORMATIONAL Autor: D. Ooms, B. Sales, W. Livens, A. Acharya, F. Griffoul, F. Ansari |
| RFC3354 Internet Open Trading Protocol Version 2 Requirements | August 2002 Status: INFORMATIONAL Autor: D. Eastlake 3rd |
| RFC3355 Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5) | August 2002 Status: PROPOSED STANDARD Autor: A. Singh, R. Turner, R. Tio, S. Nanji |
| RFC3356 Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines | August 2002 Status: INFORMATIONAL Autor: G. Fishman, S. Bradner |
| RFC3357 One-way Loss Pattern Sample Metrics | August 2002 Status: INFORMATIONAL Autor: R. Koodli, R. Ravikanth |
| RFC3358 Optional Checksums in Intermediate System to Intermediate System (ISIS) | August 2002 Status: INFORMATIONAL Autor: T. Przygienda |
| RFC3359 Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System | August 2002 Status: INFORMATIONAL Autor: T. Przygienda |
| RFC3360 Inappropriate TCP Resets Considered Harmful | August 2002 Status: BEST CURRENT PRACTICE Autor: S. Floyd |
| RFC3361 Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers | August 2002 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC3362 Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration | August 2002 Status: PROPOSED STANDARD Autor: G. Parsons |
| RFC3363 Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS) | August 2002 Status: INFORMATIONAL Autor: R. Bush, A. Durand, B. Fink, O. Gudmundsson, T. Hain |
| RFC3364 Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6) | August 2002 Status: INFORMATIONAL Autor: R. Austein |
| RFC3365 Strong Security Requirements for Internet Engineering Task Force Standard Protocols | August 2002 Status: BEST CURRENT PRACTICE Autor: J. Schiller |
| RFC3366 Advice to link designers on link Automatic Repeat reQuest (ARQ) | August 2002 Status: BEST CURRENT PRACTICE Autor: G. Fairhurst, L. Wood |
| RFC3367 Common Name Resolution Protocol (CNRP) | August 2002 Status: PROPOSED STANDARD Autor: N. Popp, M. Mealling, M. Moseley |
| RFC3368 The 'go' URI Scheme for the Common Name Resolution Protocol | August 2002 Status: PROPOSED STANDARD Autor: M. Mealling |
| RFC3369 Cryptographic Message Syntax (CMS) | August 2002 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC3370 Cryptographic Message Syntax (CMS) Algorithms | August 2002 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC3371 Layer Two Tunneling Protocol "L2TP" Management Information Base | August 2002 Status: PROPOSED STANDARD Autor: E. Caves, P. Calhoun, R. Wheeler |
| RFC3372 Session Initiation Protocol for Telephones (SIP-T): Context and Architectures | September 2002 Status: BEST CURRENT PRACTICE Autor: A. Vemuri, J. Peterson |
| RFC3373 Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies | September 2002 Status: INFORMATIONAL Autor: D. Katz, R. Saluja |
| RFC3374 Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access Network | September 2002 Status: INFORMATIONAL Autor: J. Kempf |
| RFC3375 Generic Registry-Registrar Protocol Requirements | September 2002 Status: INFORMATIONAL Autor: S. Hollenbeck |
| RFC3376 Internet Group Management Protocol, Version 3 | October 2002 Status: PROPOSED STANDARD Autor: B. Cain, S. Deering, I. Kouvelas, B. Fenner, A. Thyagarajan |
| RFC3377 Lightweight Directory Access Protocol (v3): Technical Specification | September 2002 Status: PROPOSED STANDARD Autor: J. Hodges, R. Morgan |
| RFC3378 EtherIP: Tunneling Ethernet Frames in IP Datagrams | September 2002 Status: INFORMATIONAL Autor: R. Housley, S. Hollenbeck |
| RFC3379 Delegated Path Validation and Delegated Path Discovery Protocol Requirements | September 2002 Status: INFORMATIONAL Autor: D. Pinkas, R. Housley |
| RFC3380 Internet Printing Protocol (IPP): Job and Printer Set Operations | September 2002 Status: PROPOSED STANDARD Autor: T. Hastings, R. Herriot, C. Kugler, H. Lewis |
| RFC3381 Internet Printing Protocol (IPP): Job Progress Attributes | September 2002 Status: PROPOSED STANDARD Autor: T. Hastings, H. Lewis, R. Bergman |
| RFC3382 Internet Printing Protocol (IPP): The 'collection' attribute syntax | September 2002 Status: PROPOSED STANDARD Autor: R. deBry, T. Hastings, R. Herriot, K. Ocke, P. Zehler |
| RFC3383 Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) | September 2002 Status: BEST CURRENT PRACTICE Autor: K. Zeilenga |
| RFC3384 Lightweight Directory Access Protocol (version 3) Replication Requirements | October 2002 Status: INFORMATIONAL Autor: E. Stokes, R. Weiser, R. Moats, R. Huber |
| RFC3385 Internet Protocol Small Computer System Interface (iSCSI) Cyclic Redundancy Check (CRC)/Checksum Considerations | September 2002 Status: INFORMATIONAL Autor: D. Sheinwald, J. Satran, P. Thaler, V. Cavanna |
| RFC3386 Network Hierarchy and Multilayer Survivability | November 2002 Status: INFORMATIONAL Autor: W. Lai, D. McDysan |
| RFC3387 Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP Network | September 2002 Status: INFORMATIONAL Autor: M. Eder, H. Chaskar, S. Nag |
| RFC3388 Grouping of Media Lines in the Session Description Protocol (SDP) | December 2002 Status: PROPOSED STANDARD Autor: G. Camarillo, G. Eriksson, J. Holler, H. Schulzrinne |
| RFC3389 Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN) | September 2002 Status: PROPOSED STANDARD Autor: R. Zopf |
| RFC3390 Increasing TCP's Initial Window | October 2002 Status: PROPOSED STANDARD Autor: M. Allman, S. Floyd, C. Partridge |
| RFC3391 The MIME Application/Vnd.pwg-multiplexed Content-Type | December 2002 Status: INFORMATIONAL Autor: R. Herriot |
| RFC3392 Capabilities Advertisement with BGP-4 | November 2002 Status: DRAFT STANDARD Autor: R. Chandra, J. Scudder |
| RFC3393 IP Packet Delay Variation Metric for IP Performance Metrics (IPPM) | November 2002 Status: PROPOSED STANDARD Autor: C. Demichelis, P. Chimento |
| RFC3394 Advanced Encryption Standard (AES) Key Wrap Algorithm | September 2002 Status: INFORMATIONAL Autor: J. Schaad, R. Housley |
| RFC3395 Remote Network Monitoring MIB Protocol Identifier Reference Extensions | September 2002 Status: PROPOSED STANDARD Autor: A. Bierman, C. Bucci, R. Dietz, A. Warth |
| RFC3396 Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4) | November 2002 Status: PROPOSED STANDARD Autor: T. Lemon, S. Cheshire |
| RFC3397 Dynamic Host Configuration Protocol (DHCP) Domain Search Option | November 2002 Status: PROPOSED STANDARD Autor: B. Aboba, S. Cheshire |
| RFC3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping | December 2002 Status: PROPOSED STANDARD Autor: G. Camarillo, A. B. Roach, J. Peterson, L. Ong |
| RFC3401 Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS 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. | October 2002 Status: INFORMATIONAL Autor: M. Mealling |
| RFC3402 Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm 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] | October 2002 Status: PROPOSED STANDARD Autor: M. Mealling |
| RFC3403 Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database 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] | October 2002 Status: PROPOSED STANDARD Autor: M. Mealling |
| RFC3404 Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) 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] | October 2002 Status: PROPOSED STANDARD Autor: M. Mealling |
| RFC3405 Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures 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. | October 2002 Status: BEST CURRENT PRACTICE Autor: M. Mealling |
| RFC3406 Uniform Resource Names (URN) Namespace Definition Mechanisms 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. | October 2002 Status: BEST CURRENT PRACTICE Autor: L. Daigle, D. van Gulik, R. Iannella, P. Faltstrom |
| RFC3407 Session Description Protocol (SDP) Simple Capability Declaration 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] | October 2002 Status: PROPOSED STANDARD Autor: F. Andreasen |
| RFC3408 Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended Link-Layer Assisted RObust Header Compression (ROHC) Profile 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] | December 2002 Status: PROPOSED STANDARD Autor: Z. Liu, K. Le |
| RFC3409 Lower Layer Guidelines for Robust RTP/UDP/IP Header Compression 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. | December 2002 Status: INFORMATIONAL Autor: K. Svanbro |
| RFC3410 Introduction and Applicability Statements for Internet-Standard Management Framework 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. | December 2002 Status: INFORMATIONAL Autor: J. Case, R. Mundy, D. Partain, B. Stewart |
| RFC3411 An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks 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] | December 2002 Status: STANDARD Autor: D. Harrington, R. Presuhn, B. Wijnen |
| RFC3412 Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) 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] | December 2002 Status: STANDARD Autor: J. Case, D. Harrington, R. Presuhn, B. Wijnen |
| RFC3413 Simple Network Management Protocol (SNMP) Applications 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] | December 2002 Status: STANDARD Autor: D. Levi, P. Meyer, B. Stewart |
| RFC3414 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) This document describes the User-based Security Model (USM) for 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] | December 2002 Status: STANDARD Autor: U. Blumenthal, B. Wijnen |
| RFC3415 View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) 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] | December 2002 Status: STANDARD Autor: B. Wijnen, R. Presuhn, K. McCloghrie |
| RFC3416 Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP) 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] | December 2002 Status: STANDARD Autor: R. Presuhn |
| RFC3417 Transport Mappings for the Simple Network Management Protocol (SNMP) This document defines the transport of Simple Network Management Protocol (SNMP) messages over various protocols. This document obsoletes RFC 1906. [STANDARDS-TRACK] | December 2002 Status: STANDARD Autor: R. Presuhn |
| RFC3418 Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) 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] | December 2002 Status: STANDARD Autor: R. Presuhn |
| RFC3419 Textual Conventions for Transport Addresses 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] | December 2002 Status: PROPOSED STANDARD Autor: M. Daniele, J. Schoenwaelder |
| RFC3420 Internet Media Type message/sipfrag 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] | November 2002 Status: PROPOSED STANDARD Autor: R. Sparks |
| RFC3421 Select and Sort Extensions for the Service Location Protocol (SLP) 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. | November 2002 Status: EXPERIMENTAL Autor: W. Zhao, H. Schulzrinne, E. Guttman, C. Bisdikian, W. Jerome |
| RFC3422 Forwarding Media Access Control (MAC) Frames over Multiple Access Protocol over Synchronous Optical Network/Synchronous Digital Hierarchy (MAPOS) 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. | November 2002 Status: INFORMATIONAL Autor: O. Okamoto, M. Maruyama, T. Sajima |
| RFC3423 XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0 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. | November 2002 Status: INFORMATIONAL Autor: K. Zhang, E. Elkin |
| RFC3424 IAB Considerations for UNilateral Self-Address Fixing (UNSAF) Across Network Address Translation 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. | November 2002 Status: INFORMATIONAL Autor: L. Daigle, IAB |
| RFC3425 Obsoleting IQUERY 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] | November 2002 Status: PROPOSED STANDARD Autor: D. Lawrence |
| RFC3426 General Architectural and Policy Considerations 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. | November 2002 Status: INFORMATIONAL Autor: S. Floyd |
| RFC3427 Change Process for the Session Initiation Protocol (SIP) 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. | December 2002 Status: BEST CURRENT PRACTICE Autor: A. Mankin, S. Bradner, R. Mahy, D. Willis, J. Ott, B. Rosen |
| RFC3428 Session Initiation Protocol (SIP) Extension for Instant Messaging 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] | December 2002 Status: PROPOSED STANDARD Autor: B. Campbell, J. Rosenberg, H. Schulzrinne, C. Huitema, D. Gurle |
| RFC3429 Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions 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. | November 2002 Status: INFORMATIONAL Autor: H. Ohta |
| RFC3430 Simple Network Management Protocol Over Transmission Control Protocol Transport Mapping 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. | December 2002 Status: EXPERIMENTAL Autor: J. Schoenwaelder |
| RFC3431 Sieve Extension: Relational Tests 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] | December 2002 Status: PROPOSED STANDARD Autor: W. Segmuller |
| RFC3432 Network performance measurement with periodic streams 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] | November 2002 Status: PROPOSED STANDARD Autor: V. Raisanen, G. Grotefeld, A. Morton |
| RFC3433 Entity Sensor 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 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] | December 2002 Status: PROPOSED STANDARD Autor: A. Bierman, D. Romascanu, K.C. Norseth |
| RFC3434 Remote Monitoring MIB Extensions for High Capacity Alarms 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] | December 2002 Status: PROPOSED STANDARD Autor: A. Bierman, K. McCloghrie |
| RFC3435 Media Gateway Control Protocol (MGCP) Version 1.0 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. | January 2003 Status: INFORMATIONAL Autor: F. Andreasen, B. Foster |
| RFC3436 Transport Layer Security over Stream Control Transmission Protocol 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] | December 2002 Status: PROPOSED STANDARD Autor: A. Jungmaier, E. Rescorla, M. Tuexen |
| RFC3437 Layer-Two Tunneling Protocol Extensions for PPP Link Control Protocol Negotiation 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] | December 2002 Status: PROPOSED STANDARD Autor: W. Palter, W. Townsley |
| RFC3438 Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update 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. | December 2002 Status: BEST CURRENT PRACTICE Autor: W. Townsley |
| RFC3439 Some Internet Architectural Guidelines and Philosophy 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. | December 2002 Status: INFORMATIONAL Autor: R. Bush, D. Meyer |
| RFC3440 Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines 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] | December 2002 Status: PROPOSED STANDARD Autor: F. Ly, G. Bathrick |
| RFC3441 Asynchronous Transfer Mode (ATM) Package for the Media Gateway Control Protocol (MGCP) 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. | January 2003 Status: INFORMATIONAL Autor: R. Kumar |
| RFC3442 The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4 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] | December 2002 Status: PROPOSED STANDARD Autor: T. Lemon, S. Cheshire, B. Volz |
| RFC3443 Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks 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] | January 2003 Status: PROPOSED STANDARD Autor: P. Agarwal, B. Akyol |
| RFC3444 On the Difference between Information Models and Data Models 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. | January 2003 Status: INFORMATIONAL Autor: A. Pras, J. Schoenwaelder |
| RFC3445 Limiting the Scope of the KEY Resource Record (RR) 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] | December 2002 Status: PROPOSED STANDARD Autor: D. Massey, S. Rose |
| RFC3446 Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) 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. | January 2003 Status: INFORMATIONAL Autor: D. Kim, D. Meyer, H. Kilmer, D. Farinacci |
| RFC3447 Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1 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. | February 2003 Status: INFORMATIONAL Autor: J. Jonsson, B. Kaliski |
| RFC3448 TCP Friendly Rate Control (TFRC): Protocol Specification 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] | January 2003 Status: PROPOSED STANDARD Autor: M. Handley, S. Floyd, J. Padhye, J. Widmer |
| RFC3449 TCP Performance Implications of Network Path Asymmetry 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. | December 2002 Status: BEST CURRENT PRACTICE Autor: H. Balakrishnan, V. Padmanabhan, G. Fairhurst, M. Sooriyabandara |
| RFC3450 Asynchronous Layered Coding (ALC) Protocol Instantiation 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. | December 2002 Status: EXPERIMENTAL Autor: M. Luby, J. Gemmell, L. Vicisano, L. Rizzo, J. Crowcroft |
| RFC3451 Layered Coding Transport (LCT) Building Block 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. | December 2002 Status: EXPERIMENTAL Autor: M. Luby, J. Gemmell, L. Vicisano, L. Rizzo, M. Handley, J. Crowcroft |
| RFC3452 Forward Error Correction (FEC) Building Block 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. | December 2002 Status: EXPERIMENTAL Autor: M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, J. Crowcroft |
| RFC3453 The Use of Forward Error Correction (FEC) in Reliable Multicast 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. | December 2002 Status: INFORMATIONAL Autor: M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, J. Crowcroft |
| RFC3454 Preparation of Internationalized Strings ("stringprep") 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] | December 2002 Status: PROPOSED STANDARD Autor: P. Hoffman, M. Blanchet |
| RFC3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP) 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. | January 2003 Status: INFORMATIONAL Autor: M. Garcia-Martin, E. Henrikson, D. Mills |
| RFC3456 Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode 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] | January 2003 Status: PROPOSED STANDARD Autor: B. Patel, B. Aboba, S. Kelly, V. Gupta |
| RFC3457 Requirements for IPsec 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. | January 2003 Status: INFORMATIONAL Autor: S. Kelly, S. Ramamoorthi |
| RFC3458 Message Context for Internet Mail 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] | January 2003 Status: PROPOSED STANDARD Autor: E. Burger, E. Candell, C. Eliot, G. Klyne |
| RFC3459 Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter 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] | January 2003 Status: PROPOSED STANDARD Autor: E. Burger |
| RFC3460 Policy Core Information Model (PCIM) Extensions 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] | January 2003 Status: PROPOSED STANDARD Autor: B. Moore |
| RFC3461 Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs) 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] | January 2003 Status: DRAFT STANDARD Autor: K. Moore |
| RFC3462 The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages 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] | January 2003 Status: DRAFT STANDARD Autor: G. Vaudreuil |
| RFC3463 Enhanced Mail System Status Codes 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] | January 2003 Status: DRAFT STANDARD Autor: G. Vaudreuil |
| RFC3464 An Extensible Message Format for Delivery Status Notifications 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] | January 2003 Status: DRAFT STANDARD Autor: K. Moore, G. Vaudreuil |
| RFC3465 TCP Congestion Control with Appropriate Byte Counting (ABC) 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. | February 2003 Status: EXPERIMENTAL Autor: M. Allman |
| RFC3466 A Model for Content Internetworking (CDI) 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. | February 2003 Status: INFORMATIONAL Autor: M. Day, B. Cain, G. Tomlinson, P. Rzewski |
| RFC3467 Role of the Domain Name System (DNS) 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. | February 2003 Status: INFORMATIONAL Autor: J. Klensin |
| RFC3468 The Multiprotocol Label Switching (MPLS) Working Group decision on MPLS signaling protocols 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. | February 2003 Status: INFORMATIONAL Autor: L. Andersson, G. Swallow |
| RFC3469 Framework for Multi-Protocol Label Switching (MPLS)-based Recovery 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. | February 2003 Status: INFORMATIONAL Autor: V. Sharma, F. Hellstrand |
| RFC3470 Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols 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. | January 2003 Status: BEST CURRENT PRACTICE Autor: S. Hollenbeck, M. Rose, L. Masinter |
| RFC3471 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description 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] | January 2003 Status: PROPOSED STANDARD Autor: L. Berger |
| RFC3472 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions 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] | January 2003 Status: PROPOSED STANDARD Autor: P. Ashwood-Smith, L. Berger |
| RFC3473 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions 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] | January 2003 Status: PROPOSED STANDARD Autor: L. Berger |
| 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) 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. | March 2003 Status: INFORMATIONAL Autor: Z. Lin, D. Pendarakis |
| RFC3475 Documentation of IANA assignments for Constraint-Based LSP setup using LDP (CR-LDP) Extensions for Automatic Switched Optical Network (ASON) 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. | March 2003 Status: INFORMATIONAL Autor: O. Aboul-Magd |
| 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 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. | March 2003 Status: INFORMATIONAL Autor: B. Rajagopalan |
| RFC3477 Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-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 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] | January 2003 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter |
| RFC3478 Graceful Restart Mechanism for Label Distribution Protocol 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] | February 2003 Status: PROPOSED STANDARD Autor: M. Leelanivas, Y. Rekhter, R. Aggarwal |
| RFC3479 Fault Tolerance for the Label Distribution Protocol (LDP) 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] | February 2003 Status: PROPOSED STANDARD Autor: A. Farrel |
| RFC3480 Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol) 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] | February 2003 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter, A. Kullberg |
| RFC3481 TCP over Second (2.5G) and Third (3G) Generation Wireless Networks 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. | February 2003 Status: BEST CURRENT PRACTICE Autor: H. Inamura, G. Montenegro, R. Ludwig, A. Gurtov, F. Khafizov |
| RFC3482 Number Portability in the Global Switched Telephone Network (GSTN): An Overview 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. | February 2003 Status: INFORMATIONAL Autor: M. Foster, T. McGarry, J. Yu |
| RFC3483 Framework for Policy Usage Feedback for Common Open Policy Service with Policy Provisioning (COPS-PR) 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. | March 2003 Status: INFORMATIONAL Autor: D. Rawlins, A. Kulkarni, M. Bokaemper, K. Chan |
| RFC3484 Default Address Selection for Internet Protocol version 6 (IPv6) 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] | February 2003 Status: PROPOSED STANDARD Autor: R. Draves |
| RFC3485 The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp) 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] | February 2003 Status: PROPOSED STANDARD Autor: M. Garcia-Martin, C. Bormann, J. Ott, R. Price, A. B. Roach |
| RFC3486 Compressing the Session Initiation Protocol (SIP) 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] | February 2003 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC3487 Requirements for Resource Priority Mechanisms for the Session Initiation Protocol (SIP) 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. | February 2003 Status: INFORMATIONAL Autor: H. Schulzrinne |
| RFC3488 Cisco Systems Router-port Group Management Protocol (RGMP) 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. | February 2003 Status: INFORMATIONAL Autor: I. Wu, T. Eckert |
| RFC3489 STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) 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] | March 2003 Status: PROPOSED STANDARD Autor: J. Rosenberg, J. Weinberger, C. Huitema, R. Mahy |
| RFC3490 Internationalizing Domain Names in Applications (IDNA) 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] | March 2003 Status: PROPOSED STANDARD Autor: P. Faltstrom, P. Hoffman, A. Costello |
| RFC3491 Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN) 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] | March 2003 Status: PROPOSED STANDARD Autor: P. Hoffman, M. Blanchet |
| RFC3492 Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA) 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] | March 2003 Status: PROPOSED STANDARD Autor: A. Costello |
| RFC3493 Basic Socket Interface Extensions for IPv6 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. | February 2003 Status: INFORMATIONAL Autor: R. Gilligan, S. Thomson, J. Bound, J. McCann, W. Stevens |
| RFC3494 Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status 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. | March 2003 Status: INFORMATIONAL Autor: K. Zeilenga |
| RFC3495 Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration 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] | March 2003 Status: PROPOSED STANDARD Autor: B. Beser, P. Duffy |
| RFC3496 Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering 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. | March 2003 Status: INFORMATIONAL Autor: A. G. Malis, T. Hsiao |
| RFC3497 RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M Video 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] | March 2003 Status: PROPOSED STANDARD Autor: L. Gharai, C. Perkins, G. Goncher, A. Mankin |
| RFC3498 Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures 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] | March 2003 Status: PROPOSED STANDARD Autor: J. Kuhfeld, J. Johnson, M. Thatcher |
| RFC3499 Request for Comments Summary RFC Numbers 3400-3499 | December 2003 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC3501 INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. 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] | March 2003 Status: PROPOSED STANDARD Autor: M. Crispin |
| RFC3502 Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension 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] | March 2003 Status: PROPOSED STANDARD Autor: M. Crispin |
| RFC3503 Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP) 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] | March 2003 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC3504 Internet Open Trading Protocol (IOTP) Version 1, Errata 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. | March 2003 Status: INFORMATIONAL Autor: D. Eastlake |
| RFC3505 Electronic Commerce Modeling Language (ECML): Version 2 Requirements 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. | March 2003 Status: INFORMATIONAL Autor: D. Eastlake |
| RFC3506 Requirements and Design for Voucher Trading System (VTS) 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. | March 2003 Status: INFORMATIONAL Autor: K. Fujimura, D. Eastlake |
| RFC3507 Internet Content Adaptation Protocol (ICAP) 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. | April 2003 Status: INFORMATIONAL Autor: J. Elson, A. Cerpa |
| RFC3508 H.323 Uniform Resource Locator (URL) Scheme Registration 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. | April 2003 Status: INFORMATIONAL Autor: O. Levin |
| RFC3509 Alternative Implementations of OSPF Area Border Routers 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. | April 2003 Status: INFORMATIONAL Autor: A. Zinin, A. Lindem, D. Yeung |
| RFC3510 Internet Printing Protocol/1.1: IPP URL Scheme 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] | April 2003 Status: PROPOSED STANDARD Autor: R. Herriot, I. McDonald |
| RFC3511 Benchmarking Methodology for Firewall Performance 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. | April 2003 Status: INFORMATIONAL Autor: B. Hickman, D. Newman, S. Tadjudin, T. Martin |
| RFC3512 Configuring Networks and Devices with Simple Network Management Protocol (SNMP) 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. | April 2003 Status: INFORMATIONAL Autor: M. MacFaden, D. Partain, J. Saperia, W. Tackabury |
| RFC3513 Internet Protocol Version 6 (IPv6) Addressing Architecture 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] | April 2003 Status: PROPOSED STANDARD Autor: R. Hinden, S. Deering |
| RFC3514 The Security Flag in the IPv4 Header 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. | April 2003 Status: INFORMATIONAL Autor: S. Bellovin |
| RFC3515 The Session Initiation Protocol (SIP) Refer Method 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] | April 2003 Status: PROPOSED STANDARD Autor: R. Sparks |
| RFC3516 IMAP4 Binary Content Extension 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] | April 2003 Status: PROPOSED STANDARD Autor: L. Nerenberg |
| RFC3517 A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCP 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] | April 2003 Status: PROPOSED STANDARD Autor: E. Blanton, M. Allman, K. Fall, L. Wang |
| RFC3518 Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) 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] | April 2003 Status: PROPOSED STANDARD Autor: M. Higashiyama, F. Baker, T. Liao |
| RFC3519 Mobile IP Traversal of Network Address Translation (NAT) Devices 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] | April 2003 Status: PROPOSED STANDARD Autor: H. Levkowetz, S. Vaarala |
| RFC3520 Session Authorization Policy Element 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] | April 2003 Status: PROPOSED STANDARD Autor: L-N. Hamer, B. Gage, B. Kosinski, H. Shieh |
| RFC3521 Framework for Session Set-up with Media Authorization 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. | April 2003 Status: INFORMATIONAL Autor: L-N. Hamer, B. Gage, H. Shieh |
| RFC3522 The Eifel Detection Algorithm for TCP 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. | April 2003 Status: EXPERIMENTAL Autor: R. Ludwig, M. Meyer |
| RFC3523 Internet Emergency Preparedness (IEPREP) Telephony Topology Terminology 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. | April 2003 Status: INFORMATIONAL Autor: J. Polk |
| RFC3524 Mapping of Media Streams to Resource Reservation Flows 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] | April 2003 Status: PROPOSED STANDARD Autor: G. Camarillo, A. Monrad |
| RFC3525 Gateway Control Protocol Version 1 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] | June 2003 Status: HISTORIC Autor: C. Groves, M. Pantaleo, T. Anderson, T. Taylor |
| RFC3526 More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE) 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] | May 2003 Status: PROPOSED STANDARD Autor: T. Kivinen, M. Kojo |
| RFC3527 Link Selection sub-option for the Relay Agent Information Option for DHCPv4 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] | April 2003 Status: PROPOSED STANDARD Autor: K. Kinnear, M. Stapp, R. Johnson, J. Kumarasamy |
| RFC3528 Mesh-enhanced Service Location Protocol (mSLP) 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. | April 2003 Status: EXPERIMENTAL Autor: W. Zhao, H. Schulzrinne, E. Guttman |
| RFC3529 Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP) 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. | April 2003 Status: EXPERIMENTAL Autor: W. Harold |
| RFC3530 Network File System (NFS) version 4 Protocol 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] | April 2003 Status: PROPOSED STANDARD Autor: S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, C. Beame, M. Eisler, D. Noveck |
| RFC3531 A Flexible Method for Managing the Assignment of Bits of an IPv6 Address Block 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. | April 2003 Status: INFORMATIONAL Autor: M. Blanchet |
| RFC3532 Requirements for the Dynamic Partitioning of Switching Elements 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. | May 2003 Status: INFORMATIONAL Autor: T. Anderson, J. Buerkle |
| RFC3533 The Ogg Encapsulation Format Version 0 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. | May 2003 Status: INFORMATIONAL Autor: S. Pfeiffer |
| RFC3534 The application/ogg Media Type 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] | May 2003 Status: PROPOSED STANDARD Autor: L. Walleij |
| RFC3535 Overview of the 2002 IAB Network Management Workshop 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. | May 2003 Status: INFORMATIONAL Autor: J. Schoenwaelder |
| RFC3536 Terminology Used in Internationalization in the IETF 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. | May 2003 Status: INFORMATIONAL Autor: P. Hoffman |
| RFC3537 Wrapping a Hashed Message Authentication Code (HMAC) key with a Triple-Data Encryption Standard (DES) Key or an Advanced Encryption Standard (AES) Key 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] | May 2003 Status: PROPOSED STANDARD Autor: J. Schaad, R. Housley |
| RFC3538 Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP) 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. | June 2003 Status: INFORMATIONAL Autor: Y. Kawatsura |
| RFC3539 Authentication, Authorization and Accounting (AAA) Transport Profile 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] | June 2003 Status: PROPOSED STANDARD Autor: B. Aboba, J. Wood |
| RFC3540 Robust Explicit Congestion Notification (ECN) Signaling with Nonces 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. | June 2003 Status: EXPERIMENTAL Autor: N. Spring, D. Wetherall, D. Ely |
| RFC3541 A Uniform Resource Name (URN) Namespace for the Web3D Consortium (Web3D) 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. | May 2003 Status: INFORMATIONAL Autor: A. Walsh |
| RFC3542 Advanced Sockets Application Program Interface (API) for IPv6 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. | May 2003 Status: INFORMATIONAL Autor: W. Stevens, M. Thomas, E. Nordmark, T. Jinmei |
| RFC3543 Registration Revocation in Mobile IPv4 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] | August 2003 Status: PROPOSED STANDARD Autor: S. Glass, M. Chandra |
| RFC3544 IP Header Compression over PPP 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] | July 2003 Status: PROPOSED STANDARD Autor: T. Koren, S. Casner, C. Bormann |
| RFC3545 Enhanced Compressed RTP (CRTP) for Links with High Delay, Packet Loss and Reordering 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] | July 2003 Status: PROPOSED STANDARD Autor: T. Koren, S. Casner, J. Geevarghese, B. Thompson, P. Ruddy |
| RFC3546 Transport Layer Security (TLS) Extensions 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] | June 2003 Status: PROPOSED STANDARD Autor: S. Blake-Wilson, M. Nystrom, D. Hopwood, J. Mikkelsen, T. Wright |
| RFC3547 The Group Domain of Interpretation 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] | July 2003 Status: PROPOSED STANDARD Autor: M. Baugher, B. Weis, T. Hardjono, H. Harney |
| RFC3548 The Base16, Base32, and Base64 Data Encodings 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. | July 2003 Status: INFORMATIONAL Autor: S. Josefsson |
| RFC3549 Linux Netlink as an IP Services Protocol 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. | July 2003 Status: INFORMATIONAL Autor: J. Salim, H. Khosravi, A. Kleen, A. Kuznetsov |
| RFC3550 RTP: A Transport Protocol for Real-Time Applications This memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. 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] | July 2003 Status: STANDARD Autor: H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson |
| RFC3551 RTP Profile for Audio and Video Conferences with Minimal Control 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] | July 2003 Status: STANDARD Autor: H. Schulzrinne, S. Casner |
| RFC3552 Guidelines for Writing RFC Text on Security Considerations 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. | July 2003 Status: BEST CURRENT PRACTICE Autor: E. Rescorla, B. Korver |
| RFC3553 An IETF URN Sub-namespace for Registered Protocol Parameters 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. | June 2003 Status: BEST CURRENT PRACTICE Autor: M. Mealling, L. Masinter, T. Hardie, G. Klyne |
| RFC3554 On the Use of Stream Control Transmission Protocol (SCTP) with IPsec 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] | July 2003 Status: PROPOSED STANDARD Autor: S. Bellovin, J. Ioannidis, A. Keromytis, R. Stewart |
| RFC3555 MIME Type Registration of RTP Payload Formats 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] | July 2003 Status: PROPOSED STANDARD Autor: S. Casner, P. Hoschka |
| RFC3556 Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth 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] | July 2003 Status: PROPOSED STANDARD Autor: S. Casner |
| RFC3557 RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition Encoding 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] | July 2003 Status: PROPOSED STANDARD Autor: Q. Xie |
| RFC3558 RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV) 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] | July 2003 Status: PROPOSED STANDARD Autor: A. Li |
| RFC3559 Multicast Address Allocation 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 multicast address allocation. [STANDARDS-TRACK] | June 2003 Status: PROPOSED STANDARD Autor: D. Thaler |
| RFC3560 Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS) 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] | July 2003 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC3561 Ad hoc On-Demand Distance Vector (AODV) Routing 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. | July 2003 Status: EXPERIMENTAL Autor: C. Perkins, E. Belding-Royer, S. Das |
| RFC3562 Key Management Considerations for the TCP MD5 Signature Option 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. | July 2003 Status: INFORMATIONAL Autor: M. Leech |
| 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 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. | July 2003 Status: INFORMATIONAL Autor: A. Zinin |
| RFC3564 Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering 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. | July 2003 Status: INFORMATIONAL Autor: F. Le Faucheur, W. Lai |
| RFC3565 Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS) This document specifies the conventions for using the Advanced Encryption Standard (AES) algorithm for encryption with the Cryptographic Message Syntax (CMS). [STANDARDS-TRACK] | July 2003 Status: PROPOSED STANDARD Autor: J. Schaad |
| RFC3566 The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec 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] | September 2003 Status: PROPOSED STANDARD Autor: S. Frankel, H. Herbert |
| RFC3567 Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication 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. | July 2003 Status: INFORMATIONAL Autor: T. Li, R. Atkinson |
| RFC3568 Known Content Network (CN) Request-Routing Mechanisms 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. | July 2003 Status: INFORMATIONAL Autor: A. Barbir, B. Cain, R. Nair, O. Spatscheck |
| RFC3569 An Overview of Source-Specific Multicast (SSM) 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. | July 2003 Status: INFORMATIONAL Autor: S. Bhattacharyya |
| RFC3570 Content Internetworking (CDI) Scenarios 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. | July 2003 Status: INFORMATIONAL Autor: P. Rzewski, M. Day, D. Gilletti |
| RFC3571 Framework Policy Information Base for Usage Feedback 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. | August 2003 Status: INFORMATIONAL Autor: D. Rawlins, A. Kulkarni, K. Ho Chan, M. Bokaemper, D. Dutt |
| RFC3572 Internet Protocol Version 6 over MAPOS (Multiple Access Protocol Over SONET/SDH) 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. | July 2003 Status: INFORMATIONAL Autor: T. Ogura, M. Maruyama, T. Yoshida |
| RFC3573 Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP) 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] | July 2003 Status: PROPOSED STANDARD Autor: I. Goyret |
| RFC3574 Transition Scenarios for 3GPP Networks 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. | August 2003 Status: INFORMATIONAL Autor: J. Soininen |
| RFC3575 IANA Considerations for RADIUS (Remote Authentication Dial In User Service) This document describes the IANA considerations for the Remote Authentication Dial In User Service (RADIUS). [STANDARDS-TRACK] | July 2003 Status: PROPOSED STANDARD Autor: B. Aboba |
| RFC3576 Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) 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. | July 2003 Status: INFORMATIONAL Autor: M. Chiba, G. Dommety, M. Eklund, D. Mitton, B. Aboba |
| RFC3577 Introduction to the Remote Monitoring (RMON) Family of MIB Modules 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. | August 2003 Status: INFORMATIONAL Autor: S. Waldbusser, R. Cole, C. Kalbfleisch, D. Romascanu |
| RFC3578 Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP) 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] | August 2003 Status: PROPOSED STANDARD Autor: G. Camarillo, A. B. Roach, J. Peterson, L. Ong |
| RFC3579 RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP) 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. | September 2003 Status: INFORMATIONAL Autor: B. Aboba, P. Calhoun |
| RFC3580 IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines 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. | September 2003 Status: INFORMATIONAL Autor: P. Congdon, B. Aboba, A. Smith, G. Zorn, J. Roese |
| RFC3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing 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] | August 2003 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne |
| RFC3582 Goals for IPv6 Site-Multihoming Architectures 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. | August 2003 Status: INFORMATIONAL Autor: J. Abley, B. Black, V. Gill |
| RFC3583 Requirements of a Quality of Service (QoS) Solution for Mobile IP 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. | September 2003 Status: INFORMATIONAL Autor: H. Chaskar |
| RFC3584 Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework 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. | August 2003 Status: BEST CURRENT PRACTICE Autor: R. Frye, D. Levi, S. Routhier, B. Wijnen |
| RFC3585 IPsec Configuration Policy Information Model 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] | August 2003 Status: PROPOSED STANDARD Autor: J. Jason, L. Rafalow, E. Vyncke |
| RFC3586 IP Security Policy (IPSP) Requirements 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] | August 2003 Status: PROPOSED STANDARD Autor: M. Blaze, A. Keromytis, M. Richardson, L. Sanchez |
| RFC3587 IPv6 Global Unicast Address Format 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. | August 2003 Status: INFORMATIONAL Autor: R. Hinden, S. Deering, E. Nordmark |
| RFC3588 Diameter Base Protocol 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] | September 2003 Status: PROPOSED STANDARD Autor: P. Calhoun, J. Loughney, E. Guttman, G. Zorn, J. Arkko |
| RFC3589 Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5 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. | September 2003 Status: INFORMATIONAL Autor: J. Loughney |
| RFC3590 Source Address Selection for the Multicast Listener Discovery (MLD) Protocol 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] | September 2003 Status: PROPOSED STANDARD Autor: B. Haberman |
| RFC3591 Definitions of Managed Objects for the Optical Interface Type 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] | September 2003 Status: PROPOSED STANDARD Autor: H-K. Lam, M. Stewart, A. Huynh |
| RFC3592 Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing 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] | September 2003 Status: DRAFT STANDARD Autor: K. Tesink |
| RFC3593 Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals 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] | September 2003 Status: DRAFT STANDARD Autor: K. Tesink |
| RFC3594 PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option 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] | September 2003 Status: PROPOSED STANDARD Autor: P. Duffy |
| RFC3595 Textual Conventions for IPv6 Flow Label 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] | September 2003 Status: PROPOSED STANDARD Autor: B. Wijnen |
| RFC3596 DNS Extensions to Support IP Version 6 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] | October 2003 Status: DRAFT STANDARD Autor: S. Thomson, C. Huitema, V. Ksinant, M. Souissi |
| RFC3597 Handling of Unknown DNS Resource Record (RR) Types 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] | September 2003 Status: PROPOSED STANDARD Autor: A. Gustafsson |
| RFC3598 Sieve Email Filtering -- Subaddress Extension 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] | September 2003 Status: PROPOSED STANDARD Autor: K. Murchison |
| RFC3599 Request for Comments Summary RFC Numbers 3500-3599 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. | December 2003 Status: INFORMATIONAL Autor: S. Ginoza |
| RFC3600 Internet Official Protocol Standards 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. | November 2003 Status: HISTORIC Autor: J. Reynolds, S. Ginoza |
| RFC3601 Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 Addresses 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. | September 2003 Status: PROPOSED STANDARD Autor: C. Allocchio |
| RFC3602 The AES-CBC Cipher Algorithm and Its Use with IPsec 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). | September 2003 Status: PROPOSED STANDARD Autor: S. Frankel, R. Glenn, S. Kelly |
| RFC3603 Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture 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. | October 2003 Status: INFORMATIONAL Autor: W. Marshall, F. Andreasen |
| RFC3604 Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3) 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. | October 2003 Status: INFORMATIONAL Autor: H. Khosravi, G. Kullgren, S. Shew, J. Sadler, A. Watanabe |
| RFC3605 Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP) 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. | October 2003 Status: PROPOSED STANDARD Autor: C. Huitema |
| RFC3606 Definitions of Supplemental Managed Objects for ATM Interface 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). | November 2003 Status: PROPOSED STANDARD Autor: F. Ly, M. Noto, A. Smith, E. Spiegel, K. Tesink |
| RFC3607 Chinese Lottery Cryptanalysis Revisited: The Internet as a Codebreaking Tool 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. | September 2003 Status: INFORMATIONAL Autor: M. Leech |
| RFC3608 Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration 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. | October 2003 Status: PROPOSED STANDARD Autor: D. Willis, B. Hoeneisen |
| RFC3609 Tracing Requirements for Generic Tunnels 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. | September 2003 Status: INFORMATIONAL Autor: R. Bonica, K. Kompella, D. Meyer |
| RFC3610 Counter with CBC-MAC (CCM) 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). | September 2003 Status: INFORMATIONAL Autor: D. Whiting, R. Housley, N. Ferguson |
| RFC3611 RTP Control Protocol Extended Reports (RTCP XR) 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. | November 2003 Status: PROPOSED STANDARD Autor: T. Friedman, R. Caceres, A. Clark |
| RFC3612 Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP) 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". | September 2003 Status: INFORMATIONAL Autor: A. Farrel |
| RFC3613 Definition of a Uniform Resource Name (URN) Namespace for the Middleware Architecture Committee for Education (MACE) 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. | October 2003 Status: INFORMATIONAL Autor: R. Morgan, K. Hazelton |
| RFC3614 A Uniform Resource Name (URN) Namespace for the Motion Picture Experts Group (MPEG) 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. | September 2003 Status: INFORMATIONAL Autor: J. Smith |
| RFC3615 A Uniform Resource Name (URN) Namespace for SWIFT Financial Messaging This document describes a Uniform Resource Name (URN) namespace that is managed by SWIFT for usage within messages standardized by SWIFT. | September 2003 Status: INFORMATIONAL Autor: J. Gustin, A. Goyens |
| RFC3616 A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA) 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. | September 2003 Status: INFORMATIONAL Autor: F. Bellifemine, I. Constantinescu, S. Willmott |
| RFC3617 Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial File Transfer Protocol (TFTP) 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. | October 2003 Status: INFORMATIONAL Autor: E. Lear |
| RFC3618 Multicast Source Discovery Protocol (MSDP) 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. | October 2003 Status: EXPERIMENTAL Autor: B. Fenner, D. Meyer |
| RFC3619 Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1 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). | October 2003 Status: INFORMATIONAL Autor: S. Shah, M. Yip |
| RFC3620 The TUNNEL Profile 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. | October 2003 Status: PROPOSED STANDARD Autor: D. New |
| RFC3621 Power Ethernet MIB 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). | December 2003 Status: PROPOSED STANDARD Autor: A. Berger, D. Romascanu |
| RFC3622 A Uniform Resource Name (URN) Namespace for the Liberty Alliance Project This document describes a Uniform Resource Name (URN) namespace that will identify various objects within the Liberty Architecture for federated network identity. | February 2004 Status: INFORMATIONAL Autor: M. Mealling |
| RFC3623 Graceful OSPF Restart 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. | November 2003 Status: PROPOSED STANDARD Autor: J. Moy, P. Pillay-Esnault, A. Lindem |
| RFC3624 The Media Gateway Control Protocol (MGCP) Bulk Audit Package 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. | November 2003 Status: INFORMATIONAL Autor: B. Foster, D. Auerbach, F. Andreasen |
| RFC3625 The QCP File Format and Media Types for Speech Data 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. | September 2003 Status: INFORMATIONAL Autor: R. Gellens, H. Garudadri |
| RFC3626 Optimized Link State Routing Protocol (OLSR) 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. | October 2003 Status: EXPERIMENTAL Autor: T. Clausen, P. Jacquet |
| RFC3627 Use of /127 Prefix Length Between Routers Considered Harmful 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. | September 2003 Status: HISTORIC Autor: P. Savola |
| RFC3628 Policy Requirements for Time-Stamping Authorities (TSAs) 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. | November 2003 Status: INFORMATIONAL Autor: D. Pinkas, N. Pope, J. Ross |
| RFC3629 UTF-8, a transformation format of ISO 10646 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. | November 2003 Status: STANDARD Autor: F. Yergeau |
| RFC3630 Traffic Engineering (TE) Extensions to OSPF Version 2 This document describes extensions to the OSPF protocol version 2 to support intra-area Traffic Engineering (TE), using Opaque Link State Advertisements. | September 2003 Status: PROPOSED STANDARD Autor: D. Katz, K. Kompella, D. Yeung |
| RFC3631 Security Mechanisms for the Internet 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. | December 2003 Status: INFORMATIONAL Autor: S. Bellovin, J. Schiller, C. Kaufman |
| RFC3632 VeriSign Registry Registrar Protocol (RRP) Version 2.0.0 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. | November 2003 Status: INFORMATIONAL Autor: S. Hollenbeck, S. Veeramachaneni, S. Yalamanchilli |
| RFC3633 IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6 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. | December 2003 Status: PROPOSED STANDARD Autor: O. Troan, R. Droms |
| RFC3634 Key Distribution Center (KDC) Server Address Sub-option for the Dynamic Host Configuration Protocol (DHCP) CableLabs Client Configuration (CCC) Option 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. | December 2003 Status: PROPOSED STANDARD Autor: K. Luehrs, R. Woundy, J. Bevilacqua, N. Davoust |
| RFC3635 Definitions of Managed Objects for the Ethernet-like Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing Ethernet-like 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. | September 2003 Status: PROPOSED STANDARD Autor: J. Flick |
| RFC3636 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) 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. | September 2003 Status: PROPOSED STANDARD Autor: J. Flick |
| RFC3637 Definitions of Managed Objects for the Ethernet WAN Interface Sublayer 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. | September 2003 Status: PROPOSED STANDARD Autor: C.M. Heard |
| RFC3638 Applicability Statement for Reclassification of RFC 1643 to Historic Status This memo recommends that RFC 1643 be reclassified as an Historic document and provides the supporting motivation for that recommendation. | September 2003 Status: INFORMATIONAL Autor: J. Flick, C. M. Heard |
| RFC3639 Considerations on the use of a Service Identifier in Packet Headers 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. | October 2003 Status: INFORMATIONAL Autor: M. St. Johns, G. Huston, IAB |
| RFC3640 RTP Payload Format for Transport of MPEG-4 Elementary 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. | November 2003 Status: PROPOSED STANDARD Autor: J. van der Meer, D. Mackie, V. Swaminathan, D. Singer, P. Gentric |
| RFC3641 Generic String Encoding Rules (GSER) for ASN.1 Types 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. | October 2003 Status: PROPOSED STANDARD Autor: S. Legg |
| RFC3642 Common Elements of Generic String Encoding Rules (GSER) Encodings 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. | October 2003 Status: PROPOSED STANDARD Autor: S. Legg |
| RFC3643 Fibre Channel (FC) Frame Encapsulation 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. | December 2003 Status: PROPOSED STANDARD Autor: R. Weber, M. Rajagopal, F. Travostino, M. O'Donnell, C. Monia, M. Merhar |
| RFC3644 Policy Quality of Service (QoS) Information Model 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. | November 2003 Status: PROPOSED STANDARD Autor: Y. Snir, Y. Ramberg, J. Strassner, R. Cohen, B. Moore |
| RFC3645 Generic Security Service Algorithm for Secret Key Transaction Authentication for DNS (GSS-TSIG) 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. | October 2003 Status: PROPOSED STANDARD Autor: S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, R. Hall |
| RFC3646 DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) 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. | December 2003 Status: PROPOSED STANDARD Autor: R. Droms |
| RFC3647 Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework 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. | November 2003 Status: INFORMATIONAL Autor: S. Chokhani, W. Ford, R. Sabett, C. Merrill, S. Wu |
| RFC3648 Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol 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. | December 2003 Status: PROPOSED STANDARD Autor: J. Whitehead, J. Reschke |
| RFC3649 HighSpeed TCP for Large Congestion Windows 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. | December 2003 Status: EXPERIMENTAL Autor: S. Floyd |
| RFC3650 Handle System Overview 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. | November 2003 Status: INFORMATIONAL Autor: S. Sun, L. Lannom, B. Boesch |
| RFC3651 Handle System Namespace and Service Definition 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. | November 2003 Status: INFORMATIONAL Autor: S. Sun, S. Reilly, L. Lannom |
| RFC3652 Handle System Protocol (ver 2.1) Specification 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. | November 2003 Status: INFORMATIONAL Autor: S. Sun, S. Reilly, L. Lannom, J. Petrone |
| RFC3653 XML-Signature XPath Filter 2.0 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. | December 2003 Status: INFORMATIONAL Autor: J. Boyer, M. Hughes, J. Reagle |
| RFC3654 Requirements for Separation of IP Control and Forwarding 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. | November 2003 Status: INFORMATIONAL Autor: H. Khosravi, T. Anderson |
| RFC3655 Redefinition of DNS Authenticated Data (AD) bit 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. | November 2003 Status: PROPOSED STANDARD Autor: B. Wellington, O. Gudmundsson |
| RFC3656 The Mailbox Update (MUPDATE) Distributed Mailbox Database Protocol 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. | December 2003 Status: EXPERIMENTAL Autor: R. Siemborski |
| RFC3657 Use of the Camellia Encryption Algorithm in Cryptographic Message Syntax (CMS) This document specifies the conventions for using the Camellia encryption algorithm for encryption with the Cryptographic Message Syntax (CMS). | January 2004 Status: PROPOSED STANDARD Autor: S. Moriai, A. Kato |
| RFC3658 Delegation Signer (DS) Resource Record (RR) 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. | December 2003 Status: PROPOSED STANDARD Autor: O. Gudmundsson |
| RFC3659 Extensions to FTP This document specifies new FTP commands to obtain listings of remote directories in a defined format, and to permit restarts of interrupted data transfers in STREAM mode. It allows character sets other than US-ASCII, and also defines an optional virtual file storage structure. [STANDARDS-TRACK] | March 2007 Status: PROPOSED STANDARD Autor: P. Hethmon |
| RFC3660 Basic Media Gateway Control Protocol (MGCP) Packages 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. | December 2003 Status: INFORMATIONAL Autor: B. Foster, F. Andreasen |
| RFC3661 Media Gateway Control Protocol (MGCP) Return Code Usage 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. | December 2003 Status: INFORMATIONAL Autor: B. Foster, C. Sivachelvan |
| RFC3662 A Lower Effort Per-Domain Behavior (PDB) for Differentiated Services 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. | December 2003 Status: INFORMATIONAL Autor: R. Bless, K. Nichols, K. Wehrle |
| RFC3663 Domain Administrative Data in Lightweight Directory Access Protocol (LDAP) 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. | December 2003 Status: EXPERIMENTAL Autor: A. Newton |
| RFC3664 The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE) 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. | January 2004 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC3665 Session Initiation Protocol (SIP) Basic Call Flow Examples 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. | December 2003 Status: BEST CURRENT PRACTICE Autor: A. Johnston, S. Donovan, R. Sparks, C. Cunningham, K. Summers |
| RFC3666 Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows 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. | December 2003 Status: BEST CURRENT PRACTICE Autor: A. Johnston, S. Donovan, R. Sparks, C. Cunningham, K. Summers |
| RFC3667 IETF Rights in Contributions 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. | February 2004 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC3668 Intellectual Property Rights in IETF Technology 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. | February 2004 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC3669 Guidelines for Working Groups on Intellectual Property Issues 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. | February 2004 Status: INFORMATIONAL Autor: S. Brim |
| RFC3670 Information Model for Describing Network Device QoS Datapath Mechanisms 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 | January 2004 Status: PROPOSED STANDARD Autor: B. Moore, D. Durham, J. Strassner, A. Westerinen, W. Weiss |
| RFC3671 Collective Attributes in the Lightweight Directory Access Protocol (LDAP) 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. | December 2003 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3672 Subentries in the Lightweight Directory Access Protocol (LDAP) 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). | December 2003 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3673 Lightweight Directory Access Protocol version 3 (LDAPv3): All Operational Attributes 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. | December 2003 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3674 Feature Discovery in Lightweight Directory Access Protocol (LDAP) 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. | December 2003 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3675 .sex Considered Dangerous 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. | February 2004 Status: INFORMATIONAL Autor: D. Eastlake 3rd |
| RFC3676 The Text/Plain Format and DelSp Parameters 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] | February 2004 Status: PROPOSED STANDARD Autor: R. Gellens |
| RFC3677 IETF ISOC Board of Trustee Appointment Procedures This memo outlines the process by which the IETF makes a selection of an Internet Society (ISOC) Board of Trustees appointment. | December 2003 Status: BEST CURRENT PRACTICE Autor: L. Daigle, Internet Architecture Board |
| RFC3678 Socket Interface Extensions for Multicast Source Filters 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. | January 2004 Status: INFORMATIONAL Autor: D. Thaler, B. Fenner, B. Quinn |
| RFC3679 Unused Dynamic Host Configuration Protocol (DHCP) Option Codes 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. | January 2004 Status: INFORMATIONAL Autor: R. Droms |
| RFC3680 A Session Initiation Protocol (SIP) Event Package for Registrations 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] | March 2004 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC3681 Delegation of E.F.F.3.IP6.ARPA 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. | January 2004 Status: BEST CURRENT PRACTICE Autor: R. Bush, R. Fink |
| RFC3682 The Generalized TTL Security Mechanism (GTSM) 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. | February 2004 Status: EXPERIMENTAL Autor: V. Gill, J. Heasley, D. Meyer |
| RFC3683 A Practice for Revoking Posting Rights to IETF Mailing Lists 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. | March 2004 Status: BEST CURRENT PRACTICE Autor: M. Rose |
| RFC3684 Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) 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. | February 2004 Status: EXPERIMENTAL Autor: R. Ogier, F. Templin, M. Lewis |
| RFC3685 SIEVE Email Filtering: Spamtest and VirusTest Extensions 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] | February 2004 Status: PROPOSED STANDARD Autor: C. Daboo |
| RFC3686 Using Advanced Encryption Standard (AES) Counter Mode With IPsec Encapsulating Security Payload (ESP) 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. | January 2004 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC3687 Lightweight Directory Access Protocol (LDAP) and X.500 Component Matching Rules 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] | February 2004 Status: PROPOSED STANDARD Autor: S. Legg |
| RFC3688 The IETF XML Registry 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. | January 2004 Status: BEST CURRENT PRACTICE Autor: M. Mealling |
| RFC3689 General Requirements for Emergency Telecommunication Service (ETS) 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. | February 2004 Status: INFORMATIONAL Autor: K. Carlberg, R. Atkinson |
| RFC3690 IP Telephony Requirements for Emergency Telecommunication Service (ETS) 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. | February 2004 Status: INFORMATIONAL Autor: K. Carlberg, R. Atkinson |
| RFC3691 Internet Message Access Protocol (IMAP) UNSELECT command 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] | February 2004 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC3692 Assigning Experimental and Testing Numbers Considered Useful 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. | January 2004 Status: BEST CURRENT PRACTICE Autor: T. Narten |
| RFC3693 Geopriv Requirements 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. | February 2004 Status: INFORMATIONAL Autor: J. Cuellar, J. Morris, D. Mulligan, J. Peterson, J. Polk |
| RFC3694 Threat Analysis of the Geopriv Protocol 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. | February 2004 Status: INFORMATIONAL Autor: M. Danley, D. Mulligan, J. Morris, J. Peterson |
| RFC3695 Compact Forward Error Correction (FEC) Schemes 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. | February 2004 Status: EXPERIMENTAL Autor: M. Luby, L. Vicisano |
| RFC3696 Application Techniques for Checking and Transformation of Names 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. | February 2004 Status: INFORMATIONAL Autor: J. Klensin |
| RFC3697 IPv6 Flow Label Specification 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] | March 2004 Status: PROPOSED STANDARD Autor: J. Rajahalme, A. Conta, B. Carpenter, S. Deering |
| RFC3698 Lightweight Directory Access Protocol (LDAP): Additional Matching Rules 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] | February 2004 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3700 Internet Official Protocol Standards 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] | July 2004 Status: HISTORIC Autor: J. Reynolds, S. Ginoza |
| RFC3701 6bone (IPv6 Testing Address Allocation) Phaseout 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. | March 2004 Status: INFORMATIONAL Autor: R. Fink, R. Hinden |
| RFC3702 Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP) 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. | February 2004 Status: INFORMATIONAL Autor: J. Loughney, G. Camarillo |
| RFC3703 Policy Core Lightweight Directory Access Protocol (LDAP) Schema 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] | February 2004 Status: PROPOSED STANDARD Autor: J. Strassner, B. Moore, R. Moats, E. Ellesson |
| RFC3704 Ingress Filtering for Multihomed Networks 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. | March 2004 Status: BEST CURRENT PRACTICE Autor: F. Baker, P. Savola |
| RFC3705 High Capacity Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals 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] | February 2004 Status: PROPOSED STANDARD Autor: B. Ray, R. Abbi |
| RFC3706 A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) Peers 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. | February 2004 Status: INFORMATIONAL Autor: G. Huang, S. Beaulieu, D. Rochefort |
| RFC3707 Cross Registry Internet Service Protocol (CRISP) Requirements 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. | February 2004 Status: INFORMATIONAL Autor: A. Newton |
| RFC3708 Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions 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. | February 2004 Status: EXPERIMENTAL Autor: E. Blanton, M. Allman |
| RFC3709 Internet X.509 Public Key Infrastructure: Logotypes in X.509 Certificates This document specifies a certificate extension for including logotypes in public key certificates and attribute certificates. [STANDARDS-TRACK] | February 2004 Status: PROPOSED STANDARD Autor: S. Santesson, R. Housley, T. Freeman |
| RFC3710 An IESG charter 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. | February 2004 Status: INFORMATIONAL Autor: H. Alvestrand |
| RFC3711 The Secure Real-time Transport Protocol (SRTP) 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] | March 2004 Status: PROPOSED STANDARD Autor: M. Baugher, D. McGrew, M. Naslund, E. Carrara, K. Norrman |
| RFC3712 Lightweight Directory Access Protocol (LDAP): Schema for Printer Services 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. | February 2004 Status: INFORMATIONAL Autor: P. Fleming, I. McDonald |
| RFC3713 A Description of the Camellia Encryption Algorithm 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. | April 2004 Status: INFORMATIONAL Autor: M. Matsui, J. Nakajima, S. Moriai |
| RFC3714 IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet 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. | March 2004 Status: INFORMATIONAL Autor: S. Floyd, J. Kempf |
| RFC3715 IPsec-Network Address Translation (NAT) Compatibility Requirements 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. | March 2004 Status: INFORMATIONAL Autor: B. Aboba, W. Dixon |
| RFC3716 The IETF in the Large: Administration and Execution 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. | March 2004 Status: INFORMATIONAL Autor: IAB Advisory Committee |
| RFC3717 IP over Optical Networks: A Framework 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. | March 2004 Status: INFORMATIONAL Autor: B. Rajagopalan, J. Luciani, D. Awduche |
| RFC3718 A Summary of Unicode Consortium Procedures, Policies, Stability, and Public Access 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. | February 2004 Status: INFORMATIONAL Autor: R. McGowan |
| RFC3719 Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS) 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. | February 2004 Status: INFORMATIONAL Autor: J. Parker |
| RFC3720 Internet Small Computer Systems Interface (iSCSI) 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] | April 2004 Status: PROPOSED STANDARD Autor: J. Satran, K. Meth, C. Sapuntzakis, M. Chadalapaka, E. Zeidner |
| RFC3721 Internet Small Computer Systems Interface (iSCSI) Naming and Discovery 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. | April 2004 Status: INFORMATIONAL Autor: M. Bakke, J. Hafner, J. Hufferd, K. Voruganti, M. Krueger |
| RFC3722 String Profile for Internet Small Computer Systems Interface (iSCSI) Names 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] | April 2004 Status: PROPOSED STANDARD Autor: M. Bakke |
| RFC3723 Securing Block Storage Protocols over IP 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] | April 2004 Status: PROPOSED STANDARD Autor: B. Aboba, J. Tseng, J. Walker, V. Rangan, F. Travostino |
| RFC3724 The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture 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. | March 2004 Status: INFORMATIONAL Autor: J. Kempf, R. Austein, IAB |
| RFC3725 Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) 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. | April 2004 Status: BEST CURRENT PRACTICE Autor: J. Rosenberg, J. Peterson, H. Schulzrinne, G. Camarillo |
| RFC3726 Requirements for Signaling Protocols 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. | April 2004 Status: INFORMATIONAL Autor: M. Brunner |
| RFC3727 ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules 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] | February 2004 Status: PROPOSED STANDARD Autor: S. Legg |
| RFC3728 Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL) 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] | February 2004 Status: PROPOSED STANDARD Autor: B. Ray, R. Abbi |
| RFC3729 Application Performance Measurement 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 measuring the application performance as experienced by end-users. [STANDARDS-TRACK] | March 2004 Status: PROPOSED STANDARD Autor: S. Waldbusser |
| RFC3730 Extensible Provisioning Protocol (EPP) 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] | March 2004 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC3731 Extensible Provisioning Protocol (EPP) Domain Name Mapping 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] | March 2004 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC3732 Extensible Provisioning Protocol (EPP) Host Mapping 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] | March 2004 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC3733 Extensible Provisioning Protocol (EPP) Contact Mapping 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] | March 2004 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC3734 Extensible Provisioning Protocol (EPP) Transport Over TCP 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] | March 2004 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC3735 Guidelines for Extending the Extensible Provisioning Protocol (EPP) 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. | March 2004 Status: INFORMATIONAL Autor: S. Hollenbeck |
| RFC3736 Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6 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] | April 2004 Status: PROPOSED STANDARD Autor: R. Droms |
| RFC3737 IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules 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] | April 2004 Status: PROPOSED STANDARD Autor: B. Wijnen, A. Bierman |
| RFC3738 Wave and Equation Based Rate Control (WEBRC) Building Block 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. | April 2004 Status: EXPERIMENTAL Autor: M. Luby, V. Goyal |
| RFC3739 Internet X.509 Public Key Infrastructure: Qualified Certificates Profile 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] | March 2004 Status: PROPOSED STANDARD Autor: S. Santesson, M. Nystrom, T. Polk |
| RFC3740 The Multicast Group Security Architecture 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. | March 2004 Status: INFORMATIONAL Autor: T. Hardjono, B. Weis |
| RFC3741 Exclusive XML Canonicalization, Version 1.0 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. | March 2004 Status: INFORMATIONAL Autor: J. Boyer, D. Eastlake 3rd, J. Reagle |
| RFC3742 Limited Slow-Start for TCP with Large Congestion Windows 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. | March 2004 Status: EXPERIMENTAL Autor: S. Floyd |
| RFC3743 Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean 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. | April 2004 Status: INFORMATIONAL Autor: K. Konishi, K. Huang, H. Qian, Y. Ko |
| RFC3744 Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol 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] | May 2004 Status: PROPOSED STANDARD Autor: G. Clemm, J. Reschke, E. Sedlar, J. Whitehead |
| RFC3745 MIME Type Registrations for JPEG 2000 (ISO/IEC 15444) 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] | April 2004 Status: PROPOSED STANDARD Autor: D. Singer, R. Clark, D. Lee |
| RFC3746 Forwarding and Control Element Separation (ForCES) Framework 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. | April 2004 Status: INFORMATIONAL Autor: L. Yang, R. Dantu, T. Anderson, R. Gopal |
| RFC3747 The Differentiated Services Configuration MIB 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] | April 2004 Status: PROPOSED STANDARD Autor: H. Hazewinkel, D. Partain |
| RFC3748 Extensible Authentication Protocol (EAP) 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] | June 2004 Status: PROPOSED STANDARD Autor: B. Aboba, L. Blunk, J. Vollbrecht, J. Carlson, H. Levkowetz |
| RFC3749 Transport Layer Security Protocol Compression Methods 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] | May 2004 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC3750 Unmanaged Networks IPv6 Transition Scenarios 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. | April 2004 Status: INFORMATIONAL Autor: C. Huitema, R. Austein, S. Satapati, R. van der Pol |
| RFC3751 Omniscience Protocol Requirements 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. | April 2004 Status: INFORMATIONAL Autor: S. Bradner |
| RFC3752 Open Pluggable Edge Services (OPES) Use Cases and Deployment Scenarios 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. | April 2004 Status: INFORMATIONAL Autor: A. Barbir, E. Burger, R. Chen, S. McHenry, H. Orman, R. Penno |
| RFC3753 Mobility Related Terminology 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. | June 2004 Status: INFORMATIONAL Autor: J. Manner, M. Kojo |
| RFC3754 IP Multicast in Differentiated Services (DS) Networks 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. | April 2004 Status: INFORMATIONAL Autor: R. Bless, K. Wehrle |
| RFC3755 Legacy Resolver Compatibility for Delegation Signer (DS) 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] | May 2004 Status: PROPOSED STANDARD Autor: S. Weiler |
| RFC3756 IPv6 Neighbor Discovery (ND) Trust Models and Threats The existing IETF standards specify that IPv6 Neighbor Discovery (ND) and Address Autoconfiguration mechanisms may be protected with IPsec Authentication Header (AH). However, the current specifications limit the security solutions to manual keying due to practical problems faced with automatic key management. This document specifies three different trust models and discusses the threats pertinent to IPv6 Neighbor Discovery. The purpose of this discussion is to define the requirements for Securing IPv6 Neighbor Discovery. This memo provides information for the Internet community. | May 2004 Status: INFORMATIONAL Autor: P. Nikander, J. Kempf, E. Nordmark |
| RFC3757 Domain Name System KEY (DNSKEY) Resource Record (RR) Secure Entry Point (SEP) Flag 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] | April 2004 Status: PROPOSED STANDARD Autor: O. Kolkman, J. Schlyter, E. Lewis |
| RFC3758 Stream Control Transmission Protocol (SCTP) Partial Reliability Extension 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] | May 2004 Status: PROPOSED STANDARD Autor: R. Stewart, M. Ramalho, Q. Xie, M. Tuexen, P. Conrad |
| RFC3759 RObust Header Compression (ROHC): Terminology and Channel Mapping Examples 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. | April 2004 Status: INFORMATIONAL Autor: L-E. Jonsson |
| RFC3760 Securely Available Credentials (SACRED) - Credential Server Framework 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. | April 2004 Status: INFORMATIONAL Autor: D. Gustafson, M. Just, M. Nystrom |
| RFC3761 The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) 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] | April 2004 Status: PROPOSED STANDARD Autor: P. Faltstrom, M. Mealling |
| RFC3762 Telephone Number Mapping (ENUM) Service Registration for H.323 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] | April 2004 Status: PROPOSED STANDARD Autor: O. Levin |
| RFC3763 One-way Active Measurement Protocol (OWAMP) Requirements 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. | April 2004 Status: INFORMATIONAL Autor: S. Shalunov, B. Teitelbaum |
| RFC3764 enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record 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] | April 2004 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3765 NOPEER Community for Border Gateway Protocol (BGP) Route Scope Control 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. | April 2004 Status: INFORMATIONAL Autor: G. Huston |
| RFC3766 Determining Strengths For Public Keys Used For Exchanging Symmetric Keys 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. | April 2004 Status: BEST CURRENT PRACTICE Autor: H. Orman, P. Hoffman |
| RFC3767 Securely Available Credentials Protocol 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] | June 2004 Status: PROPOSED STANDARD Autor: S. Farrell |
| RFC3768 Virtual Router Redundancy Protocol (VRRP) 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] | April 2004 Status: DRAFT STANDARD Autor: R. Hinden |
| RFC3769 Requirements for IPv6 Prefix Delegation 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. | June 2004 Status: INFORMATIONAL Autor: S. Miyakawa, R. Droms |
| RFC3770 Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN) 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] | May 2004 Status: PROPOSED STANDARD Autor: R. Housley, T. Moore |
| RFC3771 The Lightweight Directory Access Protocol (LDAP) Intermediate Response Message 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] | April 2004 Status: PROPOSED STANDARD Autor: R. Harrison, K. Zeilenga |
| RFC3772 Point-to-Point Protocol (PPP) Vendor Protocol 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] | May 2004 Status: PROPOSED STANDARD Autor: J. Carlson, R. Winslow |
| RFC3773 High-Level Requirements for Internet Voice Mail 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. | June 2004 Status: INFORMATIONAL Autor: E. Candell |
| RFC3774 IETF Problem Statement 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. | May 2004 Status: INFORMATIONAL Autor: E. Davies |
| RFC3775 Mobility Support in IPv6 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] | June 2004 Status: PROPOSED STANDARD Autor: D. Johnson, C. Perkins, J. Arkko |
| RFC3776 Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents 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] | June 2004 Status: PROPOSED STANDARD Autor: J. Arkko, V. Devarapalli, F. Dupont |
| RFC3777 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees The process by which the members of the IAB and IESG are selected, confirmed, and recalled is specified. This document 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. | June 2004 Status: BEST CURRENT PRACTICE Autor: J. Galvin |
| RFC3778 The application/pdf Media Type 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. | May 2004 Status: INFORMATIONAL Autor: E. Taft, J. Pravetz, S. Zilles, L. Masinter |
| RFC3779 X.509 Extensions for IP Addresses and AS Identifiers 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] | June 2004 Status: PROPOSED STANDARD Autor: C. Lynn, S. Kent, K. Seo |
| RFC3780 SMIng - Next Generation Structure of Management Information 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. | May 2004 Status: EXPERIMENTAL Autor: F. Strauss, J. Schoenwaelder |
| RFC3781 Next Generation Structure of Management Information (SMIng) Mappings to the Simple Network Management Protocol (SNMP) 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. | May 2004 Status: EXPERIMENTAL Autor: F. Strauss, J. Schoenwaelder |
| RFC3782 The NewReno Modification to TCP's Fast Recovery Algorithm 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] | April 2004 Status: PROPOSED STANDARD Autor: S. Floyd, T. Henderson, A. Gurtov |
| RFC3783 Small Computer Systems Interface (SCSI) Command Ordering Considerations with 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. | May 2004 Status: INFORMATIONAL Autor: M. Chadalapaka, R. Elliott |
| RFC3784 Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE) 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. | June 2004 Status: INFORMATIONAL Autor: H. Smit, T. Li |
| RFC3785 Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric 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. | May 2004 Status: BEST CURRENT PRACTICE Autor: F. Le Faucheur, R. Uppili, A. Vedrenne, P. Merckx, T. Telkamp |
| RFC3786 Extending the Number of Intermediate System to Intermediate System (IS-IS) Link State PDU (LSP) Fragments Beyond the 256 Limit 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. | May 2004 Status: INFORMATIONAL Autor: A. Hermelin, S. Previdi, M. Shand |
| RFC3787 Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS) 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. | May 2004 Status: INFORMATIONAL Autor: J. Parker |
| RFC3788 Security Considerations for Signaling Transport (SIGTRAN) Protocols 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] | June 2004 Status: PROPOSED STANDARD Autor: J. Loughney, M. Tuexen, J. Pastor-Balbas |
| RFC3789 Introduction to the Survey of IPv4 Addresses in Currently Deployed IETF Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: P. Nesser, II, A. Bergstrom |
| RFC3790 Survey of IPv4 Addresses in Currently Deployed IETF Internet Area Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: C. Mickles, P. Nesser, II |
| RFC3791 Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: C. Olvera, P. Nesser, II |
| RFC3792 Survey of IPv4 Addresses in Currently Deployed IETF Security Area Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: P. Nesser, II, A. Bergstrom |
| RFC3793 Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: P. Nesser, II, A. Bergstrom |
| RFC3794 Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: P. Nesser, II, A. Bergstrom |
| RFC3795 Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: R. Sofia, P. Nesser, II |
| RFC3796 Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents 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. | June 2004 Status: INFORMATIONAL Autor: P. Nesser, II, A. Bergstrom |
| RFC3797 Publicly Verifiable Nominations Committee (NomCom) Random Selection 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. | June 2004 Status: INFORMATIONAL Autor: D. Eastlake 3rd |
| RFC3798 Message Disposition Notification 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] | May 2004 Status: DRAFT STANDARD Autor: T. Hansen, G. Vaudreuil |
| RFC3801 Voice Profile for Internet Mail - version 2 (VPIMv2) 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] | June 2004 Status: DRAFT STANDARD Autor: G. Vaudreuil, G. Parsons |
| RFC3802 Toll Quality Voice - 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM) MIME Sub-type Registration 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] | June 2004 Status: DRAFT STANDARD Autor: G. Vaudreuil, G. Parsons |
| RFC3803 Content Duration MIME Header Definition 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] | June 2004 Status: DRAFT STANDARD Autor: G. Vaudreuil, G. Parsons |
| RFC3804 Voice Profile for Internet Mail (VPIM) Addressing 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] | June 2004 Status: PROPOSED STANDARD Autor: G. Parsons |
| RFC3805 Printer MIB v2 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] | June 2004 Status: PROPOSED STANDARD Autor: R. Bergman, H. Lewis, I. McDonald |
| RFC3806 Printer Finishing MIB 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. | June 2004 Status: INFORMATIONAL Autor: R. Bergman, H. Lewis, I. McDonald |
| RFC3807 V5.2-User Adaptation Layer (V5UA) 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] | June 2004 Status: PROPOSED STANDARD Autor: E. Weilandt, N. Khanchandani, S. Rao |
| RFC3808 IANA Charset MIB 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. | June 2004 Status: INFORMATIONAL Autor: I. McDonald |
| RFC3809 Generic Requirements for Provider Provisioned Virtual Private Networks (PPVPN) 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. | June 2004 Status: INFORMATIONAL Autor: A. Nagarajan |
| RFC3810 Multicast Listener Discovery Version 2 (MLDv2) for IPv6 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] | June 2004 Status: PROPOSED STANDARD Autor: R. Vida, L. Costa |
| RFC3811 Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management 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] | June 2004 Status: PROPOSED STANDARD Autor: T. Nadeau, J. Cucchiara |
| RFC3812 Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (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 Multiprotocol Label Switching (MPLS) based traffic engineering (TE). [STANDARDS-TRACK] | June 2004 Status: PROPOSED STANDARD Autor: C. Srinivasan, A. Viswanathan, T. Nadeau |
| RFC3813 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (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 describes managed objects to configure and/or monitor a Multiprotocol Label Switching (MPLS) Label Switching Router (LSR). [STANDARDS-TRACK] | June 2004 Status: PROPOSED STANDARD Autor: C. Srinivasan, A. Viswanathan, T. Nadeau |
| RFC3814 Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (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 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] | June 2004 Status: PROPOSED STANDARD Autor: T. Nadeau, C. Srinivasan, A. Viswanathan |
| RFC3815 Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP) 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] | June 2004 Status: PROPOSED STANDARD Autor: J. Cucchiara, H. Sjostrand, J. Luciani |
| RFC3816 Definitions of Managed Objects for RObust Header Compression (ROHC) 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] | June 2004 Status: PROPOSED STANDARD Autor: J. Quittek, M. Stiemerling, H. Hartenstein |
| RFC3817 Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE) 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. | June 2004 Status: INFORMATIONAL Autor: W. Townsley, R. da Silva |
| RFC3818 IANA Considerations for the Point-to-Point Protocol (PPP) 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. | June 2004 Status: BEST CURRENT PRACTICE Autor: V. Schryver |
| RFC3819 Advice for Internet Subnetwork Designers 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. | July 2004 Status: BEST CURRENT PRACTICE Autor: P. Karn, C. Bormann, G. Fairhurst, D. Grossman, R. Ludwig, J. Mahdavi, G. Montenegro, J. Touch, L. Wood |
| RFC3820 Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate Profile 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] | June 2004 Status: PROPOSED STANDARD Autor: S. Tuecke, V. Welch, D. Engert, L. Pearlman, M. Thompson |
| RFC3821 Fibre Channel Over TCP/IP (FCIP) 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] | July 2004 Status: PROPOSED STANDARD Autor: M. Rajagopal, E. Rodriguez, R. Weber |
| RFC3822 Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2) This document defines the use of Service Location Protocol version 2 (SLPv2) by Fibre Channel over TCP/IP (FCIP) Entities. [STANDARDS-TRACK] | July 2004 Status: PROPOSED STANDARD Autor: D. Peterson |
| RFC3823 MIME Media Type for the Systems Biology Markup Language (SBML) 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. | June 2004 Status: INFORMATIONAL Autor: B. Kovitz |
| RFC3824 Using E.164 numbers with the Session Initiation Protocol (SIP) 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. | June 2004 Status: INFORMATIONAL Autor: J. Peterson, H. Liu, J. Yu, B. Campbell |
| RFC3825 Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information 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] | July 2004 Status: PROPOSED STANDARD Autor: J. Polk, J. Schnizlein, M. Linsner |
| RFC3826 The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model 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] | June 2004 Status: PROPOSED STANDARD Autor: U. Blumenthal, F. Maino, K. McCloghrie |
| RFC3827 Additional Snoop Datalink Types 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. | June 2004 Status: INFORMATIONAL Autor: K. Sarcar |
| RFC3828 The Lightweight User Datagram Protocol (UDP-Lite) 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] | July 2004 Status: PROPOSED STANDARD Autor: L-A. Larzon, M. Degermark, S. Pink, L-E. Jonsson, G. Fairhurst |
| RFC3829 Lightweight Directory Access Protocol (LDAP) Authorization Identity Request and Response Controls 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. | July 2004 Status: INFORMATIONAL Autor: R. Weltman, M. Smith, M. Wahl |
| RFC3830 MIKEY: Multimedia Internet KEYing 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Arkko, E. Carrara, F. Lindholm, M. Naslund, K. Norrman |
| RFC3831 Transmission of IPv6 Packets over Fibre Channel 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] | July 2004 Status: PROPOSED STANDARD Autor: C. DeSanti |
| RFC3832 Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRV 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. | July 2004 Status: EXPERIMENTAL Autor: W. Zhao, H. Schulzrinne, E. Guttman, C. Bisdikian, W. Jerome |
| RFC3833 Threat Analysis of the Domain Name System (DNS) 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. | August 2004 Status: INFORMATIONAL Autor: D. Atkins, R. Austein |
| RFC3834 Recommendations for Automatic Responses to Electronic Mail 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] | August 2004 Status: PROPOSED STANDARD Autor: K. Moore |
| RFC3835 An Architecture for Open Pluggable Edge Services (OPES) 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. | August 2004 Status: INFORMATIONAL Autor: A. Barbir, R. Penno, R. Chen, M. Hofmann, H. Orman |
| RFC3836 Requirements for Open Pluggable Edge Services (OPES) Callout Protocols 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. | August 2004 Status: INFORMATIONAL Autor: A. Beck, M. Hofmann, H. Orman, R. Penno, A. Terzis |
| RFC3837 Security Threats and Risks for Open Pluggable Edge Services (OPES) 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. | August 2004 Status: INFORMATIONAL Autor: A. Barbir, O. Batuner, B. Srinivas, M. Hofmann, H. Orman |
| RFC3838 Policy, Authorization, and Enforcement Requirements of the Open Pluggable Edge Services (OPES) 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. | August 2004 Status: INFORMATIONAL Autor: A. Barbir, O. Batuner, A. Beck, T. Chan, H. Orman |
| RFC3839 MIME Type Registrations for 3rd Generation Partnership Project (3GPP) Multimedia files 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] | July 2004 Status: PROPOSED STANDARD Autor: R. Castagno, D. Singer |
| RFC3840 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne, P. Kyzivat |
| RFC3841 Caller Preferences for the Session Initiation Protocol (SIP) 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne, P. Kyzivat |
| RFC3842 A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP) 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] | August 2004 Status: PROPOSED STANDARD Autor: R. Mahy |
| RFC3843 RObust Header Compression (ROHC): A Compression Profile for IP 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] | June 2004 Status: PROPOSED STANDARD Autor: L-E. Jonsson, G. Pelletier |
| RFC3844 IETF Problem Resolution Process 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. | August 2004 Status: INFORMATIONAL Autor: E. Davies, J. Hofmann |
| RFC3845 DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Schlyter |
| RFC3846 Mobile IPv4 Extension for Carrying Network Access Identifiers 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] | June 2004 Status: PROPOSED STANDARD Autor: F. Johansson, T. Johansson |
| RFC3847 Restart Signaling for Intermediate System to Intermediate System (IS-IS) 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. | July 2004 Status: INFORMATIONAL Autor: M. Shand, L. Ginsberg |
| RFC3848 ESMTP and LMTP Transmission Types Registration 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] | July 2004 Status: DRAFT STANDARD Autor: C. Newman |
| RFC3849 IPv6 Address Prefix Reserved for Documentation 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. | July 2004 Status: INFORMATIONAL Autor: G. Huston, A. Lord, P. Smith |
| RFC3850 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling 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] | July 2004 Status: PROPOSED STANDARD Autor: B. Ramsdell |
| RFC3851 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification 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] | July 2004 Status: PROPOSED STANDARD Autor: B. Ramsdell |
| RFC3852 Cryptographic Message Syntax (CMS) This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. [STANDARDS-TRACK] | July 2004 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC3853 S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP) 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] | July 2004 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3854 Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME) 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] | July 2004 Status: PROPOSED STANDARD Autor: P. Hoffman, C. Bonatti, A. Eggen |
| RFC3855 Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400 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] | July 2004 Status: PROPOSED STANDARD Autor: P. Hoffman, C. Bonatti |
| RFC3856 A Presence Event Package for the Session Initiation Protocol (SIP) 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC3857 A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP) 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC3858 An Extensible Markup Language (XML) Based Format for Watcher Information 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC3859 Common Profile for Presence (CPP) 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3860 Common Profile for Instant Messaging (CPIM) 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3861 Address Resolution for Instant Messaging and Presence 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] | August 2004 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3862 Common Presence and Instant Messaging (CPIM): Message Format 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] | August 2004 Status: PROPOSED STANDARD Autor: G. Klyne, D. Atkins |
| RFC3863 Presence Information Data Format (PIDF) 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] | August 2004 Status: PROPOSED STANDARD Autor: H. Sugano, S. Fujimoto, G. Klyne, A. Bateman, W. Carr, J. Peterson |
| RFC3864 Registration Procedures for Message Header Fields 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. | September 2004 Status: BEST CURRENT PRACTICE Autor: G. Klyne, M. Nottingham, J. Mogul |
| RFC3865 A No Soliciting Simple Mail Transfer Protocol (SMTP) Service Extension 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] | September 2004 Status: PROPOSED STANDARD Autor: C. Malamud |
| RFC3866 Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP) 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] | July 2004 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3867 Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP) 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. | November 2004 Status: INFORMATIONAL Autor: Y. Kawatsura, M. Hiroya, H. Beykirch |
| RFC3868 Signalling Connection Control Part User Adaptation Layer (SUA) 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] | October 2004 Status: PROPOSED STANDARD Autor: J. Loughney, G. Sidebottom, L. Coene, G. Verwimp, J. Keller, B. Bidulock |
| RFC3869 IAB Concerns and Recommendations Regarding Internet Research and Evolution 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. | August 2004 Status: INFORMATIONAL Autor: R. Atkinson, S. Floyd, Internet Architecture Board |
| RFC3870 application/rdf+xml Media Type Registration 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. | September 2004 Status: INFORMATIONAL Autor: A. Swartz |
| RFC3871 Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure 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. | September 2004 Status: INFORMATIONAL Autor: G. Jones |
| RFC3872 Management Information Base for Telephony Routing over IP (TRIP) 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] | September 2004 Status: PROPOSED STANDARD Autor: D. Zinman, D. Walker, J. Jiang |
| RFC3873 Stream Control Transmission Protocol (SCTP) Management Information Base (MIB) 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. | September 2004 Status: PROPOSED STANDARD Autor: J. Pastor, M. Belinchon |
| RFC3874 A 224-bit One-way Hash Function: SHA-224 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. | September 2004 Status: INFORMATIONAL Autor: R. Housley |
| RFC3875 The Common Gateway Interface (CGI) Version 1.1 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. | October 2004 Status: INFORMATIONAL Autor: D. Robinson, K. Coar |
| RFC3876 Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3) 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] | September 2004 Status: PROPOSED STANDARD Autor: D. Chadwick, S. Mullan |
| RFC3877 Alarm Management Information Base (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] | September 2004 Status: PROPOSED STANDARD Autor: S. Chisholm, D. Romascanu |
| RFC3878 Alarm Reporting Control Management Information Base (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 controlling the reporting of alarm conditions. [STANDARDS-TRACK] | September 2004 Status: PROPOSED STANDARD Autor: H. Lam, A. Huynh, D. Perkins |
| RFC3879 Deprecating Site Local Addresses 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] | September 2004 Status: PROPOSED STANDARD Autor: C. Huitema, B. Carpenter |
| RFC3880 Call Processing Language (CPL): A Language for User Control of Internet Telephony Services 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] | October 2004 Status: PROPOSED STANDARD Autor: J. Lennox, X. Wu, H. Schulzrinne |
| RFC3881 Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications This document defines the format of data to be collected and minimum set of attributes that need to be captured for security auditing in healthcare application systems. The format is defined as an XML schema, which is intended as a reference for healthcare standards developers and application designers. It consolidates several previous documents on security auditing of healthcare data. This memo provides information for the Internet community. | September 2004 Status: INFORMATIONAL Autor: G. Marshall |
| RFC3882 Configuring BGP to Block Denial-of-Service Attacks 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. | September 2004 Status: INFORMATIONAL Autor: D. Turk |
| RFC3883 Detecting Inactive Neighbors over OSPF Demand Circuits (DC) 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] | October 2004 Status: PROPOSED STANDARD Autor: S. Rao, A. Zinin, A. Roy |
| RFC3884 Use of IPsec Transport Mode for Dynamic Routing 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. | September 2004 Status: INFORMATIONAL Autor: J. Touch, L. Eggert, Y. Wang |
| RFC3885 SMTP Service Extension for Message Tracking This memo defines an extension to the SMTP service whereby a client may mark a message for future tracking. [STANDARDS-TRACK] | September 2004 Status: PROPOSED STANDARD Autor: E. Allman, T. Hansen |
| RFC3886 An Extensible Message Format for Message Tracking Responses 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. | September 2004 Status: PROPOSED STANDARD Autor: E. Allman |
| RFC3887 Message Tracking Query Protocol 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] | September 2004 Status: PROPOSED STANDARD Autor: T. Hansen |
| RFC3888 Message Tracking Model and Requirements 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. | September 2004 Status: INFORMATIONAL Autor: T. Hansen |
| RFC3890 A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP) This document defines a Session Description Protocol (SDP) Transport Independent Application Specific Maximum (TIAS) bandwidth modifier that does not include transport overhead; instead an additional packet rate attribute is defined. The transport independent bit-rate value together with the maximum packet rate can then be used to calculate the real bit-rate over the transport actually used. | September 2004 Status: PROPOSED STANDARD Autor: M. Westerlund |
| RFC3891 The Session Initiation Protocol (SIP) "Replaces" Header 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] | September 2004 Status: PROPOSED STANDARD Autor: R. Mahy, B. Biggs, R. Dean |
| RFC3892 The Session Initiation Protocol (SIP) Referred-By Mechanism 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] | September 2004 Status: PROPOSED STANDARD Autor: R. Sparks |
| RFC3893 Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format 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] | September 2004 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3894 Sieve Extension: Copying Without Side Effects 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. | October 2004 Status: PROPOSED STANDARD Autor: J. Degener |
| RFC3895 Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it 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] | September 2004 Status: PROPOSED STANDARD Autor: O. Nicklass |
| RFC3896 Definitions of Managed Objects for the DS3/E3 Interface Type 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] | September 2004 Status: PROPOSED STANDARD Autor: O. Nicklass |
| RFC3897 Open Pluggable Edge Services (OPES) Entities and End Points Communication This memo documents tracing and non-blocking (bypass) requirements for Open Pluggable Edge Services (OPES). This memo provides information for the Internet community. | September 2004 Status: INFORMATIONAL Autor: A. Barbir |
| RFC3898 Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) 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] | October 2004 Status: PROPOSED STANDARD Autor: V. Kalusivalingam |
| RFC3901 DNS IPv6 Transport Operational Guidelines 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. | September 2004 Status: BEST CURRENT PRACTICE Autor: A. Durand, J. Ihren |
| RFC3902 The "application/soap+xml" media type 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. | September 2004 Status: INFORMATIONAL Autor: M. Baker, M. Nottingham |
| RFC3903 Session Initiation Protocol (SIP) Extension for Event State Publication 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. 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] | October 2004 Status: PROPOSED STANDARD Autor: A. Niemi |
| RFC3904 Evaluation of IPv6 Transition Mechanisms for Unmanaged Networks 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. | September 2004 Status: INFORMATIONAL Autor: C. Huitema, R. Austein, S. Satapati, R. van der Pol |
| RFC3905 A Template for IETF Patent Disclosures and Licensing Declarations 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. | September 2004 Status: INFORMATIONAL Autor: V. See |
| RFC3906 Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels 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. | October 2004 Status: INFORMATIONAL Autor: N. Shen, H. Smit |
| RFC3909 Lightweight Directory Access Protocol (LDAP) Cancel 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] | October 2004 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC3910 The SPIRITS (Services in PSTN requesting Internet Services) Protocol 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] | October 2004 Status: PROPOSED STANDARD Autor: V. Gurbani, A. Brusilovsky, I. Faynberg, J. Gato, H. Lu, M. Unmehopa |
| RFC3911 The Session Initiation Protocol (SIP) "Join" Header 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] | October 2004 Status: PROPOSED STANDARD Autor: R. Mahy, D. Petrie |
| RFC3912 WHOIS Protocol Specification 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] | September 2004 Status: DRAFT STANDARD Autor: L. Daigle |
| RFC3913 Border Gateway Multicast Protocol (BGMP): Protocol Specification 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. | September 2004 Status: HISTORIC Autor: D. Thaler |
| RFC3914 Open Pluggable Edge Services (OPES) Treatment of IAB Considerations 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. | October 2004 Status: INFORMATIONAL Autor: A. Barbir, A. Rousskov |
| RFC3915 Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP) 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] | September 2004 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC3916 Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3) 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. | September 2004 Status: INFORMATIONAL Autor: X. Xiao, D. McPherson, P. Pate |
| RFC3917 Requirements for IP Flow Information Export (IPFIX) 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. | October 2004 Status: INFORMATIONAL Autor: J. Quittek, T. Zseby, B. Claise, S. Zander |
| RFC3918 Methodology for IP Multicast Benchmarking 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. | October 2004 Status: INFORMATIONAL Autor: D. Stopp, B. Hickman |
| RFC3919 Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS) 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]. | October 2004 Status: INFORMATIONAL Autor: E. Stephan, J. Palet |
| RFC3920 Extensible Messaging and Presence Protocol (XMPP): Core 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] | October 2004 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC3921 Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence 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] | October 2004 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC3922 Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM) This memo describes a mapping between the Extensible Messaging and Presence Protocol (XMPP) and the Common Presence and Instant Messaging (CPIM) specifications. [STANDARDS-TRACK] | October 2004 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC3923 End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP) This memo defines methods of end-to-end signing and object encryption for the Extensible Messaging and Presence Protocol (XMPP). [STANDARDS-TRACK] | October 2004 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC3924 Cisco Architecture for Lawful Intercept in IP Networks 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. | October 2004 Status: INFORMATIONAL Autor: F. Baker, B. Foster, C. Sharp |
| RFC3925 Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) 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] | October 2004 Status: PROPOSED STANDARD Autor: J. Littlefield |
| RFC3926 FLUTE - File Delivery over Unidirectional Transport 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. | October 2004 Status: EXPERIMENTAL Autor: T. Paila, M. Luby, R. Lehtonen, V. Roca, R. Walsh |
| RFC3927 Dynamic Configuration of IPv4 Link-Local Addresses To participate in wide-area IP networking, a host needs to be configured with IP addresses for its interfaces, either manually by the user or automatically from a source on the network such as a Dynamic Host Configuration Protocol (DHCP) server. Unfortunately, such address configuration information may not always be available. It is therefore beneficial for a host to be able to depend on a useful subset of IP networking functions even when no address configuration is available. This document describes how a host may automatically configure an interface with an IPv4 address within the 169.254/16 prefix that is valid for communication with other devices connected to the same physical (or logical) link. | May 2005 Status: PROPOSED STANDARD Autor: S. Cheshire, B. Aboba, E. Guttman |
| RFC3928 Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP) 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] | October 2004 Status: PROPOSED STANDARD Autor: R. Megginson, M. Smith, O. Natkovich, J. Parham |
| RFC3929 Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF 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. | October 2004 Status: EXPERIMENTAL Autor: T. Hardie |
| RFC3930 The Protocol versus Document Points of View in Computer Protocols 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. | October 2004 Status: INFORMATIONAL Autor: D. Eastlake 3rd |
| RFC3931 Layer Two Tunneling Protocol - Version 3 (L2TPv3) 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] | March 2005 Status: PROPOSED STANDARD Autor: J. Lau, M. Townsley, I. Goyret |
| RFC3932 The IESG and RFC Editor Documents: Procedures 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. | October 2004 Status: BEST CURRENT PRACTICE Autor: H. Alvestrand |
| RFC3933 A Model for IETF Process Experiments 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. 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. | November 2004 Status: BEST CURRENT PRACTICE Autor: J. Klensin, S. Dawkins |
| RFC3934 Updates to RFC 2418 Regarding the Management of IETF Mailing Lists 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. | October 2004 Status: BEST CURRENT PRACTICE Autor: M. Wasserman |
| RFC3935 A Mission Statement for the IETF 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. | October 2004 Status: BEST CURRENT PRACTICE Autor: H. Alvestrand |
| RFC3936 Procedures for Modifying the Resource reSerVation Protocol (RSVP) 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. | October 2004 Status: BEST CURRENT PRACTICE Autor: K. Kompella, J. Lang |
| RFC3937 A Uniform Resource Name (URN) Namespace for the International Press Telecommunications Council (IPTC) 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. | October 2004 Status: INFORMATIONAL Autor: M. Steidl |
| RFC3938 Video-Message Message-Context 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". A receiving user agent (UA) may use this information as a hint to optimally present the message. [STANDARDS-TRACK] | October 2004 Status: PROPOSED STANDARD Autor: T. Hansen |
| RFC3939 Calling Line Identification for Voice Mail Messages 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] | December 2004 Status: PROPOSED STANDARD Autor: G. Parsons, J. Maruszak |
| RFC3940 Negative-acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Protocol 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. | November 2004 Status: EXPERIMENTAL Autor: B. Adamson, C. Bormann, M. Handley, J. Macker |
| RFC3941 Negative-Acknowledgment (NACK)-Oriented Reliable Multicast (NORM) Building Blocks 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. | November 2004 Status: EXPERIMENTAL Autor: B. Adamson, C. Bormann, M. Handley, J. Macker |
| RFC3942 Reclassifying Dynamic Host Configuration Protocol version 4 (DHCPv4) Options 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] | November 2004 Status: PROPOSED STANDARD Autor: B. Volz |
| RFC3943 Transport Layer Security (TLS) Protocol Compression Using Lempel-Ziv-Stac (LZS) 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. | November 2004 Status: INFORMATIONAL Autor: R. Friend |
| RFC3944 H.350 Directory Services 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. 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. | December 2004 Status: INFORMATIONAL Autor: T. Johnson, S. Okubo, S. Campos |
| RFC3945 Generalized Multi-Protocol Label Switching (GMPLS) Architecture 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. | October 2004 Status: PROPOSED STANDARD Autor: E. Mannie |
| RFC3946 Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control 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] | October 2004 Status: PROPOSED STANDARD Autor: E. Mannie, D. Papadimitriou |
| RFC3947 Negotiation of NAT-Traversal in the IKE 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] | January 2005 Status: PROPOSED STANDARD Autor: T. Kivinen, B. Swander, A. Huttunen, V. Volpe |
| RFC3948 UDP Encapsulation of IPsec ESP Packets 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] | January 2005 Status: PROPOSED STANDARD Autor: A. Huttunen, B. Swander, V. Volpe, L. DiBurro, M. Stenberg |
| RFC3949 File Format for Internet Fax 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. | February 2005 Status: DRAFT STANDARD Autor: R. Buckley, D. Venable, L. McIntyre, G. Parsons, J. Rafferty |
| RFC3950 Tag Image File Format Fax eXtended (TIFF-FX) - image/tiff-fx MIME Sub-type Registration 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] | February 2005 Status: DRAFT STANDARD Autor: L. McIntyre, G. Parsons, J. Rafferty |
| RFC3951 Internet Low Bit Rate Codec (iLBC) 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. | December 2004 Status: EXPERIMENTAL Autor: S. Andersen, A. Duric, H. Astrom, R. Hagen, W. Kleijn, J. Linden |
| RFC3952 Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech 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. | December 2004 Status: EXPERIMENTAL Autor: A. Duric, S. Andersen |
| RFC3953 Telephone Number Mapping (ENUM) Service Registration for Presence Services This document registers a Telephone Number Mapping (ENUM) service for presence. Specifically, this document focuses on provisioning pres URIs in ENUM. [STANDARDS-TRACK] | January 2005 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC3954 Cisco Systems NetFlow Services Export Version 9 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. | October 2004 Status: INFORMATIONAL Autor: B. Claise |
| RFC3955 Evaluation of Candidate Protocols for IP Flow Information Export (IPFIX) 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. | October 2004 Status: INFORMATIONAL Autor: S. Leinen |
| RFC3956 Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address 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] | November 2004 Status: PROPOSED STANDARD Autor: P. Savola, B. Haberman |
| RFC3957 Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4 Authentication, Authorization, and Accounting (AAA) servers, such as RADIUS and DIAMETER, are in use within the Internet today to provide authentication and authorization services for dial-up computers. Mobile IP for IPv4 requires strong authentication between the mobile node and its home agent. When the mobile node shares an AAA Security Association with its home AAA server, however, it is possible to use that AAA Security Association to create derived Mobility Security Associations between the mobile node and its home agent, and again between the mobile node and the foreign agent currently offering connectivity to the mobile node. This document specifies extensions to Mobile IP registration messages that can be used to create Mobility Security Associations between the mobile node and its home agent, and/or between the mobile node and a foreign agent. [STANDARDS-TRACK] | March 2005 Status: PROPOSED STANDARD Autor: C. Perkins, P. Calhoun |
| RFC3958 Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS) 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] | January 2005 Status: PROPOSED STANDARD Autor: L. Daigle, A. Newton |
| RFC3959 The Early Session Disposition Type for the Session Initiation Protocol (SIP) 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] | December 2004 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC3960 Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP) 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. | December 2004 Status: INFORMATIONAL Autor: G. Camarillo, H. Schulzrinne |
| RFC3961 Encryption and Checksum Specifications for Kerberos 5 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] | February 2005 Status: PROPOSED STANDARD Autor: K. Raeburn |
| RFC3962 Advanced Encryption Standard (AES) Encryption for Kerberos 5 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] | February 2005 Status: PROPOSED STANDARD Autor: K. Raeburn |
| RFC3963 Network Mobility (NEMO) Basic Support Protocol 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] | January 2005 Status: PROPOSED STANDARD Autor: V. Devarapalli, R. Wakikawa, A. Petrescu, P. Thubert |
| RFC3964 Security Considerations for 6to4 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. | December 2004 Status: INFORMATIONAL Autor: P. Savola, C. Patel |
| RFC3965 A Simple Mode of Facsimile Using Internet 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. | December 2004 Status: DRAFT STANDARD Autor: K. Toyoda, H. Ohno, J. Murai, D. Wing |
| RFC3966 The tel URI for Telephone Numbers 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] | December 2004 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC3967 Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level 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. | December 2004 Status: BEST CURRENT PRACTICE Autor: R. Bush, T. Narten |
| RFC3968 The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP) 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. | December 2004 Status: BEST CURRENT PRACTICE Autor: G. Camarillo |
| RFC3969 The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP) 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. | December 2004 Status: BEST CURRENT PRACTICE Autor: G. Camarillo |
| RFC3970 A Traffic Engineering (TE) 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 Traffic Engineered (TE) Tunnels; for example, Multi-Protocol Label Switched Paths. [STANDARDS-TRACK] | January 2005 Status: PROPOSED STANDARD Autor: K. Kompella |
| RFC3971 SEcure Neighbor Discovery (SEND) 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] | March 2005 Status: PROPOSED STANDARD Autor: J. Arkko, J. Kempf, B. Zill, P. Nikander |
| RFC3972 Cryptographically Generated Addresses (CGA) 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] | March 2005 Status: PROPOSED STANDARD Autor: T. Aura |
| RFC3973 Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised) 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. | January 2005 Status: EXPERIMENTAL Autor: A. Adams, J. Nicholas, W. Siadak |
| RFC3974 SMTP Operational Experience in Mixed IPv4/v6 Environments 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. | January 2005 Status: INFORMATIONAL Autor: M. Nakamura, J. Hagino |
| RFC3975 OMA-IETF Standardization Collaboration 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. | January 2005 Status: INFORMATIONAL Autor: G. Huston, I. Leuca |
| RFC3976 Interworking SIP and Intelligent Network (IN) Applications 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. | January 2005 Status: INFORMATIONAL Autor: V. K. Gurbani, F. Haerens, V. Rastogi |
| RFC3977 Network News Transfer Protocol (NNTP) The Network News Transfer Protocol (NNTP) has been in use in the Internet for a decade, and remains one of the most popular protocols (by volume) in use today. This document is a replacement for RFC 977, and officially updates the protocol specification. It clarifies some vagueness in RFC 977, includes some new base functionality, and provides a specific mechanism to add standardized extensions to NNTP. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: C. Feather |
| RFC3978 IETF Rights in Contributions 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. | March 2005 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC3979 Intellectual Property Rights in IETF Technology 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. | March 2005 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC3980 T11 Network Address Authority (NAA) Naming Format for iSCSI Node Names 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] | February 2005 Status: PROPOSED STANDARD Autor: M. Krueger, M. Chadalapaka, R. Elliott |
| RFC3981 IRIS: The Internet Registry Information Service (IRIS) Core Protocol 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] | January 2005 Status: PROPOSED STANDARD Autor: A. Newton, M. Sanz |
| RFC3982 IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS) 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] | January 2005 Status: PROPOSED STANDARD Autor: A. Newton, M. Sanz |
| RFC3983 Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP) 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] | January 2005 Status: PROPOSED STANDARD Autor: A. Newton, M. Sanz |
| RFC3984 RTP Payload Format for H.264 Video 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] | February 2005 Status: PROPOSED STANDARD Autor: S. Wenger, M.M. Hannuksela, T. Stockhammer, M. Westerlund, D. Singer |
| RFC3985 Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture 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. | March 2005 Status: INFORMATIONAL Autor: S. Bryant, P. Pate |
| RFC3986 Uniform Resource Identifier (URI): Generic Syntax 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] | January 2005 Status: STANDARD Autor: T. Berners-Lee, R. Fielding, L. Masinter |
| RFC3987 Internationalized Resource Identifiers (IRIs) This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement of 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. | January 2005 Status: PROPOSED STANDARD Autor: M. Duerst, M. Suignard |
| RFC3988 Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol 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. This document specifies experimental extensions to LDP in support of LSP MTU discovery. This memo defines an Experimental Protocol for the Internet community. | January 2005 Status: EXPERIMENTAL Autor: B. Black, K. Kompella |
| RFC3989 Middlebox Communications (MIDCOM) Protocol Semantics 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. | February 2005 Status: INFORMATIONAL Autor: M. Stiemerling, J. Quittek, T. Taylor |
| RFC3990 Configuration and Provisioning for Wireless Access Points (CAPWAP) Problem Statement This document describes the Configuration and Provisioning for Wireless Access Points (CAPWAP) problem statement. This memo provides information for the Internet community. | February 2005 Status: INFORMATIONAL Autor: B. O'Hara, P. Calhoun, J. Kempf |
| RFC3991 Media Gateway Control Protocol (MGCP) Redirect and Reset Package 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. | February 2005 Status: INFORMATIONAL Autor: B. Foster, F. Andreasen |
| RFC3992 Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism 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. | February 2005 Status: INFORMATIONAL Autor: B. Foster, F. Andreasen |
| RFC3993 Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option 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] | March 2005 Status: PROPOSED STANDARD Autor: R. Johnson, T. Palaniappan, M. Stapp |
| RFC3994 Indication of Message Composition for Instant Messaging 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] | January 2005 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC3995 Internet Printing Protocol (IPP): Event Notifications and Subscriptions 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). 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] | March 2005 Status: PROPOSED STANDARD Autor: R. Herriot, T. Hastings |
| RFC3996 Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications 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] | March 2005 Status: PROPOSED STANDARD Autor: R. Herriot, T. Hastings, H. Lewis |
| RFC3997 Internet Printing Protocol (IPP): Requirements for IPP Notifications 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. | March 2005 Status: INFORMATIONAL Autor: T. Hastings, R. K. deBry, H. Lewis |
| RFC3998 Internet Printing Protocol (IPP): Job and Printer Administrative Operations 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] | March 2005 Status: PROPOSED STANDARD Autor: C. Kugler, H. Lewis, T. Hastings |
| RFC4001 Textual Conventions for Internet Network Addresses 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] | February 2005 Status: PROPOSED STANDARD Autor: M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder |
| RFC4002 IANA Registration for Enumservice 'web' and 'ft' 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] | February 2005 Status: PROPOSED STANDARD Autor: R. Brandner, L. Conroy, R. Stastny |
| RFC4003 GMPLS Signaling Procedure for Egress Control 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] | February 2005 Status: PROPOSED STANDARD Autor: L. Berger |
| RFC4004 Diameter Mobile IPv4 Application This document specifies a Diameter application that allows a Diameter server to authenticate, authorize and collect accounting information for Mobile IPv4 services rendered to a mobile node. Combined with the Inter-Realm capability of the base protocol, this application allows mobile nodes to receive service from foreign service providers. Diameter Accounting messages will be used by the foreign and home agents to transfer usage information to the Diameter servers. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: P. Calhoun, T. Johansson, C. Perkins, T. Hiller, P. McCann |
| RFC4005 Diameter Network Access Server Application This document describes the Diameter protocol application used for Authentication, Authorization, and Accounting (AAA) services in the Network Access Server (NAS) environment. When combined with the Diameter Base protocol, Transport Profile, and Extensible Authentication Protocol specifications, this application specification satisfies typical network access services requirements. | August 2005 Status: PROPOSED STANDARD Autor: P. Calhoun, G. Zorn, D. Spence, D. Mitton |
| RFC4006 Diameter Credit-Control Application This document specifies a Diameter application that can be used to implement real-time credit-control for a variety of end user services such as network access, Session Initiation Protocol (SIP) services, messaging services, and download services. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: H. Hakala, L. Mattila, J-P. Koskinen, M. Stura, J. Loughney |
| RFC4007 IPv6 Scoped Address Architecture 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] | March 2005 Status: PROPOSED STANDARD Autor: S. Deering, B. Haberman, T. Jinmei, E. Nordmark, B. Zill |
| RFC4008 Definitions of Managed Objects for Network Address Translators (NAT) 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] | March 2005 Status: PROPOSED STANDARD Autor: R. Rohit, P. Srisuresh, R. Raghunarayan, N. Pai, C. Wang |
| RFC4009 The SEED Encryption Algorithm 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. | February 2005 Status: INFORMATIONAL Autor: J. Park, S. Lee, J. Kim, J. Lee |
| RFC4010 Use of the SEED Encryption Algorithm in Cryptographic Message Syntax (CMS) This document specifies the conventions for using the SEED encryption algorithm for encryption with the Cryptographic Message Syntax (CMS). | February 2005 Status: PROPOSED STANDARD Autor: J. Park, S. Lee, J. Kim, J. Lee |
| RFC4011 Policy Based Management MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, this 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] | March 2005 Status: PROPOSED STANDARD Autor: S. Waldbusser, J. Saperia, T. Hongal |
| RFC4012 Routing Policy Specification Language next generation (RPSLng) 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] | March 2005 Status: PROPOSED STANDARD Autor: L. Blunk, J. Damas, F. Parent, A. Robachevsky |
| RFC4013 SASLprep: Stringprep Profile for User Names and Passwords 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] | February 2005 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4014 Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option 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] | February 2005 Status: PROPOSED STANDARD Autor: R. Droms, J. Schnizlein |
| RFC4015 The Eifel Response Algorithm for TCP 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] | February 2005 Status: PROPOSED STANDARD Autor: R. Ludwig, A. Gurtov |
| RFC4016 Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security Requirements 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. | March 2005 Status: INFORMATIONAL Autor: M. Parthasarathy |
| RFC4017 Extensible Authentication Protocol (EAP) Method Requirements for Wireless LANs 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. | March 2005 Status: INFORMATIONAL Autor: D. Stanley, J. Walker, B. Aboba |
| RFC4018 Finding Internet Small Computer Systems Interface (iSCSI) Targets and Name Servers by Using Service Location Protocol version 2 (SLPv2) 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] | April 2005 Status: PROPOSED STANDARD Autor: M. Bakke, J. Hufferd, K. Voruganti, M. Krueger, T. Sperry |
| RFC4019 RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) Lite 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] | April 2005 Status: PROPOSED STANDARD Autor: G. Pelletier |
| RFC4020 Early IANA Allocation of Standards Track Code Points 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. | February 2005 Status: BEST CURRENT PRACTICE Autor: K. Kompella, A. Zinin |
| RFC4021 Registration of Mail and MIME Header Fields This document defines the initial IANA registration for permanent mail and MIME message header fields, per RFC 3864. [STANDARDS-TRACK] | March 2005 Status: PROPOSED STANDARD Autor: G. Klyne, J. Palme |
| RFC4022 Management Information Base for the Transmission Control Protocol (TCP) 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] | March 2005 Status: PROPOSED STANDARD Autor: R. Raghunarayan |
| RFC4023 Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) 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] | March 2005 Status: PROPOSED STANDARD Autor: T. Worster, Y. Rekhter, E. Rosen |
| RFC4024 Voice Messaging Client Behaviour This document defines the expected behaviour of a client to various aspects of a Voice Profile for Internet Mail (VPIM) message or any voice and/or fax message. This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: G. Parsons, J. Maruszak |
| RFC4025 A Method for Storing IPsec Keying Material in DNS 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. | March 2005 Status: PROPOSED STANDARD Autor: M. Richardson |
| RFC4026 Provider Provisioned Virtual Private Network (VPN) Terminology 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. | March 2005 Status: INFORMATIONAL Autor: L. Andersson, T. Madsen |
| RFC4027 Domain Name System Media Types 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. | April 2005 Status: INFORMATIONAL Autor: S. Josefsson |
| RFC4028 Session Timers in the Session Initiation Protocol (SIP) 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] | April 2005 Status: PROPOSED STANDARD Autor: S. Donovan, J. Rosenberg |
| RFC4029 Scenarios and Analysis for Introducing IPv6 into ISP Networks 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. | March 2005 Status: INFORMATIONAL Autor: M. Lind, V. Ksinant, S. Park, A. Baudot, P. Savola |
| RFC4030 The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option 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] | March 2005 Status: PROPOSED STANDARD Autor: M. Stapp, T. Lemon |
| RFC4031 Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs) 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. | April 2005 Status: INFORMATIONAL Autor: M. Carugi, D. McDysan |
| RFC4032 Update to the Session Initiation Protocol (SIP) Preconditions Framework 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] | March 2005 Status: PROPOSED STANDARD Autor: G. Camarillo, P. Kyzivat |
| RFC4033 DNS Security Introduction and Requirements 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] | March 2005 Status: PROPOSED STANDARD Autor: R. Arends, R. Austein, M. Larson, D. Massey, S. Rose |
| RFC4034 Resource Records for the DNS 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. | March 2005 Status: PROPOSED STANDARD Autor: R. Arends, R. Austein, M. Larson, D. Massey, S. Rose |
| RFC4035 Protocol Modifications for the DNS 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. | March 2005 Status: PROPOSED STANDARD Autor: R. Arends, R. Austein, M. Larson, D. Massey, S. Rose |
| RFC4036 Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management 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] | April 2005 Status: PROPOSED STANDARD Autor: W. Sawyer |
| RFC4037 Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core 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] | March 2005 Status: PROPOSED STANDARD Autor: A. Rousskov |
| RFC4038 Application Aspects of IPv6 Transition 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. | March 2005 Status: INFORMATIONAL Autor: M-K. Shin, Y-G. Hong, J. Hagino, P. Savola, E. M. Castro |
| RFC4039 Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4) 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] | March 2005 Status: PROPOSED STANDARD Autor: S. Park, P. Kim, B. Volz |
| RFC4040 RTP Payload Format for a 64 kbit/s Transparent Call 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". | April 2005 Status: PROPOSED STANDARD Autor: R. Kreuter |
| RFC4041 Requirements for Morality Sections in Routing Area Drafts 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. | April 2005 Status: INFORMATIONAL Autor: A. Farrel |
| RFC4042 UTF-9 and UTF-18 Efficient Transformation Formats of Unicode 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. | April 2005 Status: INFORMATIONAL Autor: M. Crispin |
| RFC4043 Internet X.509 Public Key Infrastructure Permanent Identifier This document defines a new form of name, called permanent identifier, that may be included in the subjectAltName extension of a public key certificate issued to an entity. | May 2005 Status: PROPOSED STANDARD Autor: D. Pinkas, T. Gindin |
| RFC4044 Fibre Channel Management 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] | May 2005 Status: PROPOSED STANDARD Autor: K. McCloghrie |
| RFC4045 Extensions to Support Efficient Carrying of Multicast Traffic in Layer-2 Tunneling Protocol (L2TP) 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. | April 2005 Status: EXPERIMENTAL Autor: G. Bourdon |
| RFC4046 Multicast Security (MSEC) Group Key Management Architecture 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. | April 2005 Status: INFORMATIONAL Autor: M. Baugher, R. Canetti, L. Dondeti, F. Lindholm |
| RFC4047 MIME Sub-type Registrations for Flexible Image Transport System (FITS) 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. | April 2005 Status: INFORMATIONAL Autor: S. Allen, D. Wells |
| RFC4048 RFC 1888 Is Obsolete 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. | April 2005 Status: INFORMATIONAL Autor: B. Carpenter |
| RFC4049 BinaryTime: An Alternate Format for Representing Date and Time in ASN.1 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. | April 2005 Status: EXPERIMENTAL Autor: R. Housley |
| RFC4050 Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures 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. | April 2005 Status: INFORMATIONAL Autor: S. Blake-Wilson, G. Karlinger, T. Kobayashi, Y. Wang |
| RFC4051 Additional XML Security Uniform Resource Identifiers (URIs) 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] | April 2005 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC4052 IAB Processes for Management of IETF Liaison Relationships 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. | April 2005 Status: BEST CURRENT PRACTICE Autor: L. Daigle, Internet Architecture Board |
| RFC4053 Procedures for Handling Liaison Statements to and from the IETF 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. | April 2005 Status: BEST CURRENT PRACTICE Autor: S. Trowbridge, S. Bradner, F. Baker |
| RFC4054 Impairments and Other Constraints on Optical Layer Routing 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. | May 2005 Status: INFORMATIONAL Autor: J. Strand, A. Chiu |
| RFC4055 Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile This document supplements RFC 3279. It describes the conventions for using the RSA Probabilistic Signature Scheme (RSASSA-PSS) signature algorithm, the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport algorithm and additional one-way hash functions with the Public-Key Cryptography Standards (PKCS) #1 version 1.5 signature algorithm in the Internet X.509 Public Key Infrastructure (PKI). Encoding formats, algorithm identifiers, and parameter formats are specified. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: J. Schaad, B. Kaliski, R. Housley |
| RFC4056 Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax (CMS) This document specifies the conventions for using the RSASSA-PSS (RSA Probabilistic Signature Scheme) digital signature algorithm with the Cryptographic Message Syntax (CMS). [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: J. Schaad |
| RFC4057 IPv6 Enterprise Network Scenarios This document describes the scenarios for IPv6 deployment within enterprise networks. It defines a small set of basic enterprise scenarios and includes pertinent questions to allow enterprise administrators to further refine their deployment scenarios. Enterprise deployment requirements are discussed in terms of coexistence with IPv4 nodes, networks and applications, and in terms of basic network infrastructure requirements for IPv6 deployment. The scenarios and requirements described in this document will be the basis for further analysis to determine what coexistence techniques and mechanisms are needed for enterprise IPv6 deployment. The results of that analysis will be published in a separate document. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: J. Bound |
| RFC4058 Protocol for Carrying Authentication for Network Access (PANA) Requirements It is expected that future IP devices will have a variety of access technologies to gain network connectivity. Currently there are access-specific mechanisms for providing client information to the network for authentication and authorization purposes. In addition to being limited to specific access media (e.g., 802.1X for IEEE 802 links), some of these protocols are limited to specific network topologies (e.g., PPP for point-to-point links). The goal of this document is to identify the requirements for a link-layer agnostic protocol that allows a host and a network to authenticate each other for network access. This protocol will run between a client's device and an agent in the network where the agent might be a client of the AAA infrastructure. This memo provides information for the Internet community. | May 2005 Status: INFORMATIONAL Autor: A. Yegin, Y. Ohba, R. Penno, G. Tsirtsis, C. Wang |
| RFC4059 Internet X.509 Public Key Infrastructure Warranty Certificate Extension 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. | May 2005 Status: INFORMATIONAL Autor: D. Linsenbardt, S. Pontius, A. Sturgeon |
| 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 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] | May 2005 Status: PROPOSED STANDARD Autor: Q. Xie, D. Pearce |
| RFC4061 Benchmarking Basic OSPF Single Router Control Plane Convergence 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. | April 2005 Status: INFORMATIONAL Autor: V. Manral, R. White, A. Shaikh |
| RFC4062 OSPF Benchmarking Terminology and Concepts 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. | April 2005 Status: INFORMATIONAL Autor: V. Manral, R. White, A. Shaikh |
| RFC4063 Considerations When Using Basic OSPF Convergence Benchmarks 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. | April 2005 Status: INFORMATIONAL Autor: V. Manral, R. White, A. Shaikh |
| RFC4064 Experimental Message, Extensions, and Error Codes for Mobile IPv4 Mobile IPv4 message types range from 0 to 255. This document reserves a message type for use by an individual, company, or organization for experimental purposes, to evaluate enhancements to Mobile IPv4 messages before a formal standards proposal is issued. [STANDARDS-TRACK] | May 2005 Status: PROPOSED STANDARD Autor: A. Patel, K. Leung |
| RFC4065 Instructions for Seamoby and Experimental Mobility Protocol IANA Allocations The Seamoby Candidate Access Router Discovery (CARD) protocol and the Context Transfer Protocol (CXTP) are experimental protocols designed to accelerate IP handover between wireless access routers. These protocols require IANA allocations for ICMP type and options, Stream Control Transmission Protocol (SCTP) Payload Protocol Identifiers, port numbers, and registries for certain formatted message options. This document contains instructions to IANA about which allocations are required for the Seamoby protocols. The ICMP subtype extension format for Seamoby has been additionally designed so that it can be utilized by other experimental mobility protocols, and the SCTP port number is also available for other experimental mobility protocols. This memo defines an Experimental Protocol for the Internet community. | July 2005 Status: EXPERIMENTAL Autor: J. Kempf |
| RFC4066 Candidate Access Router Discovery (CARD) To enable seamless IP-layer handover of a mobile node (MN) from one access router (AR) to another, the MN is required to discover the identities and capabilities of candidate ARs (CARs) for handover prior to the initiation of the handover. The act of discovery of CARs has two aspects: identifying the IP addresses of the CARs and finding their capabilities. This process is called "candidate access router discovery" (CARD). At the time of IP-layer handover, the CAR, whose capabilities are a good match to the preferences of the MN, is chosen as the target AR for handover. The protocol described in this document allows a mobile node to perform CARD. This memo defines an Experimental Protocol for the Internet community. | July 2005 Status: EXPERIMENTAL Autor: M. Liebsch, A. Singh, H. Chaskar, D. Funato, E. Shim |
| RFC4067 Context Transfer Protocol (CXTP) This document presents the Context Transfer Protocol (CXTP) that enables authorized context transfers. Context transfers allow better support for node based mobility so that the applications running on mobile nodes can operate with minimal disruption. Key objectives are to reduce latency and packet losses, and to avoid the re-initiation of signaling to and from the mobile node. This memo defines an Experimental Protocol for the Internet community. | July 2005 Status: EXPERIMENTAL Autor: J. Loughney, M. Nakhjiri, C. Perkins, R. Koodli |
| RFC4068 Fast Handovers for Mobile IPv6 Mobile IPv6 enables a Mobile Node to maintain its connectivity to the Internet when moving from one Access Router to another, a process referred to as handover. During handover, there is a period during which the Mobile Node is unable to send or receive packets because of link switching delay and IP protocol operations. This "handover latency" resulting from standard Mobile IPv6 procedures, namely movement detection, new Care of Address configuration, and Binding Update, is often unacceptable to real-time traffic such as Voice over IP. Reducing the handover latency could be beneficial to non-real-time, throughput-sensitive applications as well. This document specifies a protocol to improve handover latency due to Mobile IPv6 procedures. This document does not address improving the link switching latency. This memo defines an Experimental Protocol for the Internet community. | July 2005 Status: EXPERIMENTAL Autor: R. Koodli |
| RFC4069 Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line Coding 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] | May 2005 Status: PROPOSED STANDARD Autor: M. Dodge, B. Ray |
| RFC4070 Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding 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. [STANDARDS-TRACK] | May 2005 Status: PROPOSED STANDARD Autor: M. Dodge, B. Ray |
| RFC4071 Structure of the IETF Administrative Support Activity (IASA) 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. | April 2005 Status: BEST CURRENT PRACTICE Autor: R. Austein, B. Wijnen |
| RFC4072 Diameter Extensible Authentication Protocol (EAP) Application The Extensible Authentication Protocol (EAP) provides a standard mechanism for support of various authentication methods. This document defines the Command-Codes and AVPs necessary to carry EAP packets between a Network Access Server (NAS) and a back-end authentication server. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: P. Eronen, T. Hiller, G. Zorn |
| RFC4073 Protecting Multiple Contents with the Cryptographic Message Syntax (CMS) 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] | May 2005 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC4074 Common Misbehavior Against DNS Queries for IPv6 Addresses There is some known misbehavior of DNS authoritative servers when they are queried for AAAA resource records. Such behavior can block IPv4 communication that should actually be available, cause a significant delay in name resolution, or even make a denial of service attack. This memo describes details of known cases and discusses their effects. This memo provides information for the Internet community. | May 2005 Status: INFORMATIONAL Autor: Y. Morishita, T. Jinmei |
| RFC4075 Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6 This document describes a new DHCPv6 option for passing a list of Simple Network Time Protocol (SNTP) server addresses to a client. [STANDARDS-TRACK] | May 2005 Status: PROPOSED STANDARD Autor: V. Kalusivalingam |
| RFC4076 Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6) IPv6 hosts using Stateless Address Autoconfiguration are able to configure their IPv6 address and default router settings automatically. However, further settings are not available. If these hosts wish to configure their DNS, NTP, or other specific settings automatically, the stateless variant of the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) could be used. This combination of Stateless Address Autoconfiguration and stateless DHCPv6 could be used quite commonly in IPv6 networks. However, hosts using this combination currently have no means by which to be informed of changes in stateless DHCPv6 option settings; e.g., the addition of a new NTP server address, a change in DNS search paths, or full site renumbering. This document is presented as a problem statement from which a solution should be proposed in a subsequent document. This memo provides information for the Internet community. | May 2005 Status: INFORMATIONAL Autor: T. Chown, S. Venaas, A. Vijayabhaskar |
| RFC4077 A Negative Acknowledgement Mechanism for Signaling Compression This document describes a mechanism that allows Signaling Compression (SigComp) implementations to report precise error information upon receipt of a message which cannot be decompressed. This negative feedback can be used by the recipient to make fine-grained adjustments to the compressed message before retransmitting it, allowing for rapid and efficient recovery from error situations. [STANDARDS-TRACK] | May 2005 Status: PROPOSED STANDARD Autor: A.B. Roach |
| RFC4078 The TV-Anytime Content Reference Identifier (CRID) The Uniform Resource Locator (URL) scheme "CRID:" has been devised to allow references to current or future scheduled publications of broadcast media content over television distribution platforms and the Internet. | May 2005 Status: INFORMATIONAL Autor: N. Earnshaw, S. Aoki, A. Ashley, W. Kameyama |
| RFC4079 A Presence Architecture for the Distribution of GEOPRIV Location Objects GEOPRIV defines the concept of a 'using protocol' -- a protocol that carries GEOPRIV location objects. GEOPRIV also defines various scenarios for the distribution of location objects that require the concepts of subscriptions and asynchronous notifications. This document examines some existing IETF work on the concept of presence, shows how presence architectures map onto GEOPRIV architectures, and moreover demonstrates that tools already developed for presence could be reused to simplify the standardization and implementation of GEOPRIV. This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: J. Peterson |
| RFC4080 Next Steps in Signaling (NSIS): Framework The Next Steps in Signaling (NSIS) working group is considering protocols for signaling information about a data flow along its path in the network. The NSIS suite of protocols is envisioned to support various signaling applications that need to install and/or manipulate such state in the network. Based on existing work on signaling requirements, this document proposes an architectural framework for these signaling protocols. | June 2005 Status: INFORMATIONAL Autor: R. Hancock, G. Karagiannis, J. Loughney, S. Van den Bosch |
| RFC4081 Security Threats for Next Steps in Signaling (NSIS) This threats document provides a detailed analysis of the security threats relevant to the Next Steps in Signaling (NSIS) protocol suite. It calls attention to, and helps with the understanding of, various security considerations in the NSIS Requirements, Framework, and Protocol proposals. This document does not describe vulnerabilities of specific parts of the NSIS protocol suite. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: H. Tschofenig, D. Kroeselberg |
| RFC4082 Timed Efficient Stream Loss-Tolerant Authentication (TESLA): Multicast Source Authentication Transform Introduction This document introduces Timed Efficient Stream Loss-tolerant Authentication (TESLA). TESLA allows all receivers to check the integrity and authenticate the source of each packet in multicast or broadcast data streams. TESLA requires no trust between receivers, uses low-cost operations per packet at both sender and receiver, can tolerate any level of loss without retransmissions, and requires no per-receiver state at the sender. TESLA can protect receivers against denial of service attacks in certain circumstances. Each receiver must be loosely time-synchronized with the source in order to verify messages, but otherwise receivers do not have to send any messages. TESLA alone cannot support non-repudiation of the data source to third parties. | June 2005 Status: INFORMATIONAL Autor: A. Perrig, D. Song, R. Canetti, J. D. Tygar, B. Briscoe |
| RFC4083 Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP) The 3rd-Generation Partnership Project (3GPP) has selected Session Initiation Protocol (SIP) as the session establishment protocol for the 3GPP IP Multimedia Core Network Subsystem (IMS). IMS is part of Release 5 of the 3GPP specifications. Although SIP is a protocol that fulfills most of the requirements for establishing a session in an IP network, SIP has never been evaluated against the specific 3GPP requirements for operation in a cellular network. In this document, we express the requirements identified by 3GPP to support SIP for Release 5 of the 3GPP IMS in cellular networks. This memo provides information for the Internet community. | May 2005 Status: INFORMATIONAL Autor: M. Garcia-Martin |
| RFC4084 Terminology for Describing Internet Connectivity 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. | May 2005 Status: BEST CURRENT PRACTICE Autor: J. Klensin |
| RFC4085 Embedding Globally-Routable Internet Addresses Considered Harmful This document discourages the practice of embedding references to unique, globally-routable IP addresses in Internet hosts, describes some of the resulting problems, and considers selected alternatives. This document is intended to clarify best current practices in this regard. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2005 Status: BEST CURRENT PRACTICE Autor: D. Plonka |
| RFC4086 Randomness Requirements for Security Security systems are built on strong cryptographic algorithms that foil pattern analysis attempts. However, the security of these systems is dependent on generating secret quantities for passwords, cryptographic keys, and similar quantities. The use of pseudo-random processes to generate secret quantities can result in pseudo-security. A sophisticated attacker may find it easier to reproduce the environment that produced the secret quantities and to search the resulting small set of possibilities than to locate the quantities in the whole of the potential number space. | June 2005 Status: BEST CURRENT PRACTICE Autor: D. Eastlake 3rd, J. Schiller, S. Crocker |
| RFC4087 IP Tunnel MIB This memo defines a Management Information Base (MIB) module 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 and IPv6 networks. Extension MIB modules may be designed for managing protocol-specific objects. Likewise, extension MIB modules may be designed for managing security-specific objects. This MIB module does not support tunnels over non-IP networks. Management of such tunnels may be supported by other MIB modules. This memo obsoletes RFC 2667. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: D. Thaler |
| RFC4088 Uniform Resource Identifier (URI) Scheme for the Simple Network Management Protocol (SNMP) The Simple Network Management Protocol (SNMP) and the Internet Standard Management Framework are widely used for the management of communication devices, creating a need to specify SNMP access (including access to SNMP MIB object instances) from non-SNMP management environments. For example, when out-of-band IP management is used via a separate management interface (e.g., for a device that does not support in-band IP access), a uniform way to indicate how to contact the device for management is needed. Uniform Resource Identifiers (URIs) fit this need well, as they allow a single text string to indicate a management access communication endpoint for a wide variety of IP-based protocols. | June 2005 Status: PROPOSED STANDARD Autor: D. Black, K. McCloghrie, J. Schoenwaelder |
| RFC4089 IAB and IESG Recommendation for IETF Administrative Restructuring This document describes a joint recommendation of the Internet Architecture Board and the Internet Engineering Steering Group for administrative restructuring of the Internet Engineering Task Force. The IETF Chair declared that the IETF had consensus to follow this recommendation on November 11, 2004. Further work has been done to revise and refine the structures proposed. The recommendation is being published for the record. This memo provides information for the Internet community. | May 2005 Status: INFORMATIONAL Autor: S. Hollenbeck, IAB and IESG |
| RFC4090 Fast Reroute Extensions to RSVP-TE for LSP Tunnels This document defines RSVP-TE extensions to establish backup label-switched path (LSP) tunnels for local repair of LSP tunnels. These mechanisms enable the re-direction of traffic onto backup LSP tunnels in 10s of milliseconds, in the event of a failure. | May 2005 Status: PROPOSED STANDARD Autor: P. Pan, G. Swallow, A. Atlas |
| RFC4091 The Alternative Network Address Types (ANAT) Semantics for the Session Description Protocol (SDP) Grouping Framework This document defines the Alternative Network Address Types (ANAT) semantics for the Session Description Protocol (SDP) grouping framework. The ANAT semantics allow alternative types of network addresses to establish a particular media stream. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: G. Camarillo, J. Rosenberg |
| RFC4092 Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP) This document describes how to use the Alternative Network Address Types (ANAT) semantics of the Session Description Protocol (SDP) grouping framework in SIP. In particular, we define the sdp-anat SIP option-tag. This SIP option-tag ensures that SDP session descriptions that use ANAT are only handled by SIP entities with ANAT support. To justify the need for such a SIP option-tag, we describe what could possibly happen if an ANAT-unaware SIP entity tried to handle media lines grouped with ANAT. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: G. Camarillo, J. Rosenberg |
| RFC4093 Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways Deploying Mobile-IP v4 in networks that are connected to the Internet through a Virtual Private Network (VPN) gateway presents some problems that do not currently have well-described solutions. This document aims to describe and illustrate these problems, and to propose some guidelines for possible solutions. This memo provides information for the Internet community. | August 2005 Status: INFORMATIONAL Autor: F. Adrangi, H. Levkowetz |
| RFC4094 Analysis of Existing Quality-of-Service Signaling Protocols This document reviews some of the existing Quality of Service (QoS) signaling protocols for an IP network. The goal here is to learn from them and to avoid common misconceptions. Further, we need to avoid mistakes during the design and implementation of any new protocol in this area. This memo provides information for the Internet community. | May 2005 Status: INFORMATIONAL Autor: J. Manner, X. Fu |
| RFC4095 Attaching Meaning to Solicitation Class Keywords This document proposes a mechanism for finding a URI associated with a solicitation class keyword, which is defined in RFC 3865, the No Soliciting SMTP Service Extension. Solicitation class keywords are simple labels consisting of a domain name that has been reversed, such as "org.example.adv". These solicitation class keywords are inserted in selected header fields or used in the ESMTP service extension, including a new \%"No-Solicit:" header, which can contain one or more solicitation class keywords inserted by the sender. | May 2005 Status: PROPOSED STANDARD Autor: C. Malamud |
| RFC4096 Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best This memo discusses policies that require certain labels to be inserted in the "Subject:" header of a mail message. Such policies are difficult to specify accurately while remaining compliant with key RFCs and are likely to be ineffective at best. This memo discusses an alternate, \%standards-compliant approach that is significantly simpler to specify and is somewhat less likely to be ineffective. This memo provides information for the Internet community. | May 2005 Status: INFORMATIONAL Autor: C. Malamud |
| RFC4097 Middlebox Communications (MIDCOM) Protocol Evaluation This document provides an evaluation of the applicability of SNMP (Simple Network Management Protocol), RSIP (Realm Specific Internet Protocol), Megaco, Diameter, and COPS (Common Open Policy Service) as the MIDCOM (Middlebox Communications) protocol. A summary of each of the proposed protocols against the MIDCOM requirements and the MIDCOM framework is provided. Compliancy of each of the protocols against each requirement is detailed. A conclusion summarizes how each of the protocols fares in the evaluation. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: M. Barnes |
| RFC4098 Terminology for Benchmarking BGP Device Convergence in the Control Plane This document establishes terminology to standardize the description of benchmarking methodology for measuring eBGP convergence in the control plane of a single BGP device. Future documents will address iBGP convergence, the initiation of forwarding based on converged control plane information and multiple interacting BGP devices.This terminology is applicable to both IPv4 and IPv6. Illustrative examples of each version are included where relevant. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: H. Berkowitz, E. Davies, S. Hares, P. Krishnaswamy, M. Lepp |
| RFC4101 Writing Protocol Models The IETF process depends on peer review. However, IETF documents are generally written to be useful for implementors, not reviewers. In particular, while great care is generally taken to provide a complete description of the state machines and bits on the wire, this level of detail tends to get in the way of initial understanding. This document describes an approach for providing protocol "models" that allow reviewers to quickly grasp the essence of a system. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: E. Rescorla, IAB |
| RFC4102 Registration of the text/red MIME Sub-Type This document defines the text/red MIME sub-type. "Red" is short for redundant. The actual RTP packetization for this MIME type is specified in RFC 2198. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: P. Jones |
| RFC4103 RTP Payload for Text Conversation This memo obsoletes RFC 2793; it describes how to carry real-time text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140. | June 2005 Status: PROPOSED STANDARD Autor: G. Hellstrom, P. Jones |
| RFC4104 Policy Core Extension Lightweight Directory Access Protocol Schema (PCELS) This document defines a number of changes and extensions to the Policy Core Lightweight Directory Access Protocol (LDAP) Schema (RFC 3703) based on the model extensions defined by the Policy Core Information Model (PCIM) Extensions (RFC 3460). These changes and extensions consist of new LDAP object classes and attribute types. Some of the schema items defined in this document re-implement existing concepts in accordance with their new semantics introduced by RFC 3460. The other schema items implement new concepts, not covered by RFC 3703. This document updates RFC 3703. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: M. Pana, A. Reyes, A. Barba, D. Moron, M. Brunner |
| RFC4105 Requirements for Inter-Area MPLS Traffic Engineering This document lists a detailed set of functional requirements for the support of inter-area MPLS Traffic Engineering (inter-area MPLS TE). It is intended that solutions that specify procedures and protocol extensions for inter-area MPLS TE satisfy these requirements. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: J.-L. Le Roux, J.-P. Vasseur, J. Boyle |
| RFC4106 The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP) This memo describes the use of the Advanced Encryption Standard (AES) in Galois/Counter Mode (GCM) as an IPsec Encapsulating Security Payload (ESP) mechanism to provide confidentiality and data origin authentication. This method can be efficiently implemented in hardware for speeds of 10 gigabits per second and above, and is also well-suited to software implementations. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: J. Viega, D. McGrew |
| RFC4107 Guidelines for Cryptographic Key Management The question often arises of whether a given security system requires some form of automated key management, or whether manual keying is sufficient. This memo provides guidelines for making such decisions. When symmetric cryptographic mechanisms are used in a protocol, the presumption is that automated key management is generally but not always needed. If manual keying is proposed, the burden of proving that automated key management is not required falls to the proposer. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2005 Status: BEST CURRENT PRACTICE Autor: S. Bellovin, R. Housley |
| RFC4108 Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages This document describes the use of the Cryptographic Message Syntax (CMS) to protect firmware packages, which provide object code for one or more hardware module components. CMS is specified in RFC 3852. A digital signature is used to protect the firmware package from undetected modification and to provide data origin authentication. Encryption is optionally used to protect the firmware package from disclosure, and compression is optionally used to reduce the size of the protected firmware package. A firmware package loading receipt can optionally be generated to acknowledge the successful loading of a firmware package. Similarly, a firmware package load error report can optionally be generated to convey the failure to load a firmware package. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC4109 Algorithms for Internet Key Exchange version 1 (IKEv1) The required and suggested algorithms in the original Internet Key Exchange version 1 (IKEv1) specification do not reflect the current reality of the IPsec market requirements. The original specification allows weak security and suggests algorithms that are thinly implemented. This document updates RFC 2409, the original specification, and is intended for all IKEv1 implementations deployed today. [STANDARDS-TRACK] | May 2005 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC4110 A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs) This document provides a framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs). This framework is intended to aid in the standardization of protocols and mechanisms for support of layer 3 PPVPNs. It is the intent of this document to produce a coherent description of the significant technical issues that are important in the design of layer 3 PPVPN solutions. Selection of specific approaches, making choices regarding engineering tradeoffs, and detailed protocol specification, are outside of the scope of this framework document. This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: R. Callon, M. Suzuki |
| RFC4111 Security Framework for Provider-Provisioned Virtual Private Networks (PPVPNs) This document addresses security aspects pertaining to Provider-Provisioned Virtual Private Networks (PPVPNs). First, it describes the security threats in the context of PPVPNs and defensive techniques to combat those threats. It considers security issues deriving both from malicious behavior of anyone and from negligent or incorrect behavior of the providers. It also describes how these security attacks should be detected and reported. It then discusses possible user requirements for security of a PPVPN service. These user requirements translate into corresponding provider requirements. In addition, the provider may have additional requirements to make its network infrastructure secure to a level that can meet the PPVPN customer's expectations. Finally, this document defines a template that may be used to describe and analyze the security characteristics of a specific PPVPN technology. This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: L. Fang |
| RFC4112 Electronic Commerce Modeling Language (ECML) Version 2 Specification Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC4113 Management Information Base for the User Datagram Protocol (UDP) 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 User Datagram Protocol (UDP) in an IP version independent manner. This memo obsoletes RFCs 2013 and 2454. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: B. Fenner, J. Flick |
| RFC4114 E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of E.164 numbers that represent domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of E.164 numbers. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC4115 A Differentiated Service Two-Rate, Three-Color Marker with Efficient Handling of in-Profile Traffic This document describes a two-rate, three-color marker that has been in use for data services including Frame Relay services. This marker can be used for metering per-flow traffic in the emerging IP and L2 VPN services. The marker defined here is different from previously defined markers in the handling of the in-profile traffic. Furthermore, this marker doesn't impose peak-rate shaping requirements on customer edge (CE) devices. This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: O. Aboul-Magd, S. Rabie |
| RFC4116 IPv4 Multihoming Practices and Limitations Multihoming is an essential component of service for many Internet sites. This document describes some implementation strategies for multihoming with IPv4 and enumerates features for comparison with other multihoming proposals (particularly those related to IPv6). This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: J. Abley, K. Lindqvist, E. Davies, B. Black, V. Gill |
| RFC4117 Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc) This document describes how to invoke transcoding services using Session Initiation Protocol (SIP) and third party call control. This way of invocation meets the requirements for SIP regarding transcoding services invocation to support deaf, hard of hearing and speech-impaired individuals. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: G. Camarillo, E. Burger, H. Schulzrinne, A. van Wijk |
| RFC4118 Architecture Taxonomy for Control and Provisioning of Wireless Access Points (CAPWAP) This document provides a taxonomy of the architectures employed in the existing IEEE 802.11 products in the market, by analyzing Wireless LAN (WLAN) functions and services and describing the different variants in distributing these functions and services among the architectural entities. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: L. Yang, P. Zerfos, E. Sadot |
| RFC4119 A Presence-based GEOPRIV Location Object Format This document describes an object format for carrying geographical information on the Internet. This location object extends the Presence Information Data Format (PIDF), which was designed for communicating privacy-sensitive presence information and which has similar properties. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: J. Peterson |
| RFC4120 The Kerberos Network Authentication Service (V5) This document provides an overview and specification of Version 5 of the Kerberos protocol, and it obsoletes RFC 1510 to clarify aspects of the protocol and its intended use that require more detailed or clearer explanation than was provided in RFC 1510. This document is intended to provide a detailed description of the protocol, suitable for implementation, together with descriptions of the appropriate use of protocol messages and fields within those messages. [STANDARDS-TRACK] | July 2005 Status: PROPOSED STANDARD Autor: C. Neuman, T. Yu, S. Hartman, K. Raeburn |
| RFC4121 The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2 This document defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (GSS-API) when using the Kerberos Version 5 mechanism. | July 2005 Status: PROPOSED STANDARD Autor: L. Zhu, K. Jaganathan, S. Hartman |
| RFC4122 A Universally Unique IDentifier (UUID) URN Namespace This specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation\'s (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms. | July 2005 Status: PROPOSED STANDARD Autor: P. Leach, M. Mealling, R. Salz |
| RFC4123 Session Initiation Protocol (SIP)-H.323 Interworking Requirements This document describes the requirements for the logical entity known as the Session Initiation Protocol (SIP)-H.323 Interworking Function (SIP-H.323 IWF) that will allow the interworking between SIP and H.323. This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: H. Schulzrinne, C. Agboh |
| RFC4124 Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering This document specifies the protocol extensions for support of Diffserv-aware MPLS Traffic Engineering (DS-TE). This includes generalization of the semantics of a number of Interior Gateway Protocol (IGP) extensions already defined for existing MPLS Traffic Engineering in RFC 3630, RFC 3784, and additional IGP extensions beyond those. This also includes extensions to RSVP-TE signaling beyond those already specified in RFC 3209 for existing MPLS Traffic Engineering. These extensions address the requirements for DS-TE spelled out in RFC 3564. [STANDARDS-TRACK] | June 2005 Status: PROPOSED STANDARD Autor: F. Le Faucheur |
| RFC4125 Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering This document provides specifications for one Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering, which is referred to as the Maximum Allocation Model. This memo defines an Experimental Protocol for the Internet community. | June 2005 Status: EXPERIMENTAL Autor: F. Le Faucheur, W. Lai |
| RFC4126 Max Allocation with Reservation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering & Performance Comparisons This document complements the Diffserv-aware MPLS Traffic Engineering (DS-TE) requirements document by giving a functional specification for the Maximum Allocation with Reservation (MAR) Bandwidth Constraints Model. Assumptions, applicability, and examples of the operation of the MAR Bandwidth Constraints Model are presented. MAR performance is analyzed relative to the criteria for selecting a Bandwidth Constraints Model, in order to provide guidance to user implementation of the model in their networks. This memo defines an Experimental Protocol for the Internet community. | June 2005 Status: EXPERIMENTAL Autor: J. Ash |
| RFC4127 Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering This document provides specifications for one Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering, which is referred to as the Russian Dolls Model. This memo defines an Experimental Protocol for the Internet community. | June 2005 Status: EXPERIMENTAL Autor: F. Le Faucheur |
| RFC4128 Bandwidth Constraints Models for Differentiated Services (Diffserv)-aware MPLS Traffic Engineering: Performance Evaluation "Differentiated Services (Diffserv)-aware MPLS Traffic Engineering Requirements", RFC 3564, specifies the requirements and selection criteria for Bandwidth Constraints Models. Two such models, the Maximum Allocation and the Russian Dolls, are described therein. This document complements RFC 3564 by presenting the results of a performance evaluation of these two models under various operational conditions: normal load, overload, preemption fully or partially enabled, pure blocking, or complete sharing. This memo provides information for the Internet community. | June 2005 Status: INFORMATIONAL Autor: W. Lai |
| RFC4129 Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA Protocol This document defines a mechanism for backhauling Digital Private Network Signaling System 1 (DPNSS 1) and Digital Access Signaling System 2 (DASS 2) messages over IP by extending the ISDN User Adaptation (IUA) Layer Protocol defined in RFC 3057. DPNSS 1, specified in ND1301:2001/03 (formerly BTNR 188), is used to interconnect Private Branch Exchanges (PBX) in a private network. DASS 2, specified in BTNR 190, is used to connect PBXs to the PSTN. This document aims to become an Appendix to IUA and to be the base for a DPNSS 1/DASS 2 User Adaptation (DUA) implementation. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: R. Mukundan, K. Morneault, N. Mangalpally |
| RFC4130 MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2) This document provides an applicability statement (RFC 2026, Section 3.2) that describes how to exchange structured business data securely using the HTTP transfer protocol, instead of SMTP; the applicability statement for SMTP is found in RFC 3335. Structured business data may be XML; Electronic Data Interchange (EDI) in either the American National Standards Committee (ANSI) X12 format or the UN Electronic Data Interchange for Administration, Commerce, and Transport (UN/EDIFACT) format; or other structured data formats. The data is packaged using standard MIME structures. Authentication and data confidentiality are obtained by using Cryptographic Message Syntax with S/MIME security body parts. Authenticated acknowledgements make use of multipart/signed Message Disposition Notification (MDN) responses to the original HTTP message. This applicability statement is informally referred to as "AS2" because it is the second applicability statement, produced after "AS1", RFC 3335. [STANDARDS-TRACK] | July 2005 Status: PROPOSED STANDARD Autor: D. Moberg, R. Drummond |
| RFC4131 Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modems and Cable Modem Termination Systems for Baseline Privacy Plus 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 the Baseline Privacy Plus features of DOCSIS 1.1 and DOCSIS 2.0 (Data-over-Cable Service Interface Specification) compliant Cable Modems and Cable Modem Termination Systems. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: S. Green, K. Ozawa, E. Cardona, A. Katsnelson |
| RFC4132 Addition of Camellia Cipher Suites to Transport Layer Security (TLS) This document proposes the addition of new cipher suites to the Transport Layer Security (TLS) protocol to support the Camellia encryption algorithm as a bulk cipher algorithm. [STANDARDS-TRACK] | July 2005 Status: PROPOSED STANDARD Autor: S. Moriai, A. Kato, M. Kanda |
| RFC4133 Entity MIB (Version 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 describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. This document specifies version 3 of the Entity MIB, which obsoletes version 2 (RFC 2737). [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: A. Bierman, K. McCloghrie |
| RFC4134 Examples of S/MIME Messages This document gives examples of message bodies formatted using S/MIME. Specifically, it has examples of Cryptographic Message Syntax (CMS) objects and S/MIME messages (including the MIME formatting). It includes examples of many common CMS formats. The purpose of this document is to help increase interoperability for S/MIME and other protocols that rely on CMS. This memo provides information for the Internet community. | July 2005 Status: INFORMATIONAL Autor: P. Hoffman |
| RFC4135 Goals of Detecting Network Attachment in IPv6 When a host establishes a new link-layer connection, it may or may not have a valid IP configuration for Internet connectivity. The host may check for link change (i.e., determine whether a link change has occurred), and then, based on the result, it can automatically decide whether its IP configuration is still valid. During link identity detection, the host may also collect necessary information to initiate a new IP configuration if the IP subnet has changed. In this memo, this procedure is called Detecting Network Attachment (DNA). DNA schemes should be precise, sufficiently fast, secure, and of limited signaling. This memo provides information for the Internet community. | August 2005 Status: INFORMATIONAL Autor: JH. Choi, G. Daley |
| RFC4136 OSPF Refresh and Flooding Reduction in Stable Topologies This document describes an extension to the OSPF protocol to reduce periodic flooding of Link State Advertisements (LSAs) in stable topologies. | July 2005 Status: INFORMATIONAL Autor: P. Pillay-Esnault |
| RFC4137 State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator This document describes a set of state machines for Extensible Authentication Protocol (EAP) peer, EAP stand-alone authenticator (non-pass-through), EAP backend authenticator (for use on Authentication, Authorization, and Accounting (AAA) servers), and EAP full authenticator (for both local and pass-through). This set of state machines shows how EAP can be implemented to support deployment in either a peer/authenticator or peer/authenticator/AAA Server environment. The peer and stand-alone authenticator machines are illustrative of how the EAP protocol defined in RFC 3748 may be implemented. The backend and full/pass-through authenticators illustrate how EAP/AAA protocol support defined in RFC 3579 may be implemented. Where there are differences, RFC 3748 and RFC 3579 are authoritative. | August 2005 Status: INFORMATIONAL Autor: J. Vollbrecht, P. Eronen, N. Petroni, Y. Ohba |
| RFC4138 Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP) Spurious retransmission timeouts cause suboptimal TCP performance because they often result in unnecessary retransmission of the last window of data. This document describes the F-RTO detection algorithm for detecting spurious TCP retransmission timeouts. F-RTO is a TCP sender-only algorithm that does not require any TCP options to operate. After retransmitting the first unacknowledged segment triggered by a timeout, the F-RTO algorithm of the TCP sender monitors the incoming acknowledgments to determine whether the timeout was spurious. It then decides whether to send new segments or retransmit unacknowledged segments. The algorithm effectively helps to avoid additional unnecessary retransmissions and thereby improves TCP performance in the case of a spurious timeout. The F-RTO algorithm can also be applied to the Stream Control Transmission Protocol (SCTP). This memo defines an Experimental Protocol for the Internet community. | August 2005 Status: EXPERIMENTAL Autor: P. Sarolahti, M. Kojo |
| RFC4139 Requirements for Generalized MPLS (GMPLS) Signaling Usage and Extensions for Automatically Switched Optical Network (ASON) The Generalized Multi-Protocol Label Switching (GMPLS) suite of protocols has been defined to control different switching technologies and different applications. These include support for requesting Time Division Multiplexing (TDM) connections, including Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) and Optical Transport Networks (OTNs). | July 2005 Status: INFORMATIONAL Autor: D. Papadimitriou, J. Drake, J. Ash, A. Farrel, L. Ong |
| RFC4140 Hierarchical Mobile IPv6 Mobility Management (HMIPv6) This document introduces extensions to Mobile IPv6 and IPv6 Neighbour Discovery to allow for local mobility handling. Hierarchical mobility management for Mobile IPv6 is designed to reduce the amount of signalling between the Mobile Node, its Correspondent Nodes, and its Home Agent. The Mobility Anchor Point (MAP) described in this document can also be used to improve the performance of Mobile IPv6 in terms of handover speed. This memo defines an Experimental Protocol for the Internet community. | August 2005 Status: EXPERIMENTAL Autor: H. Soliman, C. Castelluccia, K. El Malki, L. Bellier |
| RFC4141 SMTP and MIME Extensions for Content Conversion A message originator sometimes sends content in a form the recipient cannot process or would prefer not to process a form of lower quality than is preferred. Such content needs to be converted to an acceptable form, with the same information or constrained information (e.g., changing from color to black and white). In a store-and-forward environment, it may be convenient to have this conversion performed by an intermediary. This specification integrates two ESMTP extensions and three MIME content header fields, which defines a cooperative service that permits authorized, accountable content form conversion by intermediaries. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: K. Toyoda, D. Crocker |
| RFC4142 Full-mode Fax Profile for Internet Mail (FFPIM) Classic facsimile document exchange represents both a set of technical specifications and a class of service. Previous work has replicated some of that service class as a profile within Internet mail. The current specification defines "full mode" carriage of facsimile data over the Internet, building upon that previous work and adding the remaining functionality necessary for achieving reliability and capability negotiation for Internet mail, on a par with classic T.30 facsimile. These additional features are designed to provide the highest level of interoperability with the standards-compliant email infrastructure and mail user agents, while providing a level of service that approximates what is currently enjoyed by fax users. [PROPOSED STANDARD] | November 2005 Status: PROPOSED STANDARD Autor: D. Crocker, G. Klyne |
| RFC4143 Facsimile Using Internet Mail (IFAX) Service of ENUM This document describes the functional specification and definition of the ENUM Naming Authority Pointer (NAPTR) record for IFax service. IFax is "facsimile using Internet mail". For this use, the Domain Name System (DNS) returns the email address of the referenced IFax system. This mechanism allows email-based fax communication to use telephone numbers instead of requiring the sender to already know the recipient email address. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: K. Toyoda, D. Crocker |
| RFC4144 How to Gain Prominence and Influence in Standards Organizations This document provides simple guidelines that can make it easier for you to gain prominence and influence in most standards organizations. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: D. Eastlake 3rd |
| RFC4145 TCP-Based Media Transport in the Session Description Protocol (SDP) This document describes how to express media transport over TCP using the Session Description Protocol (SDP). It defines the SDP 'TCP' protocol identifier, the SDP 'setup' attribute, which describes the connection setup procedure, and the SDP 'connection' attribute, which handles connection reestablishment. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: D. Yon, G. Camarillo |
| RFC4146 Simple New Mail Notification This memo documents a long-standing technique, supported by a large number of mail servers, which allows users to be notified of new mail. In addition to server support, there are a number of clients that support this, ranging from full email clients to specialized clients whose only purpose is to receive new mail notifications and alert a mail client. | August 2005 Status: INFORMATIONAL Autor: R. Gellens |
| RFC4147 Proposed Changes to the Format of the IANA IPv6 Registry This document proposes a revised format for the IANA IPv6 address registries. Rather than providing a formal definition of the format, it is described by giving examples of the (current as of preparation of this document) contents of the registries in the proposed format. The proposed format would bring the IANA IPv6 address registries into alignment with the current IPv6 Address Architecture specification, as well as update it to a more useful and generally accepted format. This memo provides information for the Internet community. | August 2005 Status: INFORMATIONAL Autor: G. Huston |
| RFC4148 IP Performance Metrics (IPPM) Metrics Registry This memo defines a registry for IP Performance Metrics (IPPM). It assigns and registers an initial set of OBJECT IDENTITIES to currently defined metrics in the IETF. | August 2005 Status: BEST CURRENT PRACTICE Autor: E. Stephan |
| RFC4149 Definition of Managed Objects for Synthetic Sources for Performance Monitoring Algorithms 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 for configuring Synthetic Sources for Performance Monitoring (SSPM) algorithms. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: C. Kalbfleisch, R. Cole, D. Romascanu |
| RFC4150 Transport Performance Metrics 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 monitoring selectable performance metrics and statistics derived from the monitoring of network packets and sub-application level transactions. The metrics can be defined through reference to existing IETF, ITU, and other standards organizations' documents. The monitoring covers both passive and active traffic generation sources. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: R. Dietz, R. Cole |
| RFC4151 The 'tag' URI Scheme This document describes the "tag" Uniform Resource Identifier (URI) scheme. Tag URIs (also known as "tags") are designed to be unique across space and time while being tractable to humans. They are distinct from most other URIs in that they have no authoritative resolution mechanism. A tag may be used purely as an entity identifier. Furthermore, using tags has some advantages over the common practice of using "http" URIs as identifiers for non-HTTP-accessible resources. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: T. Kindberg, S. Hawke |
| RFC4152 A Uniform Resource Name (URN) Namespace for the Common Language Equipment Identifier (CLEI) Code This document describes a Uniform Resource Name (URN) namespace (RFC 3406) for the assignment of the Common Language Equipment Identifier (CLEI) code, which is used in messages standardized by ANSI. The URN namespace is managed by Telcordia Technologies, Inc., as the maintenance agent for ANSI T1.213. The CLEI code is a globally unique, ten-character alphanumeric intelligent code assigned by Telcordia Technologies at the request of equipment suppliers. The CLEI code identifies communications equipment by specifying product type and features. There is a one-to-one relationship between a CLEI code and supplier's product ID (the manufacturer's name and the part number along with its version number). This memo provides information for the Internet community. | August 2005 Status: INFORMATIONAL Autor: K. Tesink, R. Fox |
| RFC4153 XML Voucher: Generic Voucher Language This document specifies rules for defining voucher properties in XML syntax. A voucher is a logical entity that represents a right to claim goods or services. A voucher can be used to transfer a wide range of electronic values, including coupons, tickets, loyalty points, and gift certificates, which often have to be processed in the course of payment and/or delivery transactions. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: K. Fujimura, M. Terada, D. Eastlake 3rd |
| RFC4154 Voucher Trading System Application Programming Interface (VTS-API) This document specifies the Voucher Trading System Application Programming Interface (VTS-API). The VTS-API allows a wallet or other application to issue, transfer, and redeem vouchers in a uniform manner independent of the VTS implementation. The VTS is a system for securely transferring vouchers; e.g., coupons, tickets, loyalty points, and gift certificates. This process is often necessary in the course of payment and/or delivery transactions. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: M. Terada, K. Fujimura |
| RFC4155 The application/mbox Media Type This memo requests that the application/mbox media type be authorized for allocation by the IESG, according to the terms specified in RFC 2048. This memo also defines a default format for the mbox database, which must be supported by all conformant implementations. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: E. Hall |
| RFC4156 The wais URI Scheme This document specifies the wais Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track. This memo defines a Historic Document for the Internet community. | August 2005 Status: HISTORIC Autor: P. Hoffman |
| RFC4157 The prospero URI Scheme This document specifies the prospero Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track. This memo defines a Historic Document for the Internet community. | August 2005 Status: HISTORIC Autor: P. Hoffman |
| RFC4158 Internet X.509 Public Key Infrastructure: Certification Path Building This document provides guidance and recommendations to developers building X.509 public-key certification paths within their applications. By following the guidance and recommendations defined in this document, an application developer is more likely to develop a robust X.509 certificate-enabled application that can build valid certification paths across a wide range of PKI environments. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: M. Cooper, Y. Dzambasow, P. Hesse, S. Joseph, R. Nicholas |
| RFC4159 Deprecation of "ip6.int" This document advises of the deprecation of the use of "ip6.int" for Standards Conformant IPv6 implementations. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2005 Status: BEST CURRENT PRACTICE Autor: G. Huston |
| RFC4160 Internet Fax Gateway Requirements To allow connectivity between the General Switched Telephone Network facsimile service (GSTN fax) and the e-mail-based Internet Fax service (i-fax) an "Internet Fax Gateway" is required. This document provides recommendations for the functionality of Internet Fax Gateways. In this context, an "offramp gateway" provides facsimile data transmission from i-fax to GSTN fax; vice versa, an "onramp gateway" provides data transmission form GSTN fax to i-fax. The recommendations in this document apply to the integrated service including Internet Fax terminals, computers with i-fax software on the Internet, and GSTN Fax terminals on the GSTN. This memo provides information for the Internet community. | August 2005 Status: INFORMATIONAL Autor: K. Mimura, K. Yokoyama, T. Satoh, C. Kanaide, C. Allocchio |
| RFC4161 Guidelines for Optional Services for Internet Fax Gateways To allow connectivity between the general switched telephone network facsimile service (GSTN fax) and the e-mail-based Internet Fax service (i-fax), an "Internet Fax Gateway" is required. This document provides guidelines for the optional functionality of Internet Fax Gateways. In this context, an "offramp gateway" provides facsimile data transmission from i-fax to GSTN fax; vice versa, an "onramp gateway" provides data transmission from GSTN fax to i-fax. The recommendations in this document apply to the integrated service including Internet Fax terminals, computers with i-fax software on the Internet, and GSTN fax terminals on the GSTN. | August 2005 Status: INFORMATIONAL Autor: K. Mimura, K. Yokoyama, T. Satoh, K. Watanabe, C. Kanaide |
| RFC4162 Addition of SEED Cipher Suites to Transport Layer Security (TLS) This document proposes the addition of new cipher suites to the Transport Layer Security (TLS) protocol to support the SEED encryption algorithm as a bulk cipher algorithm. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: H.J. Lee, J.H. Yoon, J.I. Lee |
| RFC4163 RObust Header Compression (ROHC): Requirements on TCP/IP Header Compression This document contains requirements on the TCP/IP header compression scheme (profile) to be developed by the RObust Header Compression (ROHC) Working Group. The document discusses the scope of TCP compression, performance considerations, assumptions about the surrounding environment, as well as Intellectual Property Rights concerns. The structure of this document is inherited from RFC 3096, which defines IP/UDP/RTP requirements for ROHC. This memo provides information for the Internet community. | August 2005 Status: INFORMATIONAL Autor: L-E. Jonsson |
| RFC4164 RObust Header Compression (ROHC): Context Replication for ROHC Profiles This document defines context replication, a complement to the context initialization procedure found in Robust Header Compression (ROHC), as specified in RFC 3095. Profiles defining support for context replication may use the mechanism described herein to establish a new context based on another already existing context. Context replication is introduced to reduce the overhead of the context establishment procedure. It may be especially useful for the compression of multiple short-lived flows that may be occurring simultaneously or near-simultaneously, such as short-lived TCP flows. [STANDARDS-TRACK] | August 2005 Status: PROPOSED STANDARD Autor: G. Pelletier |
| RFC4165 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA) This document defines a protocol supporting the transport of Signaling System Number 7 (SS7) Message Transfer Part (MTP) Level 3 signaling messages over Internet Protocol (IP) using the services of the Stream Control Transmission Protocol (SCTP). This protocol would be used between SS7 Signaling Points using the MTP Level 3 protocol. The SS7 Signaling Points may also use standard SS7 links using the SS7 MTP Level 2 to provide transport of MTP Level 3 signaling messages. The protocol operates in a manner similar to MTP Level 2 so as to provide peer-to-peer communication between SS7 endpoints. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: T. George, B. Bidulock, R. Dantu, H. Schwarzbauer, K. Morneault |
| RFC4166 Telephony Signalling Transport over Stream Control Transmission Protocol (SCTP) Applicability Statement This document describes the applicability of the several protocols developed under the signalling transport framework. A description of the main issues regarding the use of the Stream Control Transmission Protocol (SCTP) and an explanation of each adaptation layer for transport of telephony signalling information over IP infrastructure are given. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: L. Coene, J. Pastor-Balbas |
| RFC4167 Graceful OSPF Restart Implementation Report Graceful OSPF Restart, as specified in RFC 3623, provides a mechanism whereby an OSPF router can stay on the forwarding path even as its OSPF software is restarted. This document provides an implementation report for this extension to the base OSPF protocol. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: A. Lindem |
| RFC4168 The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP) This document specifies a mechanism for usage of SCTP (the Stream Control Transmission Protocol) as the transport mechanism between SIP (Session Initiation Protocol) entities. SCTP is a new protocol that provides several features that may prove beneficial for transport between SIP entities that exchange a large amount of messages, including gateways and proxies. As SIP is transport-independent, support of SCTP is a relatively straightforward process, nearly identical to support for TCP. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne, G. Camarillo |
| RFC4169 Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2 HTTP Digest, as specified in RFC 2617, is known to be vulnerable to man-in-the-middle attacks if the client fails to authenticate the server in TLS, or if the same passwords are used for authentication in some other context without TLS. This is a general problem that exists not just with HTTP Digest, but also with other IETF protocols that use tunneled authentication. This document specifies version 2 of the HTTP Digest AKA algorithm (RFC 3310). This algorithm can be implemented in a way that it is resistant to the man-in-the-middle attack. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: V. Torvinen, J. Arkko, M. Naslund |
| RFC4170 Tunneling Multiplexed Compressed RTP (TCRTP) This document describes a method to improve the bandwidth utilization of RTP streams over network paths that carry multiple Real-time Transport Protocol (RTP) streams in parallel between two endpoints, as in voice trunking. The method combines standard protocols that provide compression, multiplexing, and tunneling over a network path for the purpose of reducing the bandwidth used when multiple RTP streams are carried over that path. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | November 2005 Status: BEST CURRENT PRACTICE Autor: B. Thompson, T. Koren, D. Wing |
| RFC4171 Internet Storage Name Service (iSNS) This document specifies the Internet Storage Name Service (iSNS) protocol, used for interaction between iSNS servers and iSNS clients, which facilitates automated discovery, management, and configuration of iSCSI and Fibre Channel devices (using iFCP gateways) on a TCP/IP network. iSNS provides intelligent storage discovery and management services comparable to those found in Fibre Channel networks, allowing a commodity IP network to function in a capacity similar to that of a storage area network. iSNS facilitates a seamless integration of IP and Fibre Channel networks due to its ability to emulate Fibre Channel fabric services and to manage both iSCSI and Fibre Channel devices. iSNS thereby provides value in any storage network comprised of iSCSI devices, Fibre Channel devices (using iFCP gateways), or any combination thereof. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: J. Tseng, K. Gibbons, F. Travostino, C. Du Laney, J. Souza |
| RFC4172 iFCP - A Protocol for Internet Fibre Channel Storage Networking This document specifies an architecture and a gateway-to-gateway protocol for the implementation of fibre channel fabric functionality over an IP network. This functionality is provided through TCP protocols for fibre channel frame transport and the distributed fabric services specified by the fibre channel standards. The architecture enables internetworking of fibre channel devices through gateway-accessed regions with the fault isolation properties of autonomous systems and the scalability of the IP network. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: C. Monia, R. Mullendore, F. Travostino, W. Jeong, M. Edwards |
| RFC4173 Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) Protocol Internet Small Computer System Interface (iSCSI) is a proposed transport protocol for Small Computer Systems Interface (SCSI) that operates on top of TCP. This memo describes a standard mechanism for enabling clients to bootstrap themselves using the iSCSI protocol. The goal of this standard is to enable iSCSI boot clients to obtain the information to open an iSCSI session with the iSCSI boot server. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: P. Sarkar, D. Missimer, C. Sapuntzakis |
| RFC4174 The IPv4 Dynamic Host Configuration Protocol (DHCP) Option for the Internet Storage Name Service This document describes the Dynamic Host Configuration Protocol (DHCP) option to allow Internet Storage Name Service (iSNS) clients to discover the location of the iSNS server automatically through the use of DHCP for IPv4. iSNS provides discovery and management capabilities for Internet SCSI (iSCSI) and Internet Fibre Channel Protocol (iFCP) storage devices in an enterprise-scale IP storage network. iSNS provides intelligent storage management services comparable to those found in Fibre Channel networks, allowing a commodity IP network to function in a similar capacity to that of a storage area network. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: C. Monia, J. Tseng, K. Gibbons |
| RFC4175 RTP Payload Format for Uncompressed Video This memo specifies a packetization scheme for encapsulating uncompressed video into a payload format for the Real-time Transport Protocol, RTP. It supports a range of standard- and high-definition video formats, including common television formats such as ITU BT.601, and standards from the Society of Motion Picture and Television Engineers (SMPTE), such as SMPTE 274M and SMPTE 296M. The format is designed to be applicable and extensible to new video formats as they are developed. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: L. Gharai, C. Perkins |
| RFC4176 Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management This document provides a framework for the operation and management of Layer 3 Virtual Private Networks (L3VPNs). This framework intends to produce a coherent description of the significant technical issues that are important in the design of L3VPN management solutions. The selection of specific approaches, and making choices among information models and protocols are outside the scope of this document. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: Y. El Mghazli, T. Nadeau, M. Boucadair, K. Chan, A. Gonguet |
| RFC4177 Architectural Approaches to Multi-homing for IPv6 This memo provides an analysis of the architectural aspects of multi-homing support for the IPv6 protocol suite. The purpose of this analysis is to provide a taxonomy for classification of various proposed approaches to multi-homing. It is also an objective of this exercise to identify common aspects of this domain of study, and also to provide a framework that can allow exploration of some of the further implications of various architectural extensions that are intended to support multi-homing. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: G. Huston |
| RFC4178 The Simple and Protected Generic Security Service Application Program Interface (GSS-API) Negotiation Mechanism This document specifies a negotiation mechanism for the Generic Security Service Application Program Interface (GSS-API), which is described in RFC 2743. GSS-API peers can use this negotiation mechanism to choose from a common set of security mechanisms. If per-message integrity services are available on the established mechanism context, then the negotiation is protected against an attacker that forces the selection of a mechanism not desired by the peers. | October 2005 Status: PROPOSED STANDARD Autor: L. Zhu, P. Leach, K. Jaganathan, W. Ingersoll |
| RFC4179 Using Universal Content Identifier (UCI) as Uniform Resource Names (URN) This document describes a Uniform Resource Name (URN) namespace for the National Computerization Agency (NCA) for naming persistent digital resources such as music, videos, texts, images, e-books, and other types of digital resources produced or managed by NCA. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: S. Kang |
| RFC4180 Common Format and MIME Type for Comma-Separated Values (CSV) Files This RFC documents the format used for Comma-Separated Values (CSV) files and registers the associated MIME type "text/csv". This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: Y. Shafranovich |
| RFC4181 Guidelines for Authors and Reviewers of MIB Documents This memo provides guidelines for authors and reviewers of IETF standards-track specifications containing MIB modules. Applicable portions may be used as a basis for reviews of other MIB documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 2005 Status: BEST CURRENT PRACTICE Autor: C. Heard |
| RFC4182 Removing a Restriction on the use of MPLS Explicit NULL The label stack encoding for Multi-protocol Label Switching (MPLS) defines a reserved label value known as "IPv4 Explicit NULL" and a reserved label value known as "IPv6 Explicit NULL". Previously, these labels were only legal when they occurred at the bottom of the MPLS label stack. This restriction is now removed, so that these label values may legally occur anywhere in the stack. | September 2005 Status: PROPOSED STANDARD Autor: E. Rosen |
| RFC4183 A Suggested Scheme for DNS Resolution of Networks and Gateways This document suggests a method of using DNS to determine the network that contains a specified IP address, the netmask of that network, and the address(es) of first-hop routers(s) on that network. This method supports variable-length subnet masks, delegation of subnets on non-octet boundaries, and multiple routers per subnet. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: E. Warnicke |
| RFC4184 RTP Payload Format for AC-3 Audio This document describes an RTP payload format for transporting audio data using the AC-3 audio compression standard. AC-3 is a high quality, multichannel audio coding system that is used for United States HDTV, DVD, cable television, satellite television and other media. The RTP payload format presented in this document includes support for data fragmentation. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: B. Link, T. Hager, J. Flaks |
| RFC4185 National and Local Characters for DNS Top Level Domain (TLD) Names In the context of work on internationalizing the Domain Name System (DNS), there have been extensive discussions about "multilingual" or "internationalized" top level domain names (TLDs), especially for countries whose predominant language is not written in a Roman-based script. This document reviews some of the motivations for such domains, several suggestions that have been made to provide needed functionality, and the constraints that the DNS imposes. It then suggests an alternative, local translation, that may solve a superset of the problem while avoiding protocol changes, serious deployment delays, and other difficulties. The suggestion utilizes a localization technique in applications to permit any TLD to be accessed using the vocabulary and characters of any language. It is not restricted to language- or country-specific "multilingual" TLDs in the language(s) and script(s) of that country. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: J. Klensin |
| RFC4186 Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM) This document specifies an Extensible Authentication Protocol (EAP) mechanism for authentication and session key distribution using the Global System for Mobile Communications (GSM) Subscriber Identity Module (SIM). GSM is a second generation mobile network standard. The EAP-SIM mechanism specifies enhancements to GSM authentication and key agreement whereby multiple authentication triplets can be combined to create authentication responses and session keys of greater strength than the individual GSM triplets. The mechanism also includes network authentication, user anonymity support, result indications, and a fast re-authentication procedure. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: H. Haverinen, J. Salowey |
| RFC4187 Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA) This document specifies an Extensible Authentication Protocol (EAP) mechanism for authentication and session key distribution that uses the Authentication and Key Agreement (AKA) mechanism. AKA is used in the 3rd generation mobile networks Universal Mobile Telecommunications System (UMTS) and CDMA2000. AKA is based on symmetric keys, and typically runs in a Subscriber Identity Module, which is a UMTS Subscriber Identity Module, USIM, or a (Removable) User Identity Module, (R)UIM, similar to a smart card. | January 2006 Status: INFORMATIONAL Autor: J. Arkko, H. Haverinen |
| RFC4188 Definitions of Managed Objects for Bridges This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing MAC bridges based on the IEEE 802.1D-1998 standard between Local Area Network (LAN) segments. Provisions are made for the support of transparent bridging. Provisions are also made so that these objects apply to bridges connected by subnetworks other than LAN segments. | September 2005 Status: PROPOSED STANDARD Autor: K. Norseth, E. Bell |
| RFC4189 Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP) A Session Initiation Protocol (SIP) User Agent (UA) does not always trust all intermediaries in its request path to inspect its message bodies and/or headers contained in its message. The UA might want to protect the message bodies and/or headers from intermediaries, except those that provide services based on its content. This situation requires a mechanism called "end-to-middle security" to secure the information passed between the UA and intermediaries, which does not interfere with end-to-end security. This document defines a set of requirements for a mechanism to achieve end-to-middle security. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: K. Ono, S. Tachimoto |
| RFC4190 Framework for Supporting Emergency Telecommunications Service (ETS) in IP Telephony This document presents a framework for supporting authorized, emergency-related communication within the context of IP telephony. We present a series of objectives that reflect a general view of how authorized emergency service, in line with the Emergency Telecommunications Service (ETS), should be realized within today's IP architecture and service models. From these objectives, we present a corresponding set of protocols and capabilities, which provide a more specific set of recommendations regarding existing IETF protocols. Finally, we present two scenarios that act as guiding models for the objectives and functions listed in this document. These models, coupled with an example of an existing service in the Public Switched Telephone Network (PSTN), contribute to a constrained solution space. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: K. Carlberg, I. Brown, C. Beard |
| RFC4191 Default Router Preferences and More-Specific Routes This document describes an optional extension to Router Advertisement messages for communicating default router preferences and more-specific routes from routers to hosts. This improves the ability of hosts to pick an appropriate router, especially when the host is multi-homed and the routers are on different links. The preference values and specific routes advertised to hosts require administrative configuration; they are not automatically derived from routing tables. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: R. Draves, D. Thaler |
| RFC4192 Procedures for Renumbering an IPv6 Network without a Flag Day This document describes a procedure that can be used to renumber a network from one prefix to another. It uses IPv6's intrinsic ability to assign multiple addresses to a network interface to provide continuity of network service through a "make-before-break" transition, as well as addresses naming and configuration management issues. It also uses other IPv6 features to minimize the effort and time required to complete the transition from the old prefix to the new prefix. This memo provides information for the Internet community. | September 2005 Status: INFORMATIONAL Autor: F. Baker, E. Lear, R. Droms |
| RFC4193 Unique Local IPv6 Unicast Addresses This document defines an IPv6 unicast address format that is globally unique and is intended for local communications, usually inside of a site. These addresses are not expected to be routable on the global Internet. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: R. Hinden, B. Haberman |
| RFC4194 The S Hexdump Format This document specifies the S Hexdump Format (SHF), a new, XML-based open format for describing binary data in hexadecimal notation. SHF provides the ability to describe both small and large, simple and complex hexadecimal data dumps in an open, modern, transport- and vendor-neutral format. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: J. Strombergson, L. Walleij, P. Faltstrom |
| RFC4195 A Uniform Resource Name (URN) Namespace for the TV-Anytime Forum This document describes a Uniform Resource Name (URN) namespace that is engineered by the TV-Anytime Forum for naming persistent resources published by the TV-Anytime Forum including the TV-Anytime Forum Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, and other documents. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: W. Kameyama |
| RFC4196 The SEED Cipher Algorithm and Its Use with IPsec This document describes the use of the SEED block cipher algorithm in the Cipher Block Chaining Mode, with an explicit IV, as a confidentiality mechanism within the context of the IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: H.J. Lee, J.H. Yoon, S.L. Lee, J.I. Lee |
| RFC4197 Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks This document defines the specific requirements for edge-to-edge emulation of circuits carrying Time Division Multiplexed (TDM) digital signals of the Plesiochronous Digital Hierarchy as well as the Synchronous Optical NETwork/Synchronous Digital Hierarchy over packet-switched networks. It is aligned to the common architecture for Pseudo Wire Emulation Edge-to-Edge (PWE3). It makes references to the generic requirements for PWE3 where applicable and complements them by defining requirements originating from specifics of TDM circuits. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: M. Riegel |
| RFC4198 A Uniform Resource Name (URN) Namespace for Federated Content This document describes a URN (Uniform Resource Name) namespace for identifying content resources within federated content collections. A federated content collection often does not have a strong centralized authority but relies upon shared naming, metadata, and access conventions to provide interoperability among its members. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: D. Tessman |
| RFC4201 Link Bundling in MPLS Traffic Engineering (TE) For the purpose of Generalized Multi-Protocol Label Switching (GMPLS) signaling, in certain cases a combination of <link identifier, label> is not sufficient to unambiguously identify the appropriate resource used by a Label Switched Path (LSP). Such cases are handled by using the link bundling construct, which is described in this document. This document updates the interface identification TLVs, which are defined in the GMPLS Signaling Functional Description. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter, L. Berger |
| RFC4202 Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) This document specifies routing extensions in support of carrying link state information for Generalized Multi-Protocol Label Switching (GMPLS). This document enhances the routing extensions required to support MPLS Traffic Engineering (TE). [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter |
| RFC4203 OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) This document specifies encoding of extensions to the OSPF routing protocol in support of Generalized Multi-Protocol Label Switching (GMPLS). [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter |
| RFC4204 Link Management Protocol (LMP) For scalability purposes, multiple data links can be combined to form a single traffic engineering (TE) link. Furthermore, the management of TE links is not restricted to in-band messaging, but instead can be done using out-of-band techniques. This document specifies a link management protocol (LMP) that runs between a pair of nodes and is used to manage TE links. Specifically, LMP will be used to maintain control channel connectivity, verify the physical connectivity of the data links, correlate the link property information, suppress downstream alarms, and localize link failures for protection/restoration purposes in multiple kinds of networks. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: J. Lang |
| RFC4205 Intermediate System to Intermediate System (IS-IS) Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) This document specifies encoding of extensions to the IS-IS routing protocol in support of Generalized Multi-Protocol Label Switching (GMPLS). This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: K. Kompella, Y. Rekhter |
| RFC4206 Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE) To improve scalability of Generalized Multi-Protocol Label Switching (GMPLS) it may be useful to aggregate Label Switched Paths (LSPs) by creating a hierarchy of such LSPs. A way to create such a hierarchy is by (a) a Label Switching Router (LSR) creating a Traffic Engineering Label Switched Path (TE LSP), (b) the LSR forming a forwarding adjacency (FA) out of that LSP (by advertising this LSP as a Traffic Engineering (TE) link into the same instance of ISIS/OSPF as the one that was used to create the LSP), (c) allowing other LSRs to use FAs for their path computation, and (d) nesting of LSPs originated by other LSRs into that LSP (by using the label stack construct). | October 2005 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter |
| RFC4207 Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages This document details the Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) technology-specific information needed when sending Link Management Protocol (LMP) test messages. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: J. Lang, D. Papadimitriou |
| RFC4208 Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model Generalized Multiprotocol Label Switching (GMPLS) defines both routing and signaling protocols for the creation of Label Switched Paths (LSPs) in various switching technologies. These protocols can be used to support a number of deployment scenarios. This memo addresses the application of GMPLS to the overlay model. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: G. Swallow, J. Drake, H. Ishimatsu, Y. Rekhter |
| RFC4209 Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems The Link Management Protocol (LMP) is defined to manage traffic engineering (TE) links. In its present form, LMP focuses on peer nodes, i.e., nodes that peer in signaling and/or routing. This document proposes extensions to LMP to allow it to be used between a peer node and an adjacent optical line system (OLS). These extensions are intended to satisfy the "Optical Link Interface Requirements" described in a companion document. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: A. Fredette, J. Lang |
| RFC4210 Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP) This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocol (CMP). Protocol messages are defined for X.509v3 certificate creation and management. CMP provides on-line interactions between PKI components, including an exchange between a Certification Authority (CA) and a client system. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: C. Adams, S. Farrell, T. Kause, T. Mononen |
| RFC4211 Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF) This document describes the Certificate Request Message Format (CRMF) syntax and semantics. This syntax is used to convey a request for a certificate to a Certification Authority (CA), possibly via a Registration Authority (RA), for the purposes of X.509 certificate production. The request will typically include a public key and the associated registration information. This document does not define a certificate request protocol. [STANDARDS-TRACK] | September 2005 Status: PROPOSED STANDARD Autor: J. Schaad |
| RFC4212 Alternative Certificate Formats for the Public-Key Infrastructure Using X.509 (PKIX) Certificate Management Protocols The Public-Key Infrastructure using X.509 (PKIX) Working Group of the Internet Engineering Task Force (IETF) has defined a number of certificate management protocols. These protocols are primarily focused on X.509v3 public-key certificates. However, it is sometimes desirable to manage certificates in alternative formats as well. This document specifies how such certificates may be requested using the Certificate Request Message Format (CRMF) syntax that is used by several different protocols. It also explains how alternative certificate formats may be incorporated into such popular protocols as PKIX Certificate Management Protocol (PKIX-CMP) and Certificate Management Messages over CMS (CMC). This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: M. Blinov, C. Adams |
| RFC4213 Basic Transition Mechanisms for IPv6 Hosts and Routers This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. Two mechanisms are specified, dual stack and configured tunneling. Dual stack implies providing complete implementations of both versions of the Internet Protocol (IPv4 and IPv6), and configured tunneling provides a means to carry IPv6 packets over unmodified IPv4 routing infrastructures. | October 2005 Status: PROPOSED STANDARD Autor: E. Nordmark, R. Gilligan |
| RFC4214 Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects IPv6 hosts/routers over IPv4 networks. ISATAP views the IPv4 network as a link layer for IPv6 and views other nodes on the network as potential IPv6 hosts/routers. ISATAP supports an automatic tunneling abstraction similar to the Non-Broadcast Multiple Access (NBMA) model. This memo defines an Experimental Protocol for the Internet community. | October 2005 Status: EXPERIMENTAL Autor: F. Templin, T. Gleeson, M. Talwar, D. Thaler |
| RFC4215 Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) Networks This document analyzes the transition to IPv6 in Third Generation Partnership Project (3GPP) packet networks. These networks are based on General Packet Radio Service (GPRS) technology, and the radio network architecture is based on Global System for Mobile Communications (GSM) or Universal Mobile Telecommunications System (UMTS)/Wideband Code Division Multiple Access (WCDMA) technology. | October 2005 Status: INFORMATIONAL Autor: J. Wiljakka |
| RFC4216 MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements This document discusses requirements for the support of inter-AS MPLS Traffic Engineering (MPLS TE). Its main objective is to present a set of requirements and scenarios which would result in general guidelines for the definition, selection, and specification development for any technical solution(s) meeting these requirements and supporting the scenarios. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: R. Zhang, J.-P. Vasseur |
| RFC4217 Securing FTP with TLS This document describes a mechanism that can be used by FTP clients and servers to implement security and authentication using the TLS protocol defined by RFC 2246, "The TLS Protocol Version 1.0.", and the extensions to the FTP protocol defined by RFC 2228, "FTP Security Extensions". It describes the subset of the extensions that are required and the parameters to be used, discusses some of the policy issues that clients and servers will need to take, considers some of the implications of those policies, and discusses some expected behaviours of implementations to allow interoperation. This document is intended to provide TLS support for FTP in a similar way to that provided for SMTP in RFC 2487, "SMTP Service Extension for Secure SMTP over Transport Layer Security", and HTTP in RFC 2817, "Upgrading to TLS Within HTTP/1.1.". | October 2005 Status: PROPOSED STANDARD Autor: P. Ford-Hutchinson |
| RFC4218 Threats Relating to IPv6 Multihoming Solutions This document lists security threats related to IPv6 multihoming. Multihoming can introduce new opportunities to redirect packets to different, unintended IP addresses. | October 2005 Status: INFORMATIONAL Autor: E. Nordmark, T. Li |
| RFC4219 Things Multihoming in IPv6 (MULTI6) Developers Should Think About This document specifies a set of questions that authors should be prepared to answer as part of a solution to multihoming with IPv6. The questions do not assume that multihoming is the only problem of interest, nor do they demand a more general solution. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: E. Lear |
| RFC4220 Traffic Engineering Link 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 for modeling TE links as described in the Link Bundling in MPLS Traffic Engineering (TE) document. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: M. Dubuc, T. Nadeau, J. Lang |
| RFC4221 Multiprotocol Label Switching (MPLS) Management Overview A range of Management Information Base (MIB) modules has been developed to help model and manage the various aspects of Multiprotocol Label Switching (MPLS) networks. These MIB modules are defined in separate documents that focus on the specific areas of responsibility of the modules that they describe. | November 2005 Status: INFORMATIONAL Autor: T. Nadeau, C. Srinivasan, A. Farrel |
| RFC4222 Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion Avoidance This document recommends methods that are intended to improve the scalability and stability of large networks using Open Shortest Path First (OSPF) Version 2 protocol. The methods include processing OSPF Hellos and Link State Advertisement (LSA) Acknowledgments at a higher priority compared to other OSPF packets, and other congestion avoidance procedures. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 2005 Status: BEST CURRENT PRACTICE Autor: G. Choudhury |
| RFC4223 Reclassification of RFC 1863 to Historic This memo reclassifies RFC 1863, A BGP/IDRP Route Server alternative to a full mesh routing, to Historic status. This memo also obsoletes RFC 1863. This memo provides information for the Internet community. | October 2005 Status: INFORMATIONAL Autor: P. Savola |
| RFC4224 RObust Header Compression (ROHC): ROHC over Channels That Can Reorder Packets RObust Header Compression (ROHC), RFC 3095, defines a framework for header compression, along with a number of compression protocols (profiles). One operating assumption for the profiles defined in RFC 3095 is that the channel between compressor and decompressor is required to maintain packet ordering. This document discusses aspects of using ROHC over channels that can reorder packets. It provides guidelines on how to implement existing profiles over such channels, as well as suggestions for the design of new profiles. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: G. Pelletier, L-E. Jonsson, K. Sandlund |
| RFC4225 Mobile IP Version 6 Route Optimization Security Design Background This document is an account of the rationale behind the Mobile IPv6 (MIPv6) Route Optimization security design. The purpose of this document is to present the thinking and to preserve the reasoning behind the Mobile IPv6 security design in 2001 - 2002. | December 2005 Status: INFORMATIONAL Autor: P. Nikander, J. Arkko, T. Aura, G. Montenegro, E. Nordmark |
| RFC4226 HOTP: An HMAC-Based One-Time Password Algorithm This document describes an algorithm to generate one-time password values, based on Hashed Message Authentication Code (HMAC). A security analysis of the algorithm is presented, and important parameters related to the secure deployment of the algorithm are discussed. The proposed algorithm can be used across a wide range of network applications ranging from remote Virtual Private Network (VPN) access, Wi-Fi network logon to transaction-oriented Web applications. | December 2005 Status: INFORMATIONAL Autor: D. M'Raihi, M. Bellare, F. Hoornaert, D. Naccache, O. Ranen |
| RFC4227 Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol (BEEP) core. A SOAP binding describes how SOAP messages are transmitted in the network. | January 2006 Status: PROPOSED STANDARD Autor: E. O'Tuathail, M. Rose |
| RFC4228 Requirements for an IETF Draft Submission Toolset This document specifies requirements for an IETF toolset to facilitate Internet-Draft submission, validation, and posting. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: A. Rousskov |
| RFC4229 HTTP Header Field Registrations This document defines the initial contents of a permanent IANA registry for HTTP header fields and a provisional repository for HTTP header fields, per RFC 3864. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: M. Nottingham, J. Mogul |
| RFC4230 RSVP Security Properties This document summarizes the security properties of RSVP. The goal of this analysis is to benefit from previous work done on RSVP and to capture knowledge about past activities. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: H. Tschofenig, R. Graveman |
| RFC4231 Identifiers and Test Vectors for HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 This document provides test vectors for the HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 message authentication schemes. It also provides ASN.1 object identifiers and Uniform Resource Identifiers (URIs) to identify use of these schemes in protocols. The test vectors provided in this document may be used for conformance testing. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: M. Nystrom |
| RFC4233 Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer This document defines a protocol for backhauling of Integrated Services Digital Network (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). It is assumed that the SG receives ISDN signaling over a standard ISDN interface. | January 2006 Status: PROPOSED STANDARD Autor: K. Morneault, S. Rengasami, M. Kalla, G. Sidebottom |
| RFC4234 Augmented BNF for Syntax Specifications: ABNF Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity, with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] | October 2005 Status: DRAFT STANDARD Autor: D. Crocker, P. Overell |
| RFC4235 An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP) This document defines a dialog event package for the SIP Events architecture, along with a data format used in notifications for this package. The dialog package allows users to subscribe to another user and to receive notification of the changes in state of INVITE-initiated dialog usages in which the subscribed-to user is involved. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne, R. Mahy |
| RFC4236 HTTP Adaptation with Open Pluggable Edge Services (OPES) Open Pluggable Edge Services (OPES) framework documents several application-agnostic mechanisms such as OPES tracing, OPES bypass, and OPES callout protocol. This document extends those generic mechanisms for Hypertext Transfer Protocol (HTTP) adaptation. Together, application-agnostic OPES documents and this HTTP profile constitute a complete specification for HTTP adaptation with OPES. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: A. Rousskov, M. Stecher |
| RFC4237 Voice Messaging Directory Service This document provides details of the Voice Profile for Internet Mail (VPIM) directory service. The service provides the email address of the recipient that is given a telephone number. It optionally provides the spoken name of the recipient and the media capabilities of the recipient. | October 2005 Status: PROPOSED STANDARD Autor: G. Vaudreuil |
| RFC4238 Voice Message Routing Service Voice messaging is traditionally addressed using telephone number addressing. This document describes two techniques for routing voice messages based on a telephone number. The complete service uses the Voice Profile for Internet Mail (VPIM) Directory service to lookup a VPIM email address with a telephone number and confirm that the address is both valid and associated with the intended recipient. However, this service will take time to become widely deployed in the near term. This document also describes a basic send-and-pray service that routes and delivers messages using only the ENUM telephone number resolution service and the existing DNS mail routing facilities. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: G. Vaudreuil |
| RFC4239 Internet Voice Messaging (IVM) This document describes the carriage of voicemail messages over Internet mail as part of a unified messaging infrastructure. | November 2005 Status: PROPOSED STANDARD Autor: S. McRae, G. Parsons |
| RFC4240 Basic Network Media Services with SIP In SIP-based networks, there is a need to provide basic network media services. Such services include network announcements, user interaction, and conferencing services. These services are basic building blocks, from which one can construct interesting applications. In order to have interoperability between servers offering these building blocks (also known as Media Servers) and application developers, one needs to be able to locate and invoke such services in a well defined manner. | December 2005 Status: INFORMATIONAL Autor: E. Burger, J. Van Dyke, A. Spitzer |
| RFC4241 A Model of IPv6/IPv4 Dual Stack Internet Access Service This memo is a digest of the user network interface specification of NTT Communications' dual stack ADSL access service, which provide a IPv6/IPv4 dual stack services to home users. In order to simplify user setup, these services have a mechanism to configure IPv6 specific parameters automatically. The memo focuses on two basic parameters: the prefix assigned to the user and the addresses of IPv6 DNS servers, and it specifies a way to deliver these parameters to Customer Premises Equipment (CPE) automatically. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: Y. Shirasaki, S. Miyakawa, T. Yamasaki, A. Takenouchi |
| RFC4242 Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) This document describes a Dynamic Host Configuration Protocol for IPv6 (DHCPv6) option for specifying an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6. It is used with stateless DHCPv6 as there are no addresses or other entities with lifetimes that can tell the client when to contact the DHCPv6 server to refresh its configuration. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: S. Venaas, T. Chown, B. Volz |
| RFC4243 Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option This memo defines a new Vendor-Specific Information suboption for the Dynamic Host Configuration Protocol's (DHCP) relay agent information option. The suboption allows a DHCP relay agent to include vendor-specific information in the DHCP messages it forwards, as configured by its administrator. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: M. Stapp, R. Johnson, T. Palaniappan |
| RFC4244 An Extension to the Session Initiation Protocol (SIP) for Request History Information This document defines a standard mechanism for capturing the history information associated with a Session Initiation Protocol (SIP) request. This capability enables many enhanced services by providing the information as to how and why a call arrives at a specific application or user. This document defines a new optional SIP header, History-Info, for capturing the history information in requests. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: M. Barnes |
| RFC4245 High-Level Requirements for Tightly Coupled SIP Conferencing This document examines a wide range of conferencing requirements for tightly coupled SIP conferences. Separate documents will map the requirements to existing protocol primitives, define new protocol extensions, and introduce new protocols as needed. Together, these documents will provide a guide for building interoperable SIP conferencing applications. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: O. Levin, R. Even |
| RFC4246 International Standard Audiovisual Number (ISAN) URN Definition The International Standard Audiovisual Number (ISAN) is a standard numbering system for the unique and international identification of audiovisual works. This document is the definition of the formal Uniform Resource Name (URN) Namespace Identifier (NID) for ISAN. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: M. Dolan |
| RFC4247 Requirements for Header Compression over MPLS Voice over IP (VoIP) typically uses the encapsulation voice/RTP/UDP/IP. When MPLS labels are added, this becomes voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN, the packet header is typically 48 bytes, while the voice payload is often no more than 30 bytes, for example. Header compression can significantly reduce the overhead through various compression mechanisms, such as enhanced compressed RTP (ECRTP) and robust header compression (ROHC). We consider using MPLS to route compressed packets over an MPLS Label Switched Path (LSP) without compression/decompression cycles at each router. This approach can increase the bandwidth efficiency as well as processing scalability of the maximum number of simultaneous flows that use header compression at each router. In this document, we give a problem statement, goals and requirements, and an example scenario. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: J. Ash, B. Goode, J. Hand, R. Zhang |
| RFC4248 The telnet URI Scheme This document specifies the telnet Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track. [STANDARDS-TRACK] | October 2005 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC4249 Implementer-Friendly Specification of Message and MIME-Part Header Fields and Field Components Implementation of generators and parsers of header fields requires certain information about those fields. Interoperability is most likely when all such information is explicitly provided by the technical specification of the fields. Lacking such explicit information, implementers may guess, and interoperability may suffer. This memo identifies information useful to implementers of header field generators and parsers. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: B. Lilly |
| RFC4250 The Secure Shell (SSH) Protocol Assigned Numbers This document defines the instructions to the IANA and the initial state of the IANA assigned numbers for the Secure Shell (SSH) protocol. It is intended only for the initialization of the IANA registries referenced in the set of SSH documents. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: S. Lehtinen, C. Lonvick |
| RFC4251 The Secure Shell (SSH) Protocol Architecture The Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network. This document describes the architecture of the SSH protocol, as well as the notation and terminology used in SSH protocol documents. It also discusses the SSH algorithm naming system that allows local extensions. The SSH protocol consists of three major components: The Transport Layer Protocol provides server authentication, confidentiality, and integrity with perfect forward secrecy. The User Authentication Protocol authenticates the client to the server. The Connection Protocol multiplexes the encrypted tunnel into several logical channels. Details of these protocols are described in separate documents. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: T. Ylonen, C. Lonvick |
| RFC4252 The Secure Shell (SSH) Authentication Protocol The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are described in separate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: T. Ylonen, C. Lonvick |
| RFC4253 The Secure Shell (SSH) Transport Layer Protocol The Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network. | January 2006 Status: PROPOSED STANDARD Autor: T. Ylonen, C. Lonvick |
| RFC4254 The Secure Shell (SSH) Connection Protocol Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network. | January 2006 Status: PROPOSED STANDARD Autor: T. Ylonen, C. Lonvick |
| RFC4255 Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints This document describes a method of verifying Secure Shell (SSH) host keys using Domain Name System Security (DNSSEC). The document defines a new DNS resource record that contains a standard SSH key fingerprint. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: J. Schlyter, W. Griffin |
| RFC4256 Generic Message Exchange Authentication for the Secure Shell Protocol (SSH) The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes a general purpose authentication method for the SSH protocol, suitable for interactive authentications where the authentication data should be entered via a keyboard (or equivalent alphanumeric input device). The major goal of this method is to allow the SSH client to support a whole class of authentication mechanism(s) without knowing the specifics of the actual authentication mechanism(s). [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: F. Cusack, M. Forssen |
| RFC4257 Framework for Generalized Multi-Protocol Label Switching (GMPLS)-based Control of Synchronous Digital Hierarchy/Synchronous Optical Networking (SDH/SONET) Networks Generalized Multi-Protocol Label Switching (GMPLS) is a suite of protocol extensions to MPLS to make it generally applicable, to include, for example, control of non packet-based switching, and particularly, optical switching. One consideration is to use GMPLS protocols to upgrade the control plane of optical transport networks. This document illustrates this process by describing those extensions to GMPLS protocols that are aimed at controlling Synchronous Digital Hierarchy (SDH) or Synchronous Optical Networking (SONET) networks. SDH/SONET networks make good examples of this process for a variety of reasons. This document highlights extensions to GMPLS-related routing protocols to disseminate information needed in transport path computation and network operations, together with (G)MPLS protocol extensions required for the provisioning of transport circuits. New capabilities that an GMPLS control plane would bring to SDH/SONET networks, such as new restoration methods and multi-layer circuit establishment, are also discussed. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: G. Bernstein, E. Mannie, V. Sharma, E. Gray |
| RFC4258 Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON) The Generalized Multi-Protocol Label Switching (GMPLS) suite of protocols has been defined to control different switching technologies as well as different applications. These include support for requesting Time Division Multiplexing (TDM) connections including Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) and Optical Transport Networks (OTNs). | November 2005 Status: INFORMATIONAL Autor: D. Brungard |
| RFC4259 A Framework for Transmission of IP Datagrams over MPEG-2 Networks This document describes an architecture for the transport of IP Datagrams over ISO MPEG-2 Transport Streams (TS). The MPEG-2 TS has been widely accepted not only for providing digital TV services but also as a subnetwork technology for building IP networks. Examples of systems using MPEG-2 include the Digital Video Broadcast (DVB) and Advanced Television Systems Committee (ATSC) Standards for Digital Television. | November 2005 Status: INFORMATIONAL Autor: M.-J. Montpetit, G. Fairhurst, H. Clausen, B. Collini-Nocker, H. Linder |
| RFC4260 Mobile IPv6 Fast Handovers for 802.11 Networks This document describes how a Mobile IPv6 Fast Handover could be implemented on link layers conforming to the 802.11 suite of specifications. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: P. McCann |
| RFC4261 Common Open Policy Service (COPS) Over Transport Layer Security (TLS) This document describes how to use Transport Layer Security (TLS) to secure Common Open Policy Service (COPS) connections over the Internet. | December 2005 Status: PROPOSED STANDARD Autor: J. Walker, A. Kulkarni |
| RFC4262 X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities This document defines a certificate extension for inclusion of Secure/Multipurpose Internet Mail Extensions (S/MIME) Capabilities in X.509 public key certificates, as defined by RFC 3280. This certificate extension provides an optional method to indicate the cryptographic capabilities of an entity as a complement to the S/MIME Capabilities signed attribute in S/MIME messages according to RFC 3851. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: S. Santesson |
| RFC4263 Media Subtype Registration for Media Type text/troff A text media subtype for tagging content consisting of juxtaposed text and formatting directives as used by the troff series of programs and for conveying information about the intended processing steps necessary to produce formatted output is described. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: B. Lilly |
| RFC4264 BGP Wedgies It has commonly been assumed that the Border Gateway Protocol (BGP) is a tool for distributing reachability information in a manner that creates forwarding paths in a deterministic manner. In this memo we will describe a class of BGP configurations for which there is more than one potential outcome, and where forwarding states other than the intended state are equally stable. Also, the stable state where BGP converges may be selected by BGP in a non-deterministic manner. These stable, but unintended, BGP states are termed here "BGP Wedgies". This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: T. Griffin, G. Huston |
| RFC4265 Definition of Textual Conventions for Virtual Private Network (VPN) Management This document describes Textual Conventions used for managing Virtual Private Networks (VPNs). [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: B. Schliesser, T. Nadeau |
| RFC4266 The gopher URI Scheme This document specifies the gopher Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC4267 The W3C Speech Interface Framework Media Types: application/voicexml+xml, application/ssml+xml, application/srgs, application/srgs+xml, application/ccxml+xml, and application/pls+xml This document defines the media types for the languages of the W3C Speech Interface Framework, as designed by the Voice Browser Working Group in the following specifications: the Voice Extensible Markup Language (VoiceXML), the Speech Synthesis Markup Language (SSML), the Speech Recognition Grammar Specification (SRGS), the Call Control XML (CCXML), and the Pronunciation Lexicon Specification (PLS). This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: M. Froumentin |
| RFC4268 Entity State 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 extensions to the Entity MIB to provide information about the state of physical entities. | November 2005 Status: PROPOSED STANDARD Autor: S. Chisholm, D. Perkins |
| RFC4269 The SEED Encryption Algorithm 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 encryption and the key scheduling algorithm (Section 2), the S-boxes (Appendix A), and a set of test vectors (Appendix B). | December 2005 Status: INFORMATIONAL Autor: H.J. Lee, S.J. Lee, J.H. Yoon, D.H. Cheon, J.I. Lee |
| RFC4270 Attacks on Cryptographic Hashes in Internet Protocols Recent announcements of better-than-expected collision attacks in popular hash algorithms have caused some people to question whether common Internet protocols need to be changed, and if so, how. This document summarizes the use of hashes in many protocols, discusses how the collision attacks affect and do not affect the protocols, shows how to thwart known attacks on digital certificates, and discusses future directions for protocol designers. This memo provides information for the Internet community. | November 2005 Status: INFORMATIONAL Autor: P. Hoffman, B. Schneier |
| RFC4271 A Border Gateway Protocol 4 (BGP-4) This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol. | January 2006 Status: DRAFT STANDARD Autor: Y. Rekhter, T. Li, S. Hares |
| RFC4272 BGP Security Vulnerabilities Analysis Border Gateway Protocol 4 (BGP-4), along with a host of other infrastructure protocols designed before the Internet environment became perilous, was originally designed with little consideration for protection of the information it carries. There are no mechanisms internal to BGP that protect against attacks that modify, delete, forge, or replay data, any of which has the potential to disrupt overall network routing behavior. | January 2006 Status: INFORMATIONAL Autor: S. Murphy |
| RFC4273 Definitions of Managed Objects for BGP-4 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. | January 2006 Status: PROPOSED STANDARD Autor: J. Haas, S. Hares |
| RFC4274 BGP-4 Protocol Analysis The purpose of this report is to document how the requirements for publication of a routing protocol as an Internet Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). | January 2006 Status: INFORMATIONAL Autor: D. Meyer, K. Patel |
| RFC4275 BGP-4 MIB Implementation Survey This document provides a survey of implementations of BGP-4 that support RFC 1657 MIB agents according to the BGP-4 v1 MIB specification. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: S. Hares, D. Hares |
| RFC4276 BGP-4 Implementation Report This document reports the results of the BGP-4 implementation survey. The survey had 259 questions about implementations' support of BGP-4 as specified in RFC 4271. After a brief summary of the results, each response is listed. This document contains responses from the four implementers that completed the survey (Alcatel, Cisco, Laurel, and NextHop) and brief information from three that did not (Avici, Data Connection Ltd., and Nokia). | January 2006 Status: INFORMATIONAL Autor: S. Hares, A. Retana |
| RFC4277 Experience with the BGP-4 Protocol The purpose of this memo is to document how the requirements for publication of a routing protocol as an Internet Draft Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). | January 2006 Status: INFORMATIONAL Autor: D. McPherson, K. Patel |
| RFC4278 Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 Specification The IETF Standards Process requires that all normative references for a document be at the same or higher level of standardization. RFC 2026 section 9.1 allows the IESG to grant a variance to the standard practices of the IETF. This document explains why the IESG is considering doing so for the revised version of the BGP-4 specification, which refers normatively to RFC 2385, "Protection of BGP Sessions via the TCP MD5 Signature Option". RFC 2385 will remain at the Proposed Standard level. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: S. Bellovin, A. Zinin |
| RFC4279 Pre-Shared Key Ciphersuites for Transport Layer Security (TLS) This document specifies three sets of new ciphersuites for the Transport Layer Security (TLS) protocol to support authentication based on pre-shared keys (PSKs). These pre-shared keys are symmetric keys, shared in advance among the communicating parties. The first set of ciphersuites uses only symmetric key operations for authentication. The second set uses a Diffie-Hellman exchange authenticated with a pre-shared key, and the third set combines public key authentication of the server with pre-shared key authentication of the client. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: P. Eronen, H. Tschofenig |
| RFC4280 Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control Servers This document defines new options to discover the Broadcast and Multicast Service (BCMCS) controller in an IP network. BCMCS is being developed for Third generation (3G) cellular telephone networks. Users of the service interact with a controller in the network via the Mobile Node (MN) to derive information required to receive Broadcast and Multicast Service. Dynamic Host Configuration Protocol can be used to configure the MN to access a particular controller. This document defines the related options and option codes. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: K. Chowdhury, P. Yegani, L. Madour |
| RFC4281 The Codecs Parameter for "Bucket" Media Types Several MIME type/subtype combinations exist that can contain different media formats. A receiving agent thus needs to examine the details of such media content to determine if the specific elements can be rendered given an available set of codecs. Especially when the end system has limited resources, or the connection to the end system has limited bandwidth, it would be helpful to know from the Content-Type alone if the content can be rendered. | November 2005 Status: PROPOSED STANDARD Autor: R. Gellens, D. Singer, P. Frojdh |
| RFC4282 The Network Access Identifier In order to provide roaming services, it is necessary to have a standardized method for identifying users. This document defines the syntax for the Network Access Identifier (NAI), the user identity submitted by the client during network authentication. "Roaming" may be loosely defined as the ability to use any one of multiple Internet Service Providers (ISPs), while maintaining a formal, \%customer-vendor relationship with only one. Examples of where roaming capabilities might be required include ISP "confederations" and \%ISP-provided corporate network access support. This document is a revised version of RFC 2486, which originally defined NAIs. Enhancements include international character set and privacy support, as well as a number of corrections to the original RFC. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: B. Aboba, M. Beadles, J. Arkko, P. Eronen |
| RFC4283 Mobile Node Identifier Option for Mobile IPv6 (MIPv6) Mobile IPv6 (MIPv6) defines a new Mobility header that is used by mobile nodes, correspondent nodes, and home agents in all messaging related to the creation and management of bindings. Mobile IPv6 nodes need the capability to identify themselves using an identity other than the default home IP address. Some examples of identifiers include Network Access Identifier (NAI), Fully Qualified Domain Name (FQDN), International Mobile Station Identifier (IMSI), and Mobile Subscriber Number (MSISDN). This document defines a new mobility option that can be used by Mobile IPv6 entities to identify themselves in messages containing a mobility header. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: A. Patel, K. Leung, M. Khalil, H. Akhtar, K. Chowdhury |
| RFC4284 Identity Selection Hints for the Extensible Authentication Protocol (EAP) The Extensible Authentication Protocol (EAP) is defined in RFC 3748. This document defines a mechanism that allows an access network to provide identity selection hints to an EAP peer -- the end of the link that responds to the authenticator. The purpose is to assist the EAP peer in selecting an appropriate Network Access Identifier (NAI). This is useful in situations where the peer does not receive a lower-layer indication of what network it is connecting to, or when there is no direct roaming relationship between the access network and the peer's home network. In the latter case, authentication is typically accomplished via a mediating network such as a roaming consortium or broker. | January 2006 Status: INFORMATIONAL Autor: F. Adrangi, V. Lortz, F. Bari, P. Eronen |
| RFC4285 Authentication Protocol for Mobile IPv6 IPsec is specified as the means of securing signaling messages between the Mobile Node and Home Agent for Mobile IPv6 (MIPv6). MIPv6 signaling messages that are secured include the Binding Updates and Acknowledgement messages used for managing the bindings between a Mobile Node and its Home Agent. This document proposes an alternate method for securing MIPv6 signaling messages between Mobile Nodes and Home Agents. The alternate method defined here consists of a MIPv6-specific mobility message authentication option that can be added to MIPv6 signaling messages. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: A. Patel, K. Leung, M. Khalil, H. Akhtar, K. Chowdhury |
| RFC4286 Multicast Router Discovery The concept of Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) snooping requires the ability to identify the location of multicast routers. Since snooping is not standardized, there are many mechanisms in use to identify the multicast routers. However, this can lead to interoperability issues between multicast routers and snooping switches from different vendors. | December 2005 Status: PROPOSED STANDARD Autor: B. Haberman, J. Martin |
| RFC4287 The Atom Syndication Format This document specifies Atom, an XML-based Web content and metadata syndication format. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: M. Nottingham, R. Sayre |
| RFC4288 Media Type Specifications and Registration Procedures This document defines procedures for the specification and registration of media types for use in MIME and other Internet protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | December 2005 Status: BEST CURRENT PRACTICE Autor: N. Freed, J. Klensin |
| RFC4289 Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures This document specifies IANA registration procedures for MIME external body access types and content-transfer-encodings. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | December 2005 Status: BEST CURRENT PRACTICE Autor: N. Freed, J. Klensin |
| RFC4290 Suggested Practices for Registration of Internationalized Domain Names (IDN) This document explores the issues in the registration of internationalized domain names (IDNs). The basic IDN definition allows a very large number of possible characters in domain names, and this richness may lead to serious user confusion about similar-looking names. To avoid this confusion, the IDN registration process must impose rules that disallow some otherwise-valid name combinations. This document suggests a set of mechanisms that registries might use to define and implement such rules for a broad range of languages, including adaptation of methods developed for Chinese, Japanese, and Korean domain names. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: J. Klensin |
| RFC4291 IP Version 6 Addressing Architecture 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. | February 2006 Status: DRAFT STANDARD Autor: R. Hinden, S. Deering |
| RFC4292 IP Forwarding Table MIB This document 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 related to the forwarding of Internet Protocol (IP) packets in an IP version-independent manner. This document obsoletes RFC 2096. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: B. Haberman |
| RFC4293 Management Information Base for the Internet Protocol (IP) 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 Internet Protocol (IP) in an IP version independent manner. This memo obsoletes RFCs 2011, 2465, and 2466. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: S. Routhier |
| RFC4294 IPv6 Node Requirements This document defines requirements for IPv6 nodes. It is expected that IPv6 will be deployed in a wide range of devices and situations. Specifying the requirements for IPv6 nodes allows IPv6 to function well and interoperate in a large number of situations and deployments. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: J. Loughney |
| RFC4295 Mobile IPv6 Management Information Base This memo defines a portion of the Management Information Base (MIB), the Mobile-IPv6 MIB, for use with network management protocols in the Internet community. In particular, the Mobile-IPv6 MIB will be used to monitor and control the mobile node, home agent, and correspondent node functions of a Mobile IPv6 (MIPv6) entity. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: G. Keeni, K. Koide, K. Nagami, S. Gundavelli |
| RFC4296 The Architecture of Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) on Internet Protocols This document defines an abstract architecture for Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) protocols to run on Internet Protocol-suite transports. This architecture does not necessarily reflect the proper way to implement such protocols, but is, rather, a descriptive tool for defining and understanding the protocols. DDP allows the efficient placement of data into buffers designated by Upper Layer Protocols (e.g., RDMA). RDMA provides the semantics to enable Remote Direct Memory Access between peers in a way consistent with application requirements. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: S. Bailey, T. Talpey |
| RFC4297 Remote Direct Memory Access (RDMA) over IP Problem Statement Overhead due to the movement of user data in the end-system network I/O processing path at high speeds is significant, and has limited the use of Internet protocols in interconnection networks, and the Internet itself -- especially where high bandwidth, low latency, and/or low overhead are required by the hosted application. | December 2005 Status: INFORMATIONAL Autor: A. Romanow, J. Mogul, T. Talpey, S. Bailey |
| RFC4298 RTP Payload Format for BroadVoice Speech Codecs This document describes the RTP payload format for the BroadVoice(R) narrowband and wideband speech codecs. The narrowband codec, called BroadVoice16, or BV16, has been selected by CableLabs as a mandatory codec in PacketCable 1.5 and has a CableLabs specification. The document also provides specifications for the use of BroadVoice with MIME and the Session Description Protocol (SDP). [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: J.-H. Chen, W. Lee, J. Thyssen |
| RFC4301 Security Architecture for the Internet Protocol This document describes an updated version of the "Security Architecture for IP", which is designed to provide security services for traffic at the IP layer. This document obsoletes RFC 2401 (November 1998). [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: S. Kent, K. Seo |
| RFC4302 IP Authentication Header This document describes an updated version of the IP Authentication Header (AH), which is designed to provide authentication services in IPv4 and IPv6. This document obsoletes RFC 2402 (November 1998). [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: S. Kent |
| RFC4303 IP Encapsulating Security Payload (ESP) This document describes an updated version of the Encapsulating Security Payload (ESP) protocol, which is designed to provide a mix of security services in IPv4 and IPv6. ESP is used to provide confidentiality, data origin authentication, connectionless integrity, an anti-replay service (a form of partial sequence integrity), and limited traffic flow confidentiality. This document obsoletes RFC 2406 (November 1998). [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: S. Kent |
| RFC4304 Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP) The IP Security Authentication Header (AH) and Encapsulating Security Payload (ESP) protocols use a sequence number to detect replay. This document describes extensions to the Internet IP Security Domain of Interpretation (DOI) for the Internet Security Association and Key Management Protocol (ISAKMP). These extensions support negotiation of the use of traditional 32-bit sequence numbers or extended (64-bit) sequence numbers (ESNs) for a particular AH or ESP security association. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: S. Kent |
| RFC4305 Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) The IPsec series of protocols makes use of various cryptographic algorithms in order to provide security services. The Encapsulating Security Payload (ESP) and the Authentication Header (AH) provide two mechanisms for protecting data being sent over an IPsec Security Association (SA). To ensure interoperability between disparate implementations, it is necessary to specify a set of mandatory-to-implement algorithms to ensure that there is at least one algorithm that all implementations will have available. This document defines the current set of mandatory-to-implement algorithms for ESP and AH as well as specifying algorithms that should be implemented because they may be promoted to mandatory at some future time. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC4306 Internet Key Exchange (IKEv2) Protocol This document describes version 2 of the Internet Key Exchange (IKE) protocol. IKE is a component of IPsec used for performing mutual authentication and establishing and maintaining security associations (SAs). | December 2005 Status: PROPOSED STANDARD Autor: C. Kaufman |
| RFC4307 Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2) The IPsec series of protocols makes use of various cryptographic algorithms in order to provide security services. The Internet Key Exchange (IKE (RFC 2409) and IKEv2) provide a mechanism to negotiate which algorithms should be used in any given association. However, to ensure interoperability between disparate implementations, it is necessary to specify a set of mandatory-to-implement algorithms to ensure that there is at least one algorithm that all implementations will have available. This document defines the current set of algorithms that are mandatory to implement as part of IKEv2, as well as algorithms that should be implemented because they may be promoted to mandatory at some future time. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: J. Schiller |
| RFC4308 Cryptographic Suites for IPsec The IPsec, Internet Key Exchange (IKE), and IKEv2 protocols rely on security algorithms to provide privacy and authentication between the initiator and responder. There are many such algorithms available, and two IPsec systems cannot interoperate unless they are using the same algorithms. This document specifies optional suites of algorithms and attributes that can be used to simplify the administration of IPsec when used in manual keying mode, with IKEv1 or with IKEv2. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC4309 Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP) This document describes the use of Advanced Encryption Standard (AES) in Counter with CBC-MAC (CCM) Mode, with an explicit initialization vector (IV), as an IPsec Encapsulating Security Payload (ESP) mechanism to provide confidentiality, data origin authentication, and connectionless integrity. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC4310 Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of Domain Name System security extensions (DNSSEC) for domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of DNS security extensions. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: S. Hollenbeck |
| RFC4311 IPv6 Host-to-Router Load Sharing The original IPv6 conceptual sending algorithm does not do load sharing among equivalent IPv6 routers, and suggests schemes that can be problematic in practice. This document updates the conceptual sending algorithm in RFC 2461 so that traffic to different destinations can be distributed among routers in an efficient fashion. [STANDARDS-TRACK] | November 2005 Status: PROPOSED STANDARD Autor: R. Hinden, D. Thaler |
| RFC4312 The Camellia Cipher Algorithm and Its Use With IPsec This document describes the use of the Camellia block cipher algorithm in Cipher Block Chaining Mode, with an explicit Initialization Vector, as a confidentiality mechanism within the context of the IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: A. Kato, S. Moriai, M. Kanda |
| RFC4313 Requirements for Distributed Control of Automatic Speech Recognition (ASR), Speaker Identification/Speaker Verification (SI/SV), and Text-to-Speech (TTS) Resources This document outlines the needs and requirements for a protocol to control distributed speech processing of audio streams. By speech processing, this document specifically means automatic speech recognition (ASR), speaker recognition -- which includes both speaker identification (SI) and speaker verification (SV) -- and text-to-speech (TTS). Other IETF protocols, such as SIP and Real Time Streaming Protocol (RTSP), address rendezvous and control for generalized media streams. However, speech processing presents additional requirements that none of the extant IETF protocols address. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: D. Oran |
| RFC4314 IMAP4 Access Control List (ACL) Extension The Access Control List (ACL) extension (RFC 2086) of the Internet Message Access Protocol (IMAP) permits mailbox access control lists to be retrieved and manipulated through the IMAP protocol. | December 2005 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC4315 Internet Message Access Protocol (IMAP) - UIDPLUS extension The UIDPLUS extension of the Internet Message Access Protocol (IMAP) provides a set of features intended to reduce the amount of time and resources used by some client operations. The features in UIDPLUS are primarily intended for disconnected-use clients. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: M. Crispin |
| RFC4316 Datatypes for Web Distributed Authoring and Versioning (WebDAV) Properties This specification extends the Web Distributed Authoring and Versioning Protocol (WebDAV) to support datatyping. Protocol elements are defined to let clients and servers specify the datatype, and to instruct the WebDAV method PROPFIND to return datatype information. This memo defines an Experimental Protocol for the Internet community. | December 2005 Status: EXPERIMENTAL Autor: J. Reschke |
| RFC4317 Session Description Protocol (SDP) Offer/Answer Examples This document gives examples of Session Description Protocol (SDP) offer/answer exchanges. Examples include codec negotiation and selection, hold and resume, and addition and deletion of media streams. The examples show multiple media types, bidirectional, unidirectional, inactive streams, and dynamic payload types. Common Third Party Call Control (3pcc) examples are also given. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: A. Johnston, R. Sparks |
| RFC4318 Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol This memo defines an SMIv2 MIB module for managing the Rapid Spanning Tree capability defined by the IEEE P802.1t and P802.1w amendments to IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) segments. The objects in this MIB are defined to apply both to transparent bridging and to bridges connected by subnetworks other than LAN segments. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: D. Levi, D. Harrington |
| RFC4319 Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) Lines 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 High Bit-Rate Digital Subscriber Line (DSL) - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) interfaces. This document introduces extensions to several objects and textual conventions defined in HDSL2-SHDSL-Line MIB (RFC 3276). This document obsoletes RFC 3276. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: C. Sikes, B. Ray, R. Abbi |
| RFC4320 Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction This document describes modifications to the Session Initiation Protocol (SIP) to address problems that have been identified with the SIP non-INVITE transaction. These modifications reduce the probability of messages losing the race condition inherent in the non-INVITE transaction and reduce useless network traffic. They also improve the robustness of SIP networks when elements stop responding. These changes update behavior defined in RFC 3261. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: R. Sparks |
| RFC4321 Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE Transaction This document describes several problems that have been identified with the Session Initiation Protocol's (SIP) non-INVITE transaction. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: R. Sparks |
| RFC4322 Opportunistic Encryption using the Internet Key Exchange (IKE) This document describes opportunistic encryption (OE) as designed and implemented by the Linux FreeS/WAN project. OE uses the Internet Key Exchange (IKE) and IPsec protocols. The objective is to allow encryption for secure communication without any pre-arrangement specific to the pair of systems involved. DNS is used to distribute the public keys of each system involved. This is resistant to passive attacks. The use of DNS Security (DNSSEC) secures this system against active attackers as well. | December 2005 Status: INFORMATIONAL Autor: M. Richardson, D.H. Redelmeier |
| RFC4323 Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB) This document defines a basic set of managed objects for SNMP-based management of extended QoS features of Cable Modems (CMs) and Cable Modem Termination Systems (CMTSs) conforming to the Data over Cable System (DOCSIS) specifications versions 1.1 and 2.0. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: M. Patrick, W. Murwin |
| RFC4324 Calendar Access Protocol (CAP) The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS). At the time of this writing, three vendors are implementing CAP, but it has already been determined that some changes are needed. In order to get implementation experience, the participants felt that a CAP specification is needed to preserve many years of work. Many properties in CAP which have had many years of debate, can be used by other iCalendar protocols. This memo defines an Experimental Protocol for the Internet community. | December 2005 Status: EXPERIMENTAL Autor: D. Royer, G. Babics, S. Mansour |
| RFC4325 Internet X.509 Public Key Infrastructure Authority Information Access Certificate Revocation List (CRL) Extension This document updates RFC 3280 by defining the Authority Information Access Certificate Revocation List (CRL) extension. RFC 3280 defines the Authority Information Access certificate extension using the same syntax. The CRL extension provides a means of discovering and retrieving CRL issuer certificates. [STANDARDS-TRACK] | December 2005 Status: PROPOSED STANDARD Autor: S. Santesson, R. Housley |
| RFC4326 Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS) The MPEG-2 Transport Stream (TS) has been widely accepted not only for providing digital TV services, but also as a subnetwork technology for building IP networks. | December 2005 Status: PROPOSED STANDARD Autor: G. Fairhurst, B. Collini-Nocker |
| RFC4327 Link Management Protocol (LMP) Management Information Base (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 modeling the Link Management Protocol (LMP). [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: M. Dubuc, T. Nadeau, J. Lang, E. McGinnis |
| RFC4328 Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control This document is a companion to the Generalized Multi-Protocol Label Switching (GMPLS) signaling documents. It describes the technology-specific information needed to extend GMPLS signaling to control Optical Transport Networks (OTN); it also includes the so-called pre-OTN developments. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: D. Papadimitriou |
| RFC4329 Scripting Media Types This document describes the registration of media types for the ECMAScript and JavaScript programming languages and conformance requirements for implementations of these types. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: B. Hoehrmann |
| RFC4330 Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI This memorandum describes the Simple Network Time Protocol Version 4 (SNTPv4), which is a subset of the Network Time Protocol (NTP) used to synchronize computer clocks in the Internet. SNTPv4 can be used when the ultimate performance of a full NTP implementation based on RFC 1305 is neither needed nor justified. When operating with current and previous NTP and SNTP versions, SNTPv4 requires no changes to the specifications or known implementations, but rather clarifies certain design features that allow operation in a simple, stateless remote-procedure call (RPC) mode with accuracy and reliability expectations similar to the UDP/TIME protocol described in RFC 868. | January 2006 Status: INFORMATIONAL Autor: D. Mills |
| RFC4331 Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections Web Distributed Authoring and Versioning (WebDAV) servers are frequently deployed with quota (size) limitations. This document discusses the properties and minor behaviors needed for clients to interoperate with quota (size) implementations on WebDAV repositories. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: B. Korver, L. Dusseault |
| RFC4332 Cisco's Mobile IPv4 Host Configuration Extensions An IP device requires basic host configuration to be able to communicate. For example, it will typically require an IP address and the address of a DNS server. This information is configured statically or obtained dynamically using Dynamic Host Configuration Protocol (DHCP) or Point-to-Point Protocol/IP Control Protocol (PPP/IPCP). However, both DHCP and PPP/IPCP provide host configuration based on the access network. In Mobile IPv4, the registration process boots up a Mobile Node at an access network, also known as a foreign network. The information to configure the host needs to be based on the home network. This document describes the Cisco vendor-specific extensions to Mobile IPv4 to provide the base host configuration in Registration Request and Reply messages. This memo provides information for the Internet community. | December 2005 Status: INFORMATIONAL Autor: K. Leung, A. Patel, G. Tsirtsis, E. Klovning |
| RFC4333 The IETF Administrative Oversight Committee (IAOC) Member Selection Guidelines and Process This memo outlines the guidelines for selection of members of the IETF Administrative Oversight Committee, and describes the selection process used by the IAB and the IESG. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | December 2005 Status: BEST CURRENT PRACTICE Autor: G. Huston, B. Wijnen |
| RFC4334 Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN) This document defines two Extensible Authentication Protocol (EAP) extended key usage values and a public key certificate extension to carry Wireless LAN (WLAN) System Service identifiers (SSIDs). This document obsoletes RFC 3770. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: R. Housley, T. Moore |
| RFC4335 The Secure Shell (SSH) Session Channel Break Extension The Session Channel Break Extension provides a means to send a BREAK signal over a Secure Shell (SSH) terminal session. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: J. Galbraith, P. Remaker |
| RFC4336 Problem Statement for the Datagram Congestion Control Protocol (DCCP) This document describes for the historical record the motivation behind the Datagram Congestion Control Protocol (DCCP), an unreliable transport protocol incorporating end-to-end congestion control. DCCP implements a congestion-controlled, unreliable flow of datagrams for use by applications such as streaming media or on-line games. This memo provides information for the Internet community. | March 2006 Status: INFORMATIONAL Autor: S. Floyd, M. Handley, E. Kohler |
| RFC4337 MIME Type Registration for MPEG-4 This document defines the standard MIME types associated with MP4 files. It also recommends use of registered MIME types according to the type of contents. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: Y Lim, D. Singer |
| RFC4338 Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel This document specifies the way of encapsulating IPv6, IPv4, and Address Resolution Protocol (ARP) packets over Fibre Channel. This document also specifies the method of forming IPv6 link-local addresses and statelessly autoconfigured IPv6 addresses on Fibre Channel networks, and a mechanism to perform IPv4 address resolution over Fibre Channel networks. | January 2006 Status: PROPOSED STANDARD Autor: C. DeSanti, C. Carlson, R. Nixon |
| RFC4339 IPv6 Host Configuration of DNS Server Information Approaches This document describes three approaches for IPv6 recursive DNS server address configuration. It details the operational attributes of three solutions: RA option, DHCPv6 option, and well-known anycast addresses for recursive DNS servers. Additionally, it suggests the deployment scenarios in four kinds of networks (ISP, enterprise, 3GPP, and unmanaged networks) considering multi-solution resolution. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: J. Jeong |
| RFC4340 Datagram Congestion Control Protocol (DCCP) The Datagram Congestion Control Protocol (DCCP) is a transport protocol that provides bidirectional unicast connections of congestion-controlled unreliable datagrams. DCCP is suitable for applications that transfer fairly large amounts of data and that can benefit from control over the tradeoff between timeliness and reliability. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: E. Kohler, M. Handley, S. Floyd |
| RFC4341 Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control This document contains the profile for Congestion Control Identifier 2 (CCID 2), TCP-like Congestion Control, in the Datagram Congestion Control Protocol (DCCP). CCID 2 should be used by senders who would like to take advantage of the available bandwidth in an environment with rapidly changing conditions, and who are able to adapt to the abrupt changes in the congestion window typical of TCP's Additive Increase Multiplicative Decrease (AIMD) congestion control. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: S. Floyd, E. Kohler |
| RFC4342 Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC) This document contains the profile for Congestion Control Identifier 3, TCP-Friendly Rate Control (TFRC), in the Datagram Congestion Control Protocol (DCCP). CCID 3 should be used by senders that want a TCP-friendly sending rate, possibly with Explicit Congestion Notification (ECN), while minimizing abrupt rate changes. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: S. Floyd, E. Kohler, J. Padhye |
| RFC4343 Domain Name System (DNS) Case Insensitivity Clarification Domain Name System (DNS) names are "case insensitive". This document explains exactly what that means and provides a clear specification of the rules. This clarification updates RFCs 1034, 1035, and 2181. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC4344 The Secure Shell (SSH) Transport Layer Encryption Modes Researchers have discovered that the authenticated encryption portion of the current SSH Transport Protocol is vulnerable to several attacks. | January 2006 Status: PROPOSED STANDARD Autor: M. Bellare, T. Kohno, C. Namprempre |
| RFC4345 Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol This document specifies methods of using the Arcfour cipher in the Secure Shell (SSH) protocol that mitigate the weakness of the cipher's key-scheduling algorithm. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: B. Harris |
| RFC4346 The Transport Layer Security (TLS) Protocol Version 1.1 This document specifies Version 1.1 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security 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] | April 2006 Status: PROPOSED STANDARD Autor: T. Dierks, E. Rescorla |
| RFC4347 Datagram Transport Layer Security This document specifies Version 1.0 of the Datagram Transport Layer Security (DTLS) protocol. The DTLS protocol provides communications privacy for datagram protocols. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the Transport Layer Security (TLS) protocol and provides equivalent security guarantees. Datagram semantics of the underlying transport are preserved by the DTLS protocol. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: E. Rescorla, N. Modadugu |
| RFC4348 Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec This document specifies a real-time transport protocol (RTP) payload format to be used for the Variable-Rate Multimode Wideband (VMR-WB) speech codec. The payload format is designed to be able to interoperate with existing VMR-WB transport formats on non-IP networks. A media type registration is included for VMR-WB RTP payload format. | January 2006 Status: PROPOSED STANDARD Autor: S. Ahmadi |
| RFC4349 High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3) The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a protocol for tunneling a variety of data link protocols over IP networks. This document describes the specifics of how to tunnel High-Level Data Link Control (HDLC) frames over L2TPv3. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: C. Pignataro, M. Townsley |
| RFC4350 A Uniform Resource Name (URN) Formal Namespace for the New Zealand Government This document describes a Uniform Resource Name (URN) Namespace Identification (NID)convention as prescribed by the World Wide Web Consortium (W3C) for identifying, naming, assigning, and managing persistent resources and XML artefacts for the New Zealand Government. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: F. Hendrikx, C. Wallis |
| RFC4351 Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream This memo describes how to carry real-time text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140. | January 2006 Status: HISTORIC Autor: G. Hellstrom, P. Jones |
| RFC4352 RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio Codec This document specifies a Real-time Transport Protocol (RTP) payload format for Extended Adaptive Multi-Rate Wideband (AMR-WB+) encoded audio signals. The AMR-WB+ codec is an audio extension of the AMR-WB speech codec. It encompasses the AMR-WB frame types and a number of new frame types designed to support high-quality music and speech. A media type registration for AMR-WB+ is included in this specification. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: J. Sjoberg, M. Westerlund, A. Lakaniemi, S. Wenger |
| RFC4353 A Framework for Conferencing with the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) supports the initiation, modification, and termination of media sessions between user agents. These sessions are managed by SIP dialogs, which represent a SIP relationship between a pair of user agents. Because dialogs are between pairs of user agents, SIP's usage for two-party communications (such as a phone call), is obvious. Communications sessions with multiple participants, generally known as conferencing, are more complicated. This document defines a framework for how such conferencing can occur. This framework describes the overall architecture, terminology, and protocol components needed for multi-party conferencing. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: J. Rosenberg |
| RFC4354 A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service The Open Mobile Alliance (OMA) is defining the Push-to-talk over Cellular (PoC) service where SIP is the protocol used to establish half-duplex media sessions across different participants, to send instant messages, etc. This document defines a SIP event package to support publication, subscription, and notification of additional capabilities required by the PoC service. This SIP event package is applicable to the PoC service and may not be applicable to the general Internet. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: M. Garcia-Martin |
| RFC4355 IANA Registration for Enumservices email, fax, mms, ems, and sms This document registers the Enumservices "email", "fax", "sms", "ems", and "mms" using the URI schemes 'tel:' and 'mailto:' as per the IANA registration process defined in the ENUM specification RFC 3761. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: R. Brandner, L. Conroy, R. Stastny |
| RFC4356 Mapping Between the Multimedia Messaging Service (MMS) and Internet Mail The cellular telephone industry has defined a service known as the Multimedia Messaging Service (MMS). This service uses formats and protocols that are similar to, but differ in key ways from, those used in Internet mail. | January 2006 Status: PROPOSED STANDARD Autor: R. Gellens |
| RFC4357 Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms This document describes the cryptographic algorithms and parameters supplementary to the original GOST specifications, GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94, for use in Internet applications. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: V. Popov, I. Kurepkin, S. Leontiev |
| RFC4358 A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA) This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the Open Mobile Alliance (OMA). OMA defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided by the Open Mobile Naming Authority (OMNA). This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: D. Smith |
| RFC4359 The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload (ESP) and Authentication Header (AH) This memo describes the use of the RSA digital signature algorithm as an authentication algorithm within the revised IP Encapsulating Security Payload (ESP) as described in RFC 4303 and the revised IP Authentication Header (AH) as described in RFC 4302. The use of a digital signature algorithm, such as RSA, provides data origin authentication in applications when a secret key method (e.g., HMAC) does not provide this property. One example is the use of ESP and AH to authenticate the sender of an IP multicast packet. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: B. Weis |
| RFC4360 BGP Extended Communities Attribute This document describes the "extended community" BGP-4 attribute. This attribute provides a mechanism for labeling information carried in BGP-4. These labels can be used to control the distribution of this information, or for other applications. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: S. Sangli, D. Tappan, Y. Rekhter |
| RFC4361 Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4) This document specifies the format that is to be used for encoding Dynamic Host Configuration Protocol Version Four (DHCPv4) client identifiers, so that those identifiers will be interchangeable with identifiers used in the DHCPv6 protocol. This document also addresses and corrects some problems in RFC 2131 and RFC 2132 with respect to the handling of DHCP client identifiers. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: T. Lemon, B. Sommerfeld |
| RFC4362 RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP 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 related to the usage of the header-free packet format. This document is a replacement for RFC 3242, which it obsoletes. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: L-E. Jonsson, G. Pelletier, K. Sandlund |
| RFC4363 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions 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 two MIB modules for managing the capabilities of MAC bridges defined by the IEEE 802.1D-1998 (TM) MAC Bridges and the IEEE 802.1Q-2003 (TM) Virtual LAN (VLAN) standards for bridging between Local Area Network (LAN) segments. One MIB module defines objects for managing the 'Traffic Classes' and 'Enhanced Multicast Filtering' components of IEEE 802.1D-1998 and P802.1t-2001 (TM). The other MIB module defines objects for managing VLANs, as specified in IEEE 802.1Q-2003, P802.1u (TM), and P802.1v (TM). | January 2006 Status: PROPOSED STANDARD Autor: D. Levi, D. Harrington |
| RFC4364 BGP/MPLS IP Virtual Private Networks (VPNs) This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: E. Rosen, Y. Rekhter |
| RFC4365 Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs) This document provides an Applicability Statement for the Virtual Private Network (VPN) solution described in RFC 4364 and other documents listed in the References section. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: E. Rosen |
| RFC4366 Transport Layer Security (TLS) Extensions 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. | April 2006 Status: PROPOSED STANDARD Autor: S. Blake-Wilson, M. Nystrom, D. Hopwood, J. Mikkelsen, T. Wright |
| RFC4367 What's in a Name: False Assumptions about DNS Names The Domain Name System (DNS) provides an essential service on the Internet, mapping structured names to a variety of data, usually IP addresses. These names appear in email addresses, Uniform Resource Identifiers (URIs), and other application-layer identifiers that are often rendered to human users. Because of this, there has been a strong demand to acquire names that have significance to people, through equivalence to registered trademarks, company names, types of services, and so on. There is a danger in this trend; the humans and automata that consume and use such names will associate specific semantics with some names and thereby make assumptions about the services that are, or should be, provided by the hosts associated with the names. Those assumptions can often be false, resulting in a variety of failure conditions. This document discusses this problem in more detail and makes recommendations on how it can be avoided. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: J. Rosenberg, IAB |
| RFC4368 Multiprotocol Label Switching (MPLS) Label-Controlled Asynchronous Transfer Mode (ATM) and Frame-Relay Management Interface Definition This memo defines two MIB modules and corresponding MIB Object Definitions that describe how label-switching-controlled Frame-Relay and Asynchronous Transfer Mode (ATM) interfaces can be managed given the interface stacking as defined in the MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: T. Nadeau, S. Hegde |
| RFC4369 Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP) The iFCP protocol (RFC 4172) provides Fibre Channel fabric functionality on an IP network in which TCP/IP switching and routing elements replace Fibre Channel components. The iFCP protocol is used between iFCP Gateways. This document provides a mechanism to monitor and control iFCP Gateway instances, and their associated sessions, using SNMP. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: K. Gibbons, C. Monia, J. Tseng, F. Travostino |
| RFC4370 Lightweight Directory Access Protocol (LDAP) Proxied Authorization Control This document defines the Lightweight Directory Access Protocol (LDAP) Proxy Authorization Control. The Proxy Authorization Control allows a client to request that an operation be processed under a provided authorization identity instead of under the current authorization identity associated with the connection. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: R. Weltman |
| RFC4371 BCP 101 Update for IPR Trust This document updates BCP 101 to take account of the new IETF Intellectual Property Trust. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | January 2006 Status: BEST CURRENT PRACTICE Autor: B. Carpenter, L. Lynch |
| RFC4372 Chargeable User Identity This document describes a new Remote Authentication Dial-In User Service (RADIUS) attribute, Chargeable-User-Identity. This attribute can be used by a home network to identify a user for the purpose of roaming transactions that occur outside of the home network. [STANDARDS-TRACK] | January 2006 Status: PROPOSED STANDARD Autor: F. Adrangi, A. Lior, J. Korhonen, J. Loughney |
| RFC4373 Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP) The Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP) allows an LDAP client to perform a bulk update to an LDAP server. The protocol frames a sequenced set of update operations within a pair of LDAP extended operations to notify the server that the update operations in the framed set are related in such a way that the ordering of all operations can be preserved during processing even when they are sent asynchronously by the client. Update operations can be grouped within a single protocol message to maximize the efficiency of client-server communication. | January 2006 Status: INFORMATIONAL Autor: R. Harrison, J. Sermersheim, Y. Dong |
| RFC4374 The application/xv+xml Media Type This document describes the registration of the MIME sub-type application/xv+xml. This sub-type is intended for use as a media descriptor for XHTML+Voice multimodal language documents. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: G. McCobb |
| RFC4375 Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain This document presents a list of requirements in support of Emergency Telecommunications Service (ETS) within a single administrative domain. This document focuses on a specific set of administrative constraints and scope. Solutions to these requirements are not presented in this document. This memo provides information for the Internet community. | January 2006 Status: INFORMATIONAL Autor: K. Carlberg |
| RFC4376 Requirements for Floor Control Protocols Floor control is a means to manage joint or exclusive access to shared resources in a (multiparty) conferencing environment. Thereby, floor control complements other functions -- such as conference and media session setup, conference policy manipulation, and media control -- that are realized by other protocols. This document defines the requirements for a floor control protocol for multiparty conferences in the context of an existing framework. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: P. Koskelainen, J. Ott, H. Schulzrinne, X. Wu |
| RFC4377 Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks This document specifies Operations and Management (OAM) requirements for Multi-Protocol Label Switching (MPLS), as well as for applications of MPLS, such as pseudo-wire voice and virtual private network services. These requirements have been gathered from network operators who have extensive experience deploying MPLS networks. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: T. Nadeau, M. Morrow, G. Swallow, D. Allan, S. Matsushima |
| RFC4378 A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM) This document is a framework for how data plane protocols can be applied to operations and maintenance procedures for Multi-Protocol Label Switching (MPLS). The document is structured to outline how Operations and Management (OAM) functionality can be used to assist in fault, configuration, accounting, performance, and security management, commonly known by the acronym FCAPS. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: D. Allan, T. Nadeau |
| RFC4379 Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures This document describes a simple and efficient mechanism that can be used to detect data plane failures in Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). There are two parts to this document: information carried in an MPLS "echo request" and "echo reply" for the purposes of fault detection and isolation, and mechanisms for reliably sending the echo reply. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: K. Kompella, G. Swallow |
| RFC4380 Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs) We propose here a service that enables nodes located behind one or more IPv4 Network Address Translations (NATs) to obtain IPv6 connectivity by tunneling packets over UDP; we call this the Teredo service. Running the service requires the help of "Teredo servers" and "Teredo relays". The Teredo servers are stateless, and only have to manage a small fraction of the traffic between Teredo clients; the Teredo relays act as IPv6 routers between the Teredo service and the "native" IPv6 Internet. The relays can also provide interoperability with hosts using other transition mechanisms such as "6to4". [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: C. Huitema |
| RFC4381 Analysis of the Security of BGP/MPLS IP Virtual Private Networks (VPNs) This document analyses the security of the BGP/MPLS IP virtual private network (VPN) architecture that is described in RFC 4364, for the benefit of service providers and VPN users. | February 2006 Status: INFORMATIONAL Autor: M. Behringer |
| RFC4382 MPLS/BGP Layer 3 Virtual Private Network (VPN) 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 to configure and/or monitor Multiprotocol Label Switching Layer-3 Virtual Private Networks on a Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) supporting this feature. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: T. Nadeau, H. van der Linde |
| RFC4383 The Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Secure Real-time Transport Protocol (SRTP) This memo describes the use of the Timed Efficient Stream Loss-tolerant Authentication (RFC 4082) transform within the Secure Real-time Transport Protocol (SRTP), to provide data origin authentication for multicast and broadcast data streams. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: M. Baugher, E. Carrara |
| RFC4384 BGP Communities for Data Collection BGP communities (RFC 1997) are used by service providers for many purposes, including tagging of customer, peer, and geographically originated routes. Such tagging is typically used to control the scope of redistribution of routes within a provider's network and to its peers and customers. With the advent of large-scale BGP data collection (and associated research), it has become clear that the information carried in such communities is essential for a deeper understanding of the global routing system. This memo defines standard (outbound) communities and their encodings for export to BGP route collectors. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 2006 Status: BEST CURRENT PRACTICE Autor: D. Meyer |
| RFC4385 Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN This document describes the preferred design of a Pseudowire Emulation Edge-to-Edge (PWE3) Control Word to be used over an MPLS packet switched network, and the Pseudowire Associated Channel Header. The design of these fields is chosen so that an MPLS Label Switching Router performing MPLS payload inspection will not confuse a PWE3 payload with an IP payload. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: S. Bryant, G. Swallow, L. Martini, D. McPherson |
| RFC4386 Internet X.509 Public Key Infrastructure Repository Locator Service This document defines a Public Key Infrastructure (PKI) repository locator service. The service makes use of DNS SRV records defined in accordance with RFC 2782. The service enables certificate-using systems to locate PKI repositories.This memo defines an Experimental Protocol for the Internet community. | February 2006 Status: EXPERIMENTAL Autor: S. Boeyen, P. Hallam-Baker |
| RFC4387 Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTP 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 Hypertext Transfer Protocol (HTTP/HTTPS) as an interface mechanism to obtain certificates and certificate revocation lists (CRLs) from PKI repositories. Additional mechanisms addressing PKIX operational requirements are specified in separate documents. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: P. Gutmann |
| RFC4388 Dynamic Host Configuration Protocol (DHCP) Leasequery A Dynamic Host Configuration Protocol version 4 (DHCPv4) server is the authoritative source of IP addresses that it has provided to DHCPv4 clients. Other processes and devices that already make use of DHCPv4 may need to access this information. The leasequery protocol provides these processes and devices a lightweight way to access IP address information. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: R. Woundy, K. Kinnear |
| RFC4389 Neighbor Discovery Proxies (ND Proxy) Bridging multiple links into a single entity has several operational advantages. A single subnet prefix is sufficient to support multiple physical links. There is no need to allocate subnet numbers to the different networks, simplifying management. Bridging some types of media requires network-layer support, however. This document describes these cases and specifies the IP-layer support that enables bridging under these circumstances. This memo defines an Experimental Protocol for the Internet community. | April 2006 Status: EXPERIMENTAL Autor: D. Thaler, M. Talwar, C. Patel |
| RFC4390 Dynamic Host Configuration Protocol (DHCP) over InfiniBand IP over Infiniband (IPoIB) link-layer address is 20 octets long. This is larger than the 16 octets reserved for the hardware address in a Dynamic Host Configuration Protocol/Bootstrap Protocol (DHCP/BOOTP) message. The above inequality imposes restrictions on the use of the DHCP message fields when used over an IPoIB network. This document describes the use of DHCP message fields when implementing DHCP over IPoIB. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: V. Kashyap |
| RFC4391 Transmission of IP over InfiniBand (IPoIB) This document specifies a method for encapsulating and transmitting IPv4/IPv6 and Address Resolution Protocol (ARP) packets over InfiniBand (IB). It describes the link-layer address to be used when resolving the IP addresses in IP over InfiniBand (IPoIB) subnets. The document also describes the mapping from IP multicast addresses to InfiniBand multicast addresses. In addition, this document defines the setup and configuration of IPoIB links. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: J. Chu, V. Kashyap |
| RFC4392 IP over InfiniBand (IPoIB) Architecture InfiniBand is a high-speed, channel-based interconnect between systems and devices. | April 2006 Status: INFORMATIONAL Autor: V. Kashyap |
| RFC4393 MIME Type Registrations for 3GPP2 Multimedia Files This document serves to register and document the standard MIME types associated with the 3GPP2 multimedia file format, which is part of the family based on the ISO Media File Format. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: H. Garudadri |
| RFC4394 A Transport Network View of the Link Management Protocol (LMP) The Link Management Protocol (LMP) has been developed as part of the Generalized MPLS (GMPLS) protocol suite to manage Traffic Engineering (TE) resources and links. The GMPLS control plane (routing and signaling) uses TE links for establishing Label Switched Paths (LSPs). This memo describes the relationship of the LMP procedures to 'discovery' as defined in the International Telecommunication Union (ITU-T), and ongoing ITU-T work. This document provides an overview of LMP in the context of the ITU-T Automatically Switched Optical Networks (ASON) and transport network terminology and relates it to the ITU-T discovery work to promote a common understanding for progressing the work of IETF and ITU-T. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: D. Fedyk, O. Aboul-Magd, D. Brungard, J. Lang, D. Papadimitriou |
| RFC4395 Guidelines and Registration Procedures for New URI Schemes This document provides guidelines and recommendations for the definition of Uniform Resource Identifier (URI) schemes. It also updates the process and IANA registry for URI schemes. It obsoletes both RFC 2717 and RFC 2718. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 2006 Status: BEST CURRENT PRACTICE Autor: T. Hansen, T. Hardie, L. Masinter |
| RFC4396 RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text This document specifies an RTP payload format for the transmission of 3GPP (3rd Generation Partnership Project) timed text. 3GPP timed text is a time-lined, decorated text media format with defined storage in a 3GP file. Timed Text can be synchronized with audio/video contents and used in applications such as captioning, titling, and multimedia presentations. In the following sections, the problems of streaming timed text are addressed, and a payload format for streaming 3GPP timed text over RTP is specified. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: J. Rey, Y. Matsui |
| RFC4397 A Lexicography for the Interpretation of Generalized Multiprotocol Label Switching (GMPLS) Terminology within the Context of the ITU-T's Automatically Switched Optical Network (ASON) Architecture Generalized Multiprotocol Label Switching (GMPLS) has been developed by the IETF to facilitate the establishment of Label Switched Paths (LSPs) in a variety of data plane technologies and across several architectural models. The ITU-T has specified an architecture for the control of Automatically Switched Optical Networks (ASON). | February 2006 Status: INFORMATIONAL Autor: I. Bryskin, A. Farrel |
| RFC4398 Storing Certificates in the Domain Name System (DNS) Cryptographic public keys are frequently published, and their authenticity is 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] | March 2006 Status: PROPOSED STANDARD Autor: S. Josefsson |
| RFC4401 A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API) This document defines a Pseudo-Random Function (PRF) extension to the Generic Security Service Application Program Interface (GSS-API) for keying application protocols given an established GSS-API security context. The primary intended use of this function is to key secure session layers that do not or cannot use GSS-API per-message message integrity check (MIC) and wrap tokens for session protection. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC4402 A Pseudo-Random Function (PRF) for the Kerberos V Generic Security Service Application Program Interface (GSS-API) Mechanism This document defines the Pseudo-Random Function (PRF) for the Kerberos V mechanism for the Generic Security Service Application Program Interface (GSS-API), based on the PRF defined for the Kerberos V cryptographic framework, for keying application protocols given an established Kerberos V GSS-API security context. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC4403 Lightweight Directory Access Protocol (LDAP) Schema for Universal Description, Discovery, and Integration version 3 (UDDIv3) This document defines the Lightweight Directory Access Protocol (LDAPv3) schema for representing Universal Description, Discovery, and Integration (UDDI) data types in an LDAP directory. It defines the LDAP object class and attribute definitions and containment rules to model UDDI entities, defined in the UDDI version 3 information model, in an LDAPv3-compliant directory. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: B. Bergeson, K. Boogert, V. Nanjundaswamy |
| RFC4404 Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP) 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 Fibre Channel Over TCP/IP (FCIP) entities, which are used to interconnect Fibre Channel (FC) fabrics with IP networks. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: R. Natarajan, A. Rijhsinghani |
| RFC4405 SMTP Service Extension for Indicating the Responsible Submitter of an E-Mail Message This memo defines an extension to the Simple Mail Transfer Protocol (SMTP) service that allows an SMTP client to specify the responsible submitter of an e-mail message. The responsible submitter is the e-mail address of the entity most recently responsible for introducing a message into the transport stream. This extension helps receiving e-mail servers efficiently determine whether the SMTP client is authorized to transmit mail on behalf of the responsible submitter's domain. This memo defines an Experimental Protocol for the Internet community. | April 2006 Status: EXPERIMENTAL Autor: E. Allman, H. Katz |
| RFC4406 Sender ID: Authenticating E-Mail Internet mail suffers from the fact that much unwanted mail is sent using spoofed addresses -- "spoofed" in this case means that the address is used without the permission of the domain owner. This document describes a family of tests by which SMTP servers can determine whether an e-mail address in a received message was used with the permission of the owner of the domain contained in that e-mail address. This memo defines an Experimental Protocol for the Internet community. | April 2006 Status: EXPERIMENTAL Autor: J. Lyon, M. Wong |
| RFC4407 Purported Responsible Address in E-Mail Messages This document defines an algorithm by which, given an e-mail message, one can extract the identity of the party that appears to have most proximately caused that message to be delivered. This identity is called the Purported Responsible Address (PRA).This memo defines an Experimental Protocol for the Internet community. | April 2006 Status: EXPERIMENTAL Autor: J. Lyon |
| RFC4408 Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1 E-mail on the Internet can be forged in a number of ways. In particular, existing protocols place no restriction on what a sending host can use as the reverse-path of a message or the domain given on the SMTP HELO/EHLO commands. This document describes version 1 of the ender Policy Framework (SPF) protocol, whereby a domain may explicitly authorize the hosts that are allowed to use its domain name, and a receiving host may check such authorization. This memo defines an Experimental Protocol for the Internet community. | April 2006 Status: EXPERIMENTAL Autor: M. Wong, W. Schlitt |
| RFC4409 Message Submission for Mail This memo splits message submission from message relay, allowing each service to operate according to its own rules (for security, policy, etc.), and specifies what actions are to be taken by a submission server. | April 2006 Status: DRAFT STANDARD Autor: R. Gellens, J. Klensin |
| RFC4410 Selectively Reliable Multicast Protocol (SRMP) The Selectively Reliable Multicast Protocol (SRMP) is a transport protocol, intended to deliver a mix of reliable and best-effort messages in an any-to-any multicast environment, where the best-effort traffic occurs in significantly greater volume than the reliable traffic and therefore can carry sequence numbers of reliable messages for loss detection. SRMP is intended for use in a distributed simulation application environment, where only the latest value of reliable transmission for any particular data identifier requires delivery. SRMP has two sublayers: a bundling sublayer handling message aggregation and congestion control, and a Selectively Reliable Transport (SRT) sublayer. Selection between reliable and best-effort messages is performed by the application. This memo defines an Experimental Protocol for the Internet community. | February 2006 Status: EXPERIMENTAL Autor: M. Pullen, F. Zhao, D. Cohen |
| RFC4411 Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events This document proposes an IANA Registration extension to the Session Initiation Protocol (SIP) Reason Header to be included in a BYE Method Request as a result of a session preemption event, either at a user agent (UA), or somewhere in the network involving a reservation-based protocol such as the Resource ReSerVation Protocol (RSVP) or Next Steps in Signaling (NSIS). This document does not attempt to address routers failing in the packet path; instead, it addresses a deliberate tear down of a flow between UAs, and informs the terminated UA(s) with an indication of what occurred. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: J. Polk |
| RFC4412 Communications Resource Priority for the Session Initiation Protocol (SIP) This document defines two new Session Initiation Protocol (SIP) header fields for communicating resource priority, namely, "Resource-Priority" and "Accept-Resource-Priority". The "Resource-Priority" header field can influence the behavior of SIP user agents (such as telephone gateways and IP telephones) and SIP proxies. It does not directly influence the forwarding behavior of IP routers. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne, J. Polk |
| RFC4413 TCP/IP Field Behavior This memo describes TCP/IP field behavior in the context of header compression. Header compression is possible because most header fields do not vary randomly from packet to packet. Many of the fields exhibit static behavior or change in a more or less predictable way. When a header compression scheme is designed, it is of fundamental importance to understand the behavior of the fields in detail. An example of this analysis can be seen in RFC 3095. This memo performs a similar role for the compression of TCP/IP headers. This memo provides information for the Internet community. | March 2006 Status: INFORMATIONAL Autor: M. West, S. McCann |
| RFC4414 An ENUM Registry Type for the Internet Registry Information Service (IRIS) This document describes an Internet Registry Information Service (IRIS) registry schema for registered ENUM 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 ENUM registries. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: A. Newton |
| RFC4415 IANA Registration for Enumservice Voice This document registers the Enumservice "voice" (which has a defined subtype "tel"), as per the IANA registration process defined in the ENUM specification RFC 3761. This service indicates that the contact held in the generated Uniform Resource Identifier (URI) can be used to initiate an interactive voice (audio) call. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: R. Brandner, L. Conroy, R. Stastny |
| RFC4416 Goals for Internet Messaging to Support Diverse Service Environments This document is a history capturing the background, motivation and thinking during the LEMONADE definition and design process. | February 2006 Status: INFORMATIONAL Autor: J. Wong |
| RFC4417 Report of the 2004 IAB Messaging Workshop This document reports the outcome of a workshop held by the Internet Architecture Board (IAB) on the future of Internet messaging. The workshop was held on 6 and 7 October 2004 in Burlingame, CA, USA. The goal of the workshop was to examine the current state of different messaging technologies on the Internet (including, but not limited to, electronic mail, instant messaging, and voice messaging), to look at their commonalities and differences, and to find engineering, research, and architectural topics on which future work could be done. This report summarizes the discussions and conclusions of the workshop and of the IAB. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: P. Resnick, P. Saint-Andre |
| RFC4418 UMAC: Message Authentication Code using Universal Hashing This specification describes how to generate an authentication tag using the UMAC message authentication algorithm. UMAC is designed to be very fast to compute in software on contemporary uniprocessors. Measured speeds are as low as one cycle per byte. UMAC relies on addition of 32-bit and 64-bit numbers and multiplication of 32-bit numbers, operations well-supported by contemporary machines. | March 2006 Status: INFORMATIONAL Autor: T. Krovetz |
| RFC4419 Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol This memo describes a new key exchange method for the Secure Shell (SSH) protocol. It allows the SSH server to propose new groups on which to perform the Diffie-Hellman key exchange to the client. The proposed groups need not be fixed and can change with time. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: M. Friedl, N. Provos, W. Simpson |
| RFC4420 Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may be established using the Resource Reservation Protocol Traffic Engineering (RSVP-TE) extensions. This protocol includes an object (the SESSION_ATTRIBUTE object) that carries a Flags field used to indicate options and attributes of the LSP. That Flags field has eight bits allowing for eight options to be set. Recent proposals in many documents that extend RSVP-TE have suggested uses for each of the previously unused bits. | February 2006 Status: PROPOSED STANDARD Autor: A. Farrel, D. Papadimitriou, J.-P. Vasseur, A. Ayyangar |
| RFC4421 RTP Payload Format for Uncompressed Video: Additional Colour Sampling Modes The RFC Payload Format for Uncompressed Video, RFC 4175, defines a scheme to packetise uncompressed, studio-quality, video streams for transport using RTP. This memo extends the format to support additional colour sampling modes. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC4422 Simple Authentication and Security Layer (SASL) The Simple Authentication and Security Layer (SASL) is a framework for providing authentication and data security services in connection-oriented protocols via replaceable mechanisms. It provides a structured interface between protocols and mechanisms. The resulting framework allows new protocols to reuse existing mechanisms and allows old protocols to make use of new mechanisms. The framework also provides a protocol for securing subsequent protocol exchanges within a data security layer. | June 2006 Status: PROPOSED STANDARD Autor: A. Melnikov, K. Zeilenga |
| RFC4423 Host Identity Protocol (HIP) Architecture This memo describes a snapshot of the reasoning behind a proposed new namespace, the Host Identity namespace, and a new protocol layer, the Host Identity Protocol (HIP), between the internetworking and transport layers. Herein are presented the basics of the current namespaces, their strengths and weaknesses, and how a new namespace will add completeness to them. The roles of this new namespace in the protocols are defined. The memo describes the thinking of the authors as of Fall 2003. The architecture may have evolved since. This document represents one stable point in that evolution of understanding. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: R. Moskowitz, P. Nikander |
| RFC4424 Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Extension Audio Codec This document is an addendum to RFC 4348, which specifies the RTP payload format for the Variable-Rate Multimode Wideband (VMR-WB) speech codec. This document specifies some updates in RFC 4348 to enable support for the new operating mode of VMR-WB standard (i.e., VMR-WB mode 4). These updates do not affect the existing modes of VMR-WB already specified in RFC 4348. | February 2006 Status: PROPOSED STANDARD Autor: S. Ahmadi |
| RFC4425 RTP Payload Format for Video Codec 1 (VC-1) This memo specifies an RTP payload format for encapsulating Video Codec 1 (VC-1) compressed bit streams, as defined by the Society of Motion Picture and Television Engineers (SMPTE) standard, SMPTE 421M. SMPTE is the main standardizing body in the motion imaging industry, and the SMPTE 421M standard defines a compressed video bit stream format and decoding process for television. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: A. Klemets |
| RFC4426 Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional Specification This document presents a functional description of the protocol extensions needed to support Generalized Multi-Protocol Label Switching (GMPLS)-based recovery (i.e., protection and restoration). Protocol specific formats and mechanisms will be described in companion documents. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: J. Lang, B. Rajagopalan, D. Papadimitriou |
| RFC4427 Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS) This document defines a common terminology for Generalized Multi-Protocol Label Switching (GMPLS)-based recovery mechanisms (i.e., protection and restoration). The terminology is independent of the underlying transport technologies covered by GMPLS. This memo provides information for the Internet community. | March 2006 Status: INFORMATIONAL Autor: E. Mannie, D. Papadimitriou |
| RFC4428 Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based Recovery Mechanisms (including Protection and Restoration) This document provides an analysis grid to evaluate, compare, and contrast the Generalized Multi-Protocol Label Switching (GMPLS) protocol suite capabilities with the recovery mechanisms currently proposed at the IETF CCAMP Working Group. A detailed analysis of each of the recovery phases is provided using the terminology defined in RFC 4427. This document focuses on transport plane survivability and recovery issues and not on control plane resilience and related aspects. This memo provides information for the Internet community. | March 2006 Status: INFORMATIONAL Autor: D. Papadimitriou, E. Mannie |
| RFC4429 Optimistic Duplicate Address Detection (DAD) for IPv6 Optimistic Duplicate Address Detection is an interoperable modification of the existing IPv6 Neighbor Discovery (RFC 2461) and Stateless Address Autoconfiguration (RFC 2462) processes. The intention is to minimize address configuration delays in the successful case, to reduce disruption as far as possible in the failure case, and to remain interoperable with unmodified hosts and routers. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: N. Moore |
| RFC4430 Kerberized Internet Negotiation of Keys (KINK) This document describes the Kerberized Internet Negotiation of Keys (KINK) protocol. KINK defines a low-latency, computationally inexpensive, easily managed, and cryptographically sound protocol to establish and maintain security associations using the Kerberos authentication system. KINK reuses the Quick Mode payloads of the Internet Key Exchange (IKE), which should lead to substantial reuse of existing IKE implementations. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: S. Sakane, K. Kamada, M. Thomas, J. Vilhuber |
| RFC4431 The DNSSEC Lookaside Validation (DLV) DNS Resource Record This document defines a new DNS resource record, called the DNSSEC Lookaside Validation (DLV) RR, for publishing DNSSEC trust anchors outside of the DNS delegation chain. This memo provides information for the Internet community. | February 2006 Status: INFORMATIONAL Autor: M. Andrews, S. Weiler |
| RFC4432 RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol This memo describes a key-exchange method for the Secure Shell (SSH) protocol based on Rivest-Shamir-Adleman (RSA) public-key encryption. It uses much less client CPU time than the Diffie-Hellman algorithm specified as part of the core protocol, and hence is particularly suitable for slow client systems. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: B. Harris |
| RFC4433 Mobile IPv4 Dynamic Home Agent (HA) Assignment Mobile IPv4 (RFC 3344) uses the home agent (HA) to anchor sessions of a roaming mobile node (MN). This document proposes a messaging mechanism for dynamic home agent assignment and HA redirection. The goal is to provide a mechanism to assign an optimal HA for a Mobile IP session while allowing any suitable method for HA selection. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: M. Kulkarni, A. Patel, K. Leung |
| RFC4434 The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE) 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. [STANDARDS-TRACK] | February 2006 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC4435 A Framework for the Usage of Internet Media Guides (IMGs) This document defines a framework for the delivery of Internet Media Guides (IMGs). An IMG is a structured collection of multimedia session descriptions expressed using the Session Description Protocol (SDP), SDPng, or some similar session description format. This document describes a generalized model for IMG delivery mechanisms, the use of existing protocols, and the need for additional work to create an IMG delivery infrastructure. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: Y. Nomura, R. Walsh, J-P. Luoma, H. Asaeda, H. Schulzrinne |
| RFC4436 Detecting Network Attachment in IPv4 (DNAv4) The time required to detect movement between networks and to obtain (or to continue to use) an IPv4 configuration may be significant as a fraction of the total handover latency in moving between points of attachment. This document synthesizes, from experience in the deployment of hosts supporting ARP, DHCP, and IPv4 Link-Local addresses, a set of steps known as Detecting Network Attachment for IPv4 (DNAv4), in order to decrease the handover latency in moving between points of attachment. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: B. Aboba, J. Carlson, S. Cheshire |
| RFC4437 Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) to allow clients to author HTTP redirect reference resources whose default response is an HTTP/1.1 3xx (Redirection) status code. A redirect reference makes it possible to access the target resourced indirectly through any URI mapped to the redirect reference resource. This specification does not address remapping of trees of resources or regular expression based redirections. There are no integrity guarantees associated with redirect reference resources. Other mechanisms can also be used to achieve the same functionality as this specification. This specification allows operators to experiment with this mechanism and develop experience on what is the best approach to the problem. This memo defines an Experimental Protocol for the Internet community. | March 2006 Status: EXPERIMENTAL Autor: J. Whitehead, G. Clemm, J. Reschke |
| RFC4438 Fibre-Channel Name Server 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 Name Server function of a Fibre Channel network. The Fibre Channel Name Server provides a means for Fibre Channel ports to register and discover Fibre Channel names and attributes. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: C. DeSanti, V. Gaonkar, H.K. Vivek, K. McCloghrie, S. Gai |
| RFC4439 Fibre Channel Fabric Address Manager 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 a Fibre Channel network's Fabric Address Manager. [STANDARDS-TRACK] | March 2006 Status: PROPOSED STANDARD Autor: C. DeSanti, V. Gaonkar, K. McCloghrie, S. Gai |
| RFC4440 IAB Thoughts on the Role of the Internet Research Task Force (IRTF) This document is an Internet Architecture Board (IAB) report on the role of the Internet Research Task Force (IRTF), both on its own and in relationship to the IETF. This document evolved from a discussion within the IAB as part of a process of appointing a new chair of the IRTF. This memo provides information for the Internet community. | March 2006 Status: INFORMATIONAL Autor: S. Floyd, V. Paxson, A. Falk, IAB |
| RFC4441 The IEEE 802/IETF Relationship Since the late 1980s, IEEE 802 and IETF have cooperated in the development of Simple Network Management Protocol (SNMP) MIBs and Authentication, Authorization, and Accounting (AAA) applications. This document describes the policies and procedures that have developed in order to coordinate between the two organizations, as well as some of the relationship history. This memo provides information for the Internet community. | March 2006 Status: INFORMATIONAL Autor: B. Aboba |
| RFC4442 Bootstrapping Timed Efficient Stream Loss-Tolerant Authentication (TESLA) TESLA, the Timed Efficient Stream Loss-tolerant Authentication protocol, provides source authentication in multicast scenarios. TESLA is an efficient protocol with low communication and computation overhead that scales to large numbers of receivers and also tolerates packet loss. TESLA is based on loose time synchronization between the sender and the receivers. Source authentication is realized in TESLA by using Message Authentication Code (MAC) chaining. The use of TESLA within the Secure Real-time Transport Protocol (SRTP) has been published, targeting multicast authentication in scenarios where SRTP is applied to protect the multimedia data. This solution assumes that TESLA parameters are made available by out-of-band mechanisms. | March 2006 Status: PROPOSED STANDARD Autor: S. Fries, H. Tschofenig |
| RFC4443 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification This document describes the format of a set of control messages used in ICMPv6 (Internet Control Message Protocol). ICMPv6 is the Internet Control Message Protocol for Internet Protocol version 6 (IPv6). [STANDARDS-TRACK] | March 2006 Status: DRAFT STANDARD Autor: A. Conta, S. Deering, M. Gupta |
| RFC4444 Management Information Base for Intermediate System to Intermediate System (IS-IS) This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this document describes a MIB for the Intermediate System to Intermediate System (IS-IS) Routing protocol when it is used to construct routing tables for IP networks. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: J. Parker |
| RFC4445 A Proposed Media Delivery Index (MDI) This memo defines a Media Delivery Index (MDI) measurement that can be used as a diagnostic tool or a quality indicator for monitoring a network intended to deliver applications such as streaming media, MPEG video, Voice over IP, or other information sensitive to arrival time and packet loss. It provides an indication of traffic jitter, a measure of deviation from nominal flow rates, and a data loss at-a-glance measure for a particular flow. For instance, the MDI may be used as a reference in characterizing and comparing networks carrying UDP streaming media. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: J. Welch, J. Clark |
| RFC4446 IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3) This document allocates the fixed pseudowire identifier and other fixed protocol values for protocols that have been defined in the Pseudo Wire Edge to Edge (PWE3) working group. Detailed IANA allocation instructions are also included in this document. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | April 2006 Status: BEST CURRENT PRACTICE Autor: L. Martini |
| RFC4447 Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP) Layer 2 services (such as Frame Relay, Asynchronous Transfer Mode, and Ethernet) can be "emulated" over an MPLS backbone by encapsulating the Layer 2 Protocol Data Units (PDU) and transmitting them over "pseudowires". It is also possible to use pseudowires to provide low-rate Time Division Multiplexed and a Synchronous Optical NETworking circuit emulation over an MPLS-enabled network. This document specifies a protocol for establishing and maintaining the pseudowires, using extensions to Label Distribution Protocol (LDP). Procedures for encapsulating Layer 2 PDUs are specified in a set of companion documents. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: L. Martini, E. Rosen, N. El-Aawar, T. Smith, G. Heron |
| RFC4448 Encapsulation Methods for Transport of Ethernet over MPLS Networks An Ethernet pseudowire (PW) is used to carry Ethernet/802.3 Protocol Data Units (PDUs) over an MPLS network. This enables service providers to offer "emulated" Ethernet services over existing MPLS networks. This document specifies the encapsulation of Ethernet/802.3 PDUs within a pseudowire. It also specifies the procedures for using a PW to provide a "point-to-point Ethernet" service. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: L. Martini, E. Rosen, N. El-Aawar, G. Heron |
| RFC4449 Securing Mobile IPv6 Route Optimization Using a Static Shared Key A mobile node and a correspondent node may preconfigure data useful for precomputing a Binding Management Key that can subsequently be used for authorizing Binding Updates. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC4450 Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents This memo documents an experiment to review and classify Proposed Standards as not reflecting documented practice within the world today. The results identify a set of documents that were marked as Proposed Standards that are now reclassified as Historic. This memo provides information for the Internet community. | March 2006 Status: INFORMATIONAL Autor: E. Lear, H. Alvestrand |
| RFC4451 BGP MULTI_EXIT_DISC (MED) Considerations The BGP MULTI_EXIT_DISC (MED) attribute provides a mechanism for BGP speakers to convey to an adjacent AS the optimal entry point into the local AS. While BGP MEDs function correctly in many scenarios, a number of issues may arise when utilizing MEDs in dynamic or complex topologies. | March 2006 Status: INFORMATIONAL Autor: D. McPherson, V. Gill |
| RFC4452 The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces This document defines the "info" Uniform Resource Identifier (URI) scheme for information assets with identifiers in public namespaces. Namespaces participating in the "info" URI scheme are regulated by an "info" Registry mechanism. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: H. Van de Sompel, T. Hammond, E. Neylon, S. Weibel |
| RFC4453 Requirements for Consent-Based Communications in the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) supports communications across many media types, including real-time audio, video, text, instant messaging, and presence. In its current form, it allows session invitations, instant messages, and other requests to be delivered from one party to another without requiring explicit consent of the recipient. Without such consent, it is possible for SIP to be used for malicious purposes, including spam and denial-of-service attacks. This document identifies a set of requirements for extensions to SIP that add consent-based communications. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: J. Rosenberg, G. Camarillo, D. Willis |
| RFC4454 Asynchronous Transfer Mode (ATM) over Layer 2 Tunneling Protocol Version 3 (L2TPv3) The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines an extensible tunneling protocol to transport layer 2 services over IP networks. This document describes the specifics of how to use the L2TP control plane for Asynchronous Transfer Mode (ATM) Pseudowires and provides guidelines for transporting various ATM services over an IP network. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: S. Singh, M. Townsley, C. Pignataro |
| RFC4455 Definition of Managed Objects for Small Computer System Interface (SCSI) Entities 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 Small Computer System Interface (SCSI) entities, independently of the interconnect subsystem layer. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: M. Hallak-Stamler, M. Bakke, Y. Lederman, M. Krueger, K. McCloghrie |
| RFC4456 BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for TCP/IP internets. Typically, all BGP speakers within a single AS must be fully meshed so that any external routing information must be re-distributed to all other routers within that Autonomous System (AS). This represents a serious scaling problem that has been well documented with several alternatives proposed. | April 2006 Status: DRAFT STANDARD Autor: T. Bates, E. Chen, R. Chandra |
| RFC4457 The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header) This document specifies the Session Initiation Protocol (SIP) P-User-Database Private-Header (P-header). This header field is used in the 3rd-Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) to provide SIP registrars and SIP proxy servers with the address of the database that contains the user profile of the user that generated a particular request. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: G. Camarillo, G. Blanco |
| RFC4458 Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR) The Session Initiation Protocol (SIP) is often used to initiate connections to applications such as voicemail or interactive voice recognition systems. This specification describes a convention for forming SIP service URIs that request particular services based on redirecting targets from such applications. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: C. Jennings, F. Audet, J. Elwell |
| RFC4459 MTU and Fragmentation Issues with In-the-Network Tunneling Tunneling techniques such as IP-in-IP when deployed in the middle of the network, typically between routers, have certain issues regarding how large packets can be handled: whether such packets would be fragmented and reassembled (and how), whether Path MTU Discovery would be used, or how this scenario could be operationally avoided. This memo justifies why this is a common, non-trivial problem, and goes on to describe the different solutions and their characteristics at some length. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: P. Savola |
| RFC4460 Stream Control Transmission Protocol (SCTP) Specification Errata and Issues This document is a compilation of issues found during six interoperability events and 5 years of experience with implementing, testing, and using SCTP along with the suggested fixes. This document provides deltas to RFC 2960 and is organized in a time-based way. The issues are listed in the order they were brought up. Because some text is changed several times, the last delta in the text is the one that should be applied. In addition to the delta, a description of the problem and the details of the solution are also provided. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: R. Stewart, I. Arias-Rodriguez, K. Poon, A. Caro, M. Tuexen |
| RFC4461 Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs) This document presents a set of requirements for the establishment and maintenance of Point-to-Multipoint (P2MP) Traffic-Engineered (TE) Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs). | April 2006 Status: INFORMATIONAL Autor: S. Yasukawa |
| RFC4462 Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol The Secure Shell protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. | May 2006 Status: PROPOSED STANDARD Autor: J. Hutzelman, J. Salowey, J. Galbraith, V. Welch |
| RFC4463 A Media Resource Control Protocol (MRCP) Developed by Cisco, Nuance, and Speechworks This document describes a Media Resource Control Protocol (MRCP) that was developed jointly by Cisco Systems, Inc., Nuance Communications, and Speechworks, Inc. It is published as an RFC as input for further IETF development in this area. | April 2006 Status: INFORMATIONAL Autor: S. Shanmugham, P. Monaco, B. Eberman |
| RFC4464 Signaling Compression (SigComp) Users' Guide This document provides an informational guide for users of the Signaling Compression (SigComp) protocol. The aim of the document is to assist users when making SigComp implementation decisions, for example, the choice of compression algorithm and the level of robustness against lost or misordered packets. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: A. Surtees, M. West |
| RFC4465 Signaling Compression (SigComp) Torture Tests This document provides a set of "torture tests" for implementers of the Signaling Compression (SigComp) protocol. The torture tests check each of the SigComp Universal Decompressor Virtual Machine instructions in turn, focusing in particular on the boundary and error cases that are not generally encountered when running well-behaved compression algorithms. Tests are also provided for other SigComp entities such as the dispatcher and the state handler. This memo provides information for the Internet community. | June 2006 Status: INFORMATIONAL Autor: A. Surtees, M. West |
| RFC4466 Collected Extensions to IMAP4 ABNF Over the years, many documents from IMAPEXT and LEMONADE working groups, as well as many individual documents, have added syntactic extensions to many base IMAP commands described in RFC 3501. For ease of reference, this document collects most of such ABNF changes in one place. | April 2006 Status: PROPOSED STANDARD Autor: A. Melnikov, C. Daboo |
| RFC4467 Internet Message Access Protocol (IMAP) - URLAUTH Extension This document describes the URLAUTH extension to the Internet Message Access Protocol (IMAP) (RFC 3501) and the IMAP URL Scheme (IMAPURL) (RFC 2192). This extension provides a means by which an IMAP client can use URLs carrying authorization to access limited message data on the IMAP server. | May 2006 Status: PROPOSED STANDARD Autor: M. Crispin |
| RFC4468 Message Submission BURL Extension The submission profile of Simple Mail Transfer Protocol (SMTP) provides a standard way for an email client to submit a complete message for delivery. This specification extends the submission profile by adding a new BURL command that can be used to fetch submission data from an Internet Message Access Protocol (IMAP) server. This permits a mail client to inject content from an IMAP server into the SMTP infrastructure without downloading it to the client and uploading it back to the server. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: C. Newman |
| RFC4469 Internet Message Access Protocol (IMAP) CATENATE Extension The CATENATE extension to the Internet Message Access Protocol (IMAP) extends the APPEND command to allow clients to create messages on the IMAP server that may contain a combination of new data along with parts of (or entire) messages already on the server. Using this extension, the client can catenate parts of an already existing message onto a new message without having to first download the data and then upload it back to the server. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: P. Resnick |
| RFC4470 Minimally Covering NSEC Records and DNSSEC On-line Signing This document describes how to construct DNSSEC NSEC resource records that cover a smaller range of names than called for by RFC 4034. By generating and signing these records on demand, authoritative name servers can effectively stop the disclosure of zone contents otherwise made possible by walking the chain of NSEC records in a signed zone. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: S. Weiler, J. Ihren |
| RFC4471 Derivation of DNS Name Predecessor and Successor This document describes two methods for deriving the canonically-ordered predecessor and successor of a DNS name. These methods may be used for dynamic NSEC resource record synthesis, enabling security-aware name servers to provide authenticated denial of existence without disclosing other owner names in a DNSSEC secured zone. This memo defines an Experimental Protocol for the Internet community. | September 2006 Status: EXPERIMENTAL Autor: G. Sisson, B. Laurie |
| RFC4472 Operational Considerations and Issues with IPv6 DNS This memo presents operational considerations and issues with IPv6 Domain Name System (DNS), including a summary of special IPv6 addresses, documentation of known DNS implementation misbehavior, recommendations and considerations on how to perform DNS naming for service provisioning and for DNS resolver IPv6 support, considerations for DNS updates for both the forward and reverse trees, and miscellaneous issues. This memo is aimed to include a summary of information about IPv6 DNS considerations for those who have experience with IPv4 DNS. This memo provides information for the Internet community. | April 2006 Status: INFORMATIONAL Autor: A. Durand, J. Ihren, P. Savola |
| RFC4473 Requirements for Internet Media Guides (IMGs) This memo specifies requirements for a framework and protocols for accessing and updating Internet Media Guide (IMG) information for media-on-demand and multicast applications. These requirements are designed to guide choice and development of IMG protocols for efficient and scalable delivery. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: Y. Nomura, R. Walsh, J-P. Luoma, J. Ott, H. Schulzrinne |
| RFC4474 Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP) The existing security mechanisms in the Session Initiation Protocol (SIP) are inadequate for cryptographically assuring the identity of the end users that originate SIP requests, especially in an interdomain context. This document defines a mechanism for securely identifying originators of SIP messages. It does so by defining two new SIP header fields, Identity, for conveying a signature used for validating the identity, and Identity-Info, for conveying a reference to the certificate of the signer. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: J. Peterson, C. Jennings |
| RFC4475 Session Initiation Protocol (SIP) Torture Test Messages This informational document gives examples of Session Initiation Protocol (SIP) test messages designed to exercise and "torture" a SIP implementation. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: R. Sparks, A. Hawrylyshen, A. Johnston, J. Rosenberg, H. Schulzrinne |
| RFC4476 Attribute Certificate (AC) Policies Extension This document describes one certificate extension that explicitly states the Attribute Certificate Policies (ACPs) that apply to a given Attribute Certificate (AC). The goal of this document is to allow relying parties to perform an additional test when validating an AC, i.e., to assess whether a given AC carrying some attributes can be accepted on the basis of references to one or more specific ACPs. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: C. Francis, D. Pinkas |
| RFC4477 Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack Issues A node may have support for communications using IPv4 and/or IPv6 protocols. Such a node may wish to obtain IPv4 and/or IPv6 configuration settings via the Dynamic Host Configuration Protocol (DHCP). The original version of DHCP (RFC 2131) designed for IPv4 has now been complemented by a new DHCPv6 (RFC 3315) for IPv6. This document describes issues identified with dual IP version DHCP interactions, the most important aspect of which is how to handle potential problems in clients processing configuration information received from both DHCPv4 and DHCPv6 servers. The document makes a recommendation on the general strategy on how best to handle such issues and identifies future work to be undertaken. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: T. Chown, S. Venaas, C. Strauf |
| RFC4478 Repeated Authentication in Internet Key Exchange (IKEv2) Protocol This document extends the Internet Key Exchange (IKEv2) Protocol document [IKEv2]. With some IPsec peers, particularly in the remote access scenario, it is desirable to repeat the mutual authentication periodically. The purpose of this is to limit the time that security associations (SAs) can be used by a third party who has gained control of the IPsec peer. This document describes a mechanism to perform this function. This memo defines an Experimental Protocol for the Internet community. | April 2006 Status: EXPERIMENTAL Autor: Y. Nir |
| RFC4479 A Data Model for Presence This document defines the underlying presence data model used by Session Initiation Protocol (SIP) for Instant Messaging and Presence Leveraging Extensions (SIMPLE) presence agents. The data model provides guidance on how to map various communications systems into presence documents in a consistent fashion. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC4480 RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF) The Presence Information Data Format (PIDF) defines a basic format for representing presence information for a presentity. This format defines a textual note, an indication of availability (open or closed) and a Uniform Resource Identifier (URI) for communication. The Rich Presence Information Data format (RPID) described here is an extension that adds optional elements to the Presence Information Data Format (PIDF). These extensions provide additional information about the presentity and its contacts. The information is designed so that much of it can be derived automatically, e.g., from calendar files or user activity. | July 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne, V. Gurbani, P. Kyzivat, J. Rosenberg |
| RFC4481 Timed Presence Extensions to the Presence Information Data Format (PIDF) to Indicate Status Information for Past and Future Time Intervals The Presence Information Data Format (PIDF) defines a basic XML format for presenting presence information for a presentity. This document extends PIDF, adding a timed status extension (<timed-status> element) that allows a presentity to declare its status for a time interval fully in the future or the past. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC4482 CIPID: Contact Information for the Presence Information Data Format The Presence Information Data Format (PIDF) defines a basic XML format for presenting presence information for a presentity. The Contact Information for the Presence Information Data format (CIPID) is an extension that adds elements to PIDF that provide additional contact information about a presentity and its contacts, including references to address book entries and icons. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC4483 A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages This document defines an extension to the URL MIME External-Body Access-Type to satisfy the content indirection requirements for the Session Initiation Protocol (SIP). These extensions are aimed at allowing any MIME part in a SIP message to be referred to indirectly via a URI. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: E. Burger |
| RFC4484 Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP) This document lays out a set of requirements related to trait-based authorization for the Session Initiation Protocol (SIP). While some authentication mechanisms are described in the base SIP specification, trait-based authorization provides information used to make policy decisions based on the attributes of a participant in a session. This approach provides a richer framework for authorization, as well as allows greater privacy for users of an identity system. This memo provides information for the Internet community. | August 2006 Status: INFORMATIONAL Autor: J. Peterson, J. Polk, D. Sicker, H. Tschofenig |
| RFC4485 Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) is a flexible yet simple tool for establishing interactive communications sessions across the Internet. Part of this flexibility is the ease with which it can be extended. In order to facilitate effective and interoperable extensions to SIP, some guidelines need to be followed when developing SIP extensions. This document outlines a set of such guidelines for authors of SIP extensions. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: J. Rosenberg, H. Schulzrinne |
| RFC4486 Subcodes for BGP Cease Notification Message This document defines several subcodes for the BGP Cease NOTIFICATION message that would provide more information to aid network operators in correlating network events and diagnosing BGP peering issues. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: E. Chen, V. Gillet |
| RFC4487 Mobile IPv6 and Firewalls: Problem Statement This document captures the issues that may arise in the deployment of IPv6 networks when they support Mobile IPv6 and firewalls. The issues are not only applicable to firewalls protecting enterprise networks, but are also applicable in 3G mobile networks such as General Packet Radio Service / Universal Mobile Telecommunications System (GPRS/UMTS) and CDMA2000 networks. | May 2006 Status: INFORMATIONAL Autor: F. Le, S. Faccin, B. Patil, H. Tschofenig |
| RFC4488 Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription The Session Initiation Protocol (SIP) REFER extension as defined in RFC 3515 automatically establishes a typically short-lived event subscription used to notify the party sending a REFER request about the receiver's status in executing the transaction requested by the REFER. These notifications are not needed in all cases. This specification provides a way to prevent the automatic establishment of an event subscription and subsequent notifications using a new SIP extension header field that may be included in a REFER request. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: O. Levin |
| RFC4489 A Method for Generating Link-Scoped IPv6 Multicast Addresses This document specifies an extension to the multicast addressing architecture of the IPv6 protocol. The extension allows the use of Interface Identifiers (IIDs) to allocate multicast addresses. When a link-local unicast address is configured at each interface of a node, an IID is uniquely determined. After that, each node can generate its unique multicast addresses automatically without conflicts. The alternative method for creating link-local multicast addresses proposed in this document is better than known methods like unicast-prefix-based IPv6 multicast addresses. This memo updates RFC 3306. [STANDARDS-TRACK] | April 2006 Status: PROPOSED STANDARD Autor: J-S. Park, M-K. Shin, H-J. Kim |
| RFC4490 Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS) This document describes the conventions for using the cryptographic algorithms GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 with the Cryptographic Message Syntax (CMS). The CMS is used for digital signature, digest, authentication, and encryption of arbitrary message contents. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: S. Leontiev, G. Chudov |
| RFC4491 Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL Profile This document supplements RFC 3279. It describes encoding formats, identifiers, and parameter formats for the algorithms GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 for use in Internet X.509 Public Key Infrastructure (PKI). [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: S. Leontiev, D. Shefanovski |
| RFC4492 Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS) This document describes new key exchange algorithms based on Elliptic Curve Cryptography (ECC) for the Transport Layer Security (TLS) protocol. In particular, it specifies the use of Elliptic Curve Diffie-Hellman (ECDH) key agreement in a TLS handshake and the use of Elliptic Curve Digital Signature Algorithm (ECDSA) as a new authentication mechanism. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: S. Blake-Wilson, N. Bolyard, V. Gupta, C. Hawk, B. Moeller |
| RFC4493 The AES-CMAC Algorithm The National Institute of Standards and Technology (NIST) has recently specified the Cipher-based Message Authentication Code (CMAC), which is equivalent to the One-Key CBC MAC1 (OMAC1) submitted by Iwata and Kurosawa. This memo specifies an authentication algorithm based on CMAC with the 128-bit Advanced Encryption Standard (AES). This new authentication algorithm is named AES-CMAC. The purpose of this document is to make the AES-CMAC algorithm conveniently available to the Internet Community. This memo provides information for the Internet community. | June 2006 Status: INFORMATIONAL Autor: JH. Song, R. Poovendran, J. Lee, T. Iwata |
| RFC4494 The AES-CMAC-96 Algorithm and Its Use with IPsec The National Institute of Standards and Technology (NIST) has recently specified the Cipher-based Message Authentication Code (CMAC), which is equivalent to the One-Key CBC-MAC1 (OMAC1) algorithm submitted by Iwata and Kurosawa. OMAC1 efficiently reduces the key size of Extended Cipher Block Chaining mode (XCBC). This memo specifies the use of CMAC mode as an authentication mechanism of the IPsec Encapsulating Security Payload (ESP) and the Authentication Header (AH) protocols. This new algorithm is named AES-CMAC-96. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: JH. Song, R. Poovendran, J. Lee |
| RFC4495 A Resource Reservation Protocol (RSVP) Extension for the Reduction of Bandwidth of a Reservation Flow This document proposes an extension to the Resource Reservation Protocol (RSVPv1) to reduce the guaranteed bandwidth allocated to an existing reservation. This mechanism can be used to affect individual reservations, aggregate reservations, or other forms of RSVP tunnels. This specification is an extension of RFC 2205. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: J. Polk, S. Dhesikan |
| RFC4496 Open Pluggable Edge Services (OPES) SMTP Use Cases The Open Pluggable Edge Services (OPES) framework is application agnostic. Application-specific adaptations extend that framework. This document describes OPES SMTP use cases and deployment scenarios in preparation for SMTP adaptation with OPES. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: M. Stecher, A. Barbir |
| RFC4497 Interworking between the Session Initiation Protocol (SIP) and QSIG This document specifies interworking between the Session Initiation Protocol (SIP) and QSIG within corporate telecommunication networks (also known as enterprise networks). SIP is an Internet application-layer control (signalling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include, in particular, telephone calls. QSIG is a signalling protocol for creating, modifying, and terminating circuit-switched calls (in particular, telephone calls) within Private Integrated Services Networks (PISNs). QSIG is specified in a number of Ecma Standards and published also as ISO/IEC standards. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | May 2006 Status: BEST CURRENT PRACTICE Autor: J. Elwell, F. Derks, P. Mourot, O. Rousseau |
| RFC4498 The Managed Object Aggregation MIB This memo defines a portion of the Management Information Base (MIB), the Aggregation MIB modules, for use with network management protocols in the Internet community. In particular, the Aggregation MIB modules will be used to configure a network management agent to aggregate the values of a user-specified set of Managed Object instances and to service queries related to the aggregated Managed Object instances. This memo defines an Experimental Protocol for the Internet community. | May 2006 Status: EXPERIMENTAL Autor: G. Keeni |
| RFC4501 Domain Name System Uniform Resource Identifiers This document defines Uniform Resource Identifiers for Domain Name System resources. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: S. Josefsson |
| RFC4502 Remote Network Monitoring Management Information Base Version 2 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 remote network monitoring devices. | May 2006 Status: DRAFT STANDARD Autor: S. Waldbusser |
| RFC4503 A Description of the Rabbit Stream Cipher Algorithm This document describes the encryption algorithm Rabbit. It is a stream cipher algorithm with a 128-bit key and 64-bit initialization vector (IV). The method was published in 2003 and has been subject to public security and performance revision. Its high performance makes it particularly suited for the use with Internet protocols where large amounts of data have to be processed. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: M. Boesgaard, M. Vesterager, E. Zenner |
| RFC4504 SIP Telephony Device Requirements and Configuration This document describes the requirements for SIP telephony devices, based on the deployment experience of large numbers of SIP phones and PC clients using different implementations in various networks. The objectives of the requirements are a well-defined set of interoperability and multi-vendor-supported core features, so as to enable similar ease of purchase, installation, and operation as found for PCs, PDAs, analog feature phones or mobile phones. | May 2006 Status: INFORMATIONAL Autor: H. Sinnreich, S. Lass, C. Stredicke |
| RFC4505 Anonymous Simple Authentication and Security Layer (SASL) Mechanism On the Internet, it is common practice to permit anonymous access to various services. Traditionally, this has been done with a plain-text password mechanism using "anonymous" as the user name and using optional trace information, such as an email address, as the password. As plain-text login commands are not permitted in new IETF protocols, a new way to provide anonymous login is needed within the context of the Simple Authentication and Security Layer (SASL) framework. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4506 XDR: External Data Representation Standard This document describes the External Data Representation Standard (XDR) protocol as it is currently deployed and accepted. This document obsoletes RFC 1832. [STANDARDS-TRACK] | May 2006 Status: STANDARD Autor: M. Eisler |
| RFC4507 Transport Layer Security (TLS) Session Resumption without Server-Side State This document describes a mechanism that enables the Transport Layer Security (TLS) server to resume sessions and avoid keeping \%per-client session state. The TLS server encapsulates the session state into a ticket and forwards it to the client. The client can subsequently resume a session using the obtained ticket. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: J. Salowey, H. Zhou, P. Eronen, H. Tschofenig |
| RFC4508 Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method The SIP "Caller Preferences" extension defined in RFC 3840 provides a mechanism that allows a SIP request to convey information relating to the originator's capabilities and preferences for handling of that request. The SIP REFER method defined in RFC 3515 provides a mechanism that allows one party to induce another to initiate a SIP request. This document extends the REFER method to use the mechanism of RFC 3840. By doing so, the originator of a REFER may inform the recipient as to the characteristics of the target that the induced request is expected to reach. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: O. Levin, A. Johnston |
| RFC4509 Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs) This document specifies how to use the SHA-256 digest type in DNS Delegation Signer (DS) Resource Records (RRs). DS records, when stored in a parent zone, point to DNSKEYs in a child zone. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: W. Hardaker |
| RFC4510 Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. This document provides a road map of the LDAP Technical Specification. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4511 Lightweight Directory Access Protocol (LDAP): The Protocol This document describes the protocol elements, along with their semantics and encodings, of the Lightweight Directory Access Protocol (LDAP). LDAP provides access to distributed directory services that act in accordance with X.500 data and service models. These protocol elements are based on those described in the X.500 Directory Access Protocol (DAP). [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: J. Sermersheim |
| RFC4512 Lightweight Directory Access Protocol (LDAP): Directory Information Models The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. This document describes the X.500 Directory Information Models, as used in LDAP. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4513 Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms This document describes authentication methods and security mechanisms of the Lightweight Directory Access Protocol (LDAP). This document details establishment of Transport Layer Security (TLS) using the StartTLS operation. | June 2006 Status: PROPOSED STANDARD Autor: R. Harrison |
| RFC4514 Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names The X.500 Directory uses distinguished names (DNs) as primary keys to entries in the directory. This document defines the string representation used in the Lightweight Directory Access Protocol (LDAP) to transfer distinguished names. The string representation is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4515 Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters Lightweight Directory Access Protocol (LDAP) search filters are transmitted in the LDAP protocol using a binary representation that is appropriate for use on the network. This document defines a human-readable string representation of LDAP search filters that is appropriate for use in LDAP URLs (RFC 4516) and in other applications. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: M. Smith, T. Howes |
| RFC4516 Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator This document describes a format for a Lightweight Directory Access Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL describes an LDAP search operation that is used to retrieve information from an LDAP directory, or, in the context of an LDAP referral or reference, an LDAP URL describes a service where an LDAP operation may be progressed. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: M. Smith, T. Howes |
| RFC4517 Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules Each attribute stored in a Lightweight Directory Access Protocol (LDAP) directory, whose values may be transferred in the LDAP protocol, has a defined syntax that constrains the structure and format of its values. The comparison semantics for values of a syntax are not part of the syntax definition but are instead provided through separately defined matching rules. Matching rules specify an argument, an assertion value, which also has a defined syntax. This document defines a base set of syntaxes and matching rules for use in defining attributes for LDAP directories. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: S. Legg |
| RFC4518 Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation The previous Lightweight Directory Access Protocol (LDAP) technical specifications did not precisely define how character string matching is to be performed. This led to a number of usability and interoperability problems. This document defines string preparation algorithms for character-based matching rules defined for use in LDAP. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4519 Lightweight Directory Access Protocol (LDAP): Schema for User Applications This document is an integral part of the Lightweight Directory Access Protocol (LDAP) technical specification. It provides a technical specification of attribute types and object classes intended for use by LDAP directory clients for many directory services, such as White Pages. These objects are widely used as a basis for the schema in many LDAP directories. This document does not cover attributes used for the administration of directory servers, nor does it include directory objects defined for specific uses in other documents. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: A. Sciberras |
| RFC4520 Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP) This document provides procedures for registering extensible elements of the Lightweight Directory Access Protocol (LDAP). The document also provides guidelines to the Internet Assigned Numbers Authority (IANA) describing conditions under which new values can be assigned. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2006 Status: BEST CURRENT PRACTICE Autor: K. Zeilenga |
| RFC4521 Considerations for Lightweight Directory Access Protocol (LDAP) Extensions The Lightweight Directory Access Protocol (LDAP) is extensible. It provides mechanisms for adding new operations, extending existing operations, and expanding user and system schemas. This document discusses considerations for designers of LDAP extensions. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2006 Status: BEST CURRENT PRACTICE Autor: K. Zeilenga |
| RFC4522 Lightweight Directory Access Protocol (LDAP): The Binary Encoding Option Each attribute stored in a Lightweight Directory Access Protocol (LDAP) directory has a defined syntax (i.e., data type). A syntax definition specifies how attribute values conforming to the syntax are normally represented when transferred in LDAP operations. This representation is referred to as the LDAP\-specific encoding to distinguish it from other methods of encoding attribute values. This document defines an attribute option, the binary option, that can be used to specify that the associated attribute values are instead encoded according to the Basic Encoding Rules (BER) used by X.500 directories. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: S. Legg |
| RFC4523 Lightweight Directory Access Protocol (LDAP) Schema Definitions for X.509 Certificates This document describes schema for representing X.509 certificates, X.521 security information, and related elements in directories accessible using the Lightweight Directory Access Protocol (LDAP). The LDAP definitions for these X.509 and X.521 schema elements replace those provided in RFCs 2252 and 2256. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4524 COSINE LDAP/X.500 Schema This document provides a collection of schema elements for use with the Lightweight Directory Access Protocol (LDAP) from the COSINE and Internet X.500 pilot projects. | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4525 Lightweight Directory Access Protocol (LDAP) Modify-Increment Extension This document describes an extension to the Lightweight Directory Access Protocol (LDAP) Modify operation to support an increment capability. This extension is useful in provisioning applications, especially when combined with the assertion control and/or the pre-read or post-read control extension. This memo provides information for the Internet community. | June 2006 Status: INFORMATIONAL Autor: K. Zeilenga |
| RFC4526 Lightweight Directory Access Protocol (LDAP) Absolute True and False Filters This document extends the Lightweight Directory Access Protocol (LDAP) to support absolute True and False filters based upon similar capabilities found in X.500 directory systems. The document also extends the String Representation of LDAP Search Filters to support these filters. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4527 Lightweight Directory Access Protocol (LDAP) Read Entry Controls This document specifies an extension to the Lightweight Directory Access Protocol (LDAP) to allow the client to read the target entry of an update operation. The client may request to read the entry before and/or after the modifications are applied. These reads are done as an atomic part of the update operation. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4528 Lightweight Directory Access Protocol (LDAP) Assertion Control This document defines the Lightweight Directory Access Protocol (LDAP) Assertion Control, which allows a client to specify that a directory operation should only be processed if an assertion applied to the target entry of the operation is true. It can be used to construct "test and set", "test and clear", and other conditional operations. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4529 Requesting Attributes by Object Class in the Lightweight Directory Access Protocol The Lightweight Directory Access Protocol (LDAP) search operation provides mechanisms for clients to request all user application attributes, all operational attributes, and/or attributes selected by their description. This document extends LDAP to support a mechanism that LDAP clients may use to request the return of all attributes of an object class. This memo provides information for the Internet community. | June 2006 Status: INFORMATIONAL Autor: K. Zeilenga |
| RFC4530 Lightweight Directory Access Protocol (LDAP) entryUUID Operational Attribute This document describes the LDAP/X.500 \'entryUUID' operational attribute and associated matching rules and syntax. The attribute holds a server-assigned Universally Unique Identifier (UUID) for the object. Directory clients may use this attribute to distinguish objects identified by a distinguished name or to locate an object after renaming. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4531 Lightweight Directory Access Protocol (LDAP) Turn Operation This specification describes a Lightweight Directory Access Protocol (LDAP) extended operation to reverse (or "turn") the roles of client and server for subsequent protocol exchanges in the session, or to enable each peer to act as both client and server with respect to the other. This memo defines an Experimental Protocol for the Internet community. | June 2006 Status: EXPERIMENTAL Autor: K. Zeilenga |
| RFC4532 Lightweight Directory Access Protocol (LDAP) "Who am I?" Operation This specification provides a mechanism for Lightweight Directory Access Protocol (LDAP) clients to obtain the authorization identity the server has associated with the user or application entity. This mechanism is specified as an LDAP extended operation called the LDAP "Who am I?" operation. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4533 The Lightweight Directory Access Protocol (LDAP) Content Synchronization Operation This specification describes the Lightweight Directory Access Protocol (LDAP) Content Synchronization Operation. The operation allows a client to maintain a copy of a fragment of the Directory Information Tree (DIT). It supports both polling for changes and listening for changes. The operation is defined as an extension of the LDAP Search Operation. This memo defines an Experimental Protocol for the Internet community. | June 2006 Status: EXPERIMENTAL Autor: K. Zeilenga, J.H. Choi |
| RFC4534 Group Security Policy Token v1 The Group Security Policy Token is a structure used to specify the security policy and configurable parameters for a cryptographic group, such as a secure multicast group. Because the security of a group is composed of the totality of multiple security services, mechanisms, and attributes throughout the communications infrastructure, an authenticatable representation of the features that must be supported throughout the system is needed to ensure consistent security. This document specifies the structure of such a token. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: A Colegrove, H Harney |
| RFC4535 GSAKMP: Group Secure Association Key Management Protocol This document specifies the Group Secure Association Key Management Protocol (GSAKMP). The GSAKMP provides a security framework for creating and managing cryptographic groups on a network. It provides mechanisms to disseminate group policy and authenticate users, rules to perform access control decisions during group establishment and recovery, capabilities to recover from the compromise of group members, delegation of group security functions, and capabilities to destroy the group. It also generates group keys. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: H. Harney, U. Meth, A. Colegrove, G. Gross |
| RFC4536 The application/smil and application/smil+xml Media Types This document specifies the media type for versions 1.0, 2.0, and 2.1 of the Synchronized Multimedia Integration Language (SMIL 1.0, SMIL 2.0, SMIL 2.1). SMIL allows integration of a set of independent multimedia objects into a synchronized multimedia presentation. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: P. Hoschka |
| RFC4537 Kerberos Cryptosystem Negotiation Extension This document specifies an extension to the Kerberos protocol as defined in RFC 4120, in which the client can send a list of supported encryption types in decreasing preference order, and the server then selects an encryption type that is supported by both the client and the server. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: L. Zhu, P. Leach, K. Jaganathan |
| RFC4538 Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP) This specification defines the Target-Dialog header field for the Session Initiation Protocol (SIP), and the corresponding option tag, tdialog. This header field is used in requests that create SIP dialogs. It indicates to the recipient that the sender is aware of an existing dialog with the recipient, either because the sender is on the other side of that dialog, or because it has access to the dialog identifiers. The recipient can then authorize the request based on this awareness. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC4539 Media Type Registration for the Society of Motion Picture and Television Engineers (SMPTE) Material Exchange Format (MXF) This document serves to register a media type for the Society of Motion Picture and Television Engineers (SMPTE) Material Exchange Format (MXF). MXF, defined by SMPTE 377M, is a standard wrapper format developed for the interchange of audiovisual material, including both audiovisual essence and rich metadata. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: T. Edwards |
| RFC4540 NEC's Simple Middlebox Configuration (SIMCO) Protocol Version 3.0 This document describes a protocol for controlling middleboxes such as firewalls and network address translators. It is a fully compliant implementation of the Middlebox Communications (MIDCOM) semantics described in RFC 3989. Compared to earlier experimental versions of the SIMCO protocol, this version (3.0) uses binary message encodings in order to reduce resource requirements. This memo defines an Experimental Protocol for the Internet community. | May 2006 Status: EXPERIMENTAL Autor: M. Stiemerling, J. Quittek, C. Cadar |
| RFC4541 Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches This memo describes the recommendations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) snooping switches. These are based on best current practices for IGMPv2, with further considerations for IGMPv3- and MLDv2-snooping. Additional areas of relevance, such as link layer topology changes and Ethernet-specific encapsulation issues, are also considered. This memo provides information for the Internet community. | May 2006 Status: INFORMATIONAL Autor: M. Christensen, K. Kimball, F. Solensky |
| RFC4542 Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol Suite RFCs 3689 and 3690 detail requirements for an Emergency Telecommunications Service (ETS), of which an Internet Emergency Preparedness Service (IEPS) would be a part. Some of these types of services require call preemption; others require call queuing or other mechanisms. IEPS requires a Call Admission Control (CAC) procedure and a Per Hop Behavior (PHB) for the data that meet the needs of this architecture. Such a CAC procedure and PHB is appropriate to any service that might use H.323 or SIP to set up real-time sessions. The key requirement is to guarantee an elevated probability of call completion to an authorized user in time of crisis. | May 2006 Status: INFORMATIONAL Autor: F. Baker, J. Polk |
| RFC4543 The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH This memo describes the use of the Advanced Encryption Standard (AES) Galois Message Authentication Code (GMAC) as a mechanism to provide data origin authentication, but not confidentiality, within the IPsec Encapsulating Security Payload (ESP) and Authentication Header (AH). GMAC is based on the Galois/Counter Mode (GCM) of operation, and can be efficiently implemented in hardware for speeds of 10 gigabits per second and above, and is also well-suited to software implementations. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: D. McGrew, J. Viega |
| RFC4544 Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI) 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 using the Internet Small Computer System Interface (iSCSI) protocol (SCSI over TCP). [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: M. Bakke, M. Krueger, T. McSweeney, J. Muchow |
| RFC4545 Definitions of Managed Objects for IP Storage User Identity Authorization 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 user identities and the names, addresses, and credentials required manage access control, for use with various protocols. This document was motivated by the need for the configuration of authorized user identities for the iSCSI protocol, but has been extended to be useful for other protocols that have similar requirements. It is important to note that this MIB module provides only the set of identities to be used within access lists; it is the responsibility of other MIB modules making use of this one to tie them to their own access lists or other authorization control methods. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: M. Bakke, J. Muchow |
| RFC4546 Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF Interfaces 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 the Radio Frequency (RF) interfaces for systems compliant with the Data Over Cable Service Interface Specifications (DOCSIS). [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: D. Raftus, E. Cardona |
| RFC4547 Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination Systems 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 Simple Network Management Protocol (SNMP) based event notification management of Data Over Cable Service Interface Specification (DOCSIS) compliant Cable Modems and Cable Modem Termination Systems. This MIB is defined as an extension to the DOCSIS Cable Device MIB. | June 2006 Status: PROPOSED STANDARD Autor: A. Ahmad, G. Nakanishi |
| RFC4548 Internet Code Point (ICP) Assignments for NSAP Addresses This document is intended to accomplish two highly inter-related tasks: to establish an "initial" Internet Code Point (ICP) assignment for each of IPv4 and IPv6 address encoding in Network Service Access Point (NSAP) Addresses, and to recommend an IANA assignment policy for currently unassigned ICP values. In the first task, this document is a partial replacement for RFC 1888 -- particularly for section 6 of RFC 1888. In the second task, this document incorporates wording and specifications from ITU-T Recommendation X.213 and further recommends that IANA use the "IETF consensus" assignment policy in making future ICP assignments. [STANDARDS-TRACK] | May 2006 Status: PROPOSED STANDARD Autor: E. Gray, J. Rutemiller, G. Swallow |
| RFC4549 Synchronization Operations for Disconnected IMAP4 Clients This document attempts to address some of the issues involved in building a disconnected IMAP4 client. In particular, it deals with the issues of what might be called the "driver" portion of the synchronization tool: the portion of the code responsible for issuing the correct set of IMAP4 commands to synchronize the disconnected client in the way that is most likely to make the human who uses the disconnected client happy. | June 2006 Status: INFORMATIONAL Autor: A. Melnikov |
| RFC4550 Internet Email to Support Diverse Service Environments (Lemonade) Profile This document describes a profile (a set of required extensions, restrictions, and usage modes) of the IMAP and mail submission protocols. This profile allows clients (especially those that are constrained in memory, bandwidth, processing power, or other areas) to efficiently use IMAP and Submission to access and submit mail. This includes the ability to forward received mail without needing to download and upload the mail, to optimize submission, and to efficiently resynchronize in case of loss of connectivity with the server. | June 2006 Status: PROPOSED STANDARD Autor: S. Maes, A. Melnikov |
| RFC4551 IMAP Extension for Conditional STORE Operation or Quick Flag Changes Resynchronization Often, multiple IMAP (RFC 3501) clients need to coordinate changes to a common IMAP mailbox. Examples include different clients working on behalf of the same user, and multiple users accessing shared mailboxes. These clients need a mechanism to synchronize state changes for messages within the mailbox. They must be able to guarantee that only one client can change message state (e.g., message flags) at any time. An example of such an application is use of an IMAP mailbox as a message queue with multiple dequeueing clients. | June 2006 Status: PROPOSED STANDARD Autor: A. Melnikov, S. Hole |
| RFC4552 Authentication/Confidentiality for OSPFv3 This document describes means and mechanisms to provide authentication/confidentiality to OSPFv3 using an IPv6 Authentication Header/Encapsulating Security Payload (AH/ESP) extension header. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: M. Gupta, N. Melam |
| RFC4553 Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) This document describes a pseudowire encapsulation for Time Division Multiplexing (TDM) bit-streams (T1, E1, T3, E3) that disregards any structure that may be imposed on these streams, in particular the structure imposed by the standard TDM framing. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: A. Vainshtein, YJ. Stein |
| RFC4554 Use of VLANs for IPv4-IPv6 Coexistence in Enterprise Networks Ethernet VLANs are quite commonly used in enterprise networks for the purposes of traffic segregation. This document describes how such VLANs can be readily used to deploy IPv6 networking in an enterprise, which focuses on the scenario of early deployment prior to availability of IPv6-capable switch-router equipment. In this method, IPv6 may be routed in parallel with the existing IPv4 in the enterprise and delivered at Layer 2 via VLAN technology. The IPv6 connectivity to the enterprise may or may not enter the site via the same physical link. This memo provides information for the Internet community. | June 2006 Status: INFORMATIONAL Autor: T. Chown |
| RFC4555 IKEv2 Mobility and Multihoming Protocol (MOBIKE) This document describes the MOBIKE protocol, a mobility and multihoming extension to Internet Key Exchange (IKEv2). MOBIKE allows the IP addresses associated with IKEv2 and tunnel mode IPsec Security Associations to change. A mobile Virtual Private Network (VPN) client could use MOBIKE to keep the connection with the VPN gateway active while moving from one address to another. Similarly, a multihomed host could use MOBIKE to move the traffic to a different interface if, for instance, the one currently being used stops working. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: P. Eronen |
| RFC4556 Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) This document describes protocol extensions (hereafter called PKINIT) to the Kerberos protocol specification. These extensions provide a method for integrating public key cryptography into the initial authentication exchange, by using asymmetric-key signature and/or encryption algorithms in pre-authentication data fields. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: L. Zhu, B. Tung |
| RFC4557 Online Certificate Status Protocol (OCSP) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) This document defines a mechanism to enable in-band transmission of Online Certificate Status Protocol (OCSP) responses in the Kerberos network authentication protocol. These responses are used to verify the validity of the certificates used in Public Key Cryptography for Initial Authentication in Kerberos (PKINIT), which is the Kerberos Version 5 extension that provides for the use of public key cryptography. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: L. Zhu, K. Jaganathan, N. Williams |
| RFC4558 Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement Use of Node-ID based Resource Reservation Protocol (RSVP) Hello messages is implied in a number of cases, e.g., when data and control planes are separated, when TE links are unnumbered. Furthermore, when link level failure detection is performed by some means other than exchanging RSVP Hello messages, use of a Node-ID based Hello session is optimal for detecting signaling adjacency failure for Resource reSerVation Protocol-Traffic Engineering (RSVP-TE). Nonetheless, this implied behavior is unclear, and this document formalizes use of the Node-ID based RSVP Hello session in some scenarios. The procedure described in this document applies to both Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) capable nodes. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: Z. Ali, R. Rahman, D. Prairie, D. Papadimitriou |
| RFC4559 SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows This document describes how the Microsoft Internet Explorer (MSIE) and Internet Information Services (IIS) incorporated in Microsoft Windows 2000 use Kerberos for security enhancements of web transactions. The Hypertext Transport Protocol (HTTP) auth-scheme of "negotiate" is defined here; when the negotiation results in the selection of Kerberos, the security services of authentication and, optionally, impersonation (the IIS server assumes the windows identity of the principal that has been authenticated) are performed. This document explains how HTTP authentication utilizes the Simple and Protected GSS-API Negotiation mechanism. Details of Simple And Protected Negotiate (SPNEGO) implementation are not provided in this document. This memo provides information for the Internet community. | June 2006 Status: INFORMATIONAL Autor: K. Jaganathan, L. Zhu, J. Brezak |
| RFC4560 Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations This memo defines Management Information Bases (MIBs) for performing ping, traceroute, and lookup operations at a host. When managing a network, it is useful to be able to initiate and retrieve the results of ping or traceroute operations when they are performed at a remote host. A lookup capability is defined in order to enable resolution of either an IP address to an DNS name or a DNS name to an IP address at a remote host. | June 2006 Status: PROPOSED STANDARD Autor: J. Quittek, K. White |
| RFC4561 Definition of a Record Route Object (RRO) Node-Id Sub-Object In the context of MPLS TE Fast Reroute, the Merge Point (MP) address is required at the Point of Local Repair (PLR) in order to select a backup tunnel intersecting a fast reroutable Traffic Engineering Label Switched Path (TE LSP) on a downstream Label Switching Router (LSR). However, existing protocol mechanisms are not sufficient to find an MP address in multi-domain routing networks where a domain is defined as an Interior Gateway Protocol (IGP) area or an Autonomous System (AS). Hence, the current MPLS Fast Reroute mechanism cannot be used in order to protect inter-domain TE LSPs from a failure of an Area Border Router (ABR) or Autonomous System Border Router (ASBR). This document specifies the use of existing Record Route Object (RRO) IPv4 and IPv6 sub-objects (with a new flag defined) thus defining the node-id sub-object in order to solve this issue. The MPLS Fast Reroute mechanism mentioned in this document refers to the "Facility backup" MPLS TE Fast Reroute method. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: J.-P. Vasseur, Z. Ali, S. Sivabalan |
| RFC4562 MAC-Forced Forwarding: A Method for Subscriber Separation on an Ethernet Access Network This document describes a mechanism to ensure layer-2 separation of Local Area Network (LAN) stations accessing an IPv4 gateway over a bridged Ethernet segment. | June 2006 Status: INFORMATIONAL Autor: T. Melsen, S. Blake |
| RFC4563 The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY) This memo specifies a new Type (the Key ID Information Type) for the General Extension Payload in the Multimedia Internet KEYing (MIKEY) Protocol. This is used in, for example, the Multimedia Broadcast/Multicast Service specified in the Third Generation Partnership Project. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: E. Carrara, V. Lehtovirta, K. Norrman |
| RFC4564 Objectives for Control and Provisioning of Wireless Access Points (CAPWAP) This document presents objectives for an interoperable protocol for the Control and Provisioning of Wireless Access Points (CAPWAP). The document aims to establish a set of focused requirements for the development and evaluation of a CAPWAP protocol. The objectives address architecture, operation, security, and network operator requirements that are necessary to enable interoperability among Wireless Local Area Network (WLAN) devices of alternative designs. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: S. Govindan, H. Cheng, ZH. Yao, WH. Zhou, L. Yang |
| RFC4565 Evaluation of Candidate Control and Provisioning of Wireless Access Points (CAPWAP) Protocols This document is a record of the process and findings of the Control and Provisioning of Wireless Access Points Working Group (CAPWAP WG) evaluation team. The evaluation team reviewed the 4 candidate protocols as they were submitted to the working group on June 26, 2005. his memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: D. Loher, D. Nelson, O. Volinsky, B. Sarikaya |
| RFC4566 SDP: Session Description Protocol This memo 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] | July 2006 Status: PROPOSED STANDARD Autor: M. Handley, V. Jacobson, C. Perkins |
| RFC4567 Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP) This document defines general extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP) to carry messages, as specified by a key management protocol, in order to secure the media. These extensions are presented as a framework, to be used by one or more key management protocols. As such, their use is meaningful only when complemented by an appropriate key management protocol. | July 2006 Status: PROPOSED STANDARD Autor: J. Arkko, F. Lindholm, M. Naslund, K. Norrman, E. Carrara |
| RFC4568 Session Description Protocol (SDP) Security Descriptions for Media Streams This document defines a Session Description Protocol (SDP) cryptographic attribute for unicast media streams. The attribute describes a cryptographic key and other parameters that serve to configure security for a unicast media stream in either a single message or a roundtrip exchange. The attribute can be used with a variety of SDP media transports, and this document defines how to use it for the Secure Real-time Transport Protocol (SRTP) unicast media streams. The SDP crypto attribute requires the services of a data security protocol to secure the SDP message. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: F. Andreasen, M. Baugher, D. Wing |
| RFC4569 Internet Assigned Number Authority (IANA) Registration of the Message Media Feature Tag This document registers with the IANA a new media feature tag associated with the 'message' media type. This media feature tag indicates that a particular device supports 'message' as a streaming media type. Media feature tags can be used to route calls to devices that support certain features. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: G. Camarillo |
| RFC4570 Session Description Protocol (SDP) Source Filters This document describes how to adapt the Session Description Protocol (SDP) to express one or more source addresses as a source filter for one or more destination "connection" addresses. It defines the syntax and semantics for an SDP "source-filter" attribute that may reference either IPv4 or IPv6 address(es) as either an inclusive or exclusive source list for either multicast or unicast destinations. In particular, an inclusive source-filter can be used to specify a Source-Specific Multicast (SSM) session. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: B. Quinn, R. Finlayson |
| RFC4571 Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport This memo defines a method for framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) packets onto connection-oriented transport (such as TCP). The memo also defines how session descriptions may specify RTP streams that use the framing method. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: J. Lazzaro |
| RFC4572 Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP) This document specifies how to establish secure connection-oriented media transport sessions over the Transport Layer Security (TLS) protocol using the Session Description Protocol (SDP). It defines a new SDP protocol identifier, 'TCP/TLS'. It also defines the syntax and semantics for an SDP 'fingerprint' attribute that identifies the certificate that will be presented for the TLS session. This mechanism allows media transport over TLS connections to be established securely, so long as the integrity of session descriptions is assured. | July 2006 Status: PROPOSED STANDARD Autor: J. Lennox |
| RFC4573 MIME Type Registration for RTP Payload Format for H.224 In conversational video applications, far-end camera control protocol is used by participants to control the remote camera. The protocol that is commonly used is ITU H.281 over H.224. The document registers the H224 media type. It defines the syntax and the semantics of the Session Description Protocol (SDP) parameters needed to support far-end camera control protocol using H.224. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: R. Even, A. Lochbaum |
| RFC4574 The Session Description Protocol (SDP) Label Attribute This document defines a new Session Description Protocol (SDP) media-level attribute: "label". The "label" attribute carries a pointer to a media stream in the context of an arbitrary network application that uses SDP. The sender of the SDP document can attach the "label" attribute to a particular media stream or streams. The application can then use the provided pointer to refer to each particular media stream in its context. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: O. Levin, G. Camarillo |
| RFC4575 A Session Initiation Protocol (SIP) Event Package for Conference State This document defines a conference event package for tightly coupled conferences using the Session Initiation Protocol (SIP) events framework, along with a data format used in notifications for this package. The conference package allows users to subscribe to a conference Uniform Resource Identifier (URI). Notifications are sent about changes in the membership of this conference and optionally about changes in the state of additional conference components. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: J. Rosenberg, H. Schulzrinne, O. Levin |
| RFC4576 Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs) This document specifies a procedure that deals with a particular issue that may arise when a Service Provider (SP) provides "BGP/MPLS IP VPN" service to a customer and the customer uses OSPFv2 to advertise its routes to the SP. In this situation, a Customer Edge (CE) Router and a Provider Edge (PE) Router are OSPF peers, and customer routes are sent via OSPFv2 from the CE to the PE. The customer routes are converted into BGP routes, and BGP carries them across the backbone to other PE routers. The routes are then converted back to OSPF routes sent via OSPF to other CE routers. As a result of this conversion, some of the information needed to prevent loops may be lost. A procedure is needed to ensure that once a route is sent from a PE to a CE, the route will be ignored by any PE that receives it back from a CE. This document specifies the necessary procedure, using one of the options bits in the LSA (Link State Advertisements) to indicate that an LSA has already been forwarded by a PE and should be ignored by any other PEs that see it. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: E. Rosen, P. Psenak, P. Pillay-Esnault |
| RFC4577 OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) Many Service Providers offer Virtual Private Network (VPN) services to their customers, using a technique in which customer edge routers (CE routers) are routing peers of provider edge routers (PE routers). The Border Gateway Protocol (BGP) is used to distribute the customer's routes across the provider's IP backbone network, and Multiprotocol Label Switching (MPLS) is used to tunnel customer packets across the provider's backbone. This is known as a "BGP/MPLS IP VPN". The base specification for BGP/MPLS IP VPNs presumes that the routing protocol on the interface between a PE router and a CE router is BGP. This document extends that specification by allowing the routing protocol on the PE/CE interface to be the Open Shortest Path First (OSPF) protocol. | June 2006 Status: PROPOSED STANDARD Autor: E. Rosen, P. Psenak, P. Pillay-Esnault |
| RFC4578 Dynamic Host Configuration Protocol (DHCP) Options for the Intel Preboot eXecution Environment (PXE) We define Dynamic Host Configuration Protocol (DHCP) options being used by Preboot eXecution Environment (PXE) and Extensible Firmware Interface (EFI) clients to uniquely identify booting client machines and their pre-OS runtime environment so that the DHCP and/or PXE boot server can return the correct OS bootstrap image (or pre-boot application) name and server to the client. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: M. Johnston, S. Venaas |
| RFC4579 Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents This specification defines conferencing call control features for the Session Initiation Protocol (SIP). This document builds on the Conferencing Requirements and Framework documents to define how a tightly coupled SIP conference works. The approach is explored from the perspective of different user agent (UA) types: conference-unaware, conference-aware, and focus UAs. The use of Uniform Resource Identifiers (URIs) in conferencing, OPTIONS for capabilities discovery, and call control using REFER are covered in detail with example call flow diagrams. The usage of the isfocus feature tag is defined. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2006 Status: BEST CURRENT PRACTICE Autor: A. Johnston, O. Levin |
| RFC4580 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option This memo defines a new Relay Agent Subscriber-ID option for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option allows a DHCPv6 relay agent to associate a stable "Subscriber-ID" with DHCPv6 client messages in a way that is independent of the client and of the underlying physical network infrastructure. [STANDARDS-TRACK] | June 2006 Status: PROPOSED STANDARD Autor: B. Volz |
| RFC4581 Cryptographically Generated Addresses (CGA) Extension Field Format This document defines a Type-Length-Value format for Cryptographically Generated Address (CGA) Extensions. This document updates RFC 3972. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: M. Bagnulo, J. Arkko |
| RFC4582 The Binary Floor Control Protocol (BFCP) Floor control is a means to manage joint or exclusive access to shared resources in a (multiparty) conferencing environment. Thereby, floor control complements other functions -- such as conference and media session setup, conference policy manipulation, and media control -- that are realized by other protocols. | November 2006 Status: PROPOSED STANDARD Autor: G. Camarillo, J. Ott, K. Drage |
| RFC4583 Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams This document specifies how to describe Binary Floor Control Protocol (BFCP) streams in Session Description Protocol (SDP) descriptions. User agents using the offer/answer model to establish BFCP streams use this format in their offers and answers. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC4584 Extension to Sockets API for Mobile IPv6 This document describes data structures and API support for Mobile IPv6 as an extension to the Advanced Socket API for IPv6. | July 2006 Status: INFORMATIONAL Autor: S. Chakrabarti, E. Nordmark |
| RFC4585 Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF) Real-time media streams that use RTP are, to some degree, resilient against packet losses. Receivers may use the base mechanisms of the Real-time Transport Control Protocol (RTCP) to report packet reception statistics and thus allow a sender to adapt its transmission behavior in the mid-term. This is the sole means for feedback and feedback-based error repair (besides a few codec-specific mechanisms). This document defines an extension to the Audio-visual Profile (AVP) that enables receivers to provide, statistically, more immediate feedback to the senders and thus allows for short-term adaptation and efficient feedback-based repair mechanisms to be implemented. This early feedback profile (AVPF) maintains the AVP bandwidth constraints for RTCP and preserves scalability to large groups. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: J. Ott, S. Wenger, N. Sato, C. Burmeister, J. Rey |
| RFC4586 Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback: Results of the Timing Rule Simulations This document describes the results achieved when simulating the timing rules of the Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback, denoted AVPF. Unicast and multicast topologies are considered as well as several protocol and environment configurations. The results show that the timing rules result in better performance regarding feedback delay and still preserve the well-accepted RTP rules regarding allowed bit rates for control traffic. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: C. Burmeister, R. Hakenberg, A. Miyazaki, J. Ott, N. Sato, S. Fukunaga |
| RFC4587 RTP Payload Format for H.261 Video Streams This memo describes a scheme to packetize an H.261 video stream for transport using the Real-time Transport Protocol, RTP, with any of the underlying protocols that carry RTP. | August 2006 Status: PROPOSED STANDARD Autor: R. Even |
| RFC4588 RTP Retransmission Payload Format RTP retransmission is an effective packet loss recovery technique for real-time applications with relaxed delay bounds. This document describes an RTP payload format for performing retransmissions. Retransmitted RTP packets are sent in a separate stream from the original RTP stream. It is assumed that feedback from receivers to senders is available. In particular, it is assumed that Real-time Transport Control Protocol (RTCP) feedback as defined in the extended RTP profile for RTCP-based feedback (denoted RTP/AVPF) is available in this memo. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: J. Rey, D. Leon, A. Miyazaki, V. Varsa, R. Hakenberg |
| RFC4589 Location Types Registry This document creates a registry for describing the types of places a human or end system might be found. The registry is then referenced by other protocols that need a common set of location terms as protocol constants. Examples of location terms defined in this document include aircraft, office, and train station. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne, H. Tschofenig |
| RFC4590 RADIUS Extension for Digest Authentication This document defines an extension to the Remote Authentication Dial-In User Service (RADIUS) protocol to enable support of Digest Authentication, for use with HTTP-style protocols like the Session Initiation Protocol (SIP) and HTTP. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: B. Sterman, D. Sadolevsky, D. Schwartz, D. Williams, W. Beck |
| RFC4591 Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3) The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a protocol for tunneling a variety of data link protocols over IP networks. This document describes the specifics of how to tunnel Frame Relay over L2TPv3, including frame encapsulation, virtual-circuit creation and deletion, and status change notification. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: M. Townsley, G. Wilkie, S. Booth, S. Bryant, J. Lau |
| RFC4592 The Role of Wildcards in the Domain Name System This is an update to the wildcard definition of RFC 1034. The interaction with wildcards and CNAME is changed, an error condition is removed, and the words defining some concepts central to wildcards are changed. The overall goal is not to change wildcards, but to refine the definition of RFC 1034. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: E. Lewis |
| RFC4593 Generic Threats to Routing Protocols Routing protocols are subject to attacks that can harm individual users or network operations as a whole. This document provides a description and a summary of generic threats that affect routing protocols in general. This work describes threats, including threat sources and capabilities, threat actions, and threat consequences, as well as a breakdown of routing functions that might be attacked separately. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: A. Barbir, S. Murphy, Y. Yang |
| RFC4594 Configuration Guidelines for DiffServ Service Classes This document describes service classes configured with Diffserv and recommends how they can be used and how to construct them using Differentiated Services Code Points (DSCPs), traffic conditioners, Per-Hop Behaviors (PHBs), and Active Queue Management (AQM) mechanisms. There is no intrinsic requirement that particular DSCPs, traffic conditioners, PHBs, and AQM be used for a certain service class, but as a policy and for interoperability it is useful to apply them consistently. This memo provides information for the Internet community. | August 2006 Status: INFORMATIONAL Autor: J. Babiarz, K. Chan, F. Baker |
| RFC4595 Use of IKEv2 in the Fibre Channel Security Association Management Protocol This document describes the use of IKEv2 to negotiate security protocols and transforms for Fibre Channel as part of the Fibre Channel Security Association Management Protocol. This usage requires that IKEv2 be extended with Fibre-Channel-specific security protocols, transforms, and name types. This document specifies these IKEv2 extensions and allocates identifiers for them. Using new IKEv2 identifiers for Fibre Channel security protocols avoids any possible confusion between IKEv2 negotiation for IP networks and IKEv2 negotiation for Fibre Channel. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: F. Maino, D. Black |
| RFC4596 Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension This document contains guidelines for usage of the Caller Preferences Extension to the Session Initiation Protocol (SIP). It demonstrates the benefits of caller preferences with specific example applications, provides use cases to show proper operation, provides guidance on the applicability of the registered feature tags, and describes a straightforward implementation of the preference and capability matching algorithm specified in Section 7.2 of RFC 3841. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: J. Rosenberg, P. Kyzivat |
| RFC4597 Conferencing Scenarios This document describes multimedia conferencing scenarios. It describes both basic and advanced conferencing scenarios involving voice, video, text, and interactive text sessions. These scenarios will help with the definition and evaluation of the protocols being developed in the centralized conferencing XCON working group. This memo provides information for the Internet community. | August 2006 Status: INFORMATIONAL Autor: R. Even, N. Ismail |
| RFC4598 Real-time Transport Protocol (RTP) Payload Format for Enhanced AC-3 (E-AC-3) Audio This document describes a Real-time Transport Protocol (RTP) payload format for transporting Enhanced AC-3 (E-AC-3) encoded audio data. E-AC-3 is a high-quality, multichannel audio coding format and is an extension of the AC-3 audio coding format, which is used in US High-Definition Television (HDTV), DVD, cable and satellite television, and other media. E-AC-3 is an optional audio format in US and world wide digital television and high-definition DVD formats. The RTP payload format as presented in this document includes support for data fragmentation. [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: B. Link |
| RFC4601 Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised) This document specifies Protocol Independent Multicast - Sparse Mode (PIM-SM). PIM-SM is a multicast routing protocol that can use the underlying unicast routing information base or a separate multicast-capable routing information base. It builds unidirectional shared trees rooted at a Rendezvous Point (RP) per group, and optionally creates shortest-path trees per source. | August 2006 Status: PROPOSED STANDARD Autor: B. Fenner, M. Handley, H. Holbrook, I. Kouvelas |
| RFC4602 Protocol Independent Multicast - Sparse Mode (PIM-SM) IETF Proposed Standard Requirements Analysis This document provides supporting documentation to advance the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing protocol from IETF Experimental status to Proposed Standard. This memo provides information for the Internet community. | August 2006 Status: INFORMATIONAL Autor: T. Pusateri |
| RFC4603 Additional Values for the NAS-Port-Type Attribute This document defines a set of values for the NAS-Port-Type RADIUS Attribute. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: G. Zorn, G. Weber, R. Foltak |
| RFC4604 Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast The Internet Group Management Protocol Version 3 (IGMPv3) and the Multicast Listener Discovery Protocol Version 2 (MLDv2) are protocols that allow a host to inform its neighboring routers of its desire to receive IPv4 and IPv6 multicast transmissions, respectively. Source-specific multicast (SSM) is a form of multicast in which a receiver is required to specify both the network-layer address of the source and the multicast destination address in order to receive the multicast transmission. This document defines the notion of an "SSM-aware" router and host, and clarifies and (in some cases) modifies the behavior of IGMPv3 and MLDv2 on SSM-aware routers and hosts to accommodate source-specific multicast. This document updates the IGMPv3 and MLDv2 specifications. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: H. Holbrook, B. Cain, B. Haberman |
| RFC4605 Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP/MLD Proxying") In certain topologies, it is not necessary to run a multicast routing protocol. It is sufficient for a device to learn and proxy group membership information and simply forward multicast packets based upon that information. This document describes a mechanism for forwarding based solely upon Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) membership information. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: B. Fenner, H. He, B. Haberman, H. Sandick |
| RFC4606 Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control This document provides minor clarification to RFC 3946. | August 2006 Status: PROPOSED STANDARD Autor: E. Mannie, D. Papadimitriou |
| RFC4607 Source-Specific Multicast for IP IP version 4 (IPv4) addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are designated as source-specific multicast (SSM) destination addresses and are reserved for use by source-specific applications and protocols. For IP version 6 (IPv6), the address prefix FF3x::/32 is reserved for source-specific multicast use. This document defines an extension to the Internet network service that applies to datagrams sent to SSM addresses and defines the host and router requirements to support this extension. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: H. Holbrook, B. Cain |
| RFC4608 Source-Specific Protocol Independent Multicast in 232/8 IP Multicast group addresses in the 232/8 (232.0.0.0 to 232.255.255.255) range are designated as source-specific multicast destination addresses and are reserved for use by source-specific multicast applications and protocols. This document defines operational recommendations to ensure source-specific behavior within the 232/8 range. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2006 Status: BEST CURRENT PRACTICE Autor: D. Meyer, R. Rockell, G. Shepherd |
| RFC4609 Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and Enhancements This memo describes security threats for the larger (intra-domain or inter-domain) multicast routing infrastructures. Only Protocol Independent Multicast - Sparse Mode (PIM-SM) is analyzed, in its three main operational modes: the traditional Any-Source Multicast (ASM) model, the source-specific multicast (SSM) model, and the ASM model enhanced by the Embedded Rendezvous Point (Embedded-RP) group-to-RP mapping mechanism. This memo also describes enhancements to the protocol operations that mitigate the identified threats. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: P. Savola, R. Lehtonen, D. Meyer |
| RFC4610 Anycast-RP Using Protocol Independent Multicast (PIM) This specification allows Anycast-RP (Rendezvous Point) to be used inside a domain that runs Protocol Independent Multicast (PIM) only. Other multicast protocols (such as Multicast Source Discovery Protocol (MSDP), which has been used traditionally to solve this problem) are not required to support Anycast-RP. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: D. Farinacci, Y. Cai |
| RFC4611 Multicast Source Discovery Protocol (MSDP) Deployment Scenarios This document describes best current practices for intra-domain and inter-domain deployment of the Multicast Source Discovery Protocol (MSDP) in conjunction with Protocol Independent Multicast Sparse Mode (PIM-SM). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2006 Status: BEST CURRENT PRACTICE Autor: M. McBride, J. Meylor, D. Meyer |
| RFC4612 Real-Time Facsimile (T.38) - audio/t38 MIME Sub-type Registration This document defines the MIME sub-type audio/t38. The usage of this MIME type, which is intended for use within Session Description Protocol (SDP), is specified within ITU-T Recommendation T.38. This memo defines a Historic Document for the Internet community. | August 2006 Status: HISTORIC Autor: P. Jones, H. Tamura |
| RFC4613 Media Type Registrations for Downloadable Sounds for Musical Instrument Digital Interface (MIDI) This document serves to register a media type for Downloadable Sounds. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: P. Frojdh, U. Lindgren, M. Westerlund |
| RFC4614 A Roadmap for Transmission Control Protocol (TCP) Specification Documents This document contains a "roadmap" to the Requests for Comments (RFC) documents relating to the Internet's Transmission Control Protocol (TCP). This roadmap provides a brief summary of the documents defining TCP and various TCP extensions that have accumulated in the RFC series. This serves as a guide and quick reference for both TCP implementers and other parties who desire information contained in the TCP-related RFCs. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: M. Duke, R. Braden, W. Eddy, E. Blanton |
| RFC4615 The Advanced Encryption Standard-Cipher-based Message Authentication Code-Pseudo-Random Function-128 (AES-CMAC-PRF-128) Algorithm for the Internet Key Exchange Protocol (IKE) Some implementations of IP Security (IPsec) may want to use a pseudo-random function (PRF) based on the Advanced Encryption Standard (AES). This memo describes such an algorithm, called AES-CMAC-PRF-128. It supports fixed and variable key sizes. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: J. Song, R. Poovendran, J. Lee, T. Iwata |
| RFC4616 The PLAIN Simple Authentication and Security Layer (SASL) Mechanism This document defines a simple clear-text user/password Simple Authentication and Security Layer (SASL) mechanism called the PLAIN mechanism. The PLAIN mechanism is intended to be used, in combination with data confidentiality services provided by a lower layer, in protocols that lack a simple password authentication command. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC4617 A Uniform Resource Name (URN) Formal Namespace for the Latvian National Government Integration Project This document describes a Uniform Resource Name (URN) namespace that is engineered by a consortium (general contractor, Olimps LTD, and subcontractors, ABC software LTD, Microsoft Latvia LTD, Riga Internet eXchange (RIX) Technologies LTD, and Microlink LTD) for naming information resources published and produced by the Latvian National Government Integration Project (Latvian abbreviation IVIS). This memo provides information for the Internet community. | August 2006 Status: INFORMATIONAL Autor: J. Kornijenko |
| RFC4618 Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS Networks A pseudowire (PW) can be used to carry Point to Point Protocol (PPP) or High-Level Data Link Control (HDLC) Protocol Data Units over a Multiprotocol Label Switching (MPLS) network without terminating the PPP/HDLC protocol. This enables service providers to offer "emulated" HDLC, or PPP link services over existing MPLS networks. This document specifies the encapsulation of PPP/HDLC Packet Data Units (PDUs) within a pseudowire. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: L. Martini, E. Rosen, G. Heron, A. Malis |
| RFC4619 Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) Networks A frame relay pseudowire is a mechanism that exists between a provider's edge network nodes and that supports as faithfully as possible frame relay services over an MPLS packet switched network (PSN). This document describes the detailed encapsulation necessary to transport frame relay packets over an MPLS network. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: L. Martini, C. Kawa, A. Malis |
| RFC4620 IPv6 Node Information Queries This document describes a protocol for asking an IPv6 node to supply certain network information, such as its hostname or fully-qualified domain name. IPv6 implementation experience has shown that direct queries for a hostname are useful, and a direct query mechanism for other information has been found useful in serverless environments and for debugging. This memo defines an Experimental Protocol for the Internet community. | August 2006 Status: EXPERIMENTAL Autor: M. Crawford, B. Haberman |
| RFC4621 Design of the IKEv2 Mobility and Multihoming (MOBIKE) Protocol The IKEv2 Mobility and Multihoming (MOBIKE) protocol is an extension of the Internet Key Exchange Protocol version 2 (IKEv2). These extensions should enable an efficient management of IKE and IPsec Security Associations when a host possesses multiple IP addresses and/or where IP addresses of an IPsec host change over time (for example, due to mobility). | August 2006 Status: INFORMATIONAL Autor: T. Kivinen, H. Tschofenig |
| RFC4622 Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP) This document defines the use of Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in identifying or interacting with entities that can communicate via the Extensible Messaging and Presence Protocol (XMPP). [STANDARDS-TRACK] | July 2006 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC4623 Pseudowire Emulation Edge-to-Edge (PWE3) Fragmentation and Reassembly This document defines a generalized method of performing fragmentation for use by Pseudowire Emulation Edge-to-Edge (PWE3) protocols and services. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: A. Malis, M. Townsley |
| RFC4624 Multicast Source Discovery Protocol (MSDP) MIB 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 managed objects used for managing Multicast Source Discovery Protocol (MSDP) (RFC 3618) speakers. This memo defines an Experimental Protocol for the Internet community. | October 2006 Status: EXPERIMENTAL Autor: B. Fenner, D. Thaler |
| RFC4625 Fibre Channel Routing Information 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 routing within a Fibre Channel fabric, which is independent of the usage of a particular routing protocol. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: C. DeSanti, K. McCloghrie, S. Kode, S. Gai |
| RFC4626 MIB for Fibre Channel's Fabric Shortest Path First (FSPF) 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 managed objects for information related to the Fibre Channel network's Fabric Shortest Path First (FSPF) routing protocol. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: C. DeSanti, V. Gaonkar, K. McCloghrie, S. Gai |
| RFC4627 The application/json Media Type for JavaScript Object Notation (JSON) JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This memo provides information for the Internet community. | July 2006 Status: INFORMATIONAL Autor: D. Crockford |
| RFC4628 RTP Payload Format for H.263 Moving RFC 2190 to Historic Status The first RFC that describes RTP payload format for ITU Telecommunication Standardization Sector (ITU-T) recommendation H.263 is RFC 2190. This specification discusses why to move RFC 2190 to historic status. This memo provides information for the Internet community. | January 2007 Status: INFORMATIONAL Autor: R. Even |
| RFC4629 RTP Payload Format for ITU-T Rec. H.263 Video This document describes a scheme to packetize an H.263 video stream for transport using the Real-time Transport Protocol (RTP) with any of the underlying protocols that carry RTP. | January 2007 Status: PROPOSED STANDARD Autor: J. Ott, C. Bormann, G. Sullivan, S. Wenger, R. Even |
| RFC4630 Update to DirectoryString Processing in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile This document updates the handling of DirectoryString in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, which is published in RFC 3280. The use of UTF8String and PrintableString are the preferred encoding. The requirement for exclusive use of UTF8String after December 31, 2003 is removed. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: R. Housley, S. Santesson |
| RFC4631 Link Management Protocol (LMP) Management Information Base (MIB) This document provides minor corrections to and obsoletes RFC 4327. | September 2006 Status: PROPOSED STANDARD Autor: M. Dubuc, T. Nadeau, J. Lang, E. McGinnis, A. Farrel |
| RFC4632 Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan This memo discusses the strategy for address assignment of the existing 32-bit IPv4 address space with a view toward conserving the address space and limiting the growth rate of global routing state. This document obsoletes the original Classless Inter-domain Routing (CIDR) spec in RFC 1519, with changes made both to clarify the concepts it introduced and, after more than twelve years, to update the Internet community on the results of deploying the technology described. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2006 Status: BEST CURRENT PRACTICE Autor: V. Fuller, T. Li |
| RFC4633 Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists Discussion in the community has begun to question whether RFC 3683 and RFC 3934 provide the appropriate flexibility for managing Internet Engineering Task Force (IETF) mailing lists. This document is an RFC 3933 experiment designed to allow the community to experiment with a broader set of tools for mailing list management while trying to determine what the long-term guidelines should be. This memo defines an Experimental Protocol for the Internet community. | August 2006 Status: EXPERIMENTAL Autor: S. Hartman |
| RFC4634 US Secure Hash Algorithms (SHA and HMAC-SHA) The United States of America has adopted a suite of Secure Hash Algorithms (SHAs), including four beyond SHA-1, as part of a Federal Information Processing Standard (FIPS), specifically SHA-224 (RFC 3874), SHA-256, SHA-384, and SHA-512. The purpose of this document is to make source code performing these hash functions conveniently available to the Internet community. The sample code supports input strings of arbitrary bit length. SHA-1's sample code from RFC 3174 has also been updated to handle input strings of arbitrary bit length. Most of the text herein was adapted by the authors from FIPS 180-2. | July 2006 Status: INFORMATIONAL Autor: D. Eastlake 3rd, T. Hansen |
| RFC4635 HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm Identifiers Use of the Domain Name System TSIG resource record requires specification of a cryptographic message authentication code. Currently, identifiers have been specified only for HMAC MD5 (Hashed Message Authentication Code, Message Digest 5) and GSS (Generic Security Service) TSIG algorithms. This document standardizes identifiers and implementation requirements for additional HMAC SHA (Secure Hash Algorithm) TSIG algorithms and standardizes how to specify and handle the truncation of HMAC values in TSIG. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC4636 Foreign Agent Error Extension for Mobile IPv4 This document specifies a new extension for use by Foreign Agents operating Mobile IP for IPv4. Currently, a foreign agent cannot supply status information without destroying the ability for a mobile node to verify authentication data supplied by the home agent. The new extension solves this problem by making a better place for the foreign agent to provide its status information to the mobile node. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC4638 Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE) The Point-to-Point Protocol over Ethernet (PPPoE), as described in RFC 2516, mandates a maximum negotiated Maximum Receive Unit (MRU) of 1492. This document outlines a solution that relaxes this restriction and allows a maximum negotiated MRU greater than 1492 to minimize fragmentation in next-generation broadband networks. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: P. Arberg, D. Kourkouzelis, M. Duckett, T. Anschutz, J. Moisand |
| RFC4639 Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems 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 Simple Network Management Protocol (SNMP)-based management of Data Over Cable Service Interface Specification (DOCSIS)-compliant Cable Modems and Cable Modem Termination Systems. | December 2006 Status: PROPOSED STANDARD Autor: R. Woundy, K. Marez |
| RFC4640 Problem Statement for bootstrapping Mobile IPv6 (MIPv6) A mobile node needs at least the following information: a home address, a home agent address, and a security association with home agent to register with the home agent. The process of obtaining this information is called bootstrapping. This document discusses issues involved with how the mobile node can be bootstrapped for Mobile IPv6 (MIPv6) and various potential deployment scenarios for mobile node bootstrapping. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: A. Patel, G. Giaretta |
| RFC4641 DNSSEC Operational Practices This document describes a set of practices for operating the DNS with security extensions (DNSSEC). The target audience is zone administrators deploying DNSSEC. | September 2006 Status: INFORMATIONAL Autor: O. Kolkman, R. Gieben |
| RFC4642 Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP) This memo defines an extension to the Network News Transfer Protocol (NNTP) that allows an NNTP client and server to use Transport Layer Security (TLS). The primary goal is to provide encryption for single-link confidentiality purposes, but data integrity, (optional) certificate-based peer entity authentication, and (optional) data compression are also possible. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: K. Murchison, J. Vinocur, C. Newman |
| RFC4643 Network News Transfer Protocol (NNTP) Extension for Authentication This document defines an extension to the Network News Transfer Protocol (NNTP) that allows a client to indicate an authentication mechanism to the server, to perform an authentication protocol exchange, and optionally to negotiate a security layer for subsequent protocol interactions during the remainder of an NNTP session. | October 2006 Status: PROPOSED STANDARD Autor: J. Vinocur, K. Murchison |
| RFC4644 Network News Transfer Protocol (NNTP) Extension for Streaming Feeds This memo defines an extension to the Network News Transfer Protocol (NNTP) to provide asynchronous (otherwise known as "streaming") transfer of articles. This allows servers to transfer articles to other servers with much greater efficiency. | October 2006 Status: PROPOSED STANDARD Autor: J. Vinocur, K. Murchison |
| RFC4645 Initial Language Subtag Registry This memo defined the initial contents of the IANA Language Subtag Registry for use in forming tags for the identification of languages. Since the contents of this memo only served as a starting point for the registry, its actual contents have been removed before publication to avoid confusion. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: D. Ewell |
| RFC4646 Tags for Identifying Languages This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document, in combination with RFC 4647, replaces RFC 3066, which replaced RFC 1766. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 2006 Status: BEST CURRENT PRACTICE Autor: A. Phillips, M. Davis |
| RFC4647 Matching of Language Tags This document describes a syntax, called a "language-range", for specifying items in a user's list of language preferences. It also describes different mechanisms for comparing and matching these to language tags. Two kinds of matching mechanisms, filtering and lookup, are defined. Filtering produces a (potentially empty) set of language tags, whereas lookup produces a single language tag. Possible applications include language negotiation or content selection. This document, in combination with RFC 4646, replaces RFC 3066, which replaced RFC 1766. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 2006 Status: BEST CURRENT PRACTICE Autor: A. Phillips, M. Davis |
| RFC4648 The Base16, Base32, and Base64 Data Encodings 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, use of different encoding alphabets, and canonical encodings. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: S. Josefsson |
| RFC4649 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option This memo defines a new Relay Agent Remote-ID option for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). This option is the DHCPv6 equivalent for the Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Relay Agent Option's Remote-ID suboption as specified in RFC 3046. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: B. Volz |
| RFC4650 HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY) This document describes a lightweight point-to-point key management protocol variant for the multimedia Internet keying (MIKEY) protocol MIKEY, as defined in RFC 3830. In particular, this variant deploys the classic Diffie-Hellman key agreement protocol for key establishment featuring perfect forward secrecy in conjunction with a keyed hash message authentication code for achieving mutual authentication and message integrity of the key management messages exchanged. This protocol addresses the security and performance constraints of multimedia key management in MIKEY. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: M. Euchner |
| RFC4651 A Taxonomy and Analysis of Enhancements to Mobile IPv6 Route Optimization This document describes and evaluates strategies to enhance Mobile IPv6 Route Optimization, on the basis of existing proposals, in order to motivate and guide further research in this context. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This memo provides information for the Internet community. | February 2007 Status: INFORMATIONAL Autor: C. Vogt, J. Arkko |
| RFC4652 Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing Requirements The Generalized MPLS (GMPLS) suite of protocols has been defined to control different switching technologies as well as different applications. These include support for requesting TDM connections including Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) and Optical Transport Networks (OTNs). | October 2006 Status: INFORMATIONAL Autor: D. Papadimitriou, L.Ong, J. Sadler, S. Shew, D. Ward |
| RFC4653 Improving the Robustness of TCP to Non-Congestion Events This document specifies Non-Congestion Robustness (NCR) for TCP. In the absence of explicit congestion notification from the network, TCP uses loss as an indication of congestion. One of the ways TCP detects loss is using the arrival of three duplicate acknowledgments. However, this heuristic is not always correct, notably in the case when network paths reorder segments (for whatever reason), resulting in degraded performance. TCP-NCR is designed to mitigate this degraded performance by increasing the number of duplicate acknowledgments required to trigger loss recovery, based on the current state of the connection, in an effort to better disambiguate true segment loss from segment reordering. This document specifies the changes to TCP, as well as the costs and benefits of these modifications. This memo defines an Experimental Protocol for the Internet community. | August 2006 Status: EXPERIMENTAL Autor: S. Bhandarkar, A. L. N. Reddy, M. Allman, E. Blanton |
| RFC4654 TCP-Friendly Multicast Congestion Control (TFMCC): Protocol Specification This document specifies TCP-Friendly Multicast Congestion Control (TFMCC). TFMCC is a congestion control mechanism for multicast transmissions in a best-effort Internet environment. It is a single-rate congestion control scheme, where the sending rate is adapted to the receiver experiencing the worst network conditions. TFMCC is reasonably fair when competing for bandwidth with TCP flows and has a relatively low variation of throughput over time, making it suitable for applications where a relatively smooth sending rate is of importance, such as streaming media. This memo defines an Experimental Protocol for the Internet community. | August 2006 Status: EXPERIMENTAL Autor: J. Widmer, M. Handley |
| RFC4655 A Path Computation Element (PCE)-Based Architecture Constraint-based path computation is a fundamental building block for traffic engineering systems such as Multiprotocol Label Switching (MPLS) and Generalized Multiprotocol Label Switching (GMPLS) networks. Path computation in large, multi-domain, multi-region, or multi-layer networks is complex and may require special computational components and cooperation between the different network domains. | August 2006 Status: INFORMATIONAL Autor: A. Farrel, J.-P. Vasseur, J. Ash |
| RFC4656 A One-way Active Measurement Protocol (OWAMP) The One-Way Active Measurement Protocol (OWAMP) measures unidirectional characteristics such as one-way delay and one-way loss. High-precision measurement of these one-way IP performance metrics became possible with wider availability of good time sources (such as GPS and CDMA). OWAMP enables the interoperability of these measurements. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: S. Shalunov, B. Teitelbaum, A. Karp, J. Boote, M. Zekauskas |
| RFC4657 Path Computation Element (PCE) Communication Protocol Generic Requirements The PCE model is described in the "PCE Architecture" document and facilitates path computation requests from Path Computation Clients (PCCs) to Path Computation Elements (PCEs). This document specifies generic requirements for a communication protocol between PCCs and PCEs, and also between PCEs where cooperation between PCEs is desirable. Subsequent documents will specify application-specific requirements for the PCE communication protocol. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: J. Ash, J.L. Le Roux |
| RFC4659 BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN This document describes a method by which a Service Provider may use its packet-switched backbone to provide Virtual Private Network (VPN) services for its IPv6 customers. This method reuses, and extends where necessary, the "BGP/MPLS IP VPN" method for support of IPv6. In BGP/MPLS IP VPN, "Multiprotocol BGP" is used for distributing IPv4 VPN routes over the service provider backbone, and MPLS is used to forward IPv4 VPN packets over the backbone. This document defines an IPv6 VPN address family and describes the corresponding IPv6 VPN route distribution in "Multiprotocol BGP". | September 2006 Status: PROPOSED STANDARD Autor: J. De Clercq, D. Ooms, M. Carugi, F. Le Faucheur |
| RFC4660 Functional Description of Event Notification Filtering The SIP event notification framework describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications of changes to the state of a resource. The document does not describe a mechanism whereby filtering of event notification information can be achieved. | September 2006 Status: PROPOSED STANDARD Autor: H. Khartabil, E. Leppanen, M. Lonnfors, J. Costa-Requena |
| RFC4661 An Extensible Markup Language (XML)-Based Format for Event Notification Filtering The SIP event notification framework describes the usage of the Session Initiation Protocol (SIP) for subscriptions and notifications of changes to a state of a resource. The document does not describe a mechanism whereby filtering of event notification information can be achieved. Filtering is a mechanism for defining the preferred notification information to be delivered and for specifying triggers that cause that information to be delivered. In order to enable this, a format is needed to enable the subscriber to describe the state changes of a resource that cause notifications to be sent to it and what those notifications are to contain. This document presents a format in the form of an XML document. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: H. Khartabil, E. Leppanen, M. Lonnfors, J. Costa-Requena |
| RFC4662 A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists This document presents an extension to the Session Initiation Protocol (SIP)-Specific Event Notification mechanism for subscribing to a homogeneous list of resources. Instead of sending a SUBSCRIBE for each resource individually, the subscriber can subscribe to an entire list and then receive notifications when the state of any of the resources in the list changes. [STANDARDS-TRACK] | August 2006 Status: PROPOSED STANDARD Autor: A. B. Roach, B. Campbell, J. Rosenberg |
| RFC4663 Transferring MIB Work from IETF Bridge MIB WG to IEEE 802.1 WG This document describes the plan to transition responsibility for bridging-related MIB modules from the IETF Bridge MIB Working Group to the IEEE 802.1 Working Group, which develops the bridging technology the MIB modules are designed to manage. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: D. Harrington |
| RFC4664 Framework for Layer 2 Virtual Private Networks (L2VPNs) This document provides a framework for Layer 2 Provider Provisioned Virtual Private Networks (L2VPNs). This framework is intended to aid in standardizing protocols and mechanisms to support interoperable L2VPNs. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: L. Andersson, E. Rosen |
| RFC4665 Service Requirements for Layer 2 Provider-Provisioned Virtual Private Networks This document provides requirements for Layer 2 Provider-Provisioned Virtual Private Networks (L2VPNs). It first provides taxonomy and terminology and states generic and general service requirements. It covers point-to-point VPNs, referred to as Virtual Private Wire Service (VPWS), as well as multipoint-to-multipoint VPNs, also known as Virtual Private LAN Service (VPLS). Detailed requirements are expressed from both a customer as well as a service provider perspectives. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: W. Augustyn, Y. Serbest |
| RFC4666 Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA) This memo defines a protocol for supporting the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services of the Stream Control Transmission Protocol. Also, provision is made for protocol elements that enable a seamless operation of the MTP3-User peers in the SS7 and IP domains. This protocol would be used between a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP-resident Database, or between two IP-based applications. It is assumed that the SG receives SS7 signalling over a standard SS7 interface using the SS7 Message Transfer Part (MTP) to provide transport. This document obsoletes RFC 3332. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: K. Morneault, J. Pastor-Balbas |
| RFC4667 Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP) The Layer 2 Tunneling Protocol (L2TP) provides a standard method for setting up and managing L2TP sessions to tunnel a variety of L2 protocols. One of the reference models supported by L2TP describes the use of an L2TP session to connect two Layer 2 circuits attached to a pair of peering L2TP Access Concentrators (LACs), which is a basic form of Layer 2 Virtual Private Network (L2VPN). This document defines the protocol extensions for L2TP to set up different types of L2VPNs in a unified fashion. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: W. Luo |
| RFC4668 RADIUS Authentication Client MIB for IPv6 This memo defines a set of extensions that instrument RADIUS authentication client functions. These extensions represent a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Using these extensions, IP-based management stations can manage RADIUS authentication clients. | August 2006 Status: PROPOSED STANDARD Autor: D. Nelson |
| RFC4669 RADIUS Authentication Server MIB for IPv6 This memo defines a set of extensions that instrument RADIUS authentication server functions. These extensions represent a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Using these extensions, IP-based management stations can manage RADIUS authentication servers. | August 2006 Status: PROPOSED STANDARD Autor: D. Nelson |
| RFC4670 RADIUS Accounting Client MIB for IPv6 This memo defines a set of extensions that instrument RADIUS accounting client functions. These extensions represent a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Using these extensions, IP-based management stations can manage RADIUS accounting clients. | August 2006 Status: INFORMATIONAL Autor: D. Nelson |
| RFC4671 RADIUS Accounting Server MIB for IPv6 This memo defines a set of extensions that instrument RADIUS accounting server functions. These extensions represent a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Using these extensions, IP-based management stations can manage RADIUS accounting servers. | August 2006 Status: INFORMATIONAL Autor: D. Nelson |
| RFC4672 RADIUS Dynamic Authorization Client 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 the Remote Authentication Dial-In User Service (RADIUS) (RFC2865) Dynamic Authorization Client (DAC) functions that support the dynamic authorization extensions as defined in RFC 3576. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: S. De Cnodder, N. Jonnala, M. Chiba |
| RFC4673 RADIUS Dynamic Authorization Server 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 the Remote Authentication Dial-In User Service (RADIUS) (RFC 2865) Dynamic Authorization Server (DAS) functions that support the dynamic authorization extensions as defined in RFC 3576. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: S. De Cnodder, N. Jonnala, M. Chiba |
| RFC4674 Requirements for Path Computation Element (PCE) Discovery This document presents a set of requirements for a Path Computation Element (PCE) discovery mechanism that would allow a Path Computation Client (PCC) to discover dynamically and automatically a set of PCEs along with certain information relevant for PCE selection. It is intended that solutions that specify procedures and protocols or extensions to existing protocols for such PCE discovery satisfy these requirements. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: J.L. Le Roux |
| RFC4675 RADIUS Attributes for Virtual LAN and Priority Support This document proposes additional Remote Authentication Dial-In User Service (RADIUS) attributes for dynamic Virtual LAN assignment and prioritization, for use in provisioning of access to IEEE 802 local area networks. These attributes are usable within either RADIUS or Diameter. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: P. Congdon, M. Sanchez, B. Aboba |
| RFC4676 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information This document specifies a Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) option containing the civic location of the client or the DHCP server. The Location Configuration Information (LCI) includes information about the country, administrative units such as states, provinces, and cities, as well as street addresses, postal community names, and building information. The option allows multiple renditions of the same address in different scripts and languages. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC4677 The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force This document describes the inner workings of IETF meetings and Working Groups, discusses organizations related to the IETF, and introduces the standards process. It is not a formal IETF process document but instead an informational overview. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: P. Hoffman, S. Harris |
| RFC4678 Server/Application State Protocol v1 Entities responsible for distributing work across a group of systems traditionally do not know a great deal about the ability of the applications on those systems to complete the work in a satisfactory fashion. Workload management systems traditionally know a great deal about the health of applications, but have little control over the rate in which these applications receive work. The Server/Application State Protocol (SASP) provides a mechanism for load balancers and workload management systems to communicate better ways of distributing the existing workload to the group members. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: A. Bivens |
| RFC4679 DSL Forum Vendor-Specific RADIUS Attributes This document describes the set of Remote Authentication Dial-In User Service Vendor-Specific Attributes (RADIUS VSAs) defined by the DSL Forum. | September 2006 Status: INFORMATIONAL Autor: V. Mammoliti, G. Zorn, P. Arberg, R. Rennison |
| RFC4680 TLS Handshake Message for Supplemental Data This specification defines a TLS handshake message for exchange of supplemental application data. TLS hello message extensions are used to determine which supplemental data types are supported by both the TLS client and the TLS server. Then, the supplemental data handshake message is used to exchange the data. Other documents will define the syntax of these extensions and the syntax of the associated supplemental data types. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: S. Santesson |
| RFC4681 TLS User Mapping Extension This document specifies a TLS extension that enables clients to send generic user mapping hints in a supplemental data handshake message defined in RFC 4680. One such mapping hint is defined in an informative section, the UpnDomainHint, which may be used by a server to locate a user in a directory database. Other mapping hints may be defined in other documents in the future. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: S. Santesson, A. Medvinsky, J. Ball |
| RFC4682 Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: E. Nechamkin, J-F. Mule |
| RFC4683 Internet X.509 Public Key Infrastructure Subject Identification Method (SIM) This document defines the Subject Identification Method (SIM) for including a privacy-sensitive identifier in the subjectAltName extension of a certificate. | October 2006 Status: PROPOSED STANDARD Autor: J. Park, J. Lee, H.. Lee, S. Park, T. Polk |
| RFC4684 Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs) This document defines Multi-Protocol BGP (MP-BGP) procedures that allow BGP speakers to exchange Route Target reachability information. This information can be used to build a route distribution graph in order to limit the propagation of Virtual Private Network (VPN) Network Layer Reachability Information (NLRI) between different autonomous systems or distinct clusters of the same autonomous system. This document updates RFC 4364. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: P. Marques, R. Bonica, L. Fang, L. Martini, R. Raszuk, K. Patel, J. Guichard |
| RFC4685 Atom Threading Extensions This memo presents a mechanism that allows feeds publishers to express threaded discussions within the Atom Syndication Format. [STANDARDS-TRACK] | September 2006 Status: PROPOSED STANDARD Autor: J. Snell |
| RFC4686 Analysis of Threats Motivating DomainKeys Identified Mail (DKIM) This document provides an analysis of some threats against Internet mail that are intended to be addressed by signature-based mail authentication, in particular DomainKeys Identified Mail. It discusses the nature and location of the bad actors, what their capabilities are, and what they intend to accomplish via their attacks. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: J. Fenton |
| RFC4687 Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS Networks Multi-Protocol Label Switching (MPLS) has been extended to encompass point-to-multipoint (P2MP) Label Switched Paths (LSPs). As with point-to-point MPLS LSPs, the requirement to detect, handle, and diagnose control and data plane defects is critical. | September 2006 Status: INFORMATIONAL Autor: S. Yasukawa, A. Farrel, D. King, T. Nadeau |
| RFC4688 A Uniform Resource Name (URN) Namespace for Aerospace and Defence Industries Association of Europe (ASD) Specification 1000D This document describes a Uniform Resource Name (URN) namespace for naming persistent resources defined by Aerospace and Defence Industries Association of Europe (ASD) Specification 1000D. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: S. Rushing |
| RFC4689 Terminology for Benchmarking Network-layer Traffic Control Mechanisms This document describes terminology for the benchmarking of devices that implement traffic control using packet classification based on defined criteria. The terminology is to be applied to measurements made on the data plane to evaluate IP traffic control mechanisms. Rules for packet classification can be based on any field in the IP header, such as the Differentiated Services Code Point (DSCP), or any field in the packet payload, such as port number. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: S. Poretsky, J. Perser, S. Erramilli, S. Khurana |
| RFC4690 Review and Recommendations for Internationalized Domain Names (IDNs) This note describes issues raised by the deployment and use of Internationalized Domain Names. It describes problems both at the time of registration and for use of those names in the DNS. It recommends that IETF should update the RFCs relating to IDNs and a framework to be followed in doing so, as well as summarizing and identifying some work that is required outside the IETF. In particular, it proposes that some changes be investigated for the Internationalizing Domain Names in Applications (IDNA) standard and its supporting tables, based on experience gained since those standards were completed. This memo provides information for the Internet community. | September 2006 Status: INFORMATIONAL Autor: J. Klensin, P. Faltstrom, C. Karp, IAB |
| RFC4691 Guidelines for Acting as an IETF Liaison to Another Organization Whenever the IETF decides to enter into a liaison relationship with another organization, such as a Standards Development Organization (SDO), a consortium, or an industrial forum, a liaison manager is appointed. The procedures used by the IAB to establish and maintain liaison relationships between the IETF and other organizations are described in RFC 4052. This document expands on the role of liaison managers and liaison representatives, giving guidelines on their mandate and the expectations, tasks, and responsibilities placed on them. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: L. Andersson |
| RFC4692 Considerations on the IPv6 Host Density Metric This memo provides an analysis of the Host Density metric as it is currently used to guide registry allocations of IPv6 unicast address blocks. This document contrasts the address efficiency as currently adopted in the allocation of IPv4 network addresses and that used by the IPv6 protocol. Note that for large allocations there are very significant variations in the target efficiency metric between the two approaches. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: G. Huston |
| RFC4693 IETF Operational Notes This document describes a new document series intended for use as a repository for IETF operations documents, which should be more ephemeral than RFCs, but more referenceable than Internet-Drafts, and with more clear handling procedures than a random Web page. | October 2006 Status: HISTORIC Autor: H. Alvestrand |
| RFC4694 Number Portability Parameters for the "tel" URI This document defines five parameters in the "tel" Uniform Resource Identifier (URI) to carry the number portability (NP)-related information. Those parameters can be passed to the next-hop network node after an NP database dip has been performed. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: J. Yu |
| RFC4695 RTP Payload Format for MIDI This memo describes a Real-time Transport Protocol (RTP) payload format for the MIDI (Musical Instrument Digital Interface) command language. The format encodes all commands that may legally appear on a MIDI 1.0 DIN cable. The format is suitable for interactive applications (such as network musical performance) and content-delivery applications (such as file streaming). The format may be used over unicast and multicast UDP and TCP, and it defines tools for graceful recovery from packet loss. Stream behavior, including the MIDI rendering method, may be customized during session setup. The format also serves as a mode for the mpeg4-generic format, to support the MPEG 4 Audio Object Types for General MIDI, Downloadable Sounds Level 2, and Structured Audio. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: J. Lazzaro, J. Wawrzynek |
| RFC4696 An Implementation Guide for RTP MIDI This memo offers non-normative implementation guidance for the Real-time Protocol (RTP) MIDI (Musical Instrument Digital Interface) payload format. The memo presents its advice in the context of a network musical performance application. In this application two musicians, located in different physical locations, interact over a network to perform as they would if located in the same room. Underlying the performances are RTP MIDI sessions over unicast UDP. Algorithms for sending and receiving recovery journals (the resiliency structure for the payload format) are described in detail. Although the memo focuses on network musical performance, the presented implementation advice is relevant to other RTP MIDI applications. [STANDARDS-TRACK] | November 2006 Status: INFORMATIONAL Autor: J. Lazzaro, J. Wawrzynek |
| RFC4697 Observed DNS Resolution Misbehavior This memo describes DNS iterative resolver behavior that results in a significant query volume sent to the root and top-level domain (TLD) name servers. We offer implementation advice to iterative resolver developers to alleviate these unnecessary queries. The recommendations made in this document are a direct byproduct of observation and analysis of abnormal query traffic patterns seen at two of the thirteen root name servers and all thirteen com/net TLD name servers. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 2006 Status: BEST CURRENT PRACTICE Autor: M. Larson, P. Barber |
| RFC4698 IRIS: An Address Registry (areg) Type for the Internet Registry Information Service This document describes an IRIS registry schema for IP address and Autonomous System Number 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 Internet Protocol address registries. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: E. Gunduz, A. Newton, S. Kerr |
| RFC4701 A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR) It is possible for Dynamic Host Configuration Protocol (DHCP) clients to attempt to update the same DNS Fully Qualified Domain Name (FQDN) or to update a DNS FQDN that has been added to the DNS for another purpose as they obtain DHCP leases. Whether the DHCP server or the clients themselves perform the DNS updates, conflicts can arise. To resolve such conflicts, RFC 4703 proposes storing client identifiers in the DNS to unambiguously associate domain names with the DHCP clients to which they refer. This memo defines a distinct Resource Record (RR) type for this purpose for use by DHCP clients and servers: the "DHCID" RR. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: M. Stapp, T. Lemon, A. Gustafsson |
| RFC4702 The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option This document describes a Dynamic Host Configuration Protocol for IPv4 (DHCPv4) option that can be used to exchange information about a DHCPv4 client's fully qualified domain name and about responsibility for updating the DNS RR related to the client's address assignment. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: M. Stapp, B. Volz, Y. Rekhter |
| RFC4703 Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients The Dynamic Host Configuration Protocol (DHCP) provides a mechanism for host configuration that includes dynamic assignment of IP addresses and fully qualified domain names. To maintain accurate name-to-IP-address and IP-address-to-name mappings in the DNS, these dynamically assigned addresses and fully qualified domain names (FQDNs) require updates to the DNS. This document identifies situations in which conflicts in the use of fully qualified domain names may arise among DHCP clients and servers, and it describes a strategy for the use of the DHCID DNS resource record (RR) in resolving those conflicts. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: M. Stapp, B. Volz |
| RFC4704 The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option This document specifies a new Dynamic Host Configuration Protocol for IPv6 (DHCPv6) option that can be used to exchange information about a DHCPv6 client's Fully Qualified Domain Name (FQDN) and about responsibility for updating DNS resource records (RRs) related to the client's address assignments. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: B. Volz |
| RFC4705 GigaBeam High-Speed Radio Link Encryption This document describes the encryption and key management used by GigaBeam as part of the WiFiber(tm) family of radio link products. The security solution is documented in the hope that other wireless product development efforts will include comparable capabilities. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: R. Housley, A. Corry |
| RFC4706 Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2) 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 parameters of the "Asymmetric Digital Subscriber Line" family of interface types: ADSL, ADSL2, ADSL2+, and their variants. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: M. Morgenstern, M. Dodge, S. Baillie, U. Bonollo |
| RFC4707 Netnews Administration System (NAS) The Netnews Administration System (NAS) is a framework to simplify the administration and usage of network news (also known as Netnews) on the Internet. Data for the administration of newsgroups and hierarchies are kept in a distributed hierarchical database and are available through a client-server protocol. | October 2006 Status: EXPERIMENTAL Autor: P. Grau, V. Heinau, H. Schlichting, R. Schuettler |
| RFC4708 CellML Media Type This document standardises a new media type -- application/cellml+xml -- for use in exchanging mathematical models represented in a CellML Umbrella 1.0 compliant markup language. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: A. Miller |
| RFC4709 Mounting Web Distributed Authoring and Versioning (WebDAV) Servers In current Web browsers, there is no uniform way to specify that a user clicking on a link will be presented with an editable view of a Web Distinguished Authoring and Versioning (WebDAV) server. For example, it is frequently desirable to be able to click on a link and have this link open a window that can handle drag-and-drop interaction with the resources of a WebDAV server. | October 2006 Status: INFORMATIONAL Autor: J. Reschke |
| RFC4710 Real-time Application Quality-of-Service Monitoring (RAQMON) Framework There is a need to monitor end-devices such as IP phones, pagers, Instant Messaging clients, mobile phones, and various other handheld computing devices. This memo extends the remote network monitoring (RMON) family of specifications to allow real-time quality-of-service (QoS) monitoring of various applications that run on these devices and allows this information to be integrated with the RMON family using the Simple Network Management Protocol (SNMP). This memo defines the framework, architecture, relevant metrics, and transport requirements for real-time QoS monitoring of applications. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: A. Siddiqui, D. Romascanu, E. Golovinsky |
| RFC4711 Real-time Application Quality-of-Service Monitoring (RAQMON) MIB 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, RFC 2819. In particular, it describes managed objects used for real-time application Quality of Service (QoS) monitoring. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: A. Siddiqui, D. Romascanu, E. Golovinsky |
| RFC4712 Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU) This memo specifies two transport mappings of the \%Real-Time Application Quality-of-Service Monitoring (RAQMON) information model defined in RFC 4710 using TCP as a native transport and the Simple Network Management Protocol (SNMP) to carry the RAQMON information from a RAQMON Data Source (RDS) to a RAQMON Report Collector (RRC). [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: A. Siddiqui, D. Romascanu, E. Golovinsky, M. Rahman,Y. Kim |
| RFC4713 Registration and Administration Recommendations for Chinese Domain Names Many Chinese characters in common use have variants, which makes most of the Chinese Domain Names (CDNs) have at least two different forms. The equivalence between Simplified Chinese (SC) and Traditional Chinese (TC) characters is very important for CDN registration. This memo builds on the basic concepts, general guidelines, and framework of RFC 3743 to specify proposed registration and administration procedures for Chinese domain names. The document provides the information needed for understanding and using the tables defined in the IANA table registrations for Simplified and Traditional Chinese. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: X. Lee, W. Mao, E. Chen, N. Hsu, J. Klensin |
| RFC4714 Requirements for IETF Technical Publication Service The work of the IETF is to discuss, develop, and disseminate technical specifications to support the Internet's operation. Technical publication is the process by which that output is disseminated to the community at large. As such, it is important to understand the requirements on the publication process. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: A. Mankin, S. Hayes |
| RFC4715 The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI Without a tel URI parameter to carry an encoding type of Integrated Services Digital Network (ISDN) subaddress, interworking between ISDN User Part (ISUP) network and a Session Initiation Protocol (SIP) network is impossible in some cases. To solve this problem, this document specifies a new optional tel URI parameter to carry the encoding type of ISDN subaddress. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: M. Munakata, S. Schubert, T. Ohba |
| RFC4716 The Secure Shell (SSH) Public Key File Format This document formally documents an existing public key file format in use for exchanging public keys between different Secure Shell (SSH) implementations. | November 2006 Status: INFORMATIONAL Autor: J. Galbraith, R. Thayer |
| RFC4717 Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks An Asynchronous Transfer Mode (ATM) Pseudowire (PW) is used to carry ATM cells over an MPLS network. This enables service providers to offer "emulated" ATM services over existing MPLS networks. This document specifies methods for the encapsulation of ATM cells within a pseudowire. It also specifies the procedures for using a PW to provide an ATM service. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: L. Martini, J. Jayakumar, M. Bocci, N. El-Aawar, J. Brayley, G. Koleyni |
| RFC4718 IKEv2 Clarifications and Implementation Guidelines This document clarifies many areas of the IKEv2 specification. It does not to introduce any changes to the protocol, but rather provides descriptions that are less prone to ambiguous interpretations. The purpose of this document is to encourage the development of interoperable implementations. This memo provides information for the Internet community. | October 2006 Status: INFORMATIONAL Autor: P. Eronen, P. Hoffman |
| RFC4719 Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3) This document describes the transport of Ethernet frames over the Layer 2 Tunneling Protocol, Version 3 (L2TPv3). This includes the transport of Ethernet port-to-port frames as well as the transport of Ethernet VLAN frames. The mechanism described in this document can be used in the creation of Pseudowires to transport Ethernet frames over an IP network. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: R. Aggarwal, M. Townsley, M. Dos Santos |
| RFC4720 Pseudowire Emulation Edge-to-Edge (PWE3) Frame Check Sequence Retention This document defines a mechanism for preserving Frame Check Sequence (FCS) through Ethernet, Frame Relay, High-Level Data Link Control (HDLC), and PPP pseudowires. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: A. Malis, D. Allan, N. Del Regno |
| RFC4721 Mobile IPv4 Challenge/Response Extensions (Revised) Mobile IP, as originally specified, defines an authentication extension (the Mobile-Foreign Authentication extension) by which a mobile node can authenticate itself to a foreign agent. Unfortunately, that extension does not provide the foreign agent any direct guarantee that the protocol is protected from replays and does not allow for the use of existing techniques (such as Challenge Handshake Authentication Protocol (CHAP)) for authenticating portable computer devices. | January 2007 Status: PROPOSED STANDARD Autor: C. Perkins, P. Calhoun, J. Bharatia |
| RFC4722 Media Server Control Markup Language (MSCML) and Protocol Media Server Control Markup Language (MSCML) is a markup language used in conjunction with SIP to provide advanced conferencing and interactive voice response (IVR) functions. MSCML presents an application-level control model, as opposed to device-level control models. One use of this protocol is for communications between a conference focus and mixer in the IETF SIP Conferencing Framework. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: J. Van Dyke, E. Burger, A. Spitzer |
| RFC4723 Registration of Media Type audio/mobile-xmf The MIDI Manufacturers Association (MMA) and the Association of Musical Electronics Industry (AMEI) have produced the Mobile XMF standard, which was developed particularly for mobile MIDI applications. Mobile XMF is a very compact media type providing high-quality synthetic audio content for music downloading and messaging applications that require MIME registration. This document registers the media type audio/mobile-xmf. This memo provides information for the Internet community. | December 2006 Status: INFORMATIONAL Autor: T. Kosonen, T. White |
| RFC4724 Graceful Restart Mechanism for BGP This document describes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. An End-of-RIB marker is specified and can be used to convey routing convergence information. A new BGP capability, termed "Graceful Restart Capability", is defined that would allow a BGP speaker to express its ability to preserve forwarding state during BGP restart. Finally, procedures are outlined for temporarily retaining routing information across a TCP session termination/re-establishment. | January 2007 Status: PROPOSED STANDARD Autor: S. Sangli, E. Chen, R. Fernando, J. Scudder, Y. Rekhter |
| RFC4725 ENUM Validation Architecture An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether or not the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes validation requirements and a high-level architecture for an ENUM validation infrastructure. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: A. Mayrhofer, B. Hoeneisen |
| RFC4726 A Framework for Inter-Domain Multiprotocol Label Switching Traffic Engineering This document provides a framework for establishing and controlling Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) Label Switched Paths (LSPs) in multi-domain networks. | November 2006 Status: INFORMATIONAL Autor: A. Farrel, J.-P. Vasseur, A. Ayyangar |
| RFC4727 Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers 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. This document reserves some ranges of numbers for experimentation purposes in specific protocols where the need to support experimentation has been identified, and it describes the numbers that have already been reserved by other documents. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: B. Fenner |
| RFC4728 The Dynamic Source Routing Protocol (DSR) for Mobile Ad Hoc Networks for IPv4 The Dynamic Source Routing protocol (DSR) is a simple and efficient routing protocol designed specifically for use in multi-hop wireless ad hoc networks of mobile nodes. DSR allows the network to be completely self-organizing and self-configuring, without the need for any existing network infrastructure or administration. The protocol is composed of the two main mechanisms of "Route Discovery" and "Route Maintenance", which work together to allow nodes to discover and maintain routes to arbitrary destinations in the ad hoc network. All aspects of the protocol operate entirely on demand, allowing the routing packet overhead of DSR to scale automatically to only what is needed to react to changes in the routes currently in use. The protocol allows multiple routes to any destination and allows each sender to select and control the routes used in routing its packets, for example, for use in load balancing or for increased robustness. Other advantages of the DSR protocol include easily guaranteed loop-free routing, operation in networks containing unidirectional links, use of only "soft state" in routing, and very rapid recovery when routes in the network change. The DSR protocol is designed mainly for mobile ad hoc networks of up to about two hundred nodes and is designed to work well even with very high rates of mobility. This document specifies the operation of the DSR protocol for routing unicast IPv4 packets. This memo defines an Experimental Protocol for the Internet community. | February 2007 Status: EXPERIMENTAL Autor: D. Johnson, Y. Hu, D. Maltz |
| RFC4729 A Uniform Resource Name (URN) Namespace for the Near Field Communication (NFC) Forum This document describes the Namespace Identifier (NID) for Uniform Resource Name (URN) resources published by the Near Field Communication (NFC) Forum. The NFC Forum defines and manages resources that utilize this URN identification model. Management activities for these and other resource types are provided by the NFC Forum Technical Committee. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: M. Abel |
| RFC4730 A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML) This document describes a SIP Event Package "kpml" that enables monitoring of Dual Tone Multi-Frequency (DTMF) signals and uses Extensible Markup Language (XML) documents referred to as Key Press Markup Language (KPML). The kpml Event Package may be used to support applications consistent with the principles defined in the document titled "A Framework for Application Interaction in the Session Initiation Protocol (SIP)". The event package uses SUBSCRIBE messages and allows for XML documents that define and describe filter specifications for capturing key presses (DTMF Tones) entered at a presentation-free User Interface SIP User Agent (UA). The event package uses NOTIFY messages and allows for XML documents to report the captured key presses (DTMF tones), consistent with the filter specifications, to an Application Server. The scope of this package is for collecting supplemental key presses or mid-call key presses (triggers). [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: E. Burger, M. Dolly |
| RFC4731 IMAP4 Extension to SEARCH Command for Controlling What Kind of Information Is Returned This document extends IMAP (RFC 3501) SEARCH and UID SEARCH commands with several result options, which can control what kind of information is returned. The following result options are defined: minimal value, maximal value, all found messages, and number of found messages. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: A. Melnikov, D. Cridland |
| RFC4732 Internet Denial-of-Service Considerations This document provides an overview of possible avenues for denial-of-service (DoS) attack on Internet systems. The aim is to encourage protocol designers and network engineers towards designs that are more robust. We discuss partial solutions that reduce the effectiveness of attacks, and how some solutions might inadvertently open up alternative vulnerabilities. This memo provides information for the Internet community. | December 2006 Status: INFORMATIONAL Autor: M. Handley, E. Rescorla, IAB |
| RFC4733 RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals This memo describes how to carry dual-tone multifrequency (DTMF) signalling, other tone signals, and telephony events in RTP packets. It obsoletes RFC 2833. | December 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne, T. Taylor |
| RFC4734 Definition of Events for Modem, Fax, and Text Telephony Signals This memo updates RFC 4733 to add event codes for modem, fax, and text telephony signals when carried in the telephony event RTP payload. It supersedes the assignment of event codes for this purpose in RFC 2833, and therefore obsoletes that part of RFC 2833. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne, T. Taylor |
| RFC4735 Example Media Types for Use in Documentation This document is registration for the 'example' media type and 'example' subtypes within the standards tree. The 'example/*' and '*/example' media types are defined for documentation purposes only. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: T. Taylor |
| RFC4736 Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP) This document defines a mechanism for the reoptimization of loosely routed MPLS and GMPLS (Generalized Multiprotocol Label Switching) Traffic Engineering (TE) Label Switched Paths (LSPs) signaled with Resource Reservation Protocol Traffic Engineering (RSVP-TE). This document proposes a mechanism that allows a TE LSP head-end Label Switching Router (LSR) to trigger a new path re-evaluation on every hop that has a next hop defined as a loose or abstract hop and a mid-point LSR to signal to the head-end LSR that a better path exists (compared to the current path) or that the TE LSP must be reoptimized (because of maintenance required on the TE LSP path). The proposed mechanism applies to the cases of intra- and inter-domain (Interior Gateway Protocol area (IGP area) or Autonomous System) packet and non-packet TE LSPs following a loosely routed path. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: JP. Vasseur, Y. Ikejiri, R. Zhang |
| RFC4737 Packet Reordering Metrics This memo defines metrics to evaluate whether a network has maintained packet order on a packet-by-packet basis. It provides motivations for the new metrics and discusses the measurement issues, including the context information required for all metrics. The memo first defines a reordered singleton, and then uses it as the basis for sample metrics to quantify the extent of reordering in several useful dimensions for network characterization or receiver design. Additional metrics quantify the frequency of reordering and the distance between separate occurrences. We then define a metric oriented toward assessment of reordering effects on TCP. Several examples of evaluation using the various sample metrics are included. An appendix gives extended definitions for evaluating order with packet fragmentation. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: A. Morton, L. Ciavattone, G. Ramachandran, S. Shalunov, J. Perser |
| RFC4738 MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY) The Multimedia Internet Keying (MIKEY) specification describes several modes of key distribution solution that address multimedia scenarios (e.g., SIP calls and Real Time Streaming Protocol (RTSP) sessions) using pre-shared keys, public keys, and optionally a Diffie-Hellman key exchange. In the public-key mode, the Initiator encrypts a random key with the Responder's public key and sends it to the Responder. In many communication scenarios, the Initiator may not know the Responder's public key, or in some cases the Responder's ID (e.g., call forwarding) in advance. We propose a new MIKEY mode that works well in such scenarios. This mode also enhances the group key management support in MIKEY; it supports member-initiated group key download (in contrast to group manager pushing the group keys to all members). This document updates RFC 3830 with the RSA-R mode. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: D. Ignjatic, L. Dondeti, F. Audet, P. Lin |
| RFC4739 Multiple Authentication Exchanges in the Internet Key Exchange (IKEv2) Protocol The Internet Key Exchange (IKEv2) protocol supports several mechanisms for authenticating the parties, including signatures with public-key certificates, shared secrets, and Extensible Authentication Protocol (EAP) methods. Currently, each endpoint uses only one of these mechanisms to authenticate itself. This document specifies an extension to IKEv2 that allows the use of multiple authentication exchanges, using either different mechanisms or the same mechanism. This extension allows, for instance, performing certificate-based authentication of the client host followed by an EAP authentication of the user. When backend authentication servers are used, they can belong to different administrative domains, such as the network access provider and the service provider. This memo defines an Experimental Protocol for the Internet community. | November 2006 Status: EXPERIMENTAL Autor: P. Eronen, J. Korhonen |
| RFC4740 Diameter Session Initiation Protocol (SIP) Application This document specifies the Diameter Session Initiation Protocol (SIP) application. This is a Diameter application that allows a Diameter client to request authentication and authorization information. This application is designed to be used in conjunction with SIP and provides a Diameter client co-located with a SIP server, with the ability to request the authentication of users and authorization of SIP resources usage from a Diameter server. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: M. Garcia-Martin, M. Belinchon, M. Pallares-Lopez, C. Canales-Valenzuela, K. Tammi |
| RFC4741 NETCONF Configuration Protocol The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized on top of a simple Remote Procedure Call (RPC) layer. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: R. Enns |
| RFC4742 Using the NETCONF Configuration Protocol over Secure SHell (SSH) This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: M. Wasserman, T. Goddard |
| RFC4743 Using NETCONF over the Simple Object Access Protocol (SOAP) The Network Configuration Protocol (NETCONF) is applicable to a wide range of devices in a variety of environments. Web Services is one such environment and is presently characterized by the use of the Simple Object Access Protocol (SOAP). NETCONF finds many benefits in this environment: from the reuse of existing standards, to ease of software development, to integration with deployed systems. Herein, we describe SOAP over HTTP and SOAP over Blocks Exchange Extensible Protocol (BEEP) bindings for NETCONF. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: T. Goddard |
| RFC4744 Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) This document specifies an application protocol mapping for the Network Configuration Protocol (NETCONF) over the Blocks Extensible Exchange Protocol (BEEP). [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: E. Lear, K. Crozier |
| RFC4745 Common Policy: A Document Format for Expressing Privacy Preferences This document defines a framework for authorization policies controlling access to application-specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: H. Schulzrinne, H. Tschofenig, J. Morris, J. Cuellar, J. Polk, J. Rosenberg |
| RFC4746 Extensible Authentication Protocol (EAP) Password Authenticated Exchange This document defines an Extensible Authentication Protocol (EAP) method called EAP-PAX (Password Authenticated eXchange). This method is a lightweight shared-key authentication protocol with optional support for key provisioning, key management, identity protection, and authenticated data exchange. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: T. Clancy, W. Arbaugh |
| RFC4747 The Virtual Fabrics 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 network's Virtual Fabrics function. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: S. Kipp, G. Ramkumar, K. McCloghrie |
| RFC4748 RFC 3978 Update to Recognize the IETF Trust This document updates RFC 3978 "IETF Rights in Contributions" to recognize that the IETF Trust is now the proper custodian of all IETF-related intellectual property rights. | October 2006 Status: BEST CURRENT PRACTICE Autor: S. Bradner |
| RFC4749 RTP Payload Format for the G.729.1 Audio Codec This document specifies a Real-time Transport Protocol (RTP) payload format to be used for the International Telecommunication Union (ITU-T) G.729.1 audio codec. A media type registration is included for this payload format. [STANDARDS-TRACK] | October 2006 Status: PROPOSED STANDARD Autor: A. Sollaud |
| RFC4750 OSPF Version 2 Management Information Base This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing version 2 of the Open Shortest Path First Routing Protocol. Version 2 of the OSPF protocol is specific to the IPv4 address family. Version 3 of the OSPF protocol is specific to the IPv6 address family. | December 2006 Status: PROPOSED STANDARD Autor: D. Joyal, P. Galecki, S. Giacalone, R. Coltun, F. Baker |
| RFC4752 The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) Mechanism The Simple Authentication and Security Layer (SASL) is a framework for adding authentication support to connection-based protocols. This document describes the method for using the Generic Security Service Application Program Interface (GSS-API) Kerberos V5 in the SASL. | November 2006 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC4753 ECP Groups For IKE and IKEv2 This document describes new Elliptic Curve Cryptography (ECC) groups for use in the Internet Key Exchange (IKE) and Internet Key Exchange version 2 (IKEv2) protocols in addition to previously defined groups. Specifically, the new curve groups are based on modular arithmetic rather than binary arithmetic. These new groups are defined to align IKE and IKEv2 with other ECC implementations and standards, particularly NIST standards. In addition, the curves defined here can provide more efficient implementation than previously defined ECC groups. This memo provides information for the Internet community. | January 2007 Status: INFORMATIONAL Autor: D. Fu, J. Solinas |
| RFC4754 IKE and IKEv2 Authentication Using the Elliptic Curve Digital Signature Algorithm (ECDSA) This document describes how the Elliptic Curve Digital Signature Algorithm (ECDSA) may be used as the authentication method within the Internet Key Exchange (IKE) and Internet Key Exchange version 2 (IKEv2) protocols. ECDSA may provide benefits including computational efficiency, small signature sizes, and minimal bandwidth compared to other available digital signature methods. This document adds ECDSA capability to IKE and IKEv2 without introducing any changes to existing IKE operation. [STANDARDS-TRACK] | January 2007 Status: PROPOSED STANDARD Autor: D. Fu, J. Solinas |
| RFC4755 IP over InfiniBand: Connected Mode This document specifies transmission of IPv4/IPv6 packets and address resolution over the connected modes of InfiniBand. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: V. Kashyap |
| RFC4756 Forward Error Correction Grouping Semantics in Session Description Protocol This document defines the semantics that allow for grouping of Forward Error Correction (FEC) streams with the protected payload streams in Session Description Protocol (SDP). The semantics defined in this document are to be used with "Grouping of Media Lines in the Session Description Protocol" (RFC 3388) to group together "m" lines in the same session. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: A. Li |
| RFC4757 The RC4-HMAC Kerberos Encryption Types Used by Microsoft Windows The Microsoft Windows 2000 implementation of Kerberos introduces a new encryption type based on the RC4 encryption algorithm and using an MD5 HMAC for checksum. This is offered as an alternative to using the existing DES-based encryption types. | December 2006 Status: INFORMATIONAL Autor: K. Jaganathan, L. Zhu, J. Brezak |
| RFC4758 Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 Revision 1 This document constitutes Revision 1 of Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 from RSA Laboratories' One-Time Password Specifications (OTPS) series. The body of this document, except for the intellectual property considerations section, is taken from the CT-KIP Version 1.0 document, but comments received during the IETF review are reflected; hence, the status of a revised version. As no "bits-on-the-wire" have changed, the protocol specified herein is compatible with CT-KIP Version 1.0. | November 2006 Status: INFORMATIONAL Autor: M. Nystroem |
| RFC4759 The ENUM Dip Indicator Parameter for the "tel" URI This document defines a new parameter "enumdi" for the "tel" Uniform Resource Identifier (URI) to support the handling of ENUM queries in Voice over Internet Protocol (VoIP) network elements. A VoIP network element may receive a URI containing an E.164 number, where that URI contains an "enumdi" parameter. The presence of the "enumdi" parameter indicates that an ENUM query has already been performed on the E.164 number by a previous VoIP network element. Equally, if a VoIP network element sends such a URI, it asserts that an ENUM query has been carried out on this number. [STANDARDS-TRACK] | December 2006 Status: PROPOSED STANDARD Autor: R. Stastny, R. Shockey, L. Conroy |
| RFC4760 Multiprotocol Extensions for BGP-4 This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, L3VPN, 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] | January 2007 Status: DRAFT STANDARD Autor: T. Bates, R. Chandra, D. Katz, Y. Rekhter |
| RFC4761 Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature. | January 2007 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter |
| RFC4762 Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling This document describes a Virtual Private LAN Service (VPLS) solution using pseudowires, a service previously implemented over other tunneling technologies and known as Transparent LAN Services (TLS). A VPLS creates an emulated LAN segment for a given set of users; i.e., it creates a Layer 2 broadcast domain that is fully capable of learning and forwarding on Ethernet MAC addresses and that is closed to a given set of users. Multiple VPLS services can be supported from a single Provider Edge (PE) node. | January 2007 Status: PROPOSED STANDARD Autor: M. Lasserre, V. Kompella |
| RFC4763 Extensible Authentication Protocol Method for Shared-secret Authentication and Key Establishment (EAP-SAKE) This document specifies an Extensible Authentication Protocol (EAP) mechanism for Shared-secret Authentication and Key Establishment (SAKE). This RFC is published as documentation for the IANA assignment of an EAP Type for a vendor's EAP method per RFC 3748. The specification has passed Designated Expert review for this IANA assignment. This memo provides information for the Internet community. | November 2006 Status: INFORMATIONAL Autor: M. Vanderveen, H. Soliman |
| RFC4764 The EAP-PSK Protocol: A Pre-Shared Key Extensible Authentication Protocol (EAP) Method This document specifies EAP-PSK, an Extensible Authentication Protocol (EAP) method for mutual authentication and session key derivation using a Pre-Shared Key (PSK). EAP-PSK provides a protected communication channel when mutual authentication is successful for both parties to communicate over. This document describes the use of this channel only for protected exchange of result indications, but future EAP-PSK extensions may use the channel for other purposes. EAP-PSK is designed for authentication over insecure networks such as IEEE 802.11. This memo defines an Experimental Protocol for the Internet community. | January 2007 Status: EXPERIMENTAL Autor: F. Bersani, H. Tschofenig |
| RFC4765 The Intrusion Detection Message Exchange Format (IDMEF) The purpose of the Intrusion Detection Message Exchange Format (IDMEF) is to define data formats and exchange procedures for sharing information of interest to intrusion detection and response systems and to the management systems that may need to interact with them. | March 2007 Status: EXPERIMENTAL Autor: H. Debar, D. Curry, B. Feinstein |
| RFC4766 Intrusion Detection Message Exchange Requirements The purpose of the Intrusion Detection Exchange Format Working Group (IDWG) is to define data formats and exchange procedures for sharing information of interest to intrusion detection and response systems and to the management systems that may need to interact with them. This document describes the high-level requirements for such a communication mechanism, including the rationale for those requirements where clarification is needed. Scenarios are used to illustrate some requirements. This memo provides information for the Internet community. | March 2007 Status: INFORMATIONAL Autor: M. Wood, M. Erlinger |
| RFC4767 The Intrusion Detection Exchange Protocol (IDXP) This memo describes the Intrusion Detection Exchange Protocol (IDXP), an application-level protocol for exchanging data between intrusion detection entities. IDXP supports mutual-authentication, integrity, and confidentiality over a connection-oriented protocol. The protocol provides for the exchange of IDMEF messages, unstructured text, and binary data. The IDMEF message elements are described in RFC 4765, "The Intrusion Detection Message Exchange Format (IDMEF)", a companion document of the Intrusion Detection Exchange Format Working Group (IDWG) of the IETF. This memo defines an Experimental Protocol for the Internet community. | March 2007 Status: EXPERIMENTAL Autor: B. Feinstein, G. Matthews |
| RFC4768 Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming The Generic Security Services API (GSS-API) provides a naming architecture that supports name-based authorization. GSS-API authenticates two named parties to each other. Names can be stored on access control lists (ACLs) to make authorization decisions. Advances in security mechanisms and the way implementers wish to use GSS-API require this model to be extended for the next version of GSS-API. As people move within an organization or change their names, the name authenticated by GSS-API may change. Using some sort of constant identifier would make ACLs more stable. Some mechanisms, such as public-key mechanisms, do not have a single name to be used across all environments. Other mechanisms, such as Kerberos, may include group membership or role information as part of authentication. This document motivates extensions to GSS-API naming and describes the extensions under discussion. This memo provides information for the Internet community. | December 2006 Status: INFORMATIONAL Autor: S. Hartman |
| RFC4769 IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information This document registers the Enumservice type "pstn" and subtype "tel" using the URI scheme 'tel', as well as the subtype "sip" using the URI scheme 'sip' as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice is used to facilitate the routing of telephone calls in those countries where number portability exists. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: J. Livingood, R. Shockey |
| RFC4770 vCard Extensions for Instant Messaging (IM) This document describes an extension to vCard to support Instant Messaging (IM) and Presence Protocol (PP) applications. IM and PP are becoming increasingly common ways of communicating, and users want to save this contact information in their address books. It allows a URI that is associated with IM or PP to be specified inside a vCard. [STANDARDS-TRACK] | January 2007 Status: PROPOSED STANDARD Autor: C. Jennings, J. Reschke |
| RFC4771 Integrity Transform Carrying Roll-Over Counter for the Secure Real-time Transport Protocol (SRTP) This document defines an integrity transform for Secure Real-time Transport Protocol (SRTP; see RFC 3711), which allows the roll-over counter (ROC) to be transmitted in SRTP packets as part of the authentication tag. The need for sending the ROC in SRTP packets arises in situations where the receiver joins an ongoing SRTP session and needs to quickly and robustly synchronize. The mechanism also enhances SRTP operation in cases where there is a risk of losing sender-receiver synchronization. [STANDARDS-TRACK] | January 2007 Status: PROPOSED STANDARD Autor: V. Lehtovirta, M. Naslund, K. Norrman |
| RFC4772 Security Implications of Using the Data Encryption Standard (DES) The Data Encryption Standard (DES) is susceptible to brute-force attacks, which are well within the reach of a modestly financed adversary. As a result, DES has been deprecated, and replaced by the Advanced Encryption Standard (AES). Nonetheless, many applications continue to rely on DES for security, and designers and implementers continue to support it in new applications. While this is not always inappropriate, it frequently is. This note discusses DES security implications in detail, so that designers and implementers have all the information they need to make judicious decisions regarding its use. This memo provides information for the Internet community. | December 2006 Status: INFORMATIONAL Autor: S. Kelly |
| RFC4773 Administration of the IANA Special Purpose IPv6 Address Block This is a direction to IANA concerning the management of the IANA Special Purpose IPv6 address assignment registry. This memo provides information for the Internet community. | December 2006 Status: INFORMATIONAL Autor: G. Huston |
| RFC4774 Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field There have been a number of proposals for alternate semantics for the Explicit Congestion Notification (ECN) field in the IP header RFC 3168. This document discusses some of the issues in defining alternate semantics for the ECN field, and specifies requirements for a safe coexistence in an Internet that could include routers that do not understand the defined alternate semantics. This document evolved as a result of discussions with the authors of one recent proposal for such alternate semantics. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | November 2006 Status: BEST CURRENT PRACTICE Autor: S. Floyd |
| RFC4775 Procedures for Protocol Extensions and Variations This document discusses procedural issues related to the extensibility of IETF protocols, including when it is reasonable to extend IETF protocols with little or no review, and when extensions or variations need to be reviewed by the IETF community. Experience has shown that extension of protocols without early IETF review can carry risk. The document also recommends that major extensions to or variations of IETF protocols only take place through normal IETF processes or in coordination with the IETF. | December 2006 Status: BEST CURRENT PRACTICE Autor: S. Bradner, B. Carpenter, T. Narten |
| RFC4776 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information This document specifies a Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) option containing the civic location of the client or the DHCP server. The Location Configuration Information (LCI) includes information about the country, administrative units such as states, provinces, and cities, as well as street addresses, postal community names, and building information. The option allows multiple renditions of the same address in different scripts and languages. [STANDARDS-TRACK] | November 2006 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC4777 IBM's iSeries Telnet Enhancements This document describes the interface to the Telnet server on IBM's iSeries line of midrange business computers. This interface allows Telnet clients to request a Telnet terminal or printer session using specific session attributes related to device names, encryption, language support, auto-sign-on, response codes, session association, etc. | November 2006 Status: INFORMATIONAL Autor: T. Murphy Jr., P. Rieth, J. Stevens |
| RFC4778 Operational Security Current Practices in Internet Service Provider Environments This document is a survey of the current practices used in today's large ISP operational networks to secure layer 2 and layer 3 infrastructure devices. The information listed here is the result of information gathered from people directly responsible for defining and implementing secure infrastructures in Internet Service Provider environments. This memo provides information for the Internet community. | January 2007 Status: INFORMATIONAL Autor: M. Kaeo |
| RFC4779 ISP IPv6 Deployment Scenarios in Broadband Access Networks This document provides a detailed description of IPv6 deployment and integration methods and scenarios in today\'s Service Provider (SP) Broadband (BB) networks in coexistence with deployed IPv4 services. Cable/HFC, BB Ethernet, xDSL, and WLAN are the main BB technologies that are currently deployed, and discussed in this document. The emerging Broadband Power Line Communications (PLC/BPL) access technology is also discussed for completeness. In this document we will discuss main components of IPv6 BB networks, their differences from IPv4 BB networks, and how IPv6 is deployed and integrated in each of these networks using tunneling mechanisms and native IPv6. This memo provides information for the Internet community. | January 2007 Status: INFORMATIONAL Autor: S. Asadullah, A. Ahmed, C. Popoviciu, P. Savola, J. Palet |
| RFC4780 Management Information Base for the Session Initiation Protocol (SIP) 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 manage Session Initiation Protocol (SIP) entities, which include User Agents, and Proxy, Redirect and Registrar servers. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: K. Lingle, J-F. Mule, J. Maeng, D. Walker |
| RFC4781 Graceful Restart Mechanism for BGP with MPLS A mechanism for BGP that helps minimize the negative effects on routing caused by BGP restart has already been developed and is described in a separate document ("Graceful Restart Mechanism for BGP"). This document extends this mechanism to minimize the negative effects on MPLS forwarding caused by the Label Switching Router's (LSR's) control plane restart, and specifically by the restart of its BGP component when BGP is used to carry MPLS labels and the LSR is capable of preserving the MPLS forwarding state across the restart. | January 2007 Status: PROPOSED STANDARD Autor: Y. Rekhter, R. Aggarwal |
| RFC4782 Quick-Start for TCP and IP This document specifies an optional Quick-Start mechanism for transport protocols, in cooperation with routers, to determine an allowed sending rate at the start and, at times, in the middle of a data transfer (e.g., after an idle period). While Quick-Start is designed to be used by a range of transport protocols, in this document we only specify its use with TCP. Quick-Start is designed to allow connections to use higher sending rates when there is significant unused bandwidth along the path, and the sender and all of the routers along the path approve the Quick-Start Request. | January 2007 Status: EXPERIMENTAL Autor: S. Floyd, M. Allman, A. Jain, P. Sarolahti |
| RFC4783 GMPLS - Communication of Alarm Information This document describes an extension to Generalized MPLS (Multi-Protocol Label Switching) signaling to support communication of alarm information. GMPLS signaling already supports the control of alarm reporting, but not the communication of alarm information. This document presents both a functional description and GMPLS-RSVP specifics of such an extension. This document also proposes modification of the RSVP ERROR_SPEC object. | December 2006 Status: PROPOSED STANDARD Autor: L. Berger |
| RFC4784 Verizon Wireless Dynamic Mobile IP Key Update for cdma2000(R) Networks The Verizon Wireless Dynamic Mobile IP Key Update procedure is a mechanism for distributing and updating Mobile IP (MIP) cryptographic keys in cdma2000(R) networks (including High Rate Packet Data, which is often referred to as 1xEV-DO). The Dynamic Mobile IP Key Update (DMU) procedure occurs between the MIP Mobile Node (MN) and RADIUS Authentication, Authorization and Accounting (AAA) Server via a cdma2000(R) Packet Data Serving Node (PDSN) that is acting as a Mobile IP Foreign Agent (FA). | June 2007 Status: INFORMATIONAL Autor: C. Carroll, F. Quick |
| RFC4785 Pre-Shared Key (PSK) Ciphersuites with NULL Encryption for Transport Layer Security (TLS) This document specifies authentication-only ciphersuites (with no encryption) for the Pre-Shared Key (PSK) based Transport Layer Security (TLS) protocol. These ciphersuites are useful when authentication and integrity protection is desired, but confidentiality is not needed or not permitted. [STANDARDS-TRACK] | January 2007 Status: PROPOSED STANDARD Autor: U. Blumenthal, P. Goel |
| RFC4786 Operation of Anycast Services As the Internet has grown, and as systems and networked services within enterprises have become more pervasive, many services with high availability requirements have emerged. These requirements have increased the demands on the reliability of the infrastructure on which those services rely. | December 2006 Status: BEST CURRENT PRACTICE Autor: J. Abley, K. Lindqvist |
| RFC4787 Network Address Translation (NAT) Behavioral Requirements for Unicast UDP This document defines basic terminology for describing different types of Network Address Translation (NAT) behavior when handling Unicast UDP and also defines a set of requirements that would allow many applications, such as multimedia communications or online gaming, to work consistently. Developing NATs that meet this set of requirements will greatly increase the likelihood that these applications will function properly. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | January 2007 Status: BEST CURRENT PRACTICE Autor: F. Audet, C. Jennings |
| RFC4788 Enhancements to RTP Payload Formats for EVRC Family Codecs This document updates the Enhanced Variable Rate Codec (EVRC) RTP payload formats defined in RFC 3558 with several enhancements and extensions. In particular, it defines support for the header-free and interleaved/bundled packet formats for the EVRC-B codec, a new compact bundled format for the EVRC and EVRC-B codecs, as well as discontinuous transmission (DTX) support for EVRC and EVRC-B-encoded speech transported via RTP. Voice over IP (VoIP) applications operating over low bandwidth dial-up and wireless networks require such enhancements for efficient use of the bandwidth. [STANDARDS-TRACK] | January 2007 Status: PROPOSED STANDARD Autor: Q. Xie, R. Kapoor |
| RFC4789 Simple Network Management Protocol (SNMP) over IEEE 802 Networks This document specifies how Simple Network Management Protocol (SNMP) messages can be transmitted directly over IEEE 802 networks. | November 2006 Status: PROPOSED STANDARD Autor: J. Schoenwaelder, T. Jeffree |
| RFC4790 Internet Application Protocol Collation Registry Many Internet application protocols include string-based lookup, searching, or sorting operations. However, the problem space for searching and sorting international strings is large, not fully explored, and is outside the area of expertise for the Internet Engineering Task Force (IETF). Rather than attempt to solve such a large problem, this specification creates an abstraction framework so that application protocols can precisely identify a comparison function, and the repertoire of comparison functions can be extended in the future. [STANDARDS-TRACK] | March 2007 Status: PROPOSED STANDARD Autor: C. Newman, M. Duerst, A. Gulbrandsen |
| RFC4791 Calendaring Extensions to WebDAV (CalDAV) This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. This document defines the "calendar-access" feature of CalDAV. [STANDARDS-TRACK] | March 2007 Status: PROPOSED STANDARD Autor: C. Daboo, B. Desruisseaux, L. Dusseault |
| RFC4792 Encoding Instructions for the Generic String Encoding Rules (GSER) Abstract Syntax Notation One (ASN.1) defines a general framework for annotating types in an ASN.1 specification with encoding instructions that alter how values of those types are encoded according to ASN.1 encoding rules. This document defines the supporting notation for encoding instructions that apply to the Generic String Encoding Rules (GSER) and, in particular, defines an encoding instruction to provide a machine-processable representation for the declaration of a GSER ChoiceOfStrings type. [STANDARDS-TRACK] | January 2007 Status: PROPOSED STANDARD Autor: S. Legg |
| RFC4793 The EAP Protected One-Time Password Protocol (EAP-POTP) This document describes a general Extensible Authentication Protocol (EAP) method suitable for use with One-Time Password (OTP) tokens, and offers particular advantages for tokens with direct electronic interfaces to their associated clients. The method can be used to provide unilateral or mutual authentication, and key material, in protocols utilizing EAP, such as PPP, IEEE 802.1X, and Internet Key Exchange Protocol Version 2 (IKEv2). This memo provides information for the Internet community. | February 2007 Status: INFORMATIONAL Autor: M. Nystroem |
| RFC4794 RFC 1264 Is Obsolete RFC 1264 was written during what was effectively a completely different time in the life of the Internet. It prescribed rules to protect the Internet against new routing protocols that may have various undesirable properties. In today's Internet, there are so many other pressures against deploying unreasonable protocols that we believe that existing controls suffice, and the RFC 1264 rules just get in the way. This memo provides information for the Internet community. | December 2006 Status: INFORMATIONAL Autor: B. Fenner |
| RFC4795 Link-local Multicast Name Resolution (LLMNR) The goal of Link-Local Multicast Name Resolution (LLMNR) is to enable name resolution in scenarios in which conventional DNS name resolution is not possible. LLMNR supports all current and future DNS formats, types, and classes, while operating on a separate port from DNS, and with a distinct resolver cache. Since LLMNR only operates on the local link, it cannot be considered a substitute for DNS. This memo provides information for the Internet community. | January 2007 Status: INFORMATIONAL Autor: B. Aboba, D. Thaler, L. Esibov |
| RFC4796 The Session Description Protocol (SDP) Content Attribute This document defines a new Session Description Protocol (SDP) media- level attribute, 'content'. The 'content' attribute defines the content of the media stream to a more detailed level than the media description line. The sender of an SDP session description can attach the 'content' attribute to one or more media streams. The receiving application can then treat each media stream differently (e.g., show it on a big or small screen) based on its content. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: J. Hautakorpi, G. Camarillo |
| RFC4797 Use of Provider Edge to Provider Edge (PE-PE) Generic Routing Encapsulation (GRE) or IP in BGP/MPLS IP Virtual Private Networks This document describes an implementation strategy for BGP/MPLS IP Virtual Private Networks (VPNs) in which the outermost MPLS label (i.e., the tunnel label) is replaced with either an IP header or an IP header with Generic Routing Encapsulation (GRE). | January 2007 Status: INFORMATIONAL Autor: Y. Rekhter, R. Bonica, E. Rosen |
| RFC4798 Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE) This document explains how to interconnect IPv6 islands over a Multiprotocol Label Switching (MPLS)-enabled IPv4 cloud. This approach relies on IPv6 Provider Edge routers (6PE), which are Dual Stack in order to connect to IPv6 islands and to the MPLS core, which is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6 reachability information transparently over the core using the Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4. In doing so, the BGP Next Hop field is used to convey the IPv4 address of the 6PE router so that dynamically established IPv4-signaled MPLS Label Switched Paths (LSPs) can be used without explicit tunnel configuration. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: J. De Clercq, D. Ooms, S. Prevost, F. Le Faucheur |
| RFC4801 Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management This document defines a Management Information Base (MIB) module that contains textual conventions (TCs) to represent commonly used Generalized Multiprotocol Label Switching (GMPLS) management information. The intent is that these textual conventions will be imported and used in GMPLS-related MIB modules that would otherwise define their own representations. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: T. Nadeau, A. Farrel |
| RFC4802 Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering 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 for Generalized Multiprotocol Label Switching (GMPLS)-based traffic engineering. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: T. Nadeau, A. Farrel, Ed. |
| RFC4803 Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) 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 to configure and/or monitor a Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR). [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: T. Nadeau, A. Farrel |
| RFC4804 Aggregation of Resource ReSerVation Protocol (RSVP) Reservations over MPLS TE/DS-TE Tunnels RFC 3175 specifies aggregation of Resource ReSerVation Protocol (RSVP) end-to-end reservations over aggregate RSVP reservations. This document specifies aggregation of RSVP end-to-end reservations over MPLS Traffic Engineering (TE) tunnels or MPLS Diffserv-aware MPLS Traffic Engineering (DS-TE) tunnels. This approach is based on RFC 3175 and simply modifies the corresponding procedures for operations over MPLS TE tunnels instead of aggregate RSVP reservations. This approach can be used to achieve admission control of a very large number of flows in a scalable manner since the devices in the core of the network are unaware of the end-to-end RSVP reservations and are only aware of the MPLS TE tunnels. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: F. Le Faucheur |
| RFC4805 Definitions of Managed Objects for the DS1, J1, E1, DS2, and E2 Interface Types This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS1, J1, 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. | March 2007 Status: PROPOSED STANDARD Autor: O. Nicklass |
| RFC4806 Online Certificate Status Protocol (OCSP) Extensions to IKEv2 While the Internet Key Exchange Protocol version 2 (IKEv2) supports public key based authentication, the corresponding use of in-band Certificate Revocation Lists (CRL) is problematic due to unbounded CRL size. The size of an Online Certificate Status Protocol (OCSP) response is however well-bounded and small. This document defines the "OCSP Content" extension to IKEv2. A CERTREQ payload with "OCSP Content" identifies zero or more trusted OCSP responders and is a request for inclusion of an OCSP response in the IKEv2 handshake. A cooperative recipient of such a request responds with a CERT payload containing the appropriate OCSP response. This content is recognizable via the same "OCSP Content" identifier. | February 2007 Status: PROPOSED STANDARD Autor: M. Myers, H. Tschofenig |
| RFC4807 IPsec Security Policy Database Configuration MIB This document defines a Structure of Management Information Version 2 (SMIv2) Management Information Base (MIB) module for configuring the security policy database of a device implementing the IPsec protocol. The policy-based packet filtering and the corresponding execution of actions described in this document are of a more general nature than for IPsec configuration alone, such as for configuration of a firewall. This MIB module is designed to be extensible with other enterprise or standards-based defined packet filters and actions. [STANDARDS-TRACK] | March 2007 Status: PROPOSED STANDARD Autor: M. Baer, R. Charlet, W. Hardaker, R. Story, C. Wang |
| RFC4808 Key Change Strategies for TCP-MD5 The TCP-MD5 option is most commonly used to secure BGP sessions between routers. However, changing the long-term key is difficult, since the change needs to be synchronized between different organizations. We describe single-ended strategies that will permit (mostly) unsynchronized key changes. This memo provides information for the Internet community. | March 2007 Status: INFORMATIONAL Autor: S. Bellovin |
| RFC4809 Requirements for an IPsec Certificate Management Profile This informational document describes and identifies the requirements for transactions to handle Public Key Certificate (PKC) lifecycle transactions between Internet Protocol Security (IPsec) Virtual Private Network (VPN) Systems using Internet Key Exchange (IKE) (versions 1 and 2) and Public Key Infrastructure (PKI) Systems. These requirements are designed to meet the needs of enterprise-scale IPsec VPN deployments. It is intended that a standards track profile of a management protocol will be created to address many of these requirements. This memo provides information for the Internet community. | February 2007 Status: INFORMATIONAL Autor: C. Bonatti, S. Turner, G. Lebovitz |
| RFC4810 Long-Term Archive Service Requirements There are many scenarios in which users must be able to prove the existence of data at a specific point in time and be able to demonstrate the integrity of data since that time, even when the duration from time of existence to time of demonstration spans a large period of time. Additionally, users must be able to verify signatures on digitally signed data many years after the generation of the signature. This document describes a class of long-term archive services to support such scenarios and the technical requirements for interacting with such services. This memo provides information for the Internet community. | March 2007 Status: INFORMATIONAL Autor: C. Wallace, U. Pordesch, R. Brandner |
| RFC4811 OSPF Out-of-Band Link State Database (LSDB) Resynchronization OSPF is a link-state intra-domain routing protocol used in IP networks. Link State Database (LSDB) synchronization in OSPF is achieved via two methods -- initial LSDB synchronization when an OSPF router has just been connected to the network and asynchronous flooding that ensures continuous LSDB synchronization in the presence of topology changes after the initial procedure was completed. It may sometime be necessary for OSPF routers to resynchronize their LSDBs. The OSPF standard, however, does not allow routers to do so without actually changing the topology view of the network. | March 2007 Status: INFORMATIONAL Autor: L. Nguyen, A. Roy, A. Zinin |
| RFC4812 OSPF Restart Signaling OSPF is a link-state intra-domain routing protocol used in IP networks. Routers find new and detect unreachable neighbors via the Hello subprotocol. Hello OSPF packets are also used to ensure two-way connectivity within time. When a router restarts its OSPF software, it may not know its neighbors. If such a router sends a Hello packet on an interface, its neighbors are going to reset the adjacency, which may not be desirable in certain conditions. | March 2007 Status: INFORMATIONAL Autor: L. Nguyen, A. Roy, A. Zinin |
| RFC4813 OSPF Link-Local Signaling OSPF is a link-state intra-domain routing protocol used in IP networks. OSPF routers exchange information on a link using packets that follow a well-defined format. The format of OSPF packets is not flexible enough to enable applications to exchange arbitrary data, which may be necessary in certain situations. This memo describes a vendor-specific, backward-compatible technique to perform link-local signaling, i.e., exchange arbitrary data on a link. This memo defines an Experimental Protocol for the Internet community. | March 2007 Status: EXPERIMENTAL Autor: B. Friedman, L. Nguyen, A. Roy, D. Yeung, A. Zinin |
| RFC4814 Hash and Stuffing: Overlooked Factors in Network Device Benchmarking Test engineers take pains to declare all factors that affect a given measurement, including intended load, packet length, test duration, and traffic orientation. However, current benchmarking practice overlooks two factors that have a profound impact on test results. First, existing methodologies do not require the reporting of addresses or other test traffic contents, even though these fields can affect test results. Second, "stuff" bits and bytes inserted in test traffic by some link-layer technologies add significant and variable overhead, which in turn affects test results. This document describes the effects of these factors; recommends guidelines for test traffic contents; and offers formulas for determining the probability of bit- and byte-stuffing in test traffic. This memo provides information for the Internet community. | March 2007 Status: INFORMATIONAL Autor: D. Newman, T. Player |
| RFC4815 RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095 RFC 3095 defines the RObust Header Compression (ROHC) framework and profiles for IP (Internet Protocol), UDP (User Datagram Protocol), RTP (Real-Time Transport Protocol), and ESP (Encapsulating Security Payload). Some parts of the specification are unclear or contain errors that may lead to misinterpretations that may impair interoperability between different implementations. This document provides corrections, additions, and clarifications to RFC 3095; this document thus updates RFC 3095. In addition, other clarifications related to RFC 3241 (ROHC over PPP), RFC 3843 (ROHC IP profile) and RFC 4109 (ROHC UDP-Lite profiles) are also provided. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: L-E. Jonsson, K. Sandlund, G. Pelletier, P. Kremer |
| RFC4816 Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service The document describes a transparent cell transport service that makes use of the "N-to-one" cell relay mode for Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer-Mode (ATM) cell encapsulation. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: A. Malis, L. Martini, J. Brayley, T. Walsh |
| RFC4817 Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3 The Layer 2 Tunneling Protocol, Version 3 (L2TPv3) defines a protocol for tunneling a variety of payload types over IP networks. This document defines how to carry an MPLS label stack and its payload over the L2TPv3 data encapsulation. This enables an application that traditionally requires an MPLS-enabled core network, to utilize an L2TPv3 encapsulation over an IP network instead. [STANDARDS-TRACK] | March 2007 Status: PROPOSED STANDARD Autor: M. Townsley, C. Pignataro, S. Wainner, T. Seely, J. Young |
| RFC4818 RADIUS Delegated-IPv6-Prefix Attribute This document defines a RADIUS (Remote Authentication Dial In User Service) attribute that carries an IPv6 prefix that is to be delegated to the user. This attribute is usable within either RADIUS or Diameter. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: J. Salowey, R. Droms |
| RFC4819 Secure Shell Public Key Subsystem Secure Shell defines a user authentication mechanism that is based on public keys, but does not define any mechanism for key distribution. No common key management solution exists in current implementations. This document describes a protocol that can be used to configure public keys in an implementation-independent fashion, allowing client software to take on the burden of this configuration. | March 2007 Status: PROPOSED STANDARD Autor: J. Galbraith, J. Van Dyke, J. Bright |
| RFC4820 Padding Chunk and Parameter for the Stream Control Transmission Protocol (SCTP) This document defines a padding chunk and a padding parameter and describes the required receiver side procedures. The padding chunk is used to pad a Stream Control Transmission Protocol (SCTP) packet to an arbitrary size. The padding parameter is used to pad an SCTP INIT chunk to an arbitrary size. [STANDARDS-TRACK] | March 2007 Status: PROPOSED STANDARD Autor: M. Tuexen, R. Stewart, P. Lei |
| RFC4821 Packetization Layer Path MTU Discovery This document describes a robust method for Path MTU Discovery (PMTUD) that relies on TCP or some other Packetization Layer to probe an Internet path with progressively larger packets. This method is described as an extension to RFC 1191 and RFC 1981, which specify ICMP-based Path MTU Discovery for IP versions 4 and 6, respectively. [STANDARDS-TRACK] | March 2007 Status: PROPOSED STANDARD Autor: M. Mathis, J. Heffner |
| RFC4822 RIPv2 Cryptographic Authentication This note describes a revision to the RIPv2 Cryptographic Authentication mechanism originally specified in RFC 2082. This document obsoletes RFC 2082 and updates RFC 2453. This document adds details of how the SHA family of hash algorithms can be used with RIPv2 Cryptographic Authentication, whereas the original document only specified the use of Keyed-MD5. Also, this document clarifies a potential issue with an active attack on this mechanism and adds significant text to the Security Considerations section. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: R. Atkinson, M. Fanto |
| RFC4823 FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet This Applicability Statement (AS) describes how to exchange structured business data securely using the File Transfer Protocol (FTP) for XML, Binary, Electronic Data Interchange (EDI - ANSI X12 or UN/EDIFACT), or other data used for business-to-business data interchange for which MIME packaging can be accomplished using standard MIME content types. Authentication and data confidentiality are obtained by using Cryptographic Message Syntax (S/MIME) security body parts. Authenticated acknowledgements employ multipart/signed replies to the original message. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: T. Harding, R. Scott |
| RFC4824 The Transmission of IP Datagrams over the Semaphore Flag Signaling System (SFSS) This document specifies a method for encapsulating and transmitting IPv4/IPv6 packets over the Semaphore Flag Signal System (SFSS). This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: J. Hofmueller, A. Bachmann, IO. zmoelnig |
| RFC4825 The Extensible Markup Language (XML) Configuration Access Protocol (XCAP) This specification defines the Extensible Markup Language (XML) Configuration Access Protocol (XCAP). XCAP allows a client to read, write, and modify application configuration data stored in XML format on a server. XCAP maps XML document sub-trees and element attributes to HTTP URIs, so that these components can be directly accessed by HTTP. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC4826 Extensible Markup Language (XML) Formats for Representing Resource Lists In multimedia communications, presence, and instant messaging systems, there is a need to define Uniform Resource Identifiers (URIs) that represent services that are associated with a group of users. One example is a resource list service. If a user sends a Session Initiation Protocol (SIP) SUBSCRIBE message to the URI representing the resource list service, the server will obtain the state of the users in the associated group, and provide it to the sender. To facilitate definition of these services, this specification defines two Extensible Markup Language (XML) documents. One document contains service URIs, along with their service definition and a reference to the associated group of users. The second document contains the user lists that are referenced from the first. This list of users can be utilized by other applications and services. Both documents can be created and managed with the XML Configuration Access Protocol (XCAP). [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC4827 An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents This document describes a usage of the Extensible Markup Language (XML) Configuration Access Protocol (XCAP) for manipulating the contents of Presence Information Data Format (PIDF) based presence documents. It is intended to be used in Session Initiation Protocol (SIP) based presence systems, where the Event State Compositor can use the XCAP-manipulated presence document as one of the inputs on which it builds the overall presence state for the presentity. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: M. Isomaki, E. Leppanen |
| RFC4828 TCP Friendly Rate Control (TFRC): The Small-Packet (SP) Variant This document proposes a mechanism for further experimentation, but not for widespread deployment at this time in the global Internet. | April 2007 Status: EXPERIMENTAL Autor: S. Floyd, E. Kohler |
| RFC4829 Label Switched Path (LSP) Preemption Policies for MPLS Traffic Engineering When the establishment of a higher priority (Traffic Engineering Label Switched Path) TE LSP requires the preemption of a set of lower priority TE LSPs, a node has to make a local decision to select which TE LSPs will be preempted. The preempted LSPs are then rerouted by their respective \%Head-end Label Switch Router (LSR). This document presents a flexible policy that can be used to achieve different objectives: preempt the lowest priority LSPs; preempt the minimum number of LSPs; preempt the set of TE LSPs that provide the closest amount of bandwidth to the required bandwidth for the preempting TE LSPs (to minimize bandwidth wastage); preempt the LSPs that will have the maximum chance to get rerouted. Simulation results are given and a comparison among several different policies, with respect to preemption cascading, number of preempted LSPs, priority, wasted bandwidth and blocking probability is also included. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: J. de Oliveira, JP. Vasseur, L. Chen, C. Scoglio |
| RFC4830 Problem Statement for Network-Based Localized Mobility Management (NETLMM) Localized mobility management is a well-understood concept in the IETF, with a number of solutions already available. This document looks at the principal shortcomings of the existing solutions, all of which involve the host in mobility management, and makes a case for network-based local mobility management. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: J. Kempf |
| RFC4831 Goals for Network-Based Localized Mobility Management (NETLMM) In this document, design goals for a network-based localized mobility management (NETLMM) protocol are discussed. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: J. Kempf |
| RFC4832 Security Threats to Network-Based Localized Mobility Management (NETLMM) This document discusses security threats to network-based localized mobility management. Threats may occur on two interfaces: the interface between a localized mobility anchor and a mobile access gateway, as well as the interface between a mobile access gateway and a mobile node. Threats to the former interface impact the localized mobility management protocol itself. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: C. Vogt, J. Kempf |
| RFC4833 Timezone Options for DHCP Two common ways to communicate timezone information are POSIX 1003.1 timezone strings and timezone database names. This memo specifies DHCP options for each of those methods. The DHCPv4 time offset option is deprecated. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: E. Lear, P. Eggert |
| RFC4834 Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs) This document presents a set of functional requirements for network solutions that allow the deployment of IP multicast within Layer 3 (L3) Provider-Provisioned Virtual Private Networks (PPVPNs). It specifies requirements both from the end user and service provider standpoints. It is intended that potential solutions specifying the support of IP multicast within such VPNs will use these requirements as guidelines. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: T. Morin |
| RFC4835 Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) The IPsec series of protocols makes use of various cryptographic algorithms in order to provide security services. The Encapsulating Security Payload (ESP) and the Authentication Header (AH) provide two mechanisms for protecting data being sent over an IPsec Security Association (SA). To ensure interoperability between disparate implementations, it is necessary to specify a set of mandatory-to-implement algorithms to ensure that there is at least one algorithm that all implementations will have available. This document defines the current set of mandatory-to-implement algorithms for ESP and AH as well as specifying algorithms that should be implemented because they may be promoted to mandatory at some future time. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: V. Manral |
| RFC4836 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) This document defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This document obsoletes RFC 3636. It amends that specification by moving MAU type OBJECT-IDENTITY definitions and relevant textual conventions into a separate Internet Assigned Number Authority (IANA) maintained MIB module. In addition, management information is added to enable support for Ethernet in the First Mile (EFM) and 10GBASE-CX4 MAUs. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: E. Beili |
| RFC4837 Managed Objects of Ethernet Passive Optical Networks (EPON) 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 interfaces that conform to the Ethernet Passive Optical Networks (EPON) standard as defined in the IEEE Std 802.3ah-2004, which are extended capabilities to the Ethernet like interfaces. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: L. Khermosh |
| RFC4838 Delay-Tolerant Networking Architecture This document describes an architecture for delay-tolerant and disruption-tolerant networks, and is an evolution of the architecture originally designed for the Interplanetary Internet, a communication system envisioned to provide Internet-like services across interplanetary distances in support of deep space exploration. This document describes an architecture that addresses a variety of problems with internetworks having operational and performance characteristics that make conventional (Internet-like) networking approaches either unworkable or impractical. We define a message- oriented overlay that exists above the transport (or other) layers of the networks it interconnects. The document presents a motivation for the architecture, an architectural overview, review of state management required for its operation, and a discussion of application design issues. This document represents the consensus of the IRTF DTN research group and has been widely reviewed by that group. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: V. Cerf, S. Burleigh, A. Hooke, L. Torgerson, R. Durst, K. Scott, K. Fall, H. Weiss |
| RFC4839 Media Type Registrations for the Open eBook Publication Structure (OEBPS) Package File (OPF) This document serves to register a media type for the Open eBook Publication Structure (OEBPS) Package Files. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: G. Conboy, J. Rivlin, J. Ferraiolo |
| RFC4840 Multiple Encapsulation Methods Considered Harmful This document describes architectural and operational issues that arise from link-layer protocols supporting multiple Internet Protocol encapsulation methods. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: B. Aboba, E. Davies, D. Thaler |
| RFC4841 RFC 4181 Update to Recognize the IETF Trust This document updates RFC 4181, "Guidelines for Authors and Reviewers of MIB Documents", to recognize the creation of the IETF Trust. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | March 2007 Status: BEST CURRENT PRACTICE Autor: C. Heard |
| RFC4842 Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP) This document provides encapsulation formats and semantics for emulating Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) circuits and services over MPLS. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: A. Malis, P. Pate, R. Cohen, D. Zelig |
| RFC4843 An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID) This document introduces Overlay Routable Cryptographic Hash Identifiers (ORCHID) as a new, experimental class of IPv6-address- like identifiers. These identifiers are intended to be used as endpoint identifiers at applications and Application Programming Interfaces (API) and not as identifiers for network location at the IP layer, i.e., locators. They are designed to appear as application layer entities and at the existing IPv6 APIs, but they should not appear in actual IPv6 headers. To make them more like vanilla IPv6 addresses, they are expected to be routable at an overlay level. Consequently, while they are considered non-routable addresses from the IPv6 layer point-of-view, all existing IPv6 applications are expected to be able to use them in a manner compatible with current IPv6 addresses. | April 2007 Status: EXPERIMENTAL Autor: P. Nikander, J. Laganier, F. Dupont |
| RFC4844 The RFC Series and RFC Editor This document describes the framework for an RFC Series and an RFC Editor function that incorporate the principles of organized community involvement and accountability that has become necessary as the Internet technical community has grown, thereby enabling the RFC Series to continue to fulfill its mandate. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: L. Daigle, Internet Architecture Board |
| RFC4845 Process for Publication of IAB RFCs From time to time, the Internet Architecture Board (IAB) publishes documents as Requests for Comments (RFCs). This document defines the process by which those documents are produced, reviewed, and published in the RFC Series. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: L. Daigle, Internet Architecture Board |
| RFC4846 Independent Submissions to the RFC Editor There is a long-standing tradition in the Internet community, predating the Internet Engineering Task Force (IETF) by many years, of use of the RFC Series to publish materials that are not rooted in the IETF standards process and its review and approval mechanisms. These documents, known as "Independent Submissions", serve a number of important functions for the Internet community, both inside and outside of the community of active IETF participants. This document discusses the Independent Submission model and some reasons why it is important. It then describes editorial and processing norms that can be used for Independent Submissions as the community goes forward into new relationships between the IETF community and its primary technical publisher. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: J. Klensin, D. Thaler |
| RFC4847 Framework and Requirements for Layer 1 Virtual Private Networks This document provides a framework and service level requirements for Layer 1 Virtual Private Networks (L1VPNs). This framework is intended to aid in developing and standardizing protocols and mechanisms to support interoperable L1VPNs. | April 2007 Status: INFORMATIONAL Autor: T. Takeda |
| RFC4848 Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS) The purpose of this document is to define a new, straightforward Dynamic Delegation Discovery Service (DDDS) application to allow mapping of domain names to URIs for particular application services and protocols. Although defined as a new DDDS application, dubbed U-NAPTR, this is effectively an extension of the Straightforward NAPTR (S-NAPTR) DDDS Application. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: L. Daigle |
| RFC4849 RADIUS Filter Rule Attribute While RFC 2865 defines the Filter-Id attribute, it requires that the Network Access Server (NAS) be pre-populated with the desired filters. However, in situations where the server operator does not know which filters have been pre-populated, it is useful to specify filter rules explicitly. This document defines the NAS-Filter-Rule attribute within the Remote Authentication Dial In User Service (RADIUS). This attribute is based on the Diameter NAS-Filter-Rule Attribute Value Pair (AVP) described in RFC 4005, and the IPFilterRule syntax defined in RFC 3588. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: P. Congdon, M. Sanchez, B. Aboba |
| RFC4850 Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node Architecture The Internet Small Computer Systems Interface (iSCSI) protocol, described in RFC 3720, allows for extension items to the protocol in the form of Private or Public Extension Keys. This document describes a Public Extension Key for the purpose of enhancing iSCSI supportability. The key accomplishes this objective by allowing iSCSI nodes to communicate architecture details during the iSCSI login sequence. The receiving node can then use this information for enhanced logging and support. This document updates RFC 3720 to allow iSCSI extension items to be defined by standards track RFCs and experimental RFCs in addition to informational RFCs. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: D. Wysochanski |
| RFC4851 The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST) This document defines the Extensible Authentication Protocol (EAP) based Flexible Authentication via Secure Tunneling (EAP-FAST) protocol. EAP-FAST is an EAP method that enables secure communication between a peer and a server by using the Transport Layer Security (TLS) to establish a mutually authenticated tunnel. Within the tunnel, Type-Length-Value (TLV) objects are used to convey authentication related data between the peer and the EAP server. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: N. Cam-Winget, D. McGrew, J. Salowey, H. Zhou |
| RFC4852 IPv6 Enterprise Network Analysis - IP Layer 3 Focus This document analyzes the transition to IPv6 in enterprise networks focusing on IP Layer 3. These networks are characterized as having multiple internal links and one or more router connections to one or more Providers, and as being managed by a network operations entity. The analysis focuses on a base set of transition notational networks and requirements expanded from a previous document on enterprise scenarios. Discussion is provided on a focused set of transition analysis required for the enterprise to transition to IPv6, assuming a Dual-IP layer (IPv4 and IPv6) network and node environment within the enterprise. Then, a set of transition mechanisms are recommended for each notational network. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: J. Bound, Y. Pouffary, S. Klynsma, T. Chown, D. Green |
| RFC4853 Cryptographic Message Syntax (CMS) Multiple Signer Clarification This document updates the Cryptographic Message Syntax (CMS), which is published in RFC 3852. This document clarifies the proper handling of the SignedData protected content type when more than one digital signature is present. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC4854 A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP) This document describes a Uniform Resource Name (URN) namespace for uniquely identifying Extensible Markup Language (XML) formats and protocols that provide extensions to the Extensible Messaging and Presence Protocol (XMPP) and are defined in specifications published by the XMPP Standards Foundation (XSF). This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: P. Saint-Andre |
| RFC4855 Media Type Registration of RTP Payload Formats This document specifies the procedure to register RTP payload formats as audio, video, or other media subtype names. This is useful in a text-based format description or control protocol to identify the type of an RTP transmission. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: S. Casner |
| RFC4856 Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences This document specifies media type registrations for the RTP payload formats defined in the RTP Profile for Audio and Video Conferences. Some of these may also be used for transfer modes other than RTP. [STANDARDS-TRACK] | February 2007 Status: PROPOSED STANDARD Autor: S. Casner |
| RFC4857 Mobile IPv4 Regional Registration Using Mobile IP, a mobile node registers with its home agent each time it changes care-of address. This document describes a new kind of "regional registrations", i.e., registrations local to the visited domain. The regional registrations are performed via a new network entity called a Gateway Foreign Agent (GFA) and introduce a layer of hierarchy in the visited domain. Regional registrations reduce the number of signaling messages to the home network, and reduce the signaling delay when a mobile node moves from one foreign agent to another within the same visited domain. This document is an optional extension to the Mobile IPv4 protocol. This memo defines an Experimental Protocol for the Internet community. | June 2007 Status: EXPERIMENTAL Autor: E. Fogelstroem, A. Jonsson, C. Perkins |
| RFC4858 Document Shepherding from Working Group Last Call to Publication This document describes methodologies that have been designed to improve and facilitate IETF document flow processing. It specifies a set of procedures under which a working group chair or secretary serves as the primary Document Shepherd for a document that has been submitted to the IESG for publication. Before this, the Area Director responsible for the working group has traditionally filled the shepherding role. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: H. Levkowetz, D. Meyer, L. Eggert, A. Mankin |
| RFC4859 Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Session Attribute Object This document provides instructions to IANA for the creation of a new codepoint registry for the flags field in the Session Attribute object of the Resource Reservation Protocol Traffic Engineering (RSVP-TE) signaling messages used in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) signaling. This memo provides information for the Internet community. | April 2007 Status: INFORMATIONAL Autor: A. Farrel |
| RFC4860 Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations RFC 3175 defines aggregate Resource ReSerVation Protocol (RSVP) reservations allowing resources to be reserved in a Diffserv network for a given Per Hop Behavior (PHB), or given set of PHBs, from a given source to a given destination. RFC 3175 also defines how end-to-end RSVP reservations can be aggregated onto such aggregate reservations when transiting through a Diffserv cloud. There are situations where multiple such aggregate reservations are needed for the same source IP address, destination IP address, and PHB (or set of PHBs). However, this is not supported by the aggregate reservations defined in RFC 3175. In order to support this, the present document defines a more flexible type of aggregate RSVP reservations, referred to as generic aggregate reservation. Multiple such generic aggregate reservations can be established for a given PHB (or set of PHBs) from a given source IP address to a given destination IP address. The generic aggregate reservations may be used to aggregate end-to-end RSVP reservations. This document also defines the procedures for such aggregation. The generic aggregate reservations may also be used end-to-end directly by end-systems attached to a Diffserv network. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: F. Le Faucheur, B. Davie, P. Bose, C. Christou, M. Davenport |
| RFC4861 Neighbor Discovery for IP version 6 (IPv6) This document specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link-layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors. [STANDARDS-TRACK] | September 2007 Status: DRAFT STANDARD Autor: T. Narten, E. Nordmark, W. Simpson, H. Soliman |
| RFC4862 IPv6 Stateless Address Autoconfiguration This document specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link-local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link. [STANDARDS-TRACK] | September 2007 Status: DRAFT STANDARD Autor: S. Thomson, T. Narten, T. Jinmei |
| RFC4863 Wildcard Pseudowire Type Pseudowire signaling requires that the Pseudowire Type (PW Type) be identical in both directions. For certain applications the configuration of the PW Type is most easily accomplished by configuring this information at just one PW endpoint. In any form of LDP-based signaling, each PW endpoint must initiate the creation of a unidirectional LSP. In order to allow the initiation of these two LSPs to remain independent, a means is needed for allowing the PW endpoint (lacking a priori knowledge of the PW Type) to initiate the creation of an LSP. This document defines a Wildcard PW Type to satisfy this need. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: L. Martini, G. Swallow |
| RFC4864 Local Network Protection for IPv6 Although there are many perceived benefits to Network Address Translation (NAT), its primary benefit of "amplifying" available address space is not needed in IPv6. In addition to NAT's many serious disadvantages, there is a perception that other benefits exist, such as a variety of management and security attributes that could be useful for an Internet Protocol site. IPv6 was designed with the intention of making NAT unnecessary, and this document shows how Local Network Protection (LNP) using IPv6 can provide the same or more benefits without the need for address translation. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: G. Van de Velde, T. Hain, R. Droms, B. Carpenter, E. Klein |
| RFC4865 SMTP Submission Service Extension for Future Message Release This memo defines an extension to the SMTP submission protocol for a client to indicate a future time for the message to be released for delivery. This extension permits a client to use server-based storage for a message that should be held in queue until an appointed time in the future. This is useful for clients which do not have local storage or are otherwise unable to release a message for delivery at an appointed time. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: G. White, G. Vaudreuil |
| RFC4866 Enhanced Route Optimization for Mobile IPv6 This document specifies an enhanced version of Mobile IPv6 route optimization, providing lower handoff delays, increased security, and reduced signaling overhead. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: J. Arkko, C. Vogt, W. Haddad |
| RFC4867 RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs 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 media type registrations are included, one for AMR and one for AMR-WB, specifying use of both the RTP payload format and the storage format. This document obsoletes RFC 3267. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie |
| RFC4868 Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec This specification describes the use of Hashed Message Authentication Mode (HMAC) in conjunction with the SHA-256, SHA-384, and SHA-512 algorithms in IPsec. These algorithms may be used as the basis for data origin authentication and integrity verification mechanisms for the Authentication Header (AH), Encapsulating Security Payload (ESP), Internet Key Exchange Protocol (IKE), and IKEv2 protocols, and also as Pseudo-Random Functions (PRFs) for IKE and IKEv2. Truncated output lengths are specified for the authentication-related variants, with the corresponding algorithms designated as HMAC-SHA-256-128, HMAC-SHA-384-192, and HMAC-SHA-512-256. The PRF variants are not truncated, and are called PRF-HMAC-SHA-256, PRF-HMAC-SHA-384, and PRF-HMAC-SHA-512. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: S. Kelly, S. Frankel |
| RFC4869 Suite B Cryptographic Suites for IPsec This document proposes four optional cryptographic user interface suites ("UI suites") for IPsec, similar to the two suites specified in RFC 4308. The four new suites provide compatibility with the United States National Security Agency's Suite B specifications. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: L. Law, J. Solinas |
| RFC4870 Domain-Based Email Authentication Using Public Keys Advertised in the DNS (DomainKeys) "DomainKeys" creates a domain-level authentication framework for email by using public key technology and the DNS to prove the provenance and contents of an email. | May 2007 Status: HISTORIC Autor: M. Delany |
| RFC4871 DomainKeys Identified Mail (DKIM) Signatures DomainKeys Identified Mail (DKIM) defines a domain-level authentication framework for email using public-key cryptography and key server technology to permit verification of the source and contents of messages by either Mail Transfer Agents (MTAs) or Mail User Agents (MUAs). The ultimate goal of this framework is to permit a signing domain to assert responsibility for a message, thus protecting message signer identity and the integrity of the messages they convey while retaining the functionality of Internet email as it is known today. Protection of email identity may assist in the global control of "spam" and "phishing". [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: E. Allman, J. Callas, M. Delany, M. Libbey, J. Fenton, M. Thomas |
| RFC4872 RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery This document describes protocol-specific procedures and extensions for Generalized Multi-Protocol Label Switching (GMPLS) Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to support end-to-end Label Switched Path (LSP) recovery that denotes protection and restoration. A generic functional description of GMPLS recovery can be found in a companion document, RFC 4426. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: J.P. Lang, Y. Rekhter, D. Papadimitriou |
| RFC4873 GMPLS Segment Recovery This document describes protocol specific procedures for GMPLS (Generalized Multi-Protocol Label Switching) RSVP-TE (Resource ReserVation Protocol - Traffic Engineering) signaling extensions to support label switched path (LSP) segment protection and restoration. These extensions are intended to complement and be consistent with the RSVP-TE Extensions for End-to-End GMPLS Recovery (RFC 4872). Implications and interactions with fast reroute are also addressed. This document also updates the handling of NOTIFY_REQUEST objects. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: L. Berger, I. Bryskin, D. Papadimitriou, A. Farrel |
| RFC4874 Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) This document specifies ways to communicate route exclusions during path setup using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE). | April 2007 Status: PROPOSED STANDARD Autor: CY. Lee, A. Farrel, S. De Cnodder |
| RFC4875 Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs) This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for the set up of Traffic Engineered (TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi- Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. The solution relies on RSVP-TE without requiring a multicast routing protocol in the Service Provider core. Protocol elements and procedures for this solution are described. | May 2007 Status: PROPOSED STANDARD Autor: R. Aggarwal, D. Papadimitriou, S. Yasukawa |
| RFC4876 A Configuration Profile Schema for Lightweight Directory Access Protocol (LDAP)-Based Agents This document consists of two primary components, a schema for agents that make use of the Lightweight Directory Access protocol (LDAP) and a proposed use case of that schema, for distributed configuration of similar directory user agents. A set of attribute types and an object class are proposed. In the proposed use case, directory user agents (DUAs) can use this schema to determine directory data location and access parameters for specific services they support. In addition, in the proposed use case, attribute and object class mapping allows DUAs to reconfigure their expected (default) schema to match that of the end user's environment. This document is intended to be a skeleton for future documents that describe configuration of specific DUA services. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: B. Neal-Joslin, L. Howard, M. Ansari |
| RFC4877 Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture This document describes Mobile IPv6 operation with the revised IPsec architecture and IKEv2. [STANDARDS-TRACK] | April 2007 Status: PROPOSED STANDARD Autor: V. Devarapalli, F. Dupont |
| RFC4878 Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet-like interfaces conformant to the Ethernet OAM functionality defined in the Ethernet in the First Mile (EFM) clauses of the Ethernet standards. The Ethernet OAM functionality is complementary to the Simple Network Management Protocol (SNMP) in that it is focused on a small set of link-specific functions for directly connected Ethernet interfaces. This document defines objects for controlling those link OAM functions and for providing results and status of the OAM functions to management entities. [STANDARDS-TRACK] | June 2007 Status: PROPOSED STANDARD Autor: M. Squire |
| RFC4879 Clarification of the Third Party Disclosure Procedure in RFC 3979 This document clarifies and updates a single sentence in RFC 3979. Specifically, when third party Intellectual Property Rights (IPR) disclosures are made, the intention is that the IETF Executive Director notify the IPR holder that a third party disclosure has been filed, and to ask the IPR holder whether they have any disclosure that needs to be made, per applicable RFC 3979 rules. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | April 2007 Status: BEST CURRENT PRACTICE Autor: T. Narten |
| RFC4880 OpenPGP Message Format This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws. | November 2007 Status: PROPOSED STANDARD Autor: J. Callas, L. Donnerhacke, H. Finney, D. Shaw, R. Thayer |
| RFC4881 Low-Latency Handoffs in Mobile IPv4 Mobile IPv4 describes how a Mobile Node can perform IPv4-layer handoffs between subnets served by different Foreign Agents. In certain cases, the latency involved in these handoffs can be above the threshold required for the support of delay-sensitive or real-time services. The aim of this document is to present two methods to achieve low-latency Mobile IPv4 handoffs. In addition, a combination of these two methods is described. The described techniques allow greater support for real-time services on a Mobile IPv4 network by minimizing the period of time when a Mobile Node is unable to send or receive IPv4 packets due to the delay in the Mobile IPv4 Registration process. This memo defines an Experimental Protocol for the Internet community. | June 2007 Status: EXPERIMENTAL Autor: K. El Malki |
| RFC4882 IP Address Location Privacy and Mobile IPv6: Problem Statement In this document, we discuss location privacy as applicable to Mobile IPv6. We document the concerns arising from revealing a Home Address to an onlooker and from disclosing a Care-of Address to a correspondent. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: R. Koodli |
| RFC4883 Benchmarking Terminology for Resource Reservation Capable Routers The primary purpose of this document is to define terminology specific to the benchmarking of resource reservation signaling of Integrated Services (IntServ) IP routers. These terms can be used in additional documents that define benchmarking methodologies for routers that support resource reservation or reporting formats for the benchmarking measurements. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: G. Feher, K. Nemeth, A. Korn, I. Cselenyi |
| RFC4884 Extended ICMP to Support Multi-Part Messages This document redefines selected ICMP messages to support multi-part operation. A multi-part ICMP message carries all of the information that ICMP messages carried previously, as well as additional information that applications may require. | April 2007 Status: PROPOSED STANDARD Autor: R. Bonica, D. Gan, D. Tappan, C. Pignataro |
| RFC4885 Network Mobility Support Terminology This document defines a terminology for discussing network mobility (NEMO) issues and solution requirements. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: T. Ernst, H-Y. Lach |
| RFC4886 Network Mobility Support Goals and Requirements Network mobility arises when a router connecting a network to the Internet dynamically changes its point of attachment to the Internet thereby causing the reachability of the said network to be changed in relation to the fixed Internet topology. Such a type of network is referred to as a mobile network. With appropriate mechanisms, sessions established between nodes in the mobile network and the global Internet can be maintained after the mobile router changes its point of attachment. This document outlines the goals expected from network mobility support and defines the requirements that must be met by the NEMO Basic Support solution. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: T. Ernst |
| RFC4887 Network Mobility Home Network Models This paper documents some of the usage patterns and the associated issues when deploying a Home Network for Network Mobility (NEMO)- enabled Mobile Routers, conforming to the NEMO Basic Support. The aim here is specifically to provide some examples of organization of the Home Network, as they were discussed in NEMO-related mailing lists. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: P. Thubert, R. Wakikawa, V. Devarapalli |
| RFC4888 Network Mobility Route Optimization Problem Statement With current Network Mobility (NEMO) Basic Support, all communications to and from Mobile Network Nodes must go through the bi-directional tunnel established between the Mobile Router and Home Agent when the mobile network is away. This sub-optimal routing results in various inefficiencies associated with packet delivery, such as increased delay and bottleneck links leading to traffic congestion, which can ultimately disrupt all communications to and from the Mobile Network Nodes. Additionally, with nesting of Mobile Networks, these inefficiencies get compounded, and stalemate conditions may occur in specific dispositions. This document investigates such problems and provides the motivation behind Route Optimization (RO) for NEMO. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: C. Ng, P. Thubert, M. Watari, F. Zhao |
| RFC4889 Network Mobility Route Optimization Solution Space Analysis With current Network Mobility (NEMO) Basic Support, all communications to and from Mobile Network Nodes must go through the Mobile Router and Home Agent (MRHA) tunnel when the mobile network is away. This results in increased length of packet route and increased packet delay in most cases. To overcome these limitations, one might have to turn to Route Optimization (RO) for NEMO. This memo documents various types of Route Optimization in NEMO and explores the benefits and tradeoffs in different aspects of NEMO Route Optimization. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: C. Ng, F. Zhao, M. Watari, P. Thubert |
| RFC4890 Recommendations for Filtering ICMPv6 Messages in Firewalls In networks supporting IPv6, the Internet Control Message Protocol version 6 (ICMPv6) plays a fundamental role with a large number of functions, and a correspondingly large number of message types and options. ICMPv6 is essential to the functioning of IPv6, but there are a number of security risks associated with uncontrolled forwarding of ICMPv6 messages. Filtering strategies designed for the corresponding protocol, ICMP, in IPv4 networks are not directly applicable, because these strategies are intended to accommodate a useful auxiliary protocol that may not be required for correct functioning. | May 2007 Status: INFORMATIONAL Autor: E. Davies, J. Mohacsi |
| RFC4891 Using IPsec to Secure IPv6-in-IPv4 Tunnels This document gives guidance on securing manually configured IPv6-in- IPv4 tunnels using IPsec in transport mode. No additional protocol extensions are described beyond those available with the IPsec framework. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: R. Graveman, M. Parthasarathy, P. Savola, H. Tschofenig |
| RFC4892 Requirements for a Mechanism Identifying a Name Server Instance With the increased use of DNS anycast, load balancing, and other mechanisms allowing more than one DNS name server to share a single IP address, it is sometimes difficult to tell which of a pool of name servers has answered a particular query. A standardized mechanism to determine the identity of a name server responding to a particular query would be useful, particularly as a diagnostic aid for administrators. Existing ad hoc mechanisms for addressing this need have some shortcomings, not the least of which is the lack of prior analysis of exactly how such a mechanism should be designed and deployed. This document describes the existing convention used in some widely deployed implementations of the DNS protocol, including advantages and disadvantages, and discusses some attributes of an improved mechanism. This memo provides information for the Internet community. | June 2007 Status: INFORMATIONAL Autor: S. Woolf, D. Conrad |
| RFC4893 BGP Support for Four-octet AS Number Space Currently the Autonomous System (AS) number is encoded as a two-octet entity in BGP. This document describes extensions to BGP to carry the Autonomous System number as a four-octet entity. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: Q. Vohra, E. Chen |
| RFC4894 Use of Hash Algorithms in Internet Key Exchange (IKE) and IPsec This document describes how the IKEv1 (Internet Key Exchange version 1), IKEv2, and IPsec protocols use hash functions, and explains the level of vulnerability of these protocols to the reduced collision resistance of the MD5 and SHA-1 hash algorithms. This memo provides information for the Internet community. | May 2007 Status: INFORMATIONAL Autor: P. Hoffman |
| RFC4895 Authenticated Chunks for the Stream Control Transmission Protocol (SCTP) This document describes a new chunk type, several parameters, and procedures for the Stream Control Transmission Protocol (SCTP). This new chunk type can be used to authenticate SCTP chunks by using shared keys between the sender and receiver. The new parameters are used to establish the shared keys. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: M. Tuexen, R. Stewart, P. Lei, E. Rescorla |
| RFC4896 Signaling Compression (SigComp) Corrections and Clarifications This document describes common misinterpretations and some ambiguities in the Signaling Compression Protocol (SigComp), and offers guidance to developers to resolve any resultant problems. SigComp defines a scheme for compressing messages generated by application protocols such as the Session Initiation Protocol (SIP). This document updates the following RFCs: RFC 3320, RFC 3321, and RFC 3485. [STANDARDS-TRACK] | June 2007 Status: PROPOSED STANDARD Autor: A. Surtees, M. West, A.B. Roach |
| RFC4897 Handling Normative References to Standards-Track Documents The Internet Engineering Task Force (IETF) and Request for Comments (RFC) Editor have a long-standing rule that a document at a given maturity level cannot be published until all of the documents that it references as normative are at that maturity level or higher. This rule has sometimes resulted in very long publication delays for documents and some claims that it was a major obstruction to advancing documents in maturity level. The IETF agreed on a way to bypass this rule with RFC 3967. This document describes a simpler procedure for downward references to Standards-Track and Best Current Practice (BCP) documents, namely "note and move on". The procedure in RFC 3967 still applies for downward references to other classes of documents. In both cases, annotations should be added to such References. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2007 Status: BEST CURRENT PRACTICE Autor: J. Klensin, S. Hartman |
| RFC4898 TCP Extended Statistics MIB This document describes extended performance statistics for TCP. They are designed to use TCP's ideal vantage point to diagnose performance problems in both the network and the application. If a network-based application is performing poorly, TCP can determine if the bottleneck is in the sender, the receiver, or the network itself. If the bottleneck is in the network, TCP can provide specific information about its nature. [STANDARDS-TRACK] | May 2007 Status: PROPOSED STANDARD Autor: M. Mathis, J. Heffner, R. Raghunarayan |
| RFC4901 Protocol Extensions for Header Compression over MPLS This specification defines how to use Multi-Protocol Label Switching (MPLS) to route Header-Compressed (HC) packets over an MPLS label switched path. HC can significantly reduce packet-header overhead and, in combination with MPLS, can also increases bandwidth efficiency and processing scalability in terms of the maximum number of simultaneous compressed flows that use HC at each router). Here we define how MPLS pseudowires are used to transport the HC context and control messages between the ingress and egress MPLS label switching routers. This is defined for a specific set of existing HC mechanisms that might be used, for example, to support voice over IP. This specification also describes extension mechanisms to allow support for future, as yet to be defined, HC protocols. In this specification, each HC protocol operates independently over a single pseudowire instance, very much as it would over a single point-to-point link. [STANDARDS-TRACK] | June 2007 Status: PROPOSED STANDARD Autor: J. Ash, J. Hand, A. Malis |
| RFC4902 Integrity, Privacy, and Security in Open Pluggable Edge Services (OPES) for SMTP The Open Pluggable Edge Services (OPES) framework is application agnostic. Application-specific adaptations extend that framework. Previous work has focused on HTTP and work for SMTP is in progress. These protocols differ fundamentally in the way data flows, and it turns out that existing OPES requirements and IAB considerations for OPES need to be reviewed with regards to how well they fit for SMTP adaptation. This document analyzes aspects about the integrity of SMTP and mail message adaptation by OPES systems and about privacy and security issues when the OPES framework is adapted to SMTP. It also lists requirements that must be considered when creating the "SMTP adaptation with OPES" document. | May 2007 Status: INFORMATIONAL Autor: M. Stecher |
| RFC4903 Multi-Link Subnet Issues There have been several proposals around the notion that a subnet may span multiple links connected by routers. This memo documents the issues and potential problems that have been raised with such an approach. This memo provides information for the Internet community. | June 2007 Status: INFORMATIONAL Autor: D. Thaler |
| RFC4904 Representing Trunk Groups in tel/sip Uniform Resource Identifiers (URIs) This document describes a standardized mechanism to convey trunk group parameters in sip and tel Uniform Resource Identifiers (URIs). An extension to the tel URI is defined for this purpose. [STANDARDS-TRACK] | June 2007 Status: PROPOSED STANDARD Autor: V. Gurbani, C. Jennings |
| RFC4905 Encapsulation Methods for Transport of Layer 2 Frames over MPLS Networks This document describes methods for encapsulating the Protocol Data Units (PDUs) of layer 2 protocols such as Frame Relay, Asynchronous Transfer Mode (ATM), or Ethernet for transport across an MPLS network. This document describes the so-called "draft-martini" protocol, which has since been superseded by the Pseudowire Emulation Edge to Edge Working Group specifications described in RFC 4447 and related documents. This memo defines a Historic Document for the Internet community. | June 2007 Status: HISTORIC Autor: L. Martini, E. Rosen, N. El-Aawar |
| RFC4906 Transport of Layer 2 Frames Over MPLS This document describes methods for transporting the Protocol Data Units (PDUs) of layer 2 protocols such as Frame Relay, Asynchronous Transfer Mode (ATM) Adaption Layer 5 (AAL5), and Ethernet, and for providing a Synchronized Optical Network (SONET) circuit emulation service across an MPLS network. This document describes the so-called "draft-martini" protocol, which has since been superseded by the Pseudowire Emulation Edge to Edge Working Group specifications described in RFC 4447 and related documents. This memo defines a Historic Document for the Internet community. | June 2007 Status: HISTORIC Autor: L. Martini, E. Rosen, N. El-Aawar |
| RFC4907 Architectural Implications of Link Indications A link indication represents information provided by the link layer to higher layers regarding the state of the link. This document describes the role of link indications within the Internet architecture. While the judicious use of link indications can provide performance benefits, inappropriate use can degrade both robustness and performance. This document summarizes current proposals, describes the architectural issues, and provides examples of appropriate and inappropriate uses of link indications. This memo provides information for the Internet community. | June 2007 Status: INFORMATIONAL Autor: B. Aboba |
| RFC4908 Multi-homing for small scale fixed network Using Mobile IP and NEMO Multihoming technology improves the availability of host and network connectivity. Since the behaviors of fixed and mobile networks differ, distinct architectures for each have been discussed and proposed. This document proposes a common architecture for both mobile and fixed networking environments, using mobile IP (RFC 3775) and Network Mobility (NEMO; RFC 3963). The proposed architecture requires a modification of mobile IP and NEMO so that multiple Care-of Addresses (CoAs) can be used. In addition, multiple Home Agents (HAs) that are located in different places are required for redundancy. This memo defines an Experimental Protocol for the Internet community. | June 2007 Status: EXPERIMENTAL Autor: K. Nagami, S. Uda, N. Ogashiwa, H. Esaki, R. Wakikawa, H. Ohnishi |
| RFC4909 Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport This document specifies a new Multimedia Internet KEYing (MIKEY) General Extension payload (RFC 3830) to transport the short-term key message (STKM) and long-term key message (LTKM) payloads defined in the Open Mobile Alliance's (OMA) Browser and Content (BAC) Broadcast (BCAST) group's Service and Content protection specification. This memo provides information for the Internet community. | June 2007 Status: INFORMATIONAL Autor: L. Dondeti, D. Castleford, F. Hartung |
| RFC4910 Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1) This document defines a set of Abstract Syntax Notation One (ASN.1) encoding rules, called the Robust XML Encoding Rules or RXER, that produce an Extensible Markup Language (XML) representation for values of any given ASN.1 data type. Rules for producing a canonical RXER encoding are also defined. This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: S. Legg, D. Prager |
| RFC4911 Encoding Instructions for the Robust XML Encoding Rules (RXER) This document defines encoding instructions that may be used in an Abstract Syntax Notation One (ASN.1) specification to alter how ASN.1 values are encoded by the Robust XML Encoding Rules (RXER) and Canonical Robust XML Encoding Rules (CRXER), for example, to encode a component of an ASN.1 value as an Extensible Markup Language (XML) attribute rather than as a child element. Some of these encoding instructions also affect how an ASN.1 specification is translated into an Abstract Syntax Notation X (ASN.X) specification. Encoding instructions that allow an ASN.1 specification to reference definitions in other XML schema languages are also defined. This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: S. Legg |
| RFC4912 Abstract Syntax Notation X (ASN.X) Abstract Syntax Notation X (ASN.X) is a semantically equivalent Extensible Markup Language (XML) representation for Abstract Syntax Notation One (ASN.1) specifications. ASN.X completely avoids the numerous ambiguities inherent in the ASN.1 language; therefore, specifications written in ASN.X are much easier to parse and manage than original ASN.1 specifications. ASN.X, together with the Robust XML Encoding Rules (RXER), constitutes a schema language for XML documents that offers, through other ASN.1 encoding rules, alternative compact binary encodings for XML instance documents. This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: S. Legg |
| RFC4913 Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER) Abstract Syntax Notation X (ASN.X) is an Extensible Markup Language (XML) representation for Abstract Syntax Notation One (ASN.1) specifications. This document specifies the ASN.X representation of encoding instructions for the Generic String Encoding Rules (GSER). This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: S. Legg |
| RFC4914 Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the XML Encoding Rules (XER Abstract Syntax Notation X (ASN.X) is an Extensible Markup Language (XML) representation for Abstract Syntax Notation One (ASN.1) specifications. This document specifies the ASN.X representation of encoding instructions for the XML Encoding Rules (XER). This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: S. Legg |
| RFC4915 Multi-Topology (MT) Routing in OSPF This document describes an extension to Open Shortest Path First (OSPF) in order to define independent IP topologies called Multi- Topologies (MTs). The Multi-Topologies extension can be used for computing different paths for unicast traffic, multicast traffic, different classes of service based on flexible criteria, or an in- band network management topology. | June 2007 Status: PROPOSED STANDARD Autor: P. Psenak, S. Mirtorabi, A. Roy, L. Nguyen, P. Pillay-Esnault |
| RFC4916 Connected Identity in the Session Initiation Protocol (SIP) This document provides a means for a Session Initiation Protocol (SIP) User Agent (UA) that receives a dialog-forming request to supply its identity to the peer UA by means of a request in the reverse direction, and for that identity to be signed by an Authentication Service. Because of retargeting of a dialog-forming request (changing the value of the Request-URI), the UA that receives it (the User Agent Server, UAS) can have a different identity from that in the To header field. The same mechanism can be used to indicate a change of identity during a dialog, e.g., because of some action in the Public Switched Telephone Network (PSTN) behind a gateway. This document normatively updates RFC 3261 (SIP). [STANDARDS-TRACK] | June 2007 Status: PROPOSED STANDARD Autor: J. Elwell |
| RFC4917 Mobile IPv4 Message String Extension This document specifies a new extension for use in Mobile IPv4. This extension can be added by the Home Agent and the Foreign Agent to Registration Reply messages. This extension carries a text string that is intended for the user of the Mobile Node. [STANDARDS-TRACK] | June 2007 Status: PROPOSED STANDARD Autor: V. Sastry, K. Leung, A. Patel |
| RFC4918 HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV) Web Distributed Authoring and Versioning (WebDAV) consists of 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, URL namespace manipulation, and resource locking (collision avoidance). | June 2007 Status: PROPOSED STANDARD Autor: L. Dusseault |
| RFC4919 IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs): Overview, Assumptions, Problem Statement, and Goals This document describes the assumptions, problem statement, and goals for transmitting IP over IEEE 802.15.4 networks. The set of goals enumerated in this document form an initial set only. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: N. Kushalnagar, G. Montenegro, C. Schumacher |
| RFC4920 Crankback Signaling Extensions for MPLS and GMPLS RSVP-TE In a distributed, constraint-based routing environment, the information used to compute a path may be out of date. This means that Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) Label Switched Path (LSP) setup requests may be blocked by links or nodes without sufficient resources. Crankback is a scheme whereby setup failure information is returned from the point of failure to allow new setup attempts to be made avoiding the blocked resources. Crankback can also be applied to LSP recovery to indicate the location of the failed link or node. | July 2007 Status: PROPOSED STANDARD Autor: A. Farrel, A. Satyanarayana, A. Iwata, N. Fujita, G. Ash |
| RFC4923 Quality of Service (QoS) Signaling in a Nested Virtual Private Network Some networks require communication between an interior and exterior portion of a Virtual Private Network (VPN) or through a concatenation of such networks resulting in a nested VPN, but have sensitivities about what information is communicated across the boundary, especially while providing quality of service to communications with different precedence. This note seeks to outline the issues and the nature of the proposed solutions based on the framework for Integrated Services operation over Diffserv networks as described in RFC 2998. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: F. Baker, P. Bose |
| RFC4924 Reflections on Internet Transparency This document provides a review of previous IAB statements on Internet transparency, as well a discussion of new transparency issues. Far from having lessened in relevance, technical implications of intentionally or inadvertently impeding network transparency play a critical role in the Internet's ability to support innovation and global communication. This document provides some specific illustrations of those potential impacts. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: B. Aboba, E. Davies |
| RFC4925 Softwire Problem Statement This document captures the problem statement for the Softwires Working Group, which is developing standards for the discovery, control, and encapsulation methods for connecting IPv4 networks across IPv6-only networks as well as IPv6 networks across IPv4-only networks. The standards will encourage multiple, inter-operable vendor implementations by identifying, and extending where necessary, existing standard protocols to resolve a selected set of "IPv4/IPv6" and "IPv6/IPv4" transition problems. This document describes the specific problems ("Hubs and Spokes" and "Mesh") that will be solved by the standards developed by the Softwires Working Group. Some requirements (and non-requirements) are also identified to better describe the specific problem scope. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: X. Li, S. Dawkins, D. Ward, A. Durand |
| RFC4926 A URN Namespace for GEANT This document describes a proposed URN (Uniform Resource Name) namespace that would be managed by DANTE, representing European Research and academic networks, for naming persistent resources defined by GEANT, the Consortium of European Academic and Research Networks, its projects, activities, working groups, and other designated subordinates. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: T.Kalin, M.Molina |
| RFC4927 Path Computation Element Communication Protocol (PCECP) Specific Requirements for Inter-Area MPLS and GMPLS Traffic Engineering For scalability purposes, a network may comprise multiple Interior Gateway Protocol (IGP) areas. An inter-area Traffic Engineered Label Switched Path (TE-LSP) is an LSP that transits through at least two IGP areas. In a multi-area network, topology visibility remains local to a given area, and a head-end Label Switching Router (LSR) cannot compute an inter-area shortest constrained path. One key application of the Path Computation Element (PCE)-based architecture is the computation of inter-area TE-LSP paths. The PCE Communication Protocol (PCECP) is used to communicate computation requests from Path Computation Clients (PCCs) to PCEs, and to return computed paths in responses. This document lists a detailed set of PCECP-specific requirements for support of inter-area TE-LSP path computation. It complements the generic requirements for a PCE Communication Protocol. This memo provides information for the Internet community. | June 2007 Status: INFORMATIONAL Autor: J.-L. Le Roux |
| RFC4928 Avoiding Equal Cost Multipath Treatment in MPLS Networks This document describes the Equal Cost Multipath (ECMP) behavior of currently deployed MPLS networks. This document makes best practice recommendations for anyone defining an application to run over an MPLS network that wishes to avoid the reordering that can result from transmission of different packets from the same flow over multiple different equal cost paths. These recommendations rely on inspection of the IP version number field in packets. Despite the heuristic nature of the recommendations, they provide a relatively safe way to operate MPLS networks, even if future allocations of IP version numbers were made for some purpose. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2007 Status: BEST CURRENT PRACTICE Autor: G. Swallow, S. Bryant, L. Andersson |
| RFC4929 Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures This document provides guidelines for applying or extending the MPLS or GMPLS ((G)MPLS) protocol suites and clarifies the IETF's (G)MPLS working groups' responsibility for the (G)MPLS protocols. This document is directed to multi-vendor fora and Standards Development Organizations (SDOs) to provide an understanding of (G)MPLS work in the IETF and documents the requisite use of IETF review procedures when considering (G)MPLS applications or protocol extensions in their work. This document does not modify IETF processes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2007 Status: BEST CURRENT PRACTICE Autor: L. Andersson, A. Farrel |
| RFC4930 Extensible Provisioning Protocol (EPP) 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. This document obsoletes RFC 3730. [STANDARDS-TRACK] | May 2007 Status: DRAFT STANDARD Autor: S. Hollenbeck |
| RFC4931 Extensible Provisioning Protocol (EPP) Domain Name Mapping 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. This document obsoletes RFC 3731. [STANDARDS-TRACK] | May 2007 Status: DRAFT STANDARD Autor: S. Hollenbeck |
| RFC4932 Extensible Provisioning Protocol (EPP) Host Mapping 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. This document obsoletes RFC 3732. [STANDARDS-TRACK] | May 2007 Status: DRAFT STANDARD Autor: S. Hollenbeck |
| RFC4933 Extensible Provisioning Protocol (EPP) Contact Mapping 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. This document obsoletes RFC 3733. [STANDARDS-TRACK] | May 2007 Status: DRAFT STANDARD Autor: S. Hollenbeck |
| RFC4934 Extensible Provisioning Protocol (EPP) Transport Over TCP 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. This document obsoletes RFC 3734. [STANDARDS-TRACK] | May 2007 Status: DRAFT STANDARD Autor: S. Hollenbeck |
| RFC4935 Fibre Channel Fabric Configuration Server 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 Fabric Configuration Server function of a Fibre Channel network. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: C. DeSanti, H.K. Vivek, K. McCloghrie, S. Gai |
| RFC4936 Fibre Channel Zone Server 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 a Fibre Channel Zone Server. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: C. DeSanti, H.K. Vivek, K. McCloghrie, S. Gai |
| RFC4937 IANA Considerations for PPP over Ethernet (PPPoE) This document describes the IANA considerations for the PPP over Ethernet (PPPoE) protocol. This memo provides information for the Internet community. | June 2007 Status: INFORMATIONAL Autor: P. Arberg, V. Mammoliti |
| RFC4938 PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics This document extends the Point-to-Point over Ethernet (PPPoE) Protocol with a credit-based flow control mechanism and Link Quality Metric report. This optional extension should improve the performance of PPPoE over media with variable bandwidth and limited buffering, such as mobile radio links. This memo provides information for the Internet community. | June 2007 Status: INFORMATIONAL Autor: B. Berry, H. Holgate |
| RFC4939 Definitions of Managed Objects for iSNS (Internet Storage Name Service) The iSNS (Internet Storage Name Service) protocol provides storage name service functionality on an IP network that is being used for iSCSI (Internet Small Computer System Interface) or iFCP (Internet Fibre Channel Protocol) storage. This document provides a mechanism to monitor multiple iSNS Servers, including information about registered objects in an iSNS Server. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: K. Gibbons, G. Ramkumar, S. Kipp |
| RFC4940 IANA Considerations for OSPF This memo creates a number of OSPF registries and provides guidance to IANA for assignment of code points within these registries. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | July 2007 Status: BEST CURRENT PRACTICE Autor: K. Kompella, B. Fenner |
| RFC4941 Privacy Extensions for Stateless Address Autoconfiguration in IPv6 Nodes use IPv6 stateless address autoconfiguration to generate addresses using a combination of locally available information and information advertised by routers. Addresses are formed by combining network prefixes with an interface identifier. On an interface that contains an embedded IEEE Identifier, the interface identifier is typically derived from it. On other interface types, the interface identifier is generated through other means, for example, via random number generation. This document describes an extension to IPv6 stateless address autoconfiguration for interfaces whose interface identifier is derived from an IEEE identifier. Use of the extension causes nodes to generate global scope addresses from interface identifiers that change over time, even in cases where the interface contains an embedded IEEE identifier. Changing the interface identifier (and the global scope addresses generated from it) over time makes it more difficult for eavesdroppers and other information collectors to identify when different addresses used in different transactions actually correspond to the same node. [STANDARDS-TRACK] | September 2007 Status: DRAFT STANDARD Autor: T. Narten, R. Draves, S. Krishnan |
| RFC4942 IPv6 Transition/Co-existence Security Considerations The transition from a pure IPv4 network to a network where IPv4 and IPv6 coexist brings a number of extra security considerations that need to be taken into account when deploying IPv6 and operating the dual-protocol network and the associated transition mechanisms. This document attempts to give an overview of the various issues grouped into three categories: | September 2007 Status: INFORMATIONAL Autor: E. Davies, S. Krishnan, P. Savola |
| RFC4943 IPv6 Neighbor Discovery On-Link Assumption Considered Harmful This document describes the historical and background information behind the removal of the "on-link assumption" from the conceptual host sending algorithm defined in Neighbor Discovery for IP Version 6 (IPv6). According to the algorithm as originally described, when a host's default router list is empty, the host assumes that all destinations are on-link. This is particularly problematic with IPv6-capable nodes that do not have off-link IPv6 connectivity (e.g., no default router). This document describes how making this assumption causes problems and how these problems outweigh the benefits of this part of the conceptual sending algorithm. This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: S. Roy, A. Durand, J. Paugh |
| RFC4944 Transmission of IPv6 Packets over IEEE 802.15.4 Networks 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 IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: G. Montenegro, N. Kushalnagar, J. Hui, D. Culler |
| RFC4945 The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2, and PKIX The Internet Key Exchange (IKE) and Public Key Infrastructure for X.509 (PKIX) certificate profile both provide frameworks that must be profiled for use in a given application. This document provides a profile of IKE and PKIX that defines the requirements for using PKI technology in the context of IKE/IPsec. The document complements protocol specifications such as IKEv1 and IKEv2, which assume the existence of public key certificates and related keying materials, but which do not address PKI issues explicitly. This document addresses those issues. The intended audience is implementers of PKI for IPsec. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: B. Korver |
| RFC4946 Atom License Extension This memo defines an extension to the Atom Syndication Format for describing licenses associated with Atom feeds and entries. This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: J. Snell |
| RFC4947 Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks This document describes the process of binding/associating IPv4/IPv6 addresses with MPEG-2 Transport Streams (TS). This procedure is known as Address Resolution (AR) or Neighbor Discovery (ND). Such address resolution complements the higher-layer resource discovery tools that are used to advertise IP sessions. | July 2007 Status: INFORMATIONAL Autor: G. Fairhurst, M. Montpetit |
| RFC4948 Report from the IAB workshop on Unwanted Traffic March 9-10, 2006 This document reports the outcome of a workshop held by the Internet Architecture Board (IAB) on Unwanted Internet Traffic. The workshop was held on March 9-10, 2006 at USC/ISI in Marina del Rey, CA, USA. The primary goal of the workshop was to foster interchange between the operator, standards, and research communities on the topic of unwanted traffic, as manifested in, for example, Distributed Denial of Service (DDoS) attacks, spam, and phishing, to gain understandings on the ultimate sources of these unwanted traffic, and to assess their impact and the effectiveness of existing solutions. It was also a goal of the workshop to identify engineering and research topics that could be undertaken by the IAB, the IETF, the IRTF, and the network research and development community at large to develop effective countermeasures against the unwanted traffic. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: L. Andersson, E. Davies, L. Zhang |
| RFC4949 Internet Security Glossary, Version 2 This Glossary provides definitions, abbreviations, and explanations of terminology for information system security. The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026). The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: R. Shirey |
| RFC4950 ICMP Extensions for Multiprotocol Label Switching This memo defines an extension object that can be appended to selected multi-part ICMP messages. This extension permits Label Switching Routers to append MPLS information to ICMP messages, and has already been widely deployed. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: R. Bonica, D. Gan, D. Tappan, C. Pignataro |
| RFC4951 Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover" Layer 2 Tunneling Protocol (L2TP) is a connection-oriented protocol that has a shared state between active endpoints. Some of this shared state is vital for operation, but may be volatile in nature, such as packet sequence numbers used on the L2TP Control Connection. When failure of one side of a control connection occurs, a new control connection is created and associated with the old connection by exchanging information about the old connection. Such a mechanism is not intended as a replacement for an active fail over with some mirrored connection states, but as an aid for those parameters that are particularly difficult to have immediately available. Protocol extensions to L2TP defined in this document are intended to facilitate state recovery, providing additional resiliency in an L2TP network, and improving a remote system's layer 2 connectivity. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: V. Jain |
| RFC4952 Overview and Framework for Internationalized Email Full use of electronic mail throughout the world requires that people be able to use their own names, written correctly in their own languages and scripts, as mailbox names in email addresses. This document introduces a series of specifications that define mechanisms and protocol extensions needed to fully support internationalized email addresses. These changes include an SMTP extension and extension of email header syntax to accommodate UTF-8 data. The document set also includes discussion of key assumptions and issues in deploying fully internationalized email. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: J. Klensin, Y. Ko |
| RFC4953 Defending TCP Against Spoofing Attacks Recent analysis of potential attacks on core Internet infrastructure indicates an increased vulnerability of TCP connections to spurious resets (RSTs), sent with forged IP source addresses (spoofing). TCP has always been susceptible to such RST spoofing attacks, which were indirectly protected by checking that the RST sequence number was inside the current receive window, as well as via the obfuscation of TCP endpoint and port numbers. For pairs of well-known endpoints often over predictable port pairs, such as BGP or between web servers and well-known large-scale caches, increases in the path bandwidth-delay product of a connection have sufficiently increased the receive window space that off-path third parties can brute-force generate a viable RST sequence number. The susceptibility to attack increases with the square of the bandwidth, and thus presents a significant vulnerability for recent high-speed networks. This document addresses this vulnerability, discussing proposed solutions at the transport level and their inherent challenges, as well as existing network level solutions and the feasibility of their deployment. This document focuses on vulnerabilities due to spoofed TCP segments, and includes a discussion of related ICMP spoofing attacks on TCP connections. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: J. Touch |
| RFC4954 SMTP Service Extension for Authentication This document defines a Simple Mail Transport Protocol (SMTP) extension 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 during this session. This extension includes a profile of the Simple Authentication and Security Layer (SASL) for SMTP. | July 2007 Status: PROPOSED STANDARD Autor: R. Siemborski, A. Melnikov |
| RFC4955 DNS Security (DNSSEC) Experiments This document describes a methodology for deploying alternate, non-backwards-compatible, DNS Security (DNSSEC) methodologies in an experimental fashion without disrupting the deployment of standard DNSSEC. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: D. Blacka |
| RFC4956 DNS Security (DNSSEC) Opt-In In the DNS security (DNSSEC) extensions, delegations to unsigned subzones are cryptographically secured. Maintaining this cryptography is not always practical or necessary. This document describes an experimental "Opt-In" model that allows administrators to omit this cryptography and manage the cost of adopting DNSSEC with large zones. This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: R. Arends, M. Kosters, D. Blacka |
| RFC4957 Link-Layer Event Notifications for Detecting Network Attachments Certain network access technologies are capable of providing various types of link-layer status information to IP. Link-layer event notifications can help IP expeditiously detect configuration changes. This document provides a non-exhaustive catalogue of information available from well-known access technologies. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: S. Krishnan, N. Montavont, E. Njedjou, S. Veerepalli, A. Yegin |
| RFC4958 A Framework for Supporting Emergency Telecommunications Services (ETS) within a Single Administrative Domain This document presents a framework discussing the role of various protocols and mechanisms that could be considered candidates for supporting Emergency Telecommunication Services (ETS) within a single administrative domain. Comments about their potential usage as well as their current deployment are provided to the reader. Specific solutions are not presented. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: K. Carlberg |
| RFC4959 IMAP Extension for Simple Authentication and Security Layer (SASL) Initial Client Response To date, the Internet Message Access Protocol (IMAP) has used a Simple Authentication and Security Layer (SASL) profile which always required at least one complete round trip for an authentication, as it did not support an initial client response argument. This additional round trip at the beginning of the session is undesirable, especially when round-trip costs are high. | September 2007 Status: PROPOSED STANDARD Autor: R. Siemborski, A. Gulbrandsen |
| RFC4960 Stream Control Transmission Protocol This document obsoletes RFC 2960 and RFC 3309. It describes the Stream Control Transmission Protocol (SCTP). SCTP is designed to transport Public Switched Telephone Network (PSTN) signaling messages over IP networks, but is capable of broader applications. | September 2007 Status: PROPOSED STANDARD Autor: R. Stewart |
| RFC4961 Symmetric RTP / RTP Control Protocol (RTCP) This document recommends using one UDP port pair for both communication directions of bidirectional RTP and RTP Control Protocol (RTCP) sessions, commonly called "symmetric RTP" and "symmetric RTCP". This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | July 2007 Status: BEST CURRENT PRACTICE Autor: D. Wing |
| RFC4962 Guidance for Authentication, Authorization, and Accounting (AAA) Key Management This document provides guidance to designers of Authentication, Authorization, and Accounting (AAA) key management protocols. The guidance is also useful to designers of systems and solutions that include AAA key management protocols. Given the complexity and difficulty in designing secure, long-lasting key management algorithms and protocols by experts in the field, it is almost certainly inappropriate for IETF working groups without deep expertise in the area to be designing their own key management algorithms and protocols based on Authentication, Authorization, and Accounting (AAA) protocols. The guidelines in this document apply to documents requesting publication as IETF RFCs. Further, these guidelines will be useful to other standards development organizations (SDOs) that specify AAA key management. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | July 2007 Status: BEST CURRENT PRACTICE Autor: R. Housley, B. Aboba |
| RFC4963 IPv4 Reassembly Errors at High Data Rates IPv4 fragmentation is not sufficiently robust for use under some conditions in today's Internet. At high data rates, the 16-bit IP identification field is not large enough to prevent frequent incorrectly assembled IP fragments, and the TCP and UDP checksums are insufficient to prevent the resulting corrupted datagrams from being delivered to higher protocol layers. This note describes some easily reproduced experiments demonstrating the problem, and discusses some of the operational implications of these observations. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: J. Heffner, M. Mathis, B. Chandler |
| RFC4964 The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular This document describes a private Session Initiation Protocol (SIP) header (P-header) used by the Open Mobile Alliance (OMA) for Push to talk over Cellular (PoC) along with its applicability, which is limited to the OMA PoC application. The P-Answer-State header is used for indicating the answering mode of the handset, which is particular to the PoC application. This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: A. Allen, J. Holm, T. Hallin |
| RFC4965 CableLabs - IETF Standardization Collaboration This document describes the collaboration and liaison relationship between the Internet Engineering Task Force (IETF) and the Cable Television Laboratories, Inc. (CableLabs). This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: J-F. Mule, W. Townsley |
| RFC4966 Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status This document discusses issues with the specific form of IPv6-IPv4 protocol translation mechanism implemented by the Network Address Translator - Protocol Translator (NAT-PT) defined in RFC 2766. These issues are sufficiently serious that recommending RFC 2766 as a general purpose transition mechanism is no longer desirable, and this document recommends that the IETF should reclassify RFC 2766 from Proposed Standard to Historic status. This memo provides information for the Internet community. | July 2007 Status: INFORMATIONAL Autor: C. Aoun, E. Davies |
| RFC4967 Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier RFC 3966 explicitly states that 'tel' URIs may not represent a dial string. That leaves no way specify a dial string in a standardized way. Great confusion exists with the SIP URI parameter "user=phone", and specifically, if it can represent a dial string. This memo creates a new value for the user parameter "dialstring", so that one may specify "user=dialstring" to encode a dial string as a 'sip:' or 'sips:' URI. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: B. Rosen |
| RFC4968 Analysis of IPv6 Link Models for 802.16 Based Networks This document provides different IPv6 link models that are suitable for IEEE 802.16 based networks and provides analysis of various considerations for each link model and the applicability of each link model under different deployment scenarios. This document is the result of a design team (DT) that was formed to analyze the IPv6 link models for IEEE 802.16 based networks. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: S. Madanapalli |
| RFC4969 IANA Registration for vCard Enumservice This memo registers the Enumservice "vCard" using the URI schemes "http" and "https". This Enumservice is to be used to refer from an ENUM domain name to a vCard instance describing the user of the respective E.164 number. | August 2007 Status: PROPOSED STANDARD Autor: A. Mayrhofer |
| RFC4970 Extensions to OSPF for Advertising Optional Router Capabilities It is useful for routers in an OSPFv2 or OSPFv3 routing domain to know the capabilities of their neighbors and other routers in the routing domain. This document proposes extensions to OSPFv2 and OSPFv3 for advertising optional router capabilities. A new Router Information (RI) Link State Advertisement (LSA) is proposed for this purpose. In OSPFv2, the RI LSA will be implemented with a new opaque LSA type ID. In OSPFv3, the RI LSA will be implemented with a new LSA type function code. In both protocols, the RI LSA can be advertised at any of the defined flooding scopes (link, area, or autonomous system (AS)). [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: A. Lindem, N. Shen, JP. Vasseur, R. Aggarwal, S. Shaffer |
| RFC4971 Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information This document defines a new optional Intermediate System to Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple sub-TLVs, which allows a router to announce its capabilities within an IS-IS level or the entire routing domain. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: JP. Vasseur, N. Shen, R. Aggarwal |
| RFC4972 Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership The setup of a full mesh of Multi-Protocol Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths (LSP) among a set of Label Switch Routers (LSR) is a common deployment scenario of MPLS Traffic Engineering either for bandwidth optimization, bandwidth guarantees or fast rerouting with MPLS Fast Reroute. Such deployment may require the configuration of a potentially large number of TE LSPs (on the order of the square of the number of LSRs). This document specifies Interior Gateway Protocol (IGP) routing extensions for Intermediate System-to-Intermediate System (IS-IS) and Open Shortest Path First (OSPF) so as to provide an automatic discovery of the set of LSRs members of a mesh in order to automate the creation of such mesh of TE LSPs. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: JP. Vasseur, JL. Leroux, S. Yasukawa, S. Previdi, P. Psenak, P. Mabbey |
| RFC4973 OSPF-xTE: Experimental Extension to OSPF for Traffic Engineering This document defines OSPF-xTE, an experimental traffic engineering (TE) extension to the link-state routing protocol OSPF. OSPF-xTE defines new TE Link State Advertisements (LSAs) to disseminate TE metrics within an autonomous System (AS), which may consist of multiple areas. When an AS consists of TE and non-TE nodes, OSPF-xTE ensures that non-TE nodes in the AS are unaffected by the TE LSAs. OSPF-xTE generates a stand-alone TE Link State Database (TE-LSDB), distinct from the native OSPF LSDB, for computation of TE circuit paths. OSPF-xTE is versatile and extendible to non-packet networks such as Synchronous Optical Network (SONET) / Time Division Multiplexing (TDM) and optical networks. This memo defines an Experimental Protocol for the Internet community. | July 2007 Status: EXPERIMENTAL Autor: P. Srisuresh, P. Joseph |
| RFC4974 Generalized MPLS (GMPLS) RSVP-TE Signaling Extensions in Support of Calls In certain networking topologies, it may be advantageous to maintain associations between endpoints and key transit points to support an instance of a service. Such associations are known as Calls. | August 2007 Status: PROPOSED STANDARD Autor: D. Papadimitriou, A. Farrel |
| RFC4975 The Message Session Relay Protocol (MSRP) This document describes the Message Session Relay Protocol, a protocol for transmitting a series of related instant messages in the context of a session. Message sessions are treated like any other media stream when set up via a rendezvous or session creation protocol such as the Session Initiation Protocol. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: B. Campbell, R. Mahy, C. Jennings |
| RFC4976 Relay Extensions for the Message Sessions Relay Protocol (MSRP) Two separate models for conveying instant messages have been defined. Page-mode messages stand alone and are not part of a Session Initiation Protocol (SIP) session, whereas session-mode messages are set up as part of a session using SIP. The Message Session Relay Protocol (MSRP) is a protocol for near real-time, peer-to-peer exchanges of binary content without intermediaries, which is designed to be signaled using a separate rendezvous protocol such as SIP. This document introduces the notion of message relay intermediaries to MSRP and describes the extensions necessary to use them. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: C. Jennings, R. Mahy, A. B. Roach |
| RFC4977 Problem Statement: Dual Stack Mobility This document discusses the issues associated with mobility management for dual stack mobile nodes. Currently, two mobility management protocols are defined for IPv4 and IPv6. Deploying both in a dual stack mobile node introduces a number of problems. Deployment and operational issues motivate the use of a single mobility management protocol. This document discusses such motivations. The document also discusses requirements for the Mobile IPv4 (MIPv4) and Mobile IPv6 (MIPv6) protocol so that they can support mobility management for a dual stack node. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: G. Tsirtsis, H. Soliman |
| RFC4978 The IMAP COMPRESS Extension The COMPRESS extension allows an IMAP connection to be effectively and efficiently compressed. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: A. Gulbrandsen |
| RFC4979 IANA Registration for Enumservice 'XMPP' This document requests IANA registration of an Enumservice for XMPP, the Extensible Messaging and Presence Protocol. This Enumservice specifically allows the use of 'xmpp' Uniform Resource Identifiers (URIs) in the context of E.164 Number Mapping (ENUM). [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: A. Mayrhofer |
| RFC4980 Analysis of Multihoming in Network Mobility Support This document is an analysis of multihoming in the context of network mobility (NEMO) in IPv6. As there are many situations in which mobile networks may be multihomed, a taxonomy is proposed to classify the possible configurations. The possible deployment scenarios of multihomed mobile networks are described together with the associated issues when network mobility is supported by RFC 3963 (NEMO Basic Support). Recommendations are offered on how to address these issues. This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: C. Ng, T. Ernst, E. Paik, M. Bagnulo |
| RFC4981 Survey of Research towards Robust Peer-to-Peer Networks: Search Methods The pace of research on peer-to-peer (P2P) networking in the last five years warrants a critical survey. P2P has the makings of a disruptive technology -- it can aggregate enormous storage and processing resources while minimizing entry and scaling costs. | September 2007 Status: INFORMATIONAL Autor: J. Risson, T. Moors |
| RFC4982 Support for Multiple Hash Algorithms in Cryptographically Generated Addresses (CGAs) This document analyzes the implications of recent attacks on commonly used hash functions on Cryptographically Generated Addresses (CGAs) and updates the CGA specification to support multiple hash algorithms. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: M. Bagnulo, J. Arkko |
| RFC4983 Fibre Channel Registered State Change Notification (RSCN) 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 management of Fibre Channel's Registered State Change Notifications (RSCNs). [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: C. DeSanti, H.K. Vivek, K. McCloghrie, S. Gai |
| RFC4984 Report from the IAB Workshop on Routing and Addressing This document reports the outcome of the Routing and Addressing Workshop that was held by the Internet Architecture Board (IAB) on October 18-19, 2006, in Amsterdam, Netherlands. The primary goal of the workshop was to develop a shared understanding of the problems that the large backbone operators are facing regarding the scalability of today's Internet routing system. The key workshop findings include an analysis of the major factors that are driving routing table growth, constraints in router technology, and the limitations of today's Internet addressing architecture. It is hoped that these findings will serve as input to the IETF community and help identify next steps towards effective solutions. | September 2007 Status: INFORMATIONAL Autor: D. Meyer, L. Zhang, K. Fall |
| RFC4985 Internet X.509 Public Key Infrastructure Subject Alternative Name for Expression of Service Name This document defines a new name form for inclusion in the otherName field of an X.509 Subject Alternative Name extension that allows a certificate subject to be associated with the service name and domain name components of a DNS Service Resource Record. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: S. Santesson |
| RFC4986 Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover Every DNS security-aware resolver must have at least one Trust Anchor to use as the basis for validating responses from DNS signed zones. For various reasons, most DNS security-aware resolvers are expected to have several Trust Anchors. For some operations, manual monitoring and updating of Trust Anchors may be feasible, but many operations will require automated methods for updating Trust Anchors in their security-aware resolvers. This document identifies the requirements that must be met by an automated DNS Trust Anchor rollover solution for security-aware DNS resolvers. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: H. Eland, R. Mundy, S. Crocker, S. Krishnaswamy |
| RFC4987 TCP SYN Flooding Attacks and Common Mitigations This document describes TCP SYN flooding attacks, which have been well-known to the community for several years. Various countermeasures against these attacks, and the trade-offs of each, are described. This document archives explanations of the attack and common defense techniques for the benefit of TCP implementers and administrators of TCP servers or networks, but does not make any standards-level recommendations. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: W. Eddy |
| RFC4988 Mobile IPv4 Fast Handovers This document adapts the Mobile IPv6 Fast Handovers to improve delay and packet loss resulting from Mobile IPv4 handover operations. Specifically, this document addresses movement detection, IP address configuration, and location update latencies during a handover. For reducing the IP address configuration latency, the document proposes that the new Care-of Address is always made to be the new access router's IP address. This memo defines an Experimental Protocol for the Internet community. | October 2007 Status: EXPERIMENTAL Autor: R. Koodli, C. Perkins |
| RFC4990 Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks This document clarifies the use of addresses in Generalized Multiprotocol Label Switching (GMPLS) networks. The aim is to facilitate interworking of GMPLS-capable Label Switching Routers (LSRs). The document is based on experience gained in implementation, interoperability testing, and deployment. | September 2007 Status: INFORMATIONAL Autor: K. Shiomoto, R. Papneja, R. Rabbat |
| RFC4991 A Common Schema for Internet Registry Information Service Transfer Protocols This document describes an XML Schema for use by Internet Registry Information Service (IRIS) application transfer protocols that share common characteristics. It describes common information about the transfer protocol, such as version, supported extensions, and supported security mechanisms. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: A. Newton |
| RFC4992 XML Pipelining with Chunks for the Internet Registry Information Service This document describes a simple TCP transfer protocol for the Internet Registry Information Service (IRIS). Data is transferred between clients and servers using chunks to achieve pipelining. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: A. Newton |
| RFC4993 A Lightweight UDP Transfer Protocol for the Internet Registry Information Service This document describes a lightweight UDP transfer protocol for the Internet Registry Information Service (IRIS). This transfer protocol uses a single packet for every request and response, and optionally employs compression over the contents of the packet. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: A. Newton |
| RFC4994 DHCPv6 Relay Agent Echo Request Option This memo defines a Relay Agent Echo Request option for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option allows a DHCPv6 relay agent to request a list of relay agent options that the server echoes back to the relay agent. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: S. Zeng, B. Volz, K. Kinnear, J. Brzozowski |
| RFC4995 The RObust Header Compression (ROHC) Framework The Robust Header Compression (ROHC) protocol provides an efficient, flexible, and future-proof header compression concept. It is designed to operate efficiently and robustly over various link technologies with different characteristics. | July 2007 Status: PROPOSED STANDARD Autor: L-E. Jonsson, G. Pelletier, K. Sandlund |
| RFC4996 RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP) This document specifies a ROHC (Robust Header Compression) profile for compression of TCP/IP packets. The profile, called ROHC-TCP, provides efficient and robust compression of TCP headers, including frequently used TCP options such as SACK (Selective Acknowledgments) and Timestamps. | July 2007 Status: PROPOSED STANDARD Autor: G. Pelletier, K. Sandlund, L-E. Jonsson, M. West |
| RFC4997 Formal Notation for RObust Header Compression (ROHC-FN) This document defines Robust Header Compression - Formal Notation (ROHC-FN), a formal notation to specify field encodings for compressed formats when defining new profiles within the ROHC framework. ROHC-FN offers a library of encoding methods that are often used in ROHC profiles and can thereby help to simplify future profile development work. [STANDARDS-TRACK] | July 2007 Status: PROPOSED STANDARD Autor: R. Finking, G. Pelletier |
| RFC4998 Evidence Record Syntax (ERS) In many scenarios, users must be able prove the existence and integrity of data, including digitally signed data, in a common and reproducible way over a long and possibly undetermined period of time. This document specifies the syntax and processing of an Evidence Record, a structure designed to support long-term non-repudiation of existence of data. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: T. Gondrom, R. Brandner, U. Pordesch |
| RFC5000 Internet Official Protocol Standards This document is published by the RFC Editor to provide a summary of the current standards protocols (as of 18 February 2008). It lists those official protocol standards, Best Current Practice, and Experimental RFCs that have not been obsoleted; it is not a complete index to the RFC series. Newly published RFCs and RFCs whose status has changed are starred. | May 2008 Status: INFORMATIONAL Autor: RFC Editor |
| RFC5001 DNS Name Server Identifier (NSID) Option With the increased use of DNS anycast, load balancing, and other mechanisms allowing more than one DNS name server to share a single IP address, it is sometimes difficult to tell which of a pool of name servers has answered a particular query. While existing ad-hoc mechanisms allow an operator to send follow-up queries when it is necessary to debug such a configuration, the only completely reliable way to obtain the identity of the name server that responded is to have the name server include this information in the response itself. This note defines a protocol extension to support this functionality. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: R. Austein |
| RFC5002 The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header) This document specifies the SIP P-Profile-Key P-header. This header field is used in the 3rd-Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) to provide SIP registrars and SIP proxy servers with the key of the profile corresponding to the destination SIP URI of a particular SIP request. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: G. Camarillo, G. Blanco |
| RFC5003 Attachment Individual Identifier (AII) Types for Aggregation The signaling protocols used to establish point-to-point pseudowires include type-length-value (TLV) fields that identify pseudowire endpoints called attachment individual identifiers (AIIs). This document defines AII structures in the form of new AII TLV fields that support AII aggregation for improved scalability and Virtual Private Network (VPN) auto-discovery. It is envisioned that this would be useful in large inter-domain virtual private wire service networks where pseudowires are established between selected local and remote provider edge (PE) nodes based on customer need. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: C. Metz, L. Martini, F. Balus, J. Sugimoto |
| RFC5004 Avoid BGP Best Path Transitions from One External to Another In this document, we propose an extension to the BGP route selection rules that would avoid unnecessary best path transitions between external paths under certain conditions. The proposed extension would help the overall network stability, and more importantly, would eliminate certain BGP route oscillations in which more than one external path from one BGP speaker contributes to the churn. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: E. Chen, S. Sangli |
| RFC5005 Feed Paging and Archiving This specification defines three types of syndicated Web feeds that enable publication of entries across one or more feed documents. This includes "paged" feeds for piecemeal access, "archived" feeds that allow reconstruction of the feed's contents, and feeds that are explicitly "complete". [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: M. Nottingham |
| RFC5006 IPv6 Router Advertisement Option for DNS Configuration This document specifies a new IPv6 Router Advertisement option to allow IPv6 routers to advertise DNS recursive server addresses to IPv6 hosts. This memo defines an Experimental Protocol for the Internet community. | September 2007 Status: EXPERIMENTAL Autor: J. Jeong, S. Park, L. Beloeil, S. Madanapalli |
| RFC5007 DHCPv6 Leasequery This document specifies a leasequery exchange for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) that can be used to obtain lease information about DHCPv6 clients from a DHCPv6 server. This document specifies the scope of data that can be retrieved as well as both DHCPv6 leasequery requestor and server behavior. This document extends DHCPv6. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: J. Brzozowski, K. Kinnear, B. Volz, S. Zeng |
| RFC5008 Suite B in Secure/Multipurpose Internet Mail Extensions (S/MIME) This document specifies the conventions for using the United States National Security Agency's Suite B algorithms in Secure/Multipurpose Internet Mail Extensions (S/MIME) as specified in RFC 3851. This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: R. Housley, J. Solinas |
| RFC5009 Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media This document describes a private Session Initiation Protocol (SIP) header field (P-header) to be used by the European Telecommunications Standards Institute (ETSI) Telecommunications and Internet-converged Services and Protocols for Advanced Networks (TISPAN) for the purpose of authorizing early media flows in Third Generation Partnership Project (3GPP) IP Multimedia Subsystems (IMS). This header field is useful in any SIP network that is interconnected with other SIP networks and needs to control the flow of media in the early dialog state. This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: R. Ejza |
| RFC5010 The Dynamic Host Configuration Protocol Version 4 (DHCPv4) Relay Agent Flags Suboption This memo defines a new suboption of the Dynamic Host Configuration Protocol (DHCP) relay agent information option that allows the DHCP relay to specify flags for the forwarded packet. One flag is defined to indicate whether the DHCP relay received the packet via a unicast or broadcast packet. This information may be used by the DHCP server to better serve clients based on whether their request was originally broadcast or unicast. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: K. Kinnear, M. Normoyle, M. Stapp |
| RFC5011 Automated Updates of DNS Security (DNSSEC) Trust Anchors This document describes a means for automated, authenticated, and authorized updating of DNSSEC "trust anchors". The method provides protection against N-1 key compromises of N keys in the trust point key set. Based on the trust established by the presence of a current anchor, other anchors may be added at the same place in the hierarchy, and, ultimately, supplant the existing anchor(s). | September 2007 Status: PROPOSED STANDARD Autor: M. StJohns |
| RFC5012 Requirements for Emergency Context Resolution with Internet Technologies This document defines terminology and enumerates requirements for the context resolution of emergency calls placed by the public using voice-over-IP (VoIP) and general Internet multimedia systems, where Internet protocols are used end to end. This memo provides information for the Internet community. | January 2008 Status: INFORMATIONAL Autor: H. Schulzrinne, R. Marshall |
| RFC5013 The Dublin Core Metadata Element Set This document defines fifteen metadata elements for resource description in a cross-disciplinary information environment. This memo provides information for the Internet community. | August 2007 Status: INFORMATIONAL Autor: J. Kunze, T. Baker |
| RFC5014 IPv6 Socket API for Source Address Selection The IPv6 default address selection document (RFC 3484) describes the rules for selecting source and destination IPv6 addresses, and indicates that applications should be able to reverse the sense of some of the address selection rules through some unspecified API. However, no such socket API exists in the basic (RFC 3493) or advanced (RFC 3542) IPv6 socket API documents. This document fills that gap partially by specifying new socket-level options for source address selection and flags for the getaddrinfo() API to specify address selection based on the source address preference in accordance with the socket-level options that modify the default source address selection algorithm. The socket API described in this document will be particularly useful for IPv6 applications that want to choose between temporary and public addresses, and for Mobile IPv6 aware applications that want to use the care-of address for communication. It also specifies socket options and flags for selecting Cryptographically Generated Address (CGA) or non-CGA source addresses. This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: E. Nordmark, S. Chakrabarti, J. Laganier |
| RFC5015 Bidirectional Protocol Independent Multicast (BIDIR-PIM) This document discusses Bidirectional PIM (BIDIR-PIM), a variant of PIM Sparse-Mode that builds bidirectional shared trees connecting multicast sources and receivers. Bidirectional trees are built using a fail-safe Designated Forwarder (DF) election mechanism operating on each link of a multicast topology. With the assistance of the DF, multicast data is natively forwarded from sources to the Rendezvous-Point (RP) and hence along the shared tree to receivers without requiring source-specific state. The DF election takes place at RP discovery time and provides the route to the RP, thus eliminating the requirement for data-driven protocol events. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: M. Handley, I. Kouvelas, T. Speakman, L. Vicisano |
| RFC5016 Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism for domains to assert responsibility for the messages they handle. A related mechanism will allow an administrator to publish various statements about their DKIM signing practices. This document defines requirements for this mechanism, distinguishing between those that must be satisfied (MUST), and those that are highly desirable (SHOULD). This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: M. Thomas |
| RFC5017 MIB Textual Conventions for Uniform Resource Identifiers (URIs) This MIB module defines textual conventions to represent STD 66 Uniform Resource Identifiers (URIs). The intent is that these textual conventions will be imported and used in MIB modules that would otherwise define their own representation(s). [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: D. McWalter |
| RFC5018 Connection Establishment in the Binary Floor Control Protocol (BFCP) This document specifies how a Binary Floor Control Protocol (BFCP) client establishes a connection to a BFCP floor control server outside the context of an offer/answer exchange. Client and server authentication are based on Transport Layer Security (TLS). [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC5019 The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments This specification defines a profile of the Online Certificate Status Protocol (OCSP) that addresses the scalability issues inherent when using OCSP in large scale (high volume) Public Key Infrastructure (PKI) environments and/or in PKI environments that require a lightweight solution to minimize communication bandwidth and client-side processing. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: A. Deacon, R. Hurst |
| RFC5020 The Lightweight Directory Access Protocol (LDAP) entryDN Operational Attribute This document describes the Lightweight Directory Access Protocol (LDAP) / X.500 'entryDN' operational attribute. The attribute provides a copy of the entry's distinguished name for use in attribute value assertions. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC5021 Extended Kerberos Version 5 Key Distribution Center (KDC) Exchanges over TCP This document describes an extensibility mechanism for the Kerberos V5 protocol when used over TCP transports. The mechanism uses the reserved high-bit in the length field. It can be used to negotiate TCP-specific Kerberos extensions. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: S. Josefsson |
| RFC5022 Media Server Control Markup Language (MSCML) and Protocol Media Server Control Markup Language (MSCML) is a markup language used in conjunction with SIP to provide advanced conferencing and interactive voice response (IVR) functions. MSCML presents an application-level control model, as opposed to device-level control models. One use of this protocol is for communications between a conference focus and mixer in the IETF SIP Conferencing Framework. This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: J. Van Dyke, E. Burger, A. Spitzer |
| RFC5023 The Atom Publishing Protocol The Atom Publishing Protocol (AtomPub) is an application-level protocol for publishing and editing Web resources. The protocol is based on HTTP transfer of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: J. Gregorio, B. de hOra |
| RFC5024 ODETTE File Transfer Protocol 2.0 This memo updates the ODETTE File Transfer Protocol, an established file transfer protocol facilitating electronic data interchange of business data between trading partners, to version 2. | November 2007 Status: INFORMATIONAL Autor: I. Friend |
| RFC5025 Presence Authorization Rules Authorization is a key function in presence systems. Authorization policies, also known as authorization rules, specify what presence information can be given to which watchers, and when. This specification defines an Extensible Markup Language (XML) document format for expressing presence authorization rules. Such a document can be manipulated by clients using the XML Configuration Access Protocol (XCAP), although other techniques are permitted. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC5026 Mobile IPv6 Bootstrapping in Split Scenario A Mobile IPv6 node requires a Home Agent address, a home address, and IPsec security associations with its Home Agent before it can start utilizing Mobile IPv6 service. RFC 3775 requires that some or all of these are statically configured. This document defines how a Mobile IPv6 node can bootstrap this information from non-topological information and security credentials pre-configured on the Mobile Node. The solution defined in this document solves the split scenario described in the Mobile IPv6 bootstrapping problem statement in RFC 4640. The split scenario refers to the case where the Mobile Node's mobility service is authorized by a different service provider than basic network access. The solution described in this document is also generically applicable to any bootstrapping case, since other scenarios are more specific realizations of the split scenario. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: G. Giaretta, J. Kempf, V. Devarapalli |
| RFC5027 Security Preconditions for Session Description Protocol (SDP) Media Streams This document defines a new security precondition for the Session Description Protocol (SDP) precondition framework described in RFCs 3312 and 4032. A security precondition can be used to delay session establishment or modification until media stream security for a secure media stream has been negotiated successfully. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: F. Andreasen, D. Wing |
| RFC5028 A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services This document registers a Telephone Number Mapping (ENUM) service for Instant Messaging (IM). Specifically, this document focuses on provisioning 'im:' URIs (Uniform Resource Identifiers) in ENUM. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: R. Mahy |
| RFC5029 Definition of an IS-IS Link Attribute Sub-TLV This document defines a sub-TLV called "Link-attributes" carried within the TLV 22 and used to flood some link characteristics. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: JP. Vasseur, S. Previdi |
| RFC5030 Mobile IPv4 RADIUS Requirements This document provides an applicability statement as well as a scope definition for specifying Remote Authentication Dial-In User Service (RADIUS) extensions to support Mobile IPv4. The goal is to allow specification of RADIUS attributes to assist the Mobile IPv4 signaling procedures. This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: M. Nakhjiri, K. Chowdhury, A. Lior, K. Leung |
| RFC5031 A Uniform Resource Name (URN) for Emergency and Other Well-Known Services The content of many communication services depends on the context, such as the user's location. We describe a 'service' URN that allows well-known context-dependent services that can be resolved in a distributed manner to be identified. Examples include emergency services, directory assistance, and call-before-you-dig hot lines. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: H. Schulzrinne |
| RFC5032 WITHIN Search Extension to the IMAP Protocol This document describes the WITHIN extension to IMAP SEARCH. IMAP SEARCH returns messages whose internal date is within or outside a specified interval. The mechanism described here, OLDER and YOUNGER, differs from BEFORE and SINCE in that the client specifies an interval, rather than a date. WITHIN is useful for persistent searches where either the device does not have the capacity to perform the search at regular intervals or the network is of limited bandwidth and thus there is a desire to reduce network traffic from sending repeated requests and redundant responses. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: E. Burger |
| RFC5033 Specifying New Congestion Control Algorithms The IETF's standard congestion control schemes have been widely shown to be inadequate for various environments (e.g., high-speed networks). Recent research has yielded many alternate congestion control schemes that significantly differ from the IETF's congestion control principles. Using these new congestion control schemes in the global Internet has possible ramifications to both the traffic using the new congestion control and to traffic using the currently standardized congestion control. Therefore, the IETF must proceed with caution when dealing with alternate congestion control proposals. The goal of this document is to provide guidance for considering alternate congestion control algorithms within the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2007 Status: BEST CURRENT PRACTICE Autor: S. Floyd, M. Allman |
| RFC5034 The Post Office Protocol (POP3) Simple Authentication and Security Layer (SASL) Authentication Mechanism This document defines a profile of the Simple Authentication and Security Layer (SASL) for the Post Office Protocol (POP3). This extension allows a POP3 client to indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions during this session. | July 2007 Status: PROPOSED STANDARD Autor: R. Siemborski, A. Menon-Sen |
| RFC5035 Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility In the original Enhanced Security Services for S/MIME document (RFC 2634), a structure for cryptographically linking the certificate to be used in validation with the signature was introduced; this structure was hardwired to use SHA-1. This document allows for the structure to have algorithm agility and defines a new attribute for this purpose. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: J. Schaad |
| RFC5036 LDP Specification The architecture for Multiprotocol Label Switching (MPLS) is described in RFC 3031. 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] | October 2007 Status: DRAFT STANDARD Autor: L. Andersson, I. Minei, B. Thomas |
| RFC5037 Experience with the Label Distribution Protocol (LDP) The purpose of this memo is to document how some of the requirements specified in RFC 1264 for advancing protocols developed by working groups within the IETF Routing Area to Draft Standard have been satisfied by LDP (Label Distribution Protocol). Specifically, this report documents operational experience with LDP, requirement 5 of section 5.0 in RFC 1264. This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: L. Andersson, I. Minei, B. Thomas |
| RFC5038 The Label Distribution Protocol (LDP) Implementation Survey Results Multiprotocol Label Switching (MPLS), described in RFC 3031, is a method for forwarding packets that uses short, fixed-length values carried by packets, called labels, to determine packet next hops. 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 (as described in RFC 3036) , by which one LSR informs another of label bindings it has made. One such protocol, called LDP, is used by LSRs to distribute labels to support MPLS forwarding along normally routed paths. This document reports on a survey of LDP implementations conducted in August 2002 as part of the process of advancing LDP from Proposed to Draft Standard. This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: B. Thomas, L. Andersson |
| RFC5039 The Session Initiation Protocol (SIP) and Spam Spam, defined as the transmission of bulk unsolicited messages, has plagued Internet email. Unfortunately, spam is not limited to email. It can affect any system that enables user-to-user communications. The Session Initiation Protocol (SIP) defines a system for user-to- user multimedia communications. Therefore, it is susceptible to spam, just as email is. In this document, we analyze the problem of spam in SIP. We first identify the ways in which the problem is the same and the ways in which it is different from email. We then examine the various possible solutions that have been discussed for email and consider their applicability to SIP. This memo provides information for the Internet community. | January 2008 Status: INFORMATIONAL Autor: J. Rosenberg, C. Jennings |
| RFC5040 A Remote Direct Memory Access Protocol Specification This document defines a Remote Direct Memory Access Protocol (RDMAP) that operates over the Direct Data Placement Protocol (DDP protocol). RDMAP provides read and write services directly to applications and enables data to be transferred directly into Upper Layer Protocol (ULP) Buffers without intermediate data copies. It also enables a kernel bypass implementation. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: R. Recio, B. Metzler, P. Culley, J. Hilland, D. Garcia |
| RFC5041 Direct Data Placement over Reliable Transports The Direct Data Placement protocol provides information to Place the incoming data directly into an upper layer protocol's receive buffer without intermediate buffers. This removes excess CPU and memory utilization associated with transferring data through the intermediate buffers. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: H. Shah, J. Pinkerton, R. Recio, P. Culley |
| RFC5042 Direct Data Placement Protocol (DDP) / Remote Direct Memory Access Protocol (RDMAP) Security This document analyzes security issues around implementation and use of the Direct Data Placement Protocol (DDP) and Remote Direct Memory Access Protocol (RDMAP). It first defines an architectural model for an RDMA Network Interface Card (RNIC), which can implement DDP or RDMAP and DDP. The document reviews various attacks against the resources defined in the architectural model and the countermeasures that can be used to protect the system. Attacks are grouped into those that can be mitigated by using secure communication channels across the network, attacks from Remote Peers, and attacks from Local Peers. Attack categories include spoofing, tampering, information disclosure, denial of service, and elevation of privilege. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: J. Pinkerton, E. Deleganes |
| RFC5043 Stream Control Transmission Protocol (SCTP) Direct Data Placement (DDP) Adaptation This document specifies an adaptation layer to provide a Lower Layer Protocol (LLP) service for Direct Data Placement (DDP) using the Stream Control Transmission Protocol (SCTP). [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: C. Bestler, R. Stewart |
| RFC5044 Marker PDU Aligned Framing for TCP Specification Marker PDU Aligned Framing (MPA) is designed to work as an "adaptation layer" between TCP and the Direct Data Placement protocol (DDP) as described in RFC 5041. It preserves the reliable, in-order delivery of TCP, while adding the preservation of higher-level protocol record boundaries that DDP requires. MPA is fully compliant with applicable TCP RFCs and can be utilized with existing TCP implementations. MPA also supports integrated implementations that combine TCP, MPA and DDP to reduce buffering requirements in the implementation and improve performance at the system level. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: P. Culley, U. Elzur, R. Recio, S. Bailey, J. Carrier |
| RFC5045 Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct Data Placement (DDP) This document describes the applicability of Remote Direct Memory Access Protocol (RDMAP) and the Direct Data Placement Protocol (DDP). It compares and contrasts the different transport options over IP that DDP can use, provides guidance to ULP developers on choosing between available transports and/or how to be indifferent to the specific transport layer used, compares use of DDP with direct use of the supporting transports, and compares DDP over IP transports with non-IP transports that support RDMA functionality. This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: C. Bestler, L. Coene |
| RFC5046 Internet Small Computer System Interface (iSCSI) Extensions for Remote Direct Memory Access (RDMA) Internet Small Computer System Interface (iSCSI) Extensions for Remote Direct Memory Access (RDMA) provides the RDMA data transfer capability to iSCSI by layering iSCSI on top of an RDMA-Capable Protocol, such as the iWARP protocol suite. An RDMA-Capable Protocol provides RDMA Read and Write services, which enable data to be transferred directly into SCSI I/O Buffers without intermediate data copies. This document describes the extensions to the iSCSI protocol to support RDMA services as provided by an RDMA-Capable Protocol, such as the iWARP protocol suite. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: M. Ko, M. Chadalapaka, J. Hufferd, U. Elzur, H. Shah, P. Thaler |
| RFC5047 DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI) The Internet Small Computer System Interface (iSCSI) is a SCSI transport protocol that maps the SCSI family of application protocols onto TCP/IP. Datamover Architecture for iSCSI (DA) defines an abstract model in which the movement of data between iSCSI end nodes is logically separated from the rest of the iSCSI protocol in order to allow iSCSI to adapt to innovations available in new IP transports. While DA defines the architectural functions required of the class of Datamover protocols, it does not define any specific Datamover protocols. Each such Datamover protocol, defined in a separate document, provides a reliable transport for all iSCSI PDUs, but actually moves the data required for certain iSCSI PDUs without involving the remote iSCSI layer itself. This document begins with an introduction of a few new abstractions, defines a layered architecture for iSCSI and Datamover protocols, and then models the interactions within an iSCSI end node between the iSCSI layer and the Datamover layer that happen in order to transparently perform remote data movement within an IP fabric. It is intended that this definition will help map iSCSI to generic Remote Direct Memory Access (RDMA)-capable IP fabrics in the future comprising TCP, the Stream Control Transmission Protocol (SCTP), and possibly other underlying network transport layers, such as InfiniBand. This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: M. Chadalapaka, J. Hufferd, J. Satran, H. Shah |
| RFC5048 Internet Small Computer System Interface (iSCSI) Corrections and Clarifications The Internet Small Computer System Interface (iSCSI) is a SCSI transport protocol and maps the SCSI architecture and command sets onto TCP/IP. RFC 3720 defines the iSCSI protocol. This document compiles the clarifications to the original protocol definition in RFC 3720 to serve as a companion document for the iSCSI implementers. This document updates RFC 3720 and the text in this document supersedes the text in RFC 3720 when the two differ. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: M. Chadalapaka |
| RFC5049 Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP) This document describes some specifics that apply when Signaling Compression (SigComp) is applied to the Session Initiation Protocol (SIP), such as default minimum values of SigComp parameters, compartment and state management, and a few issues on SigComp over TCP. Any implementation of SigComp for use with SIP must conform to this document and SigComp, and in addition, support the SIP and Session Description Protocol (SDP) static dictionary. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: C. Bormann, Z. Liu, R. Price, G. Camarillo |
| RFC5050 Bundle Protocol Specification This document describes the end-to-end protocol, block formats, and abstract service description for the exchange of messages (bundles) in Delay Tolerant Networking (DTN). | November 2007 Status: EXPERIMENTAL Autor: K. Scott, S. Burleigh |
| RFC5051 i;unicode-casemap - Simple Unicode Collation Algorithm This document describes "i;unicode-casemap", a simple case-insensitive collation for Unicode strings. It provides equality, substring, and ordering operations. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: M. Crispin |
| RFC5052 Forward Error Correction (FEC) Building Block This document describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for bulk data transfer over IP multicast. This document defines a framework for the definition of the information that needs to be communicated in order to use an FEC code for bulk data transfer, in addition to the encoded data itself, and for definition of formats and codes for communication of that information. Both information communicated with the encoded data itself and information that needs to be communicated 'out-of-band' are considered. The procedures for specifying new FEC codes, defining the information communication requirements associated with those codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described. The requirements on Content Delivery Protocols that wish to use FEC codes defined within this framework are also defined. The companion document titled "The Use of Forward Error Correction (FEC) in Reliable Multicast" describes some applications of FEC codes for delivering content. This document obsoletes RFC 3452. [STANDARDS-TRACK] | August 2007 Status: PROPOSED STANDARD Autor: M. Watson, M. Luby, L. Vicisano |
| RFC5053 Raptor Forward Error Correction Scheme for Object Delivery This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 1, for the Raptor forward error correction code and its application to reliable delivery of data objects. | October 2007 Status: PROPOSED STANDARD Autor: M. Luby, A. Shokrollahi, M. Watson, T. Stockhammer |
| RFC5054 Using the Secure Remote Password (SRP) Protocol for TLS Authentication This memo presents a technique for using the Secure Remote Password protocol as an authentication method for the Transport Layer Security protocol. This memo provides information for the Internet community. | November 2007 Status: INFORMATIONAL Autor: D. Taylor, T. Wu, N. Mavrogiannopoulos, T. Perrin |
| RFC5055 Server-Based Certificate Validation Protocol (SCVP) The Server-Based Certificate Validation Protocol (SCVP) allows a client to delegate certification path construction and certification path validation to a server. The path construction or validation (e.g., making sure that none of the certificates in the path are revoked) is performed according to a validation policy, which contains one or more trust anchors. It allows simplification of client implementations and use of a set of predefined validation policies. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: T. Freeman, R. Housley, A. Malpani, D. Cooper, W. Polk |
| RFC5056 On the Use of Channel Bindings to Secure Channels The concept of channel binding allows applications to establish that the two end-points of a secure channel at one network layer are the same as at a higher layer by binding authentication at the higher layer to the channel at the lower layer. This allows applications to delegate session protection to lower layers, which has various performance benefits. | November 2007 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC5057 Multiple Dialog Usages in the Session Initiation Protocol Several methods in the Session Initiation Protocol (SIP) can create an association between endpoints known as a dialog. Some of these methods can also create a different, but related, association within an existing dialog. These multiple associations, or dialog usages, require carefully coordinated processing as they have independent life-cycles, but share common dialog state. Processing multiple dialog usages correctly is not completely understood. What is understood is difficult to implement. | November 2007 Status: INFORMATIONAL Autor: R. Sparks |
| RFC5058 Explicit Multicast (Xcast) Concepts and Options While traditional IP multicast schemes (RFC 1112) are scalable for very large multicast groups, they have scalability issues with a very large number of distinct multicast groups. This document describes Xcast (Explicit Multi-unicast), a new multicast scheme with complementary scaling properties: Xcast supports a very large number of small multicast sessions. Xcast achieves this by explicitly encoding the list of destinations in the data packets, instead of using a multicast group address. | November 2007 Status: EXPERIMENTAL Autor: R. Boivie, N. Feldman, Y. Imai, W. Livens, D. Ooms |
| RFC5059 Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM) This document specifies the Bootstrap Router (BSR) mechanism for the class of multicast routing protocols in the PIM (Protocol Independent Multicast) family that use the concept of a Rendezvous Point as a means for receivers to discover the sources that send to a particular multicast group. BSR is one way that a multicast router can learn the set of group-to-RP mappings required in order to function. The mechanism is dynamic, largely self-configuring, and robust to router failure. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: N. Bhaskar, A. Gall, J. Lingard, S. Venaas |
| RFC5060 Protocol Independent Multicast 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 the Protocol Independent Multicast (PIM) protocols: PIM-SM (Sparse Mode), BIDIR-PIM (Bidirectional), and PIM-DM (Dense Mode). This document is part of work in progress to obsolete RFC 2934, and is to be preferred where the two documents overlap. This document does not obsolete RFC 2934. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: R. Sivaramu, J. Lingard, D. McWalter, B. Joshi, A. Kessler |
| RFC5061 Stream Control Transmission Protocol (SCTP) Dynamic Address Reconfiguration A local host may have multiple points of attachment to the Internet, giving it a degree of fault tolerance from hardware failures. Stream Control Transmission Protocol (SCTP) (RFC 4960) was developed to take full advantage of such a multi-homed host to provide a fast failover and association survivability in the face of such hardware failures. This document describes an extension to SCTP that will allow an SCTP stack to dynamically add an IP address to an SCTP association, dynamically delete an IP address from an SCTP association, and to request to set the primary address the peer will use when sending to an endpoint. [STANDARDS-TRACK] | September 2007 Status: PROPOSED STANDARD Autor: R. Stewart, Q. Xie, M. Tuexen, S. Maruyama, M. Kozuka |
| RFC5062 Security Attacks Found Against the Stream Control Transmission Protocol (SCTP) and Current Countermeasures This document describes certain security threats to SCTP. It also describes ways to mitigate these threats, in particular by using techniques from the SCTP Specification Errata and Issues memo (RFC 4460). These techniques are included in RFC 4960, which obsoletes RFC 2960. It is hoped that this information will provide some useful background information for many of the newest requirements spelled out in the SCTP Specification Errata and Issues and included in RFC 4960. This memo provides information for the Internet community. | September 2007 Status: INFORMATIONAL Autor: R. Stewart, M. Tuexen, G. Camarillo |
| RFC5063 Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart This document describes extensions to the Resource Reservation Protocol (RSVP) Graceful Restart mechanisms defined in RFC 3473. The extensions enable the recovery of RSVP signaling state based on the Path message last sent by the node being restarted. | October 2007 Status: PROPOSED STANDARD Autor: A. Satyanarayana, R. Rahman |
| RFC5064 The Archived-At Message Header Field This memo defines a new email header field, Archived-At:, to provide a direct link to the archived form of an individual email message. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: M. Duerst |
| RFC5065 Autonomous System Confederations for BGP The Border Gateway Protocol (BGP) is an inter-autonomous system routing protocol designed for Transmission Control Protocol/Internet Protocol (TCP/IP) networks. BGP requires that all BGP speakers within a single autonomous system (AS) must be fully meshed. This represents a serious scaling problem that has been well documented in a number of proposals. | August 2007 Status: DRAFT STANDARD Autor: P. Traina, D. McPherson, J. Scudder |
| RFC5066 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB This document defines Management Information Base (MIB) modules for use with network management protocols in TCP/IP-based internets. This document describes extensions to the Ethernet-like Interfaces MIB and Medium Attachment Unit (MAU) MIB modules with a set of objects for managing Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3ah-2004 (note: IEEE Std 802.3ah-2004 has been integrated into IEEE Std 802.3- 2005). In addition, a set of objects is defined, describing cross- connect capability of a managed device with multi-layer (stacked) interfaces, extending the stack management objects in the Interfaces Group MIB and the Inverted Stack Table MIB modules. [STANDARDS-TRACK] | November 2007 Status: PROPOSED STANDARD Autor: E. Beili |
| RFC5067 Infrastructure ENUM Requirements This document provides requirements for "infrastructure" or "carrier" ENUM (E.164 Number Mapping), defined as the use of RFC 3761 technology to facilitate interconnection of networks for E.164 number addressed services, in particular but not restricted to VoIP (Voice over IP.) This memo provides information for the Internet community. | November 2007 Status: INFORMATIONAL Autor: S. Lind, P. Pfautz |
| RFC5068 Email Submission Operations: Access and Accountability Requirements Email has become a popular distribution service for a variety of socially unacceptable, mass-effect purposes. The most obvious ones include spam and worms. This note recommends conventions for the operation of email submission and transport services between independent operators, such as enterprises and Internet Service Providers. Its goal is to improve lines of accountability for controlling abusive uses of the Internet mail service. To this end, this document offers recommendations for constructive operational policies between independent operators of email submission and transmission services. | November 2007 Status: BEST CURRENT PRACTICE Autor: C. Hutzler, D. Crocker, P. Resnick, E. Allman, T. Finch |
| RFC5069 Security Threats and Requirements for Emergency Call Marking and Mapping This document reviews the security threats associated with the marking of signalling messages to indicate that they are related to an emergency, and with the process of mapping locations to Universal Resource Identifiers (URIs) that point to Public Safety Answering Points (PSAPs). This mapping occurs as part of the process of routing emergency calls through the IP network. | January 2008 Status: INFORMATIONAL Autor: T. Taylor, H. Tschofenig, H. Schulzrinne, M. Shanmugam |
| RFC5070 The Incident Object Description Exchange Format The Incident Object Description Exchange Format (IODEF) defines a data representation that provides a framework for sharing information commonly exchanged by Computer Security Incident Response Teams (CSIRTs) about computer security incidents. This document describes the information model for the IODEF and provides an associated data model specified with XML Schema. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: R. Danyliw, J. Meijer, Y. Demchenko |
| RFC5071 Dynamic Host Configuration Protocol Options Used by PXELINUX This document describes the use by PXELINUX of some DHCP Option Codes numbering from 208-211. This memo provides information for the Internet community. | December 2007 Status: INFORMATIONAL Autor: D. Hankins |
| RFC5072 IP Version 6 over PPP The Point-to-Point Protocol (PPP) 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. | September 2007 Status: DRAFT STANDARD Autor: S.Varada, D. Haskins, E. Allen |
| RFC5073 IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities It is highly desired, in several cases, to take into account Traffic Engineering (TE) node capabilities during Multi Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered Label Switched Path (TE-LSP) selection, such as, for instance, the capability to act as a branch Label Switching Router (LSR) of a Point-To-MultiPoint (P2MP) LSP. This requires advertising these capabilities within the Interior Gateway Protocol (IGP). For that purpose, this document specifies Open Shortest Path First (OSPF) and Intermediate System-Intermediate System (IS-IS) traffic engineering extensions for the advertisement of control plane and data plane traffic engineering node capabilities. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: J.P. Vasseur, J.L. Le Roux |
| RFC5074 DNSSEC Lookaside Validation (DLV) DNSSEC Lookaside Validation (DLV) is a mechanism for publishing DNS Security (DNSSEC) trust anchors outside of the DNS delegation chain. It allows validating resolvers to validate DNSSEC-signed data from zones whose ancestors either aren't signed or don't publish Delegation Signer (DS) records for their children. This memo provides information for the Internet community. | November 2007 Status: INFORMATIONAL Autor: S. Weiler |
| RFC5075 IPv6 Router Advertisement Flags Option The IPv6 Neighbor Discovery's Router Advertisement message contains an 8-bit field reserved for single-bit flags. Several protocols have reserved flags in this field and others are preparing to reserve a sufficient number of flags to exhaust the field. This document defines an option to the Router Advertisement message that expands the available number of flag bits available. [STANDARDS-TRACK] | November 2007 Status: PROPOSED STANDARD Autor: B. Haberman, R. Hinden |
| RFC5076 ENUM Validation Information Mapping for the Extensible Provisioning Protocol This document describes an Extensible Provisioning Protocol (EPP) extension framework for mapping information about the validation process that has been applied for the E.164 number (or number range) that the E.164 Number Mapping (ENUM) domain name is based on. Specified in the Extensible Markup Language (XML), this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of ENUM Domain Names. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: B. Hoeneisen |
| RFC5077 Transport Layer Security (TLS) Session Resumption without Server-Side State This document describes a mechanism that enables the Transport Layer Security (TLS) server to resume sessions and avoid keeping per-client session state. The TLS server encapsulates the session state into a ticket and forwards it to the client. The client can subsequently resume a session using the obtained ticket. This document obsoletes RFC 4507. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: J. Salowey, H. Zhou, P. Eronen, H. Tschofenig |
| RFC5078 IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees Timeline RFC 3777 defines the Nominations and Recall Committee's (NomCom's) operation, and includes a sample timeline for major steps in the NomCom process that meets the minimum normative requirements for the process. Recent NomComs have been scheduling based on the sample timeline, and the chairs of the last three NomComs -- Danny McPherson (2004-2005), Ralph Droms (2005-2006), and Andrew Lange (2006-2007) -- have all reported that this timeline is very aggressive and suggested starting earlier. This document restructures the sample timeline, but makes no normative process changes. This memo provides information for the Internet community. | October 2007 Status: INFORMATIONAL Autor: S. Dawkins |
| RFC5079 Rejecting Anonymous Requests in the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) allows for users to make anonymous calls. However, users receiving such calls have the right to reject them because they are anonymous. SIP has no way to indicate to the caller that the reason for call rejection was that the call was anonymous. Such an indication is useful to allow the call to be retried without anonymity. This specification defines a new SIP response code for this purpose. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC5080 Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested Fixes This document describes common issues seen in Remote Authentication Dial In User Service (RADIUS) implementations and suggests some fixes. Where applicable, ambiguities and errors in previous RADIUS specifications are clarified. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: D. Nelson, A. DeKok |
| RFC5081 Using OpenPGP Keys for Transport Layer Security (TLS) Authentication This memo proposes extensions to the Transport Layer Security (TLS) protocol to support the OpenPGP key format. The extensions discussed here include a certificate type negotiation mechanism, and the required modifications to the TLS Handshake Protocol. This memo defines an Experimental Protocol for the Internet community. | November 2007 Status: EXPERIMENTAL Autor: N. Mavrogiannopoulos |
| RFC5082 The Generalized TTL Security Mechanism (GTSM) The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) to verify whether the packet was originated by an adjacent node on a connected link has been used in many recent protocols. This document generalizes this technique. This document obsoletes Experimental RFC 3682. [STANDARDS-TRACK] | October 2007 Status: PROPOSED STANDARD Autor: V. Gill, J. Heasley, D. Meyer, P. Savola, C. Pignataro |
| RFC5083 Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type This document describes an additional content type for the Cryptographic Message Syntax (CMS). The authenticated-enveloped-data content type is intended for use with authenticated encryption modes. All of the various key management techniques that are supported in the CMS enveloped-data content type are also supported by the CMS authenticated-enveloped-data content type. [STANDARDS-TRACK] | November 2007 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC5084 Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS) This document specifies the conventions for using the AES-CCM and the AES-GCM authenticated encryption algorithms with the Cryptographic Message Syntax (CMS) authenticated-enveloped-data content type. [STANDARDS-TRACK] | November 2007 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC5085 Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires This document describes Virtual Circuit Connectivity Verification (VCCV), which provides a control channel that is associated with a pseudowire (PW), as well as the corresponding operations and management functions (such as connectivity verification) to be used over that control channel. VCCV applies to all supported access circuit and transport types currently defined for PWs. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: T. Nadeau, C. Pignataro |
| RFC5086 Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN) This document describes a method for encapsulating structured (NxDS0) Time Division Multiplexed (TDM) signals as pseudowires over packet-switching networks (PSNs). In this regard, it complements similar work for structure-agnostic emulation of TDM bit-streams (see RFC 4553). This memo provides information for the Internet community. | December 2007 Status: INFORMATIONAL Autor: A. Vainshtein, I. Sasson, E. Metz, T. Frost, P. Pate |
| RFC5087 Time Division Multiplexing over IP (TDMoIP) Time Division Multiplexing over IP (TDMoIP) is a structure-aware method for transporting Time Division Multiplexed (TDM) signals using pseudowires (PWs). Being structure-aware, TDMoIP is able to ensure TDM structure integrity, and thus withstand network degradations better than structure-agnostic transport. Structure-aware methods can distinguish individual channels, enabling packet loss concealment and bandwidth conservation. Accessibility of TDM signaling facilitates mechanisms that exploit or manipulate signaling. This memo provides information for the Internet community. | December 2007 Status: INFORMATIONAL Autor: Y(J). Stein, R. Shashoua, R. Insler, M. Anavi |
| RFC5088 OSPF Protocol Extensions for Path Computation Element (PCE) Discovery There are various circumstances where it is highly desirable for a Path Computation Client (PCC) to be able to dynamically and automatically discover a set of Path Computation Elements (PCEs), along with information that can be used by the PCC for PCE selection. When the PCE is a Label Switching Router (LSR) participating in the Interior Gateway Protocol (IGP), or even a server participating passively in the IGP, a simple and efficient way to announce PCEs consists of using IGP flooding. For that purpose, this document defines extensions to the Open Shortest Path First (OSPF) routing protocol for the advertisement of PCE Discovery information within an OSPF area or within the entire OSPF routing domain. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: JL. Le Roux, JP. Vasseur, Y. Ikejiri, R. Zhang |
| RFC5089 IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery There are various circumstances where it is highly desirable for a Path Computation Client (PCC) to be able to dynamically and automatically discover a set of Path Computation Elements (PCEs), along with information that can be used by the PCC for PCE selection. When the PCE is a Label Switching Router (LSR) participating in the Interior Gateway Protocol (IGP), or even a server participating passively in the IGP, a simple and efficient way to announce PCEs consists of using IGP flooding. For that purpose, this document defines extensions to the Intermediate System to Intermediate System (IS-IS) routing protocol for the advertisement of PCE Discovery information within an IS-IS area or within the entire IS-IS routing domain. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: JL. Le Roux, JP. Vasseur, Y. Ikejiri, R. Zhang |
| RFC5090 RADIUS Extension for Digest Authentication This document defines an extension to the Remote Authentication Dial-In User Service (RADIUS) protocol to enable support of Digest Authentication, for use with HTTP-style protocols like the Session Initiation Protocol (SIP) and HTTP. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: B. Sterman, D. Sadolevsky, D. Schwartz, D. Williams, W. Beck |
| RFC5091 Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 Cryptosystems This document describes the algorithms that implement Boneh-Franklin (BF) and Boneh-Boyen (BB1) Identity-based Encryption. This document is in part based on IBCS #1 v2 of Voltage Security's Identity-based Cryptography Standards (IBCS) documents, from which some irrelevant sections have been removed to create the content of this document. This memo provides information for the Internet community. | December 2007 Status: INFORMATIONAL Autor: X. Boyen, L. Martin |
| RFC5092 IMAP URL Scheme IMAP (RFC 3501) is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mailing list archives as well as private and shared message stores. This document defines a URL scheme for referencing objects on an IMAP server. | November 2007 Status: PROPOSED STANDARD Autor: A. Melnikov, C. Newman |
| RFC5093 BT's eXtended Network Quality RTP Control Protocol Extended Reports (RTCP XR XNQ) This document describes an RTCP XR report block, which reports packet transport parameters. The report block was developed by BT for pre-standards use in BT's next-generation network. This document has been produced to describe the report block in sufficient detail to register the block type with IANA in accordance with the Specification Required policy of RFC 3611. This specification does not standardise the new report block for use outside BT's network. This memo provides information for the Internet community. | December 2007 Status: INFORMATIONAL Autor: G. Hunt |
| RFC5094 Mobile IPv6 Vendor Specific Option There is a need for vendor-specific extensions to Mobility Header messages so that Mobile IPv6 vendors are able to extend the protocol for research or deployment purposes. This document defines a new vendor-specific mobility option. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: V. Devarapalli, A. Patel, K. Leung |
| RFC5095 Deprecation of Type 0 Routing Headers in IPv6 The functionality provided by IPv6's Type 0 Routing Header can be exploited in order to achieve traffic amplification over a remote path for the purposes of generating denial-of-service traffic. This document updates the IPv6 specification to deprecate the use of IPv6 Type 0 Routing Headers, in light of this security concern. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: J. Abley, P. Savola, G. Neville-Neil |
| RFC5096 Mobile IPv6 Experimental Messages This document defines a new experimental Mobility Header message and a Mobility option that can be used for experimental extensions to the Mobile IPv6 protocol. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: V. Devarapalli |
| RFC5097 MIB for the UDP-Lite protocol This document specifies a Management Information Base (MIB) module for the Lightweight User Datagram Protocol (UDP-Lite). It defines a set of new MIB objects to characterise the behaviour and performance of transport layer endpoints deploying UDP-Lite. UDP-Lite resembles UDP, but differs from the semantics of UDP by the addition of a single option. This adds the capability for variable-length data checksum coverage, which can benefit a class of applications that prefer delivery of (partially) corrupted datagram payload data in preference to discarding the datagram. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: G. Renker, G. Fairhurst |
| RFC5098 Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs) 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 Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: G. Beacham, S. Kumar, S. Channabasappa |
| RFC5101 Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information This document specifies the IP Flow Information Export (IPFIX) protocol that serves for transmitting IP Traffic Flow information over the network. In order to transmit IP Traffic Flow information from an Exporting Process to an information Collecting Process, a common representation of flow data and a standard means of communicating them is required. This document describes how the IPFIX Data and Template Records are carried over a number of transport protocols from an IPFIX Exporting Process to an IPFIX Collecting Process. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: B. Claise |
| RFC5102 Information Model for IP Flow Information Export This memo defines an information model for the IP Flow Information eXport (IPFIX) protocol. It is used by the IPFIX protocol for encoding measured traffic information and information related to the traffic Observation Point, the traffic Metering Process, and the Exporting Process. Although developed for the IPFIX protocol, the model is defined in an open way that easily allows using it in other protocols, interfaces, and applications. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: J. Quittek, S. Bryant, B. Claise, P. Aitken, J. Meyer |
| RFC5103 Bidirectional Flow Export Using IP Flow Information Export (IPFIX) This document describes an efficient method for exporting bidirectional flow (Biflow) information using the IP Flow Information Export (IPFIX) protocol, representing each Biflow using a single Flow Record. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: B. Trammell, E. Boschi |
| RFC5104 Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF) This document specifies a few extensions to the messages defined in the Audio-Visual Profile with Feedback (AVPF). They are helpful primarily in conversational multimedia scenarios where centralized multipoint functionalities are in use. However, some are also usable in smaller multicast environments and point-to-point calls. | February 2008 Status: PROPOSED STANDARD Autor: S. Wenger, U. Chandra, M. Westerlund, B. Burman |
| RFC5105 ENUM Validation Token Format Definition An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes a signed XML data format -- the Validation Token -- with which Validation Entities can convey successful completion of a validation procedure in a secure fashion. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: O. Lendl |
| RFC5106 The Extensible Authentication Protocol-Internet Key Exchange Protocol version 2 (EAP-IKEv2) Method This document specifies EAP-IKEv2, an Extensible Authentication Protocol (EAP) method that is based on the Internet Key Exchange (IKEv2) protocol. EAP-IKEv2 provides mutual authentication and session key establishment between an EAP peer and an EAP server. It supports authentication techniques that are based on passwords, high-entropy shared keys, and public key certificates. EAP-IKEv2 further provides support for cryptographic ciphersuite negotiation, hash function agility, identity confidentiality (in certain modes of operation), fragmentation, and an optional "fast reconnect" mode. This memo defines an Experimental Protocol for the Internet community. | February 2008 Status: EXPERIMENTAL Autor: H. Tschofenig, D. Kroeselberg, A. Pashalidis, Y. Ohba, F. Bersani |
| RFC5107 DHCP Server Identifier Override Suboption This memo defines a new suboption of the DHCP relay information option that allows the DHCP relay to specify a new value for the Server Identifier option, which is inserted by the DHCP Server. This allows the DHCP relay to act as the actual DHCP server such that RENEW DHCPREQUESTs will come to the relay instead of going to the server directly. This gives the relay the opportunity to include the Relay Agent option with appropriate suboptions even on DHCP RENEW messages. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: R. Johnson, J. Kumarasamy, K. Kinnear, M. Stapp |
| RFC5109 RTP Payload Format for Generic Forward Error Correction This document specifies a payload format for generic Forward Error Correction (FEC) for media data encapsulated in RTP. It is based on the exclusive-or (parity) operation. The payload format described in this document allows end systems to apply protection using various protection lengths and levels, in addition to using various protection group sizes to adapt to different media and channel characteristics. It enables complete recovery of the protected packets or partial recovery of the critical parts of the payload depending on the packet loss situation. This scheme is completely compatible with non-FEC-capable hosts, so the receivers in a multicast group that do not implement FEC can still work by simply ignoring the protection data. This specification obsoletes RFC 2733 and RFC 3009. The FEC specified in this document is not backward compatible with RFC 2733 and RFC 3009. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: A. Li |
| RFC5110 Overview of the Internet Multicast Routing Architecture This document describes multicast routing architectures that are currently deployed on the Internet. This document briefly describes those protocols and references their specifications. | January 2008 Status: INFORMATIONAL Autor: P. Savola |
| RFC5111 Experiment in Exploratory Group Formation within the Internet Engineering Task Force (IETF) This document describes an RFC 3933 experiment in the Working Group formation process, known as the Exploratory Group. Exploratory Groups may be created as the first step toward Working Group formation, or as an intermediate step between a Birds of a Feather (BOF) session and Working Group creation. Exploratory Groups are focused on completion of prerequisites for Working Group formation, and as a result they have a short life-time, with limited opportunities for milestone extension. This memo defines an Experimental Protocol for the Internet community. | January 2008 Status: EXPERIMENTAL Autor: B. Aboba, L. Dondeti |
| RFC5112 The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp) The Session Initiation Protocol (SIP) is a text-based protocol for initiating and managing communication sessions. The protocol is extended by the SIP-events notification framework to provide subscriptions and notifications of SIP events. One example of such event notification mechanism is presence, which is expressed in XML documents called presence documents. SIP can be compressed by using Signaling Compression (SigComp), which is enhanced by using the SIP/ Session Description Protocol (SDP) dictionary to achieve better compression rates. However, the SIP/SDP dictionary is not able to increase the compression factor of (typically lengthy) presence documents. This memo defines the presence-specific static dictionary that SigComp can use in order to compress presence documents to achieve higher efficiency. The dictionary is compression-algorithm independent. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: M. Garcia-Martin |
| RFC5113 Network Discovery and Selection Problem When multiple access networks are available, users may have difficulty in selecting which network to connect to and how to authenticate with that network. This document defines the network discovery and selection problem, dividing it into multiple sub- problems. Some constraints on potential solutions are outlined, and the limitations of several solutions (including existing ones) are discussed. This memo provides information for the Internet community. | January 2008 Status: INFORMATIONAL Autor: J. Arkko, B. Aboba, J. Korhonen, F. Bari |
| RFC5114 Additional Diffie-Hellman Groups for Use with IETF Standards This document describes eight Diffie-Hellman groups that can be used in conjunction with IETF protocols to provide security for Internet communications. The groups allow implementers to use the same groups with a variety of security protocols, e.g., SMIME, Secure SHell (SSH), Transport Layer Security (TLS), and Internet Key Exchange (IKE). | January 2008 Status: INFORMATIONAL Autor: M. Lepinski, S. Kent |
| RFC5115 Telephony Routing over IP (TRIP) Attribute for Resource Priority This document defines a new attribute for the Telephony Routing over IP (TRIP) protocol. The attribute associates protocols/services in the PSTN offering authorized prioritization during call setup that are reachable through a TRIP gateway. Current examples of preferential service in the Public Switched Telephone Network (PSTN) are Government Emergency Telecommunications Service (GETS) in the U.S. and Government Telephone Preference Scheme (GTPS) in the U.K. The proposed attribute for TRIP is based on the NameSpace.Value tuple defined for the SIP Resource-Priority field. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: K. Carlberg, P. O'Hanlon |
| RFC5116 An Interface and Algorithms for Authenticated Encryption This document defines algorithms for Authenticated Encryption with Associated Data (AEAD), and defines a uniform interface and a registry for such algorithms. The interface and registry can be used as an application-independent set of cryptoalgorithm suites. This approach provides advantages in efficiency and security, and promotes the reuse of crypto implementations. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: D. McGrew |
| RFC5117 RTP Topologies This document discusses multi-endpoint topologies used in Real-time Transport Protocol (RTP)-based environments. In particular, centralized topologies commonly employed in the video conferencing industry are mapped to the RTP terminology. This memo provides information for the Internet community. | January 2008 Status: INFORMATIONAL Autor: M. Westerlund, S. Wenger |
| RFC5118 Session Initiation Protocol (SIP) Torture Test Messages for Internet Protocol Version 6 (IPv6) This document provides examples of Session Initiation Protocol (SIP) test messages designed to exercise and "torture" the code of an IPv6-enabled SIP implementation. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: V. Gurbani, C. Boulton, R. Sparks |
| RFC5119 A Uniform Resource Name (URN) Namespace for the Society of Motion Picture and Television Engineers (SMPTE) This document describes a Uniform Resource Name (URN) namespace for the Society of Motion Picture and Television Engineers (SMPTE) for naming persistent resources that SMPTE produces or manages. A subnamespace for Universal Labels is specifically described. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: T. Edwards |
| RFC5120 M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs) This document describes an optional mechanism within Intermediate System to Intermediate Systems (IS-ISs) used today by many ISPs for IGP routing within their clouds. This document describes how to run, within a single IS-IS domain, a set of independent IP topologies that we call Multi-Topologies (MTs). This MT extension can be used for a variety of purposes, such as an in-band management network "on top" of the original IGP topology, maintaining separate IGP routing domains for isolated multicast or IPv6 islands within the backbone, or forcing a subset of an address space to follow a different topology. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: T. Przygienda, N. Shen, N. Sheth |
| RFC5121 Transmission of IPv6 via the IPv6 Convergence Sublayer over IEEE 802.16 Networks IEEE Std 802.16 is an air interface specification for fixed and mobile Broadband Wireless Access Systems. Service-specific convergence sublayers to which upper-layer protocols interface are a part of the IEEE 802.16 MAC (Medium Access Control). The Packet convergence sublayer (CS) is used for the transport of all packet- based protocols such as Internet Protocol (IP) and IEEE 802.3 LAN/MAN CSMA/CD Access Method (Ethernet). IPv6 packets can be sent and received via the IP-specific part of the Packet CS. This document specifies the addressing and operation of IPv6 over the IP-specific part of the Packet CS for hosts served by a network that utilizes the IEEE Std 802.16 air interface. It recommends the assignment of a unique prefix (or prefixes) to each host and allows the host to use multiple identifiers within that prefix, including support for randomly generated interface identifiers. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: B. Patil, F. Xia, B. Sarikaya, JH. Choi, S. Madanapalli |
| RFC5122 Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP) This document defines the use of Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in identifying or interacting with entities that can communicate via the Extensible Messaging and Presence Protocol (XMPP). [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC5123 Considerations in Validating the Path in BGP This document examines the implications of hop-by-hop forwarding, route aggregation, and route filtering on the concept of validation within a BGP Autonomous System (AS) Path. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: R. White, B. Akyol |
| RFC5124 Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF) An RTP profile (SAVP) for secure real-time communications and another profile (AVPF) to provide timely feedback from the receivers to a sender are defined in RFC 3711 and RFC 4585, respectively. This memo specifies the combination of both profiles to enable secure RTP communications with feedback. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: J. Ott, E. Carrara |
| RFC5125 Reclassification of RFC 3525 to Historic This document reclassifies RFC 3525, Gateway Control Protocol Version 1, to Historic Status. This memo also obsoletes RFC 3525. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: T. Taylor |
| RFC5126 CMS Advanced Electronic Signatures (CAdES) 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. | March 2008 Status: INFORMATIONAL Autor: D. Pinkas, N. Pope, J. Ross |
| RFC5127 Aggregation of DiffServ Service Classes In the core of a high-capacity network, service differentiation may still be needed to support applications' utilization of the network. Applications with similar traffic characteristics and performance requirements are mapped into Diffserv service classes based on end- to-end behavior requirements of the applications. However, some network segments may be configured in such a way that a single forwarding treatment may satisfy the traffic characteristics and performance requirements of two or more service classes. In these cases, it may be desirable to aggregate two or more Diffserv service classes into a single forwarding treatment. This document provides guidelines for the aggregation of Diffserv service classes into forwarding treatments. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: K. Chan, J. Babiarz, F. Baker |
| RFC5128 State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) This memo documents the various methods known to be in use by applications to establish direct communication in the presence of Network Address Translators (NATs) at the current time. Although this memo is intended to be mainly descriptive, the Security Considerations section makes some purely advisory recommendations about how to deal with security vulnerabilities the applications could inadvertently create when using the methods described. This memo covers NAT traversal approaches used by both TCP- and UDP-based applications. This memo is not an endorsement of the methods described, but merely an attempt to capture them in a document. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: P. Srisuresh, B. Ford, D. Kegel |
| RFC5129 Explicit Congestion Marking in MPLS RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may be encoded in the EXP field, while other uses of that field are not precluded. RFC 3270 makes no statement about how Explicit Congestion Notification (ECN) marking might be encoded in the MPLS header. This document defines how an operator might define some of the EXP codepoints for explicit congestion notification, without precluding other uses. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: B. Davie, B. Briscoe, J. Tay |
| RFC5130 A Policy Control Mechanism in IS-IS Using Administrative Tags This document describes an extension to the IS-IS protocol to add operational capabilities that allow for ease of management and control over IP prefix distribution within an IS-IS domain. This document enhances the IS-IS protocol by extending the information that an Intermediate System (IS) router can place in Link State Protocol (LSP) Data Units for policy use. This extension will provide operators with a mechanism to control IP prefix distribution throughout multi-level IS-IS domains. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: S. Previdi, M. Shand, C. Martin |
| RFC5131 A MIB Textual Convention for Language Tags This MIB module defines a textual convention to represent BCP 47 language tags. The intent is that this textual convention will be imported and used in MIB modules that would otherwise define their own representation. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: D. McWalter |
| RFC5132 IP Multicast 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 objects used for managing multicast function, independent of the specific multicast protocol(s) in use. This document obsoletes RFC 2932. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: D. McWalter, D. Thaler, A. Kessler |
| RFC5133 Terminal Endpoint Identifier (TEI) Query Request Number Change The Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer (IUA) Protocol, described in RFC 4233, defines the message type of Terminal Endpoint Identifier (TEI) Query Request messages as 5. However, this number is already being used by the Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions (DUA) to the IUA Protocol described in RFC 4129. This document updates RFC 4233 such that the message type of TEI Query Request messages is 8. [STANDARDS-TRACK] | December 2007 Status: PROPOSED STANDARD Autor: M. Tuexen, K. Morneault |
| RFC5134 A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards This document describes URN namespaces that will identify various objects within the EPCglobal system for identifying products within ecommerce and supply chain management applications. This memo provides information for the Internet community. | January 2008 Status: INFORMATIONAL Autor: M. Mealling |
| RFC5135 IP Multicast Requirements for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT) This document specifies requirements for a for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT) that support Any Source IP Multicast or Source-Specific IP Multicast. An IP multicast-capable NAT device that adheres to the requirements of this document can optimize the operation of IP multicast applications that are generally unaware of IP multicast NAT devices. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 2008 Status: BEST CURRENT PRACTICE Autor: D. Wing, T. Eckert |
| RFC5136 Defining Network Capacity Measuring capacity is a task that sounds simple, but in reality can be quite complex. In addition, the lack of a unified nomenclature on this subject makes it increasingly difficult to properly build, test, and use techniques and tools built around these constructs. This document provides definitions for the terms 'Capacity' and 'Available Capacity' related to IP traffic traveling between a source and destination in an IP network. By doing so, we hope to provide a common framework for the discussion and analysis of a diverse set of current and future estimation techniques. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: P. Chimento, J. Ishac |
| RFC5137 ASCII Escaping of Unicode Characters There are a number of circumstances in which an escape mechanism is needed in conjunction with a protocol to encode characters that cannot be represented or transmitted directly. With ASCII coding, the traditional escape has been either the decimal or hexadecimal numeric value of the character, written in a variety of different ways. The move to Unicode, where characters occupy two or more octets and may be coded in several different forms, has further complicated the question of escapes. This document discusses some options now in use and discusses considerations for selecting one for use in new IETF protocols, and protocols that are now being internationalized. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 2008 Status: BEST CURRENT PRACTICE Autor: J. Klensin |
| RFC5138 A Uniform Resource Name (URN) Namespace for the Commission for the Management and Application of Geoscience Information (CGI) This document describes a URN (Uniform Resource Name) namespace that is engineered by the Commission for the Management and Application of Geoscience Information (CGI) for naming (i) persistent resources published by the CGI and (ii) resources published by organizations that wish them to be used in the context of services conforming to protocols and agreements issued by CGI. The formal Namespace Identifier (NID) is "cgi". This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: S. Cox |
| RFC5139 Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO) This document defines an XML format for the representation of civic location. This format is designed for use with Presence Information Data Format Location Object (PIDF-LO) documents and replaces the civic location format in RFC 4119. The format is based on the civic address definition in PIDF-LO, but adds several new elements based on the civic types defined for Dynamic Host Configuration Protocol (DHCP), and adds a hierarchy to address complex road identity schemes. The format also includes support for the xml:lang language tag and restricts the types of elements where appropriate. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: M. Thomson, J. Winterbottom |
| RFC5140 A Telephony Gateway REgistration Protocol (TGREP) This document describes the Telephony Gateway Registration Protocol (TGREP) for registration of telephony prefixes supported by telephony gateways and soft switches. The registration mechanism can also be used to export resource information. The prefix and resource information can then be passed on to a Telephony Routing over IP (TRIP) Location Server, which in turn can propagate that routing information within and between Internet Telephony Administrative Domains (ITADs). TGREP shares a lot of similarities with the TRIP protocol. It has similar procedures and finite state machine for session establishment. It also shares the same format for messages and a subset of attributes with TRIP. [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: M. Bangalore, R. Kumar, J. Rosenberg, H. Salama, D.N. Shah |
| RFC5141 A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO) This document describes a Uniform Resource Name Namespace Identification (URN NID) for the International Organization for Standardization (ISO). This URN NID is intended for use for the identification of persistent resources published by the ISO standards body (including documents, document metadata, extracted resources such as standard schemata and standard value sets, and other resources). This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: J. Goodwin, H. Apel |
| RFC5142 Mobility Header Home Agent Switch Message This document specifies a new Mobility Header message type that can be used between a home agent and mobile node to signal to a mobile node that it should acquire a new home agent. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: B. Haley, V. Devarapalli, H. Deng, J. Kempf |
| RFC5143 Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation Service over MPLS (CEM) Encapsulation This document describes a historical method for encapsulating Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Path signals for transport across packet-switched networks (PSNs). The PSNs explicitly supported by this document include MPLS and IP. Note that RFC 4842 describes the standards-track protocol for this functionality, and new implementations must use RFC 4842 rather than this document except when interoperability with older implementations is desired. This memo defines a Historic Document for the Internet community. | February 2008 Status: HISTORIC Autor: A. Malis, J. Brayley, J. Shirron, L. Martini, S. Vogelsang |
| RFC5144 A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS) This document describes a lightweight domain availability service using the Internet Registry Information Service (IRIS) framework and the data model of the IRIS Domain Registry (DREG) service. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: A. Newton, M. Sanz |
| RFC5145 Framework for MPLS-TE to GMPLS Migration The migration from Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) to Generalized MPLS (GMPLS) is the process of evolving an MPLS-TE control plane to a GMPLS control plane. An appropriate migration strategy will be selected based on various factors including the service provider's network deployment plan, customer demand, and operational policy. | March 2008 Status: INFORMATIONAL Autor: K. Shiomoto |
| RFC5146 Interworking Requirements to Support Operation of MPLS-TE over GMPLS Networks Operation of a Multiprotocol Label Switching (MPLS) traffic engineering (TE) network as a client network to a Generalized MPLS (GMPLS) network has enhanced operational capabilities compared to those provided by a coexistent protocol model (i.e., operation of MPLS-TE over an independently managed transport layer). | March 2008 Status: INFORMATIONAL Autor: K. Kumaki |
| RFC5147 URI Fragment Identifiers for the text/plain Media Type This memo defines URI fragment identifiers for text/plain MIME entities. These fragment identifiers make it possible to refer to parts of a text/plain MIME entity, either identified by character position or range, or by line position or range. Fragment identifiers may also contain information for integrity checks to make them more robust. [STANDARDS-TRACK] | April 2008 Status: PROPOSED STANDARD Autor: E. Wilde, M. Duerst |
| RFC5148 Jitter Considerations in Mobile Ad Hoc Networks (MANETs) This document provides recommendations for jittering (randomly modifying timing) of control traffic transmissions in Mobile Ad hoc NETwork (MANET) routing protocols to reduce the probability of transmission collisions. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: T. Clausen, C. Dearlove, B. Adamson |
| RFC5149 Service Selection for Mobile IPv6 In some Mobile IPv6 deployments, identifying the mobile node or the mobility service subscriber is not enough to distinguish between multiple services possibly provisioned to the said mobile node and its mobility service subscription. A capability to specify different services in addition to the mobile node identity can be leveraged to provide flexibility for mobility service providers on provisioning multiple services to one mobility service subscription. This document describes a Service Selection Mobility Option for both conventional Mobile IPv6 and Proxy Mobile IPv6 that is intended to assist home agents to make a specific service selection for the mobility service subscription during the binding registration procedure. This memo provides information for the Internet community. | February 2008 Status: INFORMATIONAL Autor: J. Korhonen, U. Nilsson, V. Devarapalli |
| RFC5150 Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE) In certain scenarios, there may be a need to combine several Generalized Multiprotocol Label Switching (GMPLS) Label Switched Paths (LSPs) such that a single end-to-end (e2e) LSP is realized and all traffic from one constituent LSP is switched onto the next LSP. We will refer to this as "LSP stitching", the key requirement being that a constituent LSP not be allocated to more than one e2e LSP. The constituent LSPs will be referred to as "LSP segments" (S-LSPs). | February 2008 Status: PROPOSED STANDARD Autor: A. Ayyangar, K. Kompella, JP. Vasseur, A. Farrel |
| RFC5151 Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions This document describes procedures and protocol extensions for the use of Resource Reservation Protocol-Traffic Engineering (RSVP-TE) signaling in Multiprotocol Label Switching-Traffic Engineering (MPLS-TE) packet networks and Generalized MPLS (GMPLS) packet and non-packet networks to support the establishment and maintenance of Label Switched Paths that cross domain boundaries. | February 2008 Status: PROPOSED STANDARD Autor: A. Farrel, A. Ayyangar, JP. Vasseur |
| RFC5152 A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs) This document specifies a per-domain path computation technique for establishing inter-domain Traffic Engineering (TE) Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Label Switched Paths (LSPs). In this document, a domain refers to a collection of network elements within a common sphere of address management or path computational responsibility such as Interior Gateway Protocol (IGP) areas and Autonomous Systems. | February 2008 Status: PROPOSED STANDARD Autor: JP. Vasseur, A. Ayyangar, R. Zhang |
| RFC5153 IP Flow Information Export (IPFIX) Implementation Guidelines The IP Flow Information Export (IPFIX) protocol defines how IP Flow information can be exported from routers, measurement probes, or other devices. This document provides guidelines for the implementation and use of the IPFIX protocol. Several sets of guidelines address Template management, transport-specific issues, implementation of Exporting and Collecting Processes, and IPFIX implementation on middleboxes (such as firewalls, network address translators, tunnel endpoints, packet classifiers, etc.). This memo provides information for the Internet community. | April 2008 Status: INFORMATIONAL Autor: E. Boschi, L. Mark, J. Quittek, M. Stiemerling, P. Aitken |
| RFC5154 IP over IEEE 802.16 Problem Statement and Goals This document specifies problems in running IP over IEEE 802.16 networks by identifying specific gaps in the IEEE 802.16 Media Access Control (MAC) for IPv4 and IPv6 support. This document also provides an overview of IEEE 802.16 network characteristics and convergence sublayers. Common terminology used for the base guideline while defining the solution framework is also presented. This memo provides information for the Internet community. | April 2008 Status: INFORMATIONAL Autor: J. Jee, S. Madanapalli, J. Mandin |
| RFC5155 DNS Security (DNSSEC) Hashed Authenticated Denial of Existence The Domain Name System Security (DNSSEC) Extensions introduced the NSEC resource record (RR) for authenticated denial of existence. This document introduces an alternative resource record, NSEC3, which similarly provides authenticated denial of existence. However, it also provides measures against zone enumeration and permits gradual expansion of delegation-centric zones. [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: B. Laurie, G. Sisson, R. Arends, D. Blacka |
| RFC5156 Special-Use IPv6 Addresses This document is a compilation of special IPv6 addresses defined in other RFCs. It can be used as a checklist of invalid routing prefixes for developing filtering policies for routes and IP packets. It does not discuss addresses that are assigned to operators and users through the Regional Internet Registries. This memo provides information for the Internet community. | April 2008 Status: INFORMATIONAL Autor: M. Blanchet |
| RFC5157 IPv6 Implications for Network Scanning The much larger default 64-bit subnet address space of IPv6 should in principle make traditional network (port) scanning techniques used by certain network worms or scanning tools less effective. While traditional network scanning probes (whether by individuals or automated via network worms) may become less common, administrators should be aware that attackers may use other techniques to discover IPv6 addresses on a target network, and thus they should also be aware of measures that are available to mitigate them. This informational document discusses approaches that administrators could take when planning their site address allocation and management strategies as part of a defence-in-depth approach to network security. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: T. Chown |
| RFC5158 6to4 Reverse DNS Delegation Specification This memo describes the service mechanism for entering a delegation of DNS servers that provide reverse lookup of 6to4 IPv6 addresses into the 6to4 reverse zone file. The mechanism is based on a conventional DNS delegation service interface, allowing the service client to enter the details of a number of DNS servers for the delegated domain. In the context of a 6to4 reverse delegation, the client is primarily authenticated by its source address used in the delegation request, and is authorized to use the function if its IPv6 address prefix corresponds to an address from within the requested 6to4 delegation address block. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: G. Huston |
| RFC5159 Session Description Protocol (SDP) Attributes for Open Mobile Alliance (OMA) Broadcast (BCAST) Service and Content Protection This document provides descriptions of Session Description Protocol (SDP) attributes used by the Open Mobile Alliance's Broadcast Service and Content Protection specification. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: L. Dondeti, A. Jerichow |
| RFC5160 Considerations of Provider-to-Provider Agreements for Internet-Scale Quality of Service (QoS) This memo analyzes provider-to-provider Quality of Service (QoS) agreements suitable for a global QoS-enabled Internet. It defines terminology relevant to inter-domain QoS models. It proposes a new concept denoted by Meta-QoS-Class (MQC). This concept could potentially drive and federate the way QoS inter-domain relationships are built between providers. It opens up new perspectives for a QoS- enabled Internet that retains, as much as possible, the openness of the existing best-effort Internet. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: P. Levis, M. Boucadair |
| RFC5161 The IMAP ENABLE Extension Most IMAP extensions are used by the client when it wants to and the server supports it. However, a few extensions require the server to know whether a client supports that extension. The ENABLE extension allows an IMAP client to say which extensions it supports. [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: A. Gulbrandsen, A. Melnikov |
| RFC5162 IMAP4 Extensions for Quick Mailbox Resynchronization This document defines an IMAP4 extension, which gives an IMAP client the ability to quickly resynchronize any previously opened mailbox as part of the SELECT command, without the need for server-side state or additional client round-trips. This extension also introduces a new response that allows for a more compact representation of a list of expunged messages (and always includes the Unique Identifiers (UIDs) expunged). [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: A. Melnikov, D. Cridland, C. Wilson |
| RFC5163 Extension Formats for Unidirectional Lightweight Encapsulation (ULE) and the Generic Stream Encapsulation (GSE) This document describes a set of Extension Headers for the Unidirectional Lightweight Encapsulation (ULE), RFC 4326. | April 2008 Status: PROPOSED STANDARD Autor: G. Fairhurst, B. Collini-Nocker |
| RFC5164 Mobility Services Transport: Problem Statement There are ongoing activities in the networking community to develop solutions that aid in IP handover mechanisms between heterogeneous wired and wireless access systems including, but not limited to, IEEE 802.21. Intelligent access selection, taking into account link-layer attributes, requires the delivery of a variety of different information types to the terminal from different sources within the network and vice-versa. The protocol requirements for this signalling have both transport and security issues that must be considered. The signalling must not be constrained to specific link types, so there is at least a common component to the signalling problem, which is within the scope of the IETF. This document presents a problem statement for this core problem. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: T. Melia |
| RFC5165 A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC) This document describes a Uniform Resource Name (URN) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace IDentifier (NID) is "ogc". This memo provides information for the Internet community. | April 2008 Status: INFORMATIONAL Autor: C. Reed |
| RFC5166 Metrics for the Evaluation of Congestion Control Mechanisms This document discusses the metrics to be considered in an evaluation of new or modified congestion control mechanisms for the Internet. These include metrics for the evaluation of new transport protocols, of proposed modifications to TCP, of application-level congestion control, and of Active Queue Management (AQM) mechanisms in the router. This document is the first in a series of documents aimed at improving the models that we use in the evaluation of transport protocols. | March 2008 Status: INFORMATIONAL Autor: S. Floyd |
| RFC5167 Media Server Control Protocol Requirements This document addresses the communication between an application server and media server. The current work in IETF working groups shows these logical entities, but it does not address the physical decomposition and the protocol between the entities. | March 2008 Status: INFORMATIONAL Autor: M. Dolly, R. Even |
| RFC5168 XML Schema for Media Control This document defines an Extensible Markup Language (XML) Schema for video fast update in a tightly controlled environment, developed by Microsoft, Polycom, Radvision and used by multiple vendors. This document describes a method that has been deployed in Session Initiation Protocol (SIP) based systems over the last three years and is being used across real-time interactive applications from different vendors in an interoperable manner. New implementations are discouraged from using the method described except for backward compatibility purposes. New implementations are required to use the new Full Intra Request command in the RTP Control Protocol (RTCP) channel. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: O. Levin, R. Even, P. Hagendorf |
| RFC5169 Handover Key Management and Re-Authentication Problem Statement This document describes the Handover Keying (HOKEY) re-authentication problem statement. The current Extensible Authentication Protocol (EAP) keying framework is not designed to support re-authentication and handovers without re-executing an EAP method. This often causes unacceptable latency in various mobile wireless environments. This document details the problem and defines design goals for a generic mechanism to reuse derived EAP keying material for handover. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: T. Clancy, M. Nakhjiri, V. Narayanan, L. Dondeti |
| RFC5170 Low Density Parity Check (LDPC) Staircase and Triangle Forward Error Correction (FEC) Schemes This document describes two Fully-Specified Forward Error Correction (FEC) Schemes, Low Density Parity Check (LDPC) Staircase and LDPC Triangle, and their application to the reliable delivery of data objects on the packet erasure channel (i.e., a communication path where packets are either received without any corruption or discarded during transmission). These systematic FEC codes belong to the well- known class of "Low Density Parity Check" codes, and are large block FEC codes in the sense of RFC 3453. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: V. Roca, C. Neumann, D. Furodet |
| RFC5171 Cisco Systems UniDirectional Link Detection (UDLD) Protocol This document describes a Cisco Systems protocol that can be used to detect and disable unidirectional Ethernet fiber or copper links caused, for instance, by mis-wiring of fiber strands, interface malfunctions, media converters' faults, etc. It operates at Layer 2 in conjunction with IEEE 802.3's existing Layer 1 fault detection mechanisms. | April 2008 Status: INFORMATIONAL Autor: M. Foschiano |
| RFC5172 Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol The Point-to-Point Protocol (PPP) 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. | March 2008 Status: PROPOSED STANDARD Autor: S. Varada |
| RFC5173 Sieve Email Filtering: Body Extension This document defines a new command for the "Sieve" email filtering language that tests for the occurrence of one or more strings in the body of an email message. [STANDARDS-TRACK] | April 2008 Status: PROPOSED STANDARD Autor: J. Degener, P. Guenther |
| RFC5174 A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU) This document describes a Uniform Resource Name (URN) namespace for the European Broadcasting Union (EBU) for naming persistent resources defined within EBU technical documentation and Internet resources. 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 the EBU. This memo provides information for the Internet community. | May 2008 Status: INFORMATIONAL Autor: J-P. Evain |
| RFC5175 IPv6 Router Advertisement Flags Option The IPv6 Neighbor Discovery's Router Advertisement message contains an 8-bit field reserved for single-bit flags. Several protocols have reserved flags in this field and others are preparing to reserve a sufficient number of flags to exhaust the field. This document defines an option to the Router Advertisement message that expands the number of flag bits available. [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: B. Haberman, R. Hinden |
| RFC5176 Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) 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. | January 2008 Status: INFORMATIONAL Autor: M. Chiba, G. Dommety, M. Eklund, D. Mitton, B. Aboba |
| RFC5177 Network Mobility (NEMO) Extensions for Mobile IPv4 This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the Mobile Network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. | April 2008 Status: PROPOSED STANDARD Autor: K. Leung, G. Dommety, V. Narayanan, A. Petrescu |
| RFC5178 Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name Type This document describes domain-name-based service principal names and the corresponding name type for the Generic Security Service Application Programming Interface (GSS-API). Internationalization of the GSS-API is also covered. | May 2008 Status: PROPOSED STANDARD Autor: N. Williams, A. Melnikov |
| RFC5179 Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism This document describes the mapping of Generic Security Service Application Program Interface (GSS-API) domain-name-based service principal names onto Kerberos V principal names. [STANDARDS-TRACK] | May 2008 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC5180 IPv6 Benchmarking Methodology for Network Interconnect Devices The benchmarking methodologies defined in RFC 2544 are IP version independent. However, RFC 2544 does not address some of the specificities of IPv6. This document provides additional benchmarking guidelines, which in conjunction with RFC 2544, lead to a more complete and realistic evaluation of the IPv6 performance of network interconnect devices. IPv6 transition mechanisms are outside the scope of this document. This memo provides information for the Internet community. | May 2008 Status: INFORMATIONAL Autor: C. Popoviciu, A. Hamza, G. Van de Velde, D. Dugatkin |
| RFC5181 IPv6 Deployment Scenarios in 802.16 Networks This document provides a detailed description of IPv6 deployment and integration methods and scenarios in wireless broadband access networks in coexistence with deployed IPv4 services. In this document, we will discuss the main components of IPv6 IEEE 802.16 access networks and their differences from IPv4 IEEE 802.16 networks and how IPv6 is deployed and integrated in each of the IEEE 802.16 technologies. This memo provides information for the Internet community. | May 2008 Status: INFORMATIONAL Autor: M-K. Shin, Y-H. Han, S-E. Kim, D. Premec |
| RFC5182 IMAP Extension for Referencing the Last SEARCH Result Many IMAP clients use the result of a SEARCH command as the input to perform another operation, for example, fetching the found messages, deleting them, or copying them to another mailbox. | March 2008 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC5183 Sieve Email Filtering: Environment Extension This document describes the "environment" extension to the Sieve email filtering language. The "environment" extension gives a Sieve script access to information about the Sieve interpreter itself, where it is running, and about any transport connection currently involved in transferring the message. [STANDARDS-TRACK] | May 2008 Status: PROPOSED STANDARD Autor: N. Freed |
| RFC5184 Unified Layer 2 (L2) Abstractions for Layer 3 (L3)-Driven Fast Handover This document proposes unified Layer 2 (L2) abstractions for Layer 3 (L3)-driven fast handovers. For efficient network communication, it is vital for a protocol layer to know or utilize other layers' information, such as the form of L2 triggers. However, each protocol layer is basically designed independently. Since each protocol layer is also implemented independently in current operating systems, it is very hard to exchange control information between protocol layers. This document defines nine kinds of L2 abstractions in the form of "primitives" to achieve fast handovers in the network layer as a means of solving the problem. This mechanism is called "L3-driven fast handovers" because the network layer initiates L2 and L3 handovers by using the primitives. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This memo defines an Experimental Protocol for the Internet community. | May 2008 Status: EXPERIMENTAL Autor: F. Teraoka, K. Gogo, K. Mitsuya, R. Shibui, K. Mitani |
| RFC5185 OSPF Multi-Area Adjacency This document describes an extension to the Open Shortest Path First (OSPF) protocol to allow a single physical link to be shared by multiple areas. This is necessary to allow the link to be considered an intra-area link in multiple areas. This would create an intra- area path in each of the corresponding areas sharing the same link. [STANDARDS-TRACK] | May 2008 Status: PROPOSED STANDARD Autor: S. Mirtorabi, P. Psenak, A. Lindem, A. Oswal |
| RFC5186 Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction The definitions of the Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) require new behavior within the multicast routing protocols. The additional source information contained in IGMPv3 and MLDv2 messages necessitates that multicast routing protocols manage and utilize the information. This document describes how multicast routing protocols will interact with these source-filtering group management protocols. This memo provides information for the Internet community. | May 2008 Status: INFORMATIONAL Autor: B. Haberman, J. Martin |
| RFC5187 OSPFv3 Graceful Restart This document describes the OSPFv3 graceful restart. The OSPFv3 graceful restart is identical to that of OSPFv2 except for the differences described in this document. These differences include the format of the grace Link State Advertisements (LSAs) and other considerations. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: P. Pillay-Esnault, A. Lindem |
| RFC5188 RTP Payload Format for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and the Media Subtype Updates for EVRC-B Codec This document specifies Real-time Transport Protocol (RTP) payload formats to be used for the Enhanced Variable Rate Wideband Codec (EVRC-WB) and updates the media type registrations for EVRC-B codec. Several media type registrations are included for EVRC-WB RTP payload formats. In addition, a file format is specified for transport of EVRC-WB speech data in storage mode applications such as email. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: H. Desineni, Q. Xie |
| RFC5189 Middlebox Communication (MIDCOM) Protocol Semantics This document 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 document obsoletes RFC 3989. [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: M. Stiemerling, J. Quittek, T. Taylor |
| RFC5190 Definitions of Managed Objects for Middlebox Communication 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 configuring middleboxes, such as firewalls and network address translators, in order to enable communication across these devices. The definitions of managed objects in this documents follow closely the MIDCOM semantics defined in RFC 5189. [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: J. Quittek, M. Stiemerling, P. Srisuresh |
| RFC5191 Protocol for Carrying Authentication for Network Access (PANA) This document defines the Protocol for Carrying Authentication for Network Access (PANA), a network-layer transport for Extensible Authentication Protocol (EAP) to enable network access authentication between clients and access networks. In EAP terms, PANA is a UDP-based EAP lower layer that runs between the EAP peer and the EAP authenticator. [STANDARDS-TRACK] | May 2008 Status: PROPOSED STANDARD Autor: D. Forsberg, Y. Ohba, B. Patil, H. Tschofenig, A. Yegin |
| RFC5192 DHCP Options for Protocol for Carrying Authentication for Network Access (PANA) Authentication Agents This document defines new DHCPv4 and DHCPv6 options that contain a list of IP addresses to locate one or more PANA (Protocol for carrying Authentication for Network Access) Authentication Agents (PAAs). This is one of the methods that a PANA Client (PaC) can use to locate PAAs. [STANDARDS-TRACK] | May 2008 Status: PROPOSED STANDARD Autor: L. Morand, A. Yegin, S. Kumar, S. Madanapalli |
| RFC5193 Protocol for Carrying Authentication for Network Access (PANA) Framework This document defines the general Protocol for Carrying Authentication for Network Access (PANA) framework functional elements, high-level call flow, and deployment environments. This memo provides information for the Internet community. | May 2008 Status: INFORMATIONAL Autor: P. Jayaraman, R. Lopez, Y. Ohba, M. Parthasarathy, A. Yegin |
| RFC5194 Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP) This document lists the essential requirements for real-time Text-over-IP (ToIP) and defines a framework for implementation of all required functions based on the Session Initiation Protocol (SIP) and the Real-Time Transport Protocol (RTP). This includes interworking between Text-over-IP and existing text telephony on the Public Switched Telephone Network (PSTN) and other networks. This memo provides information for the Internet community. | June 2008 Status: INFORMATIONAL Autor: A. van Wijk, G. Gybels |
| RFC5195 BGP-Based Auto-Discovery for Layer-1 VPNs The purpose of this document is to define a BGP-based auto-discovery mechanism for Layer-1 VPNs (L1VPNs). The auto-discovery mechanism for L1VPNs allows the provider network devices to dynamically discover the set of Provider Edges (PEs) having ports attached to Customer Edge (CE) members of the same VPN. That information is necessary for completing the signaling phase of L1VPN connections. One main objective of a L1VPN auto-discovery mechanism is to support the "single-end provisioning" model, where addition of a new port to a given L1VPN would involve configuration changes only on the PE that has this port and on the CE that is connected to the PE via this port. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: H. Ould-Brahim, D. Fedyk, Y. Rekhter |
| RFC5196 Session Initiation Protocol (SIP) User Agent Capability Extension to Presence Information Data Format (PIDF) Presence Information Data Format (PIDF) defines a common presence data format for Common Profile for Presence (CPP) compliant presence protocols. This memo defines a PIDF extension to represent SIP User Agent capabilities. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: M. Lonnfors, K. Kiss |
| RFC5197 On the Applicability of Various Multimedia Internet KEYing (MIKEY) Modes and Extensions Multimedia Internet Keying (MIKEY) is a key management protocol that can be used for \%real-time applications. In particular, it has been defined focusing on the support of the Secure \%Real-time Transport Protocol (SRTP). MIKEY itself is standardized within RFC 3830 and defines four key distribution methods. Moreover, it is defined to allow extensions of the protocol. As MIKEY becomes more and more accepted, extensions to the base protocol arise, especially in terms of additional key distribution methods but also in terms of payload enhancements. | June 2008 Status: INFORMATIONAL Autor: S. Fries, D. Ignjatic |
| RFC5198 Unicode Format for Network Interchange The Internet today is in need of a standardized form for the transmission of internationalized "text" information, paralleling the specifications for the use of ASCII that date from the early days of the ARPANET. This document specifies that format, using UTF-8 with normalization and specific line-ending sequences. [STANDARDS-TRACK] | March 2008 Status: PROPOSED STANDARD Autor: J. Klensin, M. Padlipsky |
| RFC5201 Host Identity Protocol This memo specifies the details of the Host Identity Protocol (HIP). HIP allows consenting hosts to securely establish and maintain shared IP-layer state, allowing separation of the identifier and locator roles of IP addresses, thereby enabling continuity of communications across IP address changes. HIP is based on a Sigma-compliant Diffie- Hellman key exchange, using public key identifiers from a new Host Identity namespace for mutual peer authentication. The protocol is designed to be resistant to denial-of-service (DoS) and man-in-the- middle (MitM) attacks. When used together with another suitable security protocol, such as the Encapsulated Security Payload (ESP), it provides integrity protection and optional encryption for upper- layer protocols, such as TCP and UDP. This memo defines an Experimental Protocol for the Internet community. | April 2008 Status: EXPERIMENTAL Autor: R. Moskowitz, P. Nikander, P. Jokela, T. Henderson |
| RFC5202 Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP) This memo specifies an Encapsulated Security Payload (ESP) based mechanism for transmission of user data packets, to be used with the Host Identity Protocol (HIP). This memo defines an Experimental Protocol for the Internet community. | April 2008 Status: EXPERIMENTAL Autor: P. Jokela, R. Moskowitz, P. Nikander |
| RFC5203 Host Identity Protocol (HIP) Registration Extension This document specifies a registration mechanism for the Host Identity Protocol (HIP) that allows hosts to register with services, such as HIP rendezvous servers or middleboxes. This memo defines an Experimental Protocol for the Internet community. | April 2008 Status: EXPERIMENTAL Autor: J. Laganier, T. Koponen, L. Eggert |
| RFC5204 Host Identity Protocol (HIP) Rendezvous Extension This document defines a rendezvous extension for the Host Identity Protocol (HIP). The rendezvous extension extends HIP and the HIP registration extension for initiating communication between HIP nodes via HIP rendezvous servers. Rendezvous servers improve reachability and operation when HIP nodes are multi-homed or mobile. This memo defines an Experimental Protocol for the Internet community. | April 2008 Status: EXPERIMENTAL Autor: J. Laganier, L. Eggert |
| RFC5205 Host Identity Protocol (HIP) Domain Name System (DNS) Extensions This document specifies a new resource record (RR) for the Domain Name System (DNS), and how to use it with the Host Identity Protocol (HIP). This RR allows a HIP node to store in the DNS its Host Identity (HI, the public component of the node public-private key pair), Host Identity Tag (HIT, a truncated hash of its public key), and the Domain Names of its rendezvous servers (RVSs). This memo defines an Experimental Protocol for the Internet community. | April 2008 Status: EXPERIMENTAL Autor: P. Nikander, J. Laganier |
| RFC5206 End-Host Mobility and Multihoming with the Host Identity Protocol This document defines mobility and multihoming extensions to the Host Identity Protocol (HIP). Specifically, this document defines a general "LOCATOR" parameter for HIP messages that allows for a HIP host to notify peers about alternate addresses at which it may be reached. This document also defines elements of procedure for mobility of a HIP host -- the process by which a host dynamically changes the primary locator that it uses to receive packets. While the same LOCATOR parameter can also be used to support end-host multihoming, detailed procedures are left for further study. This memo defines an Experimental Protocol for the Internet community. | April 2008 Status: EXPERIMENTAL Autor: P. Nikander, T. Henderson, C. Vogt, J. Arkko |
| RFC5207 NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication The Host Identity Protocol (HIP) changes the way in which two Internet hosts communicate. One key advantage over other schemes is that HIP does not require modifications to the traditional network- layer functionality of the Internet, i.e., its routers. In the current Internet, however, many devices other than routers modify the traditional network-layer behavior of the Internet. These "middleboxes" are intermediary devices that perform functions other than the standard functions of an IP router on the datagram path between source and destination hosts. Whereas some types of middleboxes may not interfere with HIP at all, others can affect some aspects of HIP communication, and others can render HIP communication impossible. This document discusses the problems associated with HIP communication across network paths that include specific types of middleboxes, namely, network address translators and firewalls. It identifies and discusses issues in the current HIP specifications that affect communication across these types of middleboxes. This document is a product of the IRTF HIP Research Group. This memo provides information for the Internet community. | April 2008 Status: INFORMATIONAL Autor: M. Stiemerling, J. Quittek, L. Eggert |
| RFC5208 Public-Key Cryptography Standards (PKCS) #8: Private-Key Information Syntax Specification Version 1.2 This document represents a republication of PKCS #8 v1.2 from RSA Laboratories' Public Key Cryptography Standard (PKCS) series. Change control is transferred to the IETF. The body of this document, except for the security considerations section, is taken directly from the PKCS #8 v1.2 specification. | May 2008 Status: INFORMATIONAL Autor: B. Kaliski |
| RFC5209 Network Endpoint Assessment (NEA): Overview and Requirements This document defines the problem statement, scope, and protocol requirements between the components of the NEA (Network Endpoint Assessment) reference model. NEA provides owners of networks (e.g., an enterprise offering remote access) a mechanism to evaluate the posture of a system. This may take place during the request for network access and/or subsequently at any time while connected to the network. The learned posture information can then be applied to a variety of compliance-oriented decisions. The posture information is frequently useful for detecting systems that are lacking or have out-of-date security protection mechanisms such as: anti-virus and host-based firewall software. In order to provide context for the requirements, a reference model and terminology are introduced. This memo provides information for the Internet community. | June 2008 Status: INFORMATIONAL Autor: P. Sangster, H. Khosravi, M. Mani, K. Narayan, J. Tardo |
| RFC5210 A Source Address Validation Architecture (SAVA) Testbed and Deployment Experience Because the Internet forwards packets according to the IP destination address, packet forwarding typically takes place without inspection of the source address and malicious attacks have been launched using spoofed source addresses. In an effort to enhance the Internet with IP source address validation, a prototype implementation of the IP Source Address Validation Architecture (SAVA) was created and an evaluation was conducted on an IPv6 network. This document reports on the prototype implementation and the test results, as well as the lessons and insights gained from experimentation. This memo defines an Experimental Protocol for the Internet community. | June 2008 Status: EXPERIMENTAL Autor: J. Wu, J. Bi, X. Li, G. Ren, K. Xu, M. Williams |
| RFC5211 An Internet Transition Plan This memo provides one possible plan for transitioning the Internet from a predominantly IPv4-based connectivity model to a predominantly IPv6-based connectivity model. This memo provides information for the Internet community. | July 2008 Status: INFORMATIONAL Autor: J. Curran |
| RFC5212 Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN) Most of the initial efforts to utilize Generalized MPLS (GMPLS) have been related to environments hosting devices with a single switching capability. The complexity raised by the control of such data planes is similar to that seen in classical IP/MPLS networks. By extending MPLS to support multiple switching technologies, GMPLS provides a comprehensive framework for the control of a multi-layered network of either a single switching technology or multiple switching technologies. | July 2008 Status: INFORMATIONAL Autor: K. Shiomoto, D. Papadimitriou, JL. Le Roux, M. Vigoureux, D. Brungard |
| RFC5213 Proxy Mobile IPv6 Network-based mobility management enables IP mobility for a host without requiring its participation in any mobility-related signaling. The network is responsible for managing IP mobility on behalf of the host. The mobility entities in the network are responsible for tracking the movements of the host and initiating the required mobility signaling on its behalf. This specification describes a network-based mobility management protocol and is referred to as Proxy Mobile IPv6. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: S. Gundavelli, K. Leung, V. Devarapalli, K. Chowdhury, B. Patil |
| RFC5214 Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects dual-stack (IPv6/IPv4) nodes over IPv4 networks. ISATAP views the IPv4 network as a link layer for IPv6 and supports an automatic tunneling abstraction similar to the Non-Broadcast Multiple Access (NBMA) model. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: F. Templin, T. Gleeson, D. Thaler |
| RFC5215 RTP Payload Format for Vorbis Encoded Audio This document describes an RTP payload format for transporting Vorbis encoded audio. It details the RTP encapsulation mechanism for raw Vorbis data and the delivery mechanisms for the decoder probability model (referred to as a codebook), as well as other setup information. | August 2008 Status: PROPOSED STANDARD Autor: L. Barbato |
| RFC5216 The EAP-TLS Authentication Protocol The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides support for multiple authentication methods. Transport Layer Security (TLS) provides for mutual authentication, integrity-protected ciphersuite negotiation, and key exchange between two endpoints. This document defines EAP-TLS, which includes support for certificate-based mutual authentication and key derivation. | March 2008 Status: PROPOSED STANDARD Autor: D. Simon, B. Aboba, R. Hurst |
| RFC5217 Memorandum for Multi-Domain Public Key Infrastructure Interoperability The objective of this document is to establish a terminology framework and to suggest the operational requirements of Public Key Infrastructure (PKI) domain for interoperability of multi-domain Public Key Infrastructure, where each PKI domain is operated under a distinct policy. This document describes the relationships between Certification Authorities (CAs), provides the definition and requirements for PKI domains, and discusses typical models of multi-domain PKI. This memo provides information for the Internet community. | July 2008 Status: INFORMATIONAL Autor: M. Shimaoka, N. Hastings, R. Nielsen |
| RFC5218 What Makes For a Successful Protocol? The Internet community has specified a large number of protocols to date, and these protocols have achieved varying degrees of success. Based on case studies, this document attempts to ascertain factors that contribute to or hinder a protocol's success. It is hoped that these observations can serve as guidance for future protocol work. This memo provides information for the Internet community. | July 2008 Status: INFORMATIONAL Autor: D. Thaler, B. Aboba |
| RFC5219 A More Loss-Tolerant RTP Payload Format for MP3 Audio This document describes an 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. This document obsoletes RFC 3119, correcting typographical errors in the "SDP usage" section and pseudo-code appendices. [STANDARDS-TRACK] | February 2008 Status: PROPOSED STANDARD Autor: R. Finlayson |
| RFC5220 Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules A single physical link can have multiple prefixes assigned to it. In that environment, end hosts might have multiple IP addresses and be required to use them selectively. RFC 3484 defines default source and destination address selection rules and is implemented in a variety of OSs. But, it has been too difficult to use operationally for several reasons. In some environments where multiple prefixes are assigned on a single physical link, the host using the default address selection rules will experience some trouble in communication. This document describes the possible problems that end hosts could encounter in an environment with multiple prefixes. This memo provides information for the Internet community. | July 2008 Status: INFORMATIONAL Autor: A. Matsumoto, T. Fujisaki, R. Hiromi, K. Kanayama |
| RFC5221 Requirements for Address Selection Mechanisms There are some problematic cases when using the default address selection mechanism that RFC 3484 defines. This document describes additional requirements that operate with RFC 3484 to solve the problems. This memo provides information for the Internet community. | July 2008 Status: INFORMATIONAL Autor: A. Matsumoto, T. Fujisaki, R. Hiromi, K. Kanayama |
| RFC5222 LoST: A Location-to-Service Translation Protocol This document describes an XML-based protocol for mapping service identifiers and geodetic or civic location information to service contact URIs. In particular, it can be used to determine the location-appropriate Public Safety Answering Point (PSAP) for emergency services. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: T. Hardie, A. Newton, H. Schulzrinne, H. Tschofenig |
| RFC5223 Discovering Location-to-Service Translation (LoST) Servers Using the Dynamic Host Configuration Protocol (DHCP) The Location-to-Service Translation (LoST) Protocol describes an XML- based protocol for mapping service identifiers and geospatial or civic location information to service contact Uniform Resource Locators (URLs). LoST servers can be located anywhere, but a placement closer to the end host, e.g., in the access network, is desirable. In disaster situations with intermittent network connectivity, such a LoST server placement provides benefits regarding the resiliency of emergency service communication. | August 2008 Status: PROPOSED STANDARD Autor: H. Schulzrinne, J. Polk, H. Tschofenig |
| RFC5224 Diameter Policy Processing Application This document describes the need for a new IANA Diameter Command Code to be used in a vendor-specific new application for invocation of Policy Processing (Policy Evaluation, or Evaluation and Enforcement). This application is needed as one of the implementations of the Open Mobile Alliance (OMA) Policy Evaluation, Enforcement and Management (PEEM) enabler, namely for the PEM-1 interface used to send a request/response for Policy Processing. This memo provides information for the Internet community. | March 2008 Status: INFORMATIONAL Autor: M. Brenner |
| RFC5225 RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite This document specifies ROHC (Robust Header Compression) profiles that efficiently compress RTP/UDP/IP (Real-Time Transport Protocol, User Datagram Protocol, Internet Protocol), RTP/UDP-Lite/IP (User Datagram Protocol Lite), UDP/IP, UDP-Lite/IP, IP and ESP/IP (Encapsulating Security Payload) headers. | April 2008 Status: PROPOSED STANDARD Autor: G. Pelletier, K. Sandlund |
| RFC5226 Guidelines for Writing an IANA Considerations Section in RFCs Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). | May 2008 Status: BEST CURRENT PRACTICE Autor: T. Narten, H. Alvestrand |
| RFC5227 IPv4 Address Conflict Detection When two hosts on the same link attempt to use the same IPv4 address at the same time (except in rare special cases where this has been arranged by prior coordination), problems ensue for one or both hosts. This document describes (i) a simple precaution that a host can take in advance to help prevent this misconfiguration from happening, and (ii) if this misconfiguration does occur, a simple mechanism by which a host can passively detect, after the fact, that it has happened, so that the host or administrator may respond to rectify the problem. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: S. Cheshire |
| RFC5228 Sieve: An Email Filtering Language This document describes a language for filtering email messages at time of final delivery. It is designed to be implementable on either a mail client or mail server. It is meant to be extensible, simple, and independent of access protocol, mail architecture, and operating system. It is suitable for running on a mail server where users may not be allowed to execute arbitrary programs, such as on black box Internet Message Access Protocol (IMAP) servers, as the base language has no variables, loops, or ability to shell out to external programs. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: P. Guenther, T. Showalter |
| RFC5229 Sieve Email Filtering: Variables Extension In advanced mail filtering rule sets, it is useful to keep state or configuration details across rules. This document updates the Sieve filtering language (RFC 5228) with an extension to support variables. The extension changes the interpretation of strings, adds an action to store data in variables, and supplies a new test so that the value of a string can be examined. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: K. Homme |
| RFC5230 Sieve Email Filtering: Vacation Extension This document describes an extension to the Sieve email filtering language for an autoresponder similar to that of the Unix "vacation" command for replying to messages. Various safety features are included to prevent problems such as message loops. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: T. Showalter, N. Freed |
| RFC5231 Sieve Email Filtering: Relational Extension 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. | January 2008 Status: PROPOSED STANDARD Autor: W. Segmuller, B. Leiba |
| RFC5232 Sieve Email Filtering: Imap4flags Extension Recent discussions have shown that it is desirable to set different IMAP (RFC 3501) flags on message delivery. This can be done, for example, by a Sieve interpreter that works as a part of a Mail Delivery Agent. | January 2008 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC5233 Sieve Email Filtering: Subaddress Extension 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 Email Filtering Language that allows users to compare against the user and detail sub-parts of an address. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: K. Murchison |
| RFC5234 Augmented BNF for Syntax Specifications: ABNF Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] | January 2008 Status: STANDARD Autor: D. Crocker, P. Overell |
| RFC5235 Sieve Email Filtering: Spamtest and Virustest Extensions The Sieve email filtering language "spamtest", "spamtestplus", 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 proper input to the tests. [STANDARDS-TRACK] | January 2008 Status: PROPOSED STANDARD Autor: C. Daboo |
| RFC5236 Improved Packet Reordering Metrics This document presents two improved metrics for packet reordering, namely, Reorder Density (RD) and Reorder Buffer-occupancy Density (RBD). A threshold is used to clearly define when a packet is considered lost, to bound computational complexity at O(N), and to keep the memory requirement for evaluation independent of N, where N is the length of the packet sequence. RD is a comprehensive metric that captures the characteristics of reordering, while RBD evaluates the sequences from the point of view of recovery from reordering. | June 2008 Status: INFORMATIONAL Autor: A. Jayasumana, N. Piratla, T. Banka, A. Bare, R. Whitner |
| RFC5237 IANA Allocation Guidelines for the Protocol Field This document revises the IANA guidelines for allocating new Protocol field values in IPv4 header. It modifies the rules specified in RFC 2780 by removing the Expert Review option. The change will also affect the allocation of Next Header field values in IPv6. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 2008 Status: BEST CURRENT PRACTICE Autor: J. Arkko, S. Bradner |
| RFC5238 Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP) This document specifies the use of Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP). DTLS provides communications privacy for applications that use datagram transport protocols and allows client/server applications to communicate in a way that is designed to prevent eavesdropping and detect tampering or message forgery. DCCP is a transport protocol that provides a congestion-controlled unreliable datagram service. [STANDARDS-TRACK] | May 2008 Status: PROPOSED STANDARD Autor: T. Phelan |
| RFC5239 A Framework for Centralized Conferencing This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISDN User Part (ISUP), to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: M. Barnes, C. Boulton, O. Levin |
| RFC5240 Protocol Independent Multicast (PIM) Bootstrap Router MIB This document 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 Bootstrap Router (BSR) mechanism for PIM (Protocol Independent Multicast). [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: B. Joshi, R. Bijlani |
| RFC5241 Naming Rights in IETF Protocols This document proposes a new revenue source for the IETF to support standardization activities: protocol field naming rights, i.e., the association of commercial brands with protocol fields. This memo describes a process for assignment of rights and explores some of the issues associated with the process. Individuals or organizations that wish to purchase naming rights for one or more protocol fields are expected to follow this process. This memo provides information for the Internet community. | April 2008 Status: INFORMATIONAL Autor: A. Falk, S. Bradner |
| RFC5242 A Generalized Unified Character Code: Western European and CJK Sections Many issues have been identified with the use of general-purpose character sets for internationalized domain names and similar purposes. This memo describes a fully unified coded character set for scripts based on Latin, Greek, Cyrillic, and Chinese (CJK) characters. It is not a complete specification of that character set. This memo provides information for the Internet community. | April 2008 Status: INFORMATIONAL Autor: J. Klensin, H. Alvestrand |
| RFC5243 OSPF Database Exchange Summary List Optimization This document describes a backward-compatible optimization for the Database Exchange process in OSPFv2 and OSPFv3. In this optimization, a router does not list a Link State Advertisement (LSA) in Database Description packets sent to a neighbor, if the same or a more recent instance of the LSA was listed in a Database Description packet already received from the neighbor. This optimization reduces Database Description overhead by about 50% in large networks. This optimization does not affect synchronization, since it only omits unnecessary information from Database Description packets. This memo provides information for the Internet community. | May 2008 Status: INFORMATIONAL Autor: R. Ogier |
| RFC5244 Definition of Events for Channel-Oriented Telephony Signalling This memo updates RFC 4733 to add event codes for telephony signals used for channel-associated signalling when carried in the telephony event RTP payload. It supersedes and adds to the original assignment of event codes for this purpose in Section 3.14 of RFC 2833. As documented in Appendix A of RFC 4733, some of the RFC 2833 events have been deprecated because their specification was ambiguous, erroneous, or redundant. In fact, the degree of change from Section 3.14 of RFC 2833 is such that implementations of the present document will be fully backward compatible with RFC 2833 implementations only in the case of full ABCD-bit signalling. This document expands and improves the coverage of signalling systems compared to RFC 2833. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: H. Schulzrinne, T. Taylor |
| RFC5245 Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model. This protocol is called Interactive Connectivity Establishment (ICE). ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP). [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2 This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security 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] | August 2008 Status: PROPOSED STANDARD Autor: T. Dierks, E. Rescorla |
| RFC5247 Extensible Authentication Protocol (EAP) Key Management Framework The Extensible Authentication Protocol (EAP), defined in RFC 3748, enables extensible network access authentication. This document specifies the EAP key hierarchy and provides a framework for the transport and usage of keying material and parameters generated by EAP authentication algorithms, known as "methods". It also provides a detailed system-level security analysis, describing the conditions under which the key management guidelines described in RFC 4962 can be satisfied. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: B. Aboba, D. Simon, P. Eronen |
| RFC5248 A Registry for SMTP Enhanced Mail System Status Codes The specification for enhanced mail system status codes, RFC 3463, establishes a new code model and lists a collection of status codes. While it anticipated that more codes would be added over time, it did not provide an explicit mechanism for registering and tracking those codes. This document specifies an IANA registry for mail system enhanced status codes, and initializes that registry with the codes so far established in published standards-track documents, as well as other codes that have become established in the industry. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2008 Status: BEST CURRENT PRACTICE Autor: T. Hansen, J. Klensin |
| RFC5249 Templates for Internet-Drafts Containing MIB Modules This memo references three annotated templates for IETF documents that contain the definition of MIB modules. It is intended to reduce the work of the editors of such documents, making these documents more uniform and easier to read and review, thus furthering the quality of such documents and expediting their publication. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | July 2008 Status: BEST CURRENT PRACTICE Autor: D. Harrington |
| RFC5250 The OSPF Opaque LSA Option This document defines enhancements to the OSPF protocol to support a new class of link state advertisements (LSAs) called Opaque LSAs. Opaque LSAs provide a generalized mechanism to allow for the future extensibility of OSPF. Opaque LSAs consist of a standard LSA header followed by application-specific information. The information field may be used directly by OSPF or by other applications. Standard OSPF link-state database flooding mechanisms are used to distribute Opaque LSAs to all or some limited portion of the OSPF topology. | July 2008 Status: PROPOSED STANDARD Autor: L. Berger, I. Bryskin, A. Zinin, R. Coltun |
| RFC5251 Layer 1 VPN Basic Mode This document describes the Basic Mode of Layer 1 VPNs (L1VPNs). L1VPN Basic Mode (L1VPN BM) is a port-based VPN. In L1VPN Basic Mode, the basic unit of service is a Label Switched Path (LSP) between a pair of customer ports within a given VPN port topology. This document defines the operational model using either provisioning or a VPN auto-discovery mechanism, and the signaling extensions for the L1VPN BM. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: D. Fedyk, Y. Rekhter, D. Papadimitriou, R. Rabbat, L. Berger |
| RFC5252 OSPF-Based Layer 1 VPN Auto-Discovery This document defines an Open Shortest Path First (OSPF) based Layer 1 Virtual Private Network (L1VPN) auto-discovery mechanism. This mechanism enables provider edge (PE) devices using OSPF to dynamically learn about the existence of each other, and attributes of configured customer edge (CE) links and their associations with L1VPNs. This document builds on the L1VPN framework and requirements and provides a L1VPN basic mode auto-discovery mechanism. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: I. Bryskin, L. Berger |
| RFC5253 Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic Mode This document provides an applicability statement on the use of Generalized Multiprotocol Label Switching (GMPLS) protocols and mechanisms to support Basic Mode Layer 1 Virtual Private Networks (L1VPNs). | July 2008 Status: INFORMATIONAL Autor: T. Takeda |
| RFC5254 Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3) This document describes the necessary requirements to allow a service provider to extend the reach of pseudowires across multiple domains. These domains can be autonomous systems under one provider administrative control, IGP areas in one autonomous system, different autonomous systems under the administrative control of two or more service providers, or administratively established pseudowire domains. This memo provides information for the Internet community. | October 2008 Status: INFORMATIONAL Autor: N. Bitar, M. Bocci, L. Martini |
| RFC5255 Internet Message Access Protocol Internationalization Internet Message Access Protocol (IMAP) version 4rev1 has basic support for non-ASCII characters in mailbox names and search substrings. It also supports non-ASCII message headers and content encoded as specified by Multipurpose Internet Mail Extensions (MIME). This specification defines a collection of IMAP extensions that improve international support including language negotiation for international error text, translations for namespace prefixes, and comparator negotiation for search, sort, and thread. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: C. Newman, A. Gulbrandsen, A. Melnikov |
| RFC5256 Internet Message Access Protocol - SORT and THREAD Extensions This document describes the base-level server-based sorting and threading extensions to the IMAP protocol. These extensions provide substantial performance improvements for IMAP clients that offer sorted and threaded views. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: M. Crispin, K. Murchison |
| RFC5257 Internet Message Access Protocol - ANNOTATE Extension The ANNOTATE extension to the Internet Message Access Protocol permits clients and servers to maintain "meta data" for messages, or individual message parts, stored in a mailbox on the server. For example, this can be used to attach comments and other useful information to a message. It is also possible to attach annotations to specific parts of a message, so that, for example, they could be marked as seen, or important, or a comment added. | June 2008 Status: EXPERIMENTAL Autor: C. Daboo, R. Gellens |
| RFC5258 Internet Message Access Protocol version 4 - LIST Command Extensions IMAP4 has two commands for listing mailboxes: LIST and LSUB. As we have added extensions, such as Mailbox Referrals, that have required specialized lists we have had to expand the number of list commands, since each extension must add its function to both LIST and LSUB, and these commands are not, as they are defined, extensible. If we've needed the extensions to work together, we've had to add a set of commands to mix the different options, the set increasing in size with each new extension. This document describes an extension to the base LIST command that will allow these additions to be done with mutually compatible options to the LIST command, avoiding the exponential increase in specialized list commands. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: B. Leiba, A. Melnikov |
| RFC5259 Internet Message Access Protocol - CONVERT Extension CONVERT defines extensions to IMAP allowing clients to request adaptation and/or transcoding of attachments. Clients can specify the conversion details or allow servers to decide based on knowledge of client capabilities, on user or administrator preferences, or on server settings. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: A. Melnikov, P. Coates |
| RFC5260 Sieve Email Filtering: Date and Index Extensions This document describes the "date" and "index" extensions to the Sieve email filtering language. The "date" extension gives Sieve the ability to test date and time values in various ways. The "index" extension provides a means to limit header and address tests to specific instances of header fields when header fields are repeated. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: N. Freed |
| RFC5261 An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic <add>, <replace>, and <remove> directives a set of patches can then be applied to update an existing XML document. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: J. Urpalainen |
| RFC5262 Presence Information Data Format (PIDF) Extension for Partial Presence The Presence Information Document Format (PIDF) specifies the baseline XML-based format for describing presence information. One of the characteristics of the PIDF is that the document always needs to carry all presence information available for the presentity. In some environments where low bandwidth and high latency links can exist, it is often beneficial to limit the amount of transported information over the network. This document introduces a new MIME type that enables transporting of either only the changed parts or the full PIDF-based presence information. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: M. Lonnfors, E. Leppanen, H. Khartabil, J. Urpalainen |
| RFC5263 Session Initiation Protocol (SIP) Extension for Partial Notification of Presence Information By default, presence delivered using the presence event package for the Session Initiation Protocol (SIP) is represented in the Presence Information Data Format (PIDF). A PIDF document contains a set of elements, each representing a different aspect of the presence being reported. When any subset of the elements change, even just a single element, a new document containing the full set of elements is delivered. This memo defines an extension allowing delivery of only the presence data that has actually changed. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: M. Lonnfors, J. Costa-Requena, E. Leppanen, H. Khartabil |
| RFC5264 Publication of Partial Presence Information The Session Initiation Protocol (SIP) Extension for Event State Publication describes a mechanism with which a presence user agent is able to publish presence information to a presence agent. Using the Presence Information Data Format (PIDF), each presence publication contains full state, regardless of how much of that information has actually changed since the previous update. As a consequence, updating a sizeable presence document with small changes bears a considerable overhead and is therefore inefficient. Especially with low bandwidth and high latency links, this can constitute a considerable burden to the system. This memo defines a solution that aids in reducing the impact of those constraints and increases transport efficiency by introducing a mechanism that allows for publication of partial presence information. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: A. Niemi, M. Lonnfors, E. Leppanen |
| RFC5265 Mobile IPv4 Traversal across IPsec-Based VPN Gateways This document outlines a solution for the Mobile IPv4 (MIPv4) and IPsec coexistence problem for enterprise users. The solution consists of an applicability statement for using Mobile IPv4 and IPsec for session mobility in corporate remote access scenarios, and a required mechanism for detecting the trusted internal network securely. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: S. Vaarala, E. Klovning |
| RFC5266 Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE) Enterprise users require mobility and secure connectivity when they roam and connect to the services offered in the enterprise. Secure connectivity is required when the user connects to the enterprise from an untrusted network. Mobility is beneficial when the user moves, either inside or outside the enterprise network, and acquires a new IP address. This document describes a solution using Mobile IPv4 (MIPv4) and mobility extensions to IKEv2 (MOBIKE) to provide secure connectivity and mobility. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2008 Status: BEST CURRENT PRACTICE Autor: V. Devarapalli, P. Eronen |
| RFC5267 Contexts for IMAP4 The IMAP4rev1 protocol has powerful search facilities as part of the core protocol, but lacks the ability to create live, updated results that can be easily handled. This memo provides such an extension, and shows how it can be used to provide a facility similar to virtual mailboxes. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: D. Cridland, C. King |
| RFC5268 Mobile IPv6 Fast Handovers Mobile IPv6 enables a Mobile Node (MN) to maintain its connectivity to the Internet when moving from one Access Router to another, a process referred to as handover. During handover, there is a period during which the Mobile Node is unable to send or receive packets because of link switching delay and IP protocol operations. This "handover latency" resulting from standard Mobile IPv6 procedures, namely movement detection, new Care-of Address configuration, and Binding Update, is often unacceptable to real-time traffic such as Voice over IP (VoIP). Reducing the handover latency could be beneficial to non-real-time, throughput-sensitive applications as well. This document specifies a protocol to improve handover latency due to Mobile IPv6 procedures. This document does not address improving the link switching latency. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: R. Koodli |
| RFC5269 Distributing a Symmetric Fast Mobile IPv6 (FMIPv6) Handover Key Using SEcure Neighbor Discovery (SEND) Fast Mobile IPv6 requires that a Fast Binding Update is secured using a security association shared between an Access Router and a Mobile Node in order to avoid certain attacks. In this document, a method for provisioning a shared key from the Access Router to the Mobile Node is defined to protect this signaling. The Mobile Node generates a public/private key pair using the same public key algorithm as for SEND (RFC 3971). The Mobile Node sends the public key to the Access Router. The Access Router encrypts a shared handover key using the public key and sends it back to the Mobile Node. The Mobile Node decrypts the shared handover key using the matching private key, and the handover key is then available for generating an authenticator on a Fast Binding Update. The Mobile Node and Access Router use the Router Solicitation for Proxy Advertisement and Proxy Router Advertisement from Fast Mobile IPv6 for the key exchange. The key exchange messages are required to have SEND security; that is, the source address is a Cryptographically Generated Address (CGA) and the messages are signed using the CGA private key of the sending node. This allows the Access Router, prior to providing the shared handover key, to verify the authorization of the Mobile Node to claim the address so that the previous care-of CGA in the Fast Binding Update can act as the name of the key. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: J. Kempf, R. Koodli |
| RFC5270 Mobile IPv6 Fast Handovers over IEEE 802.16e Networks This document describes how a Mobile IPv6 Fast Handover can be implemented on link layers conforming to the IEEE 802.16e suite of specifications. The proposed scheme tries to achieve seamless handover by exploiting the link-layer handover indicators and thereby synchronizing the IEEE 802.16e handover procedures with the Mobile IPv6 fast handover procedures efficiently. This memo provides information for the Internet community. | June 2008 Status: INFORMATIONAL Autor: H. Jang, J. Jee, Y. Han, S. Park, J. Cha |
| RFC5271 Mobile IPv6 Fast Handovers for 3G CDMA Networks Mobile IPv6 is designed to maintain its connectivity while moving from one network to another. It is adopted in 3G CDMA networks as a way to maintain connectivity when the mobile node (MN) moves between access routers. However, this handover procedure requires not only movement detection by the MN, but also the acquisition of a new Care-of Address and Mobile IPv6 registration with the new care-of address before the traffic can be sent or received in the target network. During this period, packets destined for the mobile node may be lost, which may not be acceptable for a real-time application such as Voice over IP (VoIP) or video telephony. This document specifies fast handover methods in the 3G CDMA networks in order to reduce latency and packet loss during handover. This memo provides information for the Internet community. | June 2008 Status: INFORMATIONAL Autor: H. Yokota, G. Dommety |
| RFC5272 Certificate Management over CMS (CMC) This document defines the base syntax for CMC, a Certificate Management protocol using the Cryptographic Message Syntax (CMS). This protocol addresses two immediate needs within the Internet Public Key Infrastructure (PKI) community: | June 2008 Status: PROPOSED STANDARD Autor: J. Schaad, M. Myers |
| RFC5273 Certificate Management over CMS (CMC): Transport Protocols This document defines a number of transport mechanisms that are used to move CMC (Certificate Management over CMS (Cryptographic Message Syntax)) messages. The transport mechanisms described in this document are HTTP, file, mail, and TCP. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: J. Schaad, M. Myers |
| RFC5274 Certificate Management Messages over CMS (CMC): Compliance Requirements This document provides a set of compliance statements about the CMC (Certificate Management over CMS) enrollment protocol. The ASN.1 structures and the transport mechanisms for the CMC enrollment protocol are covered in other documents. This document provides the information needed to make a compliant version of CMC. [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: J. Schaad, M. Myers |
| RFC5275 CMS Symmetric Key Management and Distribution This document describes a mechanism to manage (i.e., set up, distribute, and rekey) keys used with symmetric cryptographic algorithms. Also defined herein is a mechanism to organize users into groups to support distribution of encrypted content using symmetric cryptographic algorithms. The mechanism uses the Cryptographic Message Syntax (CMS) protocol and Certificate Management over CMS (CMC) protocol to manage the symmetric keys. Any member of the group can then later use this distributed shared key to decrypt other CMS encrypted objects with the symmetric key. This mechanism has been developed to support Secure/Multipurpose Internet Mail Extensions (S/MIME) Mail List Agents (MLAs). [STANDARDS-TRACK] | June 2008 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC5276 Using the Server-Based Certificate Validation Protocol (SCVP) to Convey Long-Term Evidence Records The Server-based Certificate Validation Protocol (SCVP) defines an extensible means of delegating the development and validation of certification paths to a server. It can be used to support the development and validation of certification paths well after the expiration of the certificates in the path by specifying a time of interest in the past. The Evidence Record Syntax (ERS) defines structures, called evidence records, to support the non-repudiation of the existence of data. Evidence records can be used to preserve materials that comprise a certification path such that trust in the certificates can be established after the expiration of the certificates in the path and after the cryptographic algorithms used to sign the certificates in the path are no longer secure. This document describes usage of the SCVP WantBack feature to convey evidence records, enabling SCVP responders to provide preservation evidence for certificates and certificate revocation lists (CRLs). [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: C. Wallace |
| RFC5277 NETCONF Event Notifications This document defines mechanisms that provide an asynchronous message notification delivery service for the Network Configuration protocol (NETCONF). This is an optional capability built on top of the base NETCONF definition. This document defines the capabilities and operations necessary to support this service. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: S. Chisholm, H. Trevino |
| RFC5278 IANA Registration of Enumservices for Voice and Video Messaging This document registers the Enumservice named "vmsg", which is used to facilitate the real-time routing of voice, video, and unified communications to a messaging system. This vmsg Enumservice registers three Enumservice types: "voicemsg", "videomsg", and "unifmsg". Each type also registers the subtypes "sip", "sips", "http", and "https", as well as the subtype "tel" for the "voicemsg" type. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: J. Livingood, D. Troshynski |
| RFC5279 A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP) This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the 3rd Generation Partnership Project (3GPP). 3GPP defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided by the 3GPP Support Team. This memo provides information for the Internet community. | July 2008 Status: INFORMATIONAL Autor: A. Monrad, S. Loreto |
| RFC5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile This memo profiles the X.509 v3 certificate and X.509 v2 certificate revocation list (CRL) for use in the Internet. An overview of this approach and model is provided as an introduction. The X.509 v3 certificate format is described in detail, with additional information regarding the format and semantics of Internet name forms. Standard certificate extensions are described and two Internet-specific extensions are defined. A set of required certificate extensions is specified. The X.509 v2 CRL format is described in detail along with standard and Internet-specific extensions. An algorithm for X.509 certification path validation is described. An ASN.1 module and examples are provided in the appendices. [STANDARDS-TRACK] | May 2008 Status: PROPOSED STANDARD Autor: D. Cooper, S. Santesson, S. Farrell, S. Boeyen, R. Housley, W. Polk |
| RFC5281 Extensible Authentication Protocol Tunneled Transport Layer Security Authenticated Protocol Version 0 (EAP-TTLSv0) EAP-TTLS is an EAP (Extensible Authentication Protocol) method that encapsulates a TLS (Transport Layer Security) session, consisting of a handshake phase and a data phase. During the handshake phase, the server is authenticated to the client (or client and server are mutually authenticated) using standard TLS procedures, and keying material is generated in order to create a cryptographically secure tunnel for information exchange in the subsequent data phase. During the data phase, the client is authenticated to the server (or client and server are mutually authenticated) using an arbitrary authentication mechanism encapsulated within the secure tunnel. The encapsulated authentication mechanism may itself be EAP, or it may be another authentication protocol such as PAP, CHAP, MS-CHAP, or MS-CHAP-V2. Thus, EAP-TTLS allows legacy password-based authentication protocols to be used against existing authentication databases, while protecting the security of these legacy protocols against eavesdropping, man-in-the-middle, and other attacks. The data phase may also be used for additional, arbitrary data exchange. This memo provides information for the Internet community. | August 2008 Status: INFORMATIONAL Autor: P. Funk, S. Blake-Wilson |
| RFC5282 Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 (IKEv2) Protocol An authenticated encryption algorithm combines encryption and integrity into a single operation; such algorithms may also be referred to as combined modes of an encryption cipher or as combined mode algorithms. This document describes the use of authenticated encryption algorithms with the Encrypted Payload of the Internet Key Exchange version 2 (IKEv2) protocol. | August 2008 Status: PROPOSED STANDARD Autor: D. Black, D. McGrew |
| RFC5283 LDP Extension for Inter-Area Label Switched Paths (LSPs) To facilitate the establishment of Label Switched Paths (LSPs) that would span multiple IGP areas in a given Autonomous System (AS), this document describes a new optional Longest-Match Label Mapping Procedure for the Label Distribution Protocol (LDP). | July 2008 Status: PROPOSED STANDARD Autor: B. Decraene, JL. Le Roux, I. Minei |
| RFC5284 User-Defined Errors for RSVP The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object for communicating errors. That object has a defined format that permits the definition of 256 error codes. As RSVP has been developed and extended, the convention has been to be conservative in defining new error codes. Further, no provision for user-defined errors exists in RSVP. | August 2008 Status: PROPOSED STANDARD Autor: G. Swallow, A. Farrel |
| RFC5285 A General Mechanism for RTP Header Extensions This document provides a general mechanism to use the header extension feature of RTP (the Real-Time Transport Protocol). It provides the option to use a small number of small extensions in each RTP packet, where the universe of possible extensions is large and registration is de-centralized. The actual extensions in use in a session are signaled in the setup information for that session. [STANDARDS-TRACK] | July 2008 Status: PROPOSED STANDARD Autor: D. Singer, H. Desineni |
| RFC5286 Basic Specification for IP Fast Reroute: Loop-Free Alternates This document describes the use of loop-free alternates to provide local protection for unicast traffic in pure IP and MPLS/LDP networks in the event of a single failure, whether link, node, or shared risk link group (SRLG). The goal of this technology is to reduce the packet loss that happens while routers converge after a topology change due to a failure. Rapid failure repair is achieved through use of precalculated backup next-hops that are loop-free and safe to use until the distributed network convergence process completes. This simple approach does not require any support from other routers. The extent to which this goal can be met by this specification is dependent on the topology of the network. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: A. Atlas, A. Zinin |
| RFC5287 Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks This document defines extension to the Pseudowire Emulation Edge-to-Edge (PWE3) control protocol RFC 4447 and PWE3 IANA allocations RFC 4446 required for the setup of Time-Division Multiplexing (TDM) pseudowires in MPLS networks. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: A. Vainshtein, Y(J). Stein |
| RFC5288 AES Galois Counter Mode (GCM) Cipher Suites for TLS This memo describes the use of the Advanced Encryption Standard (AES) in Galois/Counter Mode (GCM) as a Transport Layer Security (TLS) authenticated encryption operation. GCM provides both confidentiality and data origin authentication, can be efficiently implemented in hardware for speeds of 10 gigabits per second and above, and is also well-suited to software implementations. This memo defines TLS cipher suites that use AES-GCM with RSA, DSA, and Diffie-Hellman-based key exchange mechanisms. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: J. Salowey, A. Choudhury, D. McGrew |
| RFC5289 TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM) RFC 4492 describes elliptic curve cipher suites for Transport Layer Security (TLS). However, all those cipher suites use HMAC-SHA-1 as their Message Authentication Code (MAC) algorithm. This document describes sixteen new cipher suites for TLS that specify stronger MAC algorithms. Eight use Hashed Message Authentication Code (HMAC) with SHA-256 or SHA-384, and eight use AES in Galois Counter Mode (GCM). This memo provides information for the Internet community. | August 2008 Status: INFORMATIONAL Autor: E. Rescorla |
| RFC5290 Comments on the Usefulness of Simple Best-Effort Traffic This document presents some observations on "simple best-effort traffic", defined loosely for the purposes of this document as Internet traffic that is not covered by Quality of Service (QOS) mechanisms, congestion-based pricing, cost-based fairness, admissions control, or the like. One observation is that simple best-effort traffic serves a useful role in the Internet, and is worth keeping. While differential treatment of traffic can clearly be useful, we believe such mechanisms are useful as *adjuncts* to simple best- effort traffic, not as *replacements* of simple best-effort traffic. A second observation is that for simple best-effort traffic, some form of rough flow-rate fairness is a useful goal for resource allocation, where "flow-rate fairness" is defined by the goal of equal flow rates for different flows over the same path. This memo provides information for the Internet community. | July 2008 Status: INFORMATIONAL Autor: S. Floyd, M. Allman |
| RFC5291 Outbound Route Filtering Capability for BGP-4 This document defines a BGP-based mechanism that allows a BGP speaker to send to its BGP peer a set of Outbound Route Filters (ORFs) that the peer would use to constrain/filter its outbound routing updates to the speaker. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: E. Chen, Y. Rekhter |
| RFC5292 Address-Prefix-Based Outbound Route Filter for BGP-4 This document defines a new Outbound Router Filter (ORF) type for BGP, termed "Address Prefix Outbound Route Filter", that can be used to perform address-prefix-based route filtering. This ORF-type supports prefix-length- or range-based matching, wild-card-based address prefix matching, as well as the exact address prefix matching for address families. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: E. Chen, S. Sangli |
| RFC5293 Sieve Email Filtering: Editheader Extension This document defines two new actions for the "Sieve" email filtering language that add and delete email header fields. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: J. Degener, P. Guenther |
| RFC5294 Host Threats to Protocol Independent Multicast (PIM) This memo complements the list of multicast infrastructure security threat analysis documents by describing Protocol Independent Multicast (PIM) threats specific to router interfaces connecting hosts. This memo provides information for the Internet community. | August 2008 Status: INFORMATIONAL Autor: P. Savola, J. Lingard |
| RFC5295 Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK) The Extensible Authentication Protocol (EAP) defined the Extended Master Session Key (EMSK) generation, but reserved it for unspecified future uses. This memo reserves the EMSK for the sole purpose of deriving root keys. Root keys are master keys that can be used for multiple purposes, identified by usage definitions. This document also specifies a mechanism for avoiding conflicts between root keys by deriving them in a manner that guarantees cryptographic separation. Finally, this document also defines one such root key usage: Domain-Specific Root Keys are root keys made available to and used within specific key management domains. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: J. Salowey, L. Dondeti, V. Narayanan, M. Nakhjiri |
| RFC5296 EAP Extensions for EAP Re-authentication Protocol (ERP) The Extensible Authentication Protocol (EAP) is a generic framework supporting multiple types of authentication methods. In systems where EAP is used for authentication, it is desirable to not repeat the entire EAP exchange with another authenticator. This document specifies extensions to EAP and the EAP keying hierarchy to support an EAP method-independent protocol for efficient re-authentication between the peer and an EAP re-authentication server through any authenticator. The re-authentication server may be in the home network or in the local network to which the peer is connecting. [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: V. Narayanan, L. Dondeti |
| RFC5297 Synthetic Initialization Vector (SIV) Authenticated Encryption Using the Advanced Encryption Standard (AES) This memo describes SIV (Synthetic Initialization Vector), a block cipher mode of operation. SIV takes a key, a plaintext, and multiple variable-length octet strings that will be authenticated but not encrypted. It produces a ciphertext having the same length as the plaintext and a synthetic initialization vector. Depending on how it is used, SIV achieves either the goal of deterministic authenticated encryption or the goal of nonce-based, misuse-resistant authenticated encryption. This memo provides information for the Internet community. | October 2008 Status: INFORMATIONAL Autor: D. Harkins |
| RFC5298 Analysis of Inter-Domain Label Switched Path (LSP) Recovery Protection and recovery are important features of service offerings in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. Increasingly, MPLS and GMPLS networks are being extended from single domain scope to multi-domain environments. | August 2008 Status: INFORMATIONAL Autor: T. Takeda, A. Farrel, Y. Ikejiri, JP. Vasseur |
| RFC5301 Dynamic Hostname Exchange Mechanism for IS-IS RFC 2763 defined a simple and dynamic mechanism for routers running IS-IS to learn about symbolic hostnames. RFC 2763 defined a new TLV that allows the IS-IS routers to flood their name-to-systemID mapping information across the IS-IS network. | October 2008 Status: PROPOSED STANDARD Autor: D. McPherson, N. Shen |
| RFC5302 Domain-Wide Prefix Distribution with Two-Level IS-IS This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support optimal routing within a two-level domain. The IS-IS protocol is specified in ISO 10589, with extensions for supporting IPv4 (Internet Protocol) specified in RFC 1195. This document replaces RFC 2966. | October 2008 Status: PROPOSED STANDARD Autor: T. Li, H. Smit, T. Przygienda |
| RFC5303 Three-Way Handshake for IS-IS Point-to-Point Adjacencies The IS-IS routing protocol (Intermediate System to Intermediate System, ISO 10589) requires reliable protocols at the link layer for point-to-point links. As a result, it does not use a three-way handshake when establishing adjacencies on point-to-point media. This paper defines a backward-compatible extension to the protocol that provides for a three-way handshake. It is fully interoperable with systems that do not support the extension. | October 2008 Status: PROPOSED STANDARD Autor: D. Katz, R. Saluja, D. Eastlake 3rd |
| RFC5304 IS-IS Cryptographic Authentication 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 replaces RFC 3567. | October 2008 Status: PROPOSED STANDARD Autor: T. Li, R. Atkinson |
| RFC5305 IS-IS Extensions for Traffic Engineering 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 Data Units (LSP). This information describes additional details regarding the state of the network that are useful for traffic engineering computations. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: T. Li, H. Smit |
| RFC5306 Restart Signaling for IS-IS 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. | October 2008 Status: PROPOSED STANDARD Autor: M. Shand, L. Ginsberg |
| RFC5307 IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS) This document specifies encoding of extensions to the IS-IS routing protocol in support of Generalized Multi-Protocol Label Switching (GMPLS). [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: K. Kompella, Y. Rekhter |
| RFC5308 Routing IPv6 with IS-IS This document specifies a method for exchanging IPv6 routing information using the IS-IS routing protocol. The described method utilizes two new TLVs: a reachability TLV and an interface address TLV to distribute the necessary IPv6 information throughout a routing domain. Using this method, one can route IPv6 along with IPv4 and OSI using a single intra-domain routing protocol. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: C. Hopps |
| RFC5309 Point-to-Point Operation over LAN in Link State Routing Protocols The two predominant circuit types used by link state routing protocols are point-to-point and broadcast. It is important to identify the correct circuit type when forming adjacencies, flooding link state database packets, and representing the circuit topologically. This document describes a simple mechanism to treat the broadcast network as a point-to-point connection from the standpoint of IP routing. This memo provides information for the Internet community. | October 2008 Status: INFORMATIONAL Autor: N. Shen, A. Zinin |
| RFC5310 IS-IS Generic Cryptographic Authentication This document proposes an extension to Intermediate System to Intermediate System (IS-IS) to allow the use of any cryptographic authentication algorithm in addition to the already-documented authentication schemes, described in the base specification and RFC 5304. IS-IS is specified in International Standards Organization (ISO) 10589, with extensions to support Internet Protocol version 4 (IPv4) described in RFC 1195. | February 2009 Status: PROPOSED STANDARD Autor: M. Bhatia, V. Manral, T. Li, R. Atkinson, R. White, M. Fanto |
| RFC5311 Simplified Extension of Link State PDU (LSP) Space for IS-IS This document describes a simplified method for extending the Link State PDU (LSP) space beyond the 256 LSP limit. This method is intended as a preferred replacement for the method defined in RFC 3786. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: D. McPherson, L. Ginsberg, S. Previdi, M. Shand |
| RFC5316 ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering This document describes extensions to the ISIS (ISIS) protocol to support Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems (ASes). It defines ISIS-TE extensions for the flooding of TE information about inter-AS links, which can be used to perform inter- AS TE path computation. | December 2008 Status: PROPOSED STANDARD Autor: M. Chen, R. Zhang, X. Duan |
| RFC5317 Joint Working Team (JWT) Report on MPLS Architectural Considerations for a Transport Profile This RFC archives the report of the IETF - ITU-T Joint Working Team (JWT) on the application of MPLS to transport networks. The JWT recommended of Option 1: The IETF and the ITU-T jointly agree to work together and bring transport requirements into the IETF and extend IETF MPLS forwarding, OAM (Operations, Administration, and Management), survivability, network management and control plane protocols to meet those requirements through the IETF Standards Process. This RFC is available in ASCII (which contains a summary of the slides) and in PDF (which contains the summary and a copy of the slides). This memo provides information for the Internet community. | February 2009 Status: INFORMATIONAL Autor: S. Bryant, L. Andersson |
| RFC5318 The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header) This document specifies the Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header). This P-Header is used in the Open Mobile Alliance's (OMA) Push to talk over Cellular (PoC) system. It enables URI-list servers to refuse the handling of incoming URI lists that have embedded URI lists. This P-Header also makes it possible for the URI-list server to inform the client about the embedded URI list that caused the rejection and the individual URIs that form such a URI list. This memo provides information for the Internet community. | December 2008 Status: INFORMATIONAL Autor: J. Hautakorpi, G. Camarillo |
| RFC5320 The Subnetwork Encapsulation and Adaptation Layer (SEAL) For the purpose of this document, subnetworks are defined as virtual topologies that span connected network regions bounded by encapsulating border nodes. These virtual topologies may span multiple IP and/or sub-IP layer forwarding hops, and can introduce failure modes due to packet duplication and/or links with diverse Maximum Transmission Units (MTUs). This document specifies a Subnetwork Encapsulation and Adaptation Layer (SEAL) that accommodates such virtual topologies over diverse underlying link technologies. This document defines an Experimental Protocol for the Internet community. | February 2010 Status: EXPERIMENTAL Autor: F. Templin |
| RFC5321 Simple Mail Transfer Protocol This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. Although SMTP was designed as a mail transport and delivery protocol, this specification also contains information that is important to its use as a "mail submission" protocol for "split-UA" (User Agent) mail reading systems and mobile environments. [STANDARDS-TRACK] | October 2008 Status: DRAFT STANDARD Autor: J. Klensin |
| RFC5322 Internet Message Format This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. [STANDARDS-TRACK] | October 2008 Status: DRAFT STANDARD Autor: P. Resnick |
| RFC5323 Web Distributed Authoring and Versioning (WebDAV) SEARCH This document specifies a set of methods, headers, and properties composing Web Distributed Authoring and Versioning (WebDAV) SEARCH, an application of the HTTP/1.1 protocol to efficiently search for DAV resources based upon a set of client-supplied criteria. [STANDARDS-TRACK] | November 2008 Status: PROPOSED STANDARD Autor: J. Reschke, S. Reddy, J. Davis, A. Babich |
| RFC5324 MIB for Fibre-Channel Security Protocols (FC-SP) 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 FC-SP, the Security Protocols defined for Fibre Channel. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: C. DeSanti, F. Maino, K. McCloghrie |
| RFC5325 Licklider Transmission Protocol - Motivation This document describes the motivation for the development of the Licklider Transmission Protocol (LTP) designed to provide retransmission-based reliability over links characterized by extremely long message round-trip times (RTTs) and/or frequent interruptions in connectivity. Since communication across interplanetary space is the most prominent example of this sort of environment, LTP is principally aimed at supporting "long-haul" reliable transmission in interplanetary space, but it has applications in other environments as well. | September 2008 Status: INFORMATIONAL Autor: S. Burleigh, M. Ramadas, S. Farrell |
| RFC5326 Licklider Transmission Protocol - Specification This document describes the Licklider Transmission Protocol (LTP), designed to provide retransmission-based reliability over links characterized by extremely long message round-trip times (RTTs) and/or frequent interruptions in connectivity. Since communication across interplanetary space is the most prominent example of this sort of environment, LTP is principally aimed at supporting "long-haul" reliable transmission in interplanetary space, but it has applications in other environments as well. | September 2008 Status: EXPERIMENTAL Autor: M. Ramadas, S. Burleigh, S. Farrell |
| RFC5327 Licklider Transmission Protocol - Security Extensions The Licklider Transmission Protocol (LTP) is intended to serve as a reliable convergence layer over single-hop deep-space radio frequency (RF) links. LTP does Automatic Repeat reQuest (ARQ) of data transmissions by soliciting selective-acknowledgment reception reports. It is stateful and has no negotiation or handshakes. This document describes security extensions to LTP, and is part of a series of related documents describing LTP. | September 2008 Status: EXPERIMENTAL Autor: S. Farrell, M. Ramadas, S. Burleigh |
| RFC5328 A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB) This document describes a Uniform Resource Name (URN) namespace for the Digital Video Broadcasting Project (DVB) for naming persistent resources defined within DVB 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 DVB. This memo provides information for the Internet community. | September 2008 Status: INFORMATIONAL Autor: A. Adolf, P. MacAvock |
| RFC5329 Traffic Engineering Extensions to OSPF Version 3 This document describes extensions to OSPFv3 to support intra-area Traffic Engineering (TE). This document extends OSPFv2 TE to handle IPv6 networks. A new TLV and several new sub-TLVs are defined to support IPv6 networks. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: K. Ishiguro, V. Manral, A. Davey, A. Lindem |
| RFC5330 A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link Several Link-type sub-Type-Length-Values (sub-TLVs) have been defined for Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (IS-IS) in the context of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE), in order to advertise some link characteristics such as the available bandwidth, traffic engineering metric, administrative group, and so on. By making statistical assumptions about the aggregated traffic carried onto a set of TE Label Switched Paths (LSPs) signalled with zero bandwidth (referred to as "unconstrained TE LSP" in this document), algorithms can be designed to load balance (existing or newly configured) unconstrained TE LSP across a set of equal cost paths. This requires knowledge of the number of unconstrained TE LSPs signalled across a link. This document specifies a new Link-type Traffic Engineering sub-TLV used to advertise the number of unconstrained TE LSPs signalled across a link. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: JP. Vasseur, M. Meyer, K. Kumaki, A. Bonda |
| RFC5331 MPLS Upstream Label Assignment and Context-Specific Label Space RFC 3031 limits the MPLS architecture to downstream-assigned MPLS labels. This document introduces the notion of upstream-assigned MPLS labels. It describes the procedures for upstream MPLS label assignment and introduces the concept of a "Context-Specific Label Space". [STANDARDS-TRACK] | August 2008 Status: PROPOSED STANDARD Autor: R. Aggarwal, Y. Rekhter, E. Rosen |
| RFC5332 MPLS Multicast Encapsulations RFC 3032 established two data link layer codepoints for MPLS, used to distinguish whether the data link layer frame is carrying an MPLS unicast or an MPLS multicast packet. However, this usage was never deployed. This specification updates RFC 3032 by redefining the meaning of these two codepoints. Both codepoints can now be used to carry multicast packets. The second codepoint (formerly the "multicast codepoint") is now to be used only on multiaccess media, and it is to mean "the top label of the following label stack is an upstream-assigned label". | August 2008 Status: PROPOSED STANDARD Autor: T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter |
| RFC5333 IANA Registration of Enumservices for Internet Calendaring This document registers Enumservices for Internet calendaring. Specifically, this document focuses on Enumservices for scheduling with iMIP (iCalendar Message-Based Interoperability Protocol) and for accessing Internet calendaring information with CalDAV (Calendaring Extensions to WebDAV). [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: R. Mahy, B. Hoeneisen |
| RFC5334 Ogg Media Types This document describes the registration of media types for the Ogg container format and conformance requirements for implementations of these types. This document obsoletes RFC 3534. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: I. Goncalves, S. Pfeiffer, C. Montgomery |
| RFC5335 Internationalized Email Headers Full internationalization of electronic mail requires not only the capabilities to transmit non-ASCII content, to encode selected information in specific header fields, and to use non-ASCII characters in envelope addresses. It also requires being able to express those addresses and the information based on them in mail header fields. This document specifies an experimental variant of Internet mail that permits the use of Unicode encoded in UTF-8, rather than ASCII, as the base form for Internet email header field. This form is permitted in transmission only if authorized by an SMTP extension, as specified in an associated specification. This specification Updates section 6.4 of RFC 2045 to conform with the requirements. This memo defines an Experimental Protocol for the Internet community. | September 2008 Status: EXPERIMENTAL Autor: A. Yang |
| RFC5336 SMTP Extension for Internationalized Email Addresses This document specifies an SMTP extension for transport and delivery of email messages with internationalized email addresses or header information. Communication with systems that do not implement this specification is specified in another document. This document updates some syntaxes and rules defined in RFC 2821 and RFC 2822, and has some material updating RFC 4952This memo defines an Experimental Protocol for the Internet community. | September 2008 Status: EXPERIMENTAL Autor: J. Yao, W. Mao |
| RFC5337 Internationalized Delivery Status and Disposition Notifications Delivery status notifications (DSNs) are critical to the correct operation of an email system. However, the existing Draft Standards (RFC 3461, RFC 3462, RFC 3464) are presently limited to US-ASCII text in the machine-readable portions of the protocol. This specification adds a new address type for international email addresses so an original recipient address with non-US-ASCII characters can be correctly preserved even after downgrading. This also provides updated content return media types for delivery status notifications and message disposition notifications to support use of the new address type. | September 2008 Status: EXPERIMENTAL Autor: C. Newman, A. Melnikov |
| RFC5338 Using the Host Identity Protocol with Legacy Applications This document is an informative overview of how legacy applications can be made to work with the Host Identity Protocol (HIP). HIP proposes to add a cryptographic name space for network stack names. From an application viewpoint, HIP-enabled systems support a new address family of host identifiers, but it may be a long time until such HIP-aware applications are widely deployed even if host systems are upgraded. This informational document discusses implementation and Application Programming Interface (API) issues relating to using HIP in situations in which the system is HIP-aware but the applications are not, and is intended to aid implementors and early adopters in thinking about and locally solving systems issues regarding the incremental deployment of HIP. This memo provides information for the Internet community. | September 2008 Status: EXPERIMENTAL Autor: T. Henderson, P. Nikander, M. Komu |
| RFC5339 Evaluation of Existing GMPLS Protocols against Multi-Layer and Multi-Region Networks (MLN/MRN) This document provides an evaluation of Generalized Multiprotocol Label Switching (GMPLS) protocols and mechanisms against the requirements for Multi-Layer Networks (MLNs) and Multi-Region Networks (MRNs). In addition, this document identifies areas where additional protocol extensions or procedures are needed to satisfy these requirements, and provides guidelines for potential extensions. This memo provides information for the Internet community. | September 2008 Status: INFORMATIONAL Autor: JL. Le Roux, D. Papadimitriou |
| RFC5340 OSPF for IPv6 This document describes the modifications to OSPF to support version 6 of the Internet Protocol (IPv6). The fundamental mechanisms of OSPF (flooding, Designated Router (DR) election, area support, Short Path First (SPF) calculations, etc.) remain unchanged. However, some changes have been necessary, either due to changes in protocol semantics between IPv4 and IPv6, or simply to handle the increased address size of IPv6. These modifications will necessitate incrementing the protocol version from version 2 to version 3. OSPF for IPv6 is also referred to as OSPF version 3 (OSPFv3). | July 2008 Status: PROPOSED STANDARD Autor: R. Coltun, D. Ferguson, J. Moy, A. Lindem |
| RFC5341 The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry This document creates an Internet Assigned Number Authority (IANA) registry for tel Uniform Resource Identifier (URI) parameters and their values. It populates the registry with the parameters defined in the tel URI specification, along with the parameters in tel URI extensions defined for number portability and trunk groups. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: C. Jennings, V. Gurbani |
| RFC5342 IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses some use of such parameters in IETF protocols and specifies IANA considerations for allocation of code points under the IANA OUI (Organizationally Unique Identifier). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 2008 Status: BEST CURRENT PRACTICE Autor: D. Eastlake 3rd |
| RFC5343 Simple Network Management Protocol (SNMP) Context EngineID Discovery The Simple Network Management Protocol (SNMP) version three (SNMPv3) requires that an application know the identifier (snmpEngineID) of the remote SNMP protocol engine in order to retrieve or manipulate objects maintained on the remote SNMP entity. | September 2008 Status: DRAFT STANDARD Autor: J. Schoenwaelder |
| RFC5344 Presence and Instant Messaging Peering Use Cases This document describes several use cases of peering of non-VoIP (Voice over IP) services between two or more Service Providers. These Service Providers create a peering relationship between themselves, thus enabling their users to collaborate with users on the other Service Provider network. The target of this document is to drive requirements for peering between domains that provide the non-VoIP based collaboration services with presence and, in particular, Instant Messaging (IM). This memo provides information for the Internet community. | October 2008 Status: INFORMATIONAL Autor: A. Houri, E. Aoki, S. Parameswar |
| RFC5345 Simple Network Management Protocol (SNMP) Traffic Measurements and Trace Exchange Formats The Simple Network Management Protocol (SNMP) is widely deployed to monitor, control, and (sometimes also) configure network elements. Even though the SNMP technology is well documented, it remains relatively unclear how SNMP is used in practice and what typical SNMP usage patterns are. | October 2008 Status: INFORMATIONAL Autor: J. Schoenwaelder |
| RFC5346 Operational Requirements for ENUM-Based Softswitch Use This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean Voice over IP (VoIP) carriers, gained during the ENUM pre-commercial trial hosted by the National Internet Development Agency of Korea (NIDA) in 2006. | October 2008 Status: INFORMATIONAL Autor: J. Lim, W. Kim, C. Park, L. Conroy |
| RFC5347 Media Gateway Control Protocol Fax Package This document defines a Media Gateway Control Protocol (MGCP) package to support fax calls. The package allows for fax calls to be supported in two different ways. The first one utilizes ITU-T Recommendation T.38 for fax relay under the control of the Call Agent. The second one lets the gateway decide upon a method for fax transmission as well as handle the details of the fax call without Call Agent involvement. This memo provides information for the Internet community. | October 2008 Status: INFORMATIONAL Autor: F. Andreasen, D. Hancock |
| RFC5348 TCP Friendly Rate Control (TFRC): Protocol Specification 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 streaming media where a relatively smooth sending rate is of importance. | September 2008 Status: PROPOSED STANDARD Autor: S. Floyd, M. Handley, J. Padhye, J. Widmer |
| RFC5349 Elliptic Curve Cryptography (ECC) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) This document describes the use of Elliptic Curve certificates, Elliptic Curve signature schemes and Elliptic Curve Diffie-Hellman (ECDH) key agreement within the framework of PKINIT -- the Kerberos Version 5 extension that provides for the use of public key cryptography. This memo provides information for the Internet community. | September 2008 Status: INFORMATIONAL Autor: L. Zhu, K. Jaganathan, K. Lauter |
| RFC5350 IANA Considerations for the IPv4 and IPv6 Router Alert Options This document updates the IANA allocation rules and registry of IPv4 and IPv6 Router Alert Option Values. [STANDARDS-TRACK] | September 2008 Status: PROPOSED STANDARD Autor: J. Manner, A. McDonald |
| RFC5351 An Overview of Reliable Server Pooling Protocols The Reliable Server Pooling effort (abbreviated "RSerPool") provides an application-independent set of services and protocols for building fault-tolerant and highly available client/server applications. This document provides an overview of the protocols and mechanisms in the Reliable Server Pooling suite. This memo provides information for the Internet community. | September 2008 Status: INFORMATIONAL Autor: P. Lei, L. Ong, M. Tuexen, T. Dreibholz |
| RFC5352 Aggregate Server Access Protocol (ASAP) Aggregate Server Access Protocol (ASAP; RFC 5352), in conjunction with the Endpoint Handlespace Redundancy Protocol (ENRP; RFC 5353), provides a high-availability data transfer mechanism over IP networks. ASAP uses a handle-based addressing model that isolates a logical communication endpoint from its IP address(es), thus effectively eliminating the binding between the communication endpoint and its physical IP address(es), which normally constitutes a single point of failure. | September 2008 Status: EXPERIMENTAL Autor: R. Stewart, Q. Xie, M. Stillman, M. Tuexen |
| RFC5353 Endpoint Handlespace Redundancy Protocol (ENRP) The Endpoint Handlespace Redundancy Protocol (ENRP) is designed to work in conjunction with the Aggregate Server Access Protocol (ASAP) to accomplish the functionality of the Reliable Server Pooling (RSerPool) requirements and architecture. Within the operational scope of RSerPool, ENRP defines the procedures and message formats of a distributed, fault-tolerant registry service for storing, bookkeeping, retrieving, and distributing pool operation and membership information. This memo defines an Experimental Protocol for the Internet community. | September 2008 Status: EXPERIMENTAL Autor: Q. Xie, R. Stewart, M. Stillman, M. Tuexen, A. Silverton |
| RFC5354 Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters This document details the parameters of the Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) defined within the Reliable Server Pooling (RSerPool) architecture. This memo defines an Experimental Protocol for the Internet community. | September 2008 Status: EXPERIMENTAL Autor: R. Stewart, Q. Xie, M. Stillman, M. Tuexen |
| RFC5355 Threats Introduced by Reliable Server Pooling (RSerPool) and Requirements for Security in Response to Threats Reliable Server Pooling (RSerPool) is an architecture and set of protocols for the management and access to server pools supporting highly reliable applications and for client access mechanisms to a server pool. This document describes security threats to the RSerPool architecture and presents requirements for security to thwart these threats. This memo provides information for the Internet community. | September 2008 Status: INFORMATIONAL Autor: M. Stillman, R. Gopal, E. Guttman, S. Sengodan, M. Holdrege |
| RFC5356 Reliable Server Pooling Policies This document describes server pool policies for Reliable Server Pooling (RSerPool) including considerations for implementing them at Endpoint Handlespace Redundancy Protocol (ENRP) servers and pool users. This memo defines an Experimental Protocol for the Internet community. | September 2008 Status: EXPERIMENTAL Autor: T. Dreibholz, M. Tuexen |
| RFC5357 A Two-Way Active Measurement Protocol (TWAMP) The One-way Active Measurement Protocol (OWAMP), specified in RFC 4656, provides a common protocol for measuring one-way metrics between network devices. OWAMP can be used bi-directionally to measure one-way metrics in both directions between two network elements. However, it does not accommodate round-trip or two-way measurements. This memo specifies a Two-Way Active Measurement Protocol (TWAMP), based on the OWAMP, that adds two-way or round-trip measurement capabilities. The TWAMP measurement architecture is usually comprised of two hosts with specific roles, and this allows for some protocol simplifications, making it an attractive alternative in some circumstances. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: K. Hedayat, R. Krzanowski, A. Morton, K. Yum, J. Babiarz |
| RFC5358 Preventing Use of Recursive Nameservers in Reflector Attacks This document describes ways to prevent the use of default configured recursive nameservers as reflectors in Denial of Service (DoS) attacks. It provides recommended configuration as measures to mitigate the attack. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 2008 Status: BEST CURRENT PRACTICE Autor: J. Damas, F. Neves |
| RFC5359 Session Initiation Protocol Service Examples This document gives examples of Session Initiation Protocol (SIP) services. This covers most features offered in so-called IP Centrex offerings from local exchange carriers and PBX (Private Branch Exchange) features. Most of the services shown in this document are implemented in the SIP user agents, although some require the assistance of a SIP proxy. Some require some extensions to SIP including the REFER, SUBSCRIBE, and NOTIFY methods and the Replaces and Join header fields. These features are not intended to be an exhaustive set, but rather show implementations of common features likely to be implemented on SIP IP telephones in a business environment. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 2008 Status: BEST CURRENT PRACTICE Autor: A. Johnston, R. Sparks, C. Cunningham, S. Donovan, K. Summers |
| RFC5360 A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP) SIP supports communications for several services, including real-time audio, video, text, instant messaging, and presence. In its current form, it allows session invitations, instant messages, and other requests to be delivered from one party to another without requiring explicit consent of the recipient. Without such consent, it is possible for SIP to be used for malicious purposes, including amplification and DoS (Denial of Service) attacks. This document identifies a framework for consent-based communications in SIP. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: J. Rosenberg, G. Camarillo, D. Willis |
| RFC5361 A Document Format for Requesting Consent This document defines an Extensible Markup Language (XML) format for a permission document used to request consent. A permission document written in this format is used by a relay to request a specific recipient permission to perform a particular routing translation. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC5362 The Session Initiation Protocol (SIP) Pending Additions Event Package This document defines the SIP Pending Additions event package. This event package is used by SIP relays to inform user agents about the consent-related status of the entries to be added to a resource list. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC5363 Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services This document describes the need for SIP URI-list services and provides requirements for their invocation. Additionally, it defines a framework for SIP URI-list services, which includes security considerations applicable to these services. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: G. Camarillo, A.B. Roach |
| RFC5364 Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists In certain types of multimedia communications, a Session Initiation Protocol (SIP) request is distributed to a group of SIP User Agents (UAs). The sender sends a single SIP request to a server which further distributes the request to the group. This SIP request contains a list of Uniform Resource Identifiers (URIs), which identify the recipients of the SIP request. This URI list is expressed as a resource list XML document. This specification defines an XML extension to the XML resource list format that allows the sender of the request to qualify a recipient with a copy control level similar to the copy control level of existing email systems. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: M. Garcia-Martin, G. Camarillo |
| RFC5365 Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP) This document specifies a mechanism that allows a SIP User Agent Client (UAC) to send a SIP MESSAGE request to a set of destinations, by using a SIP URI-list (Uniform Resource Identifier list) service. The UAC sends a SIP MESSAGE request that includes the payload along with the URI list to the MESSAGE URI-list service, which sends a MESSAGE request including the payload to each of the URIs included in the list. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: M. Garcia-Martin, G. Camarillo |
| RFC5366 Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP) This document describes how to create a conference using SIP URI-list services. In particular, it describes a mechanism that allows a User Agent Client to provide a conference server with the initial list of participants using an INVITE-contained URI list. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: G. Camarillo, A. Johnston |
| RFC5367 Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP) This document specifies a way to create subscription to a list of resources in SIP. This is achieved by including the list of resources in the body of a SUBSCRIBE request. Instead of having a subscriber send a SUBSCRIBE request for each resource individually, the subscriber defines the resource list, subscribes to it, and gets notifications about changes in the resources' states using a single SUBSCRIBE dialog. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: G. Camarillo, A.B. Roach, O. Levin |
| RFC5368 Referring to Multiple Resources in the Session Initiation Protocol (SIP) This document defines extensions to the SIP REFER method so that it can be used to refer to multiple resources in a single request. These extensions include the use of pointers to Uniform Resource Identifier (URI) lists in the Refer-To header field and the "multiple-refer" SIP option-tag. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: G. Camarillo, A. Niemi, M. Isomaki, M. Garcia-Martin, H. Khartabil |
| RFC5369 Framework for Transcoding with the Session Initiation Protocol (SIP) This document defines a framework for transcoding with SIP. This framework includes how to discover the need for transcoding services in a session and how to invoke those transcoding services. Two models for transcoding services invocation are discussed: the conference bridge model and the third-party call control model. Both models meet the requirements for SIP regarding transcoding services invocation to support deaf, hard of hearing, and speech-impaired individuals. This memo provides information for the Internet community. | October 2008 Status: INFORMATIONAL Autor: G. Camarillo |
| RFC5370 The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model This document describes how to invoke transcoding services using the conference bridge model. This way of invocation meets the requirements for SIP regarding transcoding services invocation to support deaf, hard of hearing, and speech-impaired individuals. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC5371 RTP Payload Format for JPEG 2000 Video Streams This memo describes an RTP payload format for the ISO/IEC International Standard 15444-1 | ITU-T Rec. T.800, better known as JPEG 2000. JPEG 2000 features are considered in the design of this payload format. JPEG 2000 is a truly scalable compression technology allowing applications to encode once and decode many different ways. The JPEG 2000 video stream is formed by extending from a single image to a series of JPEG 2000 images. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: S. Futemma, E. Itakura, A. Leung |
| RFC5372 Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery This memo describes extended uses for the payload header in "RTP Payload Format for JPEG 2000 Video Streams" as specified in RFC 5371, for better support of JPEG 2000 features such as scalability and main header recovery. | October 2008 Status: PROPOSED STANDARD Autor: A. Leung, S. Futemma, E. Itakura |
| RFC5373 Requesting Answering Modes for the Session Initiation Protocol (SIP) This document extends SIP with two header fields and associated option tags that can be used in INVITE requests to convey the requester's preference for user-interface handling related to answering of that request. The first header, "Answer-Mode", expresses a preference as to whether the target node's user interface waits for user input before accepting the request or, instead, accepts the request without waiting on user input. The second header, "Priv-Answer-Mode", is similar to the first, except that it requests administrative-level access and has consequent additional authentication and authorization requirements. These behaviors have applicability to applications such as push-to-talk and to diagnostics like loop-back. Usage of each header field in a response to indicate how the request was handled is also defined. [STANDARDS-TRACK] | November 2008 Status: PROPOSED STANDARD Autor: D. Willis, A. Allen |
| RFC5374 Multicast Extensions to the Security Architecture for the Internet Protocol The Security Architecture for the Internet Protocol describes security services for traffic at the IP layer. That architecture primarily defines services for Internet Protocol (IP) unicast packets. This document describes how the IPsec security services are applied to IP multicast packets. These extensions are relevant only for an IPsec implementation that supports multicast. [STANDARDS-TRACK] | November 2008 Status: PROPOSED STANDARD Autor: B. Weis, G. Gross, D. Ignjatic |
| RFC5375 IPv6 Unicast Address Assignment Considerations One fundamental aspect of any IP communications infrastructure is its addressing plan. With its new address architecture and allocation policies, the introduction of IPv6 into a network means that network designers and operators need to reconsider their existing approaches to network addressing. Lack of guidelines on handling this aspect of network design could slow down the deployment and integration of IPv6. This document aims to provide the information and recommendations relevant to planning the addressing aspects of IPv6 deployments. The document also provides IPv6 addressing case studies for both an enterprise and an ISP network. This memo provides information for the Internet community. | December 2008 Status: INFORMATIONAL Autor: G. Van de Velde, C. Popoviciu, T. Chown, O. Bonness, C. Hahn |
| RFC5376 Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP) Multiprotocol Label Switching Traffic Engineered (MPLS TE) Label Switched Paths (LSPs) may be established wholly within an Autonomous System (AS) or may cross AS boundaries. | November 2008 Status: INFORMATIONAL Autor: N. Bitar, R. Zhang, K. Kumaki |
| RFC5377 Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents Contributors grant intellectual property rights to the IETF. The IETF Trust holds and manages those rights on behalf of the IETF. The Trustees of the IETF Trust are responsible for that management. This management includes granting the licenses to copy, implement, and otherwise use IETF Contributions, among them Internet-Drafts and RFCs. The Trustees of the IETF Trust accepts direction from the IETF regarding the rights to be granted. This document describes the desires of the IETF regarding outbound rights to be granted in IETF Contributions. This memo provides information for the Internet community. | November 2008 Status: INFORMATIONAL Autor: J. Halpern |
| RFC5378 Rights Contributors Provide to the IETF Trust 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 obsoletes RFCs 3978 and 4748 and, with BCP 79 and RFC 5377, 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. | November 2008 Status: BEST CURRENT PRACTICE Autor: S. Bradner, J. Contreras |
| RFC5379 Guidelines for Using the Privacy Mechanism for SIP This is an informational document that provides guidelines for using the privacy mechanism for the Session Initiation Protocol (SIP) that is specified in RFC 3323 and subsequently extended in RFCs 3325 and 4244. It is intended to clarify the handling of the target SIP headers/parameters and the Session Description Protocol (SDP) parameters for each of the privacy header values (priv-values). This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: M. Munakata, S. Schubert, T. Ohba |
| RFC5380 Hierarchical Mobile IPv6 (HMIPv6) Mobility Management This document introduces extensions to Mobile IPv6 and IPv6 Neighbour Discovery to allow for local mobility handling. Hierarchical mobility management for Mobile IPv6 is designed to reduce the amount of signalling between the mobile node, its correspondent nodes, and its home agent. The Mobility Anchor Point (MAP) described in this document can also be used to improve the performance of Mobile IPv6 in terms of handover speed. [STANDARDS-TRACK] | October 2008 Status: PROPOSED STANDARD Autor: H. Soliman, C. Castelluccia, K. ElMalki, L. Bellier |
| RFC5381 Experience of Implementing NETCONF over SOAP This document describes how the authors developed a SOAP (Simple Object Access Protocol)-based NETCONF (Network Configuration Protocol) client and server. It describes an alternative SOAP binding for NETCONF that does not interoperate with an RFC 4743 conformant implementation making use of cookies on top of the persistent transport connections of HTTP. When SOAP is used as a transport protocol for NETCONF, various kinds of development tools are available. By making full use of these tools, developers can significantly reduce their workload. The authors developed an NMS (Network Management System) and network equipment that can deal with NETCONF messages sent over SOAP. This document aims to provide NETCONF development guidelines gained from the experience of implementing a SOAP-based NETCONF client and server. This memo provides information for the Internet community. | October 2008 Status: INFORMATIONAL Autor: T. Iijima, Y. Atarashi, H. Kimura, M. Kitani, H. Okita |
| RFC5382 NAT Behavioral Requirements for TCP This document defines a set of requirements for NATs that handle TCP that would allow many applications, such as peer-to-peer applications and online games to work consistently. Developing NATs that meet this set of requirements will greatly increase the likelihood that these applications will function properly. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 2008 Status: BEST CURRENT PRACTICE Autor: S. Guha, K. Biswas, B. Ford, S. Sivakumar, P. Srisuresh |
| RFC5383 Deployment Considerations for Lemonade-Compliant Mobile Email This document discusses deployment issues and describes requirements for successful deployment of mobile email that are implicit in the IETF lemonade documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 2008 Status: BEST CURRENT PRACTICE Autor: R. Gellens |
| RFC5384 The Protocol Independent Multicast (PIM) Join Attribute Format A "Protocol Independent Multicast - Sparse Mode" Join message sent by a given node identifies one or more multicast distribution trees that that node wishes to join. Each tree is identified by the combination of a multicast group address and a source address (where the source address is possibly a "wild card"). Under certain conditions it can be useful, when joining a tree, to specify additional information related to the construction of the tree. However, there has been no way to do so until now. This document describes a modification of the Join message that allows a node to associate attributes with a particular tree. The attributes are encoded in Type-Length-Value format. [STANDARDS-TRACK] | November 2008 Status: PROPOSED STANDARD Autor: A. Boers, I. Wijnands, E. Rosen |
| RFC5385 Version 2.0 Microsoft Word Template for Creating Internet Drafts and RFCs This document describes the properties and use of a revised Microsoft Word template (.dot) for writing Internet Drafts and RFCs. It replaces the initial template described in RFC 3285 to more fully support Word's outline modes and to be easier to use. This template can be direct-printed and direct-viewed, where either is line-for-line identical with RFC Editor-compliant ASCII output. This version obsoletes RFC 3285. | February 2010 Status: INFORMATIONAL Autor: J. Touch |
| RFC5386 Better-Than-Nothing Security: An Unauthenticated Mode of IPsec This document specifies how to use the Internet Key Exchange (IKE) protocols, such as IKEv1 and IKEv2, to setup "unauthenticated" security associations (SAs) for use with the IPsec Encapsulating Security Payload (ESP) and the IPsec Authentication Header (AH). No changes to IKEv2 bits-on-the-wire are required, but Peer Authorization Database (PAD) and Security Policy Database (SPD) extensions are specified. Unauthenticated IPsec is herein referred to by its popular acronym, "BTNS" (Better-Than-Nothing Security). [STANDARDS-TRACK] | November 2008 Status: PROPOSED STANDARD Autor: N. Williams, M. Richardson |
| RFC5387 Problem and Applicability Statement for Better-Than-Nothing Security (BTNS) The Internet network security protocol suite, IPsec, requires authentication, usually of network-layer entities, to enable access control and provide security services. This authentication can be based on mechanisms such as pre-shared symmetric keys, certificates with associated asymmetric keys, or the use of Kerberos (via Kerberized Internet Negotiation of Keys (KINK)). The need to deploy authentication information and its associated identities can be a significant obstacle to the use of IPsec. | November 2008 Status: INFORMATIONAL Autor: J. Touch, D. Black, Y. Wang |
| RFC5388 Information Model and XML Data Model for Traceroute Measurements This document describes a standard way to store the configuration and the results of traceroute measurements. This document first describes the terminology used in this document and the traceroute tool itself; afterwards, the common information model is defined, dividing the information elements into two semantically separated groups (configuration elements and results elements). Moreover, an additional element is defined to relate configuration elements and results elements by means of a common unique identifier. On the basis of the information model, a data model based on XML is defined to store the results of traceroute measurements. [STANDARDS-TRACK] | December 2008 Status: PROPOSED STANDARD Autor: S. Niccolini, S. Tartarelli, J. Quittek, T. Dietz, M. Swany |
| RFC5389 Session Traversal Utilities for NAT (STUN) Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with Network Address Translator (NAT) traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints, and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs, and does not require any special behavior from them. | October 2008 Status: PROPOSED STANDARD Autor: J. Rosenberg, R. Mahy, P. Matthews, D. Wing |
| RFC5390 Requirements for Management of Overload in the Session Initiation Protocol Overload occurs in Session Initiation Protocol (SIP) networks when proxies and user agents have insufficient resources to complete the processing of a request. SIP provides limited support for overload handling through its 503 response code, which tells an upstream element that it is overloaded. However, numerous problems have been identified with this mechanism. This document summarizes the problems with the existing 503 mechanism, and provides some requirements for a solution. This memo provides information for the Internet community. | December 2008 Status: INFORMATIONAL Autor: J. Rosenberg |
| RFC5391 RTP Payload Format for ITU-T Recommendation G.711.1 This document specifies a Real-time Transport Protocol (RTP) payload format to be used for the ITU Telecommunication Standardization Sector (ITU-T) G.711.1 audio codec. Two media type registrations are also included. [STANDARDS-TRACK] | November 2008 Status: PROPOSED STANDARD Autor: A. Sollaud |
| RFC5392 OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering This document describes extensions to the OSPF version 2 and 3 protocols to support Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems (ASes). OSPF-TE v2 and v3 extensions are defined for the flooding of TE information about inter-AS links that can be used to perform inter-AS TE path computation. | January 2009 Status: PROPOSED STANDARD Autor: M. Chen, R. Zhang, X. Duan |
| RFC5393 Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies This document normatively updates RFC 3261, the Session Initiation Protocol (SIP), to address a security vulnerability identified in SIP proxy behavior. This vulnerability enables an attack against SIP networks where a small number of legitimate, even authorized, SIP requests can stimulate massive amounts of proxy-to-proxy traffic. | December 2008 Status: PROPOSED STANDARD Autor: R. Sparks, S. Lawrence, A. Hawrylyshen, B. Campen |
| RFC5394 Policy-Enabled Path Computation Framework The Path Computation Element (PCE) architecture introduces the concept of policy in the context of path computation. This document provides additional details on policy within the PCE architecture and also provides context for the support of PCE Policy. This document introduces the use of the Policy Core Information Model (PCIM) as a framework for supporting path computation policy. This document also provides representative scenarios for the support of PCE Policy. This memo provides information for the Internet community. | December 2008 Status: INFORMATIONAL Autor: I. Bryskin, D. Papadimitriou, L. Berger, J. Ash |
| RFC5395 Domain Name System (DNS) IANA Considerations Internet Assigned Number Authority (IANA) parameter assignment considerations are specified for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | November 2008 Status: BEST CURRENT PRACTICE Autor: D. Eastlake 3rd |
| RFC5396 Textual Representation of Autonomous System (AS) Numbers A textual representation for Autonomous System (AS) numbers is defined as the decimal value of the AS number. This textual representation is to be used by all documents, systems, and user interfaces referring to AS numbers. [STANDARDS-TRACK] | December 2008 Status: PROPOSED STANDARD Autor: G. Huston, G. Michaelson |
| RFC5397 WebDAV Current Principal Extension This specification defines a new WebDAV property that allows clients to quickly determine the principal corresponding to the current authenticated user. [STANDARDS-TRACK] | December 2008 Status: PROPOSED STANDARD Autor: W. Sanchez, C. Daboo |
| RFC5398 Autonomous System (AS) Number Reservation for Documentation Use To reduce the likelihood of conflict and confusion when relating documented examples to deployed systems, two blocks of Autonomous System numbers (ASNs) are reserved for use in examples in RFCs, books, documentation, and the like. This document describes the reservation of two blocks of ASNs as reserved numbers for use in documentation. This memo provides information for the Internet community. | December 2008 Status: INFORMATIONAL Autor: G. Huston |
| RFC5401 Multicast Negative-Acknowledgment (NACK) Building Blocks This document discusses the creation of reliable multicast protocols that utilize negative-acknowledgment (NACK) feedback. The rationale for protocol design goals and assumptions are presented. Technical challenges for NACK-based (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 reliable multicast protocol operation. It is anticipated that these building blocks will be useful in generating different instantiations of reliable multicast protocols. This document obsoletes RFC 3941. [STANDARDS-TRACK] | November 2008 Status: PROPOSED STANDARD Autor: B. Adamson, C. Bormann, M. Handley, J. Macker |
| RFC5402 Compressed Data within an Internet Electronic Data Interchange (EDI) Message This document explains the rules and procedures for utilizing compression (RFC 3274) within an Internet EDI (Electronic Data Interchange) 'AS' message, as defined in RFCs 3335, 4130, and 4823. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: T. Harding |
| RFC5403 RPCSEC_GSS Version 2 This document describes version 2 of the RPCSEC_GSS protocol. Version 2 is the same as version 1 (specified in RFC 2203) except that support for channel bindings has been added. RPCSEC_GSS allows remote procedure call (RPC) protocols to access the Generic Security Services Application Programming Interface (GSS-API). [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: M. Eisler |
| RFC5404 RTP Payload Format for G.719 This document specifies the payload format for packetization of the G.719 full-band codec encoded audio signals into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple channels, multiple frames per payload, and interleaving. [STANDARDS-TRACK] | January 2009 Status: PROPOSED STANDARD Autor: M. Westerlund, I. Johansson |
| RFC5405 Unicast UDP Usage Guidelines for Application Designers The User Datagram Protocol (UDP) provides a minimal message-passing transport that has no inherent congestion control mechanisms. Because congestion control is critical to the stable operation of the Internet, applications and upper-layer protocols that choose to use UDP as an Internet transport must employ mechanisms to prevent congestion collapse and to establish some degree of fairness with concurrent traffic. This document provides guidelines on the use of UDP for the designers of unicast applications and upper-layer protocols. Congestion control guidelines are a primary focus, but the document also provides guidance on other topics, including message sizes, reliability, checksums, and middlebox traversal. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | November 2008 Status: BEST CURRENT PRACTICE Autor: L. Eggert, G. Fairhurst |
| RFC5406 Guidelines for Specifying the Use of IPsec Version 2 The Security Considerations sections of many Internet Drafts say, in effect, "just use IPsec". While this is sometimes correct, more often it will leave users without real, interoperable security mechanisms. This memo offers some guidance on when IPsec Version 2 should and should not be specified. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | February 2009 Status: BEST CURRENT PRACTICE Autor: S. Bellovin |
| RFC5407 Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP) This document gives example call flows of race conditions in the Session Initiation Protocol (SIP). Race conditions are inherently confusing and difficult to thwart; this document shows the best practices to handle them. The elements in these call flows include SIP User Agents and SIP Proxy Servers. Call flow diagrams and message details are given. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | December 2008 Status: BEST CURRENT PRACTICE Autor: M. Hasebe, J. Koshiko, Y. Suzuki, T. Yoshikawa, P. Kyzivat |
| RFC5408 Identity-Based Encryption Architecture and Supporting Data Structures This document describes the security architecture required to implement identity-based encryption, a public-key encryption technology that uses a user's identity as a public key. It also defines data structures that can be used to implement the technology. This memo provides information for the Internet community. | January 2009 Status: INFORMATIONAL Autor: G. Appenzeller, L. Martin, M. Schertler |
| RFC5409 Using the Boneh-Franklin and Boneh-Boyen Identity-Based Encryption Algorithms with the Cryptographic Message Syntax (CMS) This document describes the conventions for using the Boneh-Franklin (BF) and Boneh-Boyen (BB1) identity-based encryption algorithms in the Cryptographic Message Syntax (CMS) to encrypt content-encryption keys. Object identifiers and the convention for encoding a recipient's identity are also defined. This memo provides information for the Internet community. | January 2009 Status: INFORMATIONAL Autor: L. Martin, M. Schertler |
| RFC5410 Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST 1.0 | January 2009 Status: INFORMATIONAL Autor: A. Jerichow, L. Piron |
| RFC5411 A Hitchhiker's Guide to the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) is the subject of numerous specifications that have been produced by the IETF. It can be difficult to locate the right document, or even to determine the set of Request for Comments (RFC) about SIP. This specification serves as a guide to the SIP RFC series. It lists a current snapshot of the specifications under the SIP umbrella, briefly summarizes each, and groups them into categories. This memo provides information for the Internet community. | February 2009 Status: INFORMATIONAL Autor: J. Rosenberg |
| RFC5412 Lightweight Access Point Protocol In recent years, there has been a shift in wireless LAN (WLAN) product architectures from autonomous access points to centralized control of lightweight access points. The general goal has been to move most of the traditional wireless functionality such as access control (user authentication and authorization), mobility, and radio management out of the access point into a centralized controller. | February 2010 Status: HISTORIC Autor: P. Calhoun, R. Suri, N. Cam Winget, M. Williams, S. Hares, B. O'Hara, S. Kelly |
| RFC5413 SLAPP: Secure Light Access Point Protocol The Control and Provisioning of Wireless Access Points (CAPWAP) problem statement describes a problem that needs to be addressed before a wireless LAN (WLAN) network designer can construct a solution composed of Wireless Termination Points (WTP) and Access Controllers (AC) from multiple, different vendors. One of the primary goals is to find a solution that solves the interoperability between the two classes of devices (WTPs and ACs) that then enables an AC from one vendor to control and manage a WTP from another. | February 2010 Status: HISTORIC Autor: P. Narasimhan, D. Harkins, S. Ponnuswamy |
| RFC5414 Wireless LAN Control Protocol (WiCoP) The popularity of wireless local area networks (WLANs) has led to widespread deployments across different establishments. It has also translated into an increasing scale of the WLANs. Large-scale deployments made of large numbers of wireless termination points (WTPs) and covering substantial areas are increasingly common. | February 2010 Status: HISTORIC Autor: S. Iino, S. Govindan, M. Sugiura, H. Cheng |
| RFC5415 Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification This specification defines the Control And Provisioning of Wireless Access Points (CAPWAP) Protocol, meeting the objectives defined by the CAPWAP Working Group in RFC 4564. The CAPWAP protocol is designed to be flexible, allowing it to be used for a variety of wireless technologies. This document describes the base CAPWAP protocol, while separate binding extensions will enable its use with additional wireless technologies. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: P. Calhoun, M. Montemurro, D. Stanley |
| RFC5416 Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11 Wireless LAN product architectures have evolved from single autonomous access points to systems consisting of a centralized Access Controller (AC) and Wireless Termination Points (WTPs). The general goal of centralized control architectures is to move access control, including user authentication and authorization, mobility management, and radio management from the single access point to a centralized controller. | March 2009 Status: PROPOSED STANDARD Autor: P. Calhoun, M. Montemurro, D. Stanley |
| RFC5417 Control And Provisioning of Wireless Access Points (CAPWAP) Access Controller DHCP Option The Control And Provisioning of Wireless Access Points Protocol allows a Wireless Termination Point to use DHCP to discover the Access Controllers to which it is to connect. This document describes the DHCP options to be used by the CAPWAP Protocol. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: P. Calhoun |
| RFC5418 Control And Provisioning of Wireless Access Points (CAPWAP) Threat Analysis for IEEE 802.11 Deployments Early Wireless Local Area Network (WLAN) deployments feature a "fat" Access Point (AP), which serves as a \%stand-alone interface between the wired and wireless network segments. However, this model raises scaling, mobility, and manageability issues, and the Control and Provisioning of Wireless Access Points (CAPWAP) protocol is meant to address these issues. CAPWAP effectively splits the fat AP functionality into two network elements, and the communication channel between these components may traverse potentially hostile hops. This document analyzes the security exposure resulting from the introduction of CAPWAP and summarizes the associated security considerations for IEEE 802.11-based CAPWAP implementations and deployments. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: S. Kelly, T. Clancy |
| RFC5419 Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6) Mobile IPv6 defines a set of signaling messages that enable the mobile node (MN) to authenticate and perform registration with its home agent (HA). These authentication signaling messages between the mobile node and home agent are secured by an IPsec security association (SA) that is established between the MN and HA. The MIP6 working group has specified a mechanism to secure the Binding Update (BU) and Binding Acknowledgement (BAck) messages using an authentication option, similar to the authentication option in Mobile IPv4, carried within the signaling messages that are exchanged between the MN and HA to establish a binding. This document provides the justifications as to why the authentication option mechanism is needed for Mobile IPv6 deployment in certain environments. This memo provides information for the Internet community. | January 2009 Status: INFORMATIONAL Autor: B. Patil, G. Dommety |
| RFC5420 Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE) Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may be established using the Resource Reservation Protocol Traffic Engineering (RSVP-TE) extensions. This protocol includes an object (the SESSION_ATTRIBUTE object) that carries a Flags field used to indicate options and attributes of the LSP. That Flags field has eight bits, allowing for eight options to be set. Recent proposals in many documents that extend RSVP-TE have suggested uses for each of the previously unused bits. | February 2009 Status: PROPOSED STANDARD Autor: A. Farrel, D. Papadimitriou, JP. Vasseur, A. Ayyangarps |
| RFC5421 Basic Password Exchange within the Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) method enables secure communication between a peer and a server by using Transport Layer Security (TLS) to establish a mutually authenticated tunnel. Within this tunnel, a basic password exchange, based on the Generic Token Card method (EAP-GTC), may be executed to authenticate the peer. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: N. Cam-Winget, H. Zhou |
| RFC5422 Dynamic Provisioning Using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) method enables secure communication between a peer and a server by using Transport Layer Security (TLS) to establish a mutually authenticated tunnel. EAP- FAST also enables the provisioning credentials or other information through this protected tunnel. This document describes the use of EAP-FAST for dynamic provisioning. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: N. Cam-Winget, D. McGrew, J. Salowey, H. Zhou |
| RFC5423 Internet Message Store Events One of the missing features in the existing Internet mail and messaging standards is a facility for server-to-server and server-to- client event notifications related to message store events. As the scope of Internet mail expands to support more diverse media (such as voice mail) and devices (such as cell phones) and to provide rich interactions with other services (such as web portals and legal compliance systems), the need for an interoperable notification system increases. This document attempts to enumerate the types of events that interest real-world consumers of such a system. | March 2009 Status: PROPOSED STANDARD Autor: R. Gellens, C. Newman |
| RFC5424 The Syslog Protocol This document describes the syslog protocol, which is used to convey event notification messages. This protocol utilizes a layered architecture, which allows the use of any number of transport protocols for transmission of syslog messages. It also provides a message format that allows vendor-specific extensions to be provided in a structured way. | March 2009 Status: PROPOSED STANDARD Autor: R. Gerhards |
| RFC5425 Transport Layer Security (TLS) Transport Mapping for Syslog This document describes the use of Transport Layer Security (TLS) to provide a secure connection for the transport of syslog messages. This document describes the security threats to syslog and how TLS can be used to counter such threats. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: F. Miao, Y. Ma, J. Salowey |
| RFC5426 Transmission of Syslog Messages over UDP This document describes the transport for syslog messages over UDP/ IPv4 or UDP/IPv6. The syslog protocol layered architecture provides for support of any number of transport mappings. However, for interoperability purposes, syslog protocol implementers are required to support this transport mapping. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: A. Okmianski |
| RFC5427 Textual Conventions for Syslog Management This MIB module defines textual conventions to represent Facility and Severity information commonly used in syslog messages. The intent is that these textual conventions will be imported and used in MIB modules that would otherwise define their own representations. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: G. Keeni |
| RFC5428 Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: S. Channabasappa, W. De Ketelaere, E. Nechamkin |
| RFC5429 Sieve Email Filtering: Reject and Extended Reject Extensions This memo updates the definition of the Sieve mail filtering language "reject" extension, originally defined in RFC 3028. | March 2009 Status: PROPOSED STANDARD Autor: A. Stone |
| RFC5430 Suite B Profile for Transport Layer Security (TLS) The United States government has published guidelines for "NSA Suite B Cryptography", which defines cryptographic algorithm policy for national security applications. This document defines a profile of Transport Layer Security (TLS) version 1.2 that is fully conformant with Suite B. This document also defines a transitional profile for use with TLS version 1.0 and TLS version 1.1 which employs Suite B algorithms to the greatest extent possible. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: M. Salter, E. Rescorla, R. Housley |
| RFC5431 Diameter ITU-T Rw Policy Enforcement Interface Application This document describes the need for a new pair of IANA Diameter Command Codes to be used in a vendor-specific new application, namely for the ITU-T Rec. Q.3303.3 - Rw interface used to send a request/ response for authorizing network Quality of Service (QoS) resources and policy enforcement in a network element, as one of the recommendations of the International Telecommunication Union - Telecommunication Standardization Sector (ITU-T). This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: D. Sun |
| RFC5432 Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP) The offer/answer model for the Session Description Protocol (SDP) assumes that endpoints somehow establish the Quality of Service (QoS) required for the media streams they establish. Endpoints in closed environments typically agree out-of-band (e.g., using configuration information) regarding which QoS mechanism to use. However, on the Internet, there is more than one QoS service available. Consequently, there is a need for a mechanism to negotiate which QoS mechanism to use for a particular media stream. This document defines such a mechanism. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: J. Polk, S. Dhesikan, G. Camarillo |
| RFC5433 Extensible Authentication Protocol - Generalized Pre-Shared Key (EAP-GPSK) Method This memo defines an Extensible Authentication Protocol (EAP) method called EAP Generalized Pre-Shared Key (EAP-GPSK). This method is a lightweight shared-key authentication protocol supporting mutual authentication and key derivation. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: T. Clancy, H. Tschofenig |
| RFC5434 Considerations for Having a Successful Birds-of-a-Feather (BOF) Session This document discusses tactics and strategy for hosting a successful IETF Birds-of-a-Feather (BOF) session, especially one oriented at the formation of an IETF Working Group. It is based on the experiences of having participated in numerous BOFs, both successful and unsuccessful. [STANDARDS-TRACK] | February 2009 Status: INFORMATIONAL Autor: T. Narten |
| RFC5435 Sieve Email Filtering: Extension for Notifications Users go to great lengths to be notified as quickly as possible that they have received new mail. Most of these methods involve polling to check for new messages periodically. A push method handled by the final delivery agent gives users quicker notifications and saves server resources. This document does not specify the notification method, but it is expected that using existing instant messaging infrastructure such as Extensible Messaging and Presence Protocol (XMPP), or Global System for Mobile Communications (GSM) Short Message Service (SMS) messages will be popular. This document describes an extension to the Sieve mail filtering language that allows users to give specific rules for how and when notifications should be sent. [STANDARDS-TRACK] | January 2009 Status: PROPOSED STANDARD Autor: A. Melnikov, B. Leiba, W. Segmuller, T. Martin |
| RFC5436 Sieve Notification Mechanism: mailto This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent by electronic mail. [STANDARDS-TRACK] | January 2009 Status: PROPOSED STANDARD Autor: B. Leiba, M. Haardt |
| RFC5437 Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP) This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over the Extensible Messaging and Presence Protocol (XMPP), also known as Jabber. [STANDARDS-TRACK] | January 2009 Status: PROPOSED STANDARD Autor: P. Saint-Andre, A. Melnikov |
| RFC5438 Instant Message Disposition Notification (IMDN) Instant Messaging (IM) refers to the transfer of messages between users in real-time. This document provides a mechanism whereby endpoints can request Instant Message Disposition Notifications (IMDN), including delivery, processing, and display notifications, for page-mode instant messages. | February 2009 Status: PROPOSED STANDARD Autor: E. Burger, H. Khartabil |
| RFC5439 An Analysis of Scaling Issues in MPLS-TE Core Networks Traffic engineered Multiprotocol Label Switching (MPLS-TE) is deployed in providers' core networks. As providers plan to grow these networks, they need to understand whether existing protocols and implementations can support the network sizes that they are planning. | February 2009 Status: INFORMATIONAL Autor: S. Yasukawa, A. Farrel, O. Komolafe |
| RFC5440 Path Computation Element (PCE) Communication Protocol (PCEP) This document specifies the Path Computation Element (PCE) Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a PCE, or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed to be flexible and extensible so as to easily allow for the addition of further messages and objects, should further requirements be expressed in the future. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: JP. Vasseur, JL. Le Roux |
| RFC5441 A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched Paths The ability to compute shortest constrained Traffic Engineering Label Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks across multiple domains has been identified as a key requirement. In this context, a domain is a collection of network elements within a common sphere of address management or path computational responsibility such as an IGP area or an Autonomous Systems. This document specifies a procedure relying on the use of multiple Path Computation Elements (PCEs) to compute such inter-domain shortest constrained paths across a predetermined sequence of domains, using a backward-recursive path computation technique. This technique preserves confidentiality across domains, which is sometimes required when domains are managed by different service providers. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: JP. Vasseur, R. Zhang, N. Bitar, JL. Le Roux |
| RFC5442 LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet Mail This document specifies the architecture for mobile email, as described by the Open Mobile Alliance (OMA), using Internet Mail protocols. This architecture was an important consideration for much of the work of the LEMONADE (Enhancements to Internet email to Support Diverse Service Environments) working group in the IETF. This document also describes how the LEMONADE architecture meets OMA's requirements for their Mobile Email (MEM) service. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: E. Burger, G. Parsons |
| RFC5443 LDP IGP Synchronization In certain networks, there is dependency on the edge-to-edge Label Switched Paths (LSPs) setup by the Label Distribution Protocol (LDP), e.g., networks that are used for Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) applications. For such applications, it is not possible to rely on Internet Protocol (IP) forwarding if the MPLS LSP is not operating appropriately. Blackholing of labeled traffic can occur in situations where the Interior Gateway Protocol (IGP) is operational on a link on which LDP is not. While the link could still be used for IP forwarding, it is not useful for MPLS forwarding, for example, MPLS VPN applications or Border Gateway Protocol (BGP) route-free cores. This document describes a mechanism to avoid traffic loss due to this condition without introducing any protocol changes. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: M. Jork, A. Atlas, L. Fang |
| RFC5444 Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format This document specifies a packet format capable of carrying multiple messages that may be used by mobile ad hoc network routing protocols. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: T. Clausen, C. Dearlove, J. Dean, C. Adjih |
| RFC5445 Basic Forward Error Correction (FEC) Schemes This document provides Forward Error Correction (FEC) Scheme specifications according to the Reliable Multicast Transport (RMT) FEC building block for the Compact No-Code FEC Scheme, the Small Block, Large Block, and Expandable FEC Scheme, the Small Block Systematic FEC Scheme, and the Compact FEC Scheme. This document obsoletes RFC 3695 and assumes responsibility for the FEC Schemes defined in RFC 3452. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: M. Watson |
| RFC5446 Service Selection for Mobile IPv4 In some Mobile IPv4 deployments, identifying the mobile node or the mobility service subscriber is not enough to distinguish among the multiple services possibly provisioned to the mobile node. The capability to specify different services in addition to the mobile node's identity can be leveraged to provide flexibility for mobility service providers to provide multiple services within a single mobility service subscription. This document describes a Service Selection extension for Mobile IPv4 that is intended to assist home agents to make specific service selections for their mobility service subscriptions during the registration procedure. This memo provides information for the Internet community. | February 2009 Status: INFORMATIONAL Autor: J. Korhonen, U. Nilsson |
| RFC5447 Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction A Mobile IPv6 node requires a home agent address, a home address, and a security association with its home agent before it can start utilizing Mobile IPv6. RFC 3775 requires that some or all of these parameters be statically configured. Mobile IPv6 bootstrapping work aims to make this information dynamically available to the mobile node. An important aspect of the Mobile IPv6 bootstrapping solution is to support interworking with existing Authentication, Authorization, and Accounting (AAA) infrastructures. This document describes MIPv6 bootstrapping using the Diameter Network Access Server to home AAA server interface. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: J. Korhonen, J. Bournelle, H. Tschofenig, C. Perkins, K. Chowdhury |
| RFC5448 Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA') This specification defines a new EAP method, EAP-AKA', which is a small revision of the EAP-AKA (Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement) method. The change is a new key derivation function that binds the keys derived within the method to the name of the access network. The new key derivation mechanism has been defined in the 3rd Generation Partnership Project (3GPP). This specification allows its use in EAP in an interoperable manner. In addition, EAP-AKA' employs SHA-256 instead of SHA-1. | May 2009 Status: INFORMATIONAL Autor: J. Arkko, V. Lehtovirta, P. Eronen |
| RFC5449 OSPF Multipoint Relay (MPR) Extension for Ad Hoc Networks This document specifies an OSPFv3 interface type tailored for mobile ad hoc networks. This interface type is derived from the broadcast interface type, and is denoted the "OSPFv3 MANET interface type". This memo defines an Experimental Protocol for the Internet community. | February 2009 Status: EXPERIMENTAL Autor: E. Baccelli, P. Jacquet, D. Nguyen, T. Clausen |
| RFC5450 Transmission Time Offsets in RTP Streams This document describes a method to inform Real-time Transport Protocol (RTP) clients when RTP packets are transmitted at a time other than their 'nominal' transmission time. It also provides a mechanism to provide improved inter-arrival jitter reports from the clients, that take into account the reported transmission times. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: D. Singer, H. Desineni |
| RFC5451 Message Header Field for Indicating Message Authentication Status This memo defines a new header field for use with electronic mail messages to indicate the results of message authentication efforts. Any receiver-side software, such as mail filters or Mail User Agents (MUAs), may use this message header field to relay that information in a convenient way to users or to make sorting and filtering decisions. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: M. Kucherawy |
| RFC5452 Measures for Making DNS More Resilient against Forged Answers The current Internet climate poses serious threats to the Domain Name System. In the interim period before the DNS protocol can be secured more fully, measures can already be taken to harden the DNS to make 'spoofing' a recursing nameserver many orders of magnitude harder. | January 2009 Status: PROPOSED STANDARD Autor: A. Hubert, R. van Mook |
| RFC5453 Reserved IPv6 Interface Identifiers Interface identifiers in IPv6 unicast addresses are used to identify interfaces on a link. They are required to be unique within a subnet. Several RFCs have specified interface identifiers or identifier ranges that have a special meaning attached to them. An IPv6 node autoconfiguring an interface identifier in these ranges will encounter unexpected consequences. Since there is no centralized repository for such reserved identifiers, this document aims to create one. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: S. Krishnan |
| RFC5454 Dual-Stack Mobile IPv4 This specification provides IPv6 extensions to the Mobile IPv4 protocol. The extensions allow a dual-stack node to use IPv4 and IPv6 home addresses as well as to move between IPv4 and dual stack network infrastructures. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: G. Tsirtsis, V. Park, H. Soliman |
| RFC5455 Diffserv-Aware Class-Type Object for the Path Computation Element Communication Protocol This document specifies a CLASSTYPE object to support Diffserv-Aware Traffic Engineering (DS-TE) where path computation is performed with the aid of a Path Computation Element (PCE). [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: S. Sivabalan, J. Parker, S. Boutros, K. Kumaki |
| RFC5456 IAX: Inter-Asterisk eXchange Version 2 This document describes IAX, the Inter-Asterisk eXchange protocol, an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks. IAX was developed by the open source community for the Asterisk Private Branch Exchange (PBX) and is targeted primarily at Voice over Internet Protocol (VoIP) call control, but it can be used with streaming video or any other type of multimedia. | February 2010 Status: INFORMATIONAL Autor: M. Spencer, B. Capouch, E. Guy, F. Miller, K. Shumard |
| RFC5457 IANA Considerations for IAX: Inter-Asterisk eXchange Version 2 This document establishes the IANA registries for IAX, the Inter- Asterisk eXchange protocol, an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks. IAX was developed by the open source community for the Asterisk PBX and is targeted primarily at Voice over Internet Protocol (VoIP) call control, but it can be used with streaming video or any other type of multimedia. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: E. Guy |
| RFC5458 Security Requirements for the Unidirectional Lightweight Encapsulation (ULE) Protocol The MPEG-2 standard defined by ISO 13818-1 supports a range of transmission methods for a variety of services. This document provides a threat analysis and derives the security requirements when using the Transport Stream, TS, to support an Internet network-layer using Unidirectional Lightweight Encapsulation (ULE) defined in RFC 4326. The document also provides the motivation for link-layer security for a ULE Stream. A ULE Stream may be used to send IPv4 packets, IPv6 packets, and other Protocol Data Units (PDUs) to an arbitrarily large number of Receivers supporting unicast and/or multicast transmission. | March 2009 Status: INFORMATIONAL Autor: H. Cruickshank, P. Pillai, M. Noisternig, S. Iyengar |
| RFC5459 G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) Support This document updates the Real-time Transport Protocol (RTP) payload format to be used for the International Telecommunication Union (ITU-T) Recommendation G.729.1 audio codec. It adds Discontinuous Transmission (DTX) support to the RFC 4749 specification, in a backward-compatible way. An updated media type registration is included for this payload format. [STANDARDS-TRACK] | January 2009 Status: PROPOSED STANDARD Autor: A. Sollaud |
| RFC5460 DHCPv6 Bulk Leasequery The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been extended with a Leasequery capability that allows a client to request information about DHCPv6 bindings. That mechanism is limited to queries for individual bindings. In some situations individual binding queries may not be efficient, or even possible. This document expands on the Leasequery protocol, adding new query types and allowing for bulk transfer of DHCPv6 binding data via TCP. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: M. Stapp |
| RFC5461 TCP's Reaction to Soft Errors This document describes a non-standard, but widely implemented, modification to TCP's handling of ICMP soft error messages that rejects pending connection-requests when those error messages are received. This behavior reduces the likelihood of long delays between connection-establishment attempts that may arise in a number of scenarios, including one in which dual-stack nodes that have IPv6 enabled by default are deployed in IPv4 or mixed IPv4 and IPv6 environments. This memo provides information for the Internet community. | February 2009 Status: INFORMATIONAL Autor: F. Gont |
| RFC5462 Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field The early Multiprotocol Label Switching (MPLS) documents defined the form of the MPLS label stack entry. This includes a three-bit field called the "EXP field". The exact use of this field was not defined by these documents, except to state that it was to be "reserved for experimental use". | February 2009 Status: PROPOSED STANDARD Autor: L. Andersson, R. Asati |
| RFC5463 Sieve Email Filtering: Ihave Extension This document describes the "ihave" extension to the Sieve email filtering language. The "ihave" extension provides a means to write scripts that can take advantage of optional Sieve features but can still run when those optional features are not available. The extension also defines a new error control command intended to be used to report situations where no combination of available extensions satisfies the needs of the script. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: N. Freed |
| RFC5464 The IMAP METADATA Extension The METADATA extension to the Internet Message Access Protocol permits clients and servers to maintain "annotations" or "metadata" on IMAP servers. It is possible to have annotations on a per-mailbox basis or on the server as a whole. For example, this would allow comments about the purpose of a particular mailbox to be "attached" to that mailbox, or a "message of the day" containing server status information to be made available to anyone logging in to the server. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: C. Daboo |
| RFC5465 The IMAP NOTIFY Extension This document defines an IMAP extension that allows a client to request specific kinds of unsolicited notifications for specified mailboxes, such as messages being added to or deleted from such mailboxes. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: A. Gulbrandsen, C. King, A. Melnikov |
| RFC5466 IMAP4 Extension for Named Searches (Filters) The document defines a way to persistently store named IMAP (RFC 3501) searches on the server. Such named searches can be subsequently referenced in a SEARCH or any other command that accepts a search criterion as a parameter. [STANDARDS-TRACK] | February 2009 Status: PROPOSED STANDARD Autor: A. Melnikov, C. King |
| RFC5467 GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs) This document defines a method for the support of GMPLS asymmetric bandwidth bidirectional Label Switched Paths (LSPs). The presented approach is applicable to any switching technology and builds on the original Resource Reservation Protocol (RSVP) model for the transport of traffic-related parameters. The procedures described in this document are experimental. This memo defines an Experimental Protocol for the Internet community. | March 2009 Status: EXPERIMENTAL Autor: L. Berger, A. Takacs, D. Caviglia, D. Fedyk, J. Meuric |
| RFC5468 Performance Analysis of Inter-Domain Path Computation Methodologies This document presents a performance comparison between the per-domain path computation method and the Path Computation Element (PCE) Architecture-based Backward Recursive Path Computation (BRPC) procedure. Metrics to capture the significant performance aspects are identified, and detailed simulations are carried out on realistic scenarios. A performance analysis for each of the path computation methods is then undertaken. This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: S. Dasgupta, J. de Oliveira, JP. Vasseur |
| RFC5469 DES and IDEA Cipher Suites for Transport Layer Security (TLS) Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC 4346) include cipher suites based on DES (Data Encryption Standard) and IDEA (International Data Encryption Algorithm) algorithms. DES (when used in single-DES mode) and IDEA are no longer recommended for general use in TLS, and have been removed from TLS version 1.2 (RFC 5246). This document specifies these cipher suites for completeness and discusses reasons why their use is no longer recommended. This memo provides information for the Internet community. | February 2009 Status: INFORMATIONAL Autor: P. Eronen |
| RFC5470 Architecture for IP Flow Information Export This memo defines the IP Flow Information eXport (IPFIX) architecture for the selective monitoring of IP Flows, and for the export of measured IP Flow information from an IPFIX Device to a Collector. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: G. Sadasivan, N. Brownlee, B. Claise, J. Quittek |
| RFC5471 Guidelines for IP Flow Information Export (IPFIX) Testing This document presents a list of tests for implementers of IP Flow Information eXport (IPFIX) compliant Exporting Processes and Collecting Processes. This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations. These tests cover all important functions, in order to gain a level of confidence in the IPFIX implementation. Therefore, they allow the implementer to perform interoperability or plug tests with other IPFIX Exporting Processes and Collecting Processes. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: C. Schmoll, P. Aitken, B. Claise |
| RFC5472 IP Flow Information Export (IPFIX) Applicability In this document, we describe the applicability of the IP Flow Information eXport (IPFIX) protocol for a variety of applications. We show how applications can use IPFIX, describe the relevant Information Elements (IEs) for those applications, and present opportunities and limitations of the protocol. Furthermore, we describe relations of the IPFIX framework to other architectures and frameworks. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: T. Zseby, E. Boschi, N. Brownlee, B. Claise |
| RFC5473 Reducing Redundancy in IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) Reports This document describes a bandwidth saving method for exporting Flow or packet information using the IP Flow Information eXport (IPFIX) protocol. As the Packet Sampling (PSAMP) protocol is based on IPFIX, these considerations are valid for PSAMP exports as well. | March 2009 Status: INFORMATIONAL Autor: E. Boschi, L. Mark, B. Claise |
| RFC5474 A Framework for Packet Selection and Reporting This document specifies a framework for the PSAMP (Packet SAMPling) protocol. The functions of this protocol are to select packets from a stream according to a set of standardized Selectors, to form a stream of reports on the selected packets, and to export the reports to a Collector. This framework details the components of this architecture, then describes some generic requirements, motivated by the dual aims of ubiquitous deployment and utility of the reports for applications. Detailed requirements for selection, reporting, and exporting are described, along with configuration requirements of the PSAMP functions. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: N. Duffield, D. Chiou, B. Claise, A. Greenberg, M. Grossglauser, J. Rexford |
| RFC5475 Sampling and Filtering Techniques for IP Packet Selection This document describes Sampling and Filtering techniques for IP packet selection. It provides a categorization of schemes and defines what parameters are needed to describe the most common selection schemes. Furthermore, it shows how techniques can be combined to build more elaborate packet Selectors. The document provides the basis for the definition of information models for configuring selection techniques in Metering Processes and for reporting the technique in use to a Collector. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: T. Zseby, M. Molina, N. Duffield, S. Niccolini, F. Raspall |
| RFC5476 Packet Sampling (PSAMP) Protocol Specifications This document specifies the export of packet information from a Packet SAMPling (PSAMP) Exporting Process to a PSAMP Collecting Process. For export of packet information, the IP Flow Information eXport (IPFIX) protocol is used, as both the IPFIX and PSAMP architecture match very well, and the means provided by the IPFIX protocol are sufficient. The document specifies in detail how the IPFIX protocol is used for PSAMP export of packet information. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: B. Claise, A. Johnson, J. Quittek |
| RFC5477 Information Model for Packet Sampling Exports This memo defines an information model for the Packet SAMPling (PSAMP) protocol. It is used by the PSAMP protocol for encoding sampled packet data and information related to the Sampling process. As the PSAMP protocol is based on the IP Flow Information eXport (IPFIX) protocol, this information model is an extension to the IPFIX information model. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: T. Dietz, B. Claise, P. Aitken, F. Dressler, G. Carle |
| RFC5478 IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces This document creates additional Session Initiation Protocol (SIP) Resource-Priority namespaces to meet the requirements of the US Defense Information Systems Agency, and places these namespaces in the IANA registry. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: J. Polk |
| RFC5479 Requirements and Analysis of Media Security Management Protocols This document describes requirements for a protocol to negotiate a security context for SIP-signaled Secure RTP (SRTP) media. In addition to the natural security requirements, this negotiation protocol must interoperate well with SIP in certain ways. A number of proposals have been published and a summary of these proposals is in the appendix of this document. This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: D. Wing, S. Fries, H. Tschofenig, F. Audet |
| RFC5480 Elliptic Curve Cryptography Subject Public Key Information This document specifies the syntax and semantics for the Subject Public Key Information field in certificates that support Elliptic Curve Cryptography. This document updates Sections 2.3.5 and 5, and the ASN.1 module of "Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 3279. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: S. Turner, D. Brown, K. Yiu, R. Housley, T. Polk |
| RFC5481 Packet Delay Variation Applicability Statement Packet delay variation metrics appear in many different standards documents. The metric definition in RFC 3393 has considerable flexibility, and it allows multiple formulations of delay variation through the specification of different packet selection functions. | March 2009 Status: INFORMATIONAL Autor: A. Morton, B. Claise |
| RFC5482 TCP User Timeout Option The TCP user timeout controls how long transmitted data may remain unacknowledged before a connection is forcefully closed. It is a local, per-connection parameter. This document specifies a new TCP option -- the TCP User Timeout Option -- that allows one end of a TCP connection to advertise its current user timeout value. This information provides advice to the other end of the TCP connection to adapt its user timeout accordingly. Increasing the user timeouts on both ends of a TCP connection allows it to survive extended periods without end-to-end connectivity. Decreasing the user timeouts allows busy servers to explicitly notify their clients that they will maintain the connection state only for a short time without connectivity. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: L. Eggert, F. Gont |
| RFC5483 ENUM Implementation Issues and Experiences This document captures experiences in implementing systems based on the ENUM protocol and experiences of ENUM data that have been created by others. As such, it clarifies the ENUM and Dynamic Delegation Discovery System standards. Its aim is to help others by reporting both what is "out there" and potential pitfalls in interpreting the set of documents that specify the ENUM protocol. It does not revise the standards but is intended to provide technical input to future revisions of those documents. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: L. Conroy, K. Fujiwara |
| RFC5484 Associating Time-Codes with RTP Streams This document describes a mechanism for associating \%time-codes, as defined by the Society of Motion Picture and Television Engineers (SMPTE), with media streams in a way that is independent of the RTP payload format of the media stream itself. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: D. Singer |
| RFC5485 Digital Signatures on Internet-Draft Documents This document specifies the conventions for digital signatures on Internet-Drafts. The Cryptographic Message Syntax (CMS) is used to create a detached signature, which is stored in a separate companion file so that no existing utilities are impacted by the addition of the digital signature. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: R. Housley |
| RFC5486 Session Peering for Multimedia Interconnect (SPEERMINT) Terminology This document defines the terminology that is to be used in describing Session PEERing for Multimedia INTerconnect (SPEERMINT). This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: D. Malas, D. Meyer |
| RFC5487 Pre-Shared Key Cipher Suites for TLS with SHA-256/384 and AES Galois Counter Mode RFC 4279 and RFC 4785 describe pre-shared key cipher suites for Transport Layer Security (TLS). However, all those cipher suites use SHA-1 in their Message Authentication Code (MAC) algorithm. This document describes a set of pre-shared key cipher suites for TLS that uses stronger digest algorithms (i.e., SHA-256 or SHA-384) and another set that uses the Advanced Encryption Standard (AES) in Galois Counter Mode (GCM). [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: M. Badra |
| RFC5488 Network Mobility (NEMO) Management Information Base This memo defines a portion of the Management Information Base (MIB), the Network Mobility (NEMO) support MIB, for use with network management protocols in the Internet community. In particular, the NEMO MIB will be used to monitor and control a Mobile IPv6 node with NEMO functionality. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: S. Gundavelli, G. Keeni, K. Koide, K. Nagami |
| RFC5489 ECDHE_PSK Cipher Suites for Transport Layer Security (TLS) This document extends RFC 4279, RFC 4492, and RFC 4785 and specifies a set of cipher suites that use a pre-shared key (PSK) to authenticate an Elliptic Curve Diffie-Hellman exchange with Ephemeral keys (ECDHE). These cipher suites provide Perfect Forward Secrecy (PFS). This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: M. Badra, I. Hajjeh |
| RFC5490 The Sieve Mail-Filtering Language -- Extensions for Checking Mailbox Status and Accessing Mailbox Metadata This memo defines an extension to the Sieve mail filtering language (RFC 5228) for accessing mailbox and server annotations, checking for mailbox existence, and controlling mailbox creation on "fileinto" action. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC5491 GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations The Presence Information Data Format Location Object (PIDF-LO) specification provides a flexible and versatile means to represent location information. There are, however, circumstances that arise when information needs to be constrained in how it is represented. In these circumstances, the range of options that need to be implemented are reduced. There is growing interest in being able to use location information contained in a PIDF-LO for routing applications. To allow successful interoperability between applications, location information needs to be normative and more tightly constrained than is currently specified in RFC 4119 (PIDF-LO). This document makes recommendations on how to constrain, represent, and interpret locations in a PIDF-LO. It further recommends a subset of Geography Markup Language (GML) 3.1.1 that is mandatory to implement by applications involved in location-based routing. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: J. Winterbottom, M. Thomson, H. Tschofenig |
| RFC5492 Capabilities Advertisement with BGP-4 This document defines an Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated. | February 2009 Status: DRAFT STANDARD Autor: J. Scudder, R. Chandra |
| RFC5493 Requirements for the Conversion between Permanent Connections and Switched Connections in a Generalized Multiprotocol Label Switching (GMPLS) Network From a carrier perspective, the possibility of turning a permanent connection (PC) into a soft permanent connection (SPC) and vice versa, without actually affecting data plane traffic being carried over it, is a valuable option. In other terms, such operation can be seen as a way of transferring the ownership and control of an existing and in-use data plane connection between the management plane and the control plane, leaving its data plane state untouched. | April 2009 Status: INFORMATIONAL Autor: D. Caviglia, D. Bramanti, D. Li, D. McDysan |
| RFC5494 IANA Allocation Guidelines for the Address Resolution Protocol (ARP) This document specifies the IANA guidelines for allocating new values in the Address Resolution Protocol (ARP). This document also reserves some numbers for experimentation purposes. The changes also affect other protocols that employ values from the ARP name spaces. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: J. Arkko, C. Pignataro |
| RFC5495 Description of the Resource Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart Procedures The Hello message for the Resource Reservation Protocol (RSVP) has been defined to establish and maintain basic signaling node adjacencies for Label Switching Routers (LSRs) participating in a Multiprotocol Label Switching (MPLS) traffic-engineered (TE) network. The Hello message has been extended for use in Generalized MPLS (GMPLS) networks for state recovery of control channel or nodal faults. | March 2009 Status: INFORMATIONAL Autor: D. Li, J. Gao, A. Satyanarayana, S. Bardalai |
| RFC5496 The Reverse Path Forwarding (RPF) Vector TLV This document describes a use of the Protocol Independent Multicast (PIM) Join Attribute as defined in RFC 5384, which enables PIM to build multicast trees through an MPLS-enabled network, even if that network's IGP does not have a route to the source of the tree. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: IJ. Wijnands, A. Boers, E. Rosen |
| RFC5497 Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs) This document describes a general and flexible TLV (type-length-value structure) for representing time-values, such as an interval or a duration, using the generalized Mobile Ad hoc NETwork (MANET) packet/ message format. It defines two Message TLVs and two Address Block TLVs for representing validity and interval times for MANET routing protocols. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: T. Clausen, C. Dearlove |
| RFC5498 IANA Allocations for Mobile Ad Hoc Network (MANET) Protocols This document enumerates several common IANA allocations for use by Mobile Ad hoc NETwork (MANET) protocols. The following well-known numbers are required: a UDP port number, an IP protocol number, and a link-local multicast group address. [STANDARDS-TRACK] | March 2009 Status: PROPOSED STANDARD Autor: I. Chakeres |
| RFC5501 Requirements for Multicast Support in Virtual Private LAN Services This document provides functional requirements for network solutions that support multicast over Virtual Private LAN Service (VPLS). It specifies requirements both from the end user and service provider standpoints. It is intended that potential solutions will use these requirements as guidelines. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: Y. Kamite, Y. Wada, Y. Serbest, T. Morin, L. Fang |
| RFC5502 The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem This document specifies the SIP P-Served-User P-header. This header field addresses an issue that was found in the 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) between an S-CSCF (Serving Call Session Control Function) and an AS (Application Server) on the ISC (IMS Service Control) interface. This header field conveys the identity of the served user and the session case that applies to this particular communication session and application invocation. This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: J. van Elburg |
| RFC5503 Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture In order to deploy a residential telephone service at a 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, RFC 3261, 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. This memo provides information for the Internet community. | March 2009 Status: INFORMATIONAL Autor: F. Andreasen, B. McKibben, B. Marshall |
| RFC5504 Downgrading Mechanism for Email Address Internationalization Traditional mail systems handle only ASCII characters in SMTP envelope and mail header fields. The Email Address Internationalization (UTF8SMTP) extension allows UTF-8 characters in SMTP envelope and mail header fields. To avoid rejecting internationalized email messages when a server in the delivery path does not support the UTF8SMTP extension, some sort of converting mechanism is required. This document describes a downgrading mechanism for Email Address Internationalization. Note that this is a way to downgrade, not tunnel. There is no associated up-conversion mechanism, although internationalized email clients might use original internationalized addresses or other data when displaying or replying to downgraded messages. This memo defines an Experimental Protocol for the Internet community. | March 2009 Status: EXPERIMENTAL Autor: K. Fujiwara, Y. Yoneya |
| RFC5505 Principles of Internet Host Configuration This document describes principles of Internet host configuration. It covers issues relating to configuration of Internet-layer parameters, as well as parameters affecting higher-layer protocols. This memo provides information for the Internet community. | May 2009 Status: INFORMATIONAL Autor: B. Aboba, D. Thaler, L. Andersson, S. Cheshire |
| RFC5506 Support for Reduced-Size Real-Time Transport Control Protocol (RTCP): Opportunities and Consequences This memo discusses benefits and issues that arise when allowing Real-time Transport Protocol (RTCP) packets to be transmitted with reduced size. The size can be reduced if the rules on how to create compound packets outlined in RFC 3550 are removed or changed. Based on that analysis, this memo defines certain changes to the rules to allow feedback messages to be sent as Reduced-Size RTCP packets under certain conditions when using the RTP/AVPF (Real-time Transport Protocol / Audio-Visual Profile with Feedback) profile (RFC 4585). This document updates RFC 3550, RFC 3711, and RFC 4585. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: I. Johansson, M. Westerlund |
| RFC5507 Design Choices When Expanding the DNS This note discusses how to extend the DNS with new data for a new application. DNS extension discussions too often focus on reuse of the TXT Resource Record Type. This document lists different mechanisms to extend the DNS, and concludes that the use of a new DNS Resource Record Type is the best solution. This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: IAB, P. Faltstrom, R. Austein, P. Koch |
| RFC5508 NAT Behavioral Requirements for ICMP This document specifies the behavioral properties required of the Network Address Translator (NAT) devices in conjunction with the Internet Control Message Protocol (ICMP). The objective of this memo is to make NAT devices more predictable and compatible with diverse application protocols that traverse the devices. Companion documents provide behavioral recommendations specific to TCP, UDP, and other protocols. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | April 2009 Status: BEST CURRENT PRACTICE Autor: P. Srisuresh, B. Ford, S. Sivakumar, S. Guha |
| RFC5509 Internet Assigned Numbers Authority (IANA) Registration of Instant Messaging and Presence DNS SRV RRs for the Session Initiation Protocol (SIP) This document registers with IANA two new DNS SRV protocol labels for resolving Instant Messaging and Presence services with SIP. [STANDARDS TRACK] | April 2009 Status: PROPOSED STANDARD Autor: S. Loreto |
| RFC5510 Reed-Solomon Forward Error Correction (FEC) Schemes This document describes a Fully-Specified Forward Error Correction (FEC) Scheme for the Reed-Solomon FEC codes over GF(2^^m), where m is in {2..16}, and its application to the reliable delivery of data objects on the packet erasure channel (i.e., a communication path where packets are either received without any corruption or discarded during transmission). This document also describes a Fully-Specified FEC Scheme for the special case of Reed-Solomon codes over GF(2^^8) when there is no encoding symbol group. Finally, in the context of the Under-Specified Small Block Systematic FEC Scheme (FEC Encoding ID 129), this document assigns an FEC Instance ID to the special case of Reed-Solomon codes over GF(2^^8). | April 2009 Status: PROPOSED STANDARD Autor: J. Lacan, V. Roca, J. Peltotalo, S. Peltotalo |
| RFC5511 Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications Several protocols have been specified in the Routing Area of the IETF using a common variant of the Backus-Naur Form (BNF) of representing message syntax. However, there is no formal definition of this version of BNF. | April 2009 Status: PROPOSED STANDARD Autor: A. Farrel |
| RFC5512 The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute In certain situations, transporting a packet from one Border Gateway Protocol (BGP) speaker to another (the BGP next hop) requires that the packet be encapsulated by the first BGP speaker and decapsulated by the second. To support these situations, there needs to be some agreement between the two BGP speakers with regard to the "encapsulation information", i.e., the format of the encapsulation header as well as the contents of various fields of the header. | April 2009 Status: PROPOSED STANDARD Autor: P. Mohapatra, E. Rosen |
| RFC5513 IANA Considerations for Three Letter Acronyms Three Letter Acronyms (TLAs) are commonly used to identify components of networks or protocols as designed or specified within the IETF. A common concern is that one acronym may have multiple expansions. While this may not have been an issue in the past, network convergence means that protocols that did not previously operate together are now found in close proximity. This results in contention for acronyms, and confusion in interpretation. Such confusion has the potential to degrade the performance of the Internet as misunderstandings lead to misconfiguration or other operating errors. | April 2009 Status: INFORMATIONAL Autor: A. Farrel |
| RFC5514 IPv6 over Social Networks There is a lack of IPv6 utilization in early 2009; this is partly linked to the fact that the number of IPv6 nodes is rather low. This document proposes to vastly increase the number of IPv6 hosts by transforming all Social Networking platforms into IPv6 networks. This will immediately add millions of IPv6 hosts to the existing IPv6 Internet. This document includes sections on addressing and transport of IPv6 over a Social Network. A working prototype has been developed. This memo defines an Experimental Protocol for the Internet community. | April 2009 Status: EXPERIMENTAL Autor: E. Vyncke |
| RFC5515 Layer 2 Tunneling Protocol (L2TP) Access Line Information Attribute Value Pair (AVP) Extensions This document describes a set of Layer 2 Tunneling Protocol (L2TP) Attribute Value Pair (AVP) extensions designed to carry the subscriber Access Line identification and characterization information that arrives at the Broadband Remote Access Server (BRAS) with L2TP Access Concentrator (LAC) functionality. It also describes a mechanism to report connection speed changes, after the initial connection speeds are sent during session establishment. The primary purpose of this document is to provide a reference for DSL equipment vendors wishing to interoperate with other vendors' products. The L2TP AVPs defined in this document are applicable to both L2TPv2 and L2TPv3. This memo provides information for the Internet community. | May 2009 Status: INFORMATIONAL Autor: V. Mammoliti, C. Pignataro, P. Arberg, J. Gibbons, P. Howard |
| RFC5516 Diameter Command Code Registration for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS) This document registers a set of IANA Diameter Command Codes to be used in new vendor-specific Diameter applications defined for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS). These new Diameter applications are defined for Mobile Management Entity (MME)- and Serving GPRS (General Packet Radio Service) Support Node (SGSN)-related interfaces in the architecture for the Evolved 3GPP Packet Switched Domain, which is also known as the Evolved Packet System (EPS). This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: M. Jones, L. Morand |
| RFC5517 Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment This document describes a mechanism to achieve device isolation through the application of special Layer 2 forwarding constraints. Such a mechanism allows end devices to share the same IP subnet while being Layer 2 isolated, which in turn allows network designers to employ larger subnets and so reduce the address management overhead. | February 2010 Status: INFORMATIONAL Autor: S. HomChaudhuri, M. Foschiano |
| RFC5518 Vouch By Reference This document describes the Vouch By Reference (VBR) protocol. VBR is a protocol for adding third-party certification to email. It permits independent third parties to certify the owner of a domain name that is associated with received mail. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: P. Hoffman, J. Levine, A. Hathcock |
| RFC5519 Multicast Group Membership Discovery 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 objects used for managing the Internet Group Management Protocol (IGMP) and the Multicast Listener Discovery (MLD) protocol. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: J. Chesterfield, B. Haberman |
| RFC5520 Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Paths (LSPs) may be computed by Path Computation Elements (PCEs). Where the TE LSP crosses multiple domains, such as Autonomous Systems (ASes), the path may be computed by multiple PCEs that cooperate, with each responsible for computing a segment of the path. However, in some cases (e.g., when ASes are administered by separate Service Providers), it would break confidentiality rules for a PCE to supply a path segment to a PCE in another domain, thus disclosing AS-internal topology information. This issue may be circumvented by returning a loose hop and by invoking a new path computation from the domain boundary Label Switching Router (LSR) during TE LSP setup as the signaling message enters the second domain, but this technique has several issues including the problem of maintaining path diversity. | April 2009 Status: PROPOSED STANDARD Autor: R. Bradford, JP. Vasseur, A. Farrel |
| RFC5521 Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions The Path Computation Element (PCE) provides functions of path computation in support of traffic engineering (TE) in Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. | April 2009 Status: PROPOSED STANDARD Autor: E. Oki, T. Takeda, A. Farrel |
| RFC5522 Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks This document describes the requirements and desired properties of Network Mobility (NEMO) Route Optimization techniques for use in global-networked communications systems for aeronautics and space exploration. | October 2009 Status: INFORMATIONAL Autor: W. Eddy, W. Ivancic, T. Davis |
| RFC5523 OSPFv3-Based Layer 1 VPN Auto-Discovery This document defines an OSPFv3-based (Open Shortest Path First version 3) Layer 1 Virtual Private Network (L1VPN) auto-discovery mechanism. This document parallels the existing OSPF version 2 L1VPN auto-discovery mechanism. The notable functional difference is the support of IPv6. This memo defines an Experimental Protocol for the Internet community. | April 2009 Status: EXPERIMENTAL Autor: L. Berger |
| RFC5524 Extended URLFETCH for Binary and Converted Parts The URLFETCH command defined as part of URLAUTH provides a mechanism for third parties to gain access to data held within messages in a user's private store; however, this data is sent verbatim, which is not suitable for a number of applications. This memo specifies a method for obtaining data in forms suitable for non-mail applications. [STANDARDS-TRACK] | May 2009 Status: PROPOSED STANDARD Autor: D. Cridland |
| RFC5525 Reliable Server Pooling MIB Module Definition Reliable Server Pooling (RSerPool) is a framework to provide reliable server pooling. The RSerPool framework consists of two protocols: ASAP (Aggregate Server Access Protocol) and ENRP (Endpoint Handlespace Redundancy Protocol). This document defines an \%SMIv2- compliant (Structure of Management Information Version 2) Management Information Base (MIB) module providing access to managed objects in an RSerPool implementation. This memo defines an Experimental Protocol for the Internet community. | April 2009 Status: EXPERIMENTAL Autor: T. Dreibholz, J. Mulik |
| RFC5526 The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application for Infrastructure ENUM This document defines the use case for Infrastructure ENUM and proposes its implementation as a parallel namespace to "e164.arpa", as defined in RFC 3761, as the long-term solution to the problem of allowing carriers to provision DNS records for telephone numbers independently of those provisioned by end users (number assignees). This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: J. Livingood, P. Pfautz, R. Stastny |
| RFC5527 Combined User and Infrastructure ENUM in the e164.arpa Tree This memo defines an interim solution for Infrastructure ENUM in order to allow a combined User and Infrastructure ENUM implementation in e164.arpa as a national choice. This interim solution will be deprecated after implementation of the long-term solution. This memo provides information for the Internet community. | May 2009 Status: INFORMATIONAL Autor: M. Haberler, O. Lendl, R. Stastny |
| RFC5528 Camellia Counter Mode and Camellia Counter with CBC-MAC Mode Algorithms This document describes the algorithms and presents test vectors for the Camellia block cipher algorithm in Counter mode (CTR) and Counter with Cipher Block Chaining MAC mode (CCM). The purpose of this document is to make the Camellia-CTR and Camellia-CCM algorithm conveniently available to the Internet Community. This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: A. Kato, M. Kanda, S. Kanno |
| RFC5529 Modes of Operation for Camellia for Use with IPsec This document describes the use of the Camellia block cipher algorithm in Cipher Block Chaining (CBC) mode, Counter (CTR) mode, and Counter with CBC-MAC (CCM) mode as additional, optional-to- implement Internet Key Exchange Protocol version 2 (IKEv2) and Encapsulating Security Payload (ESP) mechanisms to provide confidentiality, data origin authentication, and connectionless integrity. [STANDARDS-TRACK] | April 2009 Status: PROPOSED STANDARD Autor: A. Kato, M. Kanda, S. Kanno |
| RFC5530 IMAP Response Codes IMAP responses consist of a response type (OK, NO, BAD), an optional machine-readable response code, and a human-readable text. | May 2009 Status: PROPOSED STANDARD Autor: A. Gulbrandsen |
| RFC5531 RPC: Remote Procedure Call Protocol Specification Version 2 This document describes the Open Network Computing (ONC) Remote Procedure Call (RPC) version 2 protocol as it is currently deployed and accepted. This document obsoletes RFC 1831. [STANDARDS-TRACK] | May 2009 Status: DRAFT STANDARD Autor: R. Thurlow |
| RFC5532 Network File System (NFS) Remote Direct Memory Access (RDMA) Problem Statement This document addresses enabling the use of Remote Direct Memory Access (RDMA) by the Network File System (NFS) protocols. NFS implementations historically incur significant overhead due to data copies on end-host systems, as well as other processing overhead. This document explores the potential benefits of RDMA to these implementations and evaluates the reasons why RDMA is especially well-suited to NFS and network file protocols in general. This memo provides information for the Internet community. | May 2009 Status: INFORMATIONAL Autor: T. Talpey, C. Juszczak |
| RFC5533 Shim6: Level 3 Multihoming Shim Protocol for IPv6 This document defines the Shim6 protocol, a layer 3 shim for providing locator agility below the transport protocols, so that multihoming can be provided for IPv6 with failover and load-sharing properties, without assuming that a multihomed site will have a provider-independent IPv6 address prefix announced in the global IPv6 routing table. The hosts in a site that has multiple provider- allocated IPv6 address prefixes will use the Shim6 protocol specified in this document to set up state with peer hosts so that the state can later be used to failover to a different locator pair, should the original one stop working. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: E. Nordmark, M. Bagnulo |
| RFC5534 Failure Detection and Locator Pair Exploration Protocol for IPv6 Multihoming This document specifies how the level 3 multihoming Shim6 protocol (Shim6) detects failures between two communicating nodes. It also specifies an exploration protocol for switching to another pair of interfaces and/or addresses between the same nodes if a failure occurs and an operational pair can be found. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: J. Arkko, I. van Beijnum |
| RFC5535 Hash-Based Addresses (HBA) This memo describes a mechanism to provide a secure binding between the multiple addresses with different prefixes available to a host within a multihomed site. This mechanism employs either Cryptographically Generated Addresses (CGAs) or a new variant of the same theme that uses the same format in the addresses. The main idea in the new variant is that information about the multiple prefixes is included within the addresses themselves. This is achieved by generating the interface identifiers of the addresses of a host as hashes of the available prefixes and a random number. Then, the multiple addresses are generated by prepending the different prefixes to the generated interface identifiers. The result is a set of addresses, called Hash-Based Addresses (HBAs), that are inherently bound to each other. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: M. Bagnulo |
| RFC5536 Netnews Article Format This document specifies the syntax of Netnews articles in the context of the Internet Message Format (RFC 5322) and Multipurpose Internet Mail Extensions (MIME) (RFC 2045). This document obsoletes RFC 1036, providing an updated specification to reflect current practice and incorporating incremental changes specified in other documents. [STANDARDS-TRACK] | November 2009 Status: PROPOSED STANDARD Autor: K. Murchison, C. Lindsey, D. Kohn |
| RFC5537 Netnews Architecture and Protocols This document defines the architecture of Netnews systems and specifies the correct manipulation and interpretation of Netnews articles by software that originates, distributes, stores, and displays them. It also specifies the requirements that must be met by any protocol used to transport and serve Netnews articles. [STANDARDS-TRACK] | November 2009 Status: PROPOSED STANDARD Autor: R. Allbery, C. Lindsey |
| RFC5538 The 'news' and 'nntp' URI Schemes This memo specifies the 'news' and 'nntp' Uniform Resource Identifier (URI) schemes that were originally defined in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about these schemes on the Standards Track. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: F. Ellermann |
| RFC5539 NETCONF over Transport Layer Security (TLS) The Network Configuration Protocol (NETCONF) provides mechanisms to install, manipulate, and delete the configuration of network devices. This document describes how to use the Transport Layer Security (TLS) protocol to secure NETCONF exchanges. [STANDARDS-TRACK] | May 2009 Status: PROPOSED STANDARD Autor: M. Badra |
| RFC5540 40 Years of RFCs This RFC marks the 40th anniversary of the RFC document series. This memo provides information for the Internet community. | April 2009 Status: INFORMATIONAL Autor: RFC Editor |
| RFC5541 Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) The computation of one or a set of Traffic Engineering Label Switched Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks is subject to a set of one or more specific optimization criteria, referred to as objective functions (e.g., minimum cost path, widest path, etc.). | June 2009 Status: PROPOSED STANDARD Autor: JL. Le Roux, JP. Vasseur, Y. Lee |
| RFC5542 Definitions of Textual Conventions for Pseudowire (PW) Management This memo defines a Management Information Base (MIB) module that contains textual conventions (TCs) to represent commonly used pseudowire (PW) management information. The intent is that these TCs will be imported and used in PW-related MIB modules that would otherwise define their own representations. [STANDARDS-TRACK] | May 2009 Status: PROPOSED STANDARD Autor: T. Nadeau, D. Zelig, O. Nicklass |
| RFC5543 BGP Traffic Engineering Attribute This document defines a new BGP attribute, the Traffic Engineering attribute, that enables BGP to carry Traffic Engineering information. | May 2009 Status: PROPOSED STANDARD Autor: H. Ould-Brahim, D. Fedyk, Y. Rekhter |
| RFC5544 Syntax for Binding Documents with Time-Stamps This document describes an envelope that can be used to bind a file (not necessarily protected by means of cryptographic techniques) with one or more time-stamp tokens obtained for that file, where "time-stamp token" has the meaning defined in RFC 3161 or its successors. Additional types of temporal evidence are also allowed. | February 2010 Status: INFORMATIONAL Autor: A. Santoni |
| RFC5545 Internet Calendaring and Scheduling Core Object Specification (iCalendar) This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. [STANDARDS-TRACK] | September 2009 Status: PROPOSED STANDARD Autor: B. Desruisseaux |
| RFC5546 iCalendar Transport-Independent Interoperability Protocol (iTIP) This document specifies a protocol that uses the iCalendar object specification to provide scheduling interoperability between different calendaring systems. This is done without reference to a specific transport protocol so as to allow multiple methods of communication between systems. Subsequent documents will define profiles of this protocol that use specific, interoperable methods of communication between systems. | December 2009 Status: PROPOSED STANDARD Autor: C. Daboo |
| RFC5547 A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer This document provides a mechanism to negotiate the transfer of one or more files between two endpoints by using the Session Description Protocol (SDP) offer/answer model specified in RFC 3264. SDP is extended to describe the attributes of the files to be transferred. The offerer can describe either the files it wants to send or the files it would like to receive. The answerer can either accept or reject the offer separately for each individual file. The transfer of one or more files is initiated after a successful negotiation. The Message Session Relay Protocol (MSRP) is defined as the default mechanism to actually carry the files between the endpoints. The conventions on how to use MSRP for file transfer are also provided in this document. [STANDARDS-TRACK] | May 2009 Status: PROPOSED STANDARD Autor: M. Garcia-Martin, M. Isomaki, G. Camarillo, S. Loreto, P. Kyzivat |
| RFC5548 Routing Requirements for Urban Low-Power and Lossy Networks The application-specific routing requirements for Urban Low-Power and Lossy Networks (U-LLNs) are presented in this document. In the near future, sensing and actuating nodes will be placed outdoors in urban environments so as to improve people's living conditions as well as to monitor compliance with increasingly strict environmental laws. These field nodes are expected to measure and report a wide gamut of data (for example, the data required by applications that perform smart-metering or that monitor meteorological, pollution, and allergy conditions). The majority of these nodes are expected to communicate wirelessly over a variety of links such as IEEE 802.15.4, low-power IEEE 802.11, or IEEE 802.15.1 (Bluetooth), which given the limited radio range and the large number of nodes requires the use of suitable routing protocols. The design of such protocols will be mainly impacted by the limited resources of the nodes (memory, processing power, battery, etc.) and the particularities of the outdoor urban application scenarios. As such, for a wireless solution for Routing Over Low-Power and Lossy (ROLL) networks to be useful, the protocol(s) ought to be energy-efficient, scalable, and autonomous. This documents aims to specify a set of IPv6 routing requirements reflecting these and further U-LLNs' tailored characteristics. This memo provides information for the Internet community. | May 2009 Status: INFORMATIONAL Autor: M. Dohler, T. Watteyne, T. Winter, D. Barthel |
| RFC5549 Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop Multiprotocol BGP (MP-BGP) specifies that the set of network-layer protocols to which the address carried in the Next Hop field may belong is determined by the Address Family Identifier (AFI) and the Subsequent Address Family Identifier (SAFI). The current AFI/SAFI definitions for the IPv4 address family only have provisions for advertising a Next Hop address that belongs to the IPv4 protocol when advertising IPv4 Network Layer Reachability Information (NLRI) or VPN-IPv4 NLRI. This document specifies the extensions necessary to allow advertising IPv4 NLRI or VPN-IPv4 NLRI with a Next Hop address that belongs to the IPv6 protocol. This comprises an extension of the AFI/SAFI definitions to allow the address of the Next Hop for IPv4 NLRI or VPN-IPv4 NLRI to also belong to the IPv6 protocol, the encoding of the Next Hop in order to determine which of the protocols the address actually belongs to, and a new BGP Capability allowing MP-BGP Peers to dynamically discover whether they can exchange IPv4 NLRI and VPN-IPv4 NLRI with an IPv6 Next Hop. [STANDARDS-TRACK] | May 2009 Status: PROPOSED STANDARD Autor: F. Le Faucheur, E. Rosen |
| RFC5550 The Internet Email to Support Diverse Service Environments (Lemonade) Profile This document describes a profile (a set of required extensions, restrictions, and usage modes), dubbed Lemonade, of the IMAP, mail submission, and Sieve protocols. This profile allows clients (especially those that are constrained in memory, bandwidth, processing power, or other areas) to efficiently use IMAP and Submission to access and submit mail. This includes the ability to forward received mail without needing to download and upload the mail, to optimize submission, and to efficiently resynchronize in case of loss of connectivity with the server. | August 2009 Status: PROPOSED STANDARD Autor: D. Cridland, A. Melnikov, S. Maes |
| RFC5551 Lemonade Notifications Architecture Notification and filtering mechanisms can make email more enjoyable on mobile and other constrained devices (such as those with limited screen sizes, memory, data transfer rates, etc.). Notifications make the client aware of significant events (such as the arrival of new mail) so it can react (such as by fetching interesting mail immediately). Filtering reduces the visible mail to a set of messages that meet some criteria for "interesting". This functionality is included in the goals of the Lemonade (Enhancements to Internet email to Support Diverse Service Environments) Working Group. | August 2009 Status: INFORMATIONAL Autor: R. Gellens |
| RFC5552 SIP Interface to VoiceXML Media Services This document describes a SIP interface to VoiceXML media services. Commonly, Application Servers controlling Media Servers use this protocol for pure VoiceXML processing capabilities. This protocol is an adjunct to the full MEDIACTRL protocol and packages mechanism. [STANDARDS-TRACK] | May 2009 Status: PROPOSED STANDARD Autor: D. Burke, M. Scott |
| RFC5553 Resource Reservation Protocol (RSVP) Extensions for Path Key Support The paths taken by Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Paths (LSPs) may be computed by Path Computation Elements (PCEs). Where the TE LSP crosses multiple domains, such as Autonomous Systems (ASes), the path may be computed by multiple PCEs that cooperate, with each responsible for computing a segment of the path. | May 2009 Status: PROPOSED STANDARD Autor: A. Farrel, R. Bradford, JP. Vasseur |
| RFC5554 Clarifications and Extensions to the Generic Security Service Application Program Interface (GSS-API) for the Use of Channel Bindings This document clarifies and generalizes the Generic Security Service Application Programming Interface (GSS-API) "channel bindings" facility, and imposes requirements on future GSS-API mechanisms and programming language bindings of the GSS-API. [STANDARDS-TRACK] | May 2009 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC5555 Mobile IPv6 Support for Dual Stack Hosts and Routers The current Mobile IPv6 and Network Mobility (NEMO) specifications support IPv6 only. This specification extends those standards to allow the registration of IPv4 addresses and prefixes, respectively, and the transport of both IPv4 and IPv6 packets over the tunnel to the home agent. This specification also allows the mobile node to roam over both IPv6 and IPv4, including the case where Network Address Translation is present on the path between the mobile node and its home agent. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: H. Soliman |
| RFC5556 Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement Current IEEE 802.1 LANs use spanning tree protocols that have a number of challenges. These protocols need to strictly avoid loops, even temporary ones, during route propagation, because of the lack of header loop detection support. Routing tends not to take full advantage of alternate paths, or even non-overlapping pairwise paths (in the case of spanning trees). This document addresses these concerns and suggests applying modern network-layer routing protocols at the link layer. This document assumes that solutions would not address issues of scalability beyond that of existing IEEE 802.1 bridged links, but that a solution would be backward compatible with 802.1, including hubs, bridges, and their existing plug-and-play capabilities. This memo provides information for the Internet community. | May 2009 Status: INFORMATIONAL Autor: J. Touch, R. Perlman |
| RFC5557 Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization The Path Computation Element Communication Protocol (PCEP) allows Path Computation Clients (PCCs) to request path computations from Path Computation Elements (PCEs), and lets the PCEs return responses. When computing or reoptimizing the routes of a set of Traffic Engineering Label Switched Paths (TE LSPs) through a network, it may be advantageous to perform bulk path computations in order to avoid blocking problems and to achieve more optimal network-wide solutions. Such bulk optimization is termed Global Concurrent Optimization (GCO). A GCO is able to simultaneously consider the entire topology of the network and the complete set of existing TE LSPs, and their respective constraints, and look to optimize or reoptimize the entire network to satisfy all constraints for all TE LSPs. A GCO may also be applied to some subset of the TE LSPs in a network. The GCO application is primarily a Network Management System (NMS) solution. | July 2009 Status: PROPOSED STANDARD Autor: Y. Lee, JL. Le Roux, D. King, E. Oki |
| RFC5558 Virtual Enterprise Traversal (VET) Enterprise networks connect routers over various link types, and may also connect to provider networks and/or the global Internet. Enterprise network nodes require a means to automatically provision IP addresses/prefixes and support internetworking operation in a wide variety of use cases including Small Office, Home Office (SOHO) networks, Mobile Ad hoc Networks (MANETs), multi-organizational corporate networks and the interdomain core of the global Internet itself. This document specifies a Virtual Enterprise Traversal (VET) abstraction for autoconfiguration and operation of nodes in enterprise networks. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: F. Templin |
| RFC5559 Pre-Congestion Notification (PCN) Architecture This document describes a general architecture for flow admission and termination based on pre-congestion information in order to protect the quality of service of established, inelastic flows within a single Diffserv domain. This memo provides information for the Internet community. | June 2009 Status: INFORMATIONAL Autor: P. Eardley |
| RFC5560 A One-Way Packet Duplication Metric When a packet is sent from one host to the other, one normally expects that exactly one copy of the packet that was sent arrives at the destination. It is, however, possible that a packet is either lost or that multiple copies arrive. | May 2009 Status: PROPOSED STANDARD Autor: H. Uijterwaal |
| RFC5561 LDP Capabilities A number of enhancements to the Label Distribution Protocol (LDP) have been proposed. Some have been implemented, and some are advancing toward standardization. It is likely that additional enhancements will be proposed in the future. This document defines a mechanism for advertising LDP enhancements at session initialization time, as well as a mechanism to enable and disable enhancements after LDP session establishment. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: B. Thomas, K. Raza, S. Aggarwal, R. Aggarwal, JL. Le Roux |
| RFC5562 Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets The proposal in this document is Experimental. While it may be deployed in the current Internet, it does not represent a consensus that this is the best possible mechanism for the use of Explicit Congestion Notification (ECN) in TCP SYN/ACK packets. | June 2009 Status: EXPERIMENTAL Autor: A. Kuzmanovic, A. Mondal, S. Floyd, K. Ramakrishnan |
| RFC5563 WiMAX Forum / 3GPP2 Proxy Mobile IPv4 Mobile IPv4 is a standard mobility protocol that enables an IPv4 device to move among networks while maintaining its IP address. The mobile device has the Mobile IPv4 client function to signal its location to the routing anchor, known as the Home Agent. However, there are many IPv4 devices without such capability due to various reasons. This document describes Proxy Mobile IPv4 (PMIPv4), a scheme based on having the Mobile IPv4 client function in a network entity to provide mobility support for an unaltered and mobility-unaware IPv4 device. This document also describes a particular application of PMIPv4 as specified in the WiMAX Forum and another application that is to be adopted in 3GPP2. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: K. Leung, G. Dommety, P. Yegani, K. Chowdhury |
| RFC5564 Linguistic Guidelines for the Use of the Arabic Language in Internet Domains This document constitutes technical specifications for the use of Arabic in Internet domain names and provides linguistic guidelines for Arabic domain names. It addresses Arabic-specific linguistic issues pertaining to the use of Arabic language in domain names. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: A. El-Sherbiny, M. Farah, I. Oueichek, A. Al-Zoman |
| RFC5565 Softwire Mesh Framework The Internet needs to be able to handle both IPv4 and IPv6 packets. However, it is expected that some constituent networks of the Internet will be "single-protocol" networks. One kind of single-protocol network can parse only IPv4 packets and can process only IPv4 routing information; another kind can parse only IPv6 packets and can process only IPv6 routing information. It is nevertheless required that either kind of single-protocol network be able to provide transit service for the "other" protocol. This is done by passing the "other kind" of routing information from one edge of the single-protocol network to the other, and by tunneling the "other kind" of data packet from one edge to the other. The tunnels are known as "softwires". This framework document explains how the routing information and the data packets of one protocol are passed through a single-protocol network of the other protocol. The document is careful to specify when this can be done with existing technology and when it requires the development of new or modified technology. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: J. Wu, Y. Cui, C. Metz, E. Rosen |
| RFC5566 BGP IPsec Tunnel Encapsulation Attribute The BGP Encapsulation Subsequent Address Family Identifier (SAFI) provides a method for the dynamic exchange of encapsulation information and for the indication of encapsulation protocol types to be used for different next hops. Currently, support for Generic Routing Encapsulation (GRE), Layer 2 Tunneling Protocol (L2TPv3), and IP in IP tunnel types are defined. This document defines support for IPsec tunnel types. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: L. Berger, R. White, E. Rosen |
| RFC5567 An Architectural Framework for Media Server Control This document describes an architectural framework for Media Server control. The primary focus will be to define logical entities that exist within the context of Media Server control, and define the appropriate naming conventions and interactions between them. This memo provides information for the Internet community. | June 2009 Status: INFORMATIONAL Autor: T. Melanchuk |
| RFC5568 Mobile IPv6 Fast Handovers Mobile IPv6 enables a mobile node (MN) to maintain its connectivity to the Internet when moving from one Access Router to another, a process referred to as handover. During handover, there is a period during which the mobile node is unable to send or receive packets because of link-switching delay and IP protocol operations. This "handover latency" resulting from standard Mobile IPv6 procedures (namely, movement detection, new Care-of Address configuration, and Binding Update) is often unacceptable to real-time traffic such as Voice over IP (VoIP). Reducing the handover latency could be beneficial to non-real-time, throughput-sensitive applications as well. This document specifies a protocol to improve handover latency due to Mobile IPv6 procedures. This document does not address improving the link-switching latency. | July 2009 Status: PROPOSED STANDARD Autor: R. Koodli |
| RFC5569 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) IPv6 rapid deployment on IPv4 infrastructures (6rd) builds upon mechanisms of 6to4 to enable a service provider to rapidly deploy IPv6 unicast service to IPv4 sites to which it provides customer premise equipment. Like 6to4, it utilizes stateless IPv6 in IPv4 encapsulation in order to transit IPv4-only network infrastructure. Unlike 6to4, a 6rd service provider uses an IPv6 prefix of its own in place of the fixed 6to4 prefix. A service provider has used this mechanism for its own IPv6 "rapid deployment": five weeks from first exposure to 6rd principles to more than 1,500,000 residential sites being provided native IPv6, under the only condition that they activate it. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2010 Status: INFORMATIONAL Autor: R. Despres |
| RFC5570 Common Architecture Label IPv6 Security Option (CALIPSO) This document describes an optional method for encoding explicit packet Sensitivity Labels on IPv6 packets. It is intended for use only within Multi-Level Secure (MLS) networking environments that are both trusted and trustworthy. This memo provides information for the Internet community. | July 2009 Status: INFORMATIONAL Autor: M. StJohns, R. Atkinson, G. Thomas |
| RFC5571 Softwire Hub and Spoke Deployment Framework with Layer Two Tunneling Protocol Version 2 (L2TPv2) This document describes the framework of the Softwire "Hub and Spoke" solution with the Layer Two Tunneling Protocol version 2 (L2TPv2). The implementation details specified in this document should be followed to achieve interoperability among different vendor implementations. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: B. Storer, C. Pignataro, M. Dos Santos, B. Stevant, L. Toutain, J. Tremblay |
| RFC5572 IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP) A tunnel broker with the Tunnel Setup Protocol (TSP) enables the establishment of tunnels of various inner protocols, such as IPv6 or IPv4, inside various outer protocols packets, such as IPv4, IPv6, or UDP over IPv4 for IPv4 NAT traversal. The control protocol (TSP) is used by the tunnel client to negotiate the tunnel with the broker. A mobile node implementing TSP can be connected to both IPv4 and IPv6 networks whether it is on IPv4 only, IPv4 behind a NAT, or on IPv6 only. A tunnel broker may terminate the tunnels on remote tunnel servers or on itself. This document describes the TSP within the model of the tunnel broker model. This document defines an Experimental Protocol for the Internet community. | February 2010 Status: EXPERIMENTAL Autor: M. Blanchet, F. Parent |
| RFC5573 Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP) The Blocks Extensible Exchange Protocol (BEEP) provides a protocol framework for the development of application protocols. This document describes a BEEP feature that enables asynchrony for individual channels. This memo defines an Experimental Protocol for the Internet community. | June 2009 Status: EXPERIMENTAL Autor: M. Thomson |
| RFC5574 RTP Payload Format for the Speex Codec Speex is an open-source voice codec suitable for use in VoIP (Voice over IP) type applications. This document describes the payload format for Speex-generated bit streams within an RTP packet. Also included here are the necessary details for the use of Speex with the Session Description Protocol (SDP). [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: G. Herlein, J. Valin, A. Heggestad, A. Moizard |
| RFC5575 Dissemination of Flow Specification Rules This document defines a new Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute traffic flow specifications. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix. | August 2009 Status: PROPOSED STANDARD Autor: P. Marques, N. Sheth, R. Raszuk, B. Greene, J. Mauch, D. McPherson |
| RFC5576 Source-Specific Media Attributes in the Session Description Protocol (SDP) The Session Description Protocol (SDP) provides mechanisms to describe attributes of multimedia sessions and of individual media streams (e.g., Real-time Transport Protocol (RTP) sessions) within a multimedia session, but does not provide any mechanism to describe individual media sources within a media stream. This document defines a mechanism to describe RTP media sources, which are identified by their synchronization source (SSRC) identifiers, in SDP, to associate attributes with these sources, and to express relationships among sources. It also defines several source-level attributes that can be used to describe properties of media sources. [STANDARDS-TRACK] | June 2009 Status: PROPOSED STANDARD Autor: J. Lennox, J. Ott, T. Schierl |
| RFC5577 RTP Payload Format for ITU-T Recommendation G.722.1 International Telecommunication Union (ITU-T) Recommendation G.722.1 is a wide-band audio codec. This document describes the payload format for including G.722.1-generated bit streams within an RTP packet. The document also describes the syntax and semantics of the Session Description Protocol (SDP) parameters needed to support G.722.1 audio codec. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: P. Luthi, R. Even |
| RFC5578 PPP over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics This document extends the Point-to-Point Protocol over Ethernet (PPPoE) with an optional credit-based flow control mechanism and an optional Link Quality Metric report. These optional extensions improve the performance of PPPoE over media with variable bandwidth and limited buffering, such as mobile point-to-point radio links. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: B. Berry, S. Ratliff, E. Paradise, T. Kaiser, M. Adams |
| RFC5579 Transmission of IPv4 Packets over Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) Interfaces The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) specifies a Non-Broadcast, Multiple Access (NBMA) interface type for the transmission of IPv6 packets over IPv4 networks using automatic IPv6-in-IPv4 encapsulation. The original specifications make no provisions for the encapsulation and transmission of IPv4 packets, however. This document specifies a method for transmitting IPv4 packets over ISATAP interfaces. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: F. Templin |
| RFC5580 Carrying Location Objects in RADIUS and Diameter This document describes procedures for conveying access-network ownership and location information based on civic and geospatial location formats in Remote Authentication Dial-In User Service (RADIUS) and Diameter. | August 2009 Status: PROPOSED STANDARD Autor: H. Tschofenig, F. Adrangi, M. Jones, A. Lior, B. Aboba |
| RFC5581 The Camellia Cipher in OpenPGP This document presents the necessary information to use the Camellia symmetric block cipher in the OpenPGP protocol. This memo provides information for the Internet community. | June 2009 Status: INFORMATIONAL Autor: D. Shaw |
| RFC5582 Location-to-URL Mapping Architecture and Framework This document describes an architecture for a global, scalable, resilient, and administratively distributed system for mapping geographic location information to URLs, using the Location-to-Service Translation (LoST) protocol. The architecture generalizes well-known approaches found in hierarchical lookup systems such as DNS. This memo provides information for the Internet community. | September 2009 Status: INFORMATIONAL Autor: H. Schulzrinne |
| RFC5583 Signaling Media Decoding Dependency in the Session Description Protocol (SDP) This memo defines semantics that allow for signaling the decoding dependency of different media descriptions with the same media type in the Session Description Protocol (SDP). This is required, for example, if media data is separated and transported in different network streams as a result of the use of a layered or multiple descriptive media coding process. | July 2009 Status: PROPOSED STANDARD Autor: T. Schierl, S. Wenger |
| RFC5584 RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) Family This document describes an RTP payload format for efficient and flexible transporting of audio data encoded with the Adaptive TRansform Audio Coding (ATRAC) family of codecs. Recent enhancements to the ATRAC family of codecs support high-quality audio coding with multiple channels. The RTP payload format as presented in this document also includes support for data fragmentation, elementary redundancy measures, and a variation on scalable streaming. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: M. Hatanaka, J. Matsumoto |
| RFC5585 DomainKeys Identified Mail (DKIM) Service Overview This document provides an overview of the DomainKeys Identified Mail (DKIM) service and describes how it can fit into a messaging service. It also describes how DKIM relates to other IETF message signature technologies. It is intended for those who are adopting, developing, or deploying DKIM. DKIM allows an organization to take responsibility for transmitting a message, in a way that can be verified by a recipient. The organization can be the author's, the originating sending site, an intermediary, or one of their agents. A message can contain multiple signatures from the same or different organizations involved with the message. DKIM defines a domain-level digital signature authentication framework for email, using public-key cryptography, with the domain name service as its key server technology (RFC 4871). This permits verification of a responsible organization, as well as the integrity of the message contents. DKIM also enables a mechanism that permits potential email signers to publish information about their email signing practices; this will permit email receivers to make additional assessments about messages. DKIM's authentication of email identity can assist in the global control of "spam" and "phishing". This memo provides information for the Internet community. | July 2009 Status: INFORMATIONAL Autor: T. Hansen, D. Crocker, P. Hallam-Baker |
| RFC5586 MPLS Generic Associated Channel This document generalizes the applicability of the pseudowire (PW) Associated Channel Header (ACH), enabling the realization of a control channel associated to MPLS Label Switched Paths (LSPs) and MPLS Sections in addition to MPLS pseudowires. In order to identify the presence of this Associated Channel Header in the label stack, this document also assigns one of the reserved MPLS label values to the Generic Associated Channel Label (GAL), to be used as a label based exception mechanism. | June 2009 Status: PROPOSED STANDARD Autor: M. Bocci, M. Vigoureux, S. Bryant |
| RFC5587 Extended Generic Security Service Mechanism Inquiry APIs This document introduces new application programming interfaces (APIs) to the Generic Security Services API (GSS-API) for extended mechanism attribute inquiry. These interfaces are primarily intended to reduce instances of hardcoding of mechanism identifiers in GSS applications. | July 2009 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC5588 Generic Security Service Application Program Interface (GSS-API) Extension for Storing Delegated Credentials This document defines a new function for the Generic Security Service Application Program Interface (GSS-API), which allows applications to store delegated (and other) credentials in the implicit GSS-API credential store. This is needed for GSS-API applications to use delegated credentials as they would use other credentials. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC5589 Session Initiation Protocol (SIP) Call Control - Transfer This document describes providing Call Transfer capabilities in the Session Initiation Protocol (SIP). SIP extensions such as REFER and Replaces are used to provide a number of transfer services including blind transfer, consultative transfer, and attended transfer. This work is part of the SIP multiparty call control framework. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | June 2009 Status: BEST CURRENT PRACTICE Autor: R. Sparks, A. Johnston, D. Petrie |
| RFC5590 Transport Subsystem for the Simple Network Management Protocol (SNMP) This document defines a Transport Subsystem, extending the Simple Network Management Protocol (SNMP) architecture defined in RFC 3411. This document defines a subsystem to contain Transport Models that is comparable to other subsystems in the RFC 3411 architecture. As work is being done to expand the transports to include secure transports, such as the Secure Shell (SSH) Protocol and Transport Layer Security (TLS), using a subsystem will enable consistent design and modularity of such Transport Models. This document identifies and describes some key aspects that need to be considered for any Transport Model for SNMP. [STANDARDS-TRACK] | June 2009 Status: DRAFT STANDARD Autor: D. Harrington, J. Schoenwaelder |
| RFC5591 Transport Security Model for the Simple Network Management Protocol (SNMP) This memo describes a Transport Security Model for the Simple Network Management Protocol (SNMP). | June 2009 Status: DRAFT STANDARD Autor: D. Harrington, W. Hardaker |
| RFC5592 Secure Shell Transport Model for the Simple Network Management Protocol (SNMP) This memo describes a Transport Model for the Simple Network Management Protocol (SNMP), using the Secure Shell (SSH) protocol. | June 2009 Status: PROPOSED STANDARD Autor: D. Harrington, J. Salowey, W. Hardaker |
| RFC5593 Internet Message Access Protocol (IMAP) - URL Access Identifier Extension The existing IMAP URL specification (RFC 5092) lists several <access> identifiers and <access> identifier prefixes that can be used to restrict access to URLAUTH-generated URLs. However, these identifiers do not provide facilities for new services such as streaming. This document proposes a set of new <access> identifiers as well as an IANA mechanism to register new <access> identifiers for future applications. | June 2009 Status: PROPOSED STANDARD Autor: N. Cook |
| RFC5594 Report from the IETF Workshop on Peer-to-Peer (P2P) Infrastructure, May 28, 2008 This document reports the outcome of a workshop organized by the Real-time Applications and Infrastructure Area Directors of the IETF to discuss network delay and congestion issues resulting from increased Peer-to-Peer (P2P) traffic volumes. The workshop was held on May 28, 2008 at MIT in Cambridge, MA, USA. The goals of the workshop were twofold: to understand the technical problems that ISPs and end users are experiencing as a result of high volumes of P2P traffic, and to begin to understand how the IETF may be helpful in addressing these problems. Gaining an understanding of where in the IETF this work might be pursued and how to extract feasible work items were highlighted as important tasks in pursuit of the latter goal. The workshop was very well attended and produced several work items that have since been taken up by members of the IETF community. This memo provides information for the Internet community. | July 2009 Status: INFORMATIONAL Autor: J. Peterson, A. Cooper |
| RFC5595 The Datagram Congestion Control Protocol (DCCP) Service Codes This document describes the usage of Service Codes by the Datagram Congestion Control Protocol, RFC 4340. It motivates the setting of a Service Code by applications. Service Codes provide a method to identify the intended service/application to process a DCCP connection request. This provides improved flexibility in the use and assignment of port numbers for connection multiplexing. The use of a DCCP Service Code can also enable more explicit coordination of services with middleboxes (e.g., network address translators and firewalls). This document updates the specification provided in RFC 4340. [STANDARDS-TRACK] | September 2009 Status: PROPOSED STANDARD Autor: G. Fairhurst |
| RFC5596 Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal This document specifies an update to the Datagram Congestion Control Protocol (DCCP), a connection-oriented and datagram-based transport protocol. The update adds support for the DCCP-Listen packet. This assists DCCP applications to communicate through middleboxes (e.g., a Network Address Port Translator or a DCCP server behind a firewall), where peering endpoints need to initiate communication in a near- simultaneous manner to establish necessary middlebox state. [STANDARDS-TRACK] | September 2009 Status: PROPOSED STANDARD Autor: G. Fairhurst |
| RFC5597 Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol This document defines a set of requirements for NATs handling the Datagram Congestion Control Protocol (DCCP). These requirements allow DCCP applications, such as streaming applications, to operate consistently, and they are very similar to the TCP requirements for NATs, which have already been published by the IETF. Ensuring that NATs meet this set of requirements will greatly increase the likelihood that applications using DCCP will function properly. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 2009 Status: BEST CURRENT PRACTICE Autor: R. Denis-Courmont |
| RFC5598 Internet Mail Architecture Over its thirty-five-year history, Internet Mail has changed significantly in scale and complexity, as it has become a global infrastructure service. These changes have been evolutionary, rather than revolutionary, reflecting a strong desire to preserve both its installed base and its usefulness. To collaborate productively on this large and complex system, all participants need to work from a common view of it and use a common language to describe its components and the interactions among them. But the many differences in perspective currently make it difficult to know exactly what another participant means. To serve as the necessary common frame of reference, this document describes the enhanced Internet Mail architecture, reflecting the current service. This memo provides information for the Internet community. | July 2009 Status: INFORMATIONAL Autor: D. Crocker |
| RFC5601 Pseudowire (PW) Management Information Base (MIB) This memo defines a Standards Track portion of the Management Information Base for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Pseudowire Edge-to-Edge services carried over a general Packet Switched Network. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: T. Nadeau, D. Zelig |
| RFC5602 Pseudowire (PW) over MPLS PSN Management Information Base (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 a MIB module for PW operation over Multiprotocol Label Switching (MPLS) Label Switching Routers (LSRs). [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: D. Zelig, T. Nadeau |
| RFC5603 Ethernet Pseudowire (PW) Management Information Base (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 modeling of Ethernet pseudowire (PW) services. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: D. Zelig, T. Nadeau |
| RFC5604 Managed Objects for Time Division Multiplexing (TDM) over Packet Switched Networks (PSNs) 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 pseudowire encapsulation for structured or unstructured Time-Division Multiplexing (TDM) (T1, E1, T3, E3) circuits over a Packet Switched Network (PSN). [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: O. Nicklass |
| RFC5605 Managed Objects for ATM over Packet Switched Networks (PSNs) 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 modeling ATM Pseudowire (PW) carrying ATM cells over Packet Switched Networks (PSNs). [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: O. Nicklass, T. Nadeau |
| RFC5606 Implications of 'retransmission-allowed' for SIP Location Conveyance This document explores an ambiguity in the interpretation of the <retransmission-allowed> element of the Presence Information Data Format for Location Objects (PIDF-LO) in cases where PIDF-LO is conveyed by the Session Initiation Protocol (SIP). It provides recommendations for how the SIP location conveyance mechanism should adapt to this ambiguity. | August 2009 Status: INFORMATIONAL Autor: J. Peterson, T. Hardie, J. Morris |
| RFC5607 Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management This document specifies Remote Authentication Dial-In User Service (RADIUS) attributes for authorizing management access to a Network Access Server (NAS). Both local and remote management are supported, with granular access rights and management privileges. Specific provisions are made for remote management via Framed Management protocols and for management access over a secure transport protocol. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: D. Nelson, G. Weber |
| RFC5608 Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models This memo describes the use of a Remote Authentication Dial-In User Service (RADIUS) authentication and authorization service with Simple Network Management Protocol (SNMP) secure Transport Models to authenticate users and authorize creation of secure transport sessions. While the recommendations of this memo are generally applicable to a broad class of SNMP Transport Models, the examples focus on the Secure Shell (SSH) Transport Model. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: K. Narayan, D. Nelson |
| RFC5609 State Machines for the Protocol for Carrying Authentication for Network Access (PANA) This document defines the conceptual state machines for the Protocol for Carrying Authentication for Network Access (PANA). The state machines consist of the PANA Client (PaC) state machine and the PANA Authentication Agent (PAA) state machine. The two state machines show how PANA can interface with the Extensible Authentication Protocol (EAP) state machines. The state machines and associated models are informative only. Implementations may achieve the same results using different methods. This memo provides information for the Internet community. | August 2009 Status: INFORMATIONAL Autor: V. Fajardo, Y. Ohba, R. Marin-Lopez |
| RFC5610 Exporting Type Information for IP Flow Information Export (IPFIX) Information Elements This document describes an extension to the IP Flow Information Export (IPFIX) protocol, which is used to represent and transmit data from IP flow measurement devices for collection, storage, and analysis, to allow the encoding of IPFIX Information Model properties within an IPFIX Message stream. This enables the export of extended type information for enterprise-specific Information Elements and the storage of such information within IPFIX Files, facilitating interoperability and reusability among a wide variety of applications and tools. [STANDARDS-TRACK] | July 2009 Status: PROPOSED STANDARD Autor: E. Boschi, B. Trammell, L. Mark, T. Zseby |
| RFC5611 Layer Two Tunneling Protocol version 3 - Setup of Time-Division Multiplexing (TDM) Pseudowires This document defines extensions to the Layer Two Tunneling Protocol version 3 (L2TPv3) for support of structure-agnostic and structure-aware (Circuit Emulation Service over Packet Switched Network (CESoPSN) style) Time-Division Multiplexing (TDM) pseudowires. Support of structure-aware (Time-Division Multiplexing over IP (TDMoIP) style) pseudowires over L2TPv3 is left for further study. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: A. Vainshtein, S. Galtzur |
| RFC5612 Enterprise Number for Documentation Use This document describes an Enterprise Number (also known as SMI Network Management Private Enterprise Code) for use in documentation. This memo provides information for the Internet community. | August 2009 Status: INFORMATIONAL Autor: P. Eronen, D. Harrington |
| RFC5613 OSPF Link-Local Signaling OSPF is a link-state intra-domain routing protocol. OSPF routers exchange information on a link using packets that follow a well-defined fixed format. The format is not flexible enough to enable new features that need to exchange arbitrary data. This document describes a backward-compatible technique to perform link-local signaling, i.e., exchange arbitrary data on a link. This document replaces the experimental specification published in RFC 4813 to bring it on the Standards Track. | August 2009 Status: PROPOSED STANDARD Autor: A. Zinin, A. Roy, L. Nguyen, B. Friedman, D. Yeung |
| RFC5614 Mobile Ad Hoc Network (MANET) Extension of OSPF Using Connected Dominating Set (CDS) Flooding This document specifies an extension of OSPFv3 to support mobile ad hoc networks (MANETs). The extension, called OSPF-MDR, is designed as a new OSPF interface type for MANETs. OSPF-MDR is based on the selection of a subset of MANET routers, consisting of MANET Designated Routers (MDRs) and Backup MDRs. The MDRs form a connected dominating set (CDS), and the MDRs and Backup MDRs together form a biconnected CDS for robustness. This CDS is exploited in two ways. First, to reduce flooding overhead, an optimized flooding procedure is used in which only (Backup) MDRs flood new link state advertisements (LSAs) back out the receiving interface; reliable flooding is ensured by retransmitting LSAs along adjacencies. Second, adjacencies are formed only between (Backup) MDRs and a subset of their neighbors, allowing for much better scaling in dense networks. The CDS is constructed using 2-hop neighbor information provided in a Hello protocol extension. The Hello protocol is further optimized by allowing differential Hellos that report only changes in neighbor states. Options are specified for originating router-LSAs that provide full or partial topology information, allowing overhead to be reduced by advertising less topology information. This memo defines an Experimental Protocol for the Internet community. | August 2009 Status: EXPERIMENTAL Autor: R. Ogier, P. Spagnolo |
| RFC5615 H.248/MEGACO Registration Procedures This document updates the H.248/MEGACO IANA Package registration procedures in order to better describe the Package registration process and to provide a more formal review and feedback process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2009 Status: BEST CURRENT PRACTICE Autor: C. Groves, Y. Lin |
| RFC5616 Streaming Internet Messaging Attachments This document describes a method for streaming multimedia attachments received by a resource- and/or network-constrained device from an IMAP server. It allows such clients, which often have limits in storage space and bandwidth, to play video and audio email content. | August 2009 Status: INFORMATIONAL Autor: N. Cook |
| RFC5617 DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP) DomainKeys Identified Mail (DKIM) defines a domain-level authentication framework for email to permit verification of the source and contents of messages. This document specifies an adjunct mechanism to aid in assessing messages that do not contain a DKIM signature for the domain used in the author's address. It defines a record that can advertise whether a domain signs its outgoing mail as well as how other hosts can access that record. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: E. Allman, J. Fenton, M. Delany, J. Levine |
| RFC5618 Mixed Security Mode for the Two-Way Active Measurement Protocol (TWAMP) This memo describes a simple extension to TWAMP (the Two-Way Active Measurement Protocol). The extension adds the option to use different security modes in the TWAMP-Control and TWAMP-Test protocols simultaneously. The memo also describes a new IANA registry for additional features, called the TWAMP Modes registry. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: A. Morton, K. Hedayat |
| RFC5619 Softwire Security Analysis and Requirements This document describes security guidelines for the softwire "Hubs and Spokes" and "Mesh" solutions. Together with discussion of the softwire deployment scenarios, the vulnerability to security attacks is analyzed to provide security protection mechanisms such as authentication, integrity, and confidentiality to the softwire control and data packets. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: S. Yamamoto, C. Williams, H. Yokota, F. Parent |
| RFC5620 RFC Editor Model (Version 1) The RFC Editor performs a number of functions that may be carried out by various persons or entities. The RFC Editor model presented in this document divides the responsibilities for the RFC Series into four functions: The RFC Series Editor, the Independent Submission Editor, the RFC Production Center, and the RFC Publisher. It also introduces the RFC Series Advisory Group and an (optional) Independent Submission Stream Editorial Board. The model outlined here is intended to increase flexibility and operational support options, provide for the orderly succession of the RFC Editor, and ensure the continuity of the RFC series, while maintaining RFC quality and timely processing, ensuring document accessibility, reducing costs, and increasing cost transparency. This memo provides information for the Internet community. | August 2009 Status: INFORMATIONAL Autor: O. Kolkman, IAB |
| RFC5621 Message Body Handling in the Session Initiation Protocol (SIP) This document specifies how message bodies are handled in SIP. Additionally, this document specifies SIP user agent support for MIME (Multipurpose Internet Mail Extensions) in message bodies. [STANDARDS-TRACK] | September 2009 Status: PROPOSED STANDARD Autor: G. Camarillo |
| RFC5622 Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP) This document specifies a profile for Congestion Control Identifier 4, the small-packet variant of TCP-Friendly Rate Control (TFRC), in the Datagram Congestion Control Protocol (DCCP). CCID 4 is for experimental use, and uses TFRC-SP (RFC 4828), a variant of TFRC designed for applications that send small packets. CCID 4 is considered experimental because TFRC-SP is itself experimental, and is not proposed for widespread deployment in the global Internet at this time. The goal for TFRC-SP is to achieve roughly the same bandwidth in bits per second (bps) as a TCP flow using packets of up to 1500 bytes but experiencing the same level of congestion. CCID 4 is for use for senders that send small packets and would like a TCP- friendly sending rate, possibly with Explicit Congestion Notification (ECN), while minimizing abrupt rate changes. This memo defines an Experimental Protocol for the Internet community. | August 2009 Status: EXPERIMENTAL Autor: S. Floyd, E. Kohler |
| RFC5623 Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering A network may comprise multiple layers. It is important to globally optimize network resource utilization, taking into account all layers rather than optimizing resource utilization at each layer independently. This allows better network efficiency to be achieved through a process that we call inter-layer traffic engineering. The Path Computation Element (PCE) can be a powerful tool to achieve inter-layer traffic engineering. | September 2009 Status: INFORMATIONAL Autor: E. Oki, T. Takeda, JL. Le Roux, A. Farrel |
| RFC5624 Quality of Service Parameters for Usage with Diameter This document defines a number of Quality of Service (QoS) parameters that can be reused for conveying QoS information within Diameter. | August 2009 Status: PROPOSED STANDARD Autor: J. Korhonen, H. Tschofenig, E. Davies |
| RFC5625 DNS Proxy Implementation Guidelines This document provides guidelines for the implementation of DNS proxies, as found in broadband gateways and other similar network devices. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2009 Status: BEST CURRENT PRACTICE Autor: R. Bellis |
| RFC5626 Managing Client-Initiated Connections in the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) allows proxy servers to initiate TCP connections or to send asynchronous UDP datagrams to User Agents in order to deliver requests. However, in a large number of real deployments, many practical considerations, such as the existence of firewalls and Network Address Translators (NATs) or the use of TLS with server-provided certificates, prevent servers from connecting to User Agents in this way. This specification defines behaviors for User Agents, registrars, and proxy servers that allow requests to be delivered on existing connections established by the User Agent. It also defines keep-alive behaviors needed to keep NAT bindings open and specifies the usage of multiple connections from the User Agent to its registrar. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: C. Jennings, R. Mahy, F. Audet |
| RFC5627 Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Several applications of the Session Initiation Protocol (SIP) require a user agent (UA) to construct and distribute a URI that can be used by anyone on the Internet to route a call to that specific UA instance. A URI that routes to a specific UA instance is called a Globally Routable UA URI (GRUU). This document describes an extension to SIP for obtaining a GRUU from a registrar and for communicating a GRUU to a peer within a dialog. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC5628 Registration Event Package Extension for Session Initiation Protocol (SIP) Globally Routable User Agent URIs (GRUUs) RFC 3680 defines a Session Initiation Protocol (SIP) event package for registration state. This package allows a watcher to learn about information stored by a SIP registrar, including its registered contact. | October 2009 Status: PROPOSED STANDARD Autor: P. Kyzivat |
| RFC5629 A Framework for Application Interaction in the Session Initiation Protocol (SIP) This document describes a framework for the interaction between users and Session Initiation Protocol (SIP) based applications. By interacting with applications, users can guide the way in which they operate. The focus of this framework is stimulus signaling, which allows a user agent (UA) to interact with an application without knowledge of the semantics of that application. Stimulus signaling can occur to a user interface running locally with the client, or to a remote user interface, through media streams. Stimulus signaling encompasses a wide range of mechanisms, ranging from clicking on hyperlinks, to pressing buttons, to traditional Dual-Tone Multi- Frequency (DTMF) input. In all cases, stimulus signaling is supported through the use of markup languages, which play a key role in this framework. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC5630 The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) This document provides clarifications and guidelines concerning the use of the SIPS URI scheme in the Session Initiation Protocol (SIP). It also makes normative changes to SIP. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: F. Audet |
| RFC5631 Session Initiation Protocol (SIP) Session Mobility Session mobility is the transfer of media of an ongoing communication session from one device to another. This document describes the basic approaches and shows the signaling and media flow examples for providing this service using the Session Initiation Protocol (SIP). Service discovery is essential to locate targets for session transfer and is discussed using the Service Location Protocol (SLP) as an example. This document is an informational document. This memo provides information for the Internet community. | October 2009 Status: INFORMATIONAL Autor: R. Shacham, H. Schulzrinne, S. Thakolsri, W. Kellerer |
| RFC5632 Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P (P4P) Technical Trial This document describes the experiences of Comcast, a large cable broadband Internet Service Provider (ISP) in the U.S., in a Proactive Network Provider Participation for P2P (P4P) technical trial in July 2008. This trial used P4P iTracker technology, which is being considered by the IETF as part of the Application Layer Transport Optimization (ALTO) working group. This memo provides information for the Internet community. | September 2009 Status: INFORMATIONAL Autor: C. Griffiths, J. Livingood, L. Popkin, R. Woundy, Y. Yang |
| RFC5633 Nominating Committee Process: Earlier Announcement of Open Positions and Solicitation of Volunteers This document updates RFC 3777, Section 4, Bullet 13 to allow announcement of open positions and solicitation of volunteers to be issued before a Nominating and Recall Committee Chair has been named by the Internet Society President. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | August 2009 Status: BEST CURRENT PRACTICE Autor: S. Dawkins |
| RFC5634 Quick-Start for the Datagram Congestion Control Protocol (DCCP) This document specifies the use of the Quick-Start mechanism by the Datagram Congestion Control Protocol (DCCP). DCCP is a transport protocol that allows the transmission of congestion-controlled, unreliable datagrams. DCCP is intended for applications such as streaming media, Internet telephony, and online games. In DCCP, an application has a choice of congestion control mechanisms, each specified by a Congestion Control Identifier (CCID). This document specifies general procedures applicable to all DCCP CCIDs and specific procedures for the use of Quick-Start with DCCP CCID 2, CCID 3, and CCID 4. Quick-Start enables a DCCP sender to cooperate with Quick-Start routers along the end-to-end path to determine an allowed sending rate at the start of a connection and, at times, in the middle of a DCCP connection (e.g., after an idle or application- limited period). The present specification is provided for use in controlled environments, and not as a mechanism that would be intended or appropriate for ubiquitous deployment in the global Internet. This memo defines an Experimental Protocol for the Internet community. | August 2009 Status: EXPERIMENTAL Autor: G. Fairhurst, A. Sathiaseelan |
| RFC5635 Remote Triggered Black Hole Filtering with Unicast Reverse Path Forwarding (uRPF) Remote Triggered Black Hole (RTBH) filtering is a popular and effective technique for the mitigation of denial-of-service attacks. This document expands upon destination-based RTBH filtering by outlining a method to enable filtering by source address as well. This memo provides information for the Internet community. | August 2009 Status: INFORMATIONAL Autor: W. Kumari, D. McPherson |
| RFC5636 Traceable Anonymous Certificate This document defines a practical architecture and protocols for offering privacy for a user who requests and uses an X.509 certificate containing a pseudonym, while still retaining the ability to map such a certificate to the real user who requested it. The architecture is compatible with IETF certificate request formats such as PKCS10 (RFC 2986) and CMC (RFC 5272). The architecture separates the authorities involved in issuing a certificate: one for verifying ownership of a private key (Blind Issuer) and the other for validating the contents of a certificate (Anonymity Issuer). The end entity (EE) certificates issued under this model are called Traceable Anonymous Certificates (TACs). This memo defines an Experimental Protocol for the Internet community. | August 2009 Status: EXPERIMENTAL Autor: S. Park, H. Park, Y. Won, J. Lee, S. Kent |
| RFC5637 Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6 In commercial and enterprise deployments, Mobile IPv6 can be a service offered by a Mobility Services Provider (MSP). In this case, all protocol operations may need to be explicitly authorized and traced, requiring the interaction between Mobile IPv6 and the AAA infrastructure. Integrating the Authentication, Authorization, and Accounting (AAA) infrastructure (e.g., Network Access Server and AAA server) also offers a solution component for Mobile IPv6 bootstrapping. This document describes various scenarios where a AAA interface for Mobile IPv6 is required. Additionally, it lists design goals and requirements for such an interface. This memo provides information for the Internet community. | September 2009 Status: INFORMATIONAL Autor: G. Giaretta, I. Guardini, E. Demaria, J. Bournelle, R. Lopez |
| RFC5638 Simple SIP Usage Scenario for Applications in the Endpoints For Internet-centric usage, the number of SIP-required standards for presence and IM and audio/video communications can be drastically smaller than what has been published by using only the rendezvous and session-initiation capabilities of SIP. The simplification is achieved by avoiding the emulation of telephony and its model of the intelligent network. 'Simple SIP' relies on powerful computing endpoints. Simple SIP desktop applications can be combined with rich Internet applications (RIAs). Significant telephony features may also be implemented in the endpoints. | September 2009 Status: INFORMATIONAL Autor: H. Sinnreich, A. Johnston, E. Shim, K. Singh |
| RFC5639 Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation This memo proposes several elliptic curve domain parameters over finite prime fields for use in cryptographic applications. The domain parameters are consistent with the relevant international standards, and can be used in X.509 certificates and certificate revocation lists (CRLs), for Internet Key Exchange (IKE), Transport Layer Security (TLS), XML signatures, and all applications or protocols based on the cryptographic message syntax (CMS). This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2010 Status: INFORMATIONAL Autor: M. Lochter, J. Merkle |
| RFC5640 Load-Balancing for Mesh Softwires Payloads transported over a Softwire mesh service (as defined by BGP Encapsulation Subsequent Address Family Identifier (SAFI) information exchange) often carry a number of identifiable, distinct flows. It can, in some circumstances, be desirable to distribute these flows over the equal cost multiple paths (ECMPs) that exist in the packet switched network. Currently, the payload of a packet entering the Softwire can only be interpreted by the ingress and egress routers. Thus, the load-balancing decision of a core router is only based on the encapsulating header, presenting much less entropy than available in the payload or the encapsulated header since the Softwire encapsulation acts in a tunneling fashion. This document describes a method for achieving comparable load-balancing efficiency in a network carrying Softwire mesh service over Layer Two Tunneling Protocol - Version 3 (L2TPv3) over IP or Generic Routing Encapsulation (GRE) encapsulation to what would be achieved without such encapsulation. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: C. Filsfils, P. Mohapatra, C. Pignataro |
| RFC5641 Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Circuit Status Values This document defines additional Layer 2 Tunneling Protocol Version 3 (L2TPv3) bit values to be used within the "Circuit Status" Attribute Value Pair (AVP) to communicate finer-grained error states for Attachment Circuits (ACs) and pseudowires (PWs). It also generalizes the Active bit and deprecates the use of the New bit in the Circuit Status AVP, updating RFC 3931, RFC 4349, RFC 4454, RFC 4591, and RFC 4719. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: N. McGill, C. Pignataro |
| RFC5642 Dynamic Hostname Exchange Mechanism for OSPF This document defines a new OSPF Router Information (RI) TLV that allows OSPF routers to flood their hostname-to-Router-ID mapping information across an OSPF network to provide a simple and dynamic mechanism for routers running OSPF to learn about symbolic hostnames, just like for routers running IS-IS. This mechanism is applicable to both OSPFv2 and OSPFv3. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: S. Venkata, S. Harwani, C. Pignataro, D. McPherson |
| RFC5643 Management Information Base for OSPFv3 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in IPv6-based internets. In particular, it defines objects for managing the Open Shortest Path First (OSPF) Routing Protocol for IPv6, otherwise known as OSPF version 3 (OSPFv3). [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: D. Joyal, V. Manral |
| RFC5644 IP Performance Metrics (IPPM): Spatial and Multicast The IETF has standardized IP Performance Metrics (IPPM) for measuring end-to-end performance between two points. This memo defines two new categories of metrics that extend the coverage to multiple measurement points. It defines spatial metrics for measuring the performance of segments of a source to destination path, and metrics for measuring the performance between a source and many destinations in multiparty communications (e.g., a multicast tree). [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: E. Stephan, L. Liang, A. Morton |
| RFC5645 Update to the Language Subtag Registry This memo defines the procedure used to update the IANA Language Subtag Registry, in conjunction with the publication of RFC 5646, for use in forming tags for identifying languages. This memo provides information for the Internet community. | September 2009 Status: INFORMATIONAL Autor: D. Ewell |
| RFC5646 Tags for Identifying Languages This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 2009 Status: BEST CURRENT PRACTICE Autor: A. Phillips, M. Davis |
| RFC5647 AES Galois Counter Mode for the Secure Shell Transport Layer Protocol Secure shell (SSH) is a secure remote-login protocol. SSH provides for algorithms that provide authentication, key agreement, confidentiality, and data-integrity services. The purpose of this document is to show how the AES Galois Counter Mode can be used to provide both confidentiality and data integrity to the SSH Transport Layer Protocol. This memo provides information for the Internet community. | August 2009 Status: INFORMATIONAL Autor: K. Igoe, J. Solinas |
| RFC5648 Multiple Care-of Addresses Registration According to the current Mobile IPv6 specification, a mobile node may have several care-of addresses but only one, called the primary care-of address, can be registered with its home agent and the correspondent nodes. However, for matters of cost, bandwidth, delay, etc, it is useful for the mobile node to get Internet access through multiple accesses simultaneously, in which case the mobile node would be configured with multiple active IPv6 care-of addresses. This document proposes extensions to the Mobile IPv6 protocol to register and use multiple care-of addresses. The extensions proposed in this document can be used by mobile routers using the NEMO (Network Mobility) Basic Support protocol as well. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: R. Wakikawa, V. Devarapalli, G. Tsirtsis, T. Ernst, K. Nagami |
| RFC5649 Advanced Encryption Standard (AES) Key Wrap with Padding Algorithm This document specifies a padding convention for use with the AES Key Wrap algorithm specified in RFC 3394. This convention eliminates the requirement that the length of the key to be wrapped be a multiple of 64 bits, allowing a key of any practical length to be wrapped. This memo provides information for the Internet community. | September 2009 Status: INFORMATIONAL Autor: R. Housley, M. Dworkin |
| RFC5650 Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2) 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 parameters of the "Very High Speed Digital Subscriber Line 2 (VDSL2)" interface type, which are also applicable for managing Asymmetric Digital Subscriber Line (ADSL), ADSL2, and ADSL2+ interfaces. [STANDARDS-TRACK] | September 2009 Status: PROPOSED STANDARD Autor: M. Morgenstern, S. Baillie, U. Bonollo |
| RFC5651 Layered Coding Transport (LCT) Building Block The Layered Coding Transport (LCT) Building Block provides transport level support for reliable content delivery and stream delivery protocols. LCT is specifically designed to support protocols using IP multicast, but it 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 document obsoletes RFC 3451. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: M. Luby, M. Watson, L. Vicisano |
| RFC5652 Cryptographic Message Syntax (CMS) This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. [STANDARDS-TRACK] | September 2009 Status: STANDARD Autor: R. Housley |
| RFC5653 Generic Security Service API Version 2: Java Bindings Update The Generic Security Services Application Program Interface (GSS-API) offers application programmers uniform access to security services atop a variety of underlying cryptographic mechanisms. This document updates the Java bindings for the GSS-API that are specified in "Generic Security Service API Version 2 : Java Bindings" (RFC 2853). This document obsoletes RFC 2853 by making specific and incremental clarifications and corrections to it in response to identification of transcription errors and implementation experience. | August 2009 Status: PROPOSED STANDARD Autor: M. Upadhyay, S. Malkani |
| RFC5654 Requirements of an MPLS Transport Profile This document specifies the requirements of an MPLS Transport Profile (MPLS-TP). This document is a product of a joint effort of the International Telecommunications Union (ITU) and IETF to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network as defined by International Telecommunications Union - Telecommunications Standardization Sector (ITU-T). | September 2009 Status: PROPOSED STANDARD Autor: B. Niven-Jenkins, D. Brungard, M. Betts, N. Sprecher, S. Ueno |
| RFC5655 Specification of the IP Flow Information Export (IPFIX) File Format This document describes a file format for the storage of flow data based upon the IP Flow Information Export (IPFIX) protocol. It proposes a set of requirements for flat-file, binary flow data file formats, then specifies the IPFIX File format to meet these requirements based upon IPFIX Messages. This IPFIX File format is designed to facilitate interoperability and reusability among a wide variety of flow storage, processing, and analysis tools. [STANDARDS TRACK] | October 2009 Status: PROPOSED STANDARD Autor: B. Trammell, E. Boschi, L. Mark, T. Zseby, A. Wagner |
| RFC5656 Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer This document describes algorithms based on Elliptic Curve Cryptography (ECC) for use within the Secure Shell (SSH) transport protocol. In particular, it specifies Elliptic Curve Diffie-Hellman (ECDH) key agreement, Elliptic Curve Menezes-Qu-Vanstone (ECMQV) key agreement, and Elliptic Curve Digital Signature Algorithm (ECDSA) for use in the SSH Transport Layer protocol. [STANDARDS-TRACK] | December 2009 Status: PROPOSED STANDARD Autor: D. Stebila, J. Green |
| RFC5657 Guidance on Interoperation and Implementation Reports for Advancement to Draft Standard Advancing a protocol to Draft Standard requires documentation of the interoperation and implementation of the protocol. Historic reports have varied widely in form and level of content and there is little guidance available to new report preparers. This document updates the existing processes and provides more detail on what is appropriate in an interoperability and implementation report. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | September 2009 Status: BEST CURRENT PRACTICE Autor: L. Dusseault, R. Sparks |
| RFC5658 Addressing Record-Route Issues in the Session Initiation Protocol (SIP) A typical function of a Session Initiation Protocol (SIP) Proxy is to insert a Record-Route header into initial, dialog-creating requests in order to make subsequent, in-dialog requests pass through it. This header contains a SIP Uniform Resource Identifier (URI) or SIPS (secure SIP) URI indicating where and how the subsequent requests should be sent to reach the proxy. These SIP or SIPS URIs can contain IPv4 or IPv6 addresses and URI parameters that could influence the routing such as the transport parameter (for example, transport=tcp), or a compression indication like "comp=sigcomp". When a proxy has to change some of those parameters between its incoming and outgoing interfaces (multi-homed proxies, transport protocol switching, or IPv4 to IPv6 scenarios, etc.), the question arises on what should be put in Record-Route header(s). It is not possible to make one header have the characteristics of both interfaces at the same time. This document aims to clarify these scenarios and fix bugs already identified on this topic; it formally recommends the use of the double Record-Route technique as an alternative to the current RFC 3261 text, which describes only a Record-Route rewriting solution. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: T. Froment, C. Lebel, B. Bonnaerens |
| RFC5659 An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge This document describes an architecture for extending pseudowire emulation across multiple packet switched network (PSN) segments. Scenarios are discussed where each segment of a given edge-to-edge emulated service spans a different provider's PSN, as are other scenarios where the emulated service originates and terminates on the same provider's PSN, but may pass through several PSN tunnel segments in that PSN. It presents an architectural framework for such multi-segment pseudowires, defines terminology, and specifies the various protocol elements and their functions. This memo provides information for the Internet community. | October 2009 Status: INFORMATIONAL Autor: M. Bocci, S. Bryant |
| RFC5660 IPsec Channels: Connection Latching This document specifies, abstractly, how to interface applications and transport protocols with IPsec so as to create "channels" by latching "connections" (packet flows) to certain IPsec Security Association (SA) parameters for the lifetime of the connections. Connection latching is layered on top of IPsec and does not modify the underlying IPsec architecture. | October 2009 Status: PROPOSED STANDARD Autor: N. Williams |
| RFC5661 Network File System (NFS) Version 4 Minor Version 1 Protocol This document describes the Network File System (NFS) version 4 minor version 1, including features retained from the base protocol (NFS version 4 minor version 0, which is specified in RFC 3530) and protocol extensions made subsequently. Major extensions introduced in NFS version 4 minor version 1 include Sessions, Directory Delegations, and parallel NFS (pNFS). NFS version 4 minor version 1 has no dependencies on NFS version 4 minor version 0, and it is considered a separate protocol. Thus, this document neither updates nor obsoletes RFC 3530. NFS minor version 1 is deemed superior to NFS minor version 0 with no loss of functionality, and its use is preferred over version 0. Both NFS minor versions 0 and 1 can be used simultaneously on the same network, between the same client and server. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: S. Shepler, M. Eisler, D. Noveck |
| RFC5662 Network File System (NFS) Version 4 Minor Version 1 External Data Representation Standard (XDR) Description This document provides the External Data Representation Standard (XDR) description for Network File System version 4 (NFSv4) minor version 1. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: S. Shepler, M. Eisler, D. Noveck |
| RFC5663 Parallel NFS (pNFS) Block/Volume Layout Parallel NFS (pNFS) extends Network File Sharing version 4 (NFSv4) to allow clients to directly access file data on the storage used by the NFSv4 server. This ability to bypass the server for data access can increase both performance and parallelism, but requires additional client functionality for data access, some of which is dependent on the class of storage used. The main pNFS operations document specifies storage-class-independent extensions to NFS; this document specifies the additional extensions (primarily data structures) for use of pNFS with block- and volume-based storage. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: D. Black, S. Fridella, J. Glasgow |
| RFC5664 Object-Based Parallel NFS (pNFS) Operations Parallel NFS (pNFS) extends Network File System version 4 (NFSv4) to allow clients to directly access file data on the storage used by the NFSv4 server. This ability to bypass the server for data access can increase both performance and parallelism, but requires additional client functionality for data access, some of which is dependent on the class of storage used, a.k.a. the Layout Type. The main pNFS operations and data types in NFSv4 Minor version 1 specify a layout- type-independent layer; layout-type-specific information is conveyed using opaque data structures whose internal structure is further defined by the particular layout type specification. This document specifies the NFSv4.1 Object-Based pNFS Layout Type as a companion to the main NFSv4 Minor version 1 specification. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: B. Halevy, B. Welch, J. Zelenka |
| RFC5665 IANA Considerations for Remote Procedure Call (RPC) Network Identifiers and Universal Address Formats This document lists IANA Considerations for Remote Procedure Call (RPC) Network Identifiers (netids) and RPC Universal Network Addresses (uaddrs). This document updates, but does not replace, RFC 1833. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: M. Eisler |
| RFC5666 Remote Direct Memory Access Transport for Remote Procedure Call This document describes a protocol providing Remote Direct Memory Access (RDMA) as a new transport for Remote Procedure Call (RPC). The RDMA transport binding conveys the benefits of efficient, bulk-data transport over high-speed networks, while providing for minimal change to RPC applications and with no required revision of the application RPC protocol, or the RPC protocol itself. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: T. Talpey, B. Callaghan |
| RFC5667 Network File System (NFS) Direct Data Placement This document defines the bindings of the various Network File System (NFS) versions to the Remote Direct Memory Access (RDMA) operations supported by the RPC/RDMA transport protocol. It describes the use of direct data placement by means of server-initiated RDMA operations into client-supplied buffers for implementations of NFS versions 2, 3, 4, and 4.1 over such an RDMA transport. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: T. Talpey, B. Callaghan |
| RFC5668 4-Octet AS Specific BGP Extended Community This document defines a new type of a BGP extended community, which carries a 4-octet Autonomous System (AS) number. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: Y. Rekhter, S. Sangli, D. Tappan |
| RFC5669 The SEED Cipher Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP) This document describes the use of the SEED block cipher algorithm in the Secure Real-time Transport Protocol (SRTP) for providing confidentiality for Real-time Transport Protocol (RTP) traffic and for the control traffic for RTP, the Real-time Transport Control Protocol (RTCP). [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: S. Yoon, J. Kim, H. Park, H. Jeong, Y. Won |
| RFC5670 Metering and Marking Behaviour of PCN-Nodes The objective of Pre-Congestion Notification (PCN) is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain in a simple, scalable, and robust fashion. This document defines the two metering and marking behaviours of PCN-nodes. Threshold-metering and -marking marks all PCN-packets if the rate of PCN-traffic is greater than a configured rate ("PCN-threshold-rate"). Excess- traffic-metering and -marking marks a proportion of PCN-packets, such that the amount marked equals the rate of PCN-traffic in excess of a configured rate ("PCN-excess-rate"). The level of marking allows PCN-boundary-nodes to make decisions about whether to admit or terminate PCN-flows. [STANDARDS-TRACK] | November 2009 Status: PROPOSED STANDARD Autor: P. Eardley |
| RFC5671 Applicability of the Path Computation Element (PCE) to Point-to-Multipoint (P2MP) MPLS and GMPLS Traffic Engineering (TE) The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. | October 2009 Status: INFORMATIONAL Autor: S. Yasukawa, A. Farrel |
| RFC5672 RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update This document updates RFC 4871, "DomainKeys Identified Mail (DKIM) Signatures". Specifically, the document clarifies the nature, roles, and relationship of the two DKIM identifier tag values that are candidates for payload delivery to a receiving processing module. The Update is in the style of an Errata entry, albeit a rather long one. [STANDARDS-TRACK] | August 2009 Status: PROPOSED STANDARD Autor: D. Crocker |
| RFC5673 Industrial Routing Requirements in Low-Power and Lossy Networks The wide deployment of lower-cost wireless devices will significantly improve the productivity and safety of industrial plants while increasing the efficiency of plant workers by extending the information set available about the plant operations. The aim of this document is to analyze the functional requirements for a routing protocol used in industrial Low-power and Lossy Networks (LLNs) of field devices. This memo provides information for the Internet community. | October 2009 Status: INFORMATIONAL Autor: K. Pister, P. Thubert, S. Dwars, T. Phinney |
| RFC5674 Alarms in Syslog This document describes how to send alarm information in syslog. It includes the mapping of ITU perceived severities onto syslog message fields. It also includes a number of alarm-specific SD-PARAM definitions from X.733 and the IETF Alarm MIB. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: S. Chisholm, R. Gerhards |
| RFC5675 Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages This memo defines a mapping from Simple Network Management Protocol (SNMP) notifications to SYSLOG messages. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: V. Marinov, J. Schoenwaelder |
| RFC5676 Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications 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 mapping of SYSLOG messages to Simple Network Management Protocol (SNMP) notifications. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: J. Schoenwaelder, A. Clemm, A. Karmakar |
| RFC5677 IEEE 802.21 Mobility Services Framework Design (MSFD) This document describes a mobility services framework design (MSFD) for the IEEE 802.21 Media Independent Handover (MIH) protocol that addresses identified issues associated with the transport of MIH messages. The document also describes mechanisms for Mobility Services (MoS) discovery and transport-layer mechanisms for the reliable delivery of MIH messages. This document does not provide mechanisms for securing the communication between a mobile node (MN) and the Mobility Server. Instead, it is assumed that either lower-layer (e.g., link-layer) security mechanisms or overall system-specific proprietary security solutions are used. [STANDARDS-TRACK] | December 2009 Status: PROPOSED STANDARD Autor: T. Melia, G. Bajko, S. Das, N. Golmie, JC. Zuniga |
| RFC5678 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) Discovery This document defines new Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) options that contain a list of IP addresses and a list of domain names that can be mapped to servers providing IEEE 802.21 type of Mobility Service (MoS) (see RFC 5677). These Mobility Services are used to assist a mobile node (MN) in handover preparation (network discovery) and handover decision (network selection). The services addressed in this document are the Media Independent Handover Services defined in IEEE 802.21. [STANDARDS-TRACK] | December 2009 Status: PROPOSED STANDARD Autor: G. Bajko, S. Das |
| RFC5679 Locating IEEE 802.21 Mobility Services Using DNS This document defines application service tags that allow service location without relying on rigid domain naming conventions, and DNS procedures for discovering servers that provide IEEE 802.21-defined Mobility Services. Such Mobility Services are used to assist a Mobile Node (MN) supporting IEEE 802.21, in handover preparation (network discovery) and handover decision (network selection). The services addressed by this document are the Media Independent Handover Services defined in IEEE 802.21. [STANDARDS-TRACK] | December 2009 Status: PROPOSED STANDARD Autor: G. Bajko |
| RFC5680 The Nominating Committee Process: Open Disclosure of Willing Nominees This document updates RFC 3777, Section 3, Bullet 6 to allow a Nominating and Recall Committee to disclose the list of nominees who are willing to be considered to serve in positions the committee is responsible for filling. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. | October 2009 Status: BEST CURRENT PRACTICE Autor: S. Dawkins |
| RFC5681 TCP Congestion Control 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. This document obsoletes RFC 2581. [STANDARDS-TRACK] | September 2009 Status: DRAFT STANDARD Autor: M. Allman, V. Paxson, E. Blanton |
| RFC5682 Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP The purpose of this document is to move the F-RTO (Forward RTO-Recovery) functionality for TCP in RFC 4138 from Experimental to Standards Track status. The F-RTO support for Stream Control Transmission Protocol (SCTP) in RFC 4138 remains with Experimental status. See Appendix B for the differences between this document and RFC 4138. | September 2009 Status: PROPOSED STANDARD Autor: P. Sarolahti, M. Kojo, K. Yamamoto, M. Hata |
| RFC5683 Password-Authenticated Key (PAK) Diffie-Hellman Exchange This document proposes to add mutual authentication, based on a human-memorizable password, to the basic, unauthenticated Diffie-Hellman key exchange. The proposed algorithm is called the Password-Authenticated Key (PAK) exchange. PAK allows two parties to authenticate themselves while performing the Diffie-Hellman exchange. | February 2010 Status: INFORMATIONAL Autor: A. Brusilovsky, I. Faynberg, Z. Zeltsan, S. Patel |
| RFC5684 Unintended Consequences of NAT Deployments with Overlapping Address Space This document identifies two deployment scenarios that have arisen from the unconventional network topologies formed using Network Address Translator (NAT) devices. First, the simplicity of administering networks through the combination of NAT and DHCP has increasingly lead to the deployment of multi-level inter-connected private networks involving overlapping private IP address spaces. Second, the proliferation of private networks in enterprises, hotels and conferences, and the wide-spread use of Virtual Private Networks (VPNs) to access an enterprise intranet from remote locations has increasingly lead to overlapping private IP address space between remote and corporate networks. This document does not dismiss these unconventional scenarios as invalid, but recognizes them as real and offers recommendations to help ensure these deployments can function without a meltdown. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: P. Srisuresh, B. Ford |
| RFC5685 Redirect Mechanism for the Internet Key Exchange Protocol Version 2 (IKEv2) The Internet Key Exchange Protocol version 2 (IKEv2) is a protocol for setting up Virtual Private Network (VPN) tunnels from a remote location to a gateway so that the VPN client can access services in the network behind the gateway. This document defines an IKEv2 extension that allows an overloaded VPN gateway or a VPN gateway that is being shut down for maintenance to redirect the VPN client to attach to another gateway. The proposed mechanism can also be used in Mobile IPv6 to enable the home agent to redirect the mobile node to another home agent. [STANDARDS-TRACK] | November 2009 Status: PROPOSED STANDARD Autor: V. Devarapalli, K. Weniger |
| RFC5686 RTP Payload Format for mU-law EMbedded Codec for Low-delay IP Communication (UEMCLIP) Speech Codec This document describes the RTP payload format of a mU-law EMbedded Coder for Low-delay IP communication (UEMCLIP), an enhanced speech codec of ITU-T G.711. The bitstream has a scalable structure with an embedded u-law bitstream, also known as PCMU, thus providing a handy transcoding operation between narrowband and wideband speech. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: Y. Hiwasaki, H. Ohmuro |
| RFC5687 GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements This document provides a problem statement, lists requirements, and captures design aspects for a GEOPRIV Layer 7 (L7) Location Configuration Protocol (LCP). This protocol aims to allow an end host to obtain location information, by value or by reference, from a Location Information Server (LIS) that is located in the access network. The obtained location information can then be used for a variety of different protocols and purposes. For example, it can be used as input to the Location-to-Service Translation (LoST) Protocol or to convey location within the Session Initiation Protocol (SIP) to other entities. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2010 Status: INFORMATIONAL Autor: H. Tschofenig, H. Schulzrinne |
| RFC5688 A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtypes The caller preferences specification for the Session Initiation Protocol (SIP) allows a caller to express preferences that the call be routed to a User Agent (UA) with particular capabilities. Similarly, a specification exists to allow a UA to indicate its capabilities in a registration. Amongst those capabilities are the type of media streams the agent supports, described as top-level MIME types. The 'application' MIME type is used to describe a broad range of stream types, and it provides insufficient granularity as a capability. This specification allows a UA to indicate which application subtypes the agent supports. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC5689 Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV) This specification extends the Web Distributed Authoring and Versioning (WebDAV) MKCOL (Make Collection) method to allow collections of arbitrary resourcetype to be created and to allow properties to be set at the same time. [STANDARDS-TRACK] | September 2009 Status: PROPOSED STANDARD Autor: C. Daboo |
| RFC5690 Adding Acknowledgement Congestion Control to TCP This document describes a possible congestion control mechanism for acknowledgement (ACKs) traffic in TCP. The document specifies an end-to-end acknowledgement congestion control mechanism for TCP that uses participation from both TCP hosts: the TCP data sender and the TCP data receiver. The TCP data sender detects lost or Explicit Congestion Notification (ECN)-marked ACK packets, and tells the TCP data receiver the ACK Ratio R to use to respond to the congestion on the reverse path from the data receiver to the data sender. The TCP data receiver sends roughly one ACK packet for every R data packets received. This mechanism is based on the acknowledgement congestion control in the Datagram Congestion Control Protocol's (DCCP's) Congestion Control Identifier (CCID) 2. This acknowledgement congestion control mechanism is being specified for further evaluation by the network community. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: S. Floyd, A. Arcia, D. Ros, J. Iyengar |
| RFC5691 RTP Payload Format for Elementary Streams with MPEG Surround Multi-Channel Audio This memo describes extensions for the RTP payload format defined in RFC 3640 for the transport of MPEG Surround multi-channel audio. Additional Media Type parameters are defined to signal backwards- compatible transmission inside an MPEG-4 Audio elementary stream. In addition, a layered transmission scheme that doesn't use the MPEG-4 systems framework is presented to transport an MPEG Surround elementary stream via RTP in parallel with an RTP stream containing the downmixed audio data. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: F. de Bont, S. Doehla, M. Schmidt, R. Sperschneider |
| RFC5692 Transmission of IP over Ethernet over IEEE 802.16 Networks This document describes the transmission of IPv4 over Ethernet, as well as IPv6 over Ethernet, in an access network deploying the IEEE 802.16 cellular radio transmission technology. The Ethernet on top of IEEE 802.16 is realized by bridging connections that IEEE 802.16 provides between a base station and its associated subscriber stations. Due to the resource constraints of radio transmission systems and the limitations of the IEEE 802.16 Media Access Control (MAC) functionality for the realization of an Ethernet, the transmission of IP over Ethernet over IEEE 802.16 may considerably benefit by adding IP-specific support functions in the Ethernet over IEEE 802.16 while maintaining full compatibility with standard IP over Ethernet behavior. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: H. Jeon, S. Jeong, M. Riegel |
| RFC5693 Application-Layer Traffic Optimization (ALTO) Problem Statement Distributed applications -- such as file sharing, real-time communication, and live and on-demand media streaming -- prevalent on the Internet use a significant amount of network resources. Such applications often transfer large amounts of data through connections established between nodes distributed across the Internet with little knowledge of the underlying network topology. Some applications are so designed that they choose a random subset of peers from a larger set with which to exchange data. Absent any topology information guiding such choices, or acting on suboptimal or local information obtained from measurements and statistics, these applications often make less than desirable choices. | October 2009 Status: INFORMATIONAL Autor: J. Seedorf, E. Burger |
| RFC5694 Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and Applicability In this document, we provide a survey of P2P (Peer-to-Peer) systems. The survey includes a definition and several taxonomies of P2P systems. This survey also includes a description of which types of applications can be built with P2P technologies and examples of P2P applications that are currently in use on the Internet. Finally, we discuss architectural trade-offs and provide guidelines for deciding whether or not a P2P architecture would be suitable to meet the requirements of a given application. This memo provides information for the Internet community. | November 2009 Status: INFORMATIONAL Autor: G. Camarillo, IAB |
| RFC5695 MPLS Forwarding Benchmarking Methodology for IP Flows This document describes a methodology specific to the benchmarking of Multiprotocol Label Switching (MPLS) forwarding devices, limited to the most common MPLS packet forwarding scenarios and delay measurements for each, considering IP flows. It builds upon the tenets set forth in RFC 2544, RFC 1242, and other IETF Benchmarking Methodology Working Group (BMWG) efforts. This document seeks to extend these efforts to the MPLS paradigm. This memo provides information for the Internet community. | November 2009 Status: INFORMATIONAL Autor: A. Akhter, R. Asati, C. Pignataro |
| RFC5696 Baseline Encoding and Transport of Pre-Congestion Information The objective of the Pre-Congestion Notification (PCN) architecture is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. It achieves this by marking packets belonging to PCN-flows when the rate of traffic exceeds certain configured thresholds on links in the domain. These marks can then be evaluated to determine how close the domain is to being congested. This document specifies how such marks are encoded into the IP header by redefining the Explicit Congestion Notification (ECN) codepoints within such domains. The baseline encoding described here provides only two PCN encoding states: Not-marked and PCN-marked. Future extensions to this encoding may be needed in order to provide more than one level of marking severity. [STANDARDS-TRACK] | November 2009 Status: PROPOSED STANDARD Autor: T. Moncaster, B. Briscoe, M. Menth |
| RFC5697 Other Certificates Extension Some applications that associate state information with public key certificates can benefit from a way to link together a set of certificates that belong to the same end entity and that can safely be considered equivalent to one another for the purposes of referencing that application-state information. This memo defines a certificate extension that allows applications to establish the required linkage without introducing a new application protocol data unit. This memo defines an Experimental Protocol for the Internet community. | November 2009 Status: EXPERIMENTAL Autor: S. Farrell |
| RFC5698 Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC) Since cryptographic algorithms can become weak over the years, it is necessary to evaluate their security suitability. When signing or verifying data, or when encrypting or decrypting data, these evaluations must be considered. This document specifies a data structure that enables an automated analysis of the security suitability of a given cryptographic algorithm at a given point of time, which may be in the past, the present, or the future. [STANDARDS-TRACK] | November 2009 Status: PROPOSED STANDARD Autor: T. Kunz, S. Okunick, U. Pordesch |
| RFC5701 IPv6 Address Specific BGP Extended Community Attribute Current specifications of BGP Extended Communities (RFC 4360) support the IPv4 Address Specific Extended Community, but do not support an IPv6 Address Specific Extended Community. The lack of an IPv6 Address Specific Extended Community may be a problem when an application uses the IPv4 Address Specific Extended Community, and one wants to use this application in a pure IPv6 environment. This document defines a new BGP attribute, the IPv6 Address Specific Extended Community, that addresses this problem. The IPv6 Address Specific Extended Community is similar to the IPv4 Address Specific Extended Community, except that it carries an IPv6 address rather than an IPv4 address. [STANDARDS TRACK] | November 2009 Status: PROPOSED STANDARD Autor: Y. Rekhter |
| RFC5702 Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC This document describes how to produce RSA/SHA-256 and RSA/SHA-512 DNSKEY and RRSIG resource records for use in the Domain Name System Security Extensions (RFC 4033, RFC 4034, and RFC 4035). [STANDARDS TRACK] | October 2009 Status: PROPOSED STANDARD Autor: J. Jansen |
| RFC5703 Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure This document defines extensions to the Sieve email filtering language to permit analysis and manipulation of the MIME body parts of an email message. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: T. Hansen, C. Daboo |
| RFC5704 Uncoordinated Protocol Development Considered Harmful This document identifies problems that may result from the absence of formal coordination and joint development on protocols of mutual interest between standards development organizations (SDOs). Some of these problems may cause significant harm to the Internet. The document suggests that a robust procedure is required prevent this from occurring in the future. The IAB has selected a number of case studies, such as Transport MPLS (T-MPLS), as recent examples to describe the hazard to the Internet architecture that results from uncoordinated adaptation of a protocol. | November 2009 Status: INFORMATIONAL Autor: S. Bryant, M. Morrow, IAB |
| RFC5705 Keying Material Exporters for Transport Layer Security (TLS) A number of protocols wish to leverage Transport Layer Security (TLS) to perform key establishment but then use some of the keying material for their own purposes. This document describes a general mechanism for allowing that. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: E. Rescorla |
| RFC5706 Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions New protocols or protocol extensions are best designed with due consideration of the functionality needed to operate and manage the protocols. Retrofitting operations and management is sub-optimal. The purpose of this document is to provide guidance to authors and reviewers of documents that define new protocols or protocol extensions regarding aspects of operations and management that should be considered. This memo provides information for the Internet community. | November 2009 Status: INFORMATIONAL Autor: D. Harrington |
| RFC5707 Media Server Markup Language (MSML) The Media Server Markup Language (MSML) is used to control and invoke many different types of services on IP media servers. The MSML control interface was initially driven by RadiSys with subsequent significant contributions from Intel, Dialogic, and others in the industry. Clients can use it to define how multimedia sessions interact on a media server and to apply services to individuals or groups of users. MSML can be used, for example, to control media server conferencing features such as video layout and audio mixing, create sidebar conferences or personal mixes, and set the properties of media streams. As well, clients can use MSML to define media processing dialogs, which may be used as parts of application interactions with users or conferences. Transformation of media streams to and from users or conferences as well as interactive voice response (IVR) dialogs are examples of such interactions, which are specified using MSML. MSML clients may also invoke dialogs with individual users or with groups of conference participants using VoiceXMLThis document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: A. Saleem, Y. Xin, G. Sharratt |
| RFC5708 X.509 Key and Signature Encoding for the KeyNote Trust Management System This memo describes X.509 key identifiers and signature encoding for version 2 of the KeyNote trust-management system (RFC 2704). X.509 certificates (RFC 5280) can be directly used in the Authorizer or Licensees field (or in both fields) in a KeyNote assertion, allowing for easy integration with protocols that already use X.509 certificates for authentication. | January 2010 Status: INFORMATIONAL Autor: A. Keromytis |
| RFC5709 OSPFv2 HMAC-SHA Cryptographic Authentication This document describes how the National Institute of Standards and Technology (NIST) Secure Hash Standard family of algorithms can be used with OSPF version 2's built-in, cryptographic authentication mechanism. This updates, but does not supercede, the cryptographic authentication mechanism specified in RFC 2328. [STANDARDS-TRACK] | October 2009 Status: PROPOSED STANDARD Autor: M. Bhatia, V. Manral, M. Fanto, R. White, M. Barnes, T. Li, R. Atkinson |
| RFC5710 PathErr Message Triggered MPLS and GMPLS LSP Reroutes This document describes how Resource ReserVation Protocol (RSVP) PathErr messages may be used to trigger rerouting of Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) point-to-point Traffic Engineering (TE) Label Switched Paths (LSPs) without first removing LSP state or resources. Such LSP rerouting may be desirable in a number of cases, including, for example, soft-preemption and graceful shutdown. This document describes the usage of existing Standards Track mechanisms to support LSP rerouting. In this case, it relies on mechanisms already defined as part of RSVP-TE and simply describes a sequence of actions to be executed. While existing protocol definitions can be used to support reroute applications, this document also defines a new reroute-specific error code to allow for the future definition of reroute-application-specific error values. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: L. Berger, D. Papadimitriou, JP. Vasseur |
| RFC5711 Node Behavior upon Originating and Receiving Resource Reservation Protocol (RSVP) Path Error Messages The aim of this document is to describe a common practice with regard to the behavior of nodes that send and receive a Resource Reservation Protocol (RSVP) Traffic Engineering (TE) Path Error messages for a preempted Multiprotocol Label Switching (MPLS) or Generalized MPLS (GMPLS) Traffic Engineering Label Switched Path (TE LSP). (For reference to the notion of TE LSP preemption, see RFC 3209.) This document does not define any new protocol extensions. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: JP. Vasseur, G. Swallow, I. Minei |
| RFC5712 MPLS Traffic Engineering Soft Preemption This document specifies Multiprotocol Label Switching (MPLS) Traffic Engineering Soft Preemption, a suite of protocol modifications extending the concept of preemption with the goal of reducing or eliminating traffic disruption of preempted Traffic Engineering Label Switched Paths (TE LSPs). Initially, MPLS RSVP-TE was defined with support for only immediate TE LSP displacement upon preemption. The utilization of a reroute request notification helps more gracefully mitigate the reroute process of preempted TE LSP. For the brief period soft preemption is activated, reservations (though not necessarily traffic levels) are in effect under-provisioned until the TE LSP(s) can be rerouted. For this reason, the feature is primarily, but not exclusively, interesting in MPLS-enabled IP networks with Differentiated Services and Traffic Engineering capabilities. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: M. Meyer, JP. Vasseur |
| RFC5713 Security Threats and Security Requirements for the Access Node Control Protocol (ANCP) The Access Node Control Protocol (ANCP) aims to communicate Quality of Service (QoS)-related, service-related, and subscriber-related configurations and operations between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)). The main goal of this protocol is to allow the NAS to configure, manage, and control access equipment, including the ability for the Access Nodes to report information to the NAS. | January 2010 Status: INFORMATIONAL Autor: H. Moustafa, H. Tschofenig, S. De Cnodder |
| RFC5714 IP Fast Reroute Framework This document provides a framework for the development of IP fast- reroute mechanisms that provide protection against link or router failure by invoking locally determined repair paths. Unlike MPLS fast-reroute, the mechanisms are applicable to a network employing conventional IP routing and forwarding. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2010 Status: INFORMATIONAL Autor: M. Shand, S. Bryant |
| RFC5715 A Framework for Loop-Free Convergence A micro-loop is a packet forwarding loop that may occur transiently among two or more routers in a hop-by-hop packet forwarding paradigm. | January 2010 Status: INFORMATIONAL Autor: M. Shand, S. Bryant |
| RFC5716 Requirements for Federated File Systems This document describes and lists the functional requirements of a federated file system and defines related terms. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2010 Status: INFORMATIONAL Autor: J. Lentini, C. Everhart, D. Ellard, R. Tewari, M. Naik |
| RFC5717 Partial Lock Remote Procedure Call (RPC) for NETCONF The Network Configuration protocol (NETCONF) defines the lock and unlock Remote Procedure Calls (RPCs), used to lock entire configuration datastores. In some situations, a way to lock only parts of a configuration datastore is required. This document defines a capability-based extension to the NETCONF protocol for locking portions of a configuration datastore. [STANDARDS-TRACK] | December 2009 Status: PROPOSED STANDARD Autor: B. Lengyel, M. Bjorklund |
| RFC5718 An In-Band Data Communication Network For the MPLS Transport Profile The Generic Associated Channel (G-ACh) has been defined as a generalization of the pseudowire (PW) associated control channel to enable the realization of a control/communication channel that is associated with Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs), MPLS PWs, MPLS LSP segments, and MPLS sections between adjacent MPLS-capable devices. | January 2010 Status: PROPOSED STANDARD Autor: D. Beller, A. Farrel |
| RFC5719 Updated IANA Considerations for Diameter Command Code Allocations The Diameter base specification, described in RFC 3588, provides a number of ways to extend Diameter, with new Diameter commands (i.e., messages used by Diameter applications) and applications as the most extensive enhancements. RFC 3588 illustrates the conditions that lead to the need to define a new Diameter application or a new command code. Depending on the scope of the Diameter extension, IETF actions are necessary. Although defining new Diameter applications does not require IETF consensus, defining new Diameter commands requires IETF consensus per RFC 3588. This has led to questionable design decisions by other Standards Development Organizations, which chose to define new applications on existing commands -- rather than asking for assignment of new command codes -- for the pure purpose of avoiding bringing their specifications to the IETF. In some cases, interoperability problems were an effect of the poor design caused by overloading existing commands. | January 2010 Status: PROPOSED STANDARD Autor: D. Romascanu, H. Tschofenig |
| RFC5720 Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) RANGER is an architectural framework for scalable routing and addressing in networks with global enterprise recursion. The term "enterprise network" within this context extends to a wide variety of use cases and deployment scenarios, where an "enterprise" can be as small as a Small Office, Home Office (SOHO) network, as dynamic as a Mobile Ad Hoc Network, as complex as a multi-organizational corporation, or as large as the global Internet itself. Such networks will require an architected solution for the coordination of routing and addressing plans with accommodations for scalability, provider-independence, mobility, multihoming, and security. These considerations are particularly true for existing deployments, but the same principles apply even for clean-slate approaches. The RANGER architecture addresses these requirements and provides a comprehensive framework for IPv6/IPv4 coexistence. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: F. Templin |
| RFC5721 POP3 Support for UTF-8 This specification extends the Post Office Protocol version 3 (POP3) to support un-encoded international characters in user names, passwords, mail addresses, message headers, and protocol-level textual error strings. This document defines an Experimental Protocol for the Internet community. | February 2010 Status: EXPERIMENTAL Autor: R. Gellens, C. Newman |
| RFC5722 Handling of Overlapping IPv6 Fragments The fragmentation and reassembly algorithm specified in the base IPv6 specification allows fragments to overlap. This document demonstrates the security issues associated with allowing overlapping fragments and updates the IPv6 specification to explicitly forbid overlapping fragments. [STANDARDS-TRACK] | December 2009 Status: PROPOSED STANDARD Autor: S. Krishnan |
| RFC5723 Internet Key Exchange Protocol Version 2 (IKEv2) Session Resumption The Internet Key Exchange version 2 (IKEv2) protocol has a certain computational and communication overhead with respect to the number of round trips required and the cryptographic operations involved. In remote access situations, the Extensible Authentication Protocol (EAP) is used for authentication, which adds several more round trips and consequently latency. | January 2010 Status: PROPOSED STANDARD Autor: Y. Sheffer, H. Tschofenig |
| RFC5724 URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS) This memo specifies the Uniform Resource Identifier (URI) scheme "sms" for specifying one or more recipients for an SMS message. SMS messages are two-way paging messages that can be sent from and received by a mobile phone or a suitably equipped networked device. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: E. Wilde, A. Vaha-Sipila |
| RFC5725 Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs) This document defines a new report block type within the framework of RTP Control Protocol (RTCP) Extended Reports (XRs). One of the initial XR report block types is the Loss Run Length Encoding (RLE) Report Block. This report conveys information regarding the individual Real-time Transport Protocol (RTP) packet receipt and loss events experienced during the RTCP interval preceding the transmission of the report. The new report, which is referred to as the Post-repair Loss RLE report, carries information regarding the packets that remain lost after all loss-repair methods are applied. By comparing the RTP packet receipts/losses before and after the loss repair is completed, one can determine the effectiveness of the loss- repair methods in an aggregated fashion. This document also defines the signaling of the Post-repair Loss RLE report in the Session Description Protocol (SDP). [STANDARDS-TRACK] | February 2010 Status: PROPOSED STANDARD Autor: A. Begen, D. Hsu, M. Lague |
| RFC5726 Mobile IPv6 Location Privacy Solutions Mobile IPv6 (RFC 3775) enables a mobile node to remain reachable while it roams on the Internet. However, the location and movement of the mobile node can be revealed by the IP addresses used in signaling or data packets. In this document, we consider the Mobile IPv6 location privacy problem described in RFC 4882, and propose efficient and secure techniques to protect location privacy of the mobile node. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This document defines an Experimental Protocol for the Internet community. | February 2010 Status: EXPERIMENTAL Autor: Y. Qiu, F. Zhao, R. Koodli |
| RFC5727 Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area This memo documents a process intended to organize the future development of the Session Initiation Protocol (SIP) and related work in the Real-time Applications and Infrastructure (RAI) Area. As the environments in which SIP is deployed grow more numerous and diverse, modifying or extending SIP in certain ways may threaten the interoperability and security of the protocol; however, the IETF process must also cater to the realities of existing deployments and serve the needs of the implementers working with SIP. This document therefore defines the functions of two long-lived working groups in the RAI Area that are, respectively, responsible for the maintenance of the core SIP specifications and the development of new efforts to extend and apply work in this space. This document obsoletes RFC 3427. This memo documents an Internet Best Current Practice. | March 2010 Status: BEST CURRENT PRACTICE Autor: J. Peterson, C. Jennings, R. Sparks |
| RFC5728 The SatLabs Group DVB-RCS MIB This document describes the MIB module for the Digital Video Broadcasting Return Channel via Satellite system (DVB-RCS), as defined by the SatLabs Group. It defines a set of MIB objects to characterize the behavior and performance of network-layer entities deploying DVB-RCS. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2010 Status: INFORMATIONAL Autor: S. Combes, P. Amundsen, M. Lambert, H-P. Lexow |
| RFC5729 Clarifications on the Routing of Diameter Requests Based on the Username and the Realm This specification defines the behavior required of Diameter agents to route requests when the User-Name Attribute Value Pair contains a Network Access Identifier formatted with multiple realms. These multi-realm, or "Decorated", Network Access Identifiers are used in order to force the routing of request messages through a predefined list of mediating realms. [STANDARDS-TRACK] | December 2009 Status: PROPOSED STANDARD Autor: J. Korhonen, M. Jones, L. Morand, T. Tsou |
| RFC5730 Extensible Provisioning Protocol (EPP) 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. This document obsoletes RFC 4930. [STANDARDS-TRACK] | August 2009 Status: STANDARD Autor: S. Hollenbeck |
| RFC5731 Extensible Provisioning Protocol (EPP) Domain Name Mapping 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. This document obsoletes RFC 4931. [STANDARDS-TRACK] | August 2009 Status: STANDARD Autor: S. Hollenbeck |
| RFC5732 Extensible Provisioning Protocol (EPP) Host Mapping 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. This document obsoletes RFC 4932. [STANDARDS-TRACK] | August 2009 Status: STANDARD Autor: S. Hollenbeck |
| RFC5733 Extensible Provisioning Protocol (EPP) Contact Mapping 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. This document obsoletes RFC 4933. [STANDARDS-TRACK] | August 2009 Status: STANDARD Autor: S. Hollenbeck |
| RFC5734 Extensible Provisioning Protocol (EPP) Transport over TCP 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. This document obsoletes RFC 4934. [STANDARDS-TRACK] | August 2009 Status: STANDARD Autor: S. Hollenbeck |
| RFC5735 Special Use IPv4 Addresses This document obsoletes RFC 3330. It describes the global and other specialized IPv4 address blocks that have been assigned by the Internet Assigned Numbers Authority (IANA). It does not address IPv4 address space assigned to operators and users through the Regional Internet Registries, nor does it address IPv4 address space assigned directly by IANA prior to the creation of the Regional Internet Registries. It also does not address allocations or assignments of IPv6 addresses or autonomous system numbers. This memo documents an Internet Best Current Practice. | January 2010 Status: BEST CURRENT PRACTICE Autor: M. Cotton, L. Vegoda |
| RFC5736 IANA IPv4 Special Purpose Address Registry This is a direction to IANA concerning the creation and management of the IANA IPv4 Special Purpose Address Registry. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2010 Status: INFORMATIONAL Autor: G. Huston, M. Cotton, L. Vegoda |
| RFC5737 IPv4 Address Blocks Reserved for Documentation Three IPv4 unicast address blocks are reserved for use in examples in specifications and other documents. This document describes the use of these blocks. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2010 Status: INFORMATIONAL Autor: J. Arkko, M. Cotton, L. Vegoda |
| RFC5738 IMAP Support for UTF-8 This specification extends the Internet Message Access Protocol version 4rev1 (IMAP4rev1) to support UTF-8 encoded international characters in user names, mail addresses, and message headers. This document defines an Experimental Protocol for the Internet community. | March 2010 Status: EXPERIMENTAL Autor: P. Resnick, C. Newman |
| RFC5739 IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2) When Internet Key Exchange Protocol version 2 (IKEv2) is used for remote VPN access (client to VPN gateway), the gateway assigns the client an IP address from the internal network using IKEv2 configuration payloads. The configuration payloads specified in RFC 4306 work well for IPv4 but make it difficult to use certain features of IPv6. This document specifies new configuration attributes for IKEv2 that allows the VPN gateway to assign IPv6 prefixes to clients, enabling all features of IPv6 to be used with the client-gateway "virtual link". This document defines an Experimental Protocol for the Internet community. | February 2010 Status: EXPERIMENTAL Autor: P. Eronen, J. Laganier, C. Madson |
| RFC5740 NACK-Oriented Reliable Multicast (NORM) Transport Protocol This document describes the messages and procedures of the Negative- ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) protocol. This protocol can 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 (forward error correction) repair and other IETF Reliable Multicast Transport (RMT) building blocks in its design. This document obsoletes RFC 3940. [STANDARDS-TRACK] | November 2009 Status: PROPOSED STANDARD Autor: B. Adamson, C. Bormann, M. Handley, J. Macker |
| RFC5741 RFC Streams, Headers, and Boilerplates RFC documents contain a number of fixed elements such as the title page header, standard boilerplates, and copyright/IPR statements. This document describes them and introduces some updates to reflect current usage and requirements of RFC publication. In particular, this updated structure is intended to communicate clearly the source of RFC creation and review. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2009 Status: INFORMATIONAL Autor: L. Daigle, O. Kolkman, IAB |
| RFC5742 IESG Procedures for Handling of Independent and IRTF Stream Submissions This document describes the procedures used by the IESG for handling documents submitted for RFC publication from the Independent Submission and IRTF streams. | December 2009 Status: BEST CURRENT PRACTICE Autor: H. Alvestrand, R. Housley |
| RFC5743 Definition of an Internet Research Task Force (IRTF) Document Stream This memo defines the publication stream for RFCs from the Internet Research Task Force. Most documents undergoing this process will come from IRTF Research Groups, and it is expected that they will be published as Informational or Experimental RFCs by the RFC Editor. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2009 Status: INFORMATIONAL Autor: A. Falk |
| RFC5744 Procedures for Rights Handling in the RFC Independent Submission Stream This document specifies the procedures by which authors of RFC Independent Submission documents grant the community "incoming" rights for copying and using the text. It also specifies the "outgoing" rights the community grants to readers and users of those documents, and it requests that the IETF Trust manage the outgoing rights to effect this result. This memo provides information for the Internet community. | December 2009 Status: INFORMATIONAL Autor: R. Braden, J. Halpern |
| RFC5745 Procedures for Rights Handling in the RFC IAB Stream This document specifies the procedures by which authors of RFC IAB stream documents grant the community "incoming" rights for copying and using the text. It also specifies the "outgoing" rights the community grants to readers and users of those documents, and it requests that the IETF Trust manage the outgoing rights to effect this result. This memo provides information for the Internet community. | December 2009 Status: INFORMATIONAL Autor: A. Malis, IAB |
| RFC5746 Transport Layer Security (TLS) Renegotiation Indication Extension Secure Socket Layer (SSL) and Transport Layer Security (TLS) renegotiation are vulnerable to an attack in which the attacker forms a TLS connection with the target server, injects content of his choice, and then splices in a new TLS connection from a client. The server treats the client's initial TLS handshake as a renegotiation and thus believes that the initial data transmitted by the attacker is from the same entity as the subsequent client data. This specification defines a TLS extension to cryptographically tie renegotiations to the TLS connections they are being performed over, thus preventing this attack. [STANDARDS-TRACK] | February 2010 Status: PROPOSED STANDARD Autor: E. Rescorla, M. Ray, S. Dispensa, N. Oskov |
| RFC5747 4over6 Transit Solution Using IP Encapsulation and MP-BGP Extensions The emerging and growing deployment of IPv6 networks will introduce cases where connectivity with IPv4 networks crossing IPv6 transit backbones is desired. This document describes a mechanism for automatic discovery and creation of IPv4-over-IPv6 tunnels via extensions to multiprotocol BGP. It is targeted at connecting islands of IPv4 networks across an IPv6-only backbone without the need for a manually configured overlay of tunnels. The mechanisms described in this document have been implemented, tested, and deployed on the large research IPv6 network in China. This document defines an Experimental Protocol for the Internet community. | March 2010 Status: EXPERIMENTAL Autor: J. Wu, Y. Cui, X. Li, M. Xu, C. Metz |
| RFC5748 IANA Registry Update for Support of the SEED Cipher Algorithm in Multimedia Internet KEYing (MIKEY) This document updates IANA registries to support the SEED block cipher algorithm for the Secure Real-time Transport Protocol (SRTP) and the secure Real-time Transport Control Protocol (SRTCP) in Multimedia Internet KEYing (MIKEY). This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: S. Yoon, J. Jeong, H. Kim, H. Jeong, Y. Won |
| RFC5749 Distribution of EAP-Based Keys for Handover and Re-Authentication This document describes an abstract mechanism for delivering root keys from an Extensible Authentication Protocol (EAP) server to another network server that requires the keys for offering security protected services, such as re-authentication, to an EAP peer. The distributed root key can be either a usage-specific root key (USRK), a domain-specific root key (DSRK), or a domain-specific usage- specific root key (DSUSRK) that has been derived from an Extended Master Session Key (EMSK) hierarchy previously established between the EAP server and an EAP peer. This document defines a template for a key distribution exchange (KDE) protocol that can distribute these different types of root keys using a AAA (Authentication, Authorization, and Accounting) protocol and discusses its security requirements. The described protocol template does not specify message formats, data encoding, or other implementation details. It thus needs to be instantiated with a specific protocol (e.g., RADIUS or Diameter) before it can be used. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: K. Hoeper, M. Nakhjiri, Y. Ohba |
| RFC5750 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) v3.2 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 5280, 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 5280. This document obsoletes RFC 3850. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: B. Ramsdell, S. Turner |
| RFC5751 Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.2. 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 3851. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: B. Ramsdell, S. Turner |
| RFC5752 Multiple Signatures in Cryptographic Message Syntax (CMS) Cryptographic Message Syntax (CMS) SignedData includes the SignerInfo structure to convey per-signer information. SignedData supports multiple signers and multiple signature algorithms per signer with multiple SignerInfo structures. If a signer attaches more than one SignerInfo, there are concerns that an attacker could perform a downgrade attack by removing the SignerInfo(s) with the \'strong' algorithm(s). This document defines the multiple-signatures attribute, its generation rules, and its processing rules to allow signers to convey multiple SignerInfo objects while protecting against downgrade attacks. Additionally, this attribute may assist during periods of algorithm migration. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: S. Turner, J. Schaad |
| RFC5753 Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) 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 NIST FIPS 186-3 for digital signature, NIST SP800-56A and SEC1 for key agreement, RFC 3370 and RFC 3565 for key wrap and content encryption, NIST FIPS 180-3 for message digest, SEC1 for key derivation, and RFC 2104 and RFC 4231 for message authentication code standards. This document obsoletes RFC 3278. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2010 Status: INFORMATIONAL Autor: S. Turner, D. Brown |
| RFC5754 Using SHA2 Algorithms with Cryptographic Message Syntax This document describes the conventions for using the Secure Hash Algorithm (SHA) message digest algorithms (SHA-224, SHA-256, SHA-384, SHA-512) with the Cryptographic Message Syntax (CMS). It also describes the conventions for using these algorithms with the CMS and the Digital Signature Algorithm (DSA), Rivest Shamir Adleman (RSA), and Elliptic Curve DSA (ECDSA) signature algorithms. Further, it provides SMIMECapabilities attribute values for each algorithm. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC5755 An Internet Attribute Certificate Profile for Authorization 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. This document obsoletes RFC 3281. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: S. Farrell, R. Housley, S. Turner |
| RFC5756 Updates for RSAES-OAEP and RSASSA-PSS Algorithm Parameters This document updates RFC 4055. It updates the conventions for using the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport algorithm in the Internet X.509 Public Key Infrastructure (PKI). Specifically, it updates the conventions for algorithm parameters in an X.509 certificate's subjectPublicKeyInfo field. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: S. Turner, D. Brown, K. Yiu, R. Housley, T. Polk |
| RFC5757 Multicast Mobility in Mobile IP Version 6 (MIPv6): Problem Statement and Brief Survey This document discusses current mobility extensions to IP-layer multicast. It describes problems arising from mobile group communication in general, the case of multicast listener mobility, and problems for mobile senders using Any Source Multicast and Source-Specific Multicast. Characteristic aspects of multicast routing and deployment issues for fixed IPv6 networks are summarized. Specific properties and interplays with the underlying network access are surveyed with respect to the relevant technologies in the wireless domain. It outlines the principal approaches to multicast mobility, together with a comprehensive exploration of the mobile multicast problem and solution space. This document concludes with a conceptual road map for initial steps in standardization for use by future mobile multicast protocol designers. This document is a product of the IP Mobility Optimizations (MobOpts) Research Group. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: T. Schmidt, M. Waehlisch, G. Fairhurst |
| RFC5758 Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA This document updates RFC 3279 to specify algorithm identifiers and ASN.1 encoding rules for the Digital Signature Algorithm (DSA) and Elliptic Curve Digital Signature Algorithm (ECDSA) digital signatures when using SHA-224, SHA-256, SHA-384, or SHA-512 as the hashing algorithm. This specification applies to the Internet X.509 Public Key infrastructure (PKI) when digital signatures are used to sign certificates and certificate revocation lists (CRLs). This document also identifies all four SHA2 hash algorithms for use in the Internet X.509 PKI. [STANDARDS-TRACK] | January 2010 Status: PROPOSED STANDARD Autor: Q. Dang, S. Santesson, K. Moriarty, D. Brown, T. Polk |
| RFC5759 Suite B Certificate and Certificate Revocation List (CRL) Profile This document specifies a base profile for X.509 v3 Certificates and X.509 v2 Certificate Revocation Lists (CRLs) for use with the United States National Security Agency's Suite B Cryptography. The reader is assumed to have familiarity with RFC 5280, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2010 Status: INFORMATIONAL Autor: J. Solinas, L. Zieglar |
| RFC5760 RTP Control Protocol (RTCP) Extensions for Single-Source Multicast Sessions with Unicast Feedback This document specifies an extension to the Real-time Transport Control Protocol (RTCP) to use unicast feedback to a multicast sender. The proposed extension is useful for single-source multicast sessions such as Source-Specific Multicast (SSM) communication where the traditional model of many-to-many group communication is either not available or not desired. In addition, it can be applied to any group that might benefit from a sender-controlled summarized reporting mechanism. [STANDARDS-TRACK] | February 2010 Status: PROPOSED STANDARD Autor: J. Ott, J. Chesterfield, E. Schooler |
| RFC5761 Multiplexing RTP Data and Control Packets on a Single Port This memo discusses issues that arise when multiplexing RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port. It updates RFC 3550 and RFC 3551 to describe when such multiplexing is and is not appropriate, and it explains how the Session Description Protocol (SDP) can be used to signal multiplexed sessions. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: C. Perkins, M. Westerlund |
| RFC5762 RTP and the Datagram Congestion Control Protocol (DCCP) The Real-time Transport Protocol (RTP) is a widely used transport for real-time multimedia on IP networks. The Datagram Congestion Control Protocol (DCCP) is a transport protocol that provides desirable services for real-time applications. This memo specifies a mapping of RTP onto DCCP, along with associated signalling, such that real- time applications can make use of the services provided by DCCP. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC5763 Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS) This document specifies how to use the Session Initiation Protocol (SIP) to establish a Secure Real-time Transport Protocol (SRTP) security context using the Datagram Transport Layer Security (DTLS) protocol. It describes a mechanism of transporting a fingerprint attribute in the Session Description Protocol (SDP) that identifies the key that will be presented during the DTLS handshake. The key exchange travels along the media path as opposed to the signaling path. The SIP Identity mechanism can be used to protect the integrity of the fingerprint attribute from modification by intermediate proxies. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: J. Fischl, H. Tschofenig, E. Rescorla |
| RFC5764 Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP) This document describes a Datagram Transport Layer Security (DTLS) extension to establish keys for Secure RTP (SRTP) and Secure RTP Control Protocol (SRTCP) flows. DTLS keying happens on the media path, independent of any out-of-band signalling channel present. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: D. McGrew, E. Rescorla |
| RFC5765 Security Issues and Solutions in Peer-to-Peer Systems for Realtime Communications Peer-to-peer (P2P) networks have become popular for certain applications and deployments for a variety of reasons, including fault tolerance, economics, and legal issues. It has therefore become reasonable for resource consuming and typically centralized applications like Voice over IP (VoIP) and, in general, realtime communication to adapt and exploit the benefits of P2P. Such a migration needs to address a new set of P2P-specific security problems. This document describes some of the known issues found in common P2P networks, analyzing the relevance of such issues and the applicability of existing solutions when using P2P architectures for realtime communication. This document is a product of the P2P Research Group. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: H. Schulzrinne, E. Marocco, E. Ivov |
| RFC5766 Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) If a host is located behind a NAT, then in certain situations it can be impossible for that host to communicate directly with other hosts (peers). In these situations, it is necessary for the host to use the services of an intermediate node that acts as a communication relay. This specification defines a protocol, called TURN (Traversal Using Relays around NAT), that allows the host to control the operation of the relay and to exchange packets with its peers using the relay. TURN differs from some other relay control protocols in that it allows a client to communicate with multiple peers using a single relay address. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: R. Mahy, P. Matthews, J. Rosenberg |
| RFC5767 User-Agent-Driven Privacy Mechanism for SIP This document defines a guideline for a User Agent (UA) to generate an anonymous Session Initiation Protocol (SIP) message by utilizing mechanisms such as Globally Routable User Agent URIs (GRUUs) and Traversal Using Relays around NAT (TURN) without the need for a privacy service defined in RFC 3323. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: M. Munakata, S. Schubert, T. Ohba |
| RFC5768 Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP) This specification defines a media feature tag and an option tag for use with the Session Initiation Protocol (SIP). The media feature tag allows a User Agent (UA) to communicate to its registrar that it supports ICE. The option tag allows a UA to require support for ICE in order for a call to proceed. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: J. Rosenberg |
| RFC5769 Test Vectors for Session Traversal Utilities for NAT (STUN) The Session Traversal Utilities for NAT (STUN) protocol defines several STUN attributes. The content of some of these -- FINGERPRINT, MESSAGE-INTEGRITY, and XOR-MAPPED-ADDRESS -- involve binary-logical operations (hashing, xor). This document provides test vectors for those attributes. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: R. Denis-Courmont |
| RFC5770 Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address Translators This document specifies extensions to the Host Identity Protocol (HIP) to facilitate Network Address Translator (NAT) traversal. The extensions are based on the use of the Interactive Connectivity Establishment (ICE) methodology to discover a working path between two end-hosts, and on standard techniques for encapsulating Encapsulating Security Payload (ESP) packets within the User Datagram Protocol (UDP). This document also defines elements of a procedure for NAT traversal, including the optional use of a HIP relay server. With these extensions HIP is able to work in environments that have NATs and provides a generic NAT traversal solution to higher-layer networking applications. This document defines an Experimental Protocol for the Internet community. | April 2010 Status: EXPERIMENTAL Autor: M. Komu, T. Henderson, H. Tschofenig, J. Melen, A. Keranen |
| RFC5771 IANA Guidelines for IPv4 Multicast Address Assignments This document provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes RFC 3171 and RFC 3138 and updates RFC 2780. This memo documents an Internet Best Current Practice. | March 2010 Status: BEST CURRENT PRACTICE Autor: M. Cotton, L. Vegoda, D. Meyer |
| RFC5772 A Set of Possible Requirements for a Future Routing Architecture The requirements for routing architectures described in this document were produced by two sub-groups under the IRTF Routing Research Group (RRG) in 2001, with some editorial updates up to 2006. The two sub- groups worked independently, and the resulting requirements represent two separate views of the problem and of what is required to fix the problem. This document may usefully serve as part of the recommended reading for anyone who works on routing architecture designs for the Internet in the future. | February 2010 Status: HISTORIC Autor: A. Doria, E. Davies, F. Kastenholz |
| RFC5773 Analysis of Inter-Domain Routing Requirements and History This document analyzes the state of the Internet domain-based routing system, concentrating on Inter-Domain Routing (IDR) and also considering the relationship between inter-domain and intra-domain routing. The analysis is carried out with respect to RFC 1126 and other IDR requirements and design efforts looking at the routing system as it appeared to be in 2001 with editorial additions reflecting developments up to 2006. It is the companion document to "A Set of Possible Requirements for a Future Routing Architecture" (RFC 5772), which is a discussion of requirements for the future routing architecture, addressing systems developments and future routing protocols. This document summarizes discussions held several years ago by members of the IRTF Routing Research Group (IRTF RRG) and other interested parties. The document is published with the support of the IRTF RRG as a record of the work completed at that time, but with the understanding that it does not necessarily represent either the latest technical understanding or the technical consensus of the research group at the date of publication. This document defines a Historic Document for the Internet community. | February 2010 Status: HISTORIC Autor: E. Davies, A. Doria |
| RFC5774 Considerations for Civic Addresses in the Presence Information Data Format Location Object (PIDF-LO): Guidelines and IANA Registry Definition This document provides a guideline for creating civic address considerations documents for individual countries, as required by RFC 4776. Furthermore, this document also creates an IANA Registry referring to such address considerations documents and registers such address considerations for Austria. This memo documents an Internet Best Current Practice. | March 2010 Status: BEST CURRENT PRACTICE Autor: K. Wolf, A. Mayrhofer |
| RFC5775 Asynchronous Layered Coding (ALC) Protocol Instantiation 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 document obsoletes RFC 3450. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: M. Luby, M. Watson, L. Vicisano |
| RFC5776 Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols This document details the Timed Efficient Stream \%Loss-Tolerant Authentication (TESLA) packet source authentication and packet integrity verification protocol and its integration within the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) content delivery protocols. This document only considers the authentication/integrity verification of the packets generated by the session's sender. The authentication and integrity verification of the packets sent by receivers, if any, is out of the scope of this document. This document defines an Experimental Protocol for the Internet community. | April 2010 Status: EXPERIMENTAL Autor: V. Roca, A. Francillon, S. Faurite |
| RFC5777 Traffic Classification and Quality of Service (QoS) Attributes for Diameter This document defines a number of Diameter attribute-value pairs (AVPs) for traffic classification with actions for filtering and Quality of Service (QoS) treatment. These AVPs can be used in existing and future Diameter applications where permitted by the Augmented Backus-Naur Form (ABNF) specification of the respective Diameter command extension policy. [STANDARDS-TRACK] | February 2010 Status: PROPOSED STANDARD Autor: J. Korhonen, H. Tschofenig, M. Arumaithurai, M. Jones, A. Lior |
| RFC5778 Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction Mobile IPv6 deployments may want to bootstrap their operations dynamically based on an interaction between the home agent and the Diameter server of the Mobile Service Provider. This document specifies the interaction between a Mobile IP home agent and a Diameter server. | February 2010 Status: PROPOSED STANDARD Autor: J. Korhonen, H. Tschofenig, J. Bournelle, G. Giaretta, M. Nakhjiri |
| RFC5779 Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server This specification defines Authentication, Authorization, and Accounting (AAA) interactions between Proxy Mobile IPv6 entities (both Mobile Access Gateway and Local Mobility Anchor) and a AAA server within a Proxy Mobile IPv6 Domain. These AAA interactions are primarily used to download and update mobile node specific policy profile information between Proxy Mobile IPv6 entities and a remote policy store. [STANDARDS-TRACK] | February 2010 Status: PROPOSED STANDARD Autor: J. Korhonen, J. Bournelle, K. Chowdhury, A. Muhanna, U. Meyer |
| RFC5780 NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN) This specification defines an experimental usage of the Session Traversal Utilities for NAT (STUN) Protocol that discovers the presence and current behavior of NATs and firewalls between the STUN client and the STUN server. This document defines an Experimental Protocol for the Internet community. | May 2010 Status: EXPERIMENTAL Autor: D. MacDonald, B. Lowekamp |
| RFC5781 The rsync URI Scheme This document specifies the rsync Uniform Resource Identifier (URI) scheme. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: S. Weiler, D. Ward, R. Housley |
| RFC5782 DNS Blacklists and Whitelists The rise of spam and other anti-social behavior on the Internet has led to the creation of shared blacklists and whitelists of IP addresses or domains. The DNS has become the de-facto standard method of distributing these blacklists and whitelists. This memo documents the structure and usage of DNS-based blacklists and whitelists, and the protocol used to query them. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: J. Levine |
| RFC5783 Congestion Control in the RFC Series This document is an informational snapshot taken by the IRTF\'s Internet Congestion Control Research Group (ICCRG) in October 2008. It provides a survey of congestion control topics described by documents in the RFC series. This does not modify or update the specifications or status of the RFC documents that are discussed. It may be used as a reference or starting point for the future work of the research group, especially in noting gaps or open issues in the current IETF standards. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: M. Welzl, W. Eddy |
| RFC5784 Sieve Email Filtering: Sieves and Display Directives in XML This document describes a way to represent Sieve email filtering language scripts in XML. Representing Sieves in XML is intended not as an alternate storage format for Sieve but rather as a means to facilitate manipulation of scripts using XML tools. | March 2010 Status: PROPOSED STANDARD Autor: N. Freed, S. Vedam |
| RFC5785 Defining Well-Known Uniform Resource Identifiers (URIs) This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: M. Nottingham, E. Hammer-Lahav |
| RFC5786 Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions OSPF Traffic Engineering (TE) extensions are used to advertise TE Link State Advertisements (LSAs) containing information about TE-enabled links. The only addresses belonging to a router that are advertised in TE LSAs are the local addresses corresponding to TE-enabled links, and the local address corresponding to the Router ID. | March 2010 Status: PROPOSED STANDARD Autor: R. Aggarwal, K. Kompella |
| RFC5787 OSPFv2 Routing Protocols Extensions for Automatically Switched Optical Network (ASON) Routing The ITU-T has defined an architecture and requirements for operating an Automatically Switched Optical Network (ASON). | March 2010 Status: EXPERIMENTAL Autor: D. Papadimitriou |
| RFC5788 IMAP4 Keyword Registry The aim of this document is to establish a new IANA registry for IMAP keywords and to define a procedure for keyword registration, in order to improve interoperability between different IMAP clients. [STANDARDS TRACK] | March 2010 Status: PROPOSED STANDARD Autor: A. Melnikov, D. Cridland |
| RFC5789 PATCH Method for HTTP Several applications extending the Hypertext Transfer Protocol (HTTP) require a feature to do partial resource modification. The existing HTTP PUT method only allows a complete replacement of a document. This proposal adds a new HTTP method, PATCH, to modify an existing HTTP resource. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: L. Dusseault, J. Snell |
| RFC5790 Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Version 2 (MLDv2) Protocols This document describes lightweight IGMPv3 and MLDv2 protocols (LW- IGMPv3 and LW-MLDv2), which simplify the standard (full) versions of IGMPv3 and MLDv2. The interoperability with the full versions and the previous versions of IGMP and MLD is also taken into account. [STANDARDS-TRACK] | February 2010 Status: PROPOSED STANDARD Autor: H. Liu, W. Cao, H. Asaeda |
| RFC5791 RFC 2731 ("Encoding Dublin Core Metadata in HTML") Is Obsolete This document obsoletes RFC 2731, "Encoding Dublin Core Metadata in HTML", as further development of this specification has moved to the Dublin Core Metadata Initiative (DCMI). This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2010 Status: INFORMATIONAL Autor: J. Reschke, J. Kunze |
| RFC5792 PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC) This document specifies PA-TNC, a Posture Attribute protocol identical to the Trusted Computing Group's IF-M 1.0 protocol. The document then evaluates PA-TNC against the requirements defined in the NEA Requirements specification. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: P. Sangster, K. Narayan |
| RFC5793 PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC) This document specifies PB-TNC, a Posture Broker protocol identical to the Trusted Computing Group's IF-TNCCS 2.0 protocol. The document then evaluates PB-TNC against the requirements defined in the NEA Requirements specification. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: R. Sahita, S. Hanna, R. Hurst, K. Narayan |
| RFC5794 A Description of the ARIA Encryption Algorithm This document describes the ARIA encryption algorithm. ARIA is a 128-bit block cipher with 128-, 192-, and 256-bit keys. The algorithm consists of a key scheduling part and data randomizing part. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2010 Status: INFORMATIONAL Autor: J. Lee, J. Lee, J. Kim, D. Kwon, C. Kim |
| RFC5795 The RObust Header Compression (ROHC) Framework The Robust Header Compression (ROHC) protocol provides an efficient, flexible, and future-proof header compression concept. It is designed to operate efficiently and robustly over various link technologies with different characteristics. | March 2010 Status: PROPOSED STANDARD Autor: K. Sandlund, G. Pelletier, L-E. Jonsson |
| RFC5796 Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages RFC 4601 mandates the use of IPsec to ensure authentication of the link-local messages in the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing protocol. This document specifies mechanisms to authenticate the PIM-SM link-local messages using the IP security (IPsec) Encapsulating Security Payload (ESP) or (optionally) the Authentication Header (AH). It specifies optional mechanisms to provide confidentiality using the ESP. Manual keying is specified as the mandatory and default group key management solution. To deal with issues of scalability and security that exist with manual keying, optional support for an automated group key management mechanism is provided. However, the procedures for implementing automated group key management are left to other documents. This document updates RFC 4601. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: W. Atwood, S. Islam, M. Siami |
| RFC5797 FTP Command and Extension Registry Every version of the FTP specification has added a few new commands, with the early ones summarized in RFC 959. RFC 2389 established a mechanism for specifying and negotiating FTP extensions. The number of extensions, both those supported by the mechanism and some that are not, continues to increase. An IANA registry of FTP Command and Feature names is established to reduce the likelihood of conflict of names and the consequent ambiguity. This specification establishes that registry. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: J. Klensin, A. Hoenes |
| RFC5798 Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 This memo defines the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It is version three (3) of the protocol, and it is based on VRRP (version 2) for IPv4 that is defined in RFC 3768 and in "Virtual Router Redundancy Protocol for IPv6". 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 IPv4 or IPv6 address(es) associated with a virtual router is called the Master, and it forwards packets sent to these IPv4 or IPv6 addresses. VRRP Master routers are configured with virtual IPv4 or IPv6 addresses, and VRRP Backup routers infer the address family of the virtual addresses being carried based on the transport protocol. Within a VRRP router, the virtual routers in each of the IPv4 and IPv6 address families are a domain unto themselves and do not overlap. The election process provides dynamic failover in the forwarding responsibility should the Master become unavailable. For IPv4, 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. For IPv6, the advantage gained from using VRRP for IPv6 is a quicker switchover to Backup routers than can be obtained with standard IPv6 Neighbor Discovery mechanisms. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: S. Nadas |
| RFC5801 Using Generic Security Service Application Program Interface (GSS-API) Mechanisms in Simple Authentication and Security Layer (SASL): The GS2 Mechanism Family This document describes how to use a Generic Security Service Application Program Interface (GSS-API) mechanism in the Simple Authentication and Security Layer (SASL) framework. This is done by defining a new SASL mechanism family, called GS2. This mechanism family offers a number of improvements over the previous "SASL/ GSSAPI" mechanism: it is more general, uses fewer messages for the authentication phase in some cases, and supports negotiable use of channel binding. Only GSS-API mechanisms that support channel binding and mutual authentication are supported. [STANDARDS-TRACK] | July 2010 Status: PROPOSED STANDARD Autor: S. Josefsson, N. Williams |
| RFC5802 Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms The secure authentication mechanism most widely deployed and used by Internet application protocols is the transmission of clear-text passwords over a channel protected by Transport Layer Security (TLS). There are some significant security concerns with that mechanism, which could be addressed by the use of a challenge response authentication mechanism protected by TLS. Unfortunately, the challenge response mechanisms presently on the standards track all fail to meet requirements necessary for widespread deployment, and have had success only in limited use. | July 2010 Status: PROPOSED STANDARD Autor: C. Newman, A. Menon-Sen, A. Melnikov, N. Williams |
| RFC5803 Lightweight Directory Access Protocol (LDAP) Schema for Storing Salted Challenge Response Authentication Mechanism (SCRAM) Secrets This memo describes how the "authPassword" Lightweight Directory Access Protocol (LDAP) attribute can be used for storing secrets used by the Salted Challenge Response Authentication Message (SCRAM) mechanism in the Simple Authentication and Security Layer (SASL) framework. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2010 Status: INFORMATIONAL Autor: A. Melnikov |
| RFC5804 A Protocol for Remotely Managing Sieve Scripts Sieve scripts allow users to filter incoming email. Message stores are commonly sealed servers so users cannot log into them, yet users must be able to update their scripts on them. This document describes a protocol "ManageSieve" for securely managing Sieve scripts on a remote server. This protocol allows a user to have multiple scripts, and also alerts a user to syntactically flawed scripts. [STANDARDS TRACK] | July 2010 Status: PROPOSED STANDARD Autor: A. Melnikov, T. Martin |
| RFC5805 Lightweight Directory Access Protocol (LDAP) Transactions Lightweight Directory Access Protocol (LDAP) update operations, such as Add, Delete, and Modify operations, have atomic, consistency, isolation, durability (ACID) properties. Each of these update operations act upon an entry. It is often desirable to update two or more entries in a single unit of interaction, a transaction. Transactions are necessary to support a number of applications including resource provisioning. This document extends LDAP to support transactions. This document defines an Experimental Protocol for the Internet community. | March 2010 Status: EXPERIMENTAL Autor: K. Zeilenga |
| RFC5806 Diversion Indication in SIP This RFC, which contains the text of an Internet Draft that was submitted originally to the SIP Working Group, is being published now for the historical record and to provide a reference for later Informational RFCs. The original Abstract follows. | March 2010 Status: HISTORIC Autor: S. Levy, M. Mohali |
| RFC5807 Definition of Master Key between PANA Client and Enforcement Point This document defines a master key used between a client of the Protocol for carrying Authentication for Network Access (PANA) and an enforcement point, for bootstrapping lower-layer ciphering. The master key is derived from the Master Session Key of the Extensible Authentication Protocol as a result of successful PANA authentication. The master key guarantees cryptographic independence among enforcement points bootstrapped from PANA authentication across different address families. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: Y. Ohba, A. Yegin |
| RFC5808 Requirements for a Location-by-Reference Mechanism This document defines terminology and provides requirements relating to the Location-by-Reference approach using a location Uniform Resource Identifier (URI) to handle location information within signaling and other Internet messaging. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: R. Marshall |
| RFC5810 Forwarding and Control Element Separation (ForCES) Protocol Specification This document specifies the Forwarding and Control Element Separation (ForCES) protocol. The ForCES protocol is used for communications between Control Elements (CEs) and Forwarding Elements (FEs) in a ForCES Network Element (ForCES NE). This specification is intended to meet the ForCES protocol requirements defined in RFC 3654. Besides the ForCES protocol, this specification also defines the requirements for the Transport Mapping Layer (TML). [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: A. Doria, J. Hadi Salim, R. Haas, H. Khosravi, W. Wang, L. Dong, R. Gopal, J. Halpern |
| RFC5811 SCTP-Based Transport Mapping Layer (TML) for the Forwarding and Control Element Separation (ForCES) Protocol This document defines the SCTP-based TML (Transport Mapping Layer) for the ForCES (Forwarding and Control Element Separation) protocol. It explains the rationale for choosing the SCTP (Stream Control Transmission Protocol) and also describes how this TML addresses all the requirements required by and the ForCES protocol. [STANDARDS TRACK] | March 2010 Status: PROPOSED STANDARD Autor: J. Hadi Salim, K. Ogawa |
| RFC5812 Forwarding and Control Element Separation (ForCES) Forwarding Element Model This document defines the forwarding element (FE) model used in the Forwarding and Control Element Separation (ForCES) protocol. The model represents the capabilities, state, and configuration of forwarding elements within the context of the ForCES protocol, so that control elements (CEs) can control the FEs accordingly. More specifically, the model describes the logical functions that are present in an FE, what capabilities these functions support, and how these functions are or can be interconnected. This FE model is intended to satisfy the model requirements specified in RFC 3654. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: J. Halpern, J. Hadi Salim |
| RFC5813 Forwarding and Control Element Separation (ForCES) MIB This memo defines a Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it defines managed objects for the Forwarding and Control Element Separation (ForCES) Network Element (NE). [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: R. Haas |
| RFC5814 Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS Networks Generalized Multi-Protocol Label Switching (GMPLS) is one of the most promising candidate technologies for a future data transmission network. GMPLS has been developed to control and operate different kinds of network elements, such as conventional routers, switches, Dense Wavelength Division Multiplexing (DWDM) systems, Add-Drop Multiplexers (ADMs), photonic cross-connects (PXCs), optical cross- connects (OXCs), etc. These physically diverse devices differ drastically from one another in dynamic provisioning ability. At the same time, the need for dynamically provisioned connections is increasing because optical networks are being deployed in metro areas. As different applications have varied requirements in the provisioning performance of optical networks, it is imperative to define standardized metrics and procedures such that the performance of networks and application needs can be mapped to each other. | March 2010 Status: PROPOSED STANDARD Autor: W. Sun, G. Zhang |
| RFC5815 Definitions of Managed Objects for IP Flow Information Export This document defines managed objects for IP Flow Information eXport (IPFIX). These objects provide information for monitoring IPFIX Exporters and IPFIX Collectors including the basic configuration information. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: T. Dietz, A. Kobayashi, B. Claise, G. Muenz |
| RFC5816 ESSCertIDv2 Update for RFC 3161 This document updates RFC 3161. It allows the use of ESSCertIDv2, as defined in RFC 5035, to specify the hash of a signer certificate when the hash is calculated with a function other than the Secure Hash Algorithm (SHA-1). [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: S. Santesson, N. Pope |
| RFC5817 Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks MPLS-TE Graceful Shutdown is a method for explicitly notifying the nodes in a Traffic Engineering (TE) enabled network that the TE capability on a link or on an entire Label Switching Router (LSR) is going to be disabled. MPLS-TE graceful shutdown mechanisms are tailored toward addressing planned outage in the network. | April 2010 Status: INFORMATIONAL Autor: Z. Ali, JP. Vasseur, A. Zamfir, J. Newton |
| RFC5818 Data Channel Status Confirmation Extensions for the Link Management Protocol This document defines simple additions to the Link Management Protocol (LMP) to provide a control plane tool that can assist in the location of stranded resources by allowing adjacent Label-Switching Routers (LSRs) to confirm data channel statuses and provide triggers for notifying the management plane if any discrepancies are found. As LMP is already used to verify data plane connectivity, it is considered to be an appropriate candidate to support this feature. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: D. Li, H. Xu, S. Bardalai, J. Meuric, D. Caviglia |
| RFC5819 IMAP4 Extension for Returning STATUS Information in Extended LIST Many IMAP clients display information about total number of messages / total number of unseen messages in IMAP mailboxes. In order to do that, they are forced to issue a LIST or LSUB command and to list all available mailboxes, followed by a STATUS command for each mailbox found. This document provides an extension to LIST command that allows the client to request STATUS information for mailboxes together with other information typically returned by the LIST command. [STANDARDS-TRACK] | March 2010 Status: PROPOSED STANDARD Autor: A. Melnikov, T. Sirainen |
| RFC5820 Extensions to OSPF to Support Mobile Ad Hoc Networking This document describes extensions to OSPF to support mobile ad hoc networks (MANETs). The extensions, called OSPF-OR (OSPF-Overlapping Relay), include mechanisms for link-local signaling (LLS), an OSPF-MANET interface, a simple technique to reduce the size of Hello packets by only transmitting incremental state changes, and a method for optimized flooding of routing updates. OSPF-OR also provides a means to reduce unnecessary adjacencies to support larger MANETs. [STANDARDS-TRACK] | March 2010 Status: EXPERIMENTAL Autor: A. Roy, M. Chandra |
| RFC5824 Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN Today, customers expect to run triple-play services through BGP/MPLS IP-VPNs. Some service providers will deploy services that request Quality of Service (QoS) guarantees from a local Customer Edge (CE) to a remote CE across the network. As a result, the application (e.g., voice, video, bandwidth-guaranteed data pipe, etc.) requirements for an end-to-end QoS and reserving an adequate bandwidth continue to increase. | April 2010 Status: INFORMATIONAL Autor: K. Kumaki, R. Zhang, Y. Kamite |
| RFC5825 Displaying Downgraded Messages for Email Address Internationalization This document describes a method for displaying downgraded messages that originally contained internationalized email addresses or internationalized header fields. This document defines an Experimental Protocol for the Internet community. | April 2010 Status: EXPERIMENTAL Autor: K. Fujiwara, B. Leiba |
| RFC5826 Home Automation Routing Requirements in Low-Power and Lossy Networks This document presents requirements specific to home control and automation applications for Routing Over Low power and Lossy (ROLL) networks. In the near future, many homes will contain high numbers of wireless devices for a wide set of purposes. Examples include actuators (relay, light dimmer, heating valve), sensors (wall switch, water leak, blood pressure), and advanced controllers (radio-frequency-based AV remote control, central server for light and heat control). Because such devices only cover a limited radio range, routing is often required. The aim of this document is to specify the routing requirements for networks comprising such constrained devices in a home-control and automation environment. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: A. Brandt, J. Buron, G. Porcu |
| RFC5827 Early Retransmit for TCP and Stream Control Transmission Protocol (SCTP) This document proposes a new mechanism for TCP and Stream Control Transmission Protocol (SCTP) that can be used to recover lost segments when a connection's congestion window is small. The "Early Retransmit" mechanism allows the transport to reduce, in certain special circumstances, the number of duplicate acknowledgments required to trigger a fast retransmission. This allows the transport to use fast retransmit to recover segment losses that would otherwise require a lengthy retransmission timeout. [STANDARDS-TRACK] | May 2010 Status: EXPERIMENTAL Autor: M. Allman, K. Avrachenkov, U. Ayesta, J. Blanton, P. Hurtig |
| RFC5828 Generalized Multiprotocol Label Switching (GMPLS) Ethernet Label Switching Architecture and Framework There has been significant recent work in increasing the capabilities of Ethernet switches and Ethernet forwarding models. As a consequence, the role of Ethernet is rapidly expanding into "transport networks" that previously were the domain of other technologies such as Synchronous Optical Network (SONET) / Synchronous Digital Hierarchy (SDH), Time-Division Multiplexing (TDM), and Asynchronous Transfer Mode (ATM). This document defines an architecture and framework for a Generalized- MPLS-based control plane for Ethernet in this "transport network" capacity. GMPLS has already been specified for similar technologies. Some additional extensions to the GMPLS control plane are needed, and this document provides a framework for these extensions. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2010 Status: INFORMATIONAL Autor: D. Fedyk, L. Berger, L. Andersson |
| RFC5829 Link Relation Types for Simple Version Navigation between Web Resources This specification defines a set of link relation types that may be used on Web resources for navigation between a resource and other resources related to version control, such as past versions and working copies. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: A. Brown, G. Clemm, J. Reschke |
| RFC5830 GOST 28147-89: Encryption, Decryption, and Message Authentication Code (MAC) Algorithms This document is intended to be a source of information about the Russian Federal standard for electronic encryption, decryption, and message authentication algorithms (GOST 28147-89), which is one of the Russian cryptographic standard algorithms called GOST algorithms). Recently, Russian cryptography is being used in Internet applications, and this document has been created as information for developers and users of GOST 28147-89 for encryption, decryption, and message authentication. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2010 Status: INFORMATIONAL Autor: V. Dolmatov |
| RFC5831 GOST R 34.11-94: Hash Function Algorithm This document is intended to be a source of information about the Russian Federal standard hash function (GOST R 34.11-94), which is one of the Russian cryptographic standard algorithms (called GOST algorithms). Recently, Russian cryptography is being used in Internet applications, and this document has been created as information for developers and users of GOST R 34.11-94 for hash computation. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2010 Status: INFORMATIONAL Autor: V. Dolmatov |
| RFC5832 GOST R 34.10-2001: Digital Signature Algorithm This document is intended to be a source of information about the Russian Federal standard for digital signatures (GOST R 34.10-2001), which is one of the Russian cryptographic standard algorithms (called GOST algorithms). Recently, Russian cryptography is being used in Internet applications, and this document has been created as information for developers and users of GOST R 34.10-2001 for digital signature generation and verification. | March 2010 Status: INFORMATIONAL Autor: V. Dolmatov |
| RFC5833 Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Base MIB This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it describes the managed objects for modeling the Control And Provisioning of Wireless Access Points (CAPWAP) Protocol. This MIB module is presented as a basis for future work on the SNMP management of the CAPWAP protocol. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: Y. Shi, D. Perkins, C. Elliott, Y. Zhang |
| RFC5834 Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding MIB for IEEE 802.11 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it describes managed objects for modeling the Control And Provisioning of Wireless Access Points (CAPWAP) protocol for IEEE 802.11 wireless binding. This MIB module is presented as a basis for future work on the management of the CAPWAP protocol using the Simple Network Management Protocol (SNMP). This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: Y. Shi, D. Perkins, C. Elliott, Y. Zhang |
| RFC5835 Framework for Metric Composition This memo describes a detailed framework for composing and aggregating metrics (both in time and in space) originally defined by the IP Performance Metrics (IPPM), RFC 2330, and developed by the IETF. This new framework memo describes the generic composition and aggregation mechanisms. The memo provides a basis for additional documents that implement the framework to define detailed compositions and aggregations of metrics that are useful in practice. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: A. Morton, S. Van den Berghe |
| RFC5836 Extensible Authentication Protocol (EAP) Early Authentication Problem Statement Extensible Authentication Protocol (EAP) early authentication may be defined as the use of EAP by a mobile device to establish authenticated keying material on a target attachment point prior to its arrival. This document discusses the EAP early authentication problem in detail. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: Y. Ohba, Q. Wu, G. Zorn |
| RFC5837 Extending ICMP for Interface and Next-Hop Identification This memo defines a data structure that can be appended to selected ICMP messages. The ICMP extension defined herein can be used to identify any combination of the following: the IP interface upon which a datagram arrived, the sub-IP component of an IP interface upon which a datagram arrived, the IP interface through which the datagram would have been forwarded had it been forwardable, and the IP next hop to which the datagram would have been forwarded. | April 2010 Status: PROPOSED STANDARD Autor: A. Atlas, R. Bonica, C. Pignataro, N. Shen, JR. Rivers |
| RFC5838 Support of Address Families in OSPFv3 This document describes a mechanism for supporting multiple address families (AFs) in OSPFv3 using multiple instances. It maps an AF to an OSPFv3 instance using the Instance ID field in the OSPFv3 packet header. This approach is fairly simple and minimizes extensions to OSPFv3 for supporting multiple AFs. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: A. Lindem, S. Mirtorabi, A. Roy, M. Barnes, R. Aggarwal |
| RFC5839 An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification The Session Initiation Protocol (SIP) events framework enables receiving asynchronous notification of various events from other SIP user agents. This framework defines the procedures for creating, refreshing, and terminating subscriptions, as well as fetching and periodic polling of resource state. These procedures provide no tools to avoid replaying event notifications that have already been received by a user agent. This memo defines an extension to SIP events that allows the subscriber to condition the subscription request to whether the state has changed since the previous notification was received. When such a condition is true, either the body of a resulting event notification or the entire notification message is suppressed. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: A. Niemi, D. Willis |
| RFC5840 Wrapped Encapsulating Security Payload (ESP) for Traffic Visibility This document describes the Wrapped Encapsulating Security Payload (WESP) protocol, which builds on the Encapsulating Security Payload (ESP) RFC 4303 and is designed to allow intermediate devices to (1) ascertain if data confidentiality is being employed within ESP, and if not, (2) inspect the IPsec packets for network monitoring and access control functions. Currently, in the IPsec ESP standard, there is no deterministic way to differentiate between encrypted and unencrypted payloads by simply examining a packet. This poses certain challenges to the intermediate devices that need to deep inspect the packet before making a decision on what should be done with that packet (Inspect and/or Allow/Drop). The mechanism described in this document can be used to easily disambiguate integrity-only ESP from ESP-encrypted packets, without compromising on the security provided by ESP. [STANDARDS-TRACK] | April 2010 Status: PROPOSED STANDARD Autor: K. Grewal, G. Montenegro, M. Bhatia |
| RFC5841 TCP Option to Denote Packet Mood This document proposes a new TCP option to denote packet mood. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: R. Hay, W. Turkal |
| RFC5842 Binding Extensions to Web Distributed Authoring and Versioning (WebDAV) This specification defines bindings, and the BIND method for creating multiple bindings to the same resource. Creating a new binding to a resource causes at least one new URI to be mapped to that resource. Servers are required to ensure the integrity of any bindings that they allow to be created. This document defines an Experimental Protocol for the Internet community. | April 2010 Status: EXPERIMENTAL Autor: G. Clemm, J. Crawford, J. Reschke, J. Whitehead |
| RFC5843 Additional Hash Algorithms for HTTP Instance Digests The IANA registry named "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" defines values for digest algorithms used by Instance Digests in HTTP. Instance Digests in HTTP provide a digest, also known as a checksum or hash, of an entire representation of the current state of a resource. This document adds new values to the registry and updates previous values. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: A. Bryan |
| RFC5844 IPv4 Support for Proxy Mobile IPv6 This document specifies extensions to the Proxy Mobile IPv6 protocol for adding IPv4 protocol support. The scope of IPv4 protocol support is two-fold: 1) enable IPv4 home address mobility support to the mobile node, and 2) allow the mobility entities in the Proxy Mobile IPv6 domain to exchange signaling messages over an IPv4 transport network. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: R. Wakikawa, S. Gundavelli |
| RFC5845 Generic Routing Encapsulation (GRE) Key Option for Proxy Mobile IPv6 This specification defines a new mobility option for allowing the mobile access gateway and the local mobility anchor to negotiate Generic Routing Encapsulation (GRE) encapsulation mode and exchange the downlink and uplink GRE keys that are used for marking the downlink and uplink traffic that belong to a specific mobility session. In addition, the same mobility option can be used to negotiate the GRE encapsulation mode without exchanging the GRE keys. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: A. Muhanna, M. Khalil, S. Gundavelli, K. Leung |
| RFC5846 Binding Revocation for IPv6 Mobility This document defines a binding revocation mechanism to terminate a mobile node's mobility session and the associated resources. This mechanism can be used both with base Mobile IPv6 and its extensions, such as Proxy Mobile IPv6. The mechanism allows the mobility entity which initiates the revocation procedure to request its peer to terminate either one, multiple or all specified Binding Cache entries. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: A. Muhanna, M. Khalil, S. Gundavelli, K. Chowdhury, P. Yegani |
| RFC5847 Heartbeat Mechanism for Proxy Mobile IPv6 Proxy Mobile IPv6 (PMIPv6) is a network-based mobility management protocol. The mobility entities involved in the Proxy Mobile IPv6 protocol, the mobile access gateway (MAG) and the local mobility anchor (LMA), set up tunnels dynamically to manage mobility for a mobile node within the Proxy Mobile IPv6 domain. This document describes a heartbeat mechanism between the MAG and the LMA to detect failures, quickly inform peers in the event of a recovery from node failures, and allow a peer to take appropriate action. [STANDARDS TRACK] | June 2010 Status: PROPOSED STANDARD Autor: V. Devarapalli, R. Koodli, H. Lim, N. Kant, S. Krishnan, J. Laganier |
| RFC5848 Signed Syslog Messages This document describes a mechanism to add origin authentication, message integrity, replay resistance, message sequencing, and detection of missing messages to the transmitted syslog messages. This specification is intended to be used in conjunction with the work defined in RFC 5424, "The Syslog Protocol". [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: J. Kelsey, J. Callas, A. Clemm |
| RFC5849 The OAuth 1.0 Protocol OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: E. Hammer-Lahav |
| RFC5850 A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol (SIP) This document defines a framework and the requirements for call control and multi-party usage of the Session Initiation Protocol (SIP). To enable discussion of multi-party features and applications, we define an abstract call model for describing the media relationships required by many of these. The model and actions described here are specifically chosen to be independent of the SIP signaling and/or mixing approach chosen to actually set up the media relationships. In addition to its dialog manipulation aspect, this framework includes requirements for communicating related information and events such as conference and session state and session history. This framework also describes other goals that embody the spirit of SIP applications as used on the Internet such as the definition of primitives (not services), invoker and participant oriented primitives, signaling and mixing model independence, and others. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: R. Mahy, R. Sparks, J. Rosenberg, D. Petrie, A. Johnston |
| RFC5851 Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks The purpose of this document is to define a framework for an Access Node Control Mechanism between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in a multi-service reference architecture in order to perform operations related to service, quality of service, and subscribers. The Access Node Control Mechanism will ensure that the transmission of the information does not need to go through distinct element managers but rather uses a direct device-device communication. This allows for performing access-link-related operations within those network elements, while avoiding impact on the existing Operational Support Systems. | May 2010 Status: INFORMATIONAL Autor: S. Ooghe, N. Voigt, M. Platnic, T. Haag, S. Wadhwa |
| RFC5852 RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport Network In a transport network scenario, Data Plane connections controlled by either a Generalized Multiprotocol Label Switching (GMPLS) Control Plane (Soft Permanent Connections - SPC) or a Management System (Permanent Connections - PC) may independently coexist. The ability of transforming an existing PC into an SPC and vice versa -- without actually affecting Data Plane traffic being carried over it -- is a requirement. The requirements for the conversion between permanent connections and switched connections in a GMPLS Network are defined in RFC 5493. | April 2010 Status: PROPOSED STANDARD Autor: D. Caviglia, D. Ceccarelli, D. Bramanti, D. Li, S. Bardalai |
| RFC5853 Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments This document describes functions implemented in Session Initiation Protocol (SIP) intermediaries known as Session Border Controllers (SBCs). The goal of this document is to describe the commonly provided functions of SBCs. A special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. This document also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or if additional standards work is required. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: J. Hautakorpi, G. Camarillo, R. Penfield, A. Hawrylyshen, M. Bhatia |
| RFC5854 The Metalink Download Description Format This document specifies Metalink, an XML-based download description format. Metalink describes download locations (mirrors), cryptographic hashes, and other information. Clients can transparently use this information to reliably transfer files. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: A. Bryan, T. Tsujikawa, N. McNab, P. Poeml |
| RFC5855 Nameservers for IPv4 and IPv6 Reverse Zones This document specifies a stable naming scheme for the nameservers that serve the zones IN-ADDR.ARPA and IP6.ARPA in the DNS. These zones contain data that facilitate reverse mapping (address to name). This memo documents an Internet Best Current Practice. | May 2010 Status: BEST CURRENT PRACTICE Autor: J. Abley, T. Manderson |
| RFC5856 Integration of Robust Header Compression over IPsec Security Associations IP Security (IPsec) provides various security services for IP traffic. However, the benefits of IPsec come at the cost of increased overhead. This document outlines a framework for integrating Robust Header Compression (ROHC) over IPsec (ROHCoIPsec). By compressing the inner headers of IP packets, ROHCoIPsec proposes to reduce the amount of overhead associated with the transmission of traffic over IPsec Security Associations (SAs). This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: E. Ertekin, R. Jasani, C. Christou, C. Bormann |
| RFC5857 IKEv2 Extensions to Support Robust Header Compression over IPsec In order to integrate Robust Header Compression (ROHC) with IPsec, a mechanism is needed to signal ROHC channel parameters between endpoints. Internet Key Exchange (IKE) is a mechanism that can be leveraged to exchange these parameters. This document specifies extensions to IKEv2 that will allow ROHC and its associated channel parameters to be signaled for IPsec Security Associations (SAs). [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: E. Ertekin, C. Christou, R. Jasani, T. Kivinen, C. Bormann |
| RFC5858 IPsec Extensions to Support Robust Header Compression over IPsec Integrating Robust Header Compression (ROHC) with IPsec (ROHCoIPsec) offers the combined benefits of IP security services and efficient bandwidth utilization. However, in order to integrate ROHC with IPsec, extensions to the Security Policy Database (SPD) and Security Association Database (SAD) are required. This document describes the IPsec extensions required to support ROHCoIPsec. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: E. Ertekin, C. Christou, C. Bormann |
| RFC5859 TFTP Server Address Option for DHCPv4 This memo documents existing usage for the "TFTP Server Address" option. The option number currently in use is 150. This memo documents the current usage of the option in agreement with RFC 3942, which declares that any pre-existing usages of option numbers in the range 128-223 should be documented, and the Dynamic Host Configuration working group will try to officially assign those numbers to those options. The option is defined for DHCPv4 and works only with IPv4 addresses. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: R. Johnson |
| RFC5860 Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks This document lists architectural and functional requirements for the Operations, Administration, and Maintenance of MPLS Transport Profile. These requirements apply to pseudowires, Label Switched Paths, and Sections. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: M. Vigoureux, D. Ward, M. Betts |
| RFC5861 HTTP Cache-Control Extensions for Stale Content This document defines two independent HTTP Cache-Control extensions that allow control over the use of stale responses by caches. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: M. Nottingham |
| RFC5862 Path Computation Clients (PCC) - Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TE The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. | June 2010 Status: INFORMATIONAL Autor: S. Yasukawa, A. Farrel |
| RFC5863 DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations DomainKeys Identified Mail (DKIM) allows an organization to claim responsibility for transmitting a message, in a way that can be validated by a recipient. The organization can be the author's, the originating sending site, an intermediary, or one of their agents. A message can contain multiple signatures, from the same or different organizations involved with the message. DKIM defines a domain-level digital signature authentication framework for email, using public key cryptography and using the domain name service as its key server technology. This permits verification of a responsible organization, as well as the integrity of the message content. DKIM will also provide a mechanism that permits potential email signers to publish information about their email signing practices; this will permit email receivers to make additional assessments about messages. DKIM's authentication of email identity can assist in the global control of "spam" and "phishing". This document provides implementation, deployment, operational, and migration considerations for DKIM. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: T. Hansen, E. Siegel, P. Hallam-Baker, D. Crocker |
| RFC5864 DNS SRV Resource Records for AFS This document specifies how to use DNS (Domain Name Service) SRV RRs (Resource Records) to locate services for the AFS distributed file system and how the priority and weight values of the SRV RR should be interpreted in the server ranking system used by AFS. It updates RFC 1183 to deprecate the use of the AFSDB RR to locate AFS cell database servers and provides guidance for backward compatibility. [STANDARDS TRACK] | April 2010 Status: PROPOSED STANDARD Autor: R. Allbery |
| RFC5865 A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic This document requests one Differentiated Services Code Point (DSCP) from the Internet Assigned Numbers Authority (IANA) for a class of real-time traffic. This traffic class conforms to the Expedited Forwarding Per-Hop Behavior. This traffic is also admitted by the network using a Call Admission Control (CAC) procedure involving authentication, authorization, and capacity admission. This differs from a real-time traffic class that conforms to the Expedited Forwarding Per-Hop Behavior but is not subject to capacity admission or subject to very coarse capacity admission. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: F. Baker, J. Polk, M. Dolly |
| RFC5866 Diameter Quality-of-Service Application This document describes the framework, messages, and procedures for the Diameter Quality-of-Service (QoS) application. The Diameter QoS application allows network elements to interact with Diameter servers when allocating QoS resources in the network. In particular, two modes of operation, namely "Pull" and "Push", are defined. [STANDARDS TRACK] | May 2010 Status: PROPOSED STANDARD Autor: D. Sun, P. McCann, H. Tschofenig, T. Tsou, A. Doria, G. Zorn |
| RFC5867 Building Automation Routing Requirements in Low-Power and Lossy Networks The Routing Over Low-Power and Lossy (ROLL) networks Working Group has been chartered to work on routing solutions for Low-Power and Lossy Networks (LLNs) in various markets: industrial, commercial (building), home, and urban networks. Pursuant to this effort, this document defines the IPv6 routing requirements for building automation. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: J. Martocci, P. De Mil, N. Riou, W. Vermeylen |
| RFC5868 Problem Statement on the Cross-Realm Operation of Kerberos This document provides background information regarding large-scale Kerberos deployments in the industrial sector, with the aim of identifying issues in the current Kerberos cross-realm authentication model as defined in RFC 4120. | May 2010 Status: INFORMATIONAL Autor: S. Sakane, K. Kamada, S. Zrelli, M. Ishiyama |
| RFC5869 HMAC-based Extract-and-Expand Key Derivation Function (HKDF) This document specifies a simple Hashed Message Authentication Code (HMAC)-based key derivation function (HKDF), which can be used as a building block in various protocols and applications. The key derivation function (KDF) is intended to support a wide range of applications and requirements, and is conservative in its use of cryptographic hash functions. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: H. Krawczyk, P. Eronen |
| RFC5870 A Uniform Resource Identifier for Geographic Locations ('geo' URI) This document specifies a Uniform Resource Identifier (URI) for geographic locations using the 'geo\' scheme name. A 'geo' URI identifies a physical location in a two- or three-dimensional coordinate reference system in a compact, simple, human-readable, and protocol-independent way. The default coordinate reference system used is the World Geodetic System 1984 (WGS-84). [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: A. Mayrhofer, C. Spanring |
| RFC5871 IANA Allocation Guidelines for the IPv6 Routing Header This document specifies the IANA guidelines for allocating new values for the Routing Type field in the IPv6 Routing Header. [STANDARDS TRACK] | May 2010 Status: PROPOSED STANDARD Autor: J. Arkko, S. Bradner |
| RFC5872 IANA Rules for the Protocol for Carrying Authentication for Network Access (PANA) This document relaxes the IANA rules for the Protocol for Carrying Authentication for Network Access (PANA). [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: J. Arkko, A. Yegin |
| RFC5873 Pre-Authentication Support for the Protocol for Carrying Authentication for Network Access (PANA) This document defines an extension to the Protocol for Carrying Authentication for Network Access (PANA) for proactively establishing a PANA Security Association between a PANA Client in one access network and a PANA Authentication Agent in another access network to which the PANA Client may move. This document defines an Experimental Protocol for the Internet community. | May 2010 Status: EXPERIMENTAL Autor: Y. Ohba, A. Yegin |
| RFC5874 An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources This specification defines a document format that can be used to indicate that a change has occurred in a document managed by the Extensible Markup Language (XML) Configuration Access Protocol (XCAP). This format reports which document has changed and its former and new entity tags. It can report the differences between versions of the document, using an XML patch format. It can report existing element and attribute content when versions of an XCAP server document change. XCAP diff documents can be delivered to diff clients using a number of means, including a Session Initiation Protocol (SIP) event package. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: J. Rosenberg, J. Urpalainen |
| RFC5875 An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package This document describes an "xcap-diff" SIP (Session Initiation Protocol) event package for the SIP Event Notification Framework, which clients can use to receive notifications of changes to Extensible Markup Language (XML) Configuration Access Protocol (XCAP) resources. The initial synchronization information exchange and document updates are based on the XCAP Diff format. [STANDARDS TRACK] | May 2010 Status: PROPOSED STANDARD Autor: J. Urpalainen, D. Willis |
| RFC5876 Updates to Asserted Identity in the Session Initiation Protocol (SIP) The Session Initiation Protocol (SIP) has a mechanism for conveying the identity of the originator of a request by means of the P-Asserted-Identity and P-Preferred-Identity header fields. These header fields are specified for use in requests using a number of SIP methods, in particular the INVITE method. However, RFC 3325 does not specify the insertion of the P-Asserted-Identity header field by a trusted User Agent Client (UAC), does not specify the use of P-Asserted-Identity and P-Preferred-Identity header fields with certain SIP methods such as UPDATE, REGISTER, MESSAGE, and PUBLISH, and does not specify how to handle an unexpected number of URIs or unexpected URI schemes in these header fields. This document extends RFC 3325 to cover these situations. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2010 Status: INFORMATIONAL Autor: J. Elwell |
| RFC5877 The application/pkix-attr-cert Media Type for Attribute Certificates This document specifies a MIME media type used to carry a single attribute certificate as defined in RFC 5755. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: R. Housley |
| RFC5878 Transport Layer Security (TLS) Authorization Extensions This document specifies authorization extensions to the Transport Layer Security (TLS) Handshake Protocol. Extensions are carried in the client and server hello messages to confirm that both parties support the desired authorization data types. Then, if supported by both the client and the server, authorization information, such as attribute certificates (ACs) or Security Assertion Markup Language (SAML) assertions, is exchanged in the supplemental data handshake message. This document defines an Experimental Protocol for the Internet community. | May 2010 Status: EXPERIMENTAL Autor: M. Brown, R. Housley |
| RFC5879 Heuristics for Detecting ESP-NULL Packets This document describes a set of heuristics for distinguishing IPsec ESP-NULL (Encapsulating Security Payload without encryption) packets from encrypted ESP packets. These heuristics can be used on intermediate devices, like traffic analyzers, and deep-inspection engines, to quickly decide whether or not a given packet flow is encrypted, i.e., whether or not it can be inspected. Use of these heuristics does not require any changes made on existing IPsec hosts that are compliant with RFC 4303. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: T. Kivinen, D. McDonald |
| RFC5880 Bidirectional Forwarding Detection (BFD) This document describes a protocol intended to detect faults in the bidirectional path between two forwarding engines, including interfaces, data link(s), and to the extent possible the forwarding engines themselves, with potentially very low latency. It operates independently of media, data protocols, and routing protocols. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: D. Katz, D. Ward |
| RFC5881 Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop) This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol over IPv4 and IPv6 for single IP hops. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: D. Katz, D. Ward |
| RFC5882 Generic Application of Bidirectional Forwarding Detection (BFD) This document describes the generic application of the Bidirectional Forwarding Detection (BFD) protocol. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: D. Katz, D. Ward |
| RFC5883 Bidirectional Forwarding Detection (BFD) for Multihop Paths This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol over multihop paths, including unidirectional links. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: D. Katz, D. Ward |
| RFC5884 Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs) One desirable application of Bidirectional Forwarding Detection (BFD) is to detect a Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) data plane failure. LSP Ping is an existing mechanism for detecting MPLS data plane failures and for verifying the MPLS LSP data plane against the control plane. BFD can be used for the former, but not for the latter. However, the control plane processing required for BFD Control packets is relatively smaller than the processing required for LSP Ping messages. A combination of LSP Ping and BFD can be used to provide faster data plane failure detection and/or make it possible to provide such detection on a greater number of LSPs. This document describes the applicability of BFD in relation to LSP Ping for this application. It also describes procedures for using BFD in this environment. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: R. Aggarwal, K. Kompella, T. Nadeau, G. Swallow |
| RFC5885 Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV) This document describes Connectivity Verification (CV) Types using Bidirectional Forwarding Detection (BFD) with Virtual Circuit Connectivity Verification (VCCV). VCCV provides a control channel that is associated with a pseudowire (PW), as well as the corresponding operations and management functions such as connectivity verification to be used over that control channel. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: T. Nadeau, C. Pignataro |
| RFC5886 A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture A Path Computation Element (PCE)-based architecture has been specified for the computation of Traffic Engineering (TE) Label Switched Paths (LSPs) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks in the context of single or multiple domains (where a domain refers to a collection of network elements within a common sphere of address management or path computational responsibility such as Interior Gateway Protocol (IGP) areas and Autonomous Systems). Path Computation Clients (PCCs) send computation requests to PCEs, and these may forward the requests to and cooperate with other PCEs forming a "path computation chain". | June 2010 Status: PROPOSED STANDARD Autor: JP. Vasseur, JL. Le Roux, Y. Ikejiri |
| RFC5887 Renumbering Still Needs Work This document reviews the existing mechanisms for site renumbering for both IPv4 and IPv6, and it identifies operational issues with those mechanisms. It also summarises current technical proposals for additional mechanisms. Finally, there is a gap analysis identifying possible areas for future work. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2010 Status: INFORMATIONAL Autor: B. Carpenter, R. Atkinson, H. Flinck |
| RFC5888 The Session Description Protocol (SDP) Grouping Framework In this specification, we define a framework to group "m" lines in the Session Description Protocol (SDP) for different purposes. This framework uses the "group" and "mid" SDP attributes, both of which are defined in this specification. Additionally, we specify how to use the framework for two different purposes: for lip synchronization and for receiving a media flow consisting of several media streams on different transport addresses. This document obsoletes RFC 3388. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: G. Camarillo, H. Schulzrinne |
| RFC5889 IP Addressing Model in Ad Hoc Networks This document describes a model for configuring IP addresses and subnet prefixes on the interfaces of routers which connect to links with undetermined connectivity properties. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2010 Status: INFORMATIONAL Autor: E. Baccelli, M. Townsley |
| RFC5890 Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework This document is one of a collection that, together, describe the protocol and usage context for a revision of Internationalized Domain Names for Applications (IDNA), superseding the earlier version. It describes the document collection and provides definitions and other material that are common to the set. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: J. Klensin |
| RFC5891 Internationalized Domain Names in Applications (IDNA): Protocol This document is the revised protocol definition for Internationalized Domain Names (IDNs). The rationale for changes, the relationship to the older specification, and important terminology are provided in other documents. This document specifies the protocol mechanism, called Internationalized Domain Names in Applications (IDNA), for registering and looking up IDNs in a way that does not require changes to the DNS itself. IDNA is only meant for processing domain names, not free text. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: J. Klensin |
| RFC5892 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). | August 2010 Status: PROPOSED STANDARD Autor: P. Faltstrom |
| RFC5893 Right-to-Left Scripts for Internationalized Domain Names for Applications (IDNA) The use of right-to-left scripts in Internationalized Domain Names (IDNs) has presented several challenges. This memo provides a new Bidi rule for Internationalized Domain Names for Applications (IDNA) labels, based on the encountered problems with some scripts and some shortcomings in the 2003 IDNA Bidi criterion. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: H. Alvestrand, C. Karp |
| RFC5894 Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale Several years have passed since the original protocol for Internationalized Domain Names (IDNs) was completed and deployed. During that time, a number of issues have arisen, including the need to update the system to deal with newer versions of Unicode. Some of these issues require tuning of the existing protocols and the tables on which they depend. This document provides an overview of a revised system and provides explanatory material for its components. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: J. Klensin |
| RFC5895 Mapping Characters for Internationalized Domain Names in Applications (IDNA) 2008 In the original version of the Internationalized Domain Names in Applications (IDNA) protocol, any Unicode code points taken from user input were mapped into a set of Unicode code points that "made sense", and then encoded and passed to the domain name system (DNS). The IDNA2008 protocol (described in RFCs 5890, 5891, 5892, and 5893) presumes that the input to the protocol comes from a set of "permitted" code points, which it then encodes and passes to the DNS, but does not specify what to do with the result of user input. This document describes the actions that can be taken by an implementation between receiving user input and passing permitted code points to the new IDNA protocol. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2010 Status: INFORMATIONAL Autor: P. Resnick, P. Hoffman |
| RFC5896 Generic Security Service Application Program Interface (GSS-API): Delegate if Approved by Policy Several Generic Security Service Application Program Interface (GSS-API) applications work in a multi-tiered architecture, where the server takes advantage of delegated user credentials to act on behalf of the user and contact additional servers. In effect, the server acts as an agent on behalf of the user. Examples include web applications that need to access e-mail or file servers, including CIFS (Common Internet File System) file servers. However, delegating the user credentials to a party who is not sufficiently trusted is problematic from a security standpoint. Kerberos provides a flag called OK-AS-DELEGATE that allows the administrator of a Kerberos realm to communicate that a particular service is trusted for delegation. This specification adds support for this flag and similar facilities in other authentication mechanisms to GSS-API (RFC 2743). [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: L. Hornquist Astrand, S. Hartman |
| RFC5897 Identification of Communications Services in the Session Initiation Protocol (SIP) This document considers the problem of service identification in the Session Initiation Protocol (SIP). Service identification is the process of determining the user-level use case that is driving the signaling being utilized by the user agent (UA). This document discusses the uses of service identification, and outlines several architectural principles behind the process. It identifies perils when service identification is not done properly -- including fraud, interoperability failures, and stifling of innovation. It then outlines a set of recommended practices for service identification. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: J. Rosenberg |
| RFC5898 Connectivity Preconditions for Session Description Protocol (SDP) Media Streams This document defines a new connectivity precondition for the Session Description Protocol (SDP) precondition framework. A connectivity precondition can be used to delay session establishment or modification until media stream connectivity has been successfully verified. The method of verification may vary depending on the type of transport used for the media. For unreliable datagram transports such as UDP, verification involves probing the stream with data or control packets. For reliable connection-oriented transports such as TCP, verification can be achieved simply by successful connection establishment or by probing the connection with data or control packets, depending on the situation. [STANDARDS-TRACK] | July 2010 Status: PROPOSED STANDARD Autor: F. Andreasen, G. Camarillo, D. Oran, D. Wing |
| RFC5901 Extensions to the IODEF-Document Class for Reporting Phishing This document extends the Incident Object Description Exchange Format (IODEF) defined in RFC 5070 to support the reporting of phishing events, which is a particular type of fraud. These extensions are flexible enough to support information gleaned from activities throughout the entire electronic fraud cycle -- from receipt of the phishing lure to the disablement of the collection site. Both simple reporting and complete forensic reporting are possible, as is consolidating multiple incidents. [STANDARDS-TRACK] | July 2010 Status: PROPOSED STANDARD Autor: P. Cain, D. Jevans |
| RFC5902 IAB Thoughts on IPv6 Network Address Translation There has been much recent discussion on the topic of whether the IETF should develop standards for IPv6 Network Address Translators (NATs). This document articulates the architectural issues raised by IPv6 NATs, the pros and cons of having IPv6 NATs, and provides the IAB's thoughts on the current open issues and the solution space. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2010 Status: INFORMATIONAL Autor: D. Thaler, L. Zhang, G. Lebovitz |
| RFC5903 Elliptic Curve Groups modulo a Prime (ECP Groups) for IKE and IKEv2 This document describes three Elliptic Curve Cryptography (ECC) groups for use in the Internet Key Exchange (IKE) and Internet Key Exchange version 2 (IKEv2) protocols in addition to previously defined groups. These groups are based on modular arithmetic rather than binary arithmetic. These groups are defined to align IKE and IKEv2 with other ECC implementations and standards, particularly NIST standards. In addition, the curves defined here can provide more efficient implementation than previously defined ECC groups. This document obsoletes RFC 4753. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: D. Fu, J. Solinas |
| RFC5904 RADIUS Attributes for IEEE 802.16 Privacy Key Management Version 1 (PKMv1) Protocol Support This document defines a set of Remote Authentication Dial-In User Service (RADIUS) Attributes that are designed to provide RADIUS support for IEEE 802.16 Privacy Key Management Version 1. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: G. Zorn |
| RFC5905 Network Time Protocol Version 4: Protocol and Algorithms Specification The Network Time Protocol (NTP) is widely used to synchronize computer clocks in the Internet. This document describes NTP version 4 (NTPv4), which is backwards compatible with NTP version 3 (NTPv3), described in RFC 1305, as well as previous versions of the protocol. NTPv4 includes a modified protocol header to accommodate the Internet Protocol version 6 address family. NTPv4 includes fundamental improvements in the mitigation and discipline algorithms that extend the potential accuracy to the tens of microseconds with modern workstations and fast LANs. It includes a dynamic server discovery scheme, so that in many cases, specific server configuration is not required. It corrects certain errors in the NTPv3 design and implementation and includes an optional extension mechanism. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: D. Mills, J. Martin, J. Burbank, W. Kasch |
| RFC5906 Network Time Protocol Version 4: Autokey Specification This memo describes the Autokey security model for authenticating servers to clients using the Network Time Protocol (NTP) and public key cryptography. Its design is based on the premise that IPsec schemes cannot be adopted intact, since that would preclude stateless servers and severely compromise timekeeping accuracy. In addition, Public Key Infrastructure (PKI) schemes presume authenticated time values are always available to enforce certificate lifetimes; however, cryptographically verified timestamps require interaction between the timekeeping and authentication functions. | June 2010 Status: INFORMATIONAL Autor: B. Haberman, D. Mills |
| RFC5907 Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) The Network Time Protocol (NTP) is used in networks of all types and sizes for time synchronization of servers, workstations, and other networked equipment. As time synchronization is more and more a mission-critical service, standardized means for monitoring and management of this subsystem of a networked host are required to allow operators of such a service to set up a monitoring system that is platform- and vendor-independent. This document provides a standardized collection of data objects for monitoring the NTP entity of such a network participant and it is part of the NTP version 4 standardization effort. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: H. Gerstung, C. Elliott, B. Haberman |
| RFC5908 Network Time Protocol (NTP) Server Option for DHCPv6 The NTP Server Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides NTPv4 (Network Time Protocol version 4) server location information to DHCPv6 hosts. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: R. Gayraud, B. Lourdelet |
| RFC5909 Securing Neighbor Discovery Proxy: Problem Statement Neighbor Discovery Proxies are used to provide an address presence on a link for nodes that are no longer present on the link. They allow a node to receive packets directed at its address by allowing another device to perform Neighbor Discovery operations on its behalf. | July 2010 Status: INFORMATIONAL Autor: J-M. Combes, S. Krishnan, G. Daley |
| RFC5910 Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP) This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of Domain Name System security (DNSSEC) extensions for domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of DNS security extensions. This document obsoletes RFC 4310. [STANDARDS-TRACK] | May 2010 Status: PROPOSED STANDARD Autor: J. Gould, S. Hollenbeck |
| RFC5911 New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME The Cryptographic Message Syntax (CMS) format, and many associated formats, are expressed using ASN.1. The current ASN.1 modules conform to the 1988 version of ASN.1. This document updates those ASN.1 modules to conform to the 2002 version of ASN.1. There are no bits-on-the-wire changes to any of the formats; this is simply a change to the syntax. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: P. Hoffman, J. Schaad |
| RFC5912 New ASN.1 Modules for the Public Key Infrastructure Using X.509 (PKIX) The Public Key Infrastructure using X.509 (PKIX) certificate format, and many associated formats, are expressed using ASN.1. The current ASN.1 modules conform to the 1988 version of ASN.1. This document updates those ASN.1 modules to conform to the 2002 version of ASN.1. There are no bits-on-the-wire changes to any of the formats; this is simply a change to the syntax. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: P. Hoffman, J. Schaad |
| RFC5913 Clearance Attribute and Authority Clearance Constraints Certificate Extension This document defines the syntax and semantics for the Clearance attribute and the Authority Clearance Constraints extension in X.509 certificates. The Clearance attribute is used to indicate the clearance held by the subject. The Clearance attribute may appear in the subject directory attributes extension of a public key certificate or in the attributes field of an attribute certificate. The Authority Clearance Constraints certificate extension values in a Trust Anchor (TA), in Certification Authority (CA) public key certificates, and in an Attribute Authority (AA) public key certificate in a certification path for a given subject constrain the effective Clearance of the subject. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: S. Turner, S. Chokhani |
| RFC5914 Trust Anchor Format This document describes a structure for representing trust anchor information. A trust anchor is an authoritative entity represented by a public key and associated data. The public key is used to verify digital signatures, and the associated data is used to constrain the types of information or actions for which the trust anchor is authoritative. The structures defined in this document are intended to satisfy the format-related requirements defined in Trust Anchor Management Requirements. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: R. Housley, S. Ashmore, C. Wallace |
| RFC5915 Elliptic Curve Private Key Structure This document specifies the syntax and semantics for conveying Elliptic Curve (EC) private key information. The syntax and semantics defined herein are based on similar syntax and semantics defined by the Standards for Efficient Cryptography Group (SECG). This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: S. Turner, D. Brown |
| RFC5916 Device Owner Attribute This document defines the Device Owner attribute. It indicates the entity (e.g., company, organization, department, agency) that owns the device. This attribute may be included in public key certificates and attribute certificates. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: S. Turner |
| RFC5917 Clearance Sponsor Attribute This document defines the clearance sponsor attribute. It indicates the entity that sponsored (i.e., granted) the clearance. This attribute is intended for use in public key certificates and attribute certificates that also include the clearance attribute. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2010 Status: INFORMATIONAL Autor: S. Turner |
| RFC5918 Label Distribution Protocol (LDP) 'Typed Wildcard' Forward Equivalence Class (FEC) The Label Distribution Protocol (LDP) specification for the Wildcard Forward Equivalence Class (FEC) element has several limitations. This document addresses those limitations by defining a Typed Wildcard FEC Element and associated procedures. In addition, it defines a new LDP capability to address backward compatibility. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: R. Asati, I. Minei, B. Thomas |
| RFC5919 Signaling LDP Label Advertisement Completion There are situations following Label Distribution Protocol (LDP) session establishment where it would be useful for an LDP speaker to know when its peer has advertised all of its labels. The LDP specification provides no mechanism for an LDP speaker to notify a peer when it has completed its initial label advertisements to that peer. This document specifies means for an LDP speaker to signal completion of its initial label advertisements following session establishment. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: R. Asati, P. Mohapatra, E. Chen, B. Thomas |
| RFC5920 Security Framework for MPLS and GMPLS Networks This document provides a security framework for Multiprotocol Label Switching (MPLS) and Generalized Multiprotocol Label Switching (GMPLS) Networks. This document addresses the security aspects that are relevant in the context of MPLS and GMPLS. It describes the security threats, the related defensive techniques, and the mechanisms for detection and reporting. This document emphasizes RSVP-TE and LDP security considerations, as well as inter-AS and inter-provider security considerations for building and maintaining MPLS and GMPLS networks across different domains or different Service Providers. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2010 Status: INFORMATIONAL Autor: L. Fang |
| RFC5921 A Framework for MPLS in Transport Networks This document specifies an architectural framework for the application of Multiprotocol Label Switching (MPLS) to the construction of packet-switched transport networks. It describes a common set of protocol functions -- the MPLS Transport Profile (MPLS-TP) -- that supports the operational models and capabilities typical of such networks, including signaled or explicitly provisioned bidirectional connection-oriented paths, protection and restoration mechanisms, comprehensive Operations, Administration, and Maintenance (OAM) functions, and network operation in the absence of a dynamic control plane or IP forwarding support. Some of these functions are defined in existing MPLS specifications, while others require extensions to existing specifications to meet the requirements of the MPLS-TP. | July 2010 Status: INFORMATIONAL Autor: M. Bocci, S. Bryant, D. Frost, L. Levrau, L. Berger |
| RFC5922 Domain Certificates in the Session Initiation Protocol (SIP) This document describes how to construct and interpret certain information in a PKIX-compliant (Public Key Infrastructure using X.509) certificate for use in a Session Initiation Protocol (SIP) over Transport Layer Security (TLS) connection. More specifically, this document describes how to encode and extract the identity of a SIP domain in a certificate and how to use that identity for SIP domain authentication. As such, this document is relevant both to implementors of SIP and to issuers of certificates. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: V. Gurbani, S. Lawrence, A. Jeffrey |
| RFC5923 Connection Reuse in the Session Initiation Protocol (SIP) This document enables a pair of communicating proxies to reuse a congestion-controlled connection between themselves for sending requests in the forwards and backwards direction. Because the connection is essentially aliased for requests going in the backwards direction, reuse is predicated upon both the communicating endpoints authenticating themselves using X.509 certificates through Transport Layer Security (TLS). For this reason, we only consider connection reuse for TLS over TCP and TLS over Stream Control Transmission Protocol (SCTP). This document also provides guidelines on connection reuse and virtual SIP servers and the interaction of connection reuse and DNS SRV lookups in SIP. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: V. Gurbani, R. Mahy, B. Tate |
| RFC5924 Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates This memo documents an extended key usage (EKU) X.509 certificate extension for restricting the applicability of a certificate to use with a Session Initiation Protocol (SIP) service. As such, in addition to providing rules for SIP implementations, this memo also provides guidance to issuers of certificates for use with SIP. This document defines an Experimental Protocol for the Internet community. | June 2010 Status: EXPERIMENTAL Autor: S. Lawrence, V. Gurbani |
| RFC5925 The TCP Authentication Option This document specifies the TCP Authentication Option (TCP-AO), which obsoletes the TCP MD5 Signature option of RFC 2385 (TCP MD5). TCP-AO specifies the use of stronger Message Authentication Codes (MACs), protects against replays even for long-lived TCP connections, and provides more details on the association of security with TCP connections than TCP MD5. TCP-AO is compatible with either a static Master Key Tuple (MKT) configuration or an external, out-of-band MKT management mechanism; in either case, TCP-AO also protects connections when using the same MKT across repeated instances of a connection, using traffic keys derived from the MKT, and coordinates MKT changes between endpoints. The result is intended to support current infrastructure uses of TCP MD5, such as to protect long-lived connections (as used, e.g., in BGP and LDP), and to support a larger set of MACs with minimal other system and operational changes. TCP-AO uses a different option identifier than TCP MD5, even though TCP-AO and TCP MD5 are never permitted to be used simultaneously. TCP-AO supports IPv6, and is fully compatible with the proposed requirements for the replacement of TCP MD5. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: J. Touch, A. Mankin, R. Bonica |
| RFC5926 Cryptographic Algorithms for the TCP Authentication Option (TCP-AO) The TCP Authentication Option (TCP-AO) relies on security algorithms to provide authentication between two end-points. There are many such algorithms available, and two TCP-AO systems cannot interoperate unless they are using the same algorithms. This document specifies the algorithms and attributes that can be used in TCP-AO's current manual keying mechanism and provides the interface for future message authentication codes (MACs). [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: G. Lebovitz, E. Rescorla |
| RFC5927 ICMP Attacks against TCP This document discusses the use of the Internet Control Message Protocol (ICMP) to perform a variety of attacks against the Transmission Control Protocol (TCP). Additionally, this document describes a number of widely implemented modifications to TCP's handling of ICMP error messages that help to mitigate these issues. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2010 Status: INFORMATIONAL Autor: F. Gont |
| RFC5928 Traversal Using Relays around NAT (TURN) Resolution Mechanism This document defines a resolution mechanism to generate a list of server transport addresses that can be tried to create a Traversal Using Relays around NAT (TURN) allocation. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: M. Petit-Huguenin |
| RFC5929 Channel Bindings for TLS This document defines three channel binding types for Transport Layer Security (TLS), tls-unique, tls-server-end-point, and tls-unique-for-telnet, in accordance with RFC 5056 (On Channel Binding). | July 2010 Status: PROPOSED STANDARD Autor: J. Altman, N. Williams, L. Zhu |
| RFC5930 Using Advanced Encryption Standard Counter Mode (AES-CTR) with the Internet Key Exchange version 02 (IKEv2) Protocol This document describes the usage of Advanced Encryption Standard Counter Mode (AES-CTR), with an explicit Initialization Vector, by the Internet Key Exchange version 2 (IKEv2) protocol, for encrypting the IKEv2 exchanges that follow the IKE_SA_INIT exchange. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2010 Status: INFORMATIONAL Autor: S. Shen, Y. Mao, NSS. Murthy |
| RFC5931 Extensible Authentication Protocol (EAP) Authentication Using Only a Password This memo describes an Extensible Authentication Protocol (EAP) method, EAP-pwd, which uses a shared password for authentication. The password may be a low-entropy one and may be drawn from some set of possible passwords, like a dictionary, which is available to an attacker. The underlying key exchange is resistant to active attack, passive attack, and dictionary attack. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: D. Harkins, G. Zorn |
| RFC5932 Camellia Cipher Suites for TLS This document specifies a set of cipher suites for the Transport Security Layer (TLS) protocol to support the Camellia encryption algorithm as a block cipher. It amends the cipher suites originally specified in RFC 4132 by introducing counterparts using the newer cryptographic hash algorithms from the SHA-2 family. This document obsoletes RFC 4132. [STANDARDS-TRACK] | June 2010 Status: PROPOSED STANDARD Autor: A. Kato, M. Kanda, S. Kanno |
| RFC5933 Use of GOST Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC This document describes how to produce digital signatures and hash functions using the GOST R 34.10-2001 and GOST R 34.11-94 algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain Name System Security Extensions (DNSSEC). [STANDARDS-TRACK] | July 2010 Status: PROPOSED STANDARD Autor: V. Dolmatov, A. Chuprina, I. Ustinov |
| RFC5934 Trust Anchor Management Protocol (TAMP) This document describes a transport independent protocol for the management of trust anchors (TAs) and community identifiers stored in a trust anchor store. The protocol makes use of the Cryptographic Message Syntax (CMS), and a digital signature is used to provide integrity protection and data origin authentication. The protocol can be used to manage trust anchor stores containing trust anchors represented as Certificate, TBSCertificate, or TrustAnchorInfo objects. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: R. Housley, S. Ashmore, C. Wallace |
| RFC5935 Expressing SNMP SMI Datatypes in XML Schema Definition Language This memo defines the IETF standard expression of Structure of Management Information (SMI) base datatypes in XML Schema Definition (XSD) language. The primary objective of this memo is to enable the production of XML documents that are as faithful to the SMI as possible, using XSD as the validation mechanism. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: M. Ellison, B. Natale |
| RFC5936 DNS Zone Transfer Protocol (AXFR) The standard means within the Domain Name System protocol for maintaining coherence among a zone's authoritative name servers consists of three mechanisms. Authoritative Transfer (AXFR) is one of the mechanisms and is defined in RFC 1034 and RFC 1035. | June 2010 Status: PROPOSED STANDARD Autor: E. Lewis, A. Hoenes |
| RFC5937 Using Trust Anchor Constraints during Certification Path Processing This document describes how to use information associated with a trust anchor public key when validating certification paths. This information can be used to constrain the usage of a trust anchor. Typically, constraints are used to limit the certificate policies and names that can appear in certification paths validated using a trust anchor. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: S. Ashmore, C. Wallace |
| RFC5938 Individual Session Control Feature for the Two-Way Active Measurement Protocol (TWAMP) The IETF has completed its work on the core specification of TWAMP -- the Two-Way Active Measurement Protocol. This memo describes an OPTIONAL feature for TWAMP, that gives the controlling host the ability to start and stop one or more individual test sessions using Session Identifiers. The base capability of the TWAMP protocol requires all test sessions that were previously requested and accepted to start and stop at the same time. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: A. Morton, M. Chiba |
| RFC5939 Session Description Protocol (SDP) Capability Negotiation The Session Description Protocol (SDP) was intended to describe multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. SDP was not intended to provide capability indication or capability negotiation; however, over the years, SDP has seen widespread adoption and as a result it has been gradually extended to provide limited support for these, notably in the form of the offer/answer model defined in RFC 3264. SDP does not define how to negotiate one or more alternative transport protocols (e.g., RTP profiles) or attributes. This makes it difficult to deploy new RTP profiles such as Secure RTP or RTP with RTCP-based feedback, negotiate use of different security keying mechanisms, etc. It also presents problems for some forms of media negotiation. | September 2010 Status: PROPOSED STANDARD Autor: F. Andreasen |
| RFC5940 Additional Cryptographic Message Syntax (CMS) Revocation Information Choices The Cryptographic Message Syntax (CMS) allows revocation information to be conveyed as part of the SignedData, EnvelopedData, AuthenticatedData, and AuthEnvelopedData content types. The preferred format for revocation information is the Certificate Revocation List (CRL), but an extension mechanism supports other revocation information formats. This document defines two additional revocation information formats for Online Certificate Status Protocol (OCSP) responses and Server-Based Certificate Validation Protocol (SCVP) requests and responses. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: S. Turner, R. Housley |
| RFC5941 Sharing Transaction Fraud Data This document describes a document format for exchanging transaction fraud (Thraud) information. It extends the Incident Handling Working Group (INCH WG) Incident Object Description Exchange Format (IODEF) incident reporting document format. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: D. M'Raihi, S. Boeyen, M. Grandcolas, S. Bajaj |
| RFC5942 IPv6 Subnet Model: The Relationship between Links and Subnet Prefixes IPv6 specifies a model of a subnet that is different than the IPv4 subnet model. The subtlety of the differences has resulted in incorrect implementations that do not interoperate. This document spells out the most important difference: that an IPv6 address isn't automatically associated with an IPv6 on-link prefix. This document also updates (partially due to security concerns caused by incorrect implementations) a part of the definition of "on-link" from RFC 4861. [STANDARDS-TRACK] | July 2010 Status: PROPOSED STANDARD Autor: H. Singh, W. Beebee, E. Nordmark |
| RFC5943 A Dedicated Routing Policy Specification Language Interface Identifier for Operational Testing The deployment of new IP connectivity typically results in intermittent reachability for numerous reasons that are outside the scope of this document. In order to aid in the debugging of these persistent problems, this document proposes the creation of a new Routing Policy Specification Language attribute that allows a network to advertise an IP address that is reachable and can be used as a target for diagnostic tests (e.g., pings). [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: B. Haberman |
| RFC5944 IP Mobility Support for IPv4, Revised 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] | November 2010 Status: PROPOSED STANDARD Autor: C. Perkins |
| RFC5945 Resource Reservation Protocol (RSVP) Proxy Approaches The Resource Reservation Protocol (RSVP) can be used to make end-to- end resource reservations in an IP network in order to guarantee the quality of service required by certain flows. RSVP assumes that both the data sender and receiver of a given flow take part in RSVP signaling. Yet, there are use cases where resource reservation is required, but the receiver, the sender, or both, is not RSVP-capable. This document presents RSVP proxy behaviors allowing RSVP routers to initiate or terminate RSVP signaling on behalf of a receiver or a sender that is not RSVP-capable. This allows resource reservations to be established on a critical subset of the end-to-end path. This document reviews conceptual approaches for deploying RSVP proxies and discusses how RSVP reservations can be synchronized with application requirements, despite the sender, receiver, or both not participating in RSVP. This document also points out where extensions to RSVP (or to other protocols) may be needed for deployment of a given RSVP proxy approach. However, such extensions are outside the scope of this document. Finally, practical use cases for RSVP proxy are described. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: F. Le Faucheur, J. Manner, D. Wing, A. Guillou |
| RFC5946 Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy Resource Reservation Protocol (RSVP) signaling can be used to make end-to-end resource reservations in an IP network in order to guarantee the Quality of Service (QoS) required by certain flows. With conventional RSVP, both the data sender and receiver of a given flow take part in RSVP signaling. Yet, there are many use cases where resource reservation is required, but the receiver, the sender, or both, is not RSVP-capable. Where the receiver is not RSVP- capable, an RSVP router may behave as an RSVP Receiver Proxy, thereby performing RSVP signaling on behalf of the receiver. This allows resource reservations to be established on the segment of the end-to- end path from the sender to the RSVP Receiver Proxy. However, as discussed in the companion document "RSVP Proxy Approaches", RSVP extensions are needed to facilitate operations with an RSVP Receiver Proxy whose signaling is triggered by receipt of RSVP Path messages from the sender. This document specifies these extensions. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: F. Le Faucheur, J. Manner, A. Narayanan, A. Guillou, H. Malik |
| RFC5947 Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP) This document states requirements for a standardized SIP registration mechanism for multiple addresses of record (AORs), the mechanism being suitable for deployment by SIP service providers on a large scale in support of small to medium sized Private Branch Exchanges (PBXs). The requirements are for a solution that can, as a minimum, support AORs based on E.164 numbers. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2010 Status: INFORMATIONAL Autor: J. Elwell, H. Kaplan |
| RFC5948 Transmission of IPv4 Packets over the IP Convergence Sublayer of IEEE 802.16 IEEE 802.16 is an air interface specification for wireless broadband access. IEEE 802.16 has specified multiple service-specific Convergence Sublayers for transmitting upper-layer protocols. The Packet CS (Packet Convergence Sublayer) is used for the transport of all packet-based protocols such as the Internet Protocol (IP) and IEEE 802.3 (Ethernet). The IP-specific part of the Packet CS enables the transport of IPv4 packets directly over the IEEE 802.16 Media Access Control (MAC) layer. | August 2010 Status: PROPOSED STANDARD Autor: S. Madanapalli, S. Park, S. Chakrabarti, G. Montenegro |
| RFC5949 Fast Handovers for Proxy Mobile IPv6 Mobile IPv6 (MIPv6; RFC 3775) provides a mobile node with IP mobility when it performs a handover from one access router to another, and fast handovers for Mobile IPv6 (FMIPv6) are specified to enhance the handover performance in terms of latency and packet loss. While MIPv6 (and FMIPv6 as well) requires the participation of the mobile node in the mobility-related signaling, Proxy Mobile IPv6 (PMIPv6; RFC 5213) provides IP mobility to nodes that either have or do not have MIPv6 functionality without such involvement. Nevertheless, the basic performance of PMIPv6 in terms of handover latency and packet loss is considered no different from that of MIPv6. | September 2010 Status: PROPOSED STANDARD Autor: H. Yokota, K. Chowdhury, R. Koodli, B. Patil, F. Xia |
| RFC5950 Network Management Framework for MPLS-based Transport Networks This document provides the network management framework for the Transport Profile for Multi-Protocol Label Switching (MPLS-TP). | September 2010 Status: INFORMATIONAL Autor: S. Mansfield, E. Gray, K. Lam |
| RFC5951 Network Management Requirements for MPLS-based Transport Networks This document specifies the requirements for the management of equipment used in networks supporting an MPLS Transport Profile (MPLS-TP). The requirements are defined for specification of network management aspects of protocol mechanisms and procedures that constitute the building blocks out of which the MPLS Transport Profile is constructed. That is, these requirements indicate what management capabilities need to be available in MPLS for use in managing the MPLS-TP. This document is intended to identify essential network management capabilities, not to specify what functions any particular MPLS implementation supports. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: K. Lam, S. Mansfield, E. Gray |
| RFC5952 A Recommendation for IPv6 Address Text Representation As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addresses in text. While the IPv6 address architecture in Section 2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users. This document defines a canonical textual representation format. It does not define a format for internal storage, such as within an application or database. It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and be able to handle any legitimate RFC 4291 format. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: S. Kawamura, M. Kawashima |
| RFC5953 Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) This document describes a Transport Model for the Simple Network Management Protocol (SNMP), that uses either the Transport Layer Security protocol or the Datagram Transport Layer Security (DTLS) protocol. The TLS and DTLS protocols provide authentication and privacy services for SNMP applications. This document describes how the TLS Transport Model (TLSTM) implements the needed features of a SNMP Transport Subsystem to make this protection possible in an interoperable way. | August 2010 Status: PROPOSED STANDARD Autor: W. Hardaker |
| RFC5954 Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261 This document corrects the Augmented Backus-Naur Form (ABNF) production rule associated with generating IPv6 literals in RFC 3261. It also clarifies the rule for Uniform Resource Identifier (URI) comparison when the URIs contain textual representation of IP addresses. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: V. Gurbani, B. Carpenter, B. Tate |
| RFC5955 The application/timestamped-data Media Type This document defines a new media type for TimeStampedData envelopes as described in RFC 5544. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: A. Santoni |
| RFC5956 Forward Error Correction Grouping Semantics in the Session Description Protocol This document defines the semantics for grouping the associated source and FEC-based (Forward Error Correction) repair flows in the Session Description Protocol (SDP). The semantics defined in this document are to be used with the SDP Grouping Framework (RFC 5888). These semantics allow the description of grouping relationships between the source and repair flows when one or more source and/or repair flows are associated in the same group, and they provide support for additive repair flows. SSRC-level (Synchronization Source) grouping semantics are also defined in this document for Real-time Transport Protocol (RTP) streams using SSRC multiplexing. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: A. Begen |
| RFC5957 Display-Based Address Sorting for the IMAP4 SORT Extension This document describes an IMAP protocol extension enabling server- side message sorting on the commonly displayed portion of the From and To header fields. [STANDARDS-TRACK] | July 2010 Status: PROPOSED STANDARD Autor: D. Karp |
| RFC5958 Asymmetric Key Packages This document defines the syntax for private-key information and a content type for it. Private-key information includes a private key for a specified public-key algorithm and a set of attributes. The Cryptographic Message Syntax (CMS), as defined in RFC 5652, can be used to digitally sign, digest, authenticate, or encrypt the asymmetric key format content type. This document obsoletes RFC 5208. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC5959 Algorithms for Asymmetric Key Package Content Type This document describes the conventions for using several cryptographic algorithms with the EncryptedPrivateKeyInfo structure, as defined in RFC 5958. It also includes conventions necessary to protect the AsymmetricKeyPackage content type with SignedData, EnvelopedData, EncryptedData, AuthenticatedData, and AuthEnvelopedData. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC5960 MPLS Transport Profile Data Plane Architecture The Multiprotocol Label Switching Transport Profile (MPLS-TP) is the set of MPLS protocol functions applicable to the construction and operation of packet-switched transport networks. This document specifies the subset of these functions that comprises the MPLS-TP data plane: the architectural layer concerned with the encapsulation and forwarding of packets within an MPLS-TP network. | August 2010 Status: PROPOSED STANDARD Autor: D. Frost, S. Bryant, M. Bocci |
| RFC5961 Improving TCP's Robustness to Blind In-Window Attacks TCP has historically been considered to be protected against spoofed off-path packet injection attacks by relying on the fact that it is difficult to guess the 4-tuple (the source and destination IP addresses and the source and destination ports) in combination with the 32-bit sequence number(s). A combination of increasing window sizes and applications using longer-term connections (e.g., H-323 or Border Gateway Protocol (BGP) [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: A. Ramaiah, R. Stewart, M. Dalal |
| RFC5962 Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO) The Geopriv Location Object introduced by the Presence Information Data Format - Location Object (PIDF-LO), RFC 4119, defines a basic XML format for carrying geographical information of a presentity. This document defines PIDF-LO extensions to convey information about moving objects. Elements are defined that enable expression of spatial orientation, speed, and heading of the presentity. [STANDARDS TRACK] | September 2010 Status: PROPOSED STANDARD Autor: H. Schulzrinne, V. Singh, H. Tschofenig, M. Thomson |
| RFC5963 IPv6 Deployment in Internet Exchange Points (IXPs) This document provides guidance on IPv6 deployment in Internet Exchange Points (IXPs). It includes information regarding the switch fabric configuration, the addressing plan and general organizational tasks that need to be performed. IXPs are mainly a Layer 2 infrastructure, and, in many cases, the best recommendations suggest that the IPv6 data, control, and management plane should not be handled differently than in IPv4. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: R. Gagliano |
| RFC5964 Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries This document describes how holes can be specified in geodetic service boundaries. One means of implementing a search solution in a service database, such as one might provide with a Location-to- Service Translation (LoST) server, is described. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: J. Winterbottom, M. Thomson |
| RFC5965 An Extensible Format for Email Feedback Reports This document defines an extensible format and MIME type that may be used by mail operators to report feedback about received email to other parties. This format is intended as a machine-readable replacement for various existing report formats currently used in Internet email. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: Y. Shafranovich, J. Levine, M. Kucherawy |
| RFC5966 DNS Transport over TCP - Implementation Requirements This document updates the requirements for the support of TCP as a transport protocol for DNS implementations. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: R. Bellis |
| RFC5967 The application/pkcs10 Media Type This document specifies a media type used to carry PKCS #10 certification requests as defined in RFC 2986. It carries over the original specification from RFC 2311, which recently has been moved to Historic status, and properly links it to RFC 2986. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: S. Turner |
| RFC5968 Guidelines for Extending the RTP Control Protocol (RTCP) The RTP Control Protocol (RTCP) is used along with the Real-time Transport Protocol (RTP) to provide a control channel between media senders and receivers. This allows constructing a feedback loop to enable application adaptation and monitoring, among other uses. The basic reporting mechanisms offered by RTCP are generic, yet quite powerful and suffice to cover a range of uses. This document provides guidelines on extending RTCP if those basic mechanisms prove insufficient. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2010 Status: INFORMATIONAL Autor: J. Ott, C. Perkins |
| RFC5969 IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification This document specifies an automatic tunneling mechanism tailored to advance deployment of IPv6 to end users via a service provider's IPv4 network infrastructure. Key aspects include automatic IPv6 prefix delegation to sites, stateless operation, simple provisioning, and service, which is equivalent to native IPv6 at the sites that are served by the mechanism. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: W. Townsley, O. Troan |
| RFC5970 DHCPv6 Options for Network Boot The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides a framework for passing configuration information to nodes on a network. This document describes new options for DHCPv6 that SHOULD be used for booting a node from the network. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: T. Huth, J. Freimann, V. Zimmer, D. Thaler |
| RFC5971 GIST: General Internet Signalling Transport This document specifies protocol stacks for the routing and transport of per-flow signalling messages along the path taken by that flow through the network. The design uses existing transport and security protocols under a common messaging layer, the General Internet Signalling Transport (GIST), which provides a common service for diverse signalling applications. GIST does not handle signalling application state itself, but manages its own internal state and the configuration of the underlying transport and security protocols to enable the transfer of messages in both directions along the flow path. The combination of GIST and the lower layer transport and security protocols provides a solution for the base protocol component of the "Next Steps in Signalling" (NSIS) framework. This document defines an Experimental Protocol for the Internet community. | October 2010 Status: EXPERIMENTAL Autor: H. Schulzrinne, R. Hancock |
| RFC5972 General Internet Signaling Transport (GIST) State Machine | October 2010 Status: INFORMATIONAL Autor: T. Tsenov, H. Tschofenig, X. Fu, C. Aoun, E. Davies |
| RFC5973 NAT/Firewall NSIS Signaling Layer Protocol (NSLP) This memo defines the NSIS Signaling Layer Protocol (NSLP) for Network Address Translators (NATs) and firewalls. This NSLP allows hosts to signal on the data path for NATs and firewalls to be configured according to the needs of the application data flows. For instance, it enables hosts behind NATs to obtain a publicly reachable address and hosts behind firewalls to receive data traffic. The overall architecture is given by the framework and requirements defined by the Next Steps in Signaling (NSIS) working group. The network scenarios, the protocol itself, and examples for path-coupled signaling are given in this memo. This document defines an Experimental Protocol for the Internet community. | October 2010 Status: EXPERIMENTAL Autor: M. Stiemerling, H. Tschofenig, C. Aoun, E. Davies |
| RFC5974 NSIS Signaling Layer Protocol (NSLP) for Quality-of-Service Signaling This specification describes the NSIS Signaling Layer Protocol (NSLP) for signaling Quality of Service (QoS) reservations in the Internet. It is in accordance with the framework and requirements developed in NSIS. Together with General Internet Signaling Transport (GIST), it provides functionality similar to RSVP and extends it. The QoS NSLP is independent of the underlying QoS specification or architecture and provides support for different reservation models. It is simplified by the elimination of support for multicast flows. This specification explains the overall protocol approach, describes the design decisions made, and provides examples. It specifies object, message formats, and processing rules. This document defines an Experimental Protocol for the Internet community. | October 2010 Status: EXPERIMENTAL Autor: J. Manner, G. Karagiannis, A. McDonald |
| RFC5975 QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP) The Quality-of-Service (QoS) NSIS signaling layer protocol (NSLP) is used to signal QoS reservations and is independent of a specific QoS model (QOSM) such as IntServ or Diffserv. Rather, all information specific to a QOSM is encapsulated in a separate object, the QSPEC. This document defines a template for the QSPEC including a number of QSPEC parameters. The QSPEC parameters provide a common language to be reused in several QOSMs and thereby aim to ensure the extensibility and interoperability of QoS NSLP. While the base protocol is QOSM-agnostic, the parameters that can be carried in the QSPEC object are possibly closely coupled to specific models. The node initiating the NSIS signaling adds an Initiator QSPEC, which indicates the QSPEC parameters that must be interpreted by the downstream nodes less the reservation fails, thereby ensuring the intention of the NSIS initiator is preserved along the signaling path. This document defines an Experimental Protocol for the Internet community. | October 2010 Status: EXPERIMENTAL Autor: G. Ash, A. Bader, C. Kappler, D. Oran |
| RFC5976 Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service Classes This document describes a QoS-NSLP Quality-of-Service model (QOSM) based on ITU-T Recommendation Y.1541 Network QoS Classes and related guidance on signaling. Y.1541 specifies 8 classes of Network Performance objectives, and the Y.1541-QOSM extensions include additional QSPEC parameters and QOSM processing guidelines. This document defines an Experimental Protocol for the Internet community. | October 2010 Status: EXPERIMENTAL Autor: G. Ash, A. Morton, M. Dolly, P. Tarapore, C. Dvorak, Y. El Mghazli |
| RFC5977 RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in Diffserv This document describes a Next Steps in Signaling (NSIS) Quality-of-Service (QoS) Model for networks that use the Resource Management in Diffserv (RMD) concept. RMD is a technique for adding admission control and preemption function to Differentiated Services (Diffserv) networks. The RMD QoS Model allows devices external to the RMD network to signal reservation requests to Edge nodes in the RMD network. The RMD Ingress Edge nodes classify the incoming flows into traffic classes and signals resource requests for the corresponding traffic class along the data path to the Egress Edge nodes for each flow. Egress nodes reconstitute the original requests and continue forwarding them along the data path towards the final destination. In addition, RMD defines notification functions to indicate overload situations within the domain to the Edge nodes. This document defines an Experimental Protocol for the Internet community. | October 2010 Status: EXPERIMENTAL Autor: A. Bader, L. Westberg, G. Karagiannis, C. Kappler, T. Phelan |
| RFC5978 Using and Extending the NSIS Protocol Family This document gives an overview of the Next Steps in Signaling (NSIS) framework and protocol suite created by the NSIS Working Group during the period of 2001-2010. It also includes suggestions on how the industry can make use of the new protocols and how the community can exploit the extensibility of both the framework and existing protocols to address future signaling needs. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: J. Manner, R. Bless, J. Loughney, E. Davies |
| RFC5979 NSIS Operation over IP Tunnels NSIS Quality of Service (QoS) signaling enables applications to perform QoS reservation along a data flow path. When the data flow path contains IP tunnel segments, NSIS QoS signaling has no effect within those tunnel segments. Therefore, the resulting tunnel segments could become the weakest QoS link and invalidate the QoS efforts in the rest of the end-to-end path. The problem with NSIS signaling within the tunnel is caused by the tunnel encapsulation that masks packets' original IP header fields. Those original IP header fields are needed to intercept NSIS signaling messages and classify QoS data packets. This document defines a solution to this problem by mapping end-to-end QoS session requests to corresponding QoS sessions in the tunnel, thus extending the end-to-end QoS signaling into the IP tunnel segments. This document defines an Experimental Protocol for the Internet community. | March 2011 Status: EXPERIMENTAL Autor: C. Shen, H. Schulzrinne, S. Lee, J. Bang |
| RFC5980 NSIS Protocol Operation in Mobile Environments Mobility of an IP-based node affects routing paths, and as a result, can have a significant effect on the protocol operation and state management. This document discusses the effects mobility can cause to the Next Steps in Signaling (NSIS) protocol suite, and shows how the NSIS protocols operate in different scenarios with mobility management protocols. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: T. Sanda, X. Fu, S. Jeong, J. Manner, H. Tschofenig |
| RFC5981 Authorization for NSIS Signaling Layer Protocols Signaling layer protocols specified within the Next Steps in Signaling (NSIS) framework may rely on the General Internet Signaling Transport (GIST) protocol to handle authorization. Still, the signaling layer protocol above GIST itself may require separate authorization to be performed when a node receives a request for a certain kind of service or resources. This document presents a generic model and object formats for session authorization within the NSIS signaling layer protocols. 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 coordinate actions between the signaling and transport planes. This document defines an Experimental Protocol for the Internet community. | February 2011 Status: EXPERIMENTAL Autor: J. Manner, M. Stiemerling, H. Tschofenig, R. Bless |
| RFC5982 IP Flow Information Export (IPFIX) Mediation: Problem Statement Flow-based measurement is a popular method for various network monitoring usages. The sharing of flow-based information for monitoring applications having different requirements raises some open issues in terms of measurement system scalability, flow-based measurement flexibility, and export reliability that IP Flow Information Export (IPFIX) Mediation may help resolve. This document describes some problems related to flow-based measurement that network administrators have been facing, and then it describes IPFIX Mediation applicability examples along with the problems. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: A. Kobayashi, B. Claise |
| RFC5983 Mailing Lists and Internationalized Email Addresses This document describes considerations for mailing lists with the introduction of internationalized email addresses. | October 2010 Status: EXPERIMENTAL Autor: R. Gellens |
| RFC5984 Increasing Throughput in IP Networks with ESP-Based Forwarding: ESPBasedForwarding This document proposes an experimental way of reaching infinite bandwidth in IP networks by the use of ESP-based forwarding. This document defines an Experimental Protocol for the Internet community. | April 2011 Status: EXPERIMENTAL Autor: K-M. Moller |
| RFC5985 HTTP-Enabled Location Delivery (HELD) This document defines a Layer 7 Location Configuration Protocol (L7 LCP) and describes the use of HTTP and HTTP/TLS as transports for the L7 LCP. The L7 LCP is used for retrieving location information from a server within an access network. It includes options for retrieving location information in two forms: by value and by reference. The protocol is an extensible application-layer protocol that is independent of the session layer. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: M. Barnes |
| RFC5986 Discovering the Local Location Information Server (LIS) Discovery of the correct Location Information Server (LIS) in the local access network is necessary for Devices that wish to acquire location information from the network. A method is described for the discovery of a LIS in the access network serving a Device. Dynamic Host Configuration Protocol (DHCP) options for IP versions 4 and 6 are defined that specify a domain name. This domain name is then used as input to a URI-enabled NAPTR (U-NAPTR) resolution process. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: M. Thomson, J. Winterbottom |
| RFC5987 Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters By default, message header field parameters in Hypertext Transfer Protocol (HTTP) messages cannot carry characters outside the ISO- 8859-1 character set. RFC 2231 defines an encoding mechanism for use in Multipurpose Internet Mail Extensions (MIME) headers. This document specifies an encoding suitable for use in HTTP header fields that is compatible with a profile of the encoding defined in RFC 2231. [STANDARDS-TRACK] | August 2010 Status: PROPOSED STANDARD Autor: J. Reschke |
| RFC5988 Web Linking This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: M. Nottingham |
| RFC5989 A SIP Event Package for Subscribing to Changes to an HTTP Resource The Session Initiation Protocol (SIP) is increasingly being used in systems that are tightly coupled with Hypertext Transport Protocol (HTTP) servers for a variety of reasons. In many of these cases, applications can benefit from being able to discover, in near real- time, when a specific HTTP resource is created, changed, or deleted. This document proposes a mechanism, based on the SIP Event Framework, for doing so. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: A.B. Roach |
| RFC5990 Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS) The RSA-KEM Key Transport Algorithm is a one-pass (store-and-forward) mechanism for transporting keying data to a recipient using the recipient's RSA public key. ("KEM" stands for "key encapsulation mechanism".) This document specifies the conventions for using the RSA-KEM Key Transport Algorithm with the Cryptographic Message Syntax (CMS). The ASN.1 syntax is aligned with an expected forthcoming change to American National Standard (ANS) X9.44. | September 2010 Status: PROPOSED STANDARD Autor: J. Randall, B. Kaliski, J. Brainard, S. Turner |
| RFC5991 Teredo Security Updates The Teredo protocol defines a set of flags that are embedded in every Teredo IPv6 address. This document specifies a set of security updates that modify the use of this flags field, but are backward compatible. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: D. Thaler, S. Krishnan, J. Hoagland |
| RFC5992 Internationalized Domain Names Registration and Administration Guidelines for European Languages Using Cyrillic This document is a guideline for registries and registrars on registering internationalized domain names (IDNs) based on (in alphabetical order) Bosnian, Bulgarian, Byelorussian, Kildin Sami, Macedonian, Montenegrin, Russian, Serbian, and Ukrainian languages in a DNS zone. It describes appropriate characters for registration and variant considerations for characters from Greek and Latin scripts with similar appearances and/or derivations. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: S. Sharikov, D. Miloshevic, J. Klensin |
| RFC5993 RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR) This document specifies the payload format for packetization of Global System for Mobile Communications Half Rate (GSM-HR) speech codec data into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple frames per payload and packet loss robustness methods using redundancy. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: X. Duan, S. Wang, M. Westerlund, K. Hellwig, I. Johansson |
| RFC5994 Application of Ethernet Pseudowires to MPLS Transport Networks Ethernet pseudowires are widely deployed to support packet transport of Ethernet services. These services in-turn provide transport for a variety of client networks, e.g., IP and MPLS. This document uses procedures defined in the existing IETF specifications of Ethernet pseudowires carried over MPLS networks. | October 2010 Status: INFORMATIONAL Autor: S. Bryant, M. Morrow, G. Swallow, R. Cherukuri, T. Nadeau, N. Harrison, B. Niven-Jenkins |
| RFC5995 Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections The Hypertext Transfer Protocol (HTTP) Extensions for the Web Distributed Authoring and Versioning (WebDAV) do not define the behavior for the "POST" method when applied to collections, as the base specification (HTTP) leaves implementers lots of freedom for the semantics of "POST". | September 2010 Status: PROPOSED STANDARD Autor: J. Reschke |
| RFC5996 Internet Key Exchange Protocol Version 2 (IKEv2) This document describes version 2 of the Internet Key Exchange (IKE) protocol. IKE is a component of IPsec used for performing mutual authentication and establishing and maintaining Security Associations (SAs). This document replaces and updates RFC 4306, and includes all of the clarifications from RFC 4718. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: C. Kaufman, P. Hoffman, Y. Nir, P. Eronen |
| RFC5997 Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol This document describes a deployed extension to the Remote Authentication Dial In User Service (RADIUS) protocol, enabling clients to query the status of a RADIUS server. This extension utilizes the Status-Server (12) Code, which was reserved for experimental use in RFC 2865. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2010 Status: INFORMATIONAL Autor: A. DeKok |
| RFC5998 An Extension for EAP-Only Authentication in IKEv2 IKEv2 specifies that Extensible Authentication Protocol (EAP) authentication must be used together with responder authentication based on public key signatures. This is necessary with old EAP methods that provide only unilateral authentication using, e.g., one- time passwords or token cards. | September 2010 Status: PROPOSED STANDARD Autor: P. Eronen, H. Tschofenig, Y. Sheffer |
| RFC6001 Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN) There are specific requirements for the support of networks comprising Label Switching Routers (LSRs) participating in different data plane switching layers controlled by a single Generalized Multi-Protocol Label Switching (GMPLS) control plane instance, referred to as GMPLS Multi-Layer Networks / Multi-Region Networks (MLN/MRN). | October 2010 Status: PROPOSED STANDARD Autor: D. Papadimitriou, M. Vigoureux, K. Shiomoto, D. Brungard, JL. Le Roux |
| RFC6002 Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Channel Set Label Extensions This document describes two technology-independent extensions to Generalized Multi-Protocol Label Switching (GMPLS). The first extension defines the new switching type Data Channel Switching Capable. Data Channel Switching Capable interfaces are able to support switching of the whole digital channel presented on single channel interfaces. The second extension defines a new type of generalized label and updates related objects. The new label is called the Generalized Channel_Set Label and allows more than one data plane label to be controlled as part of a Label Switched Path (LSP). [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: L. Berger, D. Fedyk |
| RFC6003 Ethernet Traffic Parameters This document describes the support of Metro Ethernet Forum (MEF) Ethernet traffic parameters as described in MEF10.1 when using Generalized Multi-Protocol Label Switching (GMPLS) Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: D. Papadimitriou |
| RFC6004 Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching | October 2010 Status: PROPOSED STANDARD Autor: L. Berger, D. Fedyk |
| RFC6005 Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 User Network Interface (UNI) This document describes a method for controlling two specific types of Ethernet switching via a GMPLS-based User Network Interface (UNI). This document supports the types of switching required by the Ethernet services that have been defined in the context of the Metro Ethernet Forum (MEF) and International Telecommunication Union (ITU) G.8011. This document is the UNI companion to "Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching". This document does not define or limit the underlying intra-domain or Internal NNI (I-NNI) technology used to support the UNI. [STANDARDS- TRACK] | October 2010 Status: PROPOSED STANDARD Autor: L. Berger, D. Fedyk |
| RFC6006 Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths Point-to-point Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) may be established using signaling techniques, but their paths may first need to be determined. The Path Computation Element (PCE) has been identified as an appropriate technology for the determination of the paths of point-to-multipoint (P2MP) TE LSPs. | September 2010 Status: PROPOSED STANDARD Autor: Q. Zhao, D. King, F. Verhaeghe, T. Takeda, Z. Ali, J. Meuric |
| RFC6007 Use of the Synchronization VECtor (SVEC) List for Synchronized Dependent Path Computations A Path Computation Element (PCE) may be required to perform dependent path computations. Dependent path computations are requests that need to be synchronized in order to meet specific objectives. An example of a dependent request would be a PCE computing a set of services that are required to be diverse (disjointed) from each other. When a PCE computes sets of dependent path computation requests concurrently, use of the Synchronization VECtor (SVEC) list is required for association among the sets of dependent path computation requests. The SVEC object is optional and carried within the Path Computation Element Communication Protocol (PCEP) PCRequest (PCReq) message. | September 2010 Status: INFORMATIONAL Autor: I. Nishioka, D. King |
| RFC6008 Authentication-Results Registration for Differentiating among Cryptographic Results This memo updates the registry of properties in Authentication- Results: message header fields to allow a multiple-result report to distinguish among one or more cryptographic signatures on a message, thus associating specific results with the signatures they represent. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: M. Kucherawy |
| RFC6009 Sieve Email Filtering: Delivery Status Notifications and Deliver-By Extensions This document describes the "envelope-dsn", "redirect-dsn", "envelope-deliverby", and "redirect-deliverby" extensions to the Sieve email filtering language. The "envelope-dsn" and "envelope- deliverby" extensions provide access to additional envelope information provided by the delivery status notification (DSN) and Deliver-By SMTP extensions, respectively. The "redirect-dsn" and "redirect-deliverby" extensions extend Sieve's redirect action to provide control over delivery status notification and Deliver-By parameters, respectively. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: N. Freed |
| RFC6010 Cryptographic Message Syntax (CMS) Content Constraints Extension This document specifies the syntax and semantics for the Cryptographic Message Syntax (CMS) content constraints extension. This extension is used to determine whether a public key is appropriate to use in the processing of a protected content. In particular, the CMS content constraints extension is one part of the authorization decision; it is used when validating a digital signature on a CMS SignedData content or validating a message authentication code (MAC) on a CMS AuthenticatedData content or CMS AuthEnvelopedData content. The signed or authenticated content type is identified by an ASN.1 object identifier, and this extension indicates the content types that the public key is authorized to validate. If the authorization check is successful, the CMS content constraints extension also provides default values for absent attributes. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: R. Housley, S. Ashmore, C. Wallace |
| RFC6011 Session Initiation Protocol (SIP) User Agent Configuration This document defines procedures for how a SIP User Agent should locate, retrieve, and maintain current configuration information from a Configuration Service. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: S. Lawrence, J. Elwell |
| RFC6012 Datagram Transport Layer Security (DTLS) Transport Mapping for Syslog This document describes the transport of syslog messages over the Datagram Transport Layer Security (DTLS) protocol. It provides a secure transport for syslog messages in cases where a connectionless transport is desired. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: J. Salowey, T. Petch, R. Gerhards, H. Feng |
| RFC6013 TCP Cookie Transactions (TCPCT) TCP Cookie Transactions (TCPCT) deter spoofing of connections and prevent resource exhaustion, eliminating Responder (server) state during the initial handshake. The Initiator (client) has sole responsibility for ensuring required delays between connections. The cookie exchange may carry data, limited to inhibit amplification and reflection denial of service attacks. This document defines an Experimental Protocol for the Internet community. | January 2011 Status: EXPERIMENTAL Autor: W. Simpson |
| RFC6014 Cryptographic Algorithm Identifier Allocation for DNSSEC This document specifies how DNSSEC cryptographic algorithm identifiers in the IANA registries are allocated. It changes the requirement from "standard required" to "RFC Required". It does not change the list of algorithms that are recommended or required for DNSSEC implementations. [STANDARDS-TRACK] | November 2010 Status: PROPOSED STANDARD Autor: P. Hoffman |
| RFC6015 RTP Payload Format for 1-D Interleaved Parity Forward Error Correction (FEC) This document defines a new RTP payload format for the Forward Error Correction (FEC) that is generated by the 1-D interleaved parity code from a source media encapsulated in RTP. The 1-D interleaved parity code is a systematic code, where a number of repair symbols are generated from a set of source symbols and sent in a repair flow separate from the source flow that carries the source symbols. The 1-D interleaved parity code offers a good protection against bursty packet losses at a cost of reasonable complexity. The new payload format defined in this document should only be used (with some exceptions) as a part of the Digital Video Broadcasting-IPTV (DVB- IPTV) Application-layer FEC specification. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: A. Begen |
| RFC6016 Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs RFC 4364 and RFC 4659 define an approach to building provider-provisioned Layer 3 VPNs (L3VPNs) for IPv4 and IPv6. It may be desirable to use Resource Reservation Protocol (RSVP) to perform admission control on the links between Customer Edge (CE) routers and Provider Edge (PE) routers. This document specifies procedures by which RSVP messages traveling from CE to CE across an L3VPN may be appropriately handled by PE routers so that admission control can be performed on PE-CE links. Optionally, admission control across the provider's backbone may also be supported. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: B. Davie, F. Le Faucheur, A. Narayanan |
| RFC6017 Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field With the maturity of the Electronic Data Interchange - Internet Integration (EDIINT) standards of AS1, AS2, and AS3, applications and additional features are being built upon the basic secure transport functionality. These features are not necessarily supported by all EDIINT applications and could cause potential problems with implementations. The EDIINT-Features header field provides a means to resolve these problems and support new functionality. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2010 Status: INFORMATIONAL Autor: K. Meadors |
| RFC6018 IPv4 and IPv6 Greynets This note discusses a feature to support building Greynets for IPv4 and IPv6. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2010 Status: INFORMATIONAL Autor: F. Baker, W. Harrop, G. Armitage |
| RFC6019 BinaryTime: An Alternate Format for Representing Date and Time in ASN.1 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 5652. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: R. Housley |
| RFC6020 YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF) YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: M. Bjorklund |
| RFC6021 Common YANG Data Types This document introduces a collection of common data types to be used with the YANG data modeling language. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: J. Schoenwaelder |
| RFC6022 YANG Module for NETCONF Monitoring This document defines a Network Configuration Protocol (NETCONF) data model to be used to monitor the NETCONF protocol. The monitoring data model includes information about NETCONF datastores, sessions, locks, and statistics. This data facilitates the management of a NETCONF server. This document also defines methods for NETCONF clients to discover data models supported by a NETCONF server and defines a new NETCONF <get-schema> operation to retrieve them. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: M. Scott, M. Bjorklund |
| RFC6023 A Childless Initiation of the Internet Key Exchange Version 2 (IKEv2) Security Association (SA) This document describes an extension to the Internet Key Exchange version 2 (IKEv2) protocol that allows an IKEv2 Security Association (SA) to be created and authenticated without generating a Child SA. This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. | October 2010 Status: EXPERIMENTAL Autor: Y. Nir, H. Tschofenig, H. Deng, R. Singh |
| RFC6024 Trust Anchor Management Requirements A trust anchor represents an authoritative entity via a public key and associated data. The public key is used to verify digital signatures, and the associated data is used to constrain the types of information for which the trust anchor is authoritative. A relying party uses trust anchors to determine if a digitally signed object is valid by verifying a digital signature using the trust anchor's public key, and by enforcing the constraints expressed in the associated data for the trust anchor. This document describes some of the problems associated with the lack of a standard trust anchor management mechanism and defines requirements for data formats and push-based protocols designed to address these problems. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: R. Reddy, C. Wallace |
| RFC6025 ASN.1 Translation Abstract Syntax Notation One (ASN.1) is widely used throughout the IETF Security Area and has been for many years. Some specifications were written using a now deprecated version of ASN.1 and some were written using the current version of ASN.1. Not all ASN.1 compilers support both older and current syntax. This document is intended to provide guidance to specification authors and to implementers converting ASN.1 modules from one version of ASN.1 to another version without causing changes to the "bits on the wire". This document does not provide a comprehensive tutorial of any version of ASN.1. Instead, it addresses ASN.1 features that are used in IETF Security Area specifications with a focus on items that vary with the ASN.1 version. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: C. Wallace, C. Gardiner |
| RFC6026 Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests This document normatively updates RFC 3261, the Session Initiation Protocol (SIP), to address an error in the specified handling of success (2xx class) responses to INVITE requests. Elements following RFC 3261 exactly will misidentify retransmissions of the request as a new, unassociated request. The correction involves modifying the INVITE transaction state machines. The correction also changes the way responses that cannot be matched to an existing transaction are handled to address a security risk. [STANDARDS-TRACK] | September 2010 Status: PROPOSED STANDARD Autor: R. Sparks, T. Zourzouvillys |
| RFC6027 IPsec Cluster Problem Statement This document defines the terminology, problem statement, and requirements for implementing Internet Key Exchange (IKE) and IPsec on clusters. It also describes gaps in existing standards and their implementation that need to be filled in order to allow peers to interoperate with clusters from different vendors. Agreed upon terminology, problem statement, and requirements will allow IETF working groups to consider development of IPsec/IKEv2 mechanisms to simplify cluster implementations. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: Y. Nir |
| RFC6028 Host Identity Protocol (HIP) Multi-Hop Routing Extension This document specifies two extensions to the Host Identity Protocol (HIP) to implement multi-hop routing. The first extension allows implementing source routing in HIP. That is, a node sending a HIP packet can define a set of nodes that the HIP packet should traverse. The second extension allows a HIP packet to carry and record the list of nodes that forwarded it. This document defines an Experimental Protocol for the Internet community. | October 2010 Status: EXPERIMENTAL Autor: G. Camarillo, A. Keranen |
| RFC6029 A Survey on Research on the Application-Layer Traffic Optimization (ALTO) Problem A significant part of the Internet traffic today is generated by peer-to-peer (P2P) applications used originally for file sharing, and more recently for real-time communications and live media streaming. Such applications discover a route to each other through an overlay network with little knowledge of the underlying network topology. As a result, they may choose peers based on information deduced from empirical measurements, which can lead to suboptimal choices. This document, a product of the P2P Research Group, presents a survey of existing literature on discovering and using network topology information for Application-Layer Traffic Optimization. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: I. Rimac, V. Hilt, M. Tomsu, V. Gurbani, E. Marocco |
| RFC6030 Portable Symmetric Key Container (PSKC) This document specifies a symmetric key format for the transport and provisioning of symmetric keys to different types of crypto modules. For example, One-Time Password (OTP) shared secrets or symmetric cryptographic keys to strong authentication devices. A standard key transport format enables enterprises to deploy best-of-breed solutions combining components from different vendors into the same infrastructure. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: P. Hoyer, M. Pei, S. Machani |
| RFC6031 Cryptographic Message Syntax (CMS) Symmetric Key Package Content Type This document defines the symmetric key format content type. It is transport independent. The Cryptographic Message Syntax (CMS) can be used to digitally sign, digest, authenticate, or encrypt this content type. [STANDARDS-TRACK] | December 2010 Status: PROPOSED STANDARD Autor: S. Turner, R. Housley |
| RFC6032 Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type This document defines the Cryptographic Message Syntax (CMS) encrypted key package content type, which can be used to encrypt a content that includes a key package, such as a symmetric key package or an asymmetric key package. It is transport independent. CMS can be used to digitally sign, digest, authenticate, or further encrypt this content type. It is designed to be used with the CMS Content Constraints (CCC) extension, which does not constrain the EncryptedData, EnvelopedData, and AuthEnvelopedData. [STANDARDS-TRACK] | December 2010 Status: PROPOSED STANDARD Autor: S. Turner, R. Housley |
| RFC6033 Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type This document describes the conventions for using several cryptographic algorithms with the Cryptographic Message Syntax (CMS) encrypted key package content type. Specifically, it includes conventions necessary to implement EnvelopedData, EncryptedData, and AuthEnvelopedData. [STANDARDS-TRACK] | December 2010 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC6034 Unicast-Prefix-Based IPv4 Multicast Addresses This specification defines an extension to the multicast addressing architecture of the IP Version 4 protocol. The extension presented in this document allows for unicast-prefix-based assignment of multicast addresses. By delegating multicast addresses at the same time as unicast prefixes, network operators will be able to identify their multicast addresses without needing to run an inter-domain allocation protocol. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: D. Thaler |
| RFC6035 Session Initiation Protocol Event Package for Voice Quality Reporting This document defines a Session Initiation Protocol (SIP) event package that enables the collection and reporting of metrics that measure the quality for Voice over Internet Protocol (VoIP) sessions. Voice call quality information derived from RTP Control Protocol Extended Reports (RTCP-XR) and call information from SIP is conveyed from a User Agent (UA) in a session, known as a reporter, to a third party, known as a collector. A registration for the application/ vq-rtcpxr media type is also included. [STANDARDS-TRACK] | November 2010 Status: PROPOSED STANDARD Autor: A. Pendleton, A. Clark, A. Johnston, H. Sinnreich |
| RFC6036 Emerging Service Provider Scenarios for IPv6 Deployment This document describes practices and plans that are emerging among Internet Service Providers for the deployment of IPv6 services. They are based on practical experience so far, as well as current plans and requirements, reported in a survey of a number of ISPs carried out in early 2010. This document identifies a number of technology gaps, but it does not make recommendations. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: B. Carpenter, S. Jiang |
| RFC6037 Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs This document describes the MVPN (Multicast in BGP/MPLS IP VPNs) solution designed and deployed by Cisco Systems. The procedures specified in this document are largely a subset of the generalized MVPN framework recently standardized by the IETF. However, as the deployment of the procedures specified herein predates the publication of IETF standards (in some cases by over five years), an implementation based on these procedures differs in some respects from a fully standards-compliant implementation. These differences are pointed out in the document. This document defines a Historic Document for the Internet community. | October 2010 Status: HISTORIC Autor: E. Rosen, Y. Cai, IJ. Wijnands |
| RFC6038 Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features This memo describes two closely related features for the core specification of the Two-Way Active Measurement Protocol (TWAMP): an optional capability where the responding host returns some of the command octets or padding octets to the sender, and an optional sender packet format that ensures equal test packet sizes are used in both directions. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: A. Morton, L. Ciavattone |
| RFC6039 Issues with Existing Cryptographic Protection Methods for Routing Protocols Routing protocols have been extended over time to use cryptographic mechanisms to ensure that data received from a neighboring router has not been modified in transit and actually originated from an authorized neighboring router. | October 2010 Status: INFORMATIONAL Autor: V. Manral, M. Bhatia, J. Jaeggli, R. White |
| RFC6040 Tunnelling of Explicit Congestion Notification This document redefines how the explicit congestion notification (ECN) field of the IP header should be constructed on entry to and exit from any IP-in-IP tunnel. On encapsulation, it updates RFC 3168 to bring all IP-in-IP tunnels (v4 or v6) into line with RFC 4301 IPsec ECN processing. On decapsulation, it updates both RFC 3168 and RFC 4301 to add new behaviours for previously unused combinations of inner and outer headers. The new rules ensure the ECN field is correctly propagated across a tunnel whether it is used to signal one or two severity levels of congestion; whereas before, only one severity level was supported. Tunnel endpoints can be updated in any order without affecting pre-existing uses of the ECN field, thus ensuring backward compatibility. Nonetheless, operators wanting to support two severity levels (e.g., for pre-congestion notification -- PCN) can require compliance with this new specification. A thorough analysis of the reasoning for these changes and the implications is included. In the unlikely event that the new rules do not meet a specific need, RFC 4774 gives guidance on designing alternate ECN semantics, and this document extends that to include tunnelling issues. [STANDARDS-TRACK] | November 2010 Status: PROPOSED STANDARD Autor: B. Briscoe |
| RFC6041 Forwarding and Control Element Separation (ForCES) Applicability Statement The Forwarding and Control Element Separation (ForCES) protocol defines a standard framework and mechanism for the interconnection between control elements and forwarding elements in IP routers and similar devices. In this document we describe the applicability of the ForCES model and protocol. We provide example deployment scenarios and functionality, as well as document applications that would be inappropriate for ForCES. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: A. Crouch, H. Khosravi, A. Doria, X. Wang, K. Ogawa |
| RFC6042 Transport Layer Security (TLS) Authorization Using KeyNote This document specifies the use of the KeyNote trust-management system as an authorization extension in the Transport Layer Security (TLS) Handshake Protocol, according to guidelines in RFC 5878. Extensions carried in the client and server hello messages confirm that both parties support the desired authorization data types. Then, if supported by both the client and the server, KeyNote credentials are exchanged in the supplemental data handshake message. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2010 Status: INFORMATIONAL Autor: A. Keromytis |
| RFC6043 MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY) The Multimedia Internet KEYing (MIKEY) specification describes a key management scheme for real-time applications. In this document, we note that the currently defined MIKEY modes are insufficient to address deployment scenarios built around a centralized key management service. Interest in such deployments is increasing. Therefore, a set of new MIKEY modes that work well in such scenarios are defined. The new modes use a trusted key management service and a ticket concept, similar to that in Kerberos. The new modes also support features used by many existing applications, where the exact identity of the other endpoint may not be known at the start of the communication session. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: J. Mattsson, T. Tian |
| RFC6044 Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol (SIP) Although the SIP History-Info header is the solution adopted in IETF, the non-standard Diversion header is nevertheless widely implemented and used for conveying call-diversion-related information in SIP signaling. | October 2010 Status: INFORMATIONAL Autor: M. Mohali |
| RFC6045 Real-time Inter-network Defense (RID) Network security incidents, such as system compromises, worms, viruses, phishing incidents, and denial of service, typically result in the loss of service, data, and resources both human and system. Network providers and Computer Security Incident Response Teams need to be equipped and ready to assist in communicating and tracing security incidents with tools and procedures in place before the occurrence of an attack. Real-time Inter-network Defense (RID) outlines a proactive inter-network communication method to facilitate sharing incident handling data while integrating existing detection, tracing, source identification, and mitigation mechanisms for a complete incident handling solution. Combining these capabilities in a communication system provides a way to achieve higher security levels on networks. Policy guidelines for handling incidents are recommended and can be agreed upon by a consortium using the security recommendations and considerations. | November 2010 Status: INFORMATIONAL Autor: K. Moriarty |
| RFC6046 Transport of Real-time Inter-network Defense (RID) Messages The Incident Object Description Exchange Format (IODEF) defines a common XML format for document exchange, and Real-time Inter-network Defense (RID) defines extensions to IODEF intended for the cooperative handling of security incidents within consortia of network operators and enterprises. This document specifies a transport protocol for RID based upon the passing of RID messages over HTTP/TLS (Transport Layer Security). This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2010 Status: INFORMATIONAL Autor: K. Moriarty, B. Trammell |
| RFC6047 iCalendar Message-Based Interoperability Protocol (iMIP) This document, "iCalendar Message-Based Interoperability Protocol (iMIP)", specifies a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to Internet email-based transports. Calendaring entries defined by the iCalendar Object Model (iCalendar) are wrapped using constructs from RFC 5322 and MIME (RFC 2045, RFC 2046, RFC 2047, and RFC 2049), and then transported over SMTP. [STANDARDS-TRACK] | December 2010 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC6048 Network News Transfer Protocol (NNTP) Additions to LIST Command This document defines a set of enhancements to the Network News Transfer Protocol (NNTP) that allow a client to request extended information from NNTP servers regarding server status, policy, and other aspects of local configuration. These enhancements are made as new keywords to the existing LIST capability described in RFC 3977. | November 2010 Status: PROPOSED STANDARD Autor: J. Elie |
| RFC6049 Spatial Composition of Metrics This memo utilizes IP performance metrics that are applicable to both complete paths and sub-paths, and it defines relationships to compose a complete path metric from the sub-path metrics with some accuracy with regard to the actual metrics. This is called "spatial composition" in RFC 2330. The memo refers to the framework for metric composition, and provides background and motivation for combining metrics to derive others. The descriptions of several composed metrics and statistics follow. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: A. Morton, E. Stephan |
| RFC6050 A Session Initiation Protocol (SIP) Extension for the Identification of Services This document describes private extensions to the Session Initiation Protocol (SIP) that enable a network of trusted SIP servers to assert the service of authenticated users. The use of these extensions is only applicable inside an administrative domain with previously agreed-upon policies for generation, transport, and usage of such information. This document does NOT offer a general service identification model suitable for use between different trust domains or for use in the Internet at large. | November 2010 Status: INFORMATIONAL Autor: K. Drage |
| RFC6051 Rapid Synchronisation of RTP Flows This memo outlines how RTP sessions are synchronised, and discusses how rapidly such synchronisation can occur. We show that most RTP sessions can be synchronised immediately, but that the use of video switching multipoint conference units (MCUs) or large source-specific multicast (SSM) groups can greatly increase the synchronisation delay. This increase in delay can be unacceptable to some applications that use layered and/or multi-description codecs. | November 2010 Status: PROPOSED STANDARD Autor: C. Perkins, T. Schierl |
| RFC6052 IPv6 Addressing of IPv4/IPv6 Translators This document discusses the algorithmic translation of an IPv6 address to a corresponding IPv4 address, and vice versa, using only statically configured information. It defines a well-known prefix for use in algorithmic translations, while allowing organizations to also use network-specific prefixes when appropriate. Algorithmic translation is used in IPv4/IPv6 translators, as well as other types of proxies and gateways (e.g., for DNS) used in IPv4/IPv6 scenarios. [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: C. Bao, C. Huitema, M. Bagnulo, M. Boucadair, X. Li |
| RFC6053 Implementation Report for Forwarding and Control Element Separation (ForCES) Forwarding and Control Element Separation (ForCES) defines an architectural framework and associated protocols to standardize information exchange between the control plane and the forwarding plane in a ForCES network element (ForCES NE). RFC 3654 has defined the ForCES requirements, and RFC 3746 has defined the ForCES framework. | November 2010 Status: INFORMATIONAL Autor: E. Haleplidis, K. Ogawa, W. Wang, J. Hadi Salim |
| RFC6054 Using Counter Modes with Encapsulating Security Payload (ESP) and Authentication Header (AH) to Protect Group Traffic Counter modes have been defined for block ciphers such as the Advanced Encryption Standard (AES). Counter modes use a counter, which is typically assumed to be incremented by a single sender. This memo describes the use of counter modes when applied to the Encapsulating Security Payload (ESP) and Authentication Header (AH) in multiple-sender group applications. [STANDARDS-TRACK] | November 2010 Status: PROPOSED STANDARD Autor: D. McGrew, B. Weis |
| RFC6055 IAB Thoughts on Encodings for Internationalized Domain Names This document explores issues with Internationalized Domain Names (IDNs) that result from the use of various encoding schemes such as UTF-8 and the ASCII-Compatible Encoding produced by the Punycode algorithm. It focuses on the importance of agreeing on a single encoding and how complicated the state of affairs ends up being as a result of using different encodings today. | February 2011 Status: INFORMATIONAL Autor: D. Thaler, J. Klensin, S. Cheshire |
| RFC6056 Recommendations for Transport-Protocol Port Randomization During the last few years, awareness has been raised about a number of "blind" attacks that can be performed against the Transmission Control Protocol (TCP) and similar protocols. The consequences of these attacks range from throughput reduction to broken connections or data corruption. These attacks rely on the attacker's ability to guess or know the five-tuple (Protocol, Source Address, Destination Address, Source Port, Destination Port) that identifies the transport protocol instance to be attacked. This document describes a number of simple and efficient methods for the selection of the client port number, such that the possibility of an attacker guessing the exact value is reduced. While this is not a replacement for cryptographic methods for protecting the transport-protocol instance, the aforementioned port selection algorithms provide improved security with very little effort and without any key management overhead. The algorithms described in this document are local policies that may be incrementally deployed and that do not violate the specifications of any of the transport protocols that may benefit from them, such as TCP, UDP, UDP-lite, Stream Control Transmission Protocol (SCTP), Datagram Congestion Control Protocol (DCCP), and RTP (provided that the RTP application explicitly signals the RTP and RTCP port numbers). This memo documents an Internet Best Current Practice. | January 2011 Status: BEST CURRENT PRACTICE Autor: M. Larsen, F. Gont |
| RFC6057 Comcast's Protocol-Agnostic Congestion Management System This document describes the congestion management system of Comcast Cable, a large cable broadband Internet Service Provider (ISP) in the U.S. Comcast completed deployment of this congestion management system on December 31, 2008. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2010 Status: INFORMATIONAL Autor: C. Bastian, T. Klieber, J. Livingood, J. Mills, R. Woundy |
| RFC6058 Transient Binding for Proxy Mobile IPv6 This document specifies a mechanism that enhances Proxy Mobile IPv6 protocol signaling to support the creation of a transient binding cache entry that is used to optimize the performance of dual radio handover, as well as single radio handover. This mechanism is applicable to the mobile node's inter-MAG (Mobility Access Gateway) handover while using a single interface or different interfaces. The handover problem space using the Proxy Mobile IPv6 base protocol is analyzed and the use of transient binding cache entries at the local mobility anchor is described. The specified extension to the Proxy Mobile IPv6 protocol ensures optimized forwarding of downlink as well as uplink packets between mobile nodes and the network infrastructure and avoids superfluous packet forwarding delay or even packet loss. This document defines an Experimental Protocol for the Internet community. | March 2011 Status: EXPERIMENTAL Autor: M. Liebsch, A. Muhanna, O. Blume |
| RFC6059 Simple Procedures for Detecting Network Attachment in IPv6 Detecting Network Attachment allows hosts to assess if its existing addressing or routing configuration is valid for a newly connected network. This document provides simple procedures for Detecting Network Attachment in IPv6 hosts, and procedures for routers to support such services. [STANDARDS-TRACK] | November 2010 Status: PROPOSED STANDARD Autor: S. Krishnan, G. Daley |
| RFC6060 Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE) This specification is complementary to the GMPLS Ethernet Label Switching Architecture and Framework and describes the technology-specific aspects of GMPLS control for Provider Backbone Bridge Traffic Engineering (PBB-TE). The necessary GMPLS extensions and mechanisms are described to establish Ethernet PBB-TE point-to-point (P2P) and point-to-multipoint (P2MP) connections. This document supports, but does not modify, the standard IEEE data plane. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: D. Fedyk, H. Shah, N. Bitar, A. Takacs |
| RFC6061 Uniform Resource Name (URN) Namespace for the National Emergency Number Association (NENA) This document describes the Namespace Identifier (NID) "nena" for Uniform Resource Name (URN) resources published by the National Emergency Number Association (NENA). NENA defines and manages resources that utilize this URN model. Management activities for these and other resource types are provided by the NENA Registry System (NRS). This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2011 Status: INFORMATIONAL Autor: B. Rosen |
| RFC6062 Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations This specification defines an extension of Traversal Using Relays around NAT (TURN), a relay protocol for Network Address Translator (NAT) traversal. This extension allows a TURN client to request TCP allocations, and defines new requests and indications for the TURN server to open and accept TCP connections with the client\'s peers. TURN and this extension both purposefully restrict the ways in which the relayed address can be used. In particular, it prevents users from running general-purpose servers from ports obtained from the TURN server. [STANDARDS-TRACK] | November 2010 Status: PROPOSED STANDARD Autor: S. Perreault, J. Rosenberg |
| RFC6063 Dynamic Symmetric Key Provisioning Protocol (DSKPP) The Dynamic Symmetric Key Provisioning Protocol (DSKPP) is a client-server protocol for initialization (and configuration) of symmetric keys to locally and remotely accessible cryptographic modules. The protocol can be run with or without private key capabilities in the cryptographic modules and with or without an established public key infrastructure. | December 2010 Status: PROPOSED STANDARD Autor: A. Doherty, M. Pei, S. Machani, M. Nystrom |
| RFC6064 SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming Service and Multimedia Broadcast/Multicast Service The Packet-switched Streaming Service (PSS) and the Multimedia Broadcast/Multicast Service (MBMS) defined by 3GPP use the Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP) with some extensions. This document provides information about these extensions and registers the RTSP and SDP extensions with IANA. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2011 Status: INFORMATIONAL Autor: M. Westerlund, P. Frojdh |
| RFC6065 Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group Mappings This memo defines a portion of the Management Information Base (MIB) for use with network management protocols. It describes the use of information provided by Authentication, Authorization, and Accounting (AAA) services, such as the Remote Authentication Dial-In User Service (RADIUS), to dynamically update user-to-group mappings in the View-based Access Control Model (VACM). [STANDARDS-TRACK] | December 2010 Status: PROPOSED STANDARD Autor: K. Narayan, D. Nelson, R. Presuhn |
| RFC6066 Transport Layer Security (TLS) Extensions: Extension Definitions This document provides specifications for existing TLS extensions. It is a companion document for RFC 5246, "The Transport Layer Security (TLS) Protocol Version 1.2". The extensions specified are server_name, max_fragment_length, client_certificate_url, trusted_ca_keys, truncated_hmac, and status_request. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd |
| RFC6067 BCP 47 Extension U This document specifies an Extension to BCP 47 that provides subtags that specify language and/or locale-based behavior or refinements to language tags, according to work done by the Unicode Consortium. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2010 Status: INFORMATIONAL Autor: M. Davis, A. Phillips, Y. Umaoka |
| RFC6068 The 'mailto' URI Scheme This document defines the format of Uniform Resource Identifiers (URIs) to identify resources that are reached using Internet mail. It adds better internationalization and compatibility with Internationalized Resource Identifiers (IRIs; RFC 3987) to the previous syntax of 'mailto' URIs (RFC 2368). [STANDARDS-TRACK] | October 2010 Status: PROPOSED STANDARD Autor: M. Duerst, L. Masinter, J. Zawinski |
| RFC6069 Making TCP More Robust to Long Connectivity Disruptions (TCP-LCD) Disruptions in end-to-end path connectivity, which last longer than one retransmission timeout, cause suboptimal TCP performance. The reason for this performance degradation is that TCP interprets segment loss induced by long connectivity disruptions as a sign of congestion, resulting in repeated retransmission timer backoffs. This, in turn, leads to a delayed detection of the re-establishment of the connection since TCP waits for the next retransmission timeout before it attempts a retransmission. | December 2010 Status: EXPERIMENTAL Autor: A. Zimmermann, A. Hannemann |
| RFC6070 PKCS #5: Password-Based Key Derivation Function 2 (PBKDF2) Test Vectors This document contains test vectors for the Public-Key Cryptography Standards (PKCS) #5 Password-Based Key Derivation Function 2 (PBKDF2) with the Hash-based Message Authentication Code (HMAC) Secure Hash Algorithm (SHA-1) pseudorandom function. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2011 Status: INFORMATIONAL Autor: S. Josefsson |
| RFC6071 IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap Over the past few years, the number of RFCs that define and use IPsec and Internet Key Exchange (IKE) has greatly proliferated. This is complicated by the fact that these RFCs originate from numerous IETF working groups: the original IPsec WG, its various spin-offs, and other WGs that use IPsec and/or IKE to protect their protocols' traffic. | February 2011 Status: INFORMATIONAL Autor: S. Frankel, S. Krishnan |
| RFC6072 Certificate Management Service for the Session Initiation Protocol (SIP) This document defines a credential service that allows Session Initiation Protocol (SIP) User Agents (UAs) to use a SIP event package to discover the certificates of other users. This mechanism allows User Agents that want to contact a given Address-of-Record (AOR) to retrieve that AOR's certificate by subscribing to the credential service, which returns an authenticated response containing that certificate. The credential service also allows users to store and retrieve their own certificates and private keys. [STANDARDS-TRACK] | February 2011 Status: PROPOSED STANDARD Autor: C. Jennings, J. Fischl |
| RFC6073 Segmented Pseudowire This document describes how to connect pseudowires (PWs) between different Packet Switched Network (PSN) domains or between two or more distinct PW control plane domains, where a control plane domain uses a common control plane protocol or instance of that protocol for a given PW. The different PW control plane domains may belong to independent autonomous systems, or the PSN technology is heterogeneous, or a PW might need to be aggregated at a specific PSN point. The PW packet data units are simply switched from one PW to another without changing the PW payload. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: L. Martini, C. Metz, T. Nadeau, M. Bocci, M. Aissaoui |
| RFC6074 Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs) Provider Provisioned Layer 2 Virtual Private Networks (L2VPNs) may have different "provisioning models", i.e., models for what information needs to be configured in what entities. Once configured, the provisioning information is distributed by a "discovery process". When the discovery process is complete, a signaling protocol is automatically invoked to set up the mesh of pseudowires (PWs) that form the (virtual) backbone of the L2VPN. This document specifies a number of L2VPN provisioning models, and further specifies the semantic structure of the endpoint identifiers required by each model. It discusses the distribution of these identifiers by the discovery process, especially when discovery is based on the Border Gateway Protocol (BGP). It then specifies how the endpoint identifiers are carried in the two signaling protocols that are used to set up PWs, the Label Distribution Protocol (LDP), and the Layer 2 Tunneling Protocol version 3 (L2TPv3). [STANDARDS- TRACK] | January 2011 Status: PROPOSED STANDARD Autor: E. Rosen, B. Davie, V. Radoaca, W. Luo |
| RFC6075 The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry The original Application Configuration Access Protocol (ACAP) specification included a vendor registry now used in other protocols. This document updates the description of this registry, removing the need for a direct normative reference to ACAP and removing ambiguity. [STANDARDS-TRACK] | December 2010 Status: PROPOSED STANDARD Autor: D. Cridland |
| RFC6076 Basic Telephony SIP End-to-End Performance Metrics This document defines a set of metrics and their usage to evaluate the performance of end-to-end Session Initiation Protocol (SIP) for telephony services in both production and testing environments. The purpose of this document is to combine a standard set of common metrics, allowing interoperable performance measurements, easing the comparison of industry implementations. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: D. Malas, A. Morton |
| RFC6077 Open Research Issues in Internet Congestion Control This document describes some of the open problems in Internet congestion control that are known today. This includes several new challenges that are becoming important as the network grows, as well as some issues that have been known for many years. These challenges are generally considered to be open research topics that may require more study or application of innovative techniques before Internet-scale solutions can be confidently engineered and deployed. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: D. Papadimitriou, M. Welzl, M. Scharf, B. Briscoe |
| RFC6078 Host Identity Protocol (HIP) Immediate Carriage and Conveyance of Upper-Layer Protocol Signaling (HICCUPS) This document defines a new Host Identity Protocol (HIP) packet type called DATA. HIP DATA packets are used to reliably convey authenticated arbitrary protocol messages over various overlay networks. This document defines an Experimental Protocol for the Internet community. | January 2011 Status: EXPERIMENTAL Autor: G. Camarillo, J. Melen |
| RFC6079 HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment (BONE) This document specifies a framework to build HIP-based (Host Identity Protocol) overlay networks. This framework uses HIP to perform connection management. Other functions, such as data storage and retrieval or overlay maintenance, are implemented using protocols other than HIP. These protocols are loosely referred to as "peer protocols". This document defines an Experimental Protocol for the Internet community. | January 2011 Status: EXPERIMENTAL Autor: G. Camarillo, P. Nikander, J. Hautakorpi, A. Keranen, A. Johnston |
| RFC6080 A Framework for Session Initiation Protocol User Agent Profile Delivery This document specifies a framework to enable configuration of Session Initiation Protocol (SIP) user agents (UAs) in SIP deployments. The framework provides a means to deliver profile data that user agents need to be functional, automatically and with minimal or no User and Administrative intervention. The framework describes how SIP user agents can discover sources, request profiles, and receive notifications related to profile modifications. As part of this framework, a new SIP event package is defined for notification of profile changes. The framework provides minimal data retrieval options to ensure interoperability. The framework does not include specification of the profile data within its scope. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: D. Petrie, S. Channabasappa |
| RFC6081 Teredo Extensions This document specifies a set of extensions to the Teredo protocol. These extensions provide additional capabilities to Teredo, including support for more types of Network Address Translations (NATs) and support for more efficient communication. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: D. Thaler |
| RFC6082 Deprecating Unicode Language Tag Characters: RFC 2482 is Historic RFC 2482, "Language Tagging in Unicode Plain Text", describes a mechanism for using special Unicode language tag characters to identify languages when needed without more general markup such as that provided by XML. The Unicode Consortium has deprecated that facility and strongly recommends against its use. RFC 2482 has been moved to Historic status to reduce the possibility that Internet implementers would consider that system an appropriate mechanism for identifying languages. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2010 Status: INFORMATIONAL Autor: K. Whistler, G. Adams, M. Duerst, R. Presuhn, J. Klensin |
| RFC6083 Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP) This document describes the usage of the Datagram Transport Layer Security (DTLS) protocol over the Stream Control Transmission Protocol (SCTP). | January 2011 Status: PROPOSED STANDARD Autor: M. Tuexen, R. Seggelmann, E. Rescorla |
| RFC6084 General Internet Signaling Transport (GIST) over Stream Control Transmission Protocol (SCTP) and Datagram Transport Layer Security (DTLS) The General Internet Signaling Transport (GIST) protocol currently uses TCP or Transport Layer Security (TLS) over TCP for Connection mode operation. This document describes the usage of GIST over the Stream Control Transmission Protocol (SCTP) and Datagram Transport Layer Security (DTLS). This document defines an Experimental Protocol for the Internet community. | January 2011 Status: EXPERIMENTAL Autor: X. Fu, C. Dickmann, J. Crowcroft |
| RFC6085 Address Mapping of IPv6 Multicast Packets on Ethernet When transmitting an IPv6 packet with a multicast destination address, the IPv6 destination address is mapped to an Ethernet link-layer multicast address. This document clarifies that a mapping of an IPv6 packet with a multicast destination address may in some circumstances map to an Ethernet link-layer unicast address. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: S. Gundavelli, M. Townsley, O. Troan, W. Dec |
| RFC6086 Session Initiation Protocol (SIP) INFO Method and Package Framework This document defines a method, INFO, for the Session Initiation Protocol (SIP), and an Info Package mechanism. This document obsoletes RFC 2976. For backward compatibility, this document also specifies a "legacy" mode of usage of the INFO method that is compatible with the usage previously defined in RFC 2976, referred to as "legacy INFO Usage" in this document. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: C. Holmberg, E. Burger, H. Kaplan |
| RFC6087 Guidelines for Authors and Reviewers of YANG Data Model Documents This memo provides guidelines for authors and reviewers of Standards Track specifications containing YANG data model modules. Applicable portions may be used as a basis for reviews of other YANG data model documents. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) implementations that utilize YANG data model modules. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2011 Status: INFORMATIONAL Autor: A. Bierman |
| RFC6088 Traffic Selectors for Flow Bindings This document defines binary formats for IPv4 and IPv6 traffic selectors to be used in conjunction with flow bindings for Mobile IPv6. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: G. Tsirtsis, G. Giarreta, H. Soliman, N. Montavont |
| RFC6089 Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support This document introduces extensions to Mobile IPv6 that allow nodes to bind one or more flows to a care-of address. These extensions allow multihomed nodes to instruct home agents and other Mobile IPv6 entities to direct inbound flows to specific addresses. [STANDARDS- TRACK] | January 2011 Status: PROPOSED STANDARD Autor: G. Tsirtsis, H. Soliman, N. Montavont, G. Giaretta, K. Kuladinithi |
| RFC6090 Fundamental Elliptic Curve Cryptography Algorithms This note describes the fundamental algorithms of Elliptic Curve Cryptography (ECC) as they were defined in some seminal references from 1994 and earlier. These descriptions may be useful for implementing the fundamental algorithms without using any of the specialized methods that were developed in following years. Only elliptic curves defined over fields of characteristic greater than three are in scope; these curves are those used in Suite B. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: D. McGrew, K. Igoe, M. Salter |
| RFC6091 Using OpenPGP Keys for Transport Layer Security (TLS) Authentication This memo defines Transport Layer Security (TLS) extensions and associated semantics that allow clients and servers to negotiate the use of OpenPGP certificates for a TLS session, and specifies how to transport OpenPGP certificates via TLS. It also defines the registry for non-X.509 certificate types. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: N. Mavrogiannopoulos, D. Gillmor |
| RFC6092 Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service This document identifies a set of recommendations for the makers of devices and describes how to provide for "simple security" capabilities at the perimeter of local-area IPv6 networks in Internet-enabled homes and small offices. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2011 Status: INFORMATIONAL Autor: J. Woodyatt |
| RFC6093 On the Implementation of the TCP Urgent Mechanism This document analyzes how current TCP implementations process TCP urgent indications and how the behavior of some widely deployed middleboxes affects how end systems process urgent indications. This document updates the relevant specifications such that they accommodate current practice in processing TCP urgent indications, raises awareness about the reliability of TCP urgent indications in the Internet, and recommends against the use of urgent indications (but provides advice to applications that do). [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: F. Gont, A. Yourtchenko |
| RFC6094 Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols The routing protocols Open Shortest Path First version 2 (OSPFv2), Intermediate System to Intermediate System (IS-IS), and Routing Information Protocol (RIP) currently define cleartext and MD5 (Message Digest 5) methods for authenticating protocol packets. Recently, effort has been made to add support for the SHA (Secure Hash Algorithm) family of hash functions for the purpose of authenticating routing protocol packets for RIP, IS-IS, and OSPF. | February 2011 Status: INFORMATIONAL Autor: M. Bhatia, V. Manral |
| RFC6095 Extending YANG with Language Abstractions YANG -- the Network Configuration Protocol (NETCONF) Data Modeling Language -- supports modeling of a tree of data elements that represent the configuration and runtime status of a particular network element managed via NETCONF. This memo suggests enhancing YANG with supplementary modeling features and language abstractions with the aim to improve the model extensibility and reuse. This document defines an Experimental Protocol for the Internet community. | March 2011 Status: EXPERIMENTAL Autor: B. Linowski, M. Ersue, S. Kuryla |
| RFC6096 Stream Control Transmission Protocol (SCTP) Chunk Flags Registration This document defines the procedure for registering chunk flags with the Internet Assigned Numbers Authority (IANA) for the Stream Control Transmission Protocol (SCTP). It updates RFC 4960 and also defines the IANA registry for contents for currently defined chunk types. It does not change SCTP in any other way. [STANDARDS-TRACK] | January 2011 Status: PROPOSED STANDARD Autor: M. Tuexen, R. Stewart |
| RFC6097 Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6 Large Proxy Mobile IPv6 deployments would benefit from a functionality where a Mobile Access Gateway could dynamically discover a Local Mobility Anchor for a Mobile Node attaching to a Proxy Mobile IPv6 domain. The purpose of the dynamic discovery functionality is to reduce the amount of static configuration in the Mobile Access Gateway. This document describes several possible dynamic Local Mobility Anchor discovery solutions. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: J. Korhonen, V. Devarapalli |
| RFC6101 The Secure Sockets Layer (SSL) Protocol Version 3.0 This document is published as a historical record of the SSL 3.0 protocol. The original Abstract follows. | August 2011 Status: HISTORIC Autor: A. Freier, P. Karlton, P. Kocher |
| RFC6104 Rogue IPv6 Router Advertisement Problem Statement When deploying IPv6, whether IPv6-only or dual-stack, routers are configured to send IPv6 Router Advertisements (RAs) to convey information to nodes that enable them to autoconfigure on the network. This information includes the implied default router address taken from the observed source address of the RA message, as well as on-link prefix information. However, unintended misconfigurations by users or administrators, or possibly malicious attacks on the network, may lead to bogus RAs being present, which in turn can cause operational problems for hosts on the network. In this document, we summarise the scenarios in which rogue RAs may be observed and present a list of possible solutions to the problem. We focus on the unintended causes of rogue RAs in the text. The goal of this text is to be Informational, and as such to present a framework around which solutions can be proposed and discussed. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: T. Chown, S. Venaas |
| RFC6105 IPv6 Router Advertisement Guard Routed protocols are often susceptible to spoof attacks. The canonical solution for IPv6 is Secure Neighbor Discovery (SEND), a solution that is non-trivial to deploy. This document proposes a light-weight alternative and complement to SEND based on filtering in the layer-2 network fabric, using a variety of filtering criteria, including, for example, SEND status. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: E. Levy-Abegnoli, G. Van de Velde, C. Popoviciu, J. Mohacsi |
| RFC6106 IPv6 Router Advertisement Options for DNS Configuration This document specifies IPv6 Router Advertisement options to allow IPv6 routers to advertise a list of DNS recursive server addresses and a DNS Search List to IPv6 hosts. [STANDARDS-TRACK] | November 2010 Status: PROPOSED STANDARD Autor: J. Jeong, S. Park, L. Beloeil, S. Madanapalli |
| RFC6107 Procedures for Dynamically Signaled Hierarchical Label Switched Paths Label Switched Paths (LSPs) set up in Multiprotocol Label Switching (MPLS) or Generalized MPLS (GMPLS) networks can be used to form links to carry traffic in those networks or in other (client) networks. | February 2011 Status: PROPOSED STANDARD Autor: K. Shiomoto, A. Farrel |
| RFC6108 Comcast's Web Notification System Design The objective of this document is to describe a method of providing critical end-user notifications to web browsers, which has been deployed by Comcast, an Internet Service Provider (ISP). Such a notification system is being used to provide near-immediate notifications to customers, such as to warn them that their traffic exhibits patterns that are indicative of malware or virus infection. There are other proprietary systems that can perform such notifications, but those systems utilize Deep Packet Inspection (DPI) technology. In contrast to DPI, this document describes a system that does not rely upon DPI, and is instead based in open IETF standards and open source applications. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: C. Chung, A. Kasyanov, J. Livingood, N. Mody, B. Van Lieu |
| RFC6109 La Posta Elettronica Certificata - Italian Certified Electronic Mail Since 1997, the Italian laws have recognized electronic delivery systems as legally usable. In 2005, after two years of technical tests, the characteristics of an official electronic delivery service, named certified electronic mail (in Italian "Posta Elettronica Certificata") were defined, giving the system legal standing. | April 2011 Status: INFORMATIONAL Autor: C. Petrucci, F. Gennai, A. Shahin, A. Vinciarelli |
| RFC6110 Mapping YANG to Document Schema Definition Languages and Validating NETCONF Content This document specifies the mapping rules for translating YANG data models into Document Schema Definition Languages (DSDL), a coordinated set of XML schema languages standardized as ISO/IEC 19757. The following DSDL schema languages are addressed by the mapping: Regular Language for XML Next Generation (RELAX NG), Schematron, and Schematron and Document Schema Renaming Language (DSRL). The mapping takes one or more YANG modules and produces a set of DSDL schemas for a selected target document type -- datastore content, Network Configuration Protocol (NETCONF) messages, etc. Procedures for schema-based validation of such documents are also discussed. [STANDARDS-TRACK] | February 2011 Status: PROPOSED STANDARD Autor: L. Lhotka |
| RFC6111 Additional Kerberos Naming Constraints This document defines new naming constraints for well-known Kerberos principal names and well-known Kerberos realm names. [STANDARDS- TRACK] | April 2011 Status: PROPOSED STANDARD Autor: L. Zhu |
| RFC6112 Anonymity Support for Kerberos This document defines extensions to the Kerberos protocol to allow a Kerberos client to securely communicate with a Kerberos application service without revealing its identity, or without revealing more than its Kerberos realm. It also defines extensions that allow a Kerberos client to obtain anonymous credentials without revealing its identity to the Kerberos Key Distribution Center (KDC). This document updates RFCs 4120, 4121, and 4556. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: L. Zhu, P. Leach, S. Hartman |
| RFC6113 A Generalized Framework for Kerberos Pre-Authentication Kerberos is a protocol for verifying the identity of principals (e.g., a workstation user or a network server) on an open network. The Kerberos protocol provides a facility called pre-authentication. Pre-authentication mechanisms can use this facility to extend the Kerberos protocol and prove the identity of a principal. | April 2011 Status: PROPOSED STANDARD Autor: S. Hartman, L. Zhu |
| RFC6114 The 128-Bit Blockcipher CLEFIA This document describes the specification of the blockcipher CLEFIA. CLEFIA is a 128-bit blockcipher, with key lengths of 128, 192, and 256 bits, which is compatible with the interface of the Advanced Encryption Standard (AES). The algorithm of CLEFIA was published in 2007, and its security has been scrutinized in the public community. CLEFIA is one of the new-generation lightweight blockcipher algorithms designed after AES. Among them, CLEFIA offers high performance in software and hardware as well as lightweight implementation in hardware. CLEFIA will be of benefit to the Internet, which will be connected to more distributed and constrained devices. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: M. Katagi, S. Moriai |
| RFC6115 Recommendation for a Routing Architecture It is commonly recognized that the Internet routing and addressing architecture is facing challenges in scalability, multihoming, and inter-domain traffic engineering. This document presents, as a recommendation of future directions for the IETF, solutions that could aid the future scalability of the Internet. To this end, this document surveys many of the proposals that were brought forward for discussion in this activity, as well as some of the subsequent analysis and the architectural recommendation of the chairs. This document is a product of the Routing Research Group. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: T. Li |
| RFC6116 The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) This document discusses the use of the Domain Name System (DNS) for storage of data associated with E.164 numbers, and for resolving those numbers into URIs that can be used (for example) in telephony call setup. This document also describes how the DNS can be used to identify the services associated with an E.164 number. This document obsoletes RFC 3761. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: S. Bradner, L. Conroy, K. Fujiwara |
| RFC6117 IANA Registration of Enumservices: Guide, Template, and IANA Considerations This document specifies a revision of the IANA Registration Guidelines for Enumservices, describes corresponding registration procedures, and provides a guideline for creating Enumservice Specifications. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: B. Hoeneisen, A. Mayrhofer, J. Livingood |
| RFC6118 Update of Legacy IANA Registrations of Enumservices This document revises all Enumservices that were IANA registered under the now obsolete specification of the Enumservice registry defined in RFC 3761. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: B. Hoeneisen, A. Mayrhofer |
| RFC6119 IPv6 Traffic Engineering in IS-IS This document specifies a method for exchanging IPv6 traffic engineering information using the IS-IS routing protocol. This information enables routers in an IS-IS network to calculate traffic-engineered routes using IPv6 addresses. [STANDARDS-TRACK] | February 2011 Status: PROPOSED STANDARD Autor: J. Harrison, J. Berger, M. Bartlett |
| RFC6120 Extensible Messaging and Presence Protocol (XMPP): Core The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities. This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions. This document obsoletes RFC 3920. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC6121 Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence This document defines extensions to core features of the Extensible Messaging and Presence Protocol (XMPP) that provide basic instant messaging (IM) and presence functionality in conformance with the requirements in RFC 2779. This document obsoletes RFC 3921. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC6122 Extensible Messaging and Presence Protocol (XMPP): Address Format This document defines the format for addresses used in the Extensible Messaging and Presence Protocol (XMPP), including support for non-ASCII characters. This document updates RFC 3920. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC6123 Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts It has often been the case that manageability considerations have been retrofitted to protocols after they have been specified, standardized, implemented, or deployed. This is sub-optimal. Similarly, new protocols or protocol extensions are frequently designed without due consideration of manageability requirements. | February 2011 Status: HISTORIC Autor: A. Farrel |
| RFC6124 An EAP Authentication Method Based on the Encrypted Key Exchange (EKE) Protocol The Extensible Authentication Protocol (EAP) describes a framework that allows the use of multiple authentication mechanisms. This document defines an authentication mechanism for EAP called EAP-EKE, based on the Encrypted Key Exchange (EKE) protocol. This method provides mutual authentication through the use of a short, easy to remember password. Compared with other common authentication methods, EAP-EKE is not susceptible to dictionary attacks. Neither does it require the availability of public-key certificates. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: Y. Sheffer, G. Zorn, H. Tschofenig, S. Fluhrer |
| RFC6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS) Many application technologies enable secure communication between two entities by means of Internet Public Key Infrastructure Using X.509 (PKIX) certificates in the context of Transport Layer Security (TLS). This document specifies procedures for representing and verifying the identity of application services in such interactions. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: P. Saint-Andre, J. Hodges |
| RFC6126 The Babel Routing Protocol Babel is a loop-avoiding distance-vector routing protocol that is robust and efficient both in ordinary wired networks and in wireless mesh networks. This document defines an Experimental Protocol for the Internet community. | April 2011 Status: EXPERIMENTAL Autor: J. Chroboczek |
| RFC6127 IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios When IPv6 was designed, it was expected that the transition from IPv4 to IPv6 would occur more smoothly and expeditiously than experience has revealed. The growth of the IPv4 Internet and predicted depletion of the free pool of IPv4 address blocks on a foreseeable horizon has highlighted an urgent need to revisit IPv6 deployment models. This document provides an overview of deployment scenarios with the goal of helping to understand what types of additional tools the industry needs to assist in IPv4 and IPv6 co-existence and transition. | May 2011 Status: INFORMATIONAL Autor: J. Arkko, M. Townsley |
| RFC6128 RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions The Session Description Protocol (SDP) has an attribute that allows RTP applications to specify an address and a port associated with the RTP Control Protocol (RTCP) traffic. In RTP-based source-specific multicast (SSM) sessions, the same attribute is used to designate the address and the RTCP port of the Feedback Target in the SDP description. However, the RTCP port associated with the SSM session itself cannot be specified by the same attribute to avoid ambiguity, and thus, is required to be derived from the "m=" line of the media description. Deriving the RTCP port from the "m=" line imposes an unnecessary restriction. This document removes this restriction by introducing a new SDP attribute. [STANDARDS-TRACK] | February 2011 Status: PROPOSED STANDARD Autor: A. Begen |
| RFC6129 The 'application/tei+xml' Media Type This document defines the 'application/tei+xml' media type for markup languages defined in accordance with the Text Encoding and Interchange guidelines. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: L. Romary, S. Lundberg |
| RFC6130 Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP) This document describes a 1-hop and symmetric 2-hop neighborhood discovery protocol (NHDP) for mobile ad hoc networks (MANETs). [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: T. Clausen, C. Dearlove, J. Dean |
| RFC6131 Sieve Vacation Extension: "Seconds" Parameter This document describes a further extension to the Sieve Vacation extension, allowing multiple auto-replies to the same sender in a single day by adding a ":seconds" parameter. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: R. George, B. Leiba |
| RFC6132 Sieve Notification Using Presence Information This is a further extension to the Sieve mail filtering language Notification extension, defining presence information that may be checked through the notify_method_capability feature. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: R. George, B. Leiba |
| RFC6133 Sieve Email Filtering: Use of Presence Information with Auto-Responder Functionality This document describes how the Sieve email filtering language, along with some extensions, can be used to create automatic replies to incoming electronic mail messages based on the address book and presence information of the recipient. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: R. George, B. Leiba, A. Melnikov |
| RFC6134 Sieve Extension: Externally Stored Lists The Sieve email filtering language can be used to implement email whitelisting, blacklisting, personal distribution lists, and other sorts of list matching. Currently, this requires that all members of such lists be hard-coded in the script itself. Whenever a member of a list is added or deleted, the script needs to be updated and possibly uploaded to a mail server. | July 2011 Status: PROPOSED STANDARD Autor: A. Melnikov, B. Leiba |
| RFC6135 An Alternative Connection Model for the Message Session Relay Protocol (MSRP) This document defines an alternative connection model for Message Session Relay Protocol (MSRP) User Agents (UAs); this model uses the connection-oriented media (COMEDIA) mechanism in order to create the MSRP transport connection. The model allows MSRP UAs behind Network Address Translators (NATs) to negotiate which endpoint initiates the establishment of the Transmission Control Protocol (TCP) connection, in order for MSRP messages to traverse the NAT. [STANDARDS-TRACK] | February 2011 Status: PROPOSED STANDARD Autor: C. Holmberg, S. Blau |
| RFC6136 Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and Framework This document provides framework and requirements for Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM). The OAM framework is intended to provide OAM layering across L2VPN services, pseudowires (PWs), and Packet Switched Network (PSN) tunnels. This document is intended to identify OAM requirements for L2VPN services, i.e., Virtual Private LAN Service (VPLS), Virtual Private Wire Service (VPWS), and IP-only LAN Service (IPLS). Furthermore, if L2VPN service OAM requirements impose specific requirements on PW OAM and/or PSN OAM, those specific PW and/or PSN OAM requirements are also identified. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: A. Sajassi, D. Mohan |
| RFC6137 The Network Trouble Ticket Data Model (NTTDM) Handling multiple sets of network trouble tickets (TTs) originating from different participants' inter-connected network environments poses a series of challenges for the involved institutions. A Grid is a good example of such a multi-domain project. Each of the participants follows different procedures for handling trouble in its domain, according to the local technical and linguistic profile. The TT systems of the participants collect, represent, and disseminate TT information in different formats. | February 2011 Status: EXPERIMENTAL Autor: D. Zisiadis, S. Kopsidas, M. Tsavli, G. Cessieux |
| RFC6138 LDP IGP Synchronization for Broadcast Networks RFC 5443 describes a mechanism to achieve LDP IGP synchronization to prevent black-holing traffic (e.g., VPN) when an Interior Gateway Protocol (IGP) is operational on a link but Label Distribution Protocol (LDP) is not. If this mechanism is applied to broadcast links that have more than one LDP peer, the metric increase procedure can only be applied to the link as a whole but not to an individual peer. When a new LDP peer comes up on a broadcast network, this can result in loss of traffic through other established peers on that network. This document describes a mechanism to address that use-case without dropping traffic. The mechanism does not introduce any protocol message changes. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: S. Kini, W. Lu |
| RFC6139 Routing and Addressing in Networks with Global Enterprise Recursion (RANGER) Scenarios "Routing and Addressing in Networks with Global Enterprise Recursion (RANGER)" (RFC 5720) provides an architectural framework for scalable routing and addressing. It provides an incrementally deployable approach for scalability, provider independence, mobility, multihoming, traffic engineering, and security. This document describes a series of use cases in order to showcase the architectural capabilities. It further shows how the RANGER architecture restores the network-within-network principles originally intended for the sustained growth of the Internet. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2011 Status: INFORMATIONAL Autor: S. Russert, E. Fleischman, F. Templin |
| RFC6140 Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP) This document defines a mechanism by which a Session Initiation Protocol (SIP) server acting as a traditional Private Branch Exchange (PBX) can register with a SIP Service Provider (SSP) to receive phone calls for SIP User Agents (UAs). In order to function properly, this mechanism requires that each of the Addresses of Record (AORs) registered in bulk map to a unique set of contacts. This requirement is satisfied by AORs representing phone numbers regardless of the domain, since phone numbers are fully qualified and globally unique. This document therefore focuses on this use case. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: A.B. Roach |
| RFC6141 Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP) The procedures for handling SIP re-INVITEs are described in RFC 3261. Implementation and deployment experience has uncovered a number of issues with the original documentation, and this document provides additional procedures that update the original specification to address those issues. In particular, this document defines in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE. Additionally, this document defines further details of procedures related to target-refresh requests. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: G. Camarillo, C. Holmberg, Y. Gao |
| RFC6142 ANSI C12.22, IEEE 1703, and MC12.22 Transport Over IP This RFC provides a framework for transporting ANSI C12.22/IEEE 1703/MC12.22 Advanced Metering Infrastructure (AMI) Application Layer Messages on an IP network. | March 2011 Status: INFORMATIONAL Autor: A. Moise, J. Brodkin |
| RFC6143 The Remote Framebuffer Protocol RFB ("remote framebuffer") is a simple protocol for remote access to graphical user interfaces that allows a client to view and control a window system on another computer. Because it works at the framebuffer level, RFB is applicable to all windowing systems and applications. This document describes the protocol used to communicate between an RFB client and RFB server. RFB is the protocol used in VNC. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: T. Richardson, J. Levine |
| RFC6144 Framework for IPv4/IPv6 Translation This note describes a framework for IPv4/IPv6 translation. This is in the context of replacing Network Address Translation - Protocol Translation (NAT-PT), which was deprecated by RFC 4966, and to enable networks to have IPv4 and IPv6 coexist in a somewhat rational manner while transitioning to an IPv6 network. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: F. Baker, X. Li, C. Bao, K. Yin |
| RFC6145 IP/ICMP Translation Algorithm This document describes the Stateless IP/ICMP Translation Algorithm (SIIT), which translates between IPv4 and IPv6 packet headers (including ICMP headers). This document obsoletes RFC 2765. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: X. Li, C. Bao, F. Baker |
| RFC6146 Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers | April 2011 Status: PROPOSED STANDARD Autor: M. Bagnulo, P. Matthews, I. van Beijnum |
| RFC6147 DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers DNS64 is a mechanism for synthesizing AAAA records from A records. DNS64 is used with an IPv6/IPv4 translator to enable client-server communication between an IPv6-only client and an IPv4-only server, without requiring any changes to either the IPv6 or the IPv4 node, for the class of applications that work through NATs. This document specifies DNS64, and provides suggestions on how it should be deployed in conjunction with IPv6/IPv4 translators. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: M. Bagnulo, A. Sullivan, P. Matthews, I. van Beijnum |
| RFC6148 DHCPv4 Lease Query by Relay Agent Remote ID Some relay agents extract lease information from the DHCP messages exchanged between the client and DHCP server. This lease information is used by relay agents for various purposes like antispoofing and prevention of flooding. RFC 4388 defines a mechanism for relay agents to retrieve the lease information from the DHCP server when this information is lost. The existing lease query mechanism is data-driven, which means that a relay agent can initiate the lease query only when it starts receiving data to and from the clients. In certain scenarios, this model is not scalable. This document first looks at issues in the existing mechanism and then proposes a new query type, query by Remote ID, to address these issues. [STANDARDS-TRACK] | February 2011 Status: PROPOSED STANDARD Autor: P. Kurapati, R. Desetti, B. Joshi |
| RFC6149 MD2 to Historic Status This document retires MD2 and discusses the reasons for doing so. This document moves RFC 1319 to Historic status. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: S. Turner, L. Chen |
| RFC6150 MD4 to Historic Status This document retires RFC 1320, which documents the MD4 algorithm, and discusses the reasons for doing so. This document moves RFC 1320 to Historic status. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: S. Turner, L. Chen |
| RFC6151 Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms This document updates the security considerations for the MD5 message digest algorithm. It also updates the security considerations for HMAC-MD5. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: S. Turner, L. Chen |
| RFC6152 SMTP Service Extension for 8-bit MIME Transport 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] | March 2011 Status: STANDARD Autor: J. Klensin, N. Freed, M. Rose, D. Crocker |
| RFC6153 DHCPv4 and DHCPv6 Options for Access Network Discovery and Selection Function (ANDSF) Discovery This document defines new Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) options to enable a mobile node to discover Access Network Discovery and Selection Function (ANDSF) entities in an IP network. ANDSF is being developed in the Third Generation Partnership Project (3GPP) and provides inter-system mobility policies and access-network-specific information to the mobile nodes (MNs). [STANDARDS-TRACK] | February 2011 Status: PROPOSED STANDARD Autor: S. Das, G. Bajko |
| RFC6154 IMAP LIST Extension for Special-Use Mailboxes Some IMAP message stores include special-use mailboxes, such as those used to hold draft messages or sent messages. Many mail clients allow users to specify where draft or sent messages should be put, but configuring them requires that the user know which mailboxes the server has set aside for these purposes. This extension adds new optional mailbox attributes that a server may include in IMAP LIST command responses to identify special-use mailboxes to the client, easing configuration. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: B. Leiba, J. Nicolson |
| RFC6155 Use of Device Identity in HTTP-Enabled Location Delivery (HELD) When a Location Information Server receives a request for location information (using the locationRequest message), described in the base HTTP-Enabled Location Delivery (HELD) specification, it uses the source IP address of the arriving message as a pointer to the location determination process. This is sufficient in environments where the location of a Device can be determined based on its IP address. | March 2011 Status: PROPOSED STANDARD Autor: J. Winterbottom, M. Thomson, H. Tschofenig, R. Barnes |
| RFC6156 Traversal Using Relays around NAT (TURN) Extension for IPv6 This document adds IPv6 support to Traversal Using Relays around NAT (TURN). IPv6 support in TURN includes IPv4-to-IPv6, IPv6-to-IPv6, and IPv6-to-IPv4 relaying. This document defines the REQUESTED- ADDRESS-FAMILY attribute for TURN. The REQUESTED-ADDRESS-FAMILY attribute allows a client to explicitly request the address type the TURN server will allocate (e.g., an IPv4-only node may request the TURN server to allocate an IPv6 address). [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: G. Camarillo, O. Novo, S. Perreault |
| RFC6157 IPv6 Transition in the Session Initiation Protocol (SIP) This document describes how the IPv4 Session Initiation Protocol (SIP) user agents can communicate with IPv6 SIP user agents (and vice versa) at the signaling layer as well as exchange media once the session has been successfully set up. Both single- and dual-stack (i.e., IPv4-only and IPv4/IPv6) user agents are considered. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: G. Camarillo, K. El Malki, V. Gurbani |
| RFC6158 RADIUS Design Guidelines This document provides guidelines for the design of attributes used by the Remote Authentication Dial In User Service (RADIUS) protocol. It is expected that these guidelines will prove useful to authors and reviewers of future RADIUS attribute specifications, within the IETF as well as other Standards Development Organizations (SDOs). This memo documents an Internet Best Current Practice. | March 2011 Status: BEST CURRENT PRACTICE Autor: A. DeKok, G. Weber |
| RFC6159 Session-Specific Explicit Diameter Request Routing This document describes a mechanism to enable specific Diameter proxies to remain in the path of all message exchanges constituting a Diameter session. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: T. Tsou, G. Zorn, T. Taylor |
| RFC6160 Algorithms for Cryptographic Message Syntax (CMS) Protection of Symmetric Key Package Content Types This document describes the conventions for using several cryptographic algorithms with the Cryptographic Message Syntax (CMS) to protect the symmetric key package content type. Specifically, it includes conventions necessary to implement SignedData, EnvelopedData, EncryptedData, and AuthEnvelopedData. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC6161 Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type This document describes the conventions for using several Elliptic Curve cryptographic algorithms with the Cryptographic Message Syntax (CMS) encrypted key package content type. Specifically, it includes conventions necessary to implement Elliptic Curve Diffie-Hellman (ECDH) with EnvelopedData and Elliptic Curve Digital Signature Algorithm (ECDSA) with SignedData. This document extends RFC 6033. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC6162 Elliptic Curve Algorithms for Cryptographic Message Syntax (CMS) Asymmetric Key Package Content Type This document describes conventions for using Elliptic Curve cryptographic algorithms with SignedData and EnvelopedData to protect the AsymmetricKeyPackage content type. Specifically, it includes conventions necessary to implement Elliptic Curve Diffie-Hellman (ECDH) with EnvelopedData and Elliptic Curve Digital Signature Algorithm (ECDSA) with SignedData. This document extends RFC 5959. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: S. Turner |
| RFC6163 Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs) This document provides a framework for applying Generalized Multi-Protocol Label Switching (GMPLS) and the Path Computation Element (PCE) architecture to the control of Wavelength Switched Optical Networks (WSONs). In particular, it examines Routing and Wavelength Assignment (RWA) of optical paths. | April 2011 Status: INFORMATIONAL Autor: Y. Lee, G. Bernstein, W. Imajuku |
| RFC6164 Using 127-Bit IPv6 Prefixes on Inter-Router Links On inter-router point-to-point links, it is useful, for security and other reasons, to use 127-bit IPv6 prefixes. Such a practice parallels the use of 31-bit prefixes in IPv4. This document specifies the motivation for, and usages of, 127-bit IPv6 prefix lengths on inter-router point-to-point links. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: M. Kohno, B. Nitzan, R. Bush, Y. Matsuzaki, L. Colitti, T. Narten |
| RFC6165 Extensions to IS-IS for Layer-2 Systems This document specifies the Intermediate System to Intermediate System (IS-IS) extensions necessary to support link state routing for any protocols running directly over Layer-2. While supporting this concept involves several pieces, this document only describes extensions to IS-IS. Furthermore, the Type, Length, Value pairs (TLVs) described in this document are generic Layer-2 additions, and specific ones as needed are defined in the IS-IS technology-specific extensions. We leave it to the systems using these IS-IS extensions to explain how the information carried in IS-IS is used. [STANDARDS- TRACK] | April 2011 Status: PROPOSED STANDARD Autor: A. Banerjee, D. Ward |
| RFC6166 A Registry for PIM Message Types This document provides instructions to IANA for the creation of a registry for PIM message types. It specifies the initial content of the registry, based on existing RFCs specifying PIM message types. It also specifies a procedure for registering new types. | April 2011 Status: PROPOSED STANDARD Autor: S. Venaas |
| RFC6167 URI Scheme for Java(tm) Message Service 1.0 This document defines the format of Uniform Resource Identifiers (URIs) as defined in RFC 3986, for designating connections and destination addresses used in the Java(tm) Messaging Service (JMS). It was originally designed for particular uses, but applies generally wherever a JMS URI is needed to describe the connection to a JMS provider, and access to a JMS Destination. The syntax of this JMS URI is not compatible with previously existing, but unregistered, "jms" URI schemes. However, the expressiveness of the scheme described herein should satisfy the requirements of all existing circumstances. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: M. Phillips, P. Adams, D. Rokicki, E. Johnson |
| RFC6168 Requirements for Management of Name Servers for the DNS Management of name servers for the Domain Name System (DNS) has traditionally been done using vendor-specific monitoring, configuration, and control methods. Although some service monitoring platforms can test the functionality of the DNS itself, there is not an interoperable way to manage (monitor, control, and configure) the internal aspects of a name server itself. | May 2011 Status: INFORMATIONAL Autor: W. Hardaker |
| RFC6169 Security Concerns with IP Tunneling A number of security concerns with IP tunnels are documented in this memo. The intended audience of this document includes network administrators and future protocol developers. The primary intent of this document is to raise the awareness level regarding the security issues with IP tunnels as deployed and propose strategies for the mitigation of those issues. [STANDARDS-TRACK] | April 2011 Status: INFORMATIONAL Autor: S. Krishnan, D. Thaler, J. Hoagland |
| RFC6170 Internet X.509 Public Key Infrastructure -- Certificate Image This document specifies a method to bind a visual representation of a certificate in the form of a certificate image to a public key certificate as defined in RFC 5280, by defining a new "otherLogos" image type according to RFC 3709. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: S. Santesson, R. Housley, S. Bajaj, L. Rosenthol |
| RFC6171 The Lightweight Directory Access Protocol (LDAP) Don't Use Copy Control This document defines the Lightweight Directory Access Protocol (LDAP) Don't Use Copy control extension, which allows a client to specify that copied information should not be used in providing service. This control is based upon the X.511 dontUseCopy service control option. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: K. Zeilenga |
| RFC6172 Deprecation of the Internet Fibre Channel Protocol (iFCP) Address Translation Mode Changes to Fibre Channel have caused the specification of the Internet Fibre Channel Protocol (iFCP) address translation mode to become incorrect. Due to the absence of usage of iFCP address translation mode, it is deprecated by this document. iFCP address transparent mode remains correctly specified. | March 2011 Status: PROPOSED STANDARD Autor: D. Black, D. Peterson |
| RFC6173 Definitions of Managed Objects for the Internet Fibre Channel Protocol (iFCP) This document defines Management Information Base (MIB) objects to monitor and control the Internet Fibre Channel Protocol (iFCP) gateway instances and their associated sessions, for use with network management protocols. | March 2011 Status: PROPOSED STANDARD Autor: P. Venkatesen |
| RFC6174 Definition of IETF Working Group Document States The IETF Datatracker tool needs to be enhanced to make it possible for Working Group (WG) Chairs to provide IETF participants with more information about the status and progression of WG documents than is currently possible. | March 2011 Status: INFORMATIONAL Autor: E. Juskevicius |
| RFC6175 Requirements to Extend the Datatracker for IETF Working Group Chairs and Authors This document specifies requirements for new functionality to be added to the IETF Datatracker tool to make it possible for Working Group (WG) Chairs and their Delegates to input and update the status of the Internet-Drafts (I-Ds) associated with their WGs. After these requirements are implemented, WG Chairs will be able to use the Datatracker to provide everyone with more information about the status and progression of WG I-Ds than is currently possible. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: E. Juskevicius |
| RFC6176 Prohibiting Secure Sockets Layer (SSL) Version 2.0 This document requires that when Transport Layer Security (TLS) clients and servers establish connections, they never negotiate the use of Secure Sockets Layer (SSL) version 2.0. This document updates the backward compatibility sections found in the Transport Layer Security (TLS). [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: S. Turner, T. Polk |
| RFC6177 IPv6 Address Assignment to End Sites RFC 3177 argued that in IPv6, end sites should be assigned /48 blocks in most cases. The Regional Internet Registries (RIRs) adopted that recommendation in 2002, but began reconsidering the policy in 2005. This document obsoletes the RFC 3177 recommendations on the assignment of IPv6 address space to end sites. The exact choice of how much address space to assign end sites is an issue for the operational community. The IETF's role in this case is limited to providing guidance on IPv6 architectural and operational considerations. This document reviews the architectural and operational considerations of end site assignments as well as the motivations behind the original recommendations in RFC 3177. Moreover, this document clarifies that a one-size-fits-all recommendation of /48 is not nuanced enough for the broad range of end sites and is no longer recommended as a single default. | March 2011 Status: BEST CURRENT PRACTICE Autor: T. Narten, G. Huston, L. Roberts |
| RFC6178 Label Edge Router Forwarding of IPv4 Option Packets This document specifies how Label Edge Routers (LERs) should behave when determining whether to MPLS encapsulate an IPv4 packet with header options. Lack of a formal standard has resulted in different LER forwarding behaviors for IPv4 packets with header options despite being associated with a prefix-based Forwarding Equivalence Class (FEC). IPv4 option packets that belong to a prefix-based FEC, yet are forwarded into an IPv4/MPLS network without being MPLS- encapsulated, present a security risk against the MPLS infrastructure. Further, LERs that are unable to MPLS encapsulate IPv4 packets with header options cannot operate in certain MPLS environments. While this newly defined LER behavior is mandatory to implement, it is optional to invoke. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: D. Smith, J. Mullooly, W. Jaeger, T. Scholl |
| RFC6179 The Internet Routing Overlay Network (IRON) Since the Internet must continue to support escalating growth due to increasing demand, it is clear that current routing architectures and operational practices must be updated. This document proposes an Internet Routing Overlay Network (IRON) that supports sustainable growth while requiring no changes to end systems and no changes to the existing routing system. IRON further addresses other important issues including routing scaling, mobility management, multihoming, traffic engineering and NAT traversal. While business considerations are an important determining factor for widespread adoption, they are out of scope for this document. This document is a product of the IRTF Routing Research Group. This document defines an Experimental Protocol for the Internet community. | March 2011 Status: EXPERIMENTAL Autor: F. Templin |
| RFC6180 Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment The Internet continues to grow beyond the capabilities of IPv4. An expansion in the address space is clearly required. With its increase in the number of available prefixes and addresses in a subnet, and improvements in address management, IPv6 is the only real option on the table. Yet, IPv6 deployment requires some effort, resources, and expertise. The availability of many different deployment models is one reason why expertise is required. This document discusses the IPv6 deployment models and migration tools, and it recommends ones that have been found to work well in operational networks in many common situations. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: J. Arkko, F. Baker |
| RFC6181 Threat Analysis for TCP Extensions for Multipath Operation with Multiple Addresses Multipath TCP (MPTCP for short) describes the extensions proposed for TCP so that endpoints of a given TCP connection can use multiple paths to exchange data. Such extensions enable the exchange of segments using different source-destination address pairs, resulting in the capability of using multiple paths in a significant number of scenarios. Some level of multihoming and mobility support can be achieved through these extensions. However, the support for multiple IP addresses per endpoint may have implications on the security of the resulting MPTCP. This note includes a threat analysis for MPTCP. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: M. Bagnulo |
| RFC6182 Architectural Guidelines for Multipath TCP Development Hosts are often connected by multiple paths, but TCP restricts communications to a single path per transport connection. Resource usage within the network would be more efficient were these multiple paths able to be used concurrently. This should enhance user experience through improved resilience to network failure and higher throughput. | March 2011 Status: INFORMATIONAL Autor: A. Ford, C. Raiciu, M. Handley, S. Barre, J. Iyengar |
| RFC6183 IP Flow Information Export (IPFIX) Mediation: Framework This document describes a framework for IP Flow Information Export (IPFIX) Mediation. This framework extends the IPFIX reference model specified in RFC 5470 by defining the IPFIX Mediator components. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: A. Kobayashi, B. Claise, G. Muenz, K. Ishibashi |
| RFC6184 RTP Payload Format for H.264 Video 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, excluding the Scalable Video Coding (SVC) extension and the Multiview Video Coding extension, for which the RTP payload formats are defined elsewhere. 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 bitrate conversational usage, to Internet video streaming with interleaved transmission, to high bitrate video-on-demand. | May 2011 Status: PROPOSED STANDARD Autor: Y.-K. Wang, R. Even, T. Kristensen, R. Jesup |
| RFC6185 RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) Video This document describes an RTP payload format for the Reduced- Complexity Decoding Operation (RCDO) for H.264 Baseline profile bitstreams, as specified in ITU-T Recommendation H.241. RCDO reduces the decoding cost and resource consumption of the video processing. The RCDO RTP payload format is based on the H.264 RTP payload format. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: T. Kristensen, P. Luthi |
| RFC6186 Use of SRV Records for Locating Email Submission/Access Services This specification describes how SRV records can be used to locate email services. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: C. Daboo |
| RFC6187 X.509v3 Certificates for Secure Shell Authentication X.509 public key certificates use a signature by a trusted certification authority to bind a given public key to a given digital identity. This document specifies how to use X.509 version 3 public key certificates in public key algorithms in the Secure Shell protocol. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: K. Igoe, D. Stebila |
| RFC6188 The Use of AES-192 and AES-256 in Secure RTP This memo describes the use of the Advanced Encryption Standard (AES) with 192- and 256-bit keys within the Secure RTP (SRTP) protocol. It details counter mode encryption for SRTP and Secure Realtime Transport Control Protocol (SRTCP) and a new SRTP Key Derivation Function (KDF) for AES-192 and AES-256. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: D. McGrew |
| RFC6189 ZRTP: Media Path Key Agreement for Unicast Secure RTP This document defines ZRTP, a protocol for media path Diffie-Hellman exchange to agree on a session key and parameters for establishing unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice over IP (VoIP) applications. The ZRTP protocol is media path keying because it is multiplexed on the same port as RTP and does not require support in the signaling protocol. ZRTP does not assume a Public Key Infrastructure (PKI) or require the complexity of certificates in end devices. For the media session, ZRTP provides confidentiality, protection against man-in-the-middle (MiTM) attacks, and, in cases where the signaling protocol provides end-to-end integrity protection, authentication. ZRTP can utilize a Session Description Protocol (SDP) attribute to provide discovery and authentication through the signaling channel. To provide best effort SRTP, ZRTP utilizes normal RTP/AVP (Audio-Visual Profile) profiles. ZRTP secures media sessions that include a voice media stream and can also secure media sessions that do not include voice by using an optional digital signature. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: P. Zimmermann, A. Johnston, J. Callas |
| RFC6190 RTP Payload Format for Scalable Video Coding This memo describes an RTP payload format for Scalable Video Coding (SVC) as defined in Annex G of ITU-T Recommendation H.264, which is technically identical to Amendment 3 of ISO/IEC International Standard 14496-10. The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload, as well as fragmentation of a NAL unit in multiple RTP packets. Furthermore, it supports transmission of an SVC stream over a single as well as multiple RTP sessions. The payload format defines a new media subtype name "H264-SVC", but is still backward compatible to RFC 6184 since the base layer, when encapsulated in its own RTP stream, must use the H.264 media subtype name ("H264") and the packetization method specified in RFC 6184. The payload format has wide applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among others. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: S. Wenger, Y.-K. Wang, T. Schierl, A. Eleftheriadis |
| RFC6191 Reducing the TIME-WAIT State Using TCP Timestamps This document describes an algorithm for processing incoming SYN segments that allows higher connection-establishment rates between any two TCP endpoints when a TCP Timestamps option is present in the incoming SYN segment. This document only modifies processing of SYN segments received for connections in the TIME-WAIT state; processing in all other states is unchanged. This memo documents an Internet Best Current Practice. | April 2011 Status: BEST CURRENT PRACTICE Autor: F. Gont |
| RFC6192 Protecting the Router Control Plane This memo provides a method for protecting a router's control plane from undesired or malicious traffic. In this approach, all legitimate router control plane traffic is identified. Once legitimate traffic has been identified, a filter is deployed in the router's forwarding plane. That filter prevents traffic not specifically identified as legitimate from reaching the router's control plane, or rate-limits such traffic to an acceptable level. | March 2011 Status: INFORMATIONAL Autor: D. Dugal, C. Pignataro, R. Dunn |
| RFC6193 Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP) This document specifies how to establish a media session that represents a virtual private network using the Session Initiation Protocol for the purpose of on-demand media/application sharing between peers. It extends the protocol identifier of the Session Description Protocol (SDP) so that it can negotiate use of the Internet Key Exchange Protocol (IKE) for media sessions in the SDP offer/answer model. It also specifies a method to boot up IKE and generate IPsec security associations using a self-signed certificate. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: M. Saito, D. Wing, M. Toyama |
| RFC6194 Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms This document includes security considerations for the SHA-0 and SHA-1 message digest algorithm. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2011 Status: INFORMATIONAL Autor: T. Polk, L. Chen, S. Turner, P. Hoffman |
| RFC6195 Domain Name System (DNS) IANA Considerations This document specifies Internet Assigned Number Authority (IANA) parameter assignment considerations for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes. This memo documents an Internet Best Current Practice. | March 2011 Status: BEST CURRENT PRACTICE Autor: D. Eastlake 3rd |
| RFC6196 Moving mailserver: URI Scheme to Historic This document registers the mailserver: URI scheme as historic in the IANA URI registry. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: A. Melnikov |
| RFC6197 Location-to-Service Translation (LoST) Service List Boundary Extension Location-to-Service Translation (LoST) maps service identifiers and location information to service contact URIs. If a LoST client wants to discover available services for a particular location, it will perform a <listServicesByLocation> query to the LoST server. However, the LoST server, in its response, does not provide context information; that is, it does not provide any additional information about the geographical region within which the returned list of services is considered valid. Therefore, this document defines a Service List Boundary that returns a local context along with the list of services returned, in order to assist the client in not missing a change in available services when moving. This document defines an Experimental Protocol for the Internet community. | April 2011 Status: EXPERIMENTAL Autor: K. Wolf |
| RFC6198 Requirements for the Graceful Shutdown of BGP Sessions The Border Gateway Protocol (BGP) is heavily used in Service Provider networks for both Internet and BGP/MPLS VPN services. For resiliency purposes, redundant routers and BGP sessions can be deployed to reduce the consequences of an Autonomous System Border Router (ASBR) or BGP session breakdown on customers' or peers' traffic. However, simply taking down or even bringing up a BGP session for maintenance purposes may still induce connectivity losses during the BGP convergence. This is no longer satisfactory for new applications (e.g., voice over IP, online gaming, VPN). Therefore, a solution is required for the graceful shutdown of a (set of) BGP session(s) in order to limit the amount of traffic loss during a planned shutdown. This document expresses requirements for such a solution. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: B. Decraene, P. Francois, C. Pelsser, Z. Ahmad, A.J. Elizondo Armengol, T. Takeda |
| RFC6201 Device Reset Characterization An operational forwarding device may need to be restarted (automatically or manually) for a variety of reasons, an event called a "reset" in this document. Since there may be an interruption in the forwarding operation during a reset, it is useful to know how long a device takes to resume the forwarding operation. | March 2011 Status: INFORMATIONAL Autor: R. Asati, C. Pignataro, F. Calabria, C. Olvera |
| RFC6202 Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, "server- initiated" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such "bidirectional HTTP" applications, focusing on the two most common mechanisms: HTTP long polling and HTTP streaming. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: S. Loreto, P. Saint-Andre, S. Salsano, G. Wilkins |
| RFC6203 IMAP4 Extension for Fuzzy Search This document describes an IMAP protocol extension enabling a server to perform searches with inexact matching and assigning relevancy scores for matched messages. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: T. Sirainen |
| RFC6204 Basic Requirements for IPv6 Customer Edge Routers This document specifies requirements for an IPv6 Customer Edge (CE) router. Specifically, the current version of this document focuses on the basic provisioning of an IPv6 CE router and the provisioning of IPv6 hosts attached to it. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: H. Singh, W. Beebee, C. Donley, B. Stark, O. Troan |
| RFC6205 Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers Technology in the optical domain is constantly evolving, and, as a consequence, new equipment providing lambda switching capability has been developed and is currently being deployed. | March 2011 Status: PROPOSED STANDARD Autor: T. Otani, D. Li |
| RFC6206 The Trickle Algorithm The Trickle algorithm allows nodes in a lossy shared medium (e.g., low-power and lossy networks) to exchange information in a highly robust, energy efficient, simple, and scalable manner. Dynamically adjusting transmission windows allows Trickle to spread new information on the scale of link-layer transmission times while sending only a few messages per hour when information does not change. A simple suppression mechanism and transmission point selection allow Trickle's communication rate to scale logarithmically with density. This document describes the Trickle algorithm and considerations in its use. [STANDARDS-TRACK] | March 2011 Status: PROPOSED STANDARD Autor: P. Levis, T. Clausen, J. Hui, O. Gnawali, J. Ko |
| RFC6207 The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, and application/sru+xml This document specifies media types for the following formats: MODS (Metadata Object Description Schema), MADS (Metadata Authority Description Schema), METS (Metadata Encoding and Transmission Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve via URL Response Format) protocol response XML schema. These are all XML schemas providing representations of various forms of information including metadata and search results. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: R. Denenberg |
| RFC6208 Cloud Data Management Interface (CDMI) Media Types This document describes several Internet media types defined for the Cloud Data Management Interface (CDMI) by the Storage Networking Industry Association (SNIA). The media types are: | April 2011 Status: INFORMATIONAL Autor: K. Sankar, A. Jones |
| RFC6209 Addition of the ARIA Cipher Suites to Transport Layer Security (TLS) This document specifies a set of cipher suites for the Transport Layer Security (TLS) protocol to support the ARIA encryption algorithm as a block cipher. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: W. Kim, J. Lee, J. Park, D. Kwon |
| RFC6210 Experiment: Hash Functions with Parameters in the Cryptographic Message Syntax (CMS) and S/MIME New hash algorithms are being developed that may include parameters. Cryptographic Message Syntax (CMS) has not currently defined any hash algorithms with parameters, but anecdotal evidence suggests that defining one could cause major problems. This document defines just such an algorithm and describes how to use it so that experiments can be run to find out how bad including hash parameters will be. This document defines an Experimental Protocol for the Internet community. | April 2011 Status: EXPERIMENTAL Autor: J. Schaad |
| RFC6211 Cryptographic Message Syntax (CMS) Algorithm Identifier Protection Attribute The Cryptographic Message Syntax (CMS), unlike X.509/PKIX certificates, is vulnerable to algorithm substitution attacks. In an algorithm substitution attack, the attacker changes either the algorithm being used or the parameters of the algorithm in order to change the result of a signature verification process. In X.509 certificates, the signature algorithm is protected because it is duplicated in the TBSCertificate.signature field with the proviso that the validator is to compare both fields as part of the signature validation process. This document defines a new attribute that contains a copy of the relevant algorithm identifiers so that they are protected by the signature or authentication process. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: J. Schaad |
| RFC6212 Authentication-Results Registration for Vouch by Reference Results This memo updates the registry of properties in Authentication- Results: message header fields to allow relaying of the results of a Vouch By Reference query. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: M. Kucherawy |
| RFC6213 IS-IS BFD-Enabled TLV This document describes a type-length-value (TLV) for use in the IS-IS routing protocol that allows for the proper use of the Bidirectional Forwarding Detection (BFD) protocol. There exist certain scenarios in which IS-IS will not react appropriately to a BFD-detected forwarding plane failure without use of either this TLV or some other method. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: C. Hopps, L. Ginsberg |
| RFC6214 Adaptation of RFC 1149 for IPv6 This document specifies a method for transmission of IPv6 datagrams over the same medium as specified for IPv4 datagrams in RFC 1149. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: B. Carpenter, R. Hinden |
| RFC6215 MPLS Transport Profile User-to-Network and Network-to-Network Interfaces The framework for MPLS in transport networks (RFC 5921) provides reference models for the MPLS Transport Profile (MPLS-TP) Transport Service Interfaces, which are a User-to-Network Interface (UNI), and a Network-to-Network Interface (NNI). This document updates those reference models to show detailed reference points for these interfaces, along with further clarification of the functional architecture of MPLS-TP at a UNI and NNI. | April 2011 Status: INFORMATIONAL Autor: M. Bocci, L. Levrau, D. Frost |
| RFC6216 Example Call Flows Using Session Initiation Protocol (SIP) Security Mechanisms This document shows example call flows demonstrating the use of Transport Layer Security (TLS), and Secure/Multipurpose Internet Mail Extensions (S/MIME) in Session Initiation Protocol (SIP). It also provides information that helps implementers build interoperable SIP software. To help facilitate interoperability testing, it includes certificates used in the example call flows and processes to create certificates for testing. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: C. Jennings, K. Ono, R. Sparks, B. Hibbard |
| RFC6217 Regional Broadcast Using an Atmospheric Link Layer Broadcasting is a technology that has been largely discarded in favor of technologies like multicast. This document builds on RFC 919 and describes a more efficient routing mechanism for broadcast packets destined for multiple Local Area Networks (LANs) or Metropolitan Area Networks (MANs) using an alternative link layer. It significantly reduces congestion on network equipment and does not require additional physical infrastructure investment. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: EXPERIMENTAL Autor: T. Ritter |
| RFC6218 Cisco Vendor-Specific RADIUS Attributes for the Delivery of Keying Material This document defines a set of vendor-specific RADIUS Attributes designed to allow both the secure transmission of cryptographic keying material and strong authentication of any RADIUS message. These attributes have been allocated from the Cisco vendor-specific space and have been implemented by multiple vendors. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: G. Zorn, T. Zhang, J. Walker, J. Salowey |
| RFC6219 The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition This document presents the China Education and Research Network (CERNET)'s IVI translation design and deployment for the IPv4/IPv6 coexistence and transition. | May 2011 Status: INFORMATIONAL Autor: X. Li, C. Bao, M. Chen, H. Zhang, J. Wu |
| RFC6220 Defining the Role and Function of IETF Protocol Parameter Registry Operators Many Internet Engineering Task Force (IETF) protocols make use of commonly defined values that are passed in messages or packets. To ensure consistent interpretation of these values between independent implementations, there is a need to ensure that the values and associated semantic intent are uniquely defined. The IETF uses registry functions to record assigned protocol parameter values and their associated semantic intentions. For each IETF protocol parameter, it is current practice for the IETF to delegate the role of Protocol Parameter Registry Operator to a nominated entity. This document provides a description of, and the requirements for, these delegated functions. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: D. McPherson, O. Kolkman, J. Klensin, G. Huston, Internet Architecture Board |
| RFC6221 Lightweight DHCPv6 Relay Agent This document proposes a Lightweight DHCPv6 Relay Agent (LDRA) that is used to insert relay agent options in DHCPv6 message exchanges identifying client-facing interfaces. The LDRA can be implemented in existing access nodes (such as Digital Subscriber Link Access Multiplexers (DSLAMs) and Ethernet switches) that do not support IPv6 control or routing functions. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: D. Miles, S. Ooghe, W. Dec, S. Krishnan, A. Kavanagh |
| RFC6222 Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs) The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. While the Synchronization Source (SSRC) identifier of an RTP endpoint may change if a collision is detected or when the RTP application is restarted, its RTCP CNAME is meant to stay unchanged, so that RTP endpoints can be uniquely identified and associated with their RTP media streams. For proper functionality, RTCP CNAMEs should be unique within the participants of an RTP session. However, the existing guidelines for choosing the RTCP CNAME provided in the RTP standard are insufficient to achieve this uniqueness. This memo updates those guidelines to allow endpoints to choose unique RTCP CNAMEs. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: A. Begen, C. Perkins, D. Wing |
| RFC6223 Indication of Support for Keep-Alive This specification defines a new Session Initiation Protocol (SIP) Via header field parameter, "keep", which allows adjacent SIP entities to explicitly negotiate usage of the Network Address Translation (NAT) keep-alive mechanisms defined in SIP Outbound, in cases where SIP Outbound is not supported, cannot be applied, or where usage of keep-alives is not implicitly negotiated as part of the SIP Outbound negotiation. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: C. Holmberg |
| RFC6224 Base Deployment for Multicast Listener Support in Proxy Mobile IPv6 (PMIPv6) Domains This document describes deployment options for activating multicast listener functions in Proxy Mobile IPv6 domains without modifying mobility and multicast protocol standards. Similar to home agents in Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as multicast subscription anchor points, while Mobile Access Gateways provide Multicast Listener Discovery (MLD) proxy functions. In this scenario, mobile nodes remain agnostic of multicast mobility operations. Support for mobile multicast senders is outside the scope of this document. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: T. Schmidt, M. Waehlisch, S. Krishnan |
| RFC6225 Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information This document specifies Dynamic Host Configuration Protocol options (both DHCPv4 and DHCPv6) for the coordinate-based geographic location of the client. The Location Configuration Information (LCI) includes Latitude, Longitude, and Altitude, with resolution or uncertainty indicators for each. Separate parameters indicate the reference datum for each of these values. This document obsoletes RFC 3825. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: J. Polk, M. Linsner, M. Thomson, B. Aboba |
| RFC6226 PIM Group-to-Rendezvous-Point Mapping Each Protocol Independent Multicast - Sparse Mode (PIM-SM) router in a PIM domain that supports Any Source Multicast (ASM) maintains Group-to-RP mappings that are used to identify a Rendezvous Point (RP) for a specific multicast group. PIM-SM has defined an algorithm to choose a RP from the Group-to-RP mappings learned using various mechanisms. This algorithm does not consider the PIM mode and the mechanism through which a Group-to-RP mapping was learned. | May 2011 Status: PROPOSED STANDARD Autor: B. Joshi, A. Kessler, D. McWalter |
| RFC6227 Design Goals for Scalable Internet Routing It is commonly recognized that the Internet routing and addressing architecture is facing challenges in scalability, mobility, multi-homing, and inter-domain traffic engineering. The Routing Research Group is investigating an alternate architecture to meet these challenges. This document consists of a prioritized list of design goals for the target architecture. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: T. Li |
| RFC6228 Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog This specification defines a new Session Initiation Protocol (SIP) response code, 199 Early Dialog Terminated, that a SIP forking proxy and a User Agent Server (UAS) can use to indicate to upstream SIP entities (including the User Agent Client (UAC)) that an early dialog has been terminated, before a final response is sent towards the SIP entities. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: C. Holmberg |
| RFC6229 Test Vectors for the Stream Cipher RC4 This document contains test vectors for the stream cipher RC4. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: J. Strombergson, S. Josefsson |
| RFC6230 Media Control Channel Framework This document describes a framework and protocol for application deployment where the application programming logic and media processing are distributed. This implies that application programming logic can seamlessly gain access to appropriate resources that are not co-located on the same physical network entity. The framework uses the Session Initiation Protocol (SIP) to establish an application-level control mechanism between application servers and associated external servers such as media servers. | May 2011 Status: PROPOSED STANDARD Autor: C. Boulton, T. Melanchuk, S. McGlashan |
| RFC6231 An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework This document defines a Media Control Channel Framework Package for Interactive Voice Response (IVR) dialog interaction on media connections and conferences. The package defines dialog management request elements for preparing, starting, and terminating dialog interactions, as well as associated responses and notifications. Dialog interactions are specified in a dialog language. This package defines a lightweight IVR dialog language (supporting prompt playback, runtime controls, Dual-Tone Multi-Frequency (DTMF) collection, and media recording) and allows other dialog languages to be used. The package also defines elements for auditing package capabilities and IVR dialogs. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: S. McGlashan, T. Melanchuk, C. Boulton |
| RFC6232 Purge Originator Identification TLV for IS-IS At present, an IS-IS purge does not contain any information identifying the Intermediate System (IS) that generates the purge. This makes it difficult to locate the source IS. | May 2011 Status: PROPOSED STANDARD Autor: F. Wei, Y. Qin, Z. Li, T. Li, J. Dong |
| RFC6233 IS-IS Registry Extension for Purges IANA maintains the "IS-IS TLV Codepoints" registry. This registry documents which TLVs can appear in different types of IS-IS Protocol Data Units (PDUs), but does not document which TLVs can be found in zero Remaining Lifetime Link State PDUs (LSPs), a.k.a. purges. This document extends the existing registry to record the set of TLVs that are permissible in purges and updates the rules for generating and processing purges in the presence of authentication. This document updates RFC 3563, RFC 5304, and RFC 5310. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: T. Li, L. Ginsberg |
| RFC6234 US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) Federal Information Processing Standard, FIPS | May 2011 Status: INFORMATIONAL Autor: D. Eastlake 3rd, T. Hansen |
| RFC6235 IP Flow Anonymization Support This document describes anonymization techniques for IP flow data and the export of anonymized data using the IP Flow Information Export (IPFIX) protocol. It categorizes common anonymization schemes and defines the parameters needed to describe them. It provides guidelines for the implementation of anonymized data export and storage over IPFIX, and describes an information model and Options- based method for anonymization metadata export within the IPFIX protocol or storage in IPFIX Files. This document defines an Experimental Protocol for the Internet community. | May 2011 Status: EXPERIMENTAL Autor: E. Boschi, B. Trammell |
| RFC6236 Negotiation of Generic Image Attributes in the Session Description Protocol (SDP) This document proposes a new generic session setup attribute to make it possible to negotiate different image attributes such as image size. A possible use case is to make it possible for a \%low-end \%hand- held terminal to display video without the need to rescale the image, something that may consume large amounts of memory and processing power. The document also helps to maintain an optimal bitrate for video as only the image size that is desired by the receiver is transmitted. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: I. Johansson, K. Jung |
| RFC6237 IMAP4 Multimailbox SEARCH Extension The IMAP4 specification allows the searching of only the selected mailbox. A user often wants to search multiple mailboxes, and a client that wishes to support this must issue a series of SELECT and SEARCH commands, waiting for each to complete before moving on to the next. This extension allows a client to search multiple mailboxes with one command, limiting the round trips and waiting for various searches to complete, and not requiring disruption of the currently selected mailbox. This extension also uses MAILBOX and TAG fields in ESEARCH responses, allowing a client to pipeline the searches if it chooses. This document updates RFC 4466. This document defines an Experimental Protocol for the Internet community. | May 2011 Status: EXPERIMENTAL Autor: B. Leiba, A. Melnikov |
| RFC6238 TOTP: Time-Based One-Time Password Algorithm This document describes an extension of the One-Time Password (OTP) algorithm, namely the HMAC-based One-Time Password (HOTP) algorithm, as defined in RFC 4226, to support the time-based moving factor. The HOTP algorithm specifies an event-based OTP algorithm, where the moving factor is an event counter. The present work bases the moving factor on a time value. A time-based variant of the OTP algorithm provides short-lived OTP values, which are desirable for enhanced security. | May 2011 Status: INFORMATIONAL Autor: D. M'Raihi, S. Machani, M. Pei, J. Rydell |
| RFC6239 Suite B Cryptographic Suites for Secure Shell (SSH) This document describes the architecture of a Suite B compliant implementation of the Secure Shell Transport Layer Protocol and the Secure Shell Authentication Protocol. Suite B Secure Shell makes use of the elliptic curve Diffie-Hellman (ECDH) key agreement, the elliptic curve digital signature algorithm (ECDSA), the Advanced Encryption Standard running in Galois/Counter Mode (AES-GCM), two members of the SHA-2 family of hashes (SHA-256 and SHA-384), and X.509 certificates. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: K. Igoe |
| RFC6240 Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP) MIB Using SMIv2 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) circuits over a Packet Switch Network (PSN). [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: D. Zelig, R. Cohen, T. Nadeau |
| RFC6241 Network Configuration Protocol (NETCONF) The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: R. Enns, M. Bjorklund, J. Schoenwaelder, A. Bierman |
| RFC6242 Using the NETCONF Protocol over Secure Shell (SSH) This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: M. Wasserman |
| RFC6243 With-defaults Capability for NETCONF The Network Configuration Protocol (NETCONF) defines ways to read and edit configuration data from a NETCONF server. In some cases, part of this data may not be set by the NETCONF client, but rather a default value known to the server is used instead. In many situations the NETCONF client has a priori knowledge about default data, so the NETCONF server does not need to save it in a NETCONF configuration datastore or send it to the client in a retrieval operation reply. In other situations the NETCONF client will need this data from the server. Not all server implementations treat this default data the same way. This document defines a capability-based extension to the NETCONF protocol that allows the NETCONF client to identify how defaults are processed by the server, and also defines new mechanisms for client control of server processing of default data. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: A. Bierman, B. Lengyel |
| RFC6244 An Architecture for Network Management Using NETCONF and YANG The Network Configuration Protocol (NETCONF) gives access to native capabilities of the devices within a network, defining methods for manipulating configuration databases, retrieving operational data, and invoking specific operations. YANG provides the means to define the content carried via NETCONF, both data and operations. Using both technologies, standard modules can be defined to give interoperability and commonality to devices, while still allowing devices to express their unique capabilities. | June 2011 Status: INFORMATIONAL Autor: P. Shafer |
| RFC6245 Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4 The Generic Routing Encapsulation (GRE) specification contains a Key field, which MAY contain a value that is used to identify a particular GRE data stream. This specification defines a new Mobile IP extension that is used to exchange the value to be used in the GRE Key field. This extension further allows the Mobility Agents to set up the necessary protocol interfaces prior to receiving the mobile node traffic. The new extension allows a Foreign Agent to request GRE tunneling without disturbing the Home Agent behavior specified for Mobile IPv4. GRE tunneling with the Key field allows the operators to have home networks that consist of multiple Virtual Private Networks (VPNs), which may have overlapping home addresses. When the tuple <Care of Address, Home Address, and Home Agent Address> is the same across multiple subscriber sessions, GRE tunneling will provide a means for the Foreign Agent and Home Agent to identify data streams for the individual sessions based on the GRE key. In the absence of this key identifier, the data streams cannot be distinguished from each other -- a significant drawback when using IP-in-IP tunneling. [STANDARDS-TRACK] | May 2011 Status: PROPOSED STANDARD Autor: P. Yegani, K. Leung, A. Lior, K. Chowdhury, J. Navali |
| RFC6246 Virtual Private LAN Service (VPLS) Interoperability with Customer Edge (CE) Bridges One of the main motivations behind Virtual Private LAN Service (VPLS) is its ability to provide connectivity not only among customer routers and servers/hosts but also among customer IEEE bridges. VPLS is expected to deliver the same level of service that current enterprise users are accustomed to from their own enterprise bridged networks or their Ethernet Service Providers. | June 2011 Status: INFORMATIONAL Autor: A. Sajassi, F. Brockners, D. Mohan, Y. Serbest |
| RFC6247 Moving the Undeployed TCP Extensions RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693 to Historic Status This document reclassifies several TCP extensions that have never seen widespread use to Historic status. The affected RFCs are RFC 1072, RFC 1106, RFC 1110, RFC 1145, RFC 1146, RFC 1379, RFC 1644, and RFC 1693. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: L. Eggert |
| RFC6248 RFC 4148 and the IP Performance Metrics (IPPM) Registry of Metrics Are Obsolete This memo reclassifies RFC 4148, "IP Performance Metrics (IPPM) Metrics Registry", as Obsolete, and withdraws the IANA IPPM Metrics Registry itself from use because it is obsolete. The current registry structure has been found to be insufficiently detailed to uniquely identify IPPM metrics. Despite apparent efforts to find current or even future users, no one responded to the call for interest in the RFC 4148 registry during the second half of 2010. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2011 Status: INFORMATIONAL Autor: A. Morton |
| RFC6249 Metalink/HTTP: Mirrors and Hashes This document specifies Metalink/HTTP: Mirrors and Cryptographic Hashes in HTTP header fields, a different way to get information that is usually contained in the Metalink XML-based download description format. Metalink/HTTP describes multiple download locations (mirrors), Peer-to-Peer, cryptographic hashes, digital signatures, and other information using existing standards for HTTP header fields. Metalink clients can use this information to make file transfers more robust and reliable. Normative requirements for Metalink/HTTP clients and servers are described here. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: A. Bryan, N. McNab, T. Tsujikawa, P. Poeml, H. Nordstrom |
| RFC6250 Evolution of the IP Model This RFC attempts to document various aspects of the IP service model and how it has evolved over time. In particular, it attempts to document the properties of the IP layer as they are seen by upper- layer protocols and applications, especially properties that were (and, at times, still are) incorrectly perceived to exist as well as properties that would cause problems if changed. The discussion of these properties is organized around evaluating a set of claims, or misconceptions. Finally, this document provides some guidance to protocol designers and implementers. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: D. Thaler |
| RFC6251 Using Kerberos Version 5 over the Transport Layer Security (TLS) Protocol This document specifies how the Kerberos V5 protocol can be transported over the Transport Layer Security (TLS) protocol in order to provide additional security features. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: S. Josefsson |
| RFC6252 A Framework of Media-Independent Pre-Authentication (MPA) for Inter-Domain Handover Optimization This document describes Media-independent Pre-Authentication (MPA), a new handover optimization mechanism that addresses the issues on existing mobility management protocols and mobility optimization mechanisms to support inter-domain handover. MPA is a mobile- assisted, secure handover optimization scheme that works over any link layer and with any mobility management protocol, and is most applicable to supporting optimization during inter-domain handover. MPA's pre-authentication, pre-configuration, and proactive handover techniques allow many of the handoff-related operations to take place before the mobile node has moved to the new network. We describe the details of all the associated techniques and their applicability for different scenarios involving various mobility protocols during inter-domain handover. We have implemented the MPA mechanism for various network-layer and application-layer mobility protocols, and we report a summary of experimental performance results in this document. | June 2011 Status: INFORMATIONAL Autor: A. Dutta, V. Fajardo, Y. Ohba, K. Taniuchi, H. Schulzrinne |
| RFC6253 Host Identity Protocol Certificates The Certificate (CERT) parameter is a container for digital certificates. It is used for carrying these certificates in Host Identity Protocol (HIP) control packets. This document specifies the CERT parameter and the error signaling in case of a failed verification. Additionally, this document specifies the representations of Host Identity Tags in X.509 version 3 (v3) and Simple Public Key Infrastructure (SPKI) certificates. | May 2011 Status: EXPERIMENTAL Autor: T. Heer, S. Varjonen |
| RFC6254 Request to Move RFC 2754 to Historic Status RFC 2754 requested that each time IANA made an address assignment, it was to create appropriate inetnum and as-block objects and digitally sign them. The purpose was to distribute the IANA-held public key in software implementations of the Distributed Routing Policy System. In practice, this was never done on the public Internet. This document requests that RFC 2754 be moved to Historic status. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: M. McFadden |
| RFC6255 Delay-Tolerant Networking Bundle Protocol IANA Registries The Delay-Tolerant Networking (DTN) Research Group research group has defined many protocols such as the Bundle Protocol and Licklider Transmission Protocol. The specifications of these protocols contain fields that are subject to a registry. For the purpose of its research work, the group created ad hoc registries. As the specifications are stable and have multiple interoperable implementations, the group would like to hand off the registries to IANA for official custody. This document describes the actions executed by IANA. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: M. Blanchet |
| RFC6256 Using Self-Delimiting Numeric Values in Protocols Self-Delimiting Numeric Values (SDNVs) have recently been introduced as a field type in proposed Delay-Tolerant Networking protocols. SDNVs encode an arbitrary-length non-negative integer or arbitrary- length bitstring with minimum overhead. They are intended to provide protocol flexibility without sacrificing economy and to assist in future-proofing protocols under development. This document describes formats and algorithms for SDNV encoding and decoding, along with notes on implementation and usage. This document is a product of the Delay-Tolerant Networking Research Group and has been reviewed by that group. No objections to its publication as an RFC were raised. This document is not an Internet Standards Track specification; it is published for informational purposes. | May 2011 Status: INFORMATIONAL Autor: W. Eddy, E. Davies |
| RFC6257 Bundle Security Protocol Specification This document defines the bundle security protocol, which provides data integrity and confidentiality services for the Bundle Protocol. Separate capabilities are provided to protect the bundle payload and additional data that may be included within the bundle. We also describe various security considerations including some policy options. | May 2011 Status: EXPERIMENTAL Autor: S. Symington, S. Farrell, H. Weiss, P. Lovell |
| RFC6258 Delay-Tolerant Networking Metadata Extension Block This document defines an extension block that may be used with the Delay-Tolerant Networking (DTN) Bundle Protocol. This Metadata Extension Block is designed to carry additional information that DTN nodes can use to make processing decisions regarding bundles, such as deciding whether to store a bundle or determining to which nodes to forward a bundle. The metadata that is carried in a metadata block must be formatted according to the metadata type that is identified in the block's metadata type field. One specific metadata type, for carrying URIs as metadata, is defined in this document. Other metadata types may be defined in separate documents. This document is a product of the Delay Tolerant Networking Research Group and has been reviewed by that group. No objections to its publication as an RFC were raised. This document defines an Experimental Protocol for the Internet community. | May 2011 Status: EXPERIMENTAL Autor: S. Symington |
| RFC6259 Delay-Tolerant Networking Previous-Hop Insertion Block This document defines an extension block for use with the Delay- Tolerant Networking (DTN) Bundle Protocol. This Previous-Hop Insertion Block (PHIB) extension block is designed to be inserted by a forwarding node to provide the endpoint identifier (EID) of an endpoint of which the forwarding node is a member so that this EID may be conveyed to the next-hop receiving node. Knowledge of an EID of an endpoint of which a previous-hop node is a member may be required in some circumstances to support certain routing protocols (e.g., flood routing). If this EID cannot be provided by the convergence layer or other means, the PHIB defines the mechanism whereby the EID can be provided with the bundle. Each PHIB is always removed from the bundle by the receiving node so that its presence within the bundle is limited to exactly one hop. This document defines the format and processing of this PHIB. This document is a product of the Delay-Tolerant Networking Research Group and has been reviewed by that group. No objections to its publication as an RFC were raised. This document defines an Experimental Protocol for the Internet community. | May 2011 Status: EXPERIMENTAL Autor: S. Symington |
| RFC6260 Compressed Bundle Header Encoding (CBHE) This document describes a convention by which Delay-Tolerant Networking (DTN) Bundle Protocol (BP) "convergence-layer" adapters may represent endpoint identifiers in a compressed form within the primary blocks of bundles, provided those endpoint identifiers conform to the structure prescribed by this convention. | May 2011 Status: EXPERIMENTAL Autor: S. Burleigh |
| RFC6261 Encrypted Signaling Transport Modes for the Host Identity Protocol This document specifies two transport modes for Host Identity Protocol (HIP) signaling messages that allow them to be conveyed over encrypted connections initiated with the Host Identity Protocol. This document defines an Experimental Protocol for the Internet community. | May 2011 Status: EXPERIMENTAL Autor: A. Keranen |
| RFC6262 RTP Payload Format for IP-MR Speech Codec This document specifies the payload format for packetization of SPIRIT IP-MR encoded speech signals into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple frames per packet and introduces redundancy for robustness against packet loss and bit errors. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: S. Ikonin |
| RFC6263 Application Mechanism for Keeping Alive the NAT Mappings Associated with RTP / RTP Control Protocol (RTCP) Flows This document lists the different mechanisms that enable applications using the Real-time Transport Protocol (RTP) and the RTP Control Protocol (RTCP) to keep their RTP Network Address Translator (NAT) mappings alive. It also makes a recommendation for a preferred mechanism. This document is not applicable to Interactive Connectivity Establishment (ICE) agents. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: X. Marjou, A. Sollaud |
| RFC6264 An Incremental Carrier-Grade NAT (CGN) for IPv6 Transition Global IPv6 deployment was slower than originally expected. As IPv4 address exhaustion approaches, IPv4 to IPv6 transition issues become more critical and less tractable. Host-based transition mechanisms used in dual-stack environments cannot meet all transition requirements. Most end users are not sufficiently expert to configure or maintain host-based transition mechanisms. Carrier-Grade NAT (CGN) devices with integrated transition mechanisms can reduce the operational changes required during the IPv4 to IPv6 migration or coexistence period. | June 2011 Status: INFORMATIONAL Autor: S. Jiang, D. Guo, B. Carpenter |
| RFC6265 HTTP State Management Mechanism This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP protocol. Although cookies have many historical infelicities that degrade their security and privacy, the Cookie and Set-Cookie header fields are widely used on the Internet. This document obsoletes RFC 2965. [STANDARDS-TRACK] | April 2011 Status: PROPOSED STANDARD Autor: A. Barth |
| RFC6266 Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP) RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: J. Reschke |
| RFC6267 MIKEY-IBAKE: Identity-Based Authenticated Key Exchange (IBAKE) Mode of Key Distribution in Multimedia Internet KEYing (MIKEY) This document describes a key management protocol variant for the Multimedia Internet KEYing (MIKEY) protocol that relies on a trusted key management service. In particular, this variant utilizes Identity-Based Authenticated Key Exchange (IBAKE) framework that allows the participating clients to perform mutual authentication and derive a session key in an asymmetric Identity-Based Encryption (IBE) framework. This protocol, in addition to providing mutual authentication, eliminates the key escrow problem that is common in standard IBE and provides perfect forward and backward secrecy. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: V. Cakulev, G. Sundaram |
| RFC6268 Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX) The Cryptographic Message Syntax (CMS) format, and many associated formats, are expressed using ASN.1. The current ASN.1 modules conform to the 1988 version of ASN.1. This document updates some auxiliary ASN.1 modules to conform to the 2008 version of ASN.1; the 1988 ASN.1 modules remain the normative version. There are no bits- on-the-wire changes to any of the formats; this is simply a change to the syntax. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: J. Schaad, S. Turner |
| RFC6269 Issues with IP Address Sharing The completion of IPv4 address allocations from IANA and the Regional Internet Registries (RIRs) is causing service providers around the world to question how they will continue providing IPv4 connectivity service to their subscribers when there are no longer sufficient IPv4 addresses to allocate them one per subscriber. Several possible solutions to this problem are now emerging based around the idea of shared IPv4 addressing. These solutions give rise to a number of issues, and this memo identifies those common to all such address sharing approaches. Such issues include application failures, additional service monitoring complexity, new security vulnerabilities, and so on. Solution-specific discussions are out of scope. | June 2011 Status: INFORMATIONAL Autor: M. Ford, M. Boucadair, A. Durand, P. Levis, P. Roberts |
| RFC6270 The 'tn3270' URI Scheme This document is the specification of the 'tn3270' Uniform Resource Identifier (URI) scheme, which is used to designate the access to the resources available via Telnet 3270 mode (TN3270) and Telnet 3270 Enhanced mode (TN3270E). It updates RFC 1041 and RFC 2355, which specify these protocols, and RFC 1738, which firstly mentioned this URI scheme without defining its syntax and semantics. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: M. Yevstifeyev |
| RFC6271 Requirements for SIP-Based Session Peering This memo captures protocol requirements to enable session peering of voice, presence, instant messaging, and other types of multimedia traffic. This informational document is intended to link the various use cases described for session peering to protocol solutions. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: J-F. Mule |
| RFC6272 Internet Protocols for the Smart Grid This note identifies the key infrastructure protocols of the Internet Protocol Suite for use in the Smart Grid. The target audience is those people seeking guidance on how to construct an appropriate Internet Protocol Suite profile for the Smart Grid. In practice, such a profile would consist of selecting what is needed for Smart Grid deployment from the picture presented here. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: F. Baker, D. Meyer |
| RFC6273 The Secure Neighbor Discovery (SEND) Hash Threat Analysis This document analyzes the use of hashes in Secure Neighbor Discovery (SEND), the possible threats to these hashes and the impact of recent attacks on hash functions used by SEND. The SEND specification currently uses the SHA-1 hash algorithm and PKIX certificates and does not provide support for hash algorithm agility. This document provides an analysis of possible threats to the hash algorithms used in SEND. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: A. Kukec, S. Krishnan, S. Jiang |
| RFC6274 Security Assessment of the Internet Protocol Version 4 This document contains a security assessment of the IETF specifications of the Internet Protocol version 4 and of a number of mechanisms and policies in use by popular IPv4 implementations. It is based on the results of a project carried out by the UK's Centre for the Protection of National Infrastructure (CPNI). This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: F. Gont |
| RFC6275 Mobility Support in IPv6 This document specifies Mobile IPv6, a protocol that 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. This document obsoletes RFC 3775. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: C. Perkins, D. Johnson, J. Arkko |
| RFC6276 DHCPv6 Prefix Delegation for Network Mobility (NEMO) One aspect of network mobility support is the assignment of a prefix or prefixes to a mobile router for use on the links in the mobile network. This document specifies how DHCPv6 prefix delegation can be used for this configuration task. The mobile router plays the role of requesting router, while the home agent assumes the role of delegating router. When the mobile router is outside its home network, the mobile router also assumes the role of DHCPv6 relay agent, co-located with the requesting router function. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: R. Droms, P. Thubert, F. Dupont, W. Haddad, C. Bernardos |
| RFC6277 Online Certificate Status Protocol Algorithm Agility The Online Certificate Status Protocol (OCSP) requires server responses to be signed but does not specify a mechanism for selecting the signature algorithm to be used. This may lead to avoidable interoperability failures in contexts where multiple signature algorithms are in use. This document specifies rules for server signature algorithm selection and an extension that allows a client to advise a server that specific signature algorithms are supported. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: S. Santesson, P. Hallam-Baker |
| RFC6278 Use of Static-Static Elliptic Curve Diffie-Hellman Key Agreement in Cryptographic Message Syntax This document describes how to use the 'static-static Elliptic Curve Diffie-Hellman key-agreement scheme (i.e., Elliptic Curve Diffie- Hellman where both participants use static Diffie-Hellman values) with the Cryptographic Message Syntax. In this form of key agreement, the Diffie-Hellman values of both the sender and receiver are long-term values contained in certificates. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: J. Herzog, R. Khazan |
| RFC6279 Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem Statement Proxy Mobile IPv6 is the IETF Standard for network-based mobility management. In Proxy Mobile IPv6, mobile nodes are topologically anchored at a Local Mobility Anchor, which forwards all data for registered mobile nodes. The setup and maintenance of localized routing, which allows forwarding of data packets between two mobile nodes' Mobility Access Gateways without involvement of their Local Mobility Anchor in forwarding, is not considered. This document describes the problem space of localized routing in Proxy Mobile IPv6. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: M. Liebsch, S. Jeong, Q. Wu |
| RFC6280 An Architecture for Location and Location Privacy in Internet Applications Location-based services (such as navigation applications, emergency services, and management of equipment in the field) need geographic location information about Internet hosts, their users, and other related entities. These applications need to securely gather and transfer location information for location services, and at the same time protect the privacy of the individuals involved. This document describes an architecture for privacy-preserving location-based services in the Internet, focusing on authorization, security, and privacy requirements for the data formats and protocols used by these services. This memo documents an Internet Best Current Practice. | July 2011 Status: BEST CURRENT PRACTICE Autor: R. Barnes, M. Lepinski, A. Cooper, J. Morris, H. Tschofenig, H. Schulzrinne |
| RFC6281 Understanding Apple's Back to My Mac (BTMM) Service This document describes the implementation of Apple Inc.'s Back to My Mac (BTMM) service. BTMM provides network connectivity between devices so that a user can perform file sharing and screen sharing among multiple computers at home, at work, or on the road. The implementation of BTMM addresses the issues of single sign-on authentication, secure data communication, service discovery, and end-to-end connectivity in the face of Network Address Translators (NATs) and mobility of devices. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: S. Cheshire, Z. Zhu, R. Wakikawa, L. Zhang |
| RFC6282 Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based Networks This document updates RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks". This document specifies an IPv6 header compression format for IPv6 packet delivery in Low Power Wireless Personal Area Networks (6LoWPANs). The compression format relies on shared context to allow compression of arbitrary prefixes. How the information is maintained in that shared context is out of scope. This document specifies compression of multicast addresses and a framework for compressing next headers. UDP header compression is specified within this framework. [STANDARDS-TRACK] | September 2011 Status: PROPOSED STANDARD Autor: J. Hui, P. Thubert |
| RFC6283 Extensible Markup Language Evidence Record Syntax (XMLERS) In many scenarios, users must be able to demonstrate the (time of) existence, integrity, and validity of data including signed data for long or undetermined periods of time. This document specifies XML syntax and processing rules for creating evidence for long-term non- repudiation of existence and integrity of data. The Extensible Markup Language Evidence Record Syntax XMLERS provides alternative syntax and processing rules to the ASN.1 (Abstract Syntax Notation One) ERS (Evidence Record Syntax) (RFC 4998) syntax by using XML. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: A. Jerman Blazic, S. Saljic, T. Gondrom |
| RFC6284 Port Mapping between Unicast and Multicast RTP Sessions This document presents a port mapping solution that allows RTP receivers to choose their own ports for an auxiliary unicast session in RTP applications using both unicast and multicast services. The solution provides protection against denial-of-service or packet amplification attacks that could be used to cause one or more RTP packets to be sent to a victim client. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: A. Begen, D. Wing, T. Van Caenegem |
| RFC6285 Unicast-Based Rapid Acquisition of Multicast RTP Sessions When an RTP receiver joins a multicast session, it may need to acquire and parse certain Reference Information before it can process any data sent in the multicast session. Depending on the join time, length of the Reference Information repetition (or appearance) interval, size of the Reference Information, and the application and transport properties, the time lag before an RTP receiver can usefully consume the multicast data, which we refer to as the Acquisition Delay, varies and can be large. This is an undesirable phenomenon for receivers that frequently switch among different multicast sessions, such as video broadcasts. | June 2011 Status: PROPOSED STANDARD Autor: B. Ver Steeg, A. Begen, T. Van Caenegem, Z. Vax |
| RFC6286 Autonomous-System-Wide Unique BGP Identifier for BGP-4 To accommodate situations where the current requirements for the BGP Identifier are not met, this document relaxes the definition of the BGP Identifier to be a 4-octet, unsigned, non-zero integer and relaxes the "uniqueness" requirement so that only Autonomous-System-wide (AS-wide) uniqueness of the BGP Identifiers is required. These revisions to the base BGP specification do not introduce any backward compatibility issues. This document updates RFC 4271. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: E. Chen, J. Yuan |
| RFC6287 OCRA: OATH Challenge-Response Algorithm This document describes an algorithm for challenge-response authentication developed by the Initiative for Open Authentication (OATH). The specified mechanisms leverage the HMAC-based One-Time Password (HOTP) algorithm and offer one-way and mutual authentication, and electronic signature capabilities. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: D. M'Raihi, J. Rydell, S. Bajaj, S. Machani, D. Naccache |
| RFC6288 URN Namespace for the Defence Geospatial Information Working Group (DGIWG) This document describes the Namespace Identifier (NID) for Uniform Resource Name (URN) Namespace resources published by the Defence Geospatial Information Working Group (DGIWG). The DGIWG defines and manages resources that utilize this URN name model. | August 2011 Status: INFORMATIONAL Autor: C. Reed |
| RFC6289 A Uniform Resource Name (URN) Namespace for CableLabs This document describes the Namespace Identifier (NID) 'cablelabs' for Uniform Resource Names (URNs) used to identify resources published by Cable Television Laboratories, Inc. (CableLabs). CableLabs specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the manager of the CableLabs' Assigned Names and Numbers registry. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: E. Cardona, S. Channabasappa, J-F. Mule |
| RFC6290 A Quick Crash Detection Method for the Internet Key Exchange Protocol (IKE) This document describes an extension to the Internet Key Exchange Protocol version 2 (IKEv2) that allows for faster detection of Security Association (SA) desynchronization using a saved token. | June 2011 Status: PROPOSED STANDARD Autor: Y. Nir, D. Wierbowski, F. Detienne, P. Sethi |
| RFC6291 Guidelines for the Use of the "OAM" Acronym in the IETF At first glance, the acronym "OAM" seems to be well-known and well-understood. Looking at the acronym a bit more closely reveals a set of recurring problems that are revisited time and again. | June 2011 Status: BEST CURRENT PRACTICE Autor: L. Andersson, H. van Helvoort, R. Bonica, D. Romascanu, S. Mansfield |
| RFC6292 Requirements for a Working Group Charter Tool The IETF intends to provide a new tool to Area Directors for the creation, re-chartering, and closing of Working Groups. The tool will also allow the IETF community to view the status of the chartering process. This document describes the requirements for the proposed new tool, and it is intended as input to a later activity for the design and development of such a tool. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: P. Hoffman |
| RFC6293 Requirements for Internet-Draft Tracking by the IETF Community in the Datatracker The document gives a set of requirements for extending the IETF Datatracker to give individual IETF community members, including the IETF leadership, easy methods for tracking the progress of the Internet-Drafts and RFCs of interest to them. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: P. Hoffman |
| RFC6294 Survey of Proposed Use Cases for the IPv6 Flow Label The IPv6 protocol includes a flow label in every packet header, but this field is not used in practice. This paper describes the flow label standard and discusses the implementation issues that it raises. It then describes various published proposals for using the flow label and shows that most of them are inconsistent with the standard. Methods to address this problem are briefly reviewed. We also question whether the standard should be revised. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: Q. Hu, B. Carpenter |
| RFC6295 RTP Payload Format for MIDI This memo describes a Real-time Transport Protocol (RTP) payload format for the MIDI (Musical Instrument Digital Interface) command language. The format encodes all commands that may legally appear on a MIDI 1.0 DIN cable. The format is suitable for interactive applications (such as network musical performance) and content-delivery applications (such as file streaming). The format may be used over unicast and multicast UDP and TCP, and it defines tools for graceful recovery from packet loss. Stream behavior, including the MIDI rendering method, may be customized during session setup. The format also serves as a mode for the mpeg4-generic format, to support the MPEG 4 Audio Object Types for General MIDI, Downloadable Sounds Level 2, and Structured Audio. This document obsoletes RFC 4695. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: J. Lazzaro, J. Wawrzynek |
| RFC6296 IPv6-to-IPv6 Network Prefix Translation This document describes a stateless, transport-agnostic IPv6-to-IPv6 Network Prefix Translation (NPTv6) function that provides the address-independence benefit associated with IPv4-to-IPv4 NAT (NAPT44) and provides a 1:1 relationship between addresses in the "inside" and "outside" prefixes, preserving end-to-end reachability at the network layer. This document defines an Experimental Protocol for the Internet community. | June 2011 Status: EXPERIMENTAL Autor: M. Wasserman, F. Baker |
| RFC6297 A Survey of Lower-than-Best-Effort Transport Protocols This document provides a survey of transport protocols that are designed to have a smaller bandwidth and/or delay impact on standard TCP than standard TCP itself when they share a bottleneck with it. Such protocols could be used for delay-insensitive "background" traffic, as they provide what is sometimes called a "less than" (or "lower than") best-effort service. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: M. Welzl, D. Ros |
| RFC6298 Computing TCP's Retransmission Timer This document defines the standard algorithm that Transmission Control Protocol (TCP) senders are required to use to compute and manage their retransmission timer. It expands on the discussion in Section 4.2.3.1 of RFC 1122 and upgrades the requirement of supporting the algorithm from a SHOULD to a MUST. This document obsoletes RFC 2988. [STANDARDS-TRACK] | June 2011 Status: PROPOSED STANDARD Autor: V. Paxson, M. Allman, J. Chu, M. Sargent |
| RFC6301 A Survey of Mobility Support in the Internet Over the last two decades, many efforts have been devoted to developing solutions for mobility support over the global Internet, resulting in a variety of proposed solutions. We conducted a systematic survey of the previous efforts to gain an overall understanding on the solution space of mobility support. This document reports our findings and identifies remaining issues in providing ubiquitous and efficient Internet mobility support on a global scale. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: Z. Zhu, R. Wakikawa, L. Zhang |
| RFC6302 Logging Recommendations for Internet-Facing Servers In the wake of IPv4 exhaustion and deployment of IP address sharing techniques, this document recommends that Internet-facing servers log port number and accurate timestamps in addition to the incoming IP address. This memo documents an Internet Best Current Practice. | June 2011 Status: BEST CURRENT PRACTICE Autor: A. Durand, I. Gashinsky, D. Lee, S. Sheppard |
| RFC6303 Locally Served DNS Zones Experience with the Domain Name System (DNS) has shown that there are a number of DNS zones that all iterative resolvers and recursive nameservers should automatically serve, unless configured otherwise. RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This document extends the practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space and other well-known zones with similar characteristics. This memo documents an Internet Best Current Practice. | July 2011 Status: BEST CURRENT PRACTICE Autor: M. Andrews |
| RFC6304 AS112 Nameserver Operations Many sites connected to the Internet make use of IPv4 addresses that are not globally unique. Examples are the addresses designated in RFC 1918 for private use within individual sites. | July 2011 Status: INFORMATIONAL Autor: J. Abley, W. Maton |
| RFC6305 I'm Being Attacked by PRISONER.IANA.ORG! Many sites connected to the Internet make use of IPv4 addresses that are not globally unique. Examples are the addresses designated in RFC 1918 for private use within individual sites. | July 2011 Status: INFORMATIONAL Autor: J. Abley, W. Maton |
| RFC6306 Hierarchical IPv4 Framework This document describes a framework for how the current IPv4 address space can be divided into two new address categories: a core address space (Area Locators, ALOCs) that is globally unique, and an edge address space (Endpoint Locators, ELOCs) that is regionally unique. In the future, the ELOC space will only be significant in a private network or in a service provider domain. Therefore, a 32x32 bit addressing scheme and a hierarchical routing architecture are achieved. The hierarchical IPv4 framework is backwards compatible with the current IPv4 Internet. | July 2011 Status: EXPERIMENTAL Autor: P. Frejborg |
| RFC6308 Overview of the Internet Multicast Addressing Architecture The lack of up-to-date documentation on IP multicast address allocation and assignment procedures has caused a great deal of confusion. To clarify the situation, this memo describes the allocation and assignment techniques and mechanisms currently (as of this writing) in use. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: P. Savola |
| RFC6309 IANA Rules for MIKEY (Multimedia Internet KEYing) This document clarifies and relaxes the IANA rules for Multimedia Internet KEYing (MIKEY). This document updates RFCs 3830, 4563, 5410, and 6043; it obsoletes RFC 4909. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: J. Arkko, A. Keranen, J. Mattsson |
| RFC6310 Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message Mapping This document specifies the mapping and notification of defect states between a pseudowire (PW) and the Attachment Circuits (ACs) of the end-to-end emulated service. It standardizes the behavior of Provider Edges (PEs) with respect to PW and AC defects. It addresses ATM, Frame Relay, Time Division Multiplexing (TDM), and Synchronous Optical Network / Synchronous Digital Hierarchy (SONET/SDH) PW services, carried over MPLS, MPLS/IP, and Layer 2 Tunneling Protocol version 3/IP (L2TPv3/IP) Packet Switched Networks (PSNs). [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: M. Aissaoui, P. Busschbach, L. Martini, M. Morrow, T. Nadeau, Y(J). Stein |
| RFC6311 Protocol Support for High Availability of IKEv2/IPsec The IPsec protocol suite is widely used for business-critical network traffic. In order to make IPsec deployments highly available, more scalable, and failure-resistant, they are often implemented as IPsec High Availability (HA) clusters. However, there are many issues in IPsec HA clustering, and in particular in Internet Key Exchange Protocol version 2 (IKEv2) clustering. An earlier document, "IPsec Cluster Problem Statement", enumerates the issues encountered in the IKEv2/IPsec HA cluster environment. This document resolves these issues with the least possible change to the protocol. | July 2011 Status: PROPOSED STANDARD Autor: R. Singh, G. Kalyani, Y. Nir, Y. Sheffer, D. Zhang |
| RFC6312 Mobile Networks Considerations for IPv6 Deployment Mobile Internet access from smartphones and other mobile devices is accelerating the exhaustion of IPv4 addresses. IPv6 is widely seen as crucial for the continued operation and growth of the Internet, and in particular, it is critical in mobile networks. This document discusses the issues that arise when deploying IPv6 in mobile networks. Hence, this document can be a useful reference for service providers and network designers. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: R. Koodli |
| RFC6313 Export of Structured Data in IP Flow Information Export (IPFIX) This document specifies an extension to the IP Flow Information Export (IPFIX) protocol specification in RFC 5101 and the IPFIX information model specified in RFC 5102 to support hierarchical structured data and lists (sequences) of Information Elements in data records. This extension allows definition of complex data structures such as variable-length lists and specification of hierarchical containment relationships between Templates. Finally, the semantics are provided in order to express the relationship among multiple list elements in a structured data record. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: B. Claise, G. Dhandapani, P. Aitken, S. Yates |
| RFC6314 NAT Traversal Practices for Client-Server SIP Traversal of the Session Initiation Protocol (SIP) and the sessions it establishes through Network Address Translators (NATs) is a complex problem. Currently, there are many deployment scenarios and traversal mechanisms for media traffic. This document provides concrete recommendations and a unified method for NAT traversal as well as documents corresponding flows. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: C. Boulton, J. Rosenberg, G. Camarillo, F. Audet |
| RFC6315 IANA Registration for Enumservice 'iax' This document registers an Enumservice for the Inter-Asterisk eXchange (IAX) protocol according to the guidelines given in RFC 6117. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: E. Guy, K. Darilion |
| RFC6316 Sockets Application Program Interface (API) for Multihoming Shim This document specifies sockets API extensions for the multihoming shim layer. The API aims to enable interactions between applications and the multihoming shim layer for advanced locator management, and access to information about failure detection and path exploration. | July 2011 Status: INFORMATIONAL Autor: M. Komu, M. Bagnulo, K. Slavov, S. Sugimoto |
| RFC6317 Basic Socket Interface Extensions for the Host Identity Protocol (HIP) This document defines extensions to the current sockets API for the Host Identity Protocol (HIP). The extensions focus on the use of public-key-based identifiers discovered via DNS resolution, but also define interfaces for manual bindings between Host Identity Tags (HITs) and locators. With the extensions, the application can also support more relaxed security models where communication can be non-HIP-based, according to local policies. The extensions in this document are experimental and provide basic tools for further experimentation with policies. This document defines an Experimental Protocol for the Internet community. | July 2011 Status: EXPERIMENTAL Autor: M. Komu, T. Henderson |
| RFC6318 Suite B in Secure/Multipurpose Internet Mail Extensions (S/MIME) This document specifies the conventions for using the United States National Security Agency's Suite B algorithms in Secure/Multipurpose Internet Mail Extensions (S/MIME) as specified in RFC 5751. This document obsoletes RFC 5008. This document is not an Internet Standards Track specification; it is published for informational purposes. | June 2011 Status: INFORMATIONAL Autor: R. Housley, J. Solinas |
| RFC6319 Issues Associated with Designating Additional Private IPv4 Address Space When a private network or internetwork grows very large, it is sometimes not possible to address all interfaces using private IPv4 address space because there are not enough addresses. This document describes the problems faced by those networks, the available options, and the issues involved in assigning a new block of private IPv4 address space. | July 2011 Status: INFORMATIONAL Autor: M. Azinger, L. Vegoda |
| RFC6320 Protocol for Access Node Control Mechanism in Broadband Networks This document describes the Access Node Control Protocol (ANCP). ANCP operates between a Network Access Server (NAS) and an Access Node (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)) in a multi-service reference architecture in order to perform operations related to Quality of Service, service, and subscribers. Use cases for ANCP are documented in RFC 5851. As well as describing the base ANCP protocol, this document specifies capabilities for Digital Subscriber Line (DSL) topology discovery, line configuration, and remote line connectivity testing. The design of ANCP allows for protocol extensions in other documents if they are needed to support other use cases and other access technologies. | October 2011 Status: PROPOSED STANDARD Autor: S. Wadhwa, J. Moisand, T. Haag, N. Voigt, T. Taylor |
| RFC6321 xCal: The XML Format for iCalendar This specification defines "xCal", an XML format for iCalendar data. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: C. Daboo, M. Douglass, S. Lees |
| RFC6322 Datatracker States and Annotations for the IAB, IRTF, and Independent Submission Streams This document describes extending the IETF Datatracker to capture and display the progression of Internet-Drafts that are intended to be published as RFCs by the IAB, IRTF, or Independent Submissions Editor. The states and annotations that are to be added to the Datatracker will be applied to Internet-Drafts as soon as any of these streams identify the Internet-Draft as a potential eventual RFC, and will continue through the lifetime of the Internet-Draft. The goal of adding this information to the Datatracker is to give the whole Internet community more information about the status of these Internet-Drafts and the streams from which they originate. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: P. Hoffman |
| RFC6323 Sender RTT Estimate Option for the Datagram Congestion Control Protocol (DCCP) This document specifies an update to the round-trip time (RTT) estimation algorithm used for TFRC (TCP-Friendly Rate Control) congestion control by the Datagram Congestion Control Protocol (DCCP). It updates specifications for the CCID-3 and CCID-4 Congestion Control IDs of DCCP. | July 2011 Status: PROPOSED STANDARD Autor: G. Renker, G. Fairhurst |
| RFC6324 Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations This document is concerned with security vulnerabilities in IPv6-in- IPv4 automatic tunnels. These vulnerabilities allow an attacker to take advantage of inconsistencies between the IPv4 routing state and the IPv6 routing state. The attack forms a routing loop that can be abused as a vehicle for traffic amplification to facilitate denial- of-service (DoS) attacks. The first aim of this document is to inform on this attack and its root causes. The second aim is to present some possible mitigation measures. It should be noted that at the time of this writing there are no known reports of malicious attacks exploiting these vulnerabilities. Nonetheless, these vulnerabilities can be activated by accidental misconfiguration. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: G. Nakibly, F. Templin |
| RFC6325 Routing Bridges (RBridges): Base Protocol Specification Routing Bridges (RBridges) provide optimal pair-wise forwarding without configuration, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. They achieve these goals using IS-IS routing and encapsulation of traffic with a header that includes a hop count. | July 2011 Status: PROPOSED STANDARD Autor: R. Perlman, D. Eastlake 3rd, D. Dutt, S. Gai, A. Ghanwani |
| RFC6326 Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS The IETF has standardized the Transparent Interconnection of Lots of Links (TRILL) protocol, which provides transparent Layer 2 forwarding using encapsulation with a hop count and IS-IS link state routing. This document specifies the data formats and code points for the IS-IS extensions to support TRILL. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: D. Eastlake, A. Banerjee, D. Dutt, R. Perlman, A. Ghanwani |
| RFC6327 Routing Bridges (RBridges): Adjacency The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides optimal pair-wise data forwarding without configuration, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using IS-IS (Intermediate System to Intermediate System) link state routing and by encapsulating traffic using a header that includes a hop count. Devices that implement TRILL are called Routing Bridges (RBridges). | July 2011 Status: PROPOSED STANDARD Autor: D. Eastlake 3rd, R. Perlman, A. Ghanwani, D. Dutt, V. Manral |
| RFC6328 IANA Considerations for Network Layer Protocol Identifiers Some protocols being developed or extended by the IETF make use of the ISO/IEC (International Organization for Standardization / International Electrotechnical Commission) Network Layer Protocol Identifier (NLPID). This document provides NLPID IANA considerations. This memo documents an Internet Best Current Practice. | July 2011 Status: BEST CURRENT PRACTICE Autor: D. Eastlake 3rd |
| RFC6330 RaptorQ Forward Error Correction Scheme for Object Delivery This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 6, for the RaptorQ FEC code and its application to reliable delivery of data objects. | August 2011 Status: PROPOSED STANDARD Autor: M. Luby, A. Shokrollahi, M. Watson, T. Stockhammer, L. Minder |
| RFC6331 Moving DIGEST-MD5 to Historic This memo describes problems with the DIGEST-MD5 Simple Authentication and Security Layer (SASL) mechanism as specified in RFC 2831. It marks DIGEST-MD5 as OBSOLETE in the IANA Registry of SASL mechanisms and moves RFC 2831 to Historic status. This document is not an Internet Standards Track specification; it is published for informational purposes. | July 2011 Status: INFORMATIONAL Autor: A. Melnikov |
| RFC6332 Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs) In most RTP-based multicast applications, the RTP source sends inter- related data. Due to this interdependency, randomly joining RTP receivers usually cannot start consuming the multicast data right after they join the session. Thus, they often experience a random acquisition delay. An RTP receiver can use one or more different approaches to achieve rapid acquisition. Yet, due to various factors, performance of the rapid acquisition methods usually varies. Furthermore, in some cases, the RTP receiver can do a simple multicast join (in other cases, it is compelled to do so). For quality reporting, monitoring, and diagnostic purposes, it is important to collect detailed information from the RTP receivers about their acquisition and presentation experiences. This document addresses this issue by defining a new report block type, called the Multicast Acquisition (MA) report block, within the framework of RTP Control Protocol (RTCP) Extended Reports (XRs) (RFC 3611). This document also defines the necessary signaling of the new MA report block type in the Session Description Protocol (SDP). [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: A. Begen, E. Friedrich |
| RFC6333 Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion This document revisits the dual-stack model and introduces the Dual- Stack Lite technology aimed at better aligning the costs and benefits of deploying IPv6 in service provider networks. Dual-Stack Lite enables a broadband service provider to share IPv4 addresses among customers by combining two well-known technologies: IP in IP (IPv4- in-IPv6) and Network Address Translation (NAT). [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: A. Durand, R. Droms, J. Woodyatt, Y. Lee |
| RFC6334 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite This document specifies a DHCPv6 option that is meant to be used by a Dual-Stack Lite Basic Bridging BroadBand (B4) element to discover the IPv6 address of its corresponding Address Family Transition Router (AFTR). [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: D. Hankins, T. Mrugalski |
| RFC6335 Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the registry. | August 2011 Status: BEST CURRENT PRACTICE Autor: M. Cotton, L. Eggert, J. Touch, M. Westerlund, S. Cheshire |
| RFC6336 IANA Registry for Interactive Connectivity Establishment (ICE) Options It has been identified that "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols" (RFC 5245) is missing a registry for ICE options. This document defines this missing IANA registry and updates RFC 5245. [STANDARDS-TRACK] | July 2011 Status: PROPOSED STANDARD Autor: M. Westerlund, C. Perkins |
| RFC6337 Session Initiation Protocol (SIP) Usage of the Offer/Answer Model The Session Initiation Protocol (SIP) utilizes the offer/answer model to establish and update multimedia sessions using the Session Description Protocol (SDP). The description of the offer/answer model in SIP is dispersed across multiple RFCs. This document summarizes all the current usages of the offer/answer model in SIP communication. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: S. Okumura, T. Sawada, P. Kyzivat |
| RFC6338 Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC) This document describes a Uniform Resource Name (URN) namespace for the Schema for Academia (SCHAC). | August 2011 Status: INFORMATIONAL Autor: V. Giralt, R. McDuff |
| RFC6339 Context Token Encapsulate/Decapsulate and OID Comparison Functions for the Generic Security Service Application Program Interface (GSS-API) This document describes three abstract Generic Security Service Application Program Interface (GSS-API) interfaces used to encapsulate/decapsulate context tokens and compare OIDs. This document also specifies C bindings for the abstract interfaces. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: S. Josefsson, L. Hornquist Astrand |
| RFC6340 Textual Conventions for the Representation of Floating-Point Numbers This memo defines a Management Information Base (MIB) module containing textual conventions (TCs) to represent floating-point numbers. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: R. Presuhn |
| RFC6341 Use Cases and Requirements for SIP-Based Media Recording (SIPREC) Session recording is a critical requirement in many business communications environments, such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons. In others, calls may be recorded for quality control or business analytics. | August 2011 Status: INFORMATIONAL Autor: K. Rehor, L. Portman, A. Hutton, R. Jain |
| RFC6342 Mobile Networks Considerations for IPv6 Deployment Mobile Internet access from smartphones and other mobile devices is accelerating the exhaustion of IPv4 addresses. IPv6 is widely seen as crucial for the continued operation and growth of the Internet, and in particular, it is critical in mobile networks. This document discusses the issues that arise when deploying IPv6 in mobile networks. Hence, this document can be a useful reference for service providers and network designers. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: R. Koodli |
| RFC6343 Advisory Guidelines for 6to4 Deployment This document provides advice to network operators about deployment of the 6to4 technique for automatic tunneling of IPv6 over IPv4. It is principally addressed to Internet Service Providers (ISPs), including those that do not yet support IPv6, and to Content Providers. Some advice to implementers is also included. The intention of the advice is to minimize both user dissatisfaction and help-desk calls. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: B. Carpenter |
| RFC6344 Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS) This document describes requirements for, and the use of, the Generalized Multi-Protocol Label Switching (GMPLS) control plane in support of the Virtual Concatenation (VCAT) layer 1 inverse multiplexing data plane mechanism and its companion Link Capacity Adjustment Scheme (LCAS). LCAS can be used for hitless dynamic resizing of the inverse multiplex group. These techniques apply to Optical Transport Network (OTN), Synchronous Optical Network (SONET), Synchronous Digital Hierarchy (SDH), and Plesiochronous Digital Hierarchy (PDH) signals. This document updates RFC 4606 by making modifications to the procedures for supporting virtual concatenation. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: G. Bernstein, D. Caviglia, R. Rabbat, H. van Helvoort |
| RFC6345 Protocol for Carrying Authentication for Network Access (PANA) Relay Element This document specifies Protocol for carrying Authentication for Network Access (PANA) Relay Element functionality, which enables PANA messaging between a PANA Client (PaC) and a PANA Authentication Agent (PAA) where the two nodes cannot reach each other by means of regular IP routing. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: P. Duffy, S. Chakrabarti, R. Cragie, Y. Ohba, A. Yegin |
| RFC6346 The Address plus Port (A+P) Approach to the IPv4 Address Shortage We are facing the exhaustion of the IANA IPv4 free IP address pool. Unfortunately, IPv6 is not yet deployed widely enough to fully replace IPv4, and it is unrealistic to expect that this is going to change before the depletion of IPv4 addresses. Letting hosts seamlessly communicate in an IPv4 world without assigning a unique globally routable IPv4 address to each of them is a challenging problem. | August 2011 Status: EXPERIMENTAL Autor: R. Bush |
| RFC6347 Datagram Transport Layer Security Version 1.2 This document specifies version 1.2 of the Datagram Transport Layer Security (DTLS) protocol. The DTLS protocol provides communications privacy for datagram protocols. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the Transport Layer Security (TLS) protocol and provides equivalent security guarantees. Datagram semantics of the underlying transport are preserved by the DTLS protocol. This document updates DTLS 1.0 to work with TLS version 1.2. [STANDARDS-TRACK] | January 2012 Status: PROPOSED STANDARD Autor: E. Rescorla, N. Modadugu |
| RFC6348 Requirements for Point-to-Multipoint Extensions to the Label Distribution Protocol This document lists a set of functional requirements that served as input to the design of Label Distribution Protocol (LDP) extensions for setting up point-to-multipoint (P2MP) Label Switched Paths (LSP), in order to deliver point-to-multipoint applications over a Multiprotocol Label Switching (MPLS) infrastructure. | September 2011 Status: HISTORIC Autor: JL. Le Roux, T. Morin |
| RFC6349 Framework for TCP Throughput Testing This framework describes a practical methodology for measuring end- to-end TCP Throughput in a managed IP network. The goal is to provide a better indication in regard to user experience. In this framework, TCP and IP parameters are specified to optimize TCP Throughput. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: B. Constantine, G. Forget, R. Geib, R. Schrage |
| RFC6350 vCard Format Specification This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: S. Perreault |
| RFC6351 xCard: vCard XML Representation This document defines the XML schema of the vCard data format. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: S. Perreault |
| RFC6352 CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV) This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing contact information based on the vCard format. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: C. Daboo |
| RFC6353 Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) This document describes a Transport Model for the Simple Network Management Protocol (SNMP), that uses either the Transport Layer Security protocol or the Datagram Transport Layer Security (DTLS) protocol. The TLS and DTLS protocols provide authentication and privacy services for SNMP applications. This document describes how the TLS Transport Model (TLSTM) implements the needed features of an SNMP Transport Subsystem to make this protection possible in an interoperable way. | July 2011 Status: DRAFT STANDARD Autor: W. Hardaker |
| RFC6354 Forward-Shifted RTP Redundancy Payload Support This document defines a simple enhancement to support RTP sessions with forward-shifted redundant encodings, i.e., redundant data sent before the corresponding primary data. Forward-shifted redundancy can be used to conceal losses of a large number of consecutive media frames (e.g., consecutive loss of seconds or even tens of seconds of media). [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: Q. Xie |
| RFC6355 Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID) This document defines a new DHCPv6 Unique Identifier (DUID) type called DUID-UUID. DUID-UUIDs are derived from the already-standardized Universally Unique IDentifier (UUID) format. DUID-UUID makes it possible for devices to use UUIDs to identify themselves to DHC servers and vice versa. UUIDs are globally unique and readily available on many systems, making them convenient identifiers to leverage within DHCP. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: T. Narten, J. Johnson |
| RFC6356 Coupled Congestion Control for Multipath Transport Protocols Often endpoints are connected by multiple paths, but communications are usually restricted to a single path per connection. Resource usage within the network would be more efficient were it possible for these multiple paths to be used concurrently. Multipath TCP is a proposal to achieve multipath transport in TCP. | October 2011 Status: EXPERIMENTAL Autor: C. Raiciu, M. Handley, D. Wischik |
| RFC6357 Design Considerations for Session Initiation Protocol (SIP) Overload Control Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document discusses models and design considerations for a SIP overload control mechanism. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: V. Hilt, E. Noel, C. Shen, A. Abdelal |
| RFC6358 Additional Master Secret Inputs for TLS This document describes a mechanism for using additional master secret inputs with Transport Layer Security (TLS) and Datagram TLS (DTLS). This document defines an Experimental Protocol for the Internet community. | January 2012 Status: EXPERIMENTAL Autor: P. Hoffman |
| RFC6359 Datatracker Extensions to Include IANA and RFC Editor Processing Information This document captures the requirements for integrating IANA and RFC Editor state information into the Datatracker to provide the community with a unified tool to track the status of their document as it progresses from Internet-Draft (I-D) version -00 to RFC. Extending the Datatracker to hold document data from I-D version -00 to RFC allows for increased automation between the Datatracker, IANA, and RFC Editor, thus reducing manual labor, processing errors, and potential delay. Therefore, this document also describes the requirements to make such automation possible. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2011 Status: INFORMATIONAL Autor: S. Ginoza, M. Cotton, A. Morris |
| RFC6360 Conclusion of FYI RFC Sub-Series This document concludes the For Your Information (FYI) sub-series of RFCs, established by RFC 1150 for use by the IETF User Services Area, which no longer exists. The IESG does not intend to make any further additions to this RFC sub-series, and this document provides a record of this decision. This document also obsoletes RFC 1150 and changes the status of RFC 1150 to Historic. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: R. Housley |
| RFC6361 PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multiprotocol traffic over point-to-point links. This document describes PPP support for the Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication between Routing Bridges (RBridges) via PPP links. [STANDARDS-TRACK] | August 2011 Status: PROPOSED STANDARD Autor: J. Carlson, D. Eastlake 3rd |
| RFC6362 Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT) The Electronic Data Interchange - Internet Integration (EDIINT) AS1, AS2, and AS3 messages were designed specifically for the transport of EDI documents. Since multiple interchanges could be placed within a single EDI document, there was not a need for sending multiple EDI documents in a single message. As adoption of EDIINT grew, other uses developed aside from single EDI document transport. Some transactions required multiple attachments to be interpreted together and stored in a single message. This Informational RFC describes how multiple documents, including non-EDI payloads, can be attached and transmitted in a single EDIINT transport message. The attachments are stored within the MIME multipart/related structure. A minimal list of content-types to be supported as attachments is provided. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: K. Meadors |
| RFC6363 Forward Error Correction (FEC) Framework This document describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. This framework can be used to define Content Delivery Protocols that provide FEC for streaming media delivery or other packet flows. Content Delivery Protocols defined using this framework can support any FEC scheme (and associated FEC codes) that is compliant with various requirements defined in this document. Thus, Content Delivery Protocols can be defined that are not specific to a particular FEC scheme, and FEC schemes can be defined that are not specific to a particular Content Delivery Protocol. [STANDARDS-TRACK] | October 2011 Status: PROPOSED STANDARD Autor: M. Watson, A. Begen, V. Roca |
| RFC6364 Session Description Protocol Elements for the Forward Error Correction (FEC) Framework This document specifies the use of the Session Description Protocol (SDP) to describe the parameters required to signal the Forward Error Correction (FEC) Framework Configuration Information between the sender(s) and receiver(s). This document also provides examples that show the semantics for grouping multiple source and repair flows together for the applications that simultaneously use multiple instances of the FEC Framework. [STANDARDS-TRACK] | October 2011 Status: PROPOSED STANDARD Autor: A. Begen |
| RFC6365 Terminology Used in Internationalization in the IETF This document provides a list 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 documents an Internet Best Current Practice. | September 2011 Status: BEST CURRENT PRACTICE Autor: P. Hoffman, J. Klensin |
| RFC6366 Requirements for an Internet Audio Codec This document provides specific requirements for an Internet audio codec. These requirements address quality, sampling rate, bit-rate, and packet-loss robustness, as well as other desirable properties. This document is not an Internet Standards Track specification; it is published for informational purposes. | August 2011 Status: INFORMATIONAL Autor: J. Valin, K. Vos |
| RFC6367 Addition of the Camellia Cipher Suites to Transport Layer Security (TLS) This document specifies forty-two cipher suites for the Transport Security Layer (TLS) protocol to support the Camellia encryption algorithm as a block cipher. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2011 Status: INFORMATIONAL Autor: S. Kanno, M. Kanda |
| RFC6368 Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs) This document defines protocol extensions and procedures for BGP Provider/Customer Edge router iteration in BGP/MPLS IP VPNs. These extensions and procedures have the objective of making the usage of the BGP/MPLS IP VPN transparent to the customer network, as far as routing information is concerned. [STANDARDS-TRACK] | September 2011 Status: PROPOSED STANDARD Autor: P. Marques, R. Raszuk, K. Patel, K. Kumaki, T. Yamagata |
| RFC6369 Forwarding and Control Element Separation (ForCES) Implementation Experience The Forwarding and Control Element Separation (ForCES) protocol defines a standard communication and control mechanism through which a Control Element (CE) can control the behavior of a Forwarding Element (FE). This document captures the experience of implementing the ForCES protocol and model. Its aim is to help others by providing examples and possible strategies for implementing the ForCES protocol. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2011 Status: INFORMATIONAL Autor: E. Haleplidis, O. Koufopavlou, S. Denazis |
| RFC6370 MPLS Transport Profile (MPLS-TP) Identifiers This document specifies an initial set of identifiers to be used in the Transport Profile of Multiprotocol Label Switching (MPLS-TP). The MPLS-TP requirements (RFC 5654) require that the elements and objects in an MPLS-TP environment are able to be configured and managed without a control plane. In such an environment, many conventions for defining identifiers are possible. This document defines identifiers for MPLS-TP management and Operations, Administration, and Maintenance (OAM) functions compatible with IP/ MPLS conventions. | September 2011 Status: PROPOSED STANDARD Autor: M. Bocci, G. Swallow, E. Gray |
| RFC6371 Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks The Transport Profile of Multiprotocol Label Switching (MPLS-TP) is a packet-based transport technology based on the MPLS Traffic Engineering (MPLS-TE) and pseudowire (PW) data-plane architectures. | September 2011 Status: INFORMATIONAL Autor: I. Busi, D. Allan |
| RFC6372 MPLS Transport Profile (MPLS-TP) Survivability Framework Network survivability is the ability of a network to recover traffic delivery following failure or degradation of network resources. Survivability is critical for the delivery of guaranteed network services, such as those subject to strict Service Level Agreements (SLAs) that place maximum bounds on the length of time that services may be degraded or unavailable. | September 2011 Status: INFORMATIONAL Autor: N. Sprecher, A. Farrel |
| RFC6373 MPLS Transport Profile (MPLS-TP) Control Plane Framework The MPLS Transport Profile (MPLS-TP) supports static provisioning of transport paths via a Network Management System (NMS) and dynamic provisioning of transport paths via a control plane. This document provides the framework for MPLS-TP dynamic provisioning and covers control-plane addressing, routing, path computation, signaling, traffic engineering, and path recovery. MPLS-TP uses GMPLS as the control plane for MPLS-TP Label Switched Paths (LSPs). MPLS-TP also uses the pseudowire (PW) control plane for pseudowires. Management-plane functions are out of scope of this document. | September 2011 Status: INFORMATIONAL Autor: L. Andersson, L. Berger, L. Fang, N. Bitar, E. Gray |
| RFC6374 Packet Loss and Delay Measurement for MPLS Networks Many service provider service level agreements (SLAs) depend on the ability to measure and monitor performance metrics for packet loss and one-way and two-way delay, as well as related metrics such as delay variation and channel throughput. This measurement capability also provides operators with greater visibility into the performance characteristics of their networks, thereby facilitating planning, troubleshooting, and network performance evaluation. This document specifies protocol mechanisms to enable the efficient and accurate measurement of these performance metrics in MPLS networks. [STANDARDS-TRACK] | September 2011 Status: PROPOSED STANDARD Autor: D. Frost, S. Bryant |
| RFC6375 A Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks Procedures and protocol mechanisms to enable efficient and accurate measurement of packet loss, delay, and throughput in MPLS networks are defined in RFC 6374. | September 2011 Status: INFORMATIONAL Autor: D. Frost, S. Bryant |
| RFC6376 DomainKeys Identified Mail (DKIM) Signatures DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature. | September 2011 Status: DRAFT STANDARD Autor: D. Crocker, T. Hansen, M. Kucherawy |
| RFC6377 DomainKeys Identified Mail (DKIM) and Mailing Lists DomainKeys Identified Mail (DKIM) allows an ADministrative Management Domain (ADMD) to assume some responsibility for a message. Based on deployment experience with DKIM, this document provides guidance for the use of DKIM with scenarios that include Mailing List Managers (MLMs). This memo documents an Internet Best Current Practice. | September 2011 Status: BEST CURRENT PRACTICE Autor: M. Kucherawy |
| RFC6378 MPLS Transport Profile (MPLS-TP) Linear Protection This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunications Union Telecommunications Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and Pseudowire Emulation Edge-to-Edge (PWE3) architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T. | October 2011 Status: PROPOSED STANDARD Autor: Y. Weingarten, S. Bryant, E. Osborne, N. Sprecher, A. Fulignoli |
| RFC6379 Suite B Cryptographic Suites for IPsec This document proposes four cryptographic user interface suites ("UI suites") for IP Security (IPsec), similar to the two suites specified in RFC 4308. The four new suites provide compatibility with the United States National Security Agency's Suite B specifications. This document obsoletes RFC 4869, which presented earlier versions of these suites. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2011 Status: INFORMATIONAL Autor: L. Law, J. Solinas |
| RFC6380 Suite B Profile for Internet Protocol Security (IPsec) The United States Government has published guidelines for "NSA Suite B Cryptography" dated July, 2005, which defines cryptographic algorithm policy for national security applications. This document specifies the conventions for using Suite B cryptography in IP Security (IPsec). | October 2011 Status: INFORMATIONAL Autor: K. Burgin, M. Peck |
| RFC6381 The 'Codecs' and 'Profiles' Parameters for "Bucket" Media Types Several MIME type/subtype combinations exist that can contain different media formats. A receiving agent thus needs to examine the details of such media content to determine if the specific elements can be rendered given an available set of codecs. Especially when the end system has limited resources, or the connection to the end system has limited bandwidth, it is helpful to know from the Content- Type alone if the content can be rendered. | August 2011 Status: PROPOSED STANDARD Autor: R. Gellens, D. Singer, P. Frojdh |
| RFC6382 Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted Services This document makes recommendations regarding the use of unique origin autonomous system numbers (ASNs) per node for globally anycasted critical infrastructure services in order to provide routing system discriminators for a given anycasted prefix. Network management and monitoring techniques, or other operational mechanisms, may employ this new discriminator in whatever manner best accommodates their operating environment. This memo documents an Internet Best Current Practice. | October 2011 Status: BEST CURRENT PRACTICE Autor: D. McPherson, R. Donnelly, F. Scalzo |
| RFC6383 Advice on When It Is Safe to Start Sending Data on Label Switched Paths Established Using RSVP-TE The Resource Reservation Protocol (RSVP) has been extended to support Traffic Engineering (TE) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. The protocol enables signaling exchanges to establish Label Switched Paths (LSPs) that traverse nodes and link to provide end-to-end data paths. Each node is programmed with "cross-connect" information as the signaling messages are processed. The cross-connection information instructs the node how to forward data that it receives. | September 2011 Status: INFORMATIONAL Autor: K. Shiomoto, A. Farrel |
| RFC6384 An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 Translation The File Transfer Protocol (FTP) has a very long history, and despite the fact that today other options exist to perform file transfers, FTP is still in common use. As such, in situations where some client computers only have IPv6 connectivity while many servers are still IPv4-only and IPv6-to-IPv4 translators are used to bridge that gap, it is important that FTP is made to work through these translators to the best possible extent. | October 2011 Status: PROPOSED STANDARD Autor: I. van Beijnum |
| RFC6385 General Area Review Team (Gen-ART) Experiences The General Area Review Team (Gen-ART) has been doing reviews of Internet-Drafts (I-Ds) since 2004. This document discusses the experience and the lessons learned over the past 7 years of this process. The review team initially reviewed the I-Ds before each of the IESG telechats. Since late 2005, review team members have been assigned to review I-Ds during IETF Last Call, unless no IETF Last Call is necessary for the I-D. The same reviewer then reviews any updates when the I-D is placed on an IESG telechat agenda. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2011 Status: INFORMATIONAL Autor: M. Barnes, A. Doria, H. Alvestrand, B. Carpenter |
| RFC6386 VP8 Data Format and Decoding Guide This document describes the VP8 compressed video data format, together with a discussion of the decoding procedure for the format. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: J. Bankoski, J. Koleszar, L. Quillio, J. Salonen, P. Wilkins, Y. Xu |
| RFC6387 GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs) This document defines a method for the support of GMPLS asymmetric bandwidth bidirectional Label Switched Paths (LSPs). The approach presented is applicable to any switching technology and builds on the original Resource Reservation Protocol (RSVP) model for the transport of traffic-related parameters. This document moves the experiment documented in RFC 5467 to the standards track and obsoletes RFC 5467. [STANDARDS-TRACK] | September 2011 Status: PROPOSED STANDARD Autor: A. Takacs, L. Berger, D. Caviglia, D. Fedyk, J. Meuric |
| RFC6388 Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths This document describes extensions to the Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) Label Switched Paths (LSPs) in MPLS networks. These extensions are also referred to as multipoint LDP. Multipoint LDP constructs the P2MP or MP2MP LSPs without interacting with or relying upon any other multicast tree construction protocol. Protocol elements and procedures for this solution are described for building such LSPs in a receiver-initiated manner. There can be various applications for multipoint LSPs, for example IP multicast or support for multicast in BGP/MPLS Layer 3 Virtual Private Networks (L3VPNs). Specification of how such applications can use an LDP signaled multipoint LSP is outside the scope of this document. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: IJ. Wijnands, I. Minei, K. Kompella, B. Thomas |
| RFC6389 MPLS Upstream Label Assignment for LDP This document describes procedures for distributing upstream-assigned labels for the Label Distribution Protocol (LDP). It also describes how these procedures can be used for avoiding branch Label Switching Router (LSR) traffic replication on a LAN for LDP point-to-multipoint (P2MP) Label Switched Paths (LSPs). [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: R. Aggarwal, JL. Le Roux |
| RFC6390 Guidelines for Considering New Performance Metric Development This document describes a framework and a process for developing Performance Metrics of protocols and applications transported over IETF-specified protocols. These metrics can be used to characterize traffic on live networks and services. This memo documents an Internet Best Current Practice. | October 2011 Status: BEST CURRENT PRACTICE Autor: A. Clark, B. Claise |
| RFC6391 Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network Where the payload of a pseudowire comprises a number of distinct flows, it can be desirable to carry those flows over the Equal Cost Multiple Paths (ECMPs) that exist in the packet switched network. Most forwarding engines are able to generate a hash of the MPLS label stack and use this mechanism to balance MPLS flows over ECMPs. | November 2011 Status: PROPOSED STANDARD Autor: S. Bryant, C. Filsfils, U. Drafz, V. Kompella, J. Regan, S. Amante |
| RFC6392 A Survey of In-Network Storage Systems This document surveys deployed and experimental in-network storage systems and describes their applicability for the DECADE (DECoupled Application Data Enroute) architecture. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2011 Status: INFORMATIONAL Autor: R. Alimi, A. Rahman, Y. Yang |
| RFC6393 Moving RFC 4693 to Historic This document moves RFC 4693 to Historic status. It also obsoletes RFC 4693. This document is not an Internet Standards Track specification; it is published for informational purposes. | September 2011 Status: INFORMATIONAL Autor: M. Yevstifeyev |
| RFC6394 Use Cases and Requirements for DNS-Based Authentication of Named Entities (DANE) Many current applications use the certificate-based authentication features in Transport Layer Security (TLS) to allow clients to verify that a connected server properly represents a desired domain name. Typically, this authentication has been based on PKIX certificate chains rooted in well-known certificate authorities (CAs), but additional information can be provided via the DNS itself. This document describes a set of use cases in which the DNS and DNS Security Extensions (DNSSEC) could be used to make assertions that support the TLS authentication process. The main focus of this document is TLS server authentication, but it also covers TLS client authentication for applications where TLS clients are identified by domain names. [STANDARDS-TRACK] | October 2011 Status: INFORMATIONAL Autor: R. Barnes |
| RFC6395 An Interface Identifier (ID) Hello Option for PIM This document defines a new PIM Hello option to advertise an Interface Identifier that can be used by PIM protocols to uniquely identify an interface of a neighboring router. [STANDARDS-TRACK] | October 2011 Status: PROPOSED STANDARD Autor: S. Gulrajani, S. Venaas |
| RFC6396 Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format This document describes the MRT format for routing information export. This format was developed in concert with the Multi-threaded Routing Toolkit (MRT) from whence the format takes it name. The format can be used to export routing protocol messages, state changes, and routing information base contents. [STANDARDS-TRACK] | October 2011 Status: PROPOSED STANDARD Autor: L. Blunk, M. Karir, C. Labovitz |
| RFC6397 Multi-Threaded Routing Toolkit (MRT) Border Gateway Protocol (BGP) Routing Information Export Format with Geo-Location Extensions This document updates the Multi-threaded Routing Toolkit (MRT) export format for Border Gateway Protocol (BGP) routing information by extending it to include optional terrestrial coordinates of a BGP collector and its BGP peers. [STANDARDS-TRACK] | October 2011 Status: PROPOSED STANDARD Autor: T. Manderson |
| RFC6398 IP Router Alert Considerations and Usage The IP Router Alert Option is an IP option that alerts transit routers to more closely examine the contents of an IP packet. The Resource reSerVation Protocol (RSVP), Pragmatic General Multicast (PGM), the Internet Group Management Protocol (IGMP), Multicast Listener Discovery (MLD), Multicast Router Discovery (MRD), and General Internet Signaling Transport (GIST) are some of the protocols that make use of the IP Router Alert Option. This document discusses security aspects and usage guidelines around the use of the current IP Router Alert Option, thereby updating RFC 2113 and RFC 2711. Specifically, it provides recommendations against using the Router Alert in the end-to-end open Internet and identifies controlled environments where protocols depending on Router Alert can be used safely. It also provides recommendations about protection approaches for service providers. Finally, it provides brief guidelines for Router Alert implementation on routers. This memo documents an Internet Best Current Practice. | October 2011 Status: BEST CURRENT PRACTICE Autor: F. Le Faucheur |
| RFC6401 RSVP Extensions for Admission Priority Some applications require the ability to provide an elevated probability of session establishment to specific sessions in times of network congestion. When supported over the Internet Protocol suite, this may be facilitated through a network-layer admission control solution that supports prioritized access to resources (e.g., bandwidth). These resources may be explicitly set aside for prioritized sessions, or may be shared with other sessions. This document specifies extensions to the Resource reSerVation Protocol (RSVP) that can be used to support such an admission priority capability at the network layer. | October 2011 Status: PROPOSED STANDARD Autor: F. Le Faucheur, J. Polk, K. Carlberg |
| RFC6402 Certificate Management over CMS (CMC) Updates This document contains a set of updates to the base syntax for CMC, a Certificate Management protocol using the Cryptographic Message Syntax (CMS). This document updates RFC 5272, RFC 5273, and RFC 5274. | November 2011 Status: PROPOSED STANDARD Autor: J. Schaad |
| RFC6403 Suite B Profile of Certificate Management over CMS The United States government has published guidelines for "NSA Suite\0B Cryptography", which defines cryptographic algorithm policy for national security applications. This document specifies a profile of the Certificate Management over CMS (CMC) protocol for managing Suite B X.509 public key certificates. This profile is a refinement of RFCs 5272, 5273, and 5274. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: L. Zieglar, S. Turner, M. Peck |
| RFC6404 Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested Countermeasures The Session PEERing for Multimedia INTerconnect (SPEERMINT) working group (WG) provides a peering framework that leverages the building blocks of existing IETF-defined protocols such as SIP and ENUM for the interconnection between SIP Service Providers (SSPs). The objective of this document is to identify and enumerate SPEERMINT- specific threat vectors and to give guidance for implementers on selecting appropriate countermeasures. Security requirements for SPEERMINT that have been derived from the threats detailed in this document can be found in RFC 6271; this document provides concrete countermeasures to meet those SPEERMINT security requirements. In this document, the different security threats related to SPEERMINT are classified into threats to the Lookup Function (LUF), the Location Routing Function (LRF), the Signaling Function (SF), and the Media Function (MF) of a specific SIP Service Provider. Various instances of the threats are briefly introduced inside the classification. Finally, existing security solutions for SIP and RTP/RTCP (Real-time Transport Control Protocol) are presented to describe countermeasures currently available for such threats. Each SSP may have connections to one or more remote SSPs through peering or transit contracts. A potentially compromised remote SSP that attacks other SSPs is out of the scope of this document; this document focuses on attacks on an SSP from outside the trust domain such an SSP may have with other SSPs. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: J. Seedorf, S. Niccolini, E. Chen, H. Scholz |
| RFC6405 Voice over IP (VoIP) SIP Peering Use Cases This document depicts many common Voice over IP (VoIP) use cases for Session Initiation Protocol (SIP) peering. These use cases are categorized into static and on-demand, and then further sub- categorized into direct and indirect. These use cases are not an exhaustive set, but rather the most common use cases deployed today. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: A. Uzelac, Y. Lee |
| RFC6406 Session PEERing for Multimedia INTerconnect (SPEERMINT) Architecture This document defines a peering architecture for the Session Initiation Protocol (SIP) and its functional components and interfaces. It also describes the components and the steps necessary to establish a session between two SIP Service Provider (SSP) peering domains. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: D. Malas, J. Livingood |
| RFC6407 The Group Domain of Interpretation This document describes the Group Domain of Interpretation (GDOI) protocol specified in RFC 3547. The GDOI provides group key management to support secure group communications according to the architecture specified in RFC 4046. The GDOI manages group security associations, which are used by IPsec and potentially other data security protocols. This document replaces RFC 3547. [STANDARDS-TRACK] | October 2011 Status: PROPOSED STANDARD Autor: B. Weis, S. Rowles, T. Hardjono |
| RFC6408 Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage The Diameter base protocol specifies mechanisms whereby a given realm may advertise Diameter nodes and the supported transport protocol. However, these mechanisms do not reveal the Diameter applications that each node supports. A peer outside the realm would have to perform a Diameter capability exchange with every node until it discovers one that supports the required application. This document updates RFC 3588, "Diameter Base Protocol", and describes an improvement using an extended format for the Straightforward-Naming Authority Pointer (S-NAPTR) application service tag that allows for discovery of the supported applications without doing Diameter capability exchange beforehand. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: M. Jones, J. Korhonen, L. Morand |
| RFC6409 Message Submission for Mail This memo splits message submission from message relay, allowing each service to operate according to its own rules (for security, policy, etc.), and specifies what actions are to be taken by a submission server. | November 2011 Status: STANDARD Autor: R. Gellens, J. Klensin |
| RFC6410 Reducing the Standards Track to Two Maturity Levels This document updates the Internet Engineering Task Force (IETF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards Process from three Standards Track maturity levels to two. This memo documents an Internet Best Current Practice. | October 2011 Status: BEST CURRENT PRACTICE Autor: R. Housley, D. Crocker, E. Burger |
| RFC6411 Applicability of Keying Methods for RSVP Security The Resource reSerVation Protocol (RSVP) allows hop-by-hop integrity protection of RSVP neighbors. This requires messages to be cryptographically protected using a shared secret between participating nodes. This document compares group keying for RSVP with per-neighbor or per-interface keying, and discusses the associated key provisioning methods as well as applicability and limitations of these approaches. This document also discusses applicability of encrypting RSVP messages. This document is not an Internet Standards Track specification; it is published for informational purposes. | October 2011 Status: INFORMATIONAL Autor: M. Behringer, F. Le Faucheur, B. Weis |
| RFC6412 Terminology for Benchmarking Link-State IGP Data-Plane Route Convergence This document describes the terminology for benchmarking link-state Interior Gateway Protocol (IGP) route convergence. The terminology is to be used for benchmarking IGP convergence time through externally observable (black-box) data-plane measurements. The terminology can be applied to any link-state IGP, such as IS-IS and OSPF. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: S. Poretsky, B. Imhoff, K. Michielsen |
| RFC6413 Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence This document describes the methodology for benchmarking Link-State Interior Gateway Protocol (IGP) Route Convergence. The methodology is to be used for benchmarking IGP convergence time through externally observable (black-box) data-plane measurements. The methodology can be applied to any link-state IGP, such as IS-IS and OSPF. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: S. Poretsky, B. Imhoff, K. Michielsen |
| RFC6414 Benchmarking Terminology for Protection Performance This document provides common terminology and metrics for benchmarking the performance of sub-IP layer protection mechanisms. The performance benchmarks are measured at the IP layer; protection may be provided at the sub-IP layer. The benchmarks and terminology can be applied in methodology documents for different sub-IP layer protection mechanisms such as Automatic Protection Switching (APS), Virtual Router Redundancy Protocol (VRRP), Stateful High Availability (HA), and Multiprotocol Label Switching Fast Reroute (MPLS-FRR). This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: S. Poretsky, R. Papneja, J. Karthik, S. Vapiwala |
| RFC6415 Web Host Metadata This specification describes a method for locating host metadata as well as information about individual resources controlled by the host. [STANDARDS-TRACK] | October 2011 Status: PROPOSED STANDARD Autor: E. Hammer-Lahav, B. Cook |
| RFC6416 RTP Payload Format for MPEG-4 Audio/Visual Streams 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. This document obsoletes RFC 3016. It contains a summary of changes from RFC 3016 and discusses backward compatibility to RFC 3016. It is a necessary revision of RFC 3016 in order to correct misalignments with the 3GPP Packet- switched Streaming Service (PSS) specification regarding the RTP payload format for MPEG-4 Audio. | October 2011 Status: PROPOSED STANDARD Autor: M. Schmidt, F. de Bont, S. Doehla, J. Kim |
| RFC6417 How to Contribute Research Results to Internet Standardization The development of new technology is driven by scientific research. The Internet, with its roots in the ARPANET and NSFNet, is no exception. Many of the fundamental, long-term improvements to the architecture, security, end-to-end protocols and management of the Internet originate in the related academic research communities. Even shorter-term, more commercially driven extensions are oftentimes derived from academic research. When interoperability is required, the IETF standardizes such new technology. Timely and relevant standardization benefits from continuous input and review from the academic research community. | November 2011 Status: INFORMATIONAL Autor: P. Eardley, L. Eggert, M. Bagnulo, R. Winter |
| RFC6418 Multiple Interfaces and Provisioning Domains Problem Statement This document describes issues encountered by a node attached to multiple provisioning domains. This node receives configuration information from each of its provisioning domains, where some configuration objects are global to the node and others are local to the interface. Issues such as selecting the wrong interface to send traffic happen when conflicting node-scoped configuration objects are received and inappropriately used. Moreover, other issues are the result of simultaneous attachment to multiple networks, such as domain selection or addressing and naming space overlaps, regardless of the provisioning mechanism. While multiple provisioning domains are typically seen on nodes with multiple interfaces, this document also discusses situations involving single-interface nodes. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: M. Blanchet, P. Seite |
| RFC6419 Current Practices for Multiple-Interface Hosts An increasing number of hosts are operating in multiple-interface environments. This document summarizes current practices in this area and describes in detail how some common operating systems cope with challenges that ensue from this context. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: M. Wasserman, P. Seite |
| RFC6420 PIM Multi-Topology ID (MT-ID) Join Attribute This document introduces a new type of PIM Join Attribute that extends PIM signaling to identify a topology that should be used when constructing a particular multicast distribution tree. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: Y. Cai, H. Ou |
| RFC6421 Crypto-Agility Requirements for Remote Authentication Dial-In User Service (RADIUS) This memo describes the requirements for a crypto-agility solution for Remote Authentication Dial-In User Service (RADIUS). This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: D. Nelson |
| RFC6422 Relay-Supplied DHCP Options DHCPv6 relay agents cannot communicate with DHCPv6 clients directly. However, in some cases, the relay agent possesses some information that would be useful to the DHCPv6 client. This document describes a mechanism whereby the DHCPv6 relay agent can provide such information to the DHCPv6 server, which can, in turn, pass this information on to the DHCP client. | December 2011 Status: PROPOSED STANDARD Autor: T. Lemon, Q. Wu |
| RFC6423 Using the Generic Associated Channel Label for Pseudowire in the MPLS Transport Profile (MPLS-TP) This document describes the requirements for using the Generic Associated Channel Label (GAL) in pseudowires (PWs) in MPLS Transport Profile (MPLS-TP) networks, and provides an update to the description of GAL usage in RFC 5586 by removing the restriction that is imposed on using GAL for PWs, especially in MPLS-TP environments. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: H. Li, L. Martini, J. He, F. Huang |
| RFC6424 Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels This document describes methods for performing LSP ping (specified in RFC 4379) traceroute over MPLS tunnels and for traceroute of stitched MPLS Label Switched Paths (LSPs). The techniques outlined in RFC 4379 are insufficient to perform traceroute Forwarding Equivalency Class (FEC) validation and path discovery for an LSP that goes over other MPLS tunnels or for a stitched LSP. This document deprecates the Downstream Mapping TLV (defined in RFC 4379) in favor of a new TLV that, along with other procedures outlined in this document, can be used to trace such LSPs. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: N. Bahadur, K. Kompella, G. Swallow |
| RFC6425 Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP Ping Recent proposals have extended the scope of Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) to encompass point-to-multipoint (P2MP) LSPs. | November 2011 Status: PROPOSED STANDARD Autor: S. Saxena, G. Swallow, Z. Ali, A. Farrel, S. Yasukawa, T. Nadeau |
| RFC6426 MPLS On-Demand Connectivity Verification and Route Tracing Label Switched Path Ping (LSP ping) is an existing and widely deployed Operations, Administration, and Maintenance (OAM) mechanism for Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). This document describes extensions to LSP ping so that LSP ping can be used for on-demand connectivity verification of MPLS Transport Profile (MPLS-TP) LSPs and pseudowires. This document also clarifies procedures to be used for processing the related OAM packets. Further, it describes procedures for using LSP ping to perform connectivity verification and route tracing functions in MPLS-TP networks. Finally, this document updates RFC 4379 by adding a new address type and creating an IANA registry. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: E. Gray, N. Bahadur, S. Boutros, R. Aggarwal |
| RFC6427 MPLS Fault Management Operations, Administration, and Maintenance (OAM) This document specifies Operations, Administration, and Maintenance (OAM) messages to indicate service disruptive conditions for MPLS-based transport network Label Switched Paths. The notification mechanism employs a generic method for a service disruptive condition to be communicated to a Maintenance Entity Group End Point. This document defines an MPLS OAM channel, along with messages to communicate various types of service disruptive conditions. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: G. Swallow, A. Fulignoli, M. Vigoureux, S. Boutros, D. Ward |
| RFC6428 Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport Profile Continuity Check, Proactive Connectivity Verification, and Remote Defect Indication functionalities are required for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM). | November 2011 Status: PROPOSED STANDARD Autor: D. Allan, G. Swallow Ed., J. Drake Ed. |
| RFC6429 TCP Sender Clarification for Persist Condition This document clarifies the Zero Window Probes (ZWPs) described in RFC 1122 ("Requirements for Internet Hosts -- Communication Layers"). In particular, it clarifies the actions that can be taken on connections that are experiencing the ZWP condition. Rather than making a change to the standard, this document clarifies what has been until now a misinterpretation of the standard as specified in RFC 1122. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2011 Status: INFORMATIONAL Autor: M. Bashyam, M. Jethanandani, A. Ramaiah |
| RFC6430 Email Feedback Report Type Value: not-spam This document defines a new Abuse Reporting Format (ARF) feedback report type value: "not-spam". It can be used to report an email message that was mistakenly marked as spam. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: K. Li, B. Leiba |
| RFC6431 Huawei Port Range Configuration Options for PPP IP Control Protocol (IPCP) This document defines two Huawei IPCP (IP Control Protocol) options used to convey a set of ports. These options can be used in the context of port range-based solutions or NAT-based solutions for port delegation and forwarding purposes. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: M. Boucadair, P. Levis, G. Bajko, T. Savolainen, T. Tsou |
| RFC6432 Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses Although the use of the SIP (Session Initiation Protocol) Reason header field in responses is considered in general in RFC 3326, its use is not specified for any particular response code. Nonetheless, existing deployments have been using Reason header fields to carry failure-related Q.850 cause codes in SIP responses to INVITE requests that have been gatewayed to Public Switched Telephone Network (PSTN) systems. This document normatively describes the use of the Reason header field in carrying Q.850 cause codes in SIP responses. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: R. Jesske, L. Liess |
| RFC6433 Requirements for a Working Group Milestones Tool The IETF intends to provide a new tool to Working Group chairs and Area Directors for the creation and updating of milestones for Working Group charters. This document describes the requirements for the proposed new tool, and it is intended as input to a later activity for the design and development of such a tool. This document updates RFC 6292. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: P. Hoffman |
| RFC6434 IPv6 Node Requirements This document defines requirements for IPv6 nodes. It is expected that IPv6 will be deployed in a wide range of devices and situations. Specifying the requirements for IPv6 nodes allows IPv6 to function well and interoperate in a large number of situations and deployments. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2011 Status: INFORMATIONAL Autor: E. Jankiewicz, J. Loughney, T. Narten |
| RFC6435 MPLS Transport Profile Lock Instruct and Loopback Functions Two useful Operations, Administration, and Maintenance (OAM) functions in a transport network are "lock" and "loopback". The lock function enables an operator to lock a transport path such that it does not carry client traffic, but can continue to carry OAM messages and may carry test traffic. The loopback function allows an operator to set a specific node on the transport path into loopback mode such that it returns all received data. | November 2011 Status: PROPOSED STANDARD Autor: S. Boutros, S. Sivabalan, R. Aggarwal, M. Vigoureux, X. Dai |
| RFC6436 Rationale for Update to the IPv6 Flow Label Specification Various published proposals for use of the IPv6 flow label are incompatible with its original specification in RFC 3697. Furthermore, very little practical use is made of the flow label, partly due to some uncertainties about the correct interpretation of the specification. This document discusses and motivates changes to the specification in order to clarify it and to introduce some additional flexibility. This document is not an Internet Standards Track specification; it is published for informational purposes. | November 2011 Status: INFORMATIONAL Autor: S. Amante, B. Carpenter, S. Jiang |
| RFC6437 IPv6 Flow Label Specification This document specifies the IPv6 Flow Label field and the minimum requirements for IPv6 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 the scope for this document. | November 2011 Status: PROPOSED STANDARD Autor: S. Amante, B. Carpenter, S. Jiang, J. Rajahalme |
| RFC6438 Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels The IPv6 flow label has certain restrictions on its use. This document describes how those restrictions apply when using the flow label for load balancing by equal cost multipath routing and for link aggregation, particularly for IP-in-IPv6 tunneled traffic. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: B. Carpenter, S. Amante |
| RFC6439 Routing Bridges (RBridges): Appointed Forwarders The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides least cost pair-wise data forwarding without configuration in multi-hop networks with arbitrary topology, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using IS-IS (Intermediate System to Intermediate System) link state routing and by encapsulating traffic using a header that includes a hop count. Devices that implement TRILL are called "RBridges" (Routing Bridges). | November 2011 Status: PROPOSED STANDARD Autor: R. Perlman, D. Eastlake, Y. Li, A. Banerjee, F. Hu |
| RFC6440 The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option In order to derive a Domain-Specific Root Key (DSRK) from the Extended Master Session Key (EMSK) generated as a side effect of an Extensible Authentication Protocol (EAP) method, the EAP peer must discover the name of the domain to which it is attached. | December 2011 Status: PROPOSED STANDARD Autor: G. Zorn, Q. Wu, Y. Wang |
| RFC6441 Time to Remove Filters for Previously Unallocated IPv4 /8s It has been common for network administrators to filter IP traffic from and BGP prefixes of unallocated IPv4 address space. Now that there are no longer any unallocated IPv4 /8s, this practise is more complicated, fragile, and expensive. Network administrators are advised to remove filters based on the registration status of the address space. | November 2011 Status: BEST CURRENT PRACTICE Autor: L. Vegoda |
| RFC6442 Location Conveyance for the Session Initiation Protocol This document defines an extension to the Session Initiation Protocol (SIP) to convey geographic location information from one SIP entity to another SIP entity. The SIP extension covers end-to-end conveyance as well as location-based routing, where SIP intermediaries make routing decisions based upon the location of the Location Target. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: J. Polk, B. Rosen, J. Peterson |
| RFC6443 Framework for Emergency Calling Using Internet Multimedia The IETF has standardized various aspects of placing emergency calls. This document describes how all of those component parts are used to support emergency calls from citizens and visitors to authorities. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2011 Status: INFORMATIONAL Autor: B. Rosen, H. Schulzrinne, J. Polk, A. Newton |
| RFC6444 Location Hiding: Problem Statement and Requirements The emergency services architecture developed in the IETF Emergency Context Resolution with Internet Technology (ECRIT) working group describes an architecture where location information is provided by access networks to endpoints or Voice over IP (VoIP) service providers in order to determine the correct dial string and information to route the call to a Public Safety Answering Point (PSAP). To determine the PSAP Uniform Resource Identifier (URI), the usage of the Location-to-Service Translation (LoST) protocol is envisioned. | January 2012 Status: INFORMATIONAL Autor: H. Schulzrinne, L. Liess, H. Tschofenig, B. Stark, A. Kuett |
| RFC6445 Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute This memo defines a portion of the Management Information Base for use with network management protocols in the Internet community. In particular, it describes managed objects used to support two fast reroute (FRR) methods for Multiprotocol Label Switching (MPLS)-based traffic engineering (TE). The two methods are the one-to-one backup method and the facility backup method. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: T. Nadeau, A. Koushik, R. Cetin |
| RFC6446 Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control This document specifies mechanisms for adjusting the rate of Session Initiation Protocol (SIP) event notifications. These mechanisms can be applied in subscriptions to all SIP event packages. This document updates RFC 3265. [STANDARDS-TRACK] | January 2012 Status: PROPOSED STANDARD Autor: A. Niemi, K. Kiss, S. Loreto |
| RFC6447 Filtering Location Notifications in the Session Initiation Protocol (SIP) This document describes filters that limit asynchronous location notifications to compelling events. These filters are designed as an extension to RFC 4661, an XML-based format for event notification filtering, and based on RFC 3856, the SIP presence event package. The resulting location information is conveyed in existing location formats wrapped in the Presence Information Data Format Location Object (PIDF-LO). [STANDARDS-TRACK] | January 2012 Status: PROPOSED STANDARD Autor: R. Mahy, B. Rosen, H. Tschofenig |
| RFC6448 The Unencrypted Form of Kerberos 5 KRB-CRED Message The Kerberos 5 KRB-CRED message is used to transfer Kerberos credentials between applications. When used with a secure transport, the unencrypted form of the KRB-CRED message may be desirable. This document describes the unencrypted form of the KRB-CRED message. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: R. Yount |
| RFC6449 Complaint Feedback Loop Operational Recommendations Complaint Feedback Loops similar to those described herein have existed for more than a decade, resulting in many de facto standards and best practices. This document is an attempt to codify, and thus clarify, the ways that both providers and consumers of these feedback mechanisms intend to use the feedback, describing some already common industry practices. | November 2011 Status: INFORMATIONAL Autor: J. Falk |
| RFC6450 Multicast Ping Protocol The Multicast Ping Protocol specified in this document allows for checking whether an endpoint can receive multicast -- both Source-Specific Multicast (SSM) and Any-Source Multicast (ASM). It can also be used to obtain additional multicast-related information, such as multicast tree setup time. This protocol is based on an implementation of tools called "ssmping" and "asmping". [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: S. Venaas |
| RFC6451 Location-to-Service Translation (LoST) Protocol Extensions An important class of location-based services answers the question, "What instances of this service are closest to me?" Examples include finding restaurants, gas stations, stores, automated teller machines, wireless access points (hot spots), or parking spaces. Currently, the Location-to-Service Translation (LoST) protocol only supports mapping locations to a single service based on service regions. This document describes an extension that allows queries of the type "N nearest", "within distance X", and "served by". This document defines an Experimental Protocol for the Internet community. | December 2011 Status: EXPERIMENTAL Autor: A. Forte, H. Schulzrinne |
| RFC6452 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) - Unicode 6.0 This memo documents IETF consensus for Internationalized Domain Names for Applications (IDNA) derived character properties related to the three code points, existing in Unicode 5.2, that changed property values when version 6.0 was released. The consensus is that no update is needed to RFC 5892 based on the changes made in Unicode 6.0. [STANDARDS-TRACK] | November 2011 Status: PROPOSED STANDARD Autor: P. Faltstrom, P. Hoffman |
| RFC6453 A URN Namespace for the Open Grid Forum (OGF) This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Grid Forum (OGF) for naming persistent resources. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2011 Status: INFORMATIONAL Autor: F. Dijkstra, R. Hughes-Jones |
| RFC6454 The Web Origin Concept This document defines the concept of an "origin", which is often used as the scope of authority or privilege by user agents. Typically, user agents isolate content retrieved from different origins to prevent malicious web site operators from interfering with the operation of benign web sites. In addition to outlining the principles that underlie the concept of origin, this document details how to determine the origin of a URI and how to serialize an origin into a string. It also defines an HTTP header field, named "Origin", that indicates which origins are associated with an HTTP request. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: A. Barth |
| RFC6455 The WebSocket Protocol The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling). [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: I. Fette, A. Melnikov |
| RFC6456 Multi-Segment Pseudowires in Passive Optical Networks This document describes the application of MPLS multi-segment pseudowires (MS-PWs) in a dual-technology environment comprising a Passive Optical Network (PON) and an MPLS Packet Switched Network (PSN). | November 2011 Status: INFORMATIONAL Autor: H. Li, R. Zheng, A. Farrel |
| RFC6457 PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering The Path Computation Element (PCE) provides functions of path computation in support of traffic engineering in networks controlled by Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS). | December 2011 Status: INFORMATIONAL Autor: T. Takeda, A. Farrel |
| RFC6458 Sockets API Extensions for the Stream Control Transmission Protocol (SCTP) This document describes a mapping of the Stream Control Transmission Protocol (SCTP) into a sockets API. The benefits of this mapping include compatibility for TCP applications, access to new SCTP features, and a consolidated error and event notification scheme. This document is not an Internet Standards Track specification; it is published for informational purposes. | December 2011 Status: INFORMATIONAL Autor: R. Stewart, M. Tuexen, K. Poon, P. Lei, V. Yasevich |
| RFC6459 IPv6 in 3rd Generation Partnership Project (3GPP) Evolved Packet System (EPS) The use of cellular broadband for accessing the Internet and other data services via smartphones, tablets, and notebook/netbook computers has increased rapidly as a result of high-speed packet data networks such as HSPA, HSPA+, and now Long-Term Evolution (LTE) being deployed. Operators that have deployed networks based on 3rd Generation Partnership Project (3GPP) network architectures are facing IPv4 address shortages at the Internet registries and are feeling pressure to migrate to IPv6. This document describes the support for IPv6 in 3GPP network architectures. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2012 Status: INFORMATIONAL Autor: J. Korhonen, J. Soininen, B. Patil, T. Savolainen, G. Bajko, K. Iisakkila |
| RFC6460 Suite B Profile for Transport Layer Security (TLS) The United States government has published guidelines for "NSA Suite B Cryptography" that define cryptographic algorithm policy for national security applications. This document defines a profile of Transport Layer Security (TLS) version 1.2 that is fully compliant with Suite B. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2012 Status: INFORMATIONAL Autor: M. Salter, R. Housley |
| RFC6461 Data for Reachability of Inter-/Intra-NetworK SIP (DRINKS) Use Cases and Protocol Requirements This document captures the use cases and associated requirements for interfaces that provision session establishment data into Session Initiation Protocol (SIP) Service Provider components to assist with session routing. Specifically, this document focuses on the provisioning of one such element termed the "registry". This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2012 Status: INFORMATIONAL Autor: S. Channabasappa |
| RFC6462 Report from the Internet Privacy Workshop On December 8-9, 2010, the IAB co-hosted an Internet privacy workshop with the World Wide Web Consortium (W3C), the Internet Society (ISOC), and MIT's Computer Science and Artificial Intelligence Laboratory (CSAIL). The workshop revealed some of the fundamental challenges in designing, deploying, and analyzing privacy-protective Internet protocols and systems. Although workshop participants and the community as a whole are still far from understanding how best to systematically address privacy within Internet standards development, workshop participants identified a number of potential next steps. For the IETF, these included the creation of a privacy directorate to review Internet-Drafts, further work on documenting privacy considerations for protocol developers, and a number of exploratory efforts concerning fingerprinting and anonymized routing. Potential action items for the W3C included investigating the formation of a privacy interest group and formulating guidance about fingerprinting, referrer headers, data minimization in APIs, usability, and general considerations for non-browser-based protocols. | January 2012 Status: INFORMATIONAL Autor: A. Cooper |
| RFC6463 Runtime Local Mobility Anchor (LMA) Assignment Support for Proxy Mobile IPv6 This document describes a runtime local mobility anchor assignment functionality and corresponding mobility options for Proxy Mobile IPv6. The runtime local mobility anchor assignment takes place during a Proxy Binding Update and a Proxy Binding Acknowledgement message exchange between a mobile access gateway and a local mobility anchor. The runtime local mobility anchor assignment functionality defined in this specification can be used, for example, for load- balancing purposes. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: J. Korhonen, S. Gundavelli, H. Yokota, X. Cui |
| RFC6464 A Real-time Transport Protocol (RTP) Header Extension for Client-to-Mixer Audio Level Indication This document defines a mechanism by which packets of Real-time Transport Protocol (RTP) audio streams can indicate, in an RTP header extension, the audio level of the audio sample carried in the RTP packet. In large conferences, this can reduce the load on an audio mixer or other middlebox that wants to forward only a few of the loudest audio streams, without requiring it to decode and measure every stream that is received. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: J. Lennox, E. Ivov, E. Marocco |
| RFC6465 A Real-time Transport Protocol (RTP) Header Extension for Mixer-to-Client Audio Level Indication This document describes a mechanism for RTP-level mixers in audio conferences to deliver information about the audio level of individual participants. Such audio level indicators are transported in the same RTP packets as the audio data they pertain to. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: E. Ivov, E. Marocco, J. Lennox |
| RFC6466 IANA Registration of the 'image' Media Type for the Session Description Protocol (SDP) This document describes the usage of the 'image' media type and registers it with IANA as a top-level media type for the Session Description Protocol (SDP). This media type is primarily used by SDP to negotiate and establish T.38 media streams. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: G. Salgueiro |
| RFC6467 Secure Password Framework for Internet Key Exchange Version 2 (IKEv2) This document defines a generic way for Internet Key Exchange version 2 (IKEv2) to use any of the symmetric secure password authentication methods. Multiple methods are already specified in other documents, and this document does not add any new one. This document specifies a way to agree on which method is to be used in the current connection. This document also provides a common way to transmit, between peers, payloads that are specific to secure password authentication methods. | December 2011 Status: INFORMATIONAL Autor: T. Kivinen |
| RFC6468 Sieve Notification Mechanism: SIP MESSAGE This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over SIP MESSAGE. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: A. Melnikov, B. Leiba, K. Li |
| RFC6469 RTP Payload Format for DV (IEC 61834) Video 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). This document obsoletes RFC 3189. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: K. Kobayashi, K. Mishima, S. Casner, C. Bormann |
| RFC6470 Network Configuration Protocol (NETCONF) Base Notifications The Network Configuration Protocol (NETCONF) provides mechanisms to manipulate configuration datastores. However, client applications often need to be aware of common events, such as a change in NETCONF server capabilities, that may impact management applications. Standard mechanisms are needed to support the monitoring of the base system events within the NETCONF server. This document defines a YANG module that allows a NETCONF client to receive notifications for some common system events. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: A. Bierman |
| RFC6471 Overview of Best Email DNS-Based List (DNSBL) Operational Practices The rise of spam and other anti-social behavior on the Internet has led to the creation of shared DNS-based lists (DNSBLs) of IP addresses or domain names intended to help guide email filtering. This memo summarizes guidelines of accepted best practice for the management of public DNSBLs by their operators as well as for the proper use of such lists by mail server administrators (DNSBL users), and it provides useful background for both parties. It is not intended to advise on the utility or efficacy of particular DNSBLs or the DNSBL concept in general, nor to assist end users with questions about spam. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2012 Status: INFORMATIONAL Autor: C. Lewis, M. Sergeant |
| RFC6472 Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP This document recommends against the use of the AS_SET and AS_CONFED_SET types of the AS_PATH in BGPv4. This is done to simplify the design and implementation of BGP and to make the semantics of the originator of a route more clear. This will also simplify the design, implementation, and deployment of ongoing work in the Secure Inter-Domain Routing Working Group. This memo documents an Internet Best Current Practice. | December 2011 Status: BEST CURRENT PRACTICE Autor: W. Kumari, K. Sriram |
| RFC6473 vCard KIND:application This document defines a value of "application" for the vCard KIND property so that vCards can be used to represent software applications. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: P. Saint-Andre |
| RFC6474 vCard Format Extensions: Place of Birth, Place and Date of Death The base vCard 4.0 specification defines a large number of properties, including date of birth. This specification adds three new properties to vCard 4.0: place of birth, place of death, and date of death. [STANDARDS-TRACK] | December 2011 Status: PROPOSED STANDARD Autor: K. Li, B. Leiba |
| RFC6476 Using Message Authentication Code (MAC) Encryption in the Cryptographic Message Syntax (CMS) This document specifies the conventions for using Message Authentication Code (MAC) encryption with the Cryptographic Message Syntax (CMS) authenticated-enveloped-data content type. This mirrors the use of a MAC combined with an encryption algorithm that's already employed in IPsec, Secure Socket Layer / Transport Layer Security (SSL/TLS) and Secure SHell (SSH), which is widely supported in existing crypto libraries and hardware and has been extensively analysed by the crypto community. [STANDARDS-TRACK] | January 2012 Status: PROPOSED STANDARD Autor: P. Gutmann |
| RFC6477 Registration of Military Message Handling System (MMHS) Header Fields for Use in Internet Mail A Military Message Handling System (MMHS) processes formal messages ensuring release, distribution, security, and timely delivery across national and international strategic and tactical networks. The MMHS Elements of Service are defined as a set of extensions to the ITU-T X.400 (1992) international standards and are specified in STANAG 4406 Edition 2 and ACP 123. This document specifies message header fields and associated processing for RFC 5322 (Internet Message Format) to provide a comparable messaging service. In addition, this document provides for a STANAG 4406 / Internet Email Gateway that supports message conversion. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2012 Status: INFORMATIONAL Autor: A. Melnikov, G. Lunt |
| RFC6479 IPsec Anti-Replay Algorithm without Bit Shifting This document presents an alternate method to do the anti-replay checks and updates for IP Authentication Header (AH) and Encapsulating Security Protocol (ESP). The method defined in this document obviates the need for bit shifting and it reduces the number of times an anti-replay window is adjusted. This document is not an Internet Standards Track specification; it is published for informational purposes. | January 2012 Status: INFORMATIONAL Autor: X. Zhang, T. Tsou |
| RFC6480 An Infrastructure to Support Secure Internet Routing This document describes an architecture for an infrastructure to support improved security of Internet routing. The foundation of this architecture is a Resource Public Key Infrastructure (RPKI) that represents the allocation hierarchy of IP address space and Autonomous System (AS) numbers; and a distributed repository system for storing and disseminating the data objects that comprise the RPKI, as well as other signed objects necessary for improved routing security. As an initial application of this architecture, the document describes how a legitimate holder of IP address space can explicitly and verifiably authorize one or more ASes to originate routes to that address space. Such verifiable authorizations could be used, for example, to more securely construct BGP route filters. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: M. Lepinski, S. Kent |
| RFC6481 A Profile for Resource Certificate Repository Structure This document defines a profile for the structure of the Resource Public Key Infrastructure (RPKI) distributed repository. Each individual repository publication point is a directory that contains files that correspond to X.509/PKIX Resource Certificates, Certificate Revocation Lists and signed objects. This profile defines the object (file) naming scheme, the contents of repository publication points (directories), and a suggested internal structure of a local repository cache that is intended to facilitate synchronization across a distributed collection of repository publication points and to facilitate certification path construction. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: G. Huston, R. Loomans, G. Michaelson |
| RFC6482 A Profile for Route Origin Authorizations (ROAs) This document defines a standard profile for Route Origin Authorizations (ROAs). A ROA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate routes to one or more prefixes within the address block. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: M. Lepinski, S. Kent, D. Kong |
| RFC6483 Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs) This document defines the semantics of a Route Origin Authorization (ROA) in terms of the context of an application of the Resource Public Key Infrastructure to validate the origination of routes advertised in the Border Gateway Protocol. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: G. Huston, G. Michaelson |
| RFC6484 Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI) This document describes the certificate policy for a Public Key Infrastructure (PKI) used to support attestations about Internet Number Resource (INR) holdings. Each organization that distributes IP addresses or Autonomous System (AS) numbers to an organization will, in parallel, issue a (public key) certificate reflecting this distribution. These certificates will enable verification that the resources indicated in the certificate have been distributed to the holder of the associated private key and that this organization is the current, unique holder of these resources. This memo documents an Internet Best Current Practice. | February 2012 Status: BEST CURRENT PRACTICE Autor: S. Kent, D. Kong, K. Seo, R. Watro |
| RFC6485 The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure (RPKI) This document specifies the algorithms, algorithms' parameters, asymmetric key formats, asymmetric key size, and signature format for the Resource Public Key Infrastructure (RPKI) subscribers that generate digital signatures on certificates, Certificate Revocation Lists, and signed objects as well as for the relying parties (RPs) that verify these digital signatures. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: G. Huston |
| RFC6486 Manifests for the Resource Public Key Infrastructure (RPKI) This document defines a "manifest" for use in the Resource Public Key Infrastructure (RPKI). A manifest is a signed object (file) that contains a listing of all the signed objects (files) in the repository publication point (directory) associated with an authority responsible for publishing in the repository. For each certificate, Certificate Revocation List (CRL), or other type of signed objects issued by the authority that are published at this repository publication point, the manifest contains both the name of the file containing the object and a hash of the file content. Manifests are intended to enable a relying party (RP) to detect certain forms of attacks against a repository. Specifically, if an RP checks a manifest's contents against the signed objects retrieved from a repository publication point, then the RP can detect "stale" (valid) data and deletion of signed objects. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Austein, G. Huston, S. Kent, M. Lepinski |
| RFC6487 A Profile for X.509 PKIX Resource Certificates This document defines a standard profile for X.509 certificates for the purpose of supporting validation of assertions of "right-of-use" of Internet Number Resources (INRs). The certificates issued under this profile are used to convey the issuer's authorization of the subject to be regarded as the current holder of a "right-of-use" of the INRs that are described in the certificate. This document contains the normative specification of Certificate and Certificate Revocation List (CRL) syntax in the Resource Public Key Infrastructure (RPKI). This document also specifies profiles for the format of certificate requests and specifies the Relying Party RPKI certificate path validation procedure. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: G. Huston, G. Michaelson, R. Loomans |
| RFC6488 Signed Object Template for the Resource Public Key Infrastructure (RPKI) This document defines a generic profile for signed objects used in the Resource Public Key Infrastructure (RPKI). These RPKI signed objects make use of Cryptographic Message Syntax (CMS) as a standard encapsulation format. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: M. Lepinski, A. Chi, S. Kent |
| RFC6489 Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI) This document describes how a Certification Authority (CA) in the Resource Public Key Infrastructure (RPKI) performs a planned rollover of its key pair. This document also notes the implications of this key rollover procedure for relying parties (RPs). In general, RPs are expected to maintain a local cache of the objects that have been published in the RPKI repository, and thus the way in which a CA performs key rollover impacts RPs. This memo documents an Internet Best Current Practice. | February 2012 Status: BEST CURRENT PRACTICE Autor: G. Huston, G. Michaelson, S. Kent |
| RFC6490 Resource Public Key Infrastructure (RPKI) Trust Anchor Locator This document defines a Trust Anchor Locator (TAL) for the Resource Public Key Infrastructure (RPKI). [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: G. Huston, S. Weiler, G. Michaelson, S. Kent |
| RFC6491 Resource Public Key Infrastructure (RPKI) Objects Issued by IANA This document provides specific direction to IANA as to the Resource Public Key Infrastructure (RPKI) objects it should issue. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: T. Manderson, L. Vegoda, S. Kent |
| RFC6492 A Protocol for Provisioning Resource Certificates This document defines a framework for certificate management interactions between an Internet Number Resource issuer ("issuer") and an Internet Number Resource recipient ("subject") through the specification of a protocol for interaction between the two parties. The protocol supports the transmission of requests from the subject, and corresponding responses from the issuer encompassing the actions of certificate issuance, certificate revocation, and certificate status information reports. This protocol is intended to be limited to the application of Internet Number Resource Certificate management and is not intended to be used as part of a more general certificate management framework. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: G. Huston, R. Loomans, B. Ellacott, R. Austein |
| RFC6493 The Resource Public Key Infrastructure (RPKI) Ghostbusters Record In the Resource Public Key Infrastructure (RPKI), resource certificates completely obscure names or any other information that might be useful for contacting responsible parties to deal with issues of certificate expiration, maintenance, roll-overs, compromises, etc. This document describes the RPKI Ghostbusters Record containing human contact information that may be verified (indirectly) by a Certification Authority (CA) certificate. The data in the record are those of a severely profiled vCard. [STANDARDS- TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Bush |
| RFC6494 Certificate Profile and Certificate Management for SEcure Neighbor Discovery (SEND) SEcure Neighbor Discovery (SEND) utilizes X.509v3 certificates for performing router authorization. This document specifies a certificate profile for SEND based on resource certificates along with extended key usage values required for SEND. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Gagliano, S. Krishnan, A. Kukec |
| RFC6495 Subject Key Identifier (SKI) SEcure Neighbor Discovery (SEND) Name Type Fields SEcure Neighbor Discovery (SEND) defines the Name Type field in the ICMPv6 Trust Anchor option. This document specifies new Name Type fields based on certificate Subject Key Identifiers (SKIs). [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Gagliano, S. Krishnan, A. Kukec |
| RFC6496 Secure Proxy ND Support for SEcure Neighbor Discovery (SEND) SEcure Neighbor Discovery (SEND) specifies a method for securing Neighbor Discovery (ND) signaling against specific threats. As defined today, SEND assumes that the node sending an ND message is the owner of the address from which the message is sent and/or possesses a key that authorizes the node to act as a router, so that it is in possession of the private key or keys used to generate the digital signature on each message. This means that the Proxy ND signaling performed by nodes that do not possess knowledge of the address owner's private key and/or knowledge of a router's key cannot be secured using SEND. This document extends the current SEND specification in order to secure Proxy ND operation. This document defines an Experimental Protocol for the Internet community. | February 2012 Status: EXPERIMENTAL Autor: S. Krishnan, J. Laganier, M. Bonola, A. Garcia-Martinez |
| RFC6497 BCP 47 Extension T - Transformed Content This document specifies an Extension to BCP 47 that provides subtags for specifying the source language or script of transformed content, including content that has been transliterated, transcribed, or translated, or in some other way influenced by the source. It also provides for additional information used for identification. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: M. Davis, A. Phillips, Y. Umaoka, C. Falk |
| RFC6498 Media Gateway Control Protocol (MGCP) Voiceband Data (VBD) Package and General-Purpose Media Descriptor Parameter Package This document defines Media Gateway Control Protocol (MGCP) packages that enable a Call Agent to authorize and monitor the transition of a connection to and from Voiceband Data (VBD) with or without redundancy and FEC (forward error correction). Although the focus is on VBD, the General-Purpose Media Descriptor Parameter package can be used to authorize other modes of operation, not relevant to VBD, for a particular codec. In addition to defining these new packages, this document describes the use of the Media Format Parameter package and Fax package with VBD, redundancy, and FEC. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: J. Stone, R. Kumar, F. Andreasen |
| RFC6501 Conference Information Data Model for Centralized Conferencing (XCON) RFC 5239 defines centralized conferencing (XCON) as an association of participants with a central focus. The state of a conference is represented by a conference object. This document defines an XML- based conference information data model to be used for conference objects. A conference information data model is designed to convey information about the conference and about participation in the conference. The conference information data model defined in this document constitutes an extension of the data format specified in the Session Initiation Protocol (SIP) event package for conference State. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: O. Novo, G. Camarillo, D. Morgan, J. Urpalainen |
| RFC6502 Conference Event Package Data Format Extension for Centralized Conferencing (XCON) This document specifies the notification mechanism for XCON (centralized conferencing). This mechanism reuses the SIP (Session Initiation Protocol) event package for conference state. Additionally, the notification mechanism includes support for the XCON data model and for partial notifications. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: G. Camarillo, S. Srinivasan, R. Even, J. Urpalainen |
| RFC6503 Centralized Conferencing Manipulation Protocol The Centralized Conferencing Manipulation Protocol (CCMP) allows a Centralized Conferencing (XCON) system client to create, retrieve, change, and delete objects that describe a centralized conference. CCMP is a means to control basic and advanced conference features such as conference state and capabilities, participants, relative roles, and details. CCMP is a stateless, XML-based, client server protocol that carries, in its request and response messages, conference information in the form of XML documents and fragments conforming to the centralized conferencing data model schema. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: M. Barnes, C. Boulton, S. Romano, H. Schulzrinne |
| RFC6504 Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples This document provides detailed call flows for the scenarios documented in the Framework for Centralized Conferencing (XCON) (RFC 5239) and in the XCON scenarios (RFC 4597). The call flows document the use of the interface between a conference control client and a conference control server using the Centralized Conferencing Manipulation Protocol (CCMP) (RFC 6503). The objective is to provide detailed examples for reference by both protocol researchers and developers. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2012 Status: INFORMATIONAL Autor: M. Barnes, L. Miniero, R. Presta, S P. Romano |
| RFC6505 A Mixer Control Package for the Media Control Channel Framework This document defines a Media Control Channel Framework Package for managing mixers for media conferences and connections. The package defines request elements for managing conference mixers, managing mixers between conferences and/or connections, as well as associated responses and notifications. The package also defines elements for auditing package capabilities and mixers [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: S. McGlashan, T. Melanchuk, C. Boulton |
| RFC6506 Supporting Authentication Trailer for OSPFv3 Currently, OSPF for IPv6 (OSPFv3) uses IPsec as the only mechanism for authenticating protocol packets. This behavior is different from authentication mechanisms present in other routing protocols (OSPFv2, Intermediate System to Intermediate System (IS-IS), RIP, and Routing Information Protocol Next Generation (RIPng)). In some environments, it has been found that IPsec is difficult to configure and maintain and thus cannot be used. This document defines an alternative mechanism to authenticate OSPFv3 protocol packets so that OSPFv3 does not only depend upon IPsec for authentication. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: M. Bhatia, V. Manral, A. Lindem |
| RFC6507 Elliptic Curve-Based Certificateless Signatures for Identity-Based Encryption (ECCSI) Many signature schemes currently in use rely on certificates for authentication of identity. In Identity-based cryptography, this adds unnecessary overhead and administration. The Elliptic Curve-based Certificateless Signatures for Identity-based Encryption (ECCSI) signature scheme described in this document is certificateless. This scheme has the additional advantages of low bandwidth and low computational requirements. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: M. Groves |
| RFC6508 Sakai-Kasahara Key Encryption (SAKKE) In this document, the Sakai-Kasahara Key Encryption (SAKKE) algorithm is described. This uses Identity-Based Encryption to exchange a shared secret from a Sender to a Receiver. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: M. Groves |
| RFC6509 MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing (MIKEY) This document describes the Multimedia Internet KEYing-Sakai-Kasahara Key Encryption (MIKEY-SAKKE), a method of key exchange that uses Identity-based Public Key Cryptography (IDPKC) to establish a shared secret value and certificateless signatures to provide source authentication. MIKEY-SAKKE has a number of desirable features, including simplex transmission, scalability, low-latency call setup, and support for secure deferred delivery. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: M. Groves |
| RFC6510 Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) established using the Resource Reservation Protocol Traffic Engineering (RSVP-TE) extensions may be signaled with a set of LSP-specific attributes. These attributes may be carried in both Path and Resv messages. This document specifies how LSP attributes are to be carried in RSVP Path and Resv messages using the Routing Backus-Naur Form and clarifies related Resv message formats. This document updates RFC 4875 and RFC 5420. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: L. Berger, G. Swallow |
| RFC6511 Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths There are many deployment scenarios that require an egress Label Switching Router (LSR) to receive binding of the Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Label Switched Path (LSP) to an application and a payload identifier using some "out-of-band" (OOB) mechanism. This document defines protocol mechanisms to address this requirement. The procedures described in this document are equally applicable for point-to-point (P2P) and point-to-multipoint (P2MP) LSPs. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: Z. Ali, G. Swallow, R. Aggarwal |
| RFC6512 Using Multipoint LDP When the Backbone Has No Route to the Root The control protocol used for constructing Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths ("MP LSPs") contains a field that identifies the address of a "root node". Intermediate nodes are expected to be able to look up that address in their routing tables. However, this is not possible if the route to the root node is a BGP route and the intermediate nodes are part of a BGP-free core. This document specifies procedures that enable an MP LSP to be constructed through a BGP-free core. In these procedures, the root node address is temporarily replaced by an address that is known to the intermediate nodes and is on the path to the true root node. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: IJ. Wijnands, E. Rosen, M. Napierala, N. Leymann |
| RFC6513 Multicast in MPLS/BGP IP VPNs In order for IP multicast traffic within a BGP/MPLS IP VPN (Virtual Private Network) to travel from one VPN site to another, special protocols and procedures must be implemented by the VPN Service Provider. These protocols and procedures are specified in this document. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: E. Rosen, R. Aggarwal |
| RFC6514 BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs This document describes the BGP encodings and procedures for exchanging the information elements required by Multicast in MPLS/BGP IP VPNs, as specified in RFC 6513. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Aggarwal, E. Rosen, T. Morin, Y. Rekhter |
| RFC6515 IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPN To provide Multicast VPN (MVPN) service, Provider Edge routers originate BGP Update messages that carry Multicast-VPN ("MCAST-VPN") BGP routes; they also originate unicast VPN routes that carry MVPN-specific attributes. These routes encode addresses from the customer's address space, as well as addresses from the provider's address space. These two address spaces are independent, and the address family (IPv4 or IPv6) of the two spaces may or may not be the same. These routes always contain an "address family" field that specifies whether the customer addresses are IPv4 addresses or whether they are IPv6 addresses. However, there is no field that explicitly specifies the address family of the provider addresses. To ensure interoperability, this document specifies that provider IPv4 addresses are always encoded in these update messages as 4-octet addresses, and that the distinction between IPv4 and IPv6 is signaled solely by the length of the address field. Specific cases are explained in detail. This document updates RFC 6514. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Aggarwal, E. Rosen |
| RFC6516 IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join Messages The specification for Multicast Virtual Private Networks (MVPNs) contains an option that allows the use of PIM as the control protocol between provider edge routers. It also contains an option that allows UDP-based messages, known as Selective Provider Multicast Service Interface (S-PMSI) Join messages, to be used to bind particular customer multicast flows to particular tunnels through a service provider's network. This document extends the MVPN specification (RFC 6513) so that these options can be used when the customer multicast flows are IPv6 flows. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: Y. Cai, E. Rosen, I. Wijnands |
| RFC6517 Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN Solution More that one set of mechanisms to support multicast in a layer 3 BGP/MPLS VPN has been defined. These are presented in the documents that define them as optional building blocks. | February 2012 Status: INFORMATIONAL Autor: T. Morin, B. Niven-Jenkins, Y. Kamite, R. Zhang, N. Leymann, N. Bitar |
| RFC6518 Keying and Authentication for Routing Protocols (KARP) Design Guidelines This document is one of a series concerned with defining a roadmap of protocol specification work for the use of modern cryptographic mechanisms and algorithms for message authentication in routing protocols. In particular, it defines the framework for a key management protocol that may be used to create and manage session keys for message authentication and integrity. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: G. Lebovitz, M. Bhatia |
| RFC6519 RADIUS Extensions for Dual-Stack Lite Dual-Stack Lite is a solution to offer both IPv4 and IPv6 connectivity to customers that are addressed only with an IPv6 prefix. Dual-Stack Lite requires pre-configuration of the Dual-Stack Lite Address Family Transition Router (AFTR) tunnel information on the Basic Bridging BroadBand (B4) element. In many networks, the customer profile information may be stored in Authentication, Authorization, and Accounting (AAA) servers, while client configurations are mainly provided through the Dynamic Host Configuration Protocol (DHCP). This document specifies a new Remote Authentication Dial-In User Service (RADIUS) attribute to carry the Dual-Stack Lite AFTR tunnel name; the RADIUS attribute is defined based on the equivalent DHCPv6 OPTION_AFTR_NAME option. This RADIUS attribute is meant to be used between the RADIUS server and the Network Access Server (NAS); it is not intended to be used directly between the B4 element and the RADIUS server. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Maglione, A. Durand |
| RFC6520 Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Heartbeat Extension This document describes the Heartbeat Extension for the Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) protocols. | February 2012 Status: PROPOSED STANDARD Autor: R. Seggelmann, M. Tuexen, M. Williams |
| RFC6521 Home Agent-Assisted Route Optimization between Mobile IPv4 Networks This document describes a home agent-assisted route optimization functionality for the IPv4 Network Mobility Protocol. The function is designed to facilitate optimal routing in cases where all nodes are connected to a single home agent; thus, the use case is route optimization within a single organization or similar entity. The functionality enables the discovery of eligible peer nodes (based on information received from the home agent) and their network prefixes, and the establishment of a direct tunnel between such nodes. This document defines an Experimental Protocol for the Internet community. | February 2012 Status: EXPERIMENTAL Autor: A. Makela, J. Korhonen |
| RFC6522 The Multipart/Report Media Type for the Reporting of Mail System Administrative Messages The multipart/report Multipurpose Internet Mail Extensions (MIME) media 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 media type with respect to delivery status reports, mail processing programs will benefit if a single media type is used for all kinds of reports. | January 2012 Status: STANDARD Autor: M. Kucherawy |
| RFC6525 Stream Control Transmission Protocol (SCTP) Stream Reconfiguration Many applications that use the Stream Control Transmission Protocol (SCTP) want the ability to "reset" a stream. The intention of resetting a stream is to set the numbering sequence of the stream back to 'zero' with a corresponding notification to the application layer that the reset has been performed. Applications requiring this feature want it so that they can "reuse" streams for different purposes but still utilize the stream sequence number so that the application can track the message flows. Thus, without this feature, a new use of an old stream would result in message numbers greater than expected, unless there is a protocol mechanism to "reset the streams back to zero". This document also includes methods for resetting the transmission sequence numbers, adding additional streams, and resetting all stream sequence numbers. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: R. Stewart, M. Tuexen, P. Lei |
| RFC6526 IP Flow Information Export (IPFIX) Per Stream Control Transmission Protocol (SCTP) Stream This document specifies an extension to the specifications in RFC 5101, IP Flow Information Export (IPFIX), when using the Partial Reliability extension of SCTP (PR-SCTP, Partial Reliability Stream Control Transmission Protocol). | March 2012 Status: PROPOSED STANDARD Autor: B. Claise, P. Aitken, A. Johnson, G. Muenz |
| RFC6527 Definitions of Managed Objects for Virtual Router Redundancy Protocol Version 3 (VRRPv3) This specification defines a portion of the Management Information Base (MIB) for use with network management based on the Simple Network Management Protocol (SNMP). In particular, it defines objects for configuring, monitoring, and controlling routers that employ the Virtual Router Redundancy Protocol Version 3 (VRRPv3) for both IPv4 and IPv6 as defined in RFC 5798. This memo obsoletes RFC 2787. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: K. Tata |
| RFC6528 Defending against Sequence Number Attacks This document specifies an algorithm for the generation of TCP Initial Sequence Numbers (ISNs), such that the chances of an off-path attacker guessing the sequence numbers in use by a target connection are reduced. This document revises (and formally obsoletes) RFC 1948, and takes the ISN generation algorithm originally proposed in that document to Standards Track, formally updating RFC 793. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: F. Gont, S. Bellovin |
| RFC6529 Host/Host Protocol for the ARPA Network This document reproduces the Host/Host Protocol developed by the ARPA Network Working Group during 1969, 1970, and 1971. It describes a protocol used to manage communication between processes residing on independent Hosts. It addresses issues of multiplexing multiple streams of communication (including addressing, flow control, connection establishment/disestablishment, and other signaling) over a single hardware interface. It was the official protocol of the ARPA Network from January 1972 until the switch to TCP/IP in January 1983. It is offered as an RFC at this late date to help complete the historical record available through the RFC series. This document is not an Internet Standards Track specification; it is published for the historical record. | April 2012 Status: HISTORIC Autor: A. McKenzie, S. Crocker |
| RFC6530 Overview and Framework for Internationalized Email Full use of electronic mail throughout the world requires that (subject to other constraints) people be able to use close variations on their own names (written correctly in their own languages and scripts) as mailbox names in email addresses. This document introduces a series of specifications that define mechanisms and protocol extensions needed to fully support internationalized email addresses. These changes include an SMTP extension and extension of email header syntax to accommodate UTF-8 data. The document set also includes discussion of key assumptions and issues in deploying fully internationalized email. This document is a replacement for RFC 4952; it reflects additional issues identified since that document was published. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: J. Klensin, Y. Ko |
| RFC6531 SMTP Extension for Internationalized Email This document specifies an SMTP extension for transport and delivery of email messages with internationalized email addresses or header information. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: J. Yao, W. Mao |
| RFC6532 Internationalized Email Headers Internet mail was originally limited to 7-bit ASCII. MIME added support for the use of 8-bit character sets in body parts, and also defined an encoded-word construct so other character sets could be used in certain header field values. However, full internationalization of electronic mail requires additional enhancements to allow the use of Unicode, including characters outside the ASCII repertoire, in mail addresses as well as direct use of Unicode in header fields like "From:", "To:", and "Subject:", without requiring the use of complex encoded-word constructs. This document specifies an enhancement to the Internet Message Format and to MIME that allows use of Unicode in mail addresses and most header field content. | February 2012 Status: PROPOSED STANDARD Autor: A. Yang, S. Steele, N. Freed |
| RFC6533 Internationalized Delivery Status and Disposition Notifications Delivery status notifications (DSNs) are critical to the correct operation of an email system. However, the existing Draft Standards (RFC 3461, RFC 3464, RFC 6522) are presently limited to ASCII text in the machine-readable portions of the protocol. This specification adds a new address type for international email addresses so an original recipient address with non-ASCII characters can be correctly preserved even after downgrading. This also provides updated content return media types for delivery status notifications and message disposition notifications to support use of the new address type. | February 2012 Status: PROPOSED STANDARD Autor: T. Hansen, C. Newman, A. Melnikov |
| RFC6535 Dual-Stack Hosts Using "Bump-in-the-Host" (BIH) Bump-in-the-Host (BIH) is a host-based IPv4 to IPv6 protocol translation mechanism that allows a class of IPv4-only applications that work through NATs to communicate with IPv6-only peers. The host on which applications are running may be connected to IPv6-only or dual-stack access networks. BIH hides IPv6 and makes the IPv4-only applications think they are talking with IPv4 peers by local synthesis of IPv4 addresses. This document obsoletes RFC 2767 and RFC 3338. [STANDARDS-TRACK] | February 2012 Status: PROPOSED STANDARD Autor: B. Huang, H. Deng, T. Savolainen |
| RFC6536 Network Configuration Protocol (NETCONF) Access Control Model The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF protocol access for particular users to a pre-configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: A. Bierman, M. Bjorklund |
| RFC6537 Host Identity Protocol Distributed Hash Table Interface This document specifies a common interface for using the Host Identity Protocol (HIP) with a Distributed Hash Table (DHT) service to provide a name-to-Host-Identity-Tag lookup service and a Host- Identity-Tag-to-address lookup service. This document defines an Experimental Protocol for the Internet community. | February 2012 Status: EXPERIMENTAL Autor: J. Ahrenholz |
| RFC6538 The Host Identity Protocol (HIP) Experiment Report This document is a report from the IRTF Host Identity Protocol (HIP) research group documenting the collective experiences and lessons learned from studies, related experimentation, and designs completed by the research group. The document summarizes implications of adding HIP to host protocol stacks, Internet infrastructure, and applications. The perspective of a network operator, as well as a list of HIP experiments, are presented as well. Portions of this report may be relevant also to other network overlay-based architectures or to attempts to deploy alternative networking architectures. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2012 Status: INFORMATIONAL Autor: T. Henderson, A. Gurtov |
| RFC6539 IBAKE: Identity-Based Authenticated Key Exchange Cryptographic protocols based on public-key methods have been traditionally based on certificates and Public Key Infrastructure (PKI) to support certificate management. The emerging field of Identity-Based Encryption (IBE) protocols allows simplification of infrastructure requirements via a Private-Key Generator (PKG) while providing the same flexibility. However, one significant limitation of IBE methods is that the PKG can end up being a de facto key escrow server, with undesirable consequences. Another observed deficiency is a lack of mutual authentication of communicating parties. This document specifies the Identity-Based Authenticated Key Exchange (IBAKE) protocol. IBAKE does not suffer from the key escrow problem and in addition provides mutual authentication as well as perfect forward and backward secrecy. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2012 Status: INFORMATIONAL Autor: V. Cakulev, G. Sundaram, I. Broustis |
| RFC6541 DomainKeys Identified Mail (DKIM) Authorized Third-Party Signatures This experimental specification proposes a modification to DomainKeys Identified Mail (DKIM) allowing advertisement of third-party signature authorizations that are to be interpreted as equivalent to a signature added by the administrative domain of the message's author. This document defines an Experimental Protocol for the Internet community. | February 2012 Status: EXPERIMENTAL Autor: M. Kucherawy |
| RFC6542 Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Channel Binding Hash Agility Currently, channel bindings are implemented using an MD5 hash in the Kerberos Version 5 Generic Security Service Application Programming Interface (GSS-API) mechanism (RFC 4121). This document updates RFC 4121 to allow channel bindings using algorithms negotiated based on Kerberos crypto framework as defined in RFC 3961. In addition, because this update makes use of the last extensible field in the Kerberos client-server exchange message, extensions are defined to allow future protocol extensions. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: S. Emery |
| RFC6544 TCP Candidates with Interactive Connectivity Establishment (ICE) Interactive Connectivity Establishment (ICE) defines a mechanism for NAT traversal for multimedia communication protocols based on the offer/answer model of session negotiation. ICE works by providing a set of candidate transport addresses for each media stream, which are then validated with peer-to-peer connectivity checks based on Session Traversal Utilities for NAT (STUN). ICE provides a general framework for describing candidates but only defines UDP-based media streams. This specification extends ICE to TCP-based media, including the ability to offer a mix of TCP and UDP-based candidates for a single stream. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: J. Rosenberg, A. Keranen, B. B. Lowekamp, A. B. Roach |
| RFC6547 RFC 3627 to Historic Status This document moves "Use of /127 Prefix Length Between Routers Considered Harmful" (RFC 3627) to Historic status to reflect the updated guidance contained in "Using 127-Bit IPv6 Prefixes on Inter- Router Links" (RFC 6164). A Standards Track document supersedes an informational document; therefore, guidance provided in RFC 6164 is to be followed when the two documents are in conflict. This document links the two RFCs so that the IETF's updated guidance on this topic is clearer. This document is not an Internet Standards Track specification; it is published for informational purposes. | February 2012 Status: INFORMATIONAL Autor: W. George |
| RFC6549 OSPFv2 Multi-Instance Extensions OSPFv3 includes a mechanism to support multiple instances of the protocol running on the same interface. OSPFv2 can utilize such a mechanism in order to support multiple routing domains on the same subnet. | March 2012 Status: PROPOSED STANDARD Autor: A. Lindem, A. Roy, S. Mirtorabi |
| RFC6550 RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks Low-Power and Lossy Networks (LLNs) are a class of network in which both the routers and their interconnect are constrained. LLN routers typically operate with constraints on processing power, memory, and energy (battery power). Their interconnects are characterized by high loss rates, low data rates, and instability. LLNs are comprised of anything from a few dozen to thousands of routers. Supported traffic flows include point-to-point (between devices inside the LLN), point-to-multipoint (from a central control point to a subset of devices inside the LLN), and multipoint-to-point (from devices inside the LLN towards a central control point). This document specifies the IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL), which provides a mechanism whereby multipoint-to-point traffic from devices inside the LLN towards a central control point as well as point-to-multipoint traffic from the central control point to the devices inside the LLN are supported. Support for point-to-point traffic is also available. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: T. Winter, P. Thubert, A. Brandt, J. Hui, R. Kelsey, P. Levis, K. Pister, R. Struik, JP. Vasseur, R. Alexander |
| RFC6551 Routing Metrics Used for Path Calculation in Low-Power and Lossy Networks Low-Power and Lossy Networks (LLNs) have unique characteristics compared with traditional wired and ad hoc networks that require the specification of new routing metrics and constraints. By contrast, with typical Interior Gateway Protocol (IGP) routing metrics using hop counts or link metrics, this document specifies a set of link and node routing metrics and constraints suitable to LLNs to be used by the Routing Protocol for Low-Power and Lossy Networks (RPL). [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: JP. Vasseur, M. Kim, K. Pister, N. Dejean, D. Barthel |
| RFC6552 Objective Function Zero for the Routing Protocol for Low-Power and Lossy Networks (RPL) The Routing Protocol for Low-Power and Lossy Networks (RPL) specification defines a generic Distance Vector protocol that is adapted to a variety of network types by the application of specific Objective Functions (OFs). An OF states the outcome of the process used by a RPL node to select and optimize routes within a RPL Instance based on the Information Objects available; an OF is not an algorithm. | March 2012 Status: PROPOSED STANDARD Autor: P. Thubert |
| RFC6553 The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane Datagrams The Routing Protocol for Low-Power and Lossy Networks (RPL) includes routing information in data-plane datagrams to quickly identify inconsistencies in the routing topology. This document describes the RPL Option for use among RPL routers to include such routing information. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: J. Hui, JP. Vasseur |
| RFC6554 An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL) In Low-Power and Lossy Networks (LLNs), memory constraints on routers may limit them to maintaining, at most, a few routes. In some configurations, it is necessary to use these memory-constrained routers to deliver datagrams to nodes within the LLN. The Routing Protocol for Low-Power and Lossy Networks (RPL) can be used in some deployments to store most, if not all, routes on one (e.g., the Directed Acyclic Graph (DAG) root) or a few routers and forward the IPv6 datagram using a source routing technique to avoid large routing tables on memory-constrained routers. This document specifies a new IPv6 Routing header type for delivering datagrams within a RPL routing domain. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: J. Hui, JP. Vasseur, D. Culler, V. Manral |
| RFC6555 Happy Eyeballs: Success with Dual-Stack Hosts When a server's IPv4 path and protocol are working, but the server's IPv6 path and protocol are not working, a dual-stack client application experiences significant connection delay compared to an IPv4-only client. This is undesirable because it causes the dual- stack client to have a worse user experience. This document specifies requirements for algorithms that reduce this user-visible delay and provides an algorithm. [STANDARDS-TRACK] | April 2012 Status: PROPOSED STANDARD Autor: D. Wing, A. Yourtchenko |
| RFC6556 Testing Eyeball Happiness The amount of time it takes to establish a session using common transport APIs in dual-stack networks and networks with filtering such as proposed in BCP 38 is a barrier to IPv6 deployment. This note describes a test that can be used to determine whether an application can reliably establish sessions quickly in a complex environment such as dual-stack (IPv4+IPv6) deployment or IPv6 deployment with multiple prefixes and upstream ingress filtering. This test is not a test of a specific algorithm, but of the external behavior of the system as a black box. Any algorithm that has the intended external behavior will be accepted by it. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2012 Status: INFORMATIONAL Autor: F. Baker |
| RFC6557 Procedures for Maintaining the Time Zone Database Time zone information serves as a basic protocol element in protocols, such as the calendaring suite and DHCP. The Time Zone (TZ) Database specifies the indices used in various protocols, as well as their semantic meanings, for all localities throughout the world. This database has been meticulously maintained and distributed free of charge by a group of volunteers, coordinated by a single volunteer who is now planning to retire. This memo specifies procedures involved with maintenance of the TZ database and associated code, including how to submit proposed updates, how decisions for inclusion of those updates are made, and the selection of a designated expert by and for the time zone community. The intent of this memo is, to the extent possible, to document existing practice and provide a means to ease succession of the database maintainers. This memo documents an Internet Best Current Practice. | February 2012 Status: BEST CURRENT PRACTICE Autor: E. Lear, P. Eggert |
| RFC6558 Sieve Extension for Converting Messages before Delivery This document describes how the "CONVERT" IMAP extension can be used within the Sieve mail filtering language to transform messages before final delivery. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: A. Melnikov, B. Leiba, K. Li |
| RFC6559 A Reliable Transport Mechanism for PIM This document defines a reliable transport mechanism for the PIM protocol for transmission of Join/Prune messages. This eliminates the need for periodic Join/Prune message transmission and processing. The reliable transport mechanism can use either TCP or SCTP as the transport protocol. This document defines an Experimental Protocol for the Internet community. | March 2012 Status: EXPERIMENTAL Autor: D. Farinacci, IJ. Wijnands, S. Venaas, M. Napierala |
| RFC6560 One-Time Password (OTP) Pre-Authentication The Kerberos protocol provides a framework authenticating a client using the exchange of pre-authentication data. This document describes the use of this framework to carry out One-Time Password (OTP) authentication. [STANDARDS-TRACK] | April 2012 Status: PROPOSED STANDARD Autor: G. Richards |
| RFC6561 Recommendations for the Remediation of Bots in ISP Networks This document contains recommendations on how Internet Service Providers can use various remediation techniques to manage the effects of malicious bot infestations on computers used by their subscribers. Internet users with infected computers are exposed to risks such as loss of personal data and increased susceptibility to online fraud. Such computers can also become inadvertent participants in or components of an online crime network, spam network, and/or phishing network as well as be used as a part of a distributed denial-of-service attack. Mitigating the effects of and remediating the installations of malicious bots will make it more difficult for botnets to operate and could reduce the level of online crime on the Internet in general and/or on a particular Internet Service Provider's network. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2012 Status: INFORMATIONAL Autor: J. Livingood, N. Mody, M. O'Reirdan |
| RFC6562 Guidelines for the Use of Variable Bit Rate Audio with Secure RTP This memo discusses potential security issues that arise when using variable bit rate (VBR) audio with the secure RTP profile. Guidelines to mitigate these issues are suggested. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: C. Perkins, JM. Valin |
| RFC6563 Moving A6 to Historic Status This document provides a summary of issues related to the use of A6 records, discusses the current status, and moves RFC 2874 to Historic status, providing clarity to implementers and operators. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2012 Status: INFORMATIONAL Autor: S. Jiang, D. Conrad, B. Carpenter |
| RFC6566 A Framework for the Control of Wavelength Switched Optical Networks (WSONs) with Impairments As an optical signal progresses along its path, it may be altered by the various physical processes in the optical fibers and devices it encounters. When such alterations result in signal degradation, these processes are usually referred to as "impairments". These physical characteristics may be important constraints to consider when using a GMPLS control plane to support path setup and maintenance in wavelength switched optical networks. | March 2012 Status: INFORMATIONAL Autor: Y. Lee, G. Bernstein, D. Li, G. Martinelli |
| RFC6567 Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP This document introduces the transport of call control User-to-User Information (UUI) using the Session Initiation Protocol (SIP) and develops several requirements for a new SIP mechanism. Some SIP sessions are established by or related to a non-SIP application. This application may have information that needs to be transported between the SIP User Agents during session establishment. In addition to interworking with the Integrated Services Digital Network (ISDN) UUI Service, this extension will also be used for native SIP endpoints requiring application UUI. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2012 Status: INFORMATIONAL Autor: A. Johnston, L. Liess |
| RFC6569 Guidelines for Development of an Audio Codec within the IETF This document provides general guidelines for work on developing and specifying an interactive audio codec within the IETF. These guidelines cover the development process, evaluation, requirements conformance, and intellectual property issues. This document is not an Internet Standards Track specification; it is published for informational purposes. | March 2012 Status: INFORMATIONAL Autor: JM. Valin, S. Borilin, K. Vos, C. Montgomery, R. Chen |
| RFC6570 URI Template A URI Template is a compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion. This specification defines the URI Template syntax and the process for expanding a URI Template into a URI reference, along with guidelines for the use of URI Templates on the Internet. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: J. Gregorio, R. Fielding, M. Hadley, M. Nottingham, D. Orchard |
| RFC6573 The Item and Collection Link Relations RFC 5988 standardized a means of indicating the relationships between resources on the Web. This specification defines a pair of reciprocal link relation types that may be used to express the relationship between a collection and its members. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2012 Status: INFORMATIONAL Autor: M. Amundsen |
| RFC6576 IP Performance Metrics (IPPM) Standard Advancement Testing This document specifies tests to determine if multiple independent instantiations of a performance-metric RFC have implemented the specifications in the same way. This is the performance-metric equivalent of interoperability, required to advance RFCs along the Standards Track. Results from different implementations of metric RFCs will be collected under the same underlying network conditions and compared using statistical methods. The goal is an evaluation of the metric RFC itself to determine whether its definitions are clear and unambiguous to implementors and therefore a candidate for advancement on the IETF Standards Track. This document is an Internet Best Current Practice. | March 2012 Status: BEST CURRENT PRACTICE Autor: R. Geib, A. Morton, R. Fardid, A. Steinmitz |
| RFC6577 Authentication-Results Registration Update for Sender Policy Framework (SPF) Results This memo updates the registry of authentication method results in Authentication-Results: message header fields, correcting a discontinuity between the original registry creation and the Sender Policy Framework (SPF) specification. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: M. Kucherawy |
| RFC6578 Collection Synchronization for Web Distributed Authoring and Versioning (WebDAV) This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) that allows efficient synchronization of the contents of a WebDAV collection. [STANDARDS-TRACK] | March 2012 Status: PROPOSED STANDARD Autor: C. Daboo, A. Quillaud |
| RFC6579 The 'disclosure' Link Relation Type This document specifies the 'disclosure' link relation type. It designates a list of IPR disclosures made with respect to the material for which such a relation type is specified. [STANDARDS-TRACK] | March 2012 Status: INFORMATIONAL Autor: M. Yevstifeyev |
| RFC6580 IANA Registries for the Remote Direct Data Placement (RDDP) Protocols The original RFCs that specified the Remote Direct Data Placement (RDDP) protocol suite did not create IANA registries for RDDP error codes, operation codes, and function codes. Extensions to the RDDP protocols now require these registries to be created. This memo creates the RDDP registries, populates them with values defined in the original RDDP RFCs, and provides guidance to IANA for future assignment of code points within these registries. [STANDARDS-TRACK] | April 2012 Status: PROPOSED STANDARD Autor: M. Ko, D. Black |
| RFC6581 Enhanced Remote Direct Memory Access (RDMA) Connection Establishment This document updates RFC 5043 and RFC 5044 by extending Marker Protocol Data Unit (PDU) Aligned Framing (MPA) negotiation for Remote Direct Memory Access (RDMA) connection establishment. The first enhancement extends RFC 5044, enabling peer-to-peer connection establishment over MPA / Transmission Control Protocol (TCP). The second enhancement extends both RFC 5043 and RFC 5044, by providing an option for standardized exchange of RDMA-layer connection configuration. [STANDARDS-TRACK] | April 2012 Status: PROPOSED STANDARD Autor: A. Kanevsky, C. Bestler, R. Sharp, S. Wise |
| RFC6582 The NewReno Modification to TCP's Fast Recovery Algorithm RFC 5681 documents the following four intertwined TCP congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. RFC 5681 explicitly allows certain modifications of these algorithms, including modifications that use the TCP Selective Acknowledgment (SACK) option (RFC 2883), and modifications that respond to "partial acknowledgments" (ACKs that cover new data, but not all the data outstanding when loss was detected) in the absence of SACK. This document describes a specific algorithm for responding to partial acknowledgments, referred to as "NewReno". This response to partial acknowledgments was first proposed by Janey Hoe. This document obsoletes RFC 3782. [STANDARDS-TRACK] | April 2012 Status: PROPOSED STANDARD Autor: T. Henderson, S. Floyd, A. Gurtov, Y. Nishida |
| RFC6583 Operational Neighbor Discovery Problems In IPv4, subnets are generally small, made just large enough to cover the actual number of machines on the subnet. In contrast, the default IPv6 subnet size is a /64, a number so large it covers trillions of addresses, the overwhelming number of which will be unassigned. Consequently, simplistic implementations of Neighbor Discovery (ND) can be vulnerable to deliberate or accidental denial of service (DoS), whereby they attempt to perform address resolution for large numbers of unassigned addresses. Such denial-of-service attacks can be launched intentionally (by an attacker) or result from legitimate operational tools or accident conditions. As a result of these vulnerabilities, new devices may not be able to "join" a network, it may be impossible to establish new IPv6 flows, and existing IPv6 transported flows may be interrupted. | March 2012 Status: INFORMATIONAL Autor: I. Gashinsky, J. Jaeggli, W. Kumari |
| RFC6588 A URN Namespace for ucode This document describes a Uniform Resource Name (URN) namespace for ucode, an identifier system for objects and places. ucode technology is used in many applications, and this document provides a URN namespace for ucode to enable its use in Internet-related devices and software. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2012 Status: INFORMATIONAL Autor: C. Ishikawa |
| RFC6590 Redaction of Potentially Sensitive Data from Mail Abuse Reports Email messages often contain information that might be considered private or sensitive, per either regulation or social norms. When such a message becomes the subject of a report intended to be shared with other entities, the report generator may wish to redact or elide the sensitive portions of the message. This memo suggests one method for doing so effectively. [STANDARDS-TRACK] | April 2012 Status: PROPOSED STANDARD Autor: J. Falk, M. Kucherawy |
| RFC6592 The Null Packet The ever-elusive Null Packet received numerous mentions in documents in the RFC series, but it has never been explicitly defined. This memo corrects that omission. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2012 Status: INFORMATIONAL Autor: C. Pignataro |
| RFC6593 Service Undiscovery Using Hide-and-Go-Seek for the Domain Pseudonym System (DPS) With the ubiquitous success of service discovery techniques, curious clients are faced with an increasing overload of service instances and options listed when they browse for services. A typical domain may contain web servers, remote desktop servers, printers, file servers, video content servers, automatons, Points of Presence using artificial intelligence, etc., all advertising their presence. Unsurprisingly, it is expected that some protocols and services will choose the comfort of anonymity and avoid discovery. | April 2012 Status: EXPERIMENTAL Autor: C. Pignataro, J. Clarke, G. Salgueiro |
| RFC6594 Use of the SHA-256 Algorithm with RSA, Digital Signature Algorithm (DSA), and Elliptic Curve DSA (ECDSA) in SSHFP Resource Records This document updates the IANA registries in RFC 4255, which defines SSHFP, a DNS Resource Record (RR) that contains a standard Secure Shell (SSH) key fingerprint used to verify SSH host keys using DNS Security Extensions (DNSSEC). This document defines additional options supporting SSH public keys applying the Elliptic Curve Digital Signature Algorithm (ECDSA) and the implementation of fingerprints computed using the SHA-256 message digest algorithm in SSHFP Resource Records. [STANDARDS-TRACK] | April 2012 Status: PROPOSED STANDARD Autor: O. Sury |
| RFC6596 The Canonical Link Relation RFC 5988 specifies a way to define relationships between links on the web. This document describes a new type of such a relationship, "canonical", to designate an Internationalized Resource Identifier (IRI) as preferred over resources with duplicative content. This document is not an Internet Standards Track specification; it is published for informational purposes. | April 2012 Status: INFORMATIONAL Autor: M. Ohye, J. Kupke |
RFC, FYI, BCP