Debian Codegraph @

rfc2299.html

raw
1 <pre>Network Working Group A. Ramos
2 Request for Comments: 2299 ISI
3 Category: Informational January 1999
4
5
6
7 <span class="h1">Request for Comments Summary</span>
8
9 RFC Numbers 2200-2299
10
11 Status of This Memo
12
13 This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc2200">RFC 2200</a>
14 through RFCs 2299. This is a status report on these RFCs. This memo
15 provides information for the Internet community. It does not specify
16 an Internet standard of any kind. Distribution of this memo is
17 unlimited.
18
19 Copyright Notice
20
21 Copyright (C) The Internet Society (1999). All Rights Reserved.
22
23 Note
24
25 Many RFCs, but not all, are Proposed Standards, Draft Standards, or
26 Standards. Since the status of these RFCs may change during the
27 standards processing, we note here only that they are on the
28 standards track. Please see the latest edition of "Internet Official
29 Protocol Standards" for the current state and status of these RFCs.
30 In the following, RFCs on the standards track are marked [STANDARDS-
31 TRACK].
32
33 RFC Author Date Title
34 --- ------ ---- -----
35
36
37 <span class="h2"><a class="selflink" id="section-2299" href="#section-2299">2299</a> Ramos </span> Jan 1999 Request for Comments Summary
38
39 This memo.
40
41
42 <span class="h2"><a class="selflink" id="section-2298" href="#section-2298">2298</a> Fajman </span> Mar 1998 An Extensible Message Format
43
44 This memo defines a MIME content-type that may be used by a mail user
45 agent (UA) or electronic mail gateway to report the disposition of a
46 message after it has been sucessfully delivered to a recipient.
47 [STANDARDS-TRACK]
48
49
50
51
52 <span class="grey">Ramos Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
55
56
57 <span class="h2"><a class="selflink" id="section-2297" href="#section-2297">2297</a> Newman </span> Mar 1998 Ipsilon's General Switch
58 Management Protocol
59 Specification Version 2.0
60
61 This memo specifies enhancements to the General Switch Management
62 Protocol (GSMP) [<a href="./rfc1987">RFC1987</a>]. This memo provides information for the
63 Internet community. It does not specify an Internet standard of any
64 kind.
65
66
67 <span class="h2"><a class="selflink" id="section-2296" href="#section-2296">2296</a> Holtman </span> Mar 1998 HTTP Remote Variant Selection
68 Algorithm -- RVSA/1.0
69
70 HTTP allows web site authors to put multiple versions of the same
71 information under a single URL. Transparent content negotiation is a
72 mechanism for automatically selecting the best version when the URL is
73 accessed. A remote variant selection algorithm can be used to speed up
74 the transparent negotiation process. This document defines the remote
75 variant selection algorithm with the version number 1.0. This memo
76 defines an Experimental Protocol for the Internet community. It does
77 not specify an Internet standard of any kind. Discussion and
78 suggestions for improvement are requested.
79
80
81 <span class="h2"><a class="selflink" id="section-2295" href="#section-2295">2295</a> Holtman </span> Mar 1998 Transparent Content
82 Negotiation in HTTP
83
84 HTTP allows web site authors to put multiple versions of the same
85 information under a single URL. Transparent content negotiation is an
86 extensible negotiation mechanism, layered on top of HTTP, for
87 automatically selecting the best version when the URL is accessed. This
88 enables the smooth deployment of new web data formats and markup tags.
89 This memo defines an Experimental Protocol for the Internet community.
90 It does not specify an Internet standard of any kind. Discussion and
91 suggestions for improvement are requested.
92
93
94 <span class="h2"><a class="selflink" id="section-2294" href="#section-2294">2294</a> Kille </span> Mar 1998 Representing the O/R Address
95 hierarchy in the X.500
96 Directory Information Tree
97
98 This document defines a representation of the O/R Address hierarchy in
99 the Directory Information Tree. [STANDARDS-TRACK]
100
101
102
103
104
105
106
107
108 <span class="grey">Ramos Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
111
112
113 <span class="h2"><a class="selflink" id="section-2293" href="#section-2293">2293</a> Kille </span> Mar 1998 Representing Tables and
114 Subtrees in the X.500 Directory
115
116 This document defines techniques for representing two types of
117 information mapping in the OSI Directory: Mapping from a key to a value
118 (or set of values), as might be done in a table lookup, and mapping from
119 a distinguished name to an associated value (or values), where the
120 values are not defined by the owner of the entry. This is achieved by
121 use of a directory subtree. [STANDARDS-TRCK]
122
123
124 <span class="h2"><a class="selflink" id="section-2292" href="#section-2292">2292</a> Stevens </span> Feb 1998 Advanced Sockets API for IPv6
125
126 The current document defines some the "advanced" features of the sockets
127 API that are required for applications to take advantage of additional
128 features of IPv6. This memo provides information for the Internet
129 community. It does not specify an Internet standard of any kind.
130
131
132 <span class="h2"><a class="selflink" id="section-2291" href="#section-2291">2291</a> Slein </span> Feb 1998 Requirements for a Distributed
133 Authoring and Versioning
134 Protocol for the World Wide Web
135
136 This document presents a list of features in the form of requirements
137 for a Web Distributed Authoring and Versioning protocol which, if
138 implemented, would improve the efficiency of common remote editing
139 operations, provide a locking mechanism to prevent overwrite conflicts,
140 improve link management support between non-HTML data types, provide a
141 simple attribute-value metadata facility, provide for the creation and
142 reading of container data types, and integrate versioning into the WWW.
143 This memo provides information for the Internet community. It does not
144 specify an Internet standard of any kind.
145
146
147 <span class="h2"><a class="selflink" id="section-2290" href="#section-2290">2290</a> Solomon </span> Feb 1998 Mobile-IPv4 Configuration
148 Option for PPP IPCP
149
150 Mobile IP [<a href="./rfc2002">RFC 2002</a>] defines media-independent procedures by which a
151 Mobile Node can maintain existing transport and application-layer
152 connections despite changing its point-of-attachment to the Internet and
153 without changing its IP address. PPP [<a href="./rfc1661">RFC 1661</a>] provides a standard
154 method for transporting multi-protocol packets over point-to-point
155 links. As currently specified, Mobile IP Foreign Agents which support
156 Mobile Node connections via PPP can do so only by first assigning unique
157 addresses to those Mobile Nodes, defeating one of the primary advantages
158 of Foreign Agents. This documents corrects this problem by defining the
159 Mobile-IPv4 Configuration Option to the Internet Protocol Control
160 Protocol (IPCP) [<a href="./rfc1332">RFC 1332</a>]. Using this option, two peers can
161
162
163
164 <span class="grey">Ramos Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
167
168
169 communicate their support for Mobile IP during the IPCP phase of PPP.
170 Familiarity with Mobile IP [<a href="./rfc2002">RFC 2002</a>], IPCP [<a href="./rfc1332">RFC 1332</a>], and PPP [RFC
171 1661] is assumed. [STANDARDS-TRACK]
172
173
174 <span class="h2"><a class="selflink" id="section-2289" href="#section-2289">2289</a> Haller </span> Feb 1998 A One-Time Password System
175
176 This document describes a one-time password authentication system (OTP).
177 The system provides authentication for system access (login) and other
178 applications requiring authentication that is secure against passive
179 attacks based on replaying captured reusable passwords. [STANDARDS-
180 TRACK]
181
182
183 <span class="h2"><a class="selflink" id="section-2288" href="#section-2288">2288</a> Lynch </span> Feb 1998 Using Existing Bibliographic
184 Identifiers as Uniform
185 Resource Names
186
187 This document discusses how three major bibliographic identifiers (the
188 ISBN, ISSN and SICI) can be supported within the URN framework and the
189 currently proposed syntax for URNs. This memo provides information for
190 the Internet community. It does not specify an Internet standard of any
191 kind.
192
193
194 <span class="h2"><a class="selflink" id="section-2287" href="#section-2287">2287</a> Krupczak </span> Feb 1998 Definitions of System-Level
195 Managed Objects for Applications
196
197 This memo defines a portion of the Management Information Base (MIB) for
198 use with network management protocols in the Internet community. In
199 particular, it describes a basic set of managed objects for fault,
200 configuration and performance management of applications from a systems
201 perspective. [STANDARDS-TRACK]
202
203
204 <span class="h2"><a class="selflink" id="section-2286" href="#section-2286">2286</a> Kapp </span> Feb 1998 Test Cases for HMAC-RIPEMD160
205 and HMAC-RIPEMD128
206
207 This document provides two sets of test cases for HMAC-RIPEMD160 and
208 HMAC-RIPEMD128. This memo provides information for the Internet
209 community. It does not specify an Internet standard of any kind.
210
211
212
213
214
215
216
217
218
219
220 <span class="grey">Ramos Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
223
224
225 <span class="h2"><a class="selflink" id="section-2285" href="#section-2285">2285</a> Mandeville </span> Feb 1998 Benchmarking Terminology for
226 LAN Switching Devices
227
228 This document is intended to provide terminology for the benchmarking of
229 local area network (LAN) switching devices. It extends the terminology
230 already defined for benchmarking network interconnect devices in RFCs
231 <span class="h2"><a class="selflink" id="section-1242" href="#section-1242">1242</a> and 1944 to switching devices. </span>This memo provides information for
232 the Internet community. It does not specify an Internet standard of any
233 kind.
234
235
236 <span class="h2"><a class="selflink" id="section-2284" href="#section-2284">2284</a> Blunk </span> Mar 1998 PPP Extensible Authentication
237 Protocol (EAP)
238
239 The Point-to-Point Protocol (PPP) provides a standard method for
240 transporting multi-protocol datagrams over point-to-point links. PPP
241 also defines an extensible Link Control Protocol, which allows
242 negotiation of an Authentication Protocol for authenticating its peer
243 before allowing Network Layer protocols to transmit over the link. This
244 document defines the PPP Extensible Authentication Protocol.
245 [STANDARDS-TRACK]
246
247
248 <span class="h2"><a class="selflink" id="section-2283" href="#section-2283">2283</a> Bates </span> Feb 1998 Multiprotocol Extensions for
249 BGP-4
250
251 This document defines extensions to BGP-4 to enable it to carry routing
252 information for multiple Network Layer protocols (e.g., IPv6, IPX,
253 etc...). The extensions are backward compatible - a router that supports
254 the extensions can interoperate with a router that doesn't support the
255 extensions. [STANDARDS-TRACK]
256
257
258 <span class="h2"><a class="selflink" id="section-2282" href="#section-2282">2282</a> Galvin </span> Feb 1998 IAB and IESG Selection,
259 Confirmation, and Recall
260 Process: Operation of the
261 Nominating and Recall
262 Committees
263
264 The process by which the members of the IAB and IESG are selected,
265 confirmed, and recalled is specified. This document specifies an
266 Internet Best Current Practices for the Internet Community, and requests
267 discussion and suggestions for improvements.
268
269
270
271
272
273
274
275
276 <span class="grey">Ramos Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
279
280
281 <span class="h2"><a class="selflink" id="section-2281" href="#section-2281">2281</a> Li </span> Mar 1998 Cisco Hot Standby Router
282 Protocol (HSRP)
283
284 The memo specifies the Hot Standby Router Protocol (HSRP). The goal of
285 the protocol is to allow hosts to appear to use a single router and to
286 maintain connectivity even if the actual first hop router they are using
287 fails. This memo provides information for the Internet community. It
288 does not specify an Internet standard of any kind.
289
290
291 <span class="h2"><a class="selflink" id="section-2280" href="#section-2280">2280</a> Alaettinoglu </span> Jan 1998 Routing Policy Specification
292 Language (RPSL)
293
294 This memo is the reference document for the Routing Policy Specification
295 Language (RPSL). RPSL allows a network operator to be able to specify
296 routing policies at various levels in the Internet hierarchy; for
297 example at the Autonomous System (AS) level. At the same time, policies
298 can be specified with sufficient detail in RPSL so that low level router
299 configurations can be generated from them. RPSL is extensible; new
300 routing protocols and new protocol features can be introduced at any
301 time. [STANDARDS-TRACK]
302
303
304 <span class="h2"><a class="selflink" id="section-2279" href="#section-2279">2279</a> Yergeau </span> Jan 1998 UTF-8, a transformation format
305 of ISO 10646
306
307 UTF-8, the object of this memo, has the characteristic of preserving the
308 full US-ASCII range, providing compatibility with file systems, parsers
309 and other software that rely on US-ASCII values but are transparent to
310 other values. This memo updates and replaces <a href="./rfc2044">RFC 2044</a>, in particular
311 addressing the question of versions of the relevant standards.
312 [STANDARDS-TRACK]
313
314
315 <span class="h2"><a class="selflink" id="section-2278" href="#section-2278">2278</a> Freed </span> Jan 1998 IANA Charset
316 Registration Procedures
317
318 MIME [RFC-2045, <a href="./rfc2046">RFC-2046</a>, <a href="./rfc2047">RFC-2047</a>, <a href="./rfc2184">RFC-2184</a>] and various other modern
319 Internet protocols are capable of using many different charsets. This in
320 turn means that the ability to label different charsets is essential.
321 This registration procedure exists solely to associate a specific name
322 or names with a given charset and to give an indication of whether or
323 not a given charset can be used in MIME text objects. This document
324 specifies an Internet Best Current Practices for the Internet Community,
325 and requests discussion and suggestions for improvements.
326
327
328
329
330
331
332 <span class="grey">Ramos Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
335
336
337 <span class="h2"><a class="selflink" id="section-2277" href="#section-2277">2277</a> Alvestrand </span> Jan 1998 IETF Policy on Character Sets
338 and Languages
339
340 This document is the current policies being applied by the Internet
341 Engineering Steering Group (IESG) towards the standardization efforts in
342 the Internet Engineering Task Force (IETF) in order to help Internet
343 protocols fulfill these requirements. This document specifies an
344 Internet Best Current Practices for the Internet Community, and requests
345 discussion and suggestions for improvements.
346
347
348 <span class="h2"><a class="selflink" id="section-2276" href="#section-2276">2276</a> Sollins </span> Jan 1998 Architectural Principles of
349 Uniform Resource Name Resolution
350
351 This document addresses the issues of the discovery of URN (Uniform
352 Resource Name) resolver services that in turn will directly translate
353 URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource
354 Characteristics). This memo provides information for the Internet
355 community. It does not specify an Internet standard of any kind.
356
357
358 <span class="h2"><a class="selflink" id="section-2275" href="#section-2275">2275</a> Wijnen </span> Jan 1998 View-based Access Control
359 Model (VACM) for the
360 Simple Network Management
361 Protocol (SNMP)
362
363 This document describes the View-based Access Control Model for use in
364 the SNMP architecture [<a href="./rfc2261">RFC2261</a>]. It defines the Elements of Procedure
365 for controlling access to management information. This document also
366 includes a MIB for remotely managing the configuration parameters for
367 the View-based Access Control Model. [STANDARDS-TRACK]
368
369
370 <span class="h2"><a class="selflink" id="section-2274" href="#section-2274">2274</a> Blumenthal </span> Jan 1998 User-based Security Model
371 (USM) for version 3 of the
372 Simple Network Management
373 Protocol (SNMPv3)
374
375 This document describes the User-based Security Model (USM) for SNMP
376 version 3 for use in the SNMP architecture [<a href="./rfc2261">RFC2261</a>]. It defines the
377 Elements of Procedure for providing SNMP message level security. This
378 document also includes a MIB for remotely monitoring/managing the
379 configuration parameters for this Security Model. [STANDARDS-TRACK]
380
381
382
383
384
385
386
387
388 <span class="grey">Ramos Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
391
392
393 <span class="h2"><a class="selflink" id="section-2273" href="#section-2273">2273</a> Levi </span> Jan 1998 SNMPv3 Applications
394
395 This memo describes five types of SNMP applications which make use of an
396 SNMP engine as described in [<a href="./rfc2261">RFC2261</a>]. The types of application
397 described are Command Generators, Command Responders, Notification
398 Originators, Notification Receivers, and Proxy Forwarders. This memo
399 also defines MIB modules for specifying targets of management
400 operations, for notification filtering, and for proxy forwarding.
401 [STANDARDS-TRACK]
402
403
404 <span class="h2"><a class="selflink" id="section-2272" href="#section-2272">2272</a> Case </span> Jan 1998 Message Processing and
405 Dispatching for the Simple
406 Network Management Protocol
407 (SNMP)
408
409 This document describes the Message Processing and Dispatching for SNMP
410 messages within the SNMP architecture [<a href="./rfc2271">RFC2271</a>]. It defines the
411 procedures for dispatching potentially multiple versions of SNMP
412 messages to the proper SNMP Message Processing Models, and for
413 dispatching PDUs to SNMP applications. This document also describes one
414 Message Processing Model - the SNMPv3 Message Processing Model.
415 [STANDARDS-TRACK]
416
417
418 <span class="h2"><a class="selflink" id="section-2271" href="#section-2271">2271</a> Harrington </span> Jan 1998 An Architecture for Describing
419 SNMP Management Frameworks
420
421 This document describes an architecture for describing SNMP Management
422 Frameworks. The architecture is designed to be modular to allow the
423 evolution of the SNMP protocol standards over time. [STANDARDS-TRACK]
424
425
426 <span class="h2"><a class="selflink" id="section-2270" href="#section-2270">2270</a> Stewart </span> Jan 1998 Using a Dedicated AS for Sites
427 Homed to a Single Provider
428
429 With the increased growth of the Internet, the number of customers using
430 BGP4 has grown significantly. <a href="./rfc1930">RFC1930</a> outlines a set of guidelines for
431 when one needs and should use an AS. However, the customer and service
432 provider (ISP) are left with a problem as a result of this in that while
433 there is no need for an allocated AS under the guidelines, certain
434 conditions make the use of BGP4 a very pragmatic and perhaps only way to
435 connect a customer homed to a single ISP. This paper proposes a
436 solution to this problem in line with recommendations set forth in
437 <a href="./rfc1930">RFC1930</a>. This memo provides information for the Internet community. It
438 does not specify an Internet standard of any kind.
439
440
441
442
443
444 <span class="grey">Ramos Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
447
448
449 <span class="h2"><a class="selflink" id="section-2269" href="#section-2269">2269</a> Armitage </span> Jan 1998 Using the MARS Model in
450 non-ATM NBMA Networks
451
452 This document is intended to state the obvious equivalences, and explain
453 the less obvious implications. This memo provides information for the
454 Internet community. It does not specify an Internet standard of any
455 kind.
456
457
458 <span class="h2"><a class="selflink" id="section-2268" href="#section-2268">2268</a> Rivest </span> Mar 1998 A Description of the RC2(r)
459 Encryption Algorithm
460
461 This memo describes a conventional (secret-key) block encryption
462 algorithm, called RC2, which may be considered as a proposal for a DES
463 replacement. This memo provides information for the Internet community.
464 It does not specify an Internet standard of any kind.
465
466
467 <span class="h2"><a class="selflink" id="section-2267" href="#section-2267">2267</a> Ferguson </span> Jan 1998 Network Ingress Filtering:
468 Defeating Denial of Service
469 Attacks which employ
470 IP Source Address Spoofing
471
472 This paper discusses a simple, effective, and straightforward method for
473 using ingress traffic filtering to prohibit DoS attacks which use forged
474 IP addresses to be propagated from 'behind' an Internet Service
475 Provider's (ISP) aggregation point. This memo provides information for
476 the Internet community. It does not specify an Internet standard of any
477 kind.
478
479
480 <span class="h2"><a class="selflink" id="section-2266" href="#section-2266">2266</a> Flick </span> Jan 1998 Definitions of Managed Objects
481 for IEEE 802.12 Repeater Devices
482
483 This memo defines a portion of the Management Information Base (MIB) for
484 use with network management protocols in TCP/IP-based internets. In
485 particular, it defines objects for managing network repeaters based on
486 IEEE 802.12. [STANDARDS-TRACK]
487
488
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Ramos Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
503
504
505 <span class="h2"><a class="selflink" id="section-2265" href="#section-2265">2265</a> Wijnen </span> Jan 1998 View-based Access Control
506 Model (VACM) for the
507 Simple Network Management
508 Protocol (SNMP)
509
510 This document describes the View-based Access Control Model for use in
511 the SNMP architecture [<a href="./rfc2261">RFC2261</a>]. It defines the Elements of Procedure
512 for controlling access to management information. This document also
513 includes a MIB for remotely managing the configuration parameters for
514 the View-based Access Control Model. [STANDARDS-TRACK]
515
516
517 <span class="h2"><a class="selflink" id="section-2264" href="#section-2264">2264</a> Blumenthal </span> Jan 1998 User-based Security Model
518 (USM) for version 3 of the
519 Simple Network Management
520 Protocol (SNMPv3)
521
522 This document describes the User-based Security Model (USM) for SNMP
523 version 3 for use in the SNMP architecture [<a href="./rfc2261">RFC2261</a>]. It defines the
524 Elements of Procedure for providing SNMP message level security. This
525 document also includes a MIB for remotely monitoring/managing the
526 configuration parameters for this Security Model. [STANDARDS-TRACK]
527
528
529 <span class="h2"><a class="selflink" id="section-2263" href="#section-2263">2263</a> Levi </span> Jan 1998 SNMPv3 Applications
530
531 This memo describes five types of SNMP applications which make use of an
532 SNMP engine as described in [<a href="./rfc2261">RFC2261</a>]. The types of application
533 described are Command Generators, Command Responders, Notification
534 Originators, Notification Receivers, and Proxy Forwarders. This memo
535 also defines MIB modules for specifying targets of management
536 operations, for notification filtering, and for proxy forwarding.
537 [STANDARDS-TRACK]
538
539
540 <span class="h2"><a class="selflink" id="section-2262" href="#section-2262">2262</a> Case </span> Jan 1998 Message Processing and
541 Dispatching for the Simple
542 Network Management Protocol
543 (SNMP)
544
545 This document describes the Message Processing and Dispatching for SNMP
546 messages within the SNMP architecture [<a href="./rfc2261">RFC2261</a>]. It defines the
547 procedures for dispatching potentially multiple versions of SNMP
548 messages to the proper SNMP Message Processing Models, and for
549 dispatching PDUs to SNMP applications. This document also describes one
550 Message Processing Model - the SNMPv3 Message Processing Model.
551 [STANDARDS-TRACK]
552
553
554
555
556 <span class="grey">Ramos Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
559
560
561 <span class="h2"><a class="selflink" id="section-2261" href="#section-2261">2261</a> Harrington </span> Jan 1998 An Architecture for Describing
562 SNMP Management Frameworks
563
564 This document describes an architecture for describing SNMP Management
565 Frameworks. The architecture is designed to be modular to allow the
566 evolution of the SNMP protocol standards over time. [STANDARDS-TRACK]
567
568
569 <span class="h2"><a class="selflink" id="section-2260" href="#section-2260">2260</a> Bates </span> Jan 1998 Scalable Support for
570 Multi-homed Multi-provider
571 Connectivity
572
573 This document describes addressing and routing strategies for multi-
574 homed enterprises attached to multiple Internet Service Providers (ISPs)
575 that are intended to reduce the routing overhead due to these
576 enterprises in the global Internet routing system. This memo provides
577 information for the Internet community. It does not specify an Internet
578 standard of any kind.
579
580
581 <span class="h2"><a class="selflink" id="section-2259" href="#section-2259">2259</a> Elliott </span> Jan 1998 Simple Nomenclator Query
582 Protocol (SNQP)
583
584 The Simple Nomenclator Query Protocol (SNQP) allows a client to
585 communicate with a descriptive name service or other relational-style
586 query service. This memo provides information for the Internet
587 community. It does not specify an Internet standard of any kind
588
589
590 <span class="h2"><a class="selflink" id="section-2258" href="#section-2258">2258</a> Ordille </span> Jan 1998 Internet Nomenclator Project
591
592 The goal of the Internet Nomenclator Project is to integrate the
593 hundreds of publicly available CCSO servers from around the world. This
594 document provides an overview of the Nomenclator system, describes how
595 to register a CCSO server in the Internet Nomenclator Project, and how
596 to use the Nomenclator search engine to find people on the Internet.
597 This memo provides information for the Internet community. It does not
598 specify an Internet standard of any kind.
599
600
601 <span class="h2"><a class="selflink" id="section-2257" href="#section-2257">2257</a> Daniele </span> Jan 1998 Agent Extensibility (AgentX)
602 Protocol Version 1
603
604 This memo defines a standardized framework for extensible SNMP agents.
605 It defines processing entities called master agents and subagents, a
606 protocol (AgentX) used to communicate between them, and the elements of
607 procedure by which the extensible agent processes SNMP protocol
608 messages. [STANDARDS-TRACK]
609
610
611
612 <span class="grey">Ramos Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
615
616
617 <span class="h2"><a class="selflink" id="section-2256" href="#section-2256">2256</a> Wahl </span> Dec 1997 A Summary of the X.500(96)
618 User Schema for use with LDAPv3
619
620 This document provides an overview of the attribute types and object
621 classes defined by the ISO and ITU-T committees in the X.500 documents,
622 in particular those intended for use by directory clients. [STANDARDS-
623 TRACK]
624
625
626 <span class="h2"><a class="selflink" id="section-2255" href="#section-2255">2255</a> Howes </span> Dec 1997 The LDAP URL Format
627
628 This document describes a format for an LDAP Uniform Resource Locator.
629 [STANDARDS-TRACK]
630
631
632 <span class="h2"><a class="selflink" id="section-2254" href="#section-2254">2254</a> Howes </span> Dec 1997 The String Representation of
633 LDAP Search Filters
634
635 This document defines a human-readable string format for representing
636 LDAP search filters. [STANDARDS-TRACK]
637
638
639 <span class="h2"><a class="selflink" id="section-2253" href="#section-2253">2253</a> Wahl </span> Dec 1997 Lightweight Directory Access
640 Protocol (v3): UTF-8 String
641 Representation of
642 Distinguished Names
643
644 This specification defines the string format for representing names,
645 which is designed to give a clean representation of commonly used
646 distinguished names, while being able to represent any distinguished
647 name. [STANDARDS-TRACK]
648
649
650 <span class="h2"><a class="selflink" id="section-2252" href="#section-2252">2252</a> Wahl </span> Dec 1997 Lightweight Directory Access
651 Protocol (v3): Attribute
652 Syntax Definitions
653
654 This document defines a set of syntaxes for LDAPv3, and the rules by
655 which attribute values of these syntaxes are represented as octet
656 strings for transmission in the LDAP protocol. [STANDARDS-TRACK]
657
658
659
660
661
662
663
664
665
666
667
668 <span class="grey">Ramos Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
671
672
673 <span class="h2"><a class="selflink" id="section-2251" href="#section-2251">2251</a> Wahl </span> Dec 1997 Lightweight Directory Access
674 Protocol (v3)
675
676 The protocol described in this document is designed to provide access to
677 directories supporting the X.500 models, while not incurring the
678 resource requirements of the X.500 Directory Access Protocol (DAP).
679 [STANDARDS-TRACK]
680
681
682 <span class="h2"><a class="selflink" id="section-2250" href="#section-2250">2250</a> Hoffman </span> Jan 1998 RTP Payload Format for
683 MPEG1/MPEG2 Video
684
685 This memo describes a packetization scheme for MPEG video and audio
686 streams. [STANDARDS-TRACK]
687
688
689 <span class="h2"><a class="selflink" id="section-2249" href="#section-2249">2249</a> Freed </span> Jan 1998 Mail Monitoring MIB
690
691 This memo defines a portion of the Management Information Base (MIB) for
692 use with network management protocols in the Internet community.
693 Specifically, this memo extends the basic Network Services Monitoring
694 MIB [8] to allow monitoring of Message Transfer Agents (MTAs). It may
695 also be used to monitor MTA components within gateways. [STANDARDS-
696 TRACK]
697
698
699 <span class="h2"><a class="selflink" id="section-2248" href="#section-2248">2248</a> Freed </span> Jan 1998 Network Services Monitoring MIB
700
701 This MIB may be used on its own for any application, and for most simple
702 applications this will suffice. This MIB is also designed to serve as a
703 building block which can be used in conjunction with application-
704 specific monitoring and management. [STANDARDS-TRACK]
705
706
707 <span class="h2"><a class="selflink" id="section-2247" href="#section-2247">2247</a> Kille </span> Jan 1998 Using Domains in LDAP/X.500
708 Distinguished Names
709
710 This document defines an algorithm by which a name registered with the
711 Internet Domain Name Service [2] can be represented as an LDAP
712 distinguished name. [STANDARDS-TRACK]
713
714
715
716
717
718
719
720
721
722
723
724 <span class="grey">Ramos Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
727
728
729 <span class="h2"><a class="selflink" id="section-2246" href="#section-2246">2246</a> Dierks </span> Jan 1999 The TLS Protocol Version 1.0
730
731 This document specifies Version 1.0 of the Transport Layer Security
732 (TLS) protocol. The TLS protocol provides communications privacy over
733 the Internet. The protocol allows client/server applications to
734 communicate in a way that is designed to prevent eavesdropping,
735 tampering, or message forgery. [STANDARDS-TRACK]
736
737
738 <span class="h2"><a class="selflink" id="section-2245" href="#section-2245">2245</a> Newman </span> Nov 1997 Anonymous SASL Mechanism
739
740 As plaintext login commands are not permitted in new IETF protocols, a
741 new way to provide anonymous login is needed within the context of the
742 SASL [SASL] framework. [STANDARDS-TRACK]
743
744
745 <span class="h2"><a class="selflink" id="section-2244" href="#section-2244">2244</a> Newman </span> Nov 1997 ACAP -- Application
746 Configuration Access Protocol
747
748 The Application Configuration Access Protocol (ACAP) is designed to
749 support remote storage and access of program option, configuration and
750 preference information. [STANDARDS-TRACK]
751
752
753 <span class="h2"><a class="selflink" id="section-2243" href="#section-2243">2243</a> Metz </span> Nov 1997 OTP Extended Responses
754
755 This document provides a specification for a type of response to an OTP
756 [<a href="./rfc1938">RFC 1938</a>] challenge that carries explicit indication of the response's
757 encoding. This document also provides a specification for a response
758 that allows an OTP generator to request that a server re-initialize a
759 sequence and change parameters such as the secret pass phrase.
760 [STANDARDS-TRACK]
761
762
763 <span class="h2"><a class="selflink" id="section-2242" href="#section-2242">2242</a> Droms </span> Nov 1997 NetWare/IP Domain Name and
764 Information
765
766 This document defines options that carry NetWare/IP domain name and
767 NetWare/IP sub-options to DHCP clients. [STANDARDS-TRACK]
768
769
770
771
772
773
774
775
776
777
778
779
780 <span class="grey">Ramos Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
783
784
785 <span class="h2"><a class="selflink" id="section-2241" href="#section-2241">2241</a> Provan </span> Nov 1997 DHCP Options for Novell
786 Directory Services
787
788 This document defines three new DHCP options for delivering
789 configuration information to clients of the Novell Directory Services.
790 This document defines three new DHCP options for delivering
791 configuration information to clients of the Novell Directory Services.
792 [STANDARDS-TRACK]
793
794
795 <span class="h2"><a class="selflink" id="section-2240" href="#section-2240">2240</a> Vaughan </span> Nov 1997 A Legal Basis for Domain Name
796 Allocation
797
798 The purpose of this memo is to focus discussion on the particular
799 problems with the exhaustion of the top level domain space in the
800 Internet and the possible conflicts that can occur when multiple
801 organisations are vying for the same name. This memo provides
802 information for the Internet community. It does not specify an Internet
803 standard of any kind.
804
805
806 <span class="h2"><a class="selflink" id="section-2239" href="#section-2239">2239</a> de Graaf </span> Nov 1997 Definitions of Managed Objects
807 for IEEE 802.3 Medium
808 Attachment Units (MAUs) using SMIv2
809
810 This memo defines an portion of the Management Information Base (MIB)
811 for use with network management protocols in the Internet community. In
812 particular, it defines objects for managing 10 and 100 Mb/second Medium
813 Attachment Units (MAUs) based on IEEE Std 802.3 <a href="#section-30">Section 30</a>, "10 &amp; 100
814 Mb/s Management," October 26, 1995. [STANDARDS-TRACK]
815
816
817 <span class="h2"><a class="selflink" id="section-2238" href="#section-2238">2238</a> Clouston </span> Nov 1997 Definitions of Managed Objects
818 for HPR using SMIv2
819
820 This memo defines a portion of the Management Information Base (MIB) for
821 use with network management protocols in the Internet community. In
822 particular, it defines objects for monitoring and controlling network
823 devices with HPR (High Performance Routing) capabilities. This memo
824 identifies managed objects for the HPR protocol. [STANDARDS-TRACK]
825
826
827 <span class="h2"><a class="selflink" id="section-2237" href="#section-2237">2237</a> Tamaru </span> Nov 1997 Japanese Character Encoding
828 for Internet Messages
829
830 This memo defines an encoding scheme for the Japanese Characters,
831 describes "ISO-2022-JP-1", which is used in electronic mail [<a href="./rfc822">RFC-822</a>],
832 and network news [<a href="./rfc1036">RFC 1036</a>]. Also this memo provides a listing of the
833
834
835
836 <span class="grey">Ramos Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
839
840
841 Japanese Character Set that can be used in this encoding scheme. This
842 memo provides information for the Internet community. It does not
843 specify an Internet standard of any kind.
844
845
846 <span class="h2"><a class="selflink" id="section-2236" href="#section-2236">2236</a> Fenner </span> Nov 1997 Internet Group Management
847 Protocol, Version 2
848
849 This memo documents IGMPv2, used by IP hosts to report their multicast
850 group memberships to routers. It updates STD 5, <a href="./rfc1112">RFC 1112</a>. [STANDARDS-
851 TRACK]
852
853
854 <span class="h2"><a class="selflink" id="section-2235" href="#section-2235">2235</a> Zakon </span> Nov 1997 Hobbes' Internet Timeline
855
856 This document presents a history of the Internet in timeline fashion,
857 highlighting some of the key events and technologies which helped shape
858 the Internet as we know it today. A growth summary of the Internet and
859 some associated technologies is also included. This memo provides
860 information for the Internet community. It does not specify an Internet
861 standard of any kind.
862
863
864 <span class="h2"><a class="selflink" id="section-2234" href="#section-2234">2234</a> Crocker </span> Nov 1997 Augmented BNF for Syntax
865 Specifications: ABNF
866
867 In the early days of the Arpanet, each specification contained its own
868 definition of ABNF. This included the email specifications, <a href="./rfc733">RFC733</a> and
869 then <a href="./rfc822">RFC822</a> which have come to be the common citations for defining
870 ABNF. The current document separates out that definition, to permit
871 selective reference. Predictably, it also provides some modifications
872 and enhancements. [STANDARDS-TRACK]
873
874
875 <span class="h2"><a class="selflink" id="section-2233" href="#section-2233">2233</a> McCloghrie </span> Nov 1997 The Interfaces Group MIB using
876 SMIv2
877
878 This memo defines a portion of the Management Information Base (MIB) for
879 use with network management protocols in the Internet community. In
880 particular, it describes managed objects used for managing Network
881 Interfaces. [STANDARDS-TRACK]
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Ramos Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
895
896
897 <span class="h2"><a class="selflink" id="section-2232" href="#section-2232">2232</a> Clouston </span> Nov 1997 Definitions of Managed Objects
898 for DLUR using SMIv2
899
900 This memo defines a portion of the Management Information Base (MIB) for
901 use with network management protocols in the Internet community. In
902 particular, it defines objects for monitoring and controlling network
903 devices with DLUR (Dependent LU Requester) capabilities. This memo
904 identifies managed objects for the DLUR protocol. [STANDARDS-TRACK]
905
906
907 <span class="h2"><a class="selflink" id="section-2231" href="#section-2231">2231</a> Freed </span> Nov 1997 MIME Parameter Value and
908 Encoded Word Extensions:
909 Character Sets, Languages, and
910 Continuations
911
912 This memo defines extensions to the <a href="./rfc2045">RFC 2045</a> media type and <a href="./rfc2183">RFC 2183</a>
913 disposition parameter value mechanisms. This memo also defines an
914 extension to the encoded words defined in <a href="./rfc2047">RFC 2047</a> to allow the
915 specification of the language to be used for display as well as the
916 character set. [STANDARDS-TRACK]
917
918
919 <span class="h2"><a class="selflink" id="section-2230" href="#section-2230">2230</a> Atkinson </span> Nov 1997 Key Exchange Delegation Record
920 for the DNS
921
922 This note describes a mechanism whereby authorisation for one node to
923 act as key exchanger for a second node is delegated and made available
924 via the Secure DNS. This mechanism is intended to be used only with the
925 Secure DNS. This memo provides information for the Internet community.
926 It does not specify an Internet standard of any kind.
927
928
929 <span class="h2"><a class="selflink" id="section-2229" href="#section-2229">2229</a> Faith </span> Oct 1997 A Dictionary Server Protocol
930
931 The Dictionary Server Protocol (DICT) is a TCP transaction based
932 query/response protocol that allows a client to access dictionary
933 definitions from a set of natural language dictionary databases. This
934 memo provides information for the Internet community. It does not
935 specify an Internet standard of any kind.
936
937 <span class="h2"><a class="selflink" id="section-2228" href="#section-2228">2228</a> Horowitz </span> Oct 1997 FTP Security Extensions
938
939 This document defines extensions to the FTP specification STD 9, RFC
940 959, "FILE TRANSFER PROTOCOL (FTP)" (October 1985). [STANDARDS-TRACK]
941
942
943
944
945
946
947
948 <span class="grey">Ramos Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
951
952
953 <span class="h2"><a class="selflink" id="section-2227" href="#section-2227">2227</a> Mogul </span> Oct 1997 Simple Hit-Metering and
954 Usage-Limiting for HTTP
955
956 This document proposes a simple extension to HTTP, using a new "Meter"
957 header. [STANDARDS-TRACK]
958
959
960 <span class="h2"><a class="selflink" id="section-2226" href="#section-2226">2226</a> Smith </span> Oct 1997 IP Broadcast over ATM Networks
961
962 This memo describes how the IP multicast service being developed by the
963 IP over ATM working group may be used to support IP broadcast
964 transmission. [STANDARDS-TRACK]
965
966
967 <span class="h2"><a class="selflink" id="section-2225" href="#section-2225">2225</a> Laubach </span> Apr 1998 Classical IP and ARP over ATM
968
969 This memo defines an initial application of classical IP and ARP in an
970 Asynchronous Transfer Mode (ATM) network environment configured as a
971 Logical IP Subnetwork (LIS). [STANDARDS-TRACK]
972
973
974 <span class="h2"><a class="selflink" id="section-2224" href="#section-2224">2224</a> Callaghan </span> Oct 1997 NFS URL Scheme
975
976 A new URL scheme, 'nfs' is defined. It is used to refer to files and
977 directories on NFS servers using the general URL syntax defined in RFC
978 1738, "Uniform Resource Locators (URL)". This memo provides information
979 for the Internet community. It does not specify an Internet standard of
980 any kind.
981
982
983 <span class="h2"><a class="selflink" id="section-2223" href="#section-2223">2223</a> Postel </span> Oct 1997 Instructions to RFC Authors
984
985 This Request for Comments (RFC) provides information about the
986 preparation of RFCs, and certain policies relating to the publication of
987 RFCs. This memo provides information for the Internet community. This
988 memo does not specify an Internet standard of any kind.
989
990
991 <span class="h2"><a class="selflink" id="section-2222" href="#section-2222">2222</a> Myers </span> Oct 1997 Simple Authentication and
992 Security Layer (SASL)
993
994 This document describes a method for adding authentication support to
995 connection-based protocols. [STANDARDS-TRACK]
996
997
998
999
1000
1001
1002
1003
1004 <span class="grey">Ramos Informational [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
1007
1008
1009 <span class="h2"><a class="selflink" id="section-2221" href="#section-2221">2221</a> Gahrns </span> Oct 1997 IMAP4 Login Referrals
1010
1011
1012 When dealing with large amounts of users and many IMAP4 [<a href="./rfc2060">RFC-2060</a>]
1013 servers, it is often necessary to move users from one IMAP4 server to
1014 another. Login referrals allow clients to transparently connect to an
1015 alternate IMAP4 server, if their home IMAP4 server has changed.
1016 [STANDARDS-TRACK]
1017
1018 <span class="h2"><a class="selflink" id="section-2220" href="#section-2220">2220</a> Guenther </span> Oct 1997 The Application/MARC Content-
1019 type
1020
1021 This memorandum provides a mechanism for representing objects which are
1022 files of Machine-Readable Cataloging records (MARC). The MARC formats
1023 are standards for the representation and communication of bibliographic
1024 and related information. A MARC record contains metadata for an
1025 information resource following MARC format specifications. This memo
1026 provides information for the Internet community. It does not specify an
1027 Internet standard of any kind.
1028
1029
1030 <span class="h2"><a class="selflink" id="section-2219" href="#section-2219">2219</a> Hamilton </span> Oct 1997 Use of DNS Aliases for Network
1031 Services
1032
1033 It has become a common practice to use symbolic names (usually CNAMEs)
1034 in the Domain Name Service (DNS - [RFC-1034, <a href="./rfc1035">RFC-1035</a>]) to refer to
1035 network services such as anonymous FTP [<a href="./rfc959">RFC-959</a>] servers, Gopher [RFC-
1036 1436] servers, and most notably World-Wide Web HTTP [<a href="./rfc1945">RFC-1945</a>] servers.
1037 This is desirable for a number of reasons. It provides a way of moving
1038 services from one machine to another transparently, and a mechanism by
1039 which people or agents may programmatically discover that an
1040 organization runs, say, a World-Wide Web server. Although this approach
1041 has been almost universally adopted, there is no standards document or
1042 similar specification for these commonly used names. This document
1043 seeks to rectify this situation by gathering together the extant
1044 'folklore' on naming conventions, and proposes a mechanism for
1045 accommodating new protocols. This document specifies an Internet Best
1046 Current Practices for the Internet Community, and requests discussion
1047 and suggestions for improvements.
1048
1049
1050 <span class="h2"><a class="selflink" id="section-2218" href="#section-2218">2218</a> Genovese </span> Oct 1997 A Common Schema for the
1051 Internet White Pages Service
1052
1053 This document specifies the minimum set of core attributes of a White
1054 Pages entry for an individual and describes how new objects with those
1055 attributes can be defined and published. [STANDARDS-TRACK]
1056
1057
1058
1059
1060 <span class="grey">Ramos Informational [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-2217" href="#section-2217">2217</a> Clark </span> Oct 1997 Telnet Com Port Control Option
1066
1067 This memo proposes a protocol to allow greater use of modems attached to
1068 a network for outbound dialing purposes. This memo defines an
1069 Experimental Protocol for the Internet community.
1070
1071
1072 <span class="h2"><a class="selflink" id="section-2216" href="#section-2216">2216</a> Shenker </span> Sep 1997 Network Element Service
1073 Specification Template
1074
1075 This document defines a framework for specifying services provided by
1076 network elements, and available to applications, in an internetwork
1077 which offers multiple qualities of service. The document first provides
1078 some necessary context -- including relevant definitions and suggested
1079 data formats -- and then specifies a "template" which service
1080 specification documents should follow. This memo provides information
1081 for the Internet community. It does not specify an Internet standard of
1082 any kind.
1083
1084
1085 <span class="h2"><a class="selflink" id="section-2215" href="#section-2215">2215</a> Shenker </span> Sep 1997 General Characterization
1086 Parameters for Integrated
1087 Service Network Elements
1088
1089 This memo defines a set of general control and characterization
1090 parameters for network elements supporting the IETF integrated services
1091 QoS control framework. [STANDARDS-TRACK]
1092
1093
1094 <span class="h2"><a class="selflink" id="section-2214" href="#section-2214">2214</a> Baker </span> Sep 1997 Integrated Services Management
1095 Information Base Guaranteed
1096 Service Extensions using SMIv2
1097
1098 This memo defines a portion of the Management Information Base (MIB) for
1099 use with network management protocols in TCP/IP-based internets. In
1100 particular, it defines objects for managing the the interface attributes
1101 defined in the Guaranteed Service of the Integrated Services Model.
1102 [STANDARDS-TRACK]
1103
1104
1105 <span class="h2"><a class="selflink" id="section-2213" href="#section-2213">2213</a> Baker </span> Sep 1997 Integrated Services Management
1106 Information Base using SMIv2
1107
1108 This memo defines a portion of the Management Information Base (MIB) for
1109 use with network management protocols in TCP/IP-based internets. In
1110 particular, it defines objects for managing the the interface attributes
1111 defined in the Integrated Services Model. [STANDARDS-TRACK]
1112
1113
1114
1115
1116 <span class="grey">Ramos Informational [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="section-2212" href="#section-2212">2212</a> Shenker </span> Sep 1997 Specification of Guaranteed
1122 Quality of Service
1123
1124 This memo describes the network element behavior required to deliver a
1125 guaranteed service (guaranteed delay and bandwidth) in the Internet.
1126 [STANDARDS-TRACK]
1127
1128
1129 <span class="h2"><a class="selflink" id="section-2211" href="#section-2211">2211</a> Wroclawski </span> Sep 1997 Specification of the
1130 Controlled-Load Network
1131 Element Service
1132
1133 This memo specifies the network element behavior required to deliver
1134 Controlled-Load service in the Internet. [STANDARDS-TRACK]
1135
1136
1137 <span class="h2"><a class="selflink" id="section-2210" href="#section-2210">2210</a> Wroclawski </span> Sep 1997 The Use of RSVP with IETF
1138 Integrated Services
1139
1140 This note describes the use of the RSVP resource reservation protocol
1141 with the Controlled-Load and Guaranteed QoS control services.
1142 [STANDARDS-TRACK]
1143
1144
1145 <span class="h2"><a class="selflink" id="section-2209" href="#section-2209">2209</a> Braden </span> Sep 1997 Resource ReSerVation Protocol
1146 (RSVP) -- Version 1 Message
1147 Processing Rules
1148
1149
1150 This memo contains an algorithmic description of the rules used by an
1151 RSVP implementation for processing messages. It is intended to clarify
1152 the version 1 RSVP protocol specification. This memo provides
1153 information for the Internet community. It does not specify an Internet
1154 standard of any kind.
1155
1156
1157 <span class="h2"><a class="selflink" id="section-2208" href="#section-2208">2208</a> Mankin </span> Sep 1997 Resource ReSerVation Protocol
1158 (RSVP) Version 1 Applicability
1159 Statement Some Guidelines on
1160 Deployment
1161
1162 This document describes the applicability of RSVP along with the
1163 Integrated Services protocols and other components of resource
1164 reservation and offers guidelines for deployment of resource reservation
1165 at this time. This memo provides information for the Internet community.
1166 It does not specify an Internet standard of any kind.
1167
1168
1169
1170
1171
1172 <span class="grey">Ramos Informational [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="section-2207" href="#section-2207">2207</a> Berger </span> Sep 1997 RSVP Extensions for IPSEC Data
1178 Flows
1179
1180 This document presents extensions to Version 1 of RSVP. These
1181 extensions permit support of individual data flows using <a href="./rfc1826">RFC 1826</a>, IP
1182 Authentication Header (AH) or <a href="./rfc1827">RFC 1827</a>, IP Encapsulating Security
1183 Payload (ESP). [STANDARDS-TRACK]
1184
1185
1186 <span class="h2"><a class="selflink" id="section-2206" href="#section-2206">2206</a> Baker </span> Sep 1997 RSVP Management Information
1187 This memo defines a portion of
1188
1189 This memo defines a portion of the Management Information Base (MIB) for
1190 use with network management protocols in TCP/IP-based internets. In
1191 particular, it defines objects for managing the Resource Reservation
1192 Protocol (RSVP) within the interface attributes defined in the
1193 Integrated Services Model. [STANDARDS-TRACK]
1194
1195
1196 <span class="h2"><a class="selflink" id="section-2205" href="#section-2205">2205</a> Braden </span> Sep 1997 Resource ReSerVation Protocol
1197 (RSVP)--Version 1 Functional
1198 Specification
1199
1200 This memo describes version 1 of RSVP, a resource reservation setup
1201 protocol designed for an integrated services Internet. RSVP provides
1202 receiver-initiated setup of resource reservations for multicast or
1203 unicast data flows, with good scaling and robustness properties.
1204 [STANDARDS-TRACK]
1205
1206
1207 <span class="h2"><a class="selflink" id="section-2204" href="#section-2204">2204</a> Nash </span> Sep 1997 ODETTE File Transfer Protocol
1208
1209 This memo describes a file transfer protocol to facilitate electronic
1210 data interchange between trading partners. This memo provides
1211 information for the Internet community. It does not specify an Internet
1212 standard of any kind.
1213
1214
1215 <span class="h2"><a class="selflink" id="section-2203" href="#section-2203">2203</a> Eisler </span> Sep 1997 RPCSEC_GSS Protocol Specification
1216
1217 This memo describes an ONC/RPC security flavor that allows RPC protocols
1218 to access the Generic Security Services Application Programming
1219 Interface (referred to henceforth as GSS-API). [STANDARDS-TRACK]
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Ramos Informational [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
1231
1232
1233 <span class="h2"><a class="selflink" id="section-2202" href="#section-2202">2202</a> Cheng </span> Sep 1997 Test Cases for HMAC-MD5 and
1234 HMAC-SHA-1
1235
1236 This document provides two sets of test cases for HMAC-MD5 and HMAC-
1237 SHA-1, respectively. HMAC-MD5 and HMAC-SHA-1 are two constructs of the
1238 HMAC [HMAC] message authentication function using the MD5 [MD5] hash
1239 function and the SHA-1 [SHA] hash function. This memo provides
1240 information for the Internet community. This memo does not specify an
1241 Internet standard of any kind.
1242
1243
1244 <span class="h2"><a class="selflink" id="section-2201" href="#section-2201">2201</a> Ballardie </span> Sep 1997 Core Based Trees (CBT)
1245 Multicast Routing Architecture
1246
1247 CBT is a multicast routing architecture that builds a single delivery
1248 tree per group which is shared by all of the group's senders and
1249 receivers. This memo defines an Experimental Protocol for the Internet
1250 community.
1251
1252
1253 <span class="h2"><a class="selflink" id="section-2200" href="#section-2200">2200</a> IAB </span> Jun 1997 INTERNET OFFICIAL PROTOCOL
1254 STANDARDS
1255
1256 A discussion of the standardization process and the RFC document series
1257 is presented first, followed by an explanation of the terms. Sections
1258 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a> - 6.10 contain the lists of protocols in each stage of</span>
1259 standardization. Finally are pointers to references and contacts for
1260 further information. [STANDARDS-TRACK]
1261
1262
1263
1264 Security Considerations
1265
1266 There are no security issues in this Informational RFC.
1267
1268 Author's Address
1269
1270 Alegre Ramos
1271 University of Southern California
1272 Information Sciences Institute
1273 4676 Admiralty Way
1274 Marina del Rey, CA 90292
1275
1276 Phone: (310) 822-1511
1277 EMail: [email protected]
1278
1279
1280
1281
1282
1283
1284 <span class="grey">Ramos Informational [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2299">RFC 2299</a> Summary of 2200-2299 January 1999</span>
1287
1288
1289 Full Copyright Statement
1290
1291 Copyright (C) The Internet Society (1999). All Rights Reserved.
1292
1293 This document and translations of it may be copied and furnished to
1294 others, and derivative works that comment on or otherwise explain it
1295 or assist in its implementation may be prepared, copied, published
1296 and distributed, in whole or in part, without restriction of any
1297 kind, provided that the above copyright notice and this paragraph are
1298 included on all such copies and derivative works. However, this
1299 document itself may not be modified in any way, such as by removing
1300 the copyright notice or references to the Internet Society or other
1301 Internet organizations, except as needed for the purpose of
1302 developing Internet standards in which case the procedures for
1303 copyrights defined in the Internet Standards process must be
1304 followed, or as required to translate it into languages other than
1305 English.
1306
1307 The limited permissions granted above are perpetual and will not be
1308 revoked by the Internet Society or its successors or assigns.
1309
1310 This document and the information contained herein is provided on an
1311 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1312 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1313 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1314 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1315 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 Ramos Informational [Page 24]
1341 </pre>