Debian Codegraph @

rfc2399.html

raw
1 <pre>Network Working Group A. Ramos
2 Request for Comments: 2399 ISI
3 Category: Informational January 1999
4
5
6 <span class="h1">Request for Comments Summary</span>
7
8 RFC Numbers 2300-2399
9
10 Status of This Memo
11
12 This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc2300">RFC 2300</a>
13 through RFCs 2399. This is a status report on these RFCs. This memo
14 provides information for the Internet community. It does not specify
15 an Internet standard of any kind. Distribution of this memo is
16 unlimited.
17
18 Copyright Notice
19
20 Copyright (C) The Internet Society (1999). All Rights Reserved.
21
22 Note
23
24 Many RFCs, but not all, are Proposed Standards, Draft Standards, or
25 Standards. Since the status of these RFCs may change during the
26 standards processing, we note here only that they are on the
27 standards track. Please see the latest edition of "Internet Official
28 Protocol Standards" for the current state and status of these RFCs.
29 In the following, RFCs on the standards track are marked [STANDARDS-
30 TRACK].
31
32 RFC Author Date Title
33 --- ------ ---- -----
34
35
36 <span class="h2"><a class="selflink" id="section-2399" href="#section-2399">2399</a> Ramos </span> Jan 1999 Request for Comments Summary
37
38 This memo.
39
40
41 <span class="h2"><a class="selflink" id="section-2398" href="#section-2398">2398</a> Parker </span> Aug 1998 Some Testing Tools for TCP
42 Implementors
43
44 This document lists only tools which can evaluate one or more TCP
45 implementations, or which can privde some specific results which
46 describe or evaluate the TCP being tested. This memo provides
47 information for the Internet community. It does not specify an Internet
48 standard of any kind.
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
55
56
57 <span class="h2"><a class="selflink" id="section-2397" href="#section-2397">2397</a> Masinter </span> Aug 1998 The "data" URL scheme
58
59 A new URL scheme, "data", is defined. It allows inclusion of small data
60 items as "immediate" data, as if it had been included externally.
61 [STANDARDS-TRACK]
62
63
64 <span class="h2"><a class="selflink" id="section-2396" href="#section-2396">2396</a> Berners-Lee </span> Aug 1998 Uniform Resource Identifiers
65 (URI): Generic Syntax
66
67 This document defines a grammar that is a superset of all valid URI,
68 such that an implementation can parse the common components of a URI
69 reference without knowing the scheme-specific requirements of every
70 possible identifier type. [STANDARDS-TRACK]
71
72
73 <span class="h2"><a class="selflink" id="section-2395" href="#section-2395">2395</a> Friend </span> Dec 1998 IP Payload Compression Using LZS
74
75 This document describes a compression method based on the LZS
76 compression algorithm. This document defines the application of the LZS
77 algorithm to the IP Payload Compression Protocol. This memo provides
78 information for the Internet community. It does not specify an Internet
79 standard of any kind.
80
81
82 <span class="h2"><a class="selflink" id="section-2394" href="#section-2394">2394</a> Pereira </span> Dec 1998 IP Payload Compression Using
83 DEFLATE
84
85 This document describes a compression method based on the DEFLATE
86 compression algorithm. This document defines the application of the
87 DEFLATE algorithm to the IP Payload Compression Protocol. This memo
88 provides information for the Internet community. It does not specify an
89 Internet standard of any kind.
90
91
92 <span class="h2"><a class="selflink" id="section-2393" href="#section-2393">2393</a> Shacham </span> Dec 1998 IP Payload Compression
93 Protocol (IPComp)
94
95 This document describes a protocol intended to provide lossless
96 compression for Internet Protocol datagrams in an Internet environment.
97 [STANDARDS-TRACK]
98
99
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
111
112
113 <span class="h2"><a class="selflink" id="section-2392" href="#section-2392">2392</a> Levinson </span> Aug 1998 Content-ID and Message-ID
114 Uniform Resource Locators
115
116 The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow
117 references to messages and the body parts of messages. For example,
118 within a single multipart message, one HTML body part might include
119 embedded references to other parts of the same message. [STANDARDS-
120 TRACK]
121
122
123 <span class="h2"><a class="selflink" id="section-2391" href="#section-2391">2391</a> Srisuresh </span> Aug 1998 Load Sharing using IP Network
124 Address Translation (LSNAT)
125
126 In this document, we extend the use of NATs to offer Load share feature,
127 where session load can be distributed across a pool of servers, instead
128 of directing to a single server. This memo provides information for the
129 Internet community. It does not specify an Internet standard of any
130 kind.
131
132
133 <span class="h2"><a class="selflink" id="section-2390" href="#section-2390">2390</a> Bradley </span> Sep 1998 Inverse Address Resolution
134 Protocol
135
136 This memo describes additions to ARP that will allow a station to
137 request a protocol address corresponding to a given hardware address.
138 [STANDARDS-TRACK]
139
140
141 <span class="h2"><a class="selflink" id="section-2389" href="#section-2389">2389</a> Hethmon </span> Aug 1998 Feature negotiation mechanism
142 for the File Transfer Protocol
143
144 This document provides a mechanism by which clients of the FTP protocol
145 can discover which new features are supported by a particular FTP
146 server. [STANDARDS-TRACK]
147
148
149 <span class="h2"><a class="selflink" id="section-2388" href="#section-2388">2388</a> Masinter </span> Aug 1998 Returning Values from Forms:
150 multipart/form-data
151
152 This specification defines an Internet Media Type, multipart/form-data,
153 which can be used by a wide variety of applications and transported by a
154 wide variety of protocols as a way of returning a set of values as the
155 result of a user filling out a form. [STANDARDS-TRACK]
156
157
158
159
160
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
167
168
169 <span class="h2"><a class="selflink" id="section-2387" href="#section-2387">2387</a> Levinson </span> Aug 1998 The MIME Multipart/Related
170 Content-type
171
172 This document defines the Multipart/Related content-type and provides
173 examples of its use. [STANDARDS-TRACK]
174
175 <span class="h2"><a class="selflink" id="section-2386" href="#section-2386">2386</a> Crawley </span> Aug 1998 A Framework for QoS-based
176 Routing in the Internet
177
178 This document describes some of the QoS-based routing issues and
179 requirements, and proposes a framework for QoS-based routing in the
180 Internet. This memo provides information for the Internet community.
181 It does not specify an Internet standard of any kind.
182
183
184
185 <span class="h2"><a class="selflink" id="section-2385" href="#section-2385">2385</a> Heffernan </span> Aug 1998 Protection of BGP Sessions via
186 the TCP MD5 Signature Option
187
188 This memo describes a TCP extension to enhance security for BGP.
189 [STANDARDS-TRACK]
190
191
192 <span class="h2"><a class="selflink" id="section-2384" href="#section-2384">2384</a> Gellens </span> Aug 1998 POP URL Scheme
193
194 This memo defines a URL scheme for referencing a POP mailbox.
195 [STANDARDS-TRACK]
196
197
198 <span class="h2"><a class="selflink" id="section-2383" href="#section-2383">2383</a> Suzuki </span> Aug 1998 ST2+ over ATM Protocol
199 Specification - UNI 3.1 Version
200
201 This document specifies an ATM-based protocol for communication between
202 ST2+ agents. This memo provides information for the Internet community.
203 It does not specify an Internet standard of any kind.
204
205
206 <span class="h2"><a class="selflink" id="section-2382" href="#section-2382">2382</a> Crawley </span> Aug 1998 A Framework for Integrated
207 Services and RSVP over ATM
208
209 This document outlines the issues and framework related to providing IP
210 Integrated Services with RSVP over ATM. This memo provides information
211 for the Internet community. It does not specify an Internet standard of
212 any kind.
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
223
224
225 <span class="h2"><a class="selflink" id="section-2381" href="#section-2381">2381</a> Garrett </span> Aug 1998 Interoperation of
226 Controlled-Load Service
227 and Guaranteed Service with ATM
228
229 This document provides guidelines for mapping service classes, and
230 traffic management features and parameters between Internet and ATM
231 technologies. [STANDARDS-TRACK]
232
233
234 <span class="h2"><a class="selflink" id="section-2380" href="#section-2380">2380</a> Berger </span> Aug 1998 RSVP over ATM Implementation
235 Requirements
236
237 This memo presents specific implementation requirements for running RSVP
238 over ATM switched virtual circuits (SVCs). It presents requirements
239 that ensure interoperability between multiple implementations and
240 conformance to the RSVP and Integrated Services specifications.
241 [STANDARDS-TRACK]
242
243
244 <span class="h2"><a class="selflink" id="section-2379" href="#section-2379">2379</a> Berger </span> Aug 1998 RSVP over ATM Implementation
245 Guidelines
246
247 This memo presents specific implementation guidelines for running RSVP
248 over ATM switched virtual circuits (SVCs). This document specifies an
249 Internet Best Current Practices for the Internet Community, and requests
250 discussion and suggestions for improvements.
251
252
253 <span class="h2"><a class="selflink" id="section-2378" href="#section-2378">2378</a> Hedberg </span> Sep 1998 The CCSO Nameserver (Ph)
254 Architecture
255
256 The Ph Nameserver from the Computing and Communications Services Office
257 (CCSO), University of Illinois at Urbana-Champaign has for some time now
258 been used by several organizations as their choice of publicly available
259 database for information about people as well as other things. This
260 document provides a formal definition of the client-server protocol.
261 This memo provides information for the Internet community. It does not
262 specify an Internet standard of any kind.
263
264
265 <span class="h2"><a class="selflink" id="section-2377" href="#section-2377">2377</a> Grimstad </span> Sep 1998 Naming Plan for Internet
266 Directory-Enabled Applications
267
268 Application of the conventional X.500 approach to naming has heretofore,
269 in the experience of the authors, proven to be an obstacle to the wide
270 deployment of directory-enabled applications on the Internet. We
271 propose a new directory naming plan that leverages the strengths of the
272 most popular and successful Internet naming schemes for naming objects
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
279
280
281 in a hierarchical directory. This memo provides information for the
282 Internet community. It does not specify an Internet standard of any
283 kind.
284
285
286 <span class="h2"><a class="selflink" id="section-2376" href="#section-2376">2376</a> Whitehead </span> Jul 1998 XML Media Types
287
288 This document proposes two new media subtypes, text/xml and
289 application/xml, for use in exchanging network entities which are
290 conforming Extensible Markup Language (XML). This memo provides
291 information for the Internet community. It does not specify an Internet
292 standard of any kind.
293
294
295 <span class="h2"><a class="selflink" id="section-2375" href="#section-2375">2375</a> Hinden </span> Jul 1998 IPv6 Multicast Address
296 Assignments
297
298 This document defines the initial assignment of IPv6 multicast
299 addresses. This memo provides information for the Internet community.
300 It does not specify an Internet standard of any kind.
301
302
303 <span class="h2"><a class="selflink" id="section-2374" href="#section-2374">2374</a> Hinden </span> Jul 1998 An IPv6 Aggregatable Global
304 Unicast Address Format
305
306 This document defines an IPv6 aggregatable global unicast address format
307 for use in the Internet. [STANDARDS-TRACK]
308
309
310 <span class="h2"><a class="selflink" id="section-2373" href="#section-2373">2373</a> Hinden </span> Jul 1998 IP Version 6 Addressing
311 Architecture
312
313 This specification defines the addressing architecture of the IP Version
314 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> protocol [IPV6]. </span>[STANDARDS-TRACK]
315
316
317 <span class="h2"><a class="selflink" id="section-2372" href="#section-2372">2372</a> Evans </span> Jul 1998 Transaction Internet Protocol
318 - Requirements and
319 Supplemental Information
320
321 This document describes the purpose (usage scenarios), and requirements
322 for the Transaction Internet Protocol. This memo provides information
323 for the Internet community. It does not specify an Internet standard of
324 any kind.
325
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
335
336
337 <span class="h2"><a class="selflink" id="section-2371" href="#section-2371">2371</a> Lyon </span> Jul 1998 Transaction Internet Protocol
338 Version 3.0
339
340 In many applications where different nodes cooperate on some work, there
341 is a need to guarantee that the work happens atomically. That is, each
342 node must reach the same conclusion as to whether the work is to be
343 completed, even in the face of failures. This document proposes a
344 simple, easily-implemented protocol for achieving this end.
345 [STANDARDS-TRACK]
346
347
348 <span class="h2"><a class="selflink" id="section-2370" href="#section-2370">2370</a> Coltun </span> Jul 1998 The OSPF Opaque LSA Option
349
350 This memo defines enhancements to the OSPF protocol to support a new
351 class of link-state advertisements (LSA) called Opaque LSAs.
352 [STANDARDS-TRACK]
353
354
355 <span class="h2"><a class="selflink" id="section-2369" href="#section-2369">2369</a> Neufeld </span> Jul 1998 The Use of URLs as Meta-Syntax
356 for Core Mail List Commands
357 and their Transport through
358 Message Header Fields
359
360 The mailing list command specification header fields are a set of
361 structured fields to be added to email messages sent by email
362 distribution lists.
363
364 By including these header fields, list servers can make it possible for
365 mail clients to provide automated tools for users to perform list
366 functions. This could take the form of a menu item, push button, or
367 other user interface element. The intent is to simplify the user
368 experience, providing a common interface to the often cryptic and varied
369 mailing list manager commands. [STANDARDS-TRACK]
370
371
372 <span class="h2"><a class="selflink" id="section-2368" href="#section-2368">2368</a> Hoffman </span> Jul 1998 The mailto URL scheme
373
374 This document defines the format of Uniform Resource Locators (URL) for
375 designating electronic mail addresses. [STANDARDS-TRACK]
376
377
378
379
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
391
392
393 <span class="h2"><a class="selflink" id="section-2367" href="#section-2367">2367</a> McDonald </span> Jul 1998 PF_KEY Key Management API,
394 Version 2
395
396 A generic key management API that can be used not only for IP Security
397 but also for other network security services is presented in this
398 document. This memo provides information for the Internet community.
399 It does not specify an Internet standard of any kind.
400
401
402 <span class="h2"><a class="selflink" id="section-2366" href="#section-2366">2366</a> Chung </span> Jul 1998 Definitions of Managed Objects
403 for Multicast over UNI 3.0/3.1
404 based ATM Networks
405
406 This memo defines a portion of the Management Information Base (MIB) for
407 use with network management protocols in the Internet community. In
408 particular, it describes managed objects for IP hosts and routers that
409 use a Multicast Address Resolution Server (MARS) to support IP multicast
410 over ATM, as described in 'Support for Multicast over UNI 3.0/3.1 based
411 ATM Networks'. [STANDARDS-TRACK]
412
413
414 <span class="h2"><a class="selflink" id="section-2365" href="#section-2365">2365</a> Meyer </span> Jul 1998 Administratively Scoped IP
415 Multicast
416
417 This document defines the "administratively scoped IPv4 multicast space"
418 to be the range 239.0.0.0 to 239.255.255.255. In addition, it describes
419 a simple set of semantics for the implementation of Administratively
420 Scoped IP Multicast. Finally, it provides a mapping between the IPv6
421 multicast address classes [<a href="./rfc1884">RFC1884</a>] and IPv4 multicast address classes.
422 This document specifies an Internet Best Current Practices for the
423 Internet Community, and requests discussion and suggestions for
424 improvements.
425
426
427 <span class="h2"><a class="selflink" id="section-2364" href="#section-2364">2364</a> Gross </span> Jul 1998 PPP Over AAL5
428
429 This document describes the use of ATM Adaptation Layer 5 (AAL5) for
430 framing PPP encapsulated packets. [STANDARDS-TRACK]
431
432
433 <span class="h2"><a class="selflink" id="section-2363" href="#section-2363">2363</a> Gross </span> Jul 1998 PPP Over FUNI
434
435 This document describes the use of ATM Frame User Network Interface
436 (FUNI) for framing PPP encapsulated packets. [STANDARDS-TRACK]
437
438
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
447
448
449 <span class="h2"><a class="selflink" id="section-2362" href="#section-2362">2362</a> Estrin </span> Jun 1998 Protocol Independent
450 Multicast-Sparse Mode (PIM-SM):
451 Protocol Specification
452
453 This document describes a protocol for efficiently routing to multicast
454 groups that may span wide-area (and inter-domain) internets. This memo
455 defines an Experimental Protocol for the Internet community. It does
456 not specify an Internet standard of any kind. Discussion and
457 suggestions for improvement are requested.
458
459
460 <span class="h2"><a class="selflink" id="section-2361" href="#section-2361">2361</a> Fleischman </span> Jun 1998 WAVE and AVI Codec Registries
461
462 The purpose of this paper is to establish a mechanism by which codecs
463 registered within Microsoft's WAVE and AVI Registries may be referenced
464 within the IANA Namespace by Internet applications. This memo provides
465 information for the Internet community. It does not specify an Internet
466 standard of any kind.
467
468
469 <span class="h2"><a class="selflink" id="section-2360" href="#section-2360">2360</a> Scott </span> Jun 1998 Guide for Internet Standards
470 Writers
471
472 This document is a guide for Internet standard writers. It defines
473 those characteristics that make standards coherent, unambiguous, and
474 easy to interpret. This document specifies an Internet Best Current
475 Practices for the Internet Community, and requests discussion and
476 suggestions for improvements.
477
478
479 <span class="h2"><a class="selflink" id="section-2359" href="#section-2359">2359</a> Myers </span> Jun 1998 IMAP4 UIDPLUS extension
480
481 The UIDPLUS extension of the Internet Message Access Protocol [IMAP4]
482 provides a set of features intended to reduce the amount of time and
483 resources used by some client operations. [STANDARDS-TRACK]
484
485
486 <span class="h2"><a class="selflink" id="section-2358" href="#section-2358">2358</a> Flick </span> Jun 1998 Definitions of Managed Objects
487 for the Ethernet-like
488 Interface Types
489
490 This memo defines a portion of the Management Information Base (MIB) for
491 use with network management protocols in the Internet community. This
492 memo obsoletes <a href="./rfc1650">RFC 1650</a> "Definitions of Managed Objects for the
493 Ethernet-like Interface Types using SMIv2". This memo extends that
494 specification by including management information useful for the
495 management of 100 Mb/s Ethernet interfaces. [STANDARDS-TRACK]
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
503
504
505 <span class="h2"><a class="selflink" id="section-2357" href="#section-2357">2357</a> Mankin </span> Jun 1998 IETF Criteria for Evaluating
506 Reliable Multicast Transport
507 and Application Protocols
508
509 This memo describes the procedures and criteria for reviewing reliable
510 multicast protocols within the Transport Area (TSV) of the IETF. Within
511 today's Internet, important applications exist for a reliable multicast
512 service. This memo provides information for the Internet community. It
513 does not specify an Internet standard of any kind.
514
515
516 <span class="h2"><a class="selflink" id="section-2356" href="#section-2356">2356</a> Montenegro </span> Jun 1998 Sun's SKIP Firewall Traversal
517 for Mobile IP
518
519 The Mobile IP specification establishes the mechanisms that enable a
520 mobile host to maintain and use the same IP address as it changes its
521 point of attachment to the network. The mechanisms described in this
522 document allow a mobile node out on a public sector of the internet to
523 negotiate access past a SKIP firewall, and construct a secure channel
524 into its home network. This memo provides information for the Internet
525 community. This memo does not specify an Internet standard of any kind.
526
527
528 <span class="h2"><a class="selflink" id="section-2355" href="#section-2355">2355</a> Kelly </span> Jun 1998 TN3270 Enhancements
529
530 This document describes a protocol that more fully supports 3270 devices
531 than do traditional tn3270 practices. [STANDARDS-TRACK]
532
533
534 <span class="h2"><a class="selflink" id="section-2354" href="#section-2354">2354</a> Perkins </span> Jun 1998 Options for Repair of
535 Streaming Media
536
537 This document summarizes a range of possible techniques for the repair
538 of continuous media streams subject to packet loss. This memo provides
539 information for the Internet community. This memo does not specify an
540 Internet standard of any kind.
541
542
543 <span class="h2"><a class="selflink" id="section-2353" href="#section-2353">2353</a> Dudley </span> May 1998 APPN/HPR in IP Networks
544 APPN Implementers' Workshop
545 Closed Pages Document
546
547 This memo defines a method with which HPR nodes can use IP networks for
548 communication, and the enhancements to APPN required by this method.
549 This memo also describes an option set that allows the use of the APPN
550 connection network model to allow HPR nodes to use IP
551
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
559
560
561 networks for communication without having to predefine link connections.
562 This memo provides information for the Internet community. It does not
563 specify an Internet standard of any kind.
564
565
566 <span class="h2"><a class="selflink" id="section-2352" href="#section-2352">2352</a> Vaughan </span> May 1998 A Convention For Using Legal
567 Names as Domain Names
568
569 The purpose of this memo is to focus discussion on the particular
570 problems with the exhaustion of the top level domain space in the
571 Internet and the possible conflicts that can occur when multiple
572 organisations are vying for the same name. This memo provides
573 information for the Internet community. It does not specify an Internet
574 standard of any kind.
575
576
577 <span class="h2"><a class="selflink" id="section-2351" href="#section-2351">2351</a> Robert </span> May 1998 Mapping of Airline
578 Reservation, Ticketing,
579 and Messaging Traffic over IP
580
581 This memo specifies a protocol for the encapsulation of the airline
582 specific protocol over IP. This memo provides information for the
583 Internet community. It does not specify an Internet standard of any
584 kind.
585
586
587 <span class="h2"><a class="selflink" id="section-2250" href="#section-2250">2250</a> Brownlee </span> Jun 1998 Expectations for Computer
588 Security Incident Response
589
590 The purpose of this document is to express the general Internet
591 community's expectations of Computer Security Incident Response Teams
592 (CSIRTs). It is not possible to define a set of requirements that would
593 be appropriate for all teams, but it is possible and helpful to list and
594 describe the general set of topics and issues which are of concern and
595 interest to constituent communities. This document specifies an
596 Internet Best Current Practices for the Internet Community, and requests
597 discussion and suggestions for improvements.
598
599
600 <span class="h2"><a class="selflink" id="section-2349" href="#section-2349">2349</a> Malkin </span> May 1998 TFTP Timeout Interval and
601 Transfer Size Options
602
603 The Trivial File Transfer Protocol is a simple, lock-step, file transfer
604 protocol which allows a client to get or put a file onto a remote host.
605 This document describes two TFTP options. [STANDARDS-TRACK]
606
607
608
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
615
616
617 <span class="h2"><a class="selflink" id="section-2348" href="#section-2348">2348</a> Malkin </span> May 1998 TFTP Blocksize Option
618
619 The Trivial File Transfer Protocol is a simple, lock-step, file transfer
620 protocol which allows a client to get or put a file onto a remote host.
621 This document describes a TFTP option which allows the client and server
622 to negotiate a blocksize more applicable to the network medium.
623 [STANDARDS-TRACK]
624
625
626 <span class="h2"><a class="selflink" id="section-2347" href="#section-2347">2347</a> Malkin </span> May 1998 TFTP Option Extension
627
628 The Trivial File Transfer Protocol is a simple, lock-step, file transfer
629 protocol which allows a client to get or put a file onto a remote host.
630 This document describes a simple extension to TFTP to allow option
631 negotiation prior to the file transfer. [STANDARDS-TRACK]
632
633
634 <span class="h2"><a class="selflink" id="section-2346" href="#section-2346">2346</a> Palme </span> May 1998 Making Postscript and PDF
635 International
636
637 Certain text formats, for example Postscript (MIME-Type:
638 application/postscript; file extension .ps) and Portable Document Format
639 (MIME-Type: application/pdf; file extension .pdf) specify exactly the
640 page layout of the printed document. The commonly used paper format is
641 different in North America and the rest of the world. North America
642 uses the 'Letter' format, while the rest of the world mostly uses the
643 ISO-standard 'A4' format. This means that documents formatted on one
644 continent may not be easily printable on another continent. This memo
645 gives advice on how to produce documents which are equally well
646 printable with the Letter and the A4 formats. This memo provides
647 information for the Internet community. It does not specify an Internet
648 standard of any kind.
649
650
651 <span class="h2"><a class="selflink" id="section-2345" href="#section-2345">2345</a> Klensin </span> May 1998 Domain Names and Company Name
652 Retrieval
653
654 This document proposes a company name to URL mapping service based on
655 the oldest and least complex of Internet directory protocols, whois, in
656 order to explore whether an extremely simple and widely-deployed
657 protocol can succeed where more complex and powerful options have failed
658 or been excessively delayed. This memo defines an Experimental Protocol
659 for the Internet community. It does not specify an Internet standard of
660 any kind. Discussion and suggestions for improvement are requested.
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
671
672
673 <span class="h2"><a class="selflink" id="section-2344" href="#section-2344">2344</a> Montenegro </span> May 1998 Reverse Tunneling for Mobile IP
674
675 This document proposes backwards-compatible extensions to Mobile IP in
676 order to support topologically correct reverse tunnels. [STANDARDS-
677 TRACK]
678
679
680 <span class="h2"><a class="selflink" id="section-2343" href="#section-2343">2343</a> Civanlar </span> May 1998 RTP Payload Format for Bundled
681 MPEG
682
683 This document describes a payload type for bundled, MPEG-2 encoded video
684 and audio data that may be used with RTP, version 2. This memo defines
685 an Experimental Protocol for the Internet community. This memo does not
686 specify an Internet standard of any kind. Discussion and suggestions
687 for improvement are requested.
688
689
690 <span class="h2"><a class="selflink" id="section-2342" href="#section-2342">2342</a> Gahrns </span> May 1998 IMAP4 Namespace
691
692 This document defines a NAMESPACE command that allows a client to
693 discover the prefixes of namespaces used by a server for personal
694 mailboxes, other users' mailboxes, and shared mailboxes. [STANDARDS-
695 TRACK]
696
697
698 <span class="h2"><a class="selflink" id="section-2341" href="#section-2341">2341</a> Valencia </span> May 1998 Cisco Layer Two Forwarding
699 (Protocol) "L2F"
700
701 This document describes the Layer Two Forwarding protocol (L2F) which
702 permits the tunneling of the link layer (i.e., HDLC, async HDLC, or SLIP
703 frames) of higher level protocols. This memo describes a historic
704 protocol for the Internet community. It does not specify an Internet
705 standard of any kind.
706
707
708 <span class="h2"><a class="selflink" id="section-2340" href="#section-2340">2340</a> Jamoussi </span> May 1998 Nortel's Virtual Network
709 Switching (VNS) Overview
710
711 This document provides an overview of Virtual Network Switching (VNS).
712 This memo provides information for the Internet community. It does not
713 specify an Internet standard of any kind.
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
727
728
729 <span class="h2"><a class="selflink" id="section-2339" href="#section-2339">2339</a> ISOC </span> May 1998 An Agreement Between the
730 Internet Society, the IETF,
731 and Sun Microsystems, Inc. in
732 the matter of NFS V.4 Protocols
733
734 This Request for Comments records an agreement between Sun Microsystems,
735 Inc. and the Internet Society to permit the flow of Sun's Network File
736 System specifications into the Internet Standards process conducted by
737 the Internet Engineering Task Force. This memo provides information for
738 the Internet community. It does not specify an Internet standard of any
739 kind.
740
741
742 <span class="h2"><a class="selflink" id="section-2338" href="#section-2338">2338</a> Knight </span> Apr 1998 Virtual Router Redundancy Protocol
743
744 This memo defines the Virtual Router Redundancy Protocol (VRRP). VRRP
745 specifies an election protocol that dynamically assigns responsibility
746 for a virtual router to one of the VRRP routers on a LAN. [STANDARDS-
747 TRACK]
748
749
750 <span class="h2"><a class="selflink" id="section-2337" href="#section-2337">2337</a> Farinacci </span> Apr 1998 Intra-LIS IP multicast among
751 routers over ATM using Sparse
752 Mode PIM
753
754 This document describes how intra-LIS IP multicast can be efficiently
755 supported among routers over ATM without using the Multicast Address
756 Resolution Server (MARS). This memo defines an Experimental Protocol
757 for the Internet community. It does not specify an Internet standard of
758 any kind. Discussion and suggestions for improvement are requested.
759
760
761 <span class="h2"><a class="selflink" id="section-2336" href="#section-2336">2336</a> Luciani </span> Jul 1998 Classical IP and ARP over ATM
762 to NHRP Transition
763
764 This document describes methods and procedures for the graceful
765 transition from an ATMARP LIS to an NHRP LIS network model over ATM.
766 This memo provides information for the Internet community. It does not
767 specify an Internet standard of any kind.
768
769
770 <span class="h2"><a class="selflink" id="section-2335" href="#section-2335">2335</a> Luciani </span> Apr 1998 A Distributed NHRP Service
771 Using SCSP
772
773 This document describes a method for distributing an NHRP service within
774 a LIS. [STANDARDS-TRACK]
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
783
784
785 <span class="h2"><a class="selflink" id="section-2334" href="#section-2334">2334</a> Luciani </span> Apr 1998 Server Cache Synchronization
786 Protocol (SCSP)
787
788 This document describes the Server Cache Synchronization Protocol (SCSP)
789 and is written in terms of SCSP's use within Non Broadcast Multiple
790 Access (NBMA) networks; although, a somewhat straight forward usage is
791 applicable to BMA networks. [STANDARDS-TRACK]
792
793
794 <span class="h2"><a class="selflink" id="section-2333" href="#section-2333">2333</a> Cansever </span> Apr 1998 NHRP Protocol Applicability
795 Statement
796
797 As required by the Routing Protocol Criteria [<a href="./rfc1264">RFC 1264</a>], this memo
798 discusses the applicability of the Next Hop Resolution Protocol (NHRP)
799 in routing of IP datagrams over Non-Broadcast Multiple Access (NBMA)
800 networks, such as ATM, SMDS and X.25. [STANDARDS-TRACK]
801
802
803 <span class="h2"><a class="selflink" id="section-2332" href="#section-2332">2332</a> Luciani </span> Apr 1998 NBMA Next Hop Resolution
804 Protocol (NHRP)
805
806 This document describes the NBMA Next Hop Resolution Protocol (NHRP).
807 NHRP can be used by a source station (host or router) connected to a
808 Non-Broadcast, Multi-Access (NBMA) subnetwork to determine the
809 internetworking layer address and NBMA subnetwork addresses of the "NBMA
810 next hop" towards a destination station. [STANDARDS-TRACK]
811
812
813 <span class="h2"><a class="selflink" id="section-2331" href="#section-2331">2331</a> Maher </span> Apr 1998 ATM Signalling Support for IP
814 over ATM - UNI Signalling 4.0
815 Update
816
817 This memo describes how to efficiently use the ATM call control
818 signalling procedures defined in UNI Signalling 4.0 to support IP over
819 ATM environments as described in <a href="./rfc2225">RFC 2225</a> and in <a href="./rfc2332">RFC 2332</a>. [STANDARDS-
820 TRACK]
821
822
823 <span class="h2"><a class="selflink" id="section-2330" href="#section-2330">2330</a> Paxson </span> May 1998 Framework for IP Performance
824 Metrics
825
826 The purpose of this memo is to define a general framework for particular
827 metrics to be developed by the IETF's IP Performance Metrics effort.
828 This memo provides information for the Internet community. It does not
829 specify an Internet standard of any kind.
830
831
832
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
839
840
841 <span class="h2"><a class="selflink" id="section-2329" href="#section-2329">2329</a> Moy </span> Apr 1998 OSPF Standardization Report
842
843 This memo documents how the requirements for advancing a routing
844 protocol to Full Standard have been met for OSPFv2. This memo provides
845 information for the Internet community. It does not specify an Internet
846 standard of any kind.
847
848
849 <span class="h2"><a class="selflink" id="section-2328" href="#section-2328">2328</a> Moy </span> Apr 1998 OSPF Version 2
850
851 This memo documents version 2 of the OSPF protocol. OSPF is a link-
852 state routing protocol. [STANDARDS-TRACK]
853
854
855 <span class="h2"><a class="selflink" id="section-2327" href="#section-2327">2327</a> Handley </span> Apr 1998 SDP: Session Description Protocol
856
857 This document defines the Session Description Protocol, SDP. SDP is
858 intended for describing multimedia sessions for the purposes of session
859 announcement, session invitation, and other forms of multimedia session
860 initiation. [STANDARDS-TRACK]
861
862
863 <span class="h2"><a class="selflink" id="section-2326" href="#section-2326">2326</a> Schulzrinne </span> Apr 1998 Real Time Streaming Protocol
864 (RTSP)
865
866 The Real Time Streaming Protocol, or RTSP, is an application-level
867 protocol for control over the delivery of data with real-time
868 properties. RTSP provides an extensible framework to enable controlled,
869 on-demand delivery of real-time data, such as audio and video.
870 [STANDARDS-TRACK]
871
872
873 <span class="h2"><a class="selflink" id="section-2325" href="#section-2325">2325</a> Slavitch </span> 1 Apr 1998 Definitions of Managed Objects
874 for Drip-Type Heated Beverage
875 Hardware Devices using SMIv2
876
877 This memo defines an extension to the Management Information Base (MIB)
878 for use with network management protocols in the Internet community. In
879 particular, it defines objects for the management of coffee-brewing and
880 maintenance devices. This memo provides information for the Internet
881 community. It does not specify an Internet standard of any kind.
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
895
896
897 <span class="h2"><a class="selflink" id="section-2324" href="#section-2324">2324</a> Masinter </span> 1 Apr 1998 Hyper Text Coffee Pot Control
898 Protocol (HTCPCP/1.0)
899
900 This document describes HTCPCP, a protocol for controlling, monitoring,
901 and diagnosing coffee pots. This memo provides information for the
902 Internet community. It does not specify an Internet standard of any
903 kind.
904
905
906 <span class="h2"><a class="selflink" id="section-2323" href="#section-2323">2323</a> Ramos </span> 1 Apr 1998 IETF Identification and
907 Security Guidelines
908
909 This RFC is meant to represent a guideline by which the IETF conferences
910 may run more effeciently with regards to identification and security
911 protocols, with specific attention paid to a particular sub-group within
912 the IETF: "facial hairius extremis". This memo provides information for
913 the Internet community. It does not specify an Internet standard of any
914 kind.
915
916
917 <span class="h2"><a class="selflink" id="section-2322" href="#section-2322">2322</a> van den Hout </span> 1 Apr 1998 Management of IP numbers by
918 peg-dhcp
919
920 This RFC describes a protocol to dynamically hand out ip-numbers on
921 field networks and small events that don't necessarily have a clear
922 organisational body. This memo provides information for the Internet
923 community. It does not specify an Internet standard of any kind.
924
925
926 <span class="h2"><a class="selflink" id="section-2321" href="#section-2321">2321</a> Bressen </span> 1 Apr 1998 RITA -- The Reliable
927 Internetwork Troubleshooting
928 Agent
929
930 A Description of the usage of Nondeterministic Troubleshooting and
931 Diagnostic Methodologies as applied to today's complex nondeterministic
932 networks and environments. This memo provides information for the
933 Internet community. It does not specify an Internet standard of any
934 kind.
935
936
937 <span class="h2"><a class="selflink" id="section-2320" href="#section-2320">2320</a> Greene </span> Apr 1998 Definitions of Managed Objects
938 for Classical IP and ARP Over
939 ATM Using SMIv2
940
941 The purpose of this memo is to define the Management Information Base
942 (MIB) for supporting Classical IP and ARP over ATM as specified in
943 Classical IP and ARP over ATM. [STANDARDS-TRACK]
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
951
952
953 <span class="h2"><a class="selflink" id="section-2319" href="#section-2319">2319</a> KOI8-U WG </span> Apr 1998 Ukrainian Character Set KOI8-U
954
955 This document provides information about character encoding KOI8-U (KOI8
956 Ukrainian) wich is a de-facto standard in Ukrainian Internet community.
957 This memo provides information for the Internet community. It does not
958 specify an Internet standard of any kind.
959
960
961 <span class="h2"><a class="selflink" id="section-2318" href="#section-2318">2318</a> Lie </span> Mar 1998 The text/css Media Type
962
963 This memo provides information about the text/css Media Type. This memo
964 provides information for the Internet community. It does not specify an
965 Internet standard of any kind.
966
967
968 <span class="h2"><a class="selflink" id="section-2317" href="#section-2317">2317</a> Eidnes </span> Mar 1998 Classless IN-ADDR.ARPA delegation
969
970 This document describes a way to do IN-ADDR.ARPA delegation on non-octet
971 boundaries for address spaces covering fewer than 256 addresses. This
972 document specifies an Internet Best Current Practices for the Internet
973 Community, and requests discussion and suggestions for improvements.
974
975
976 <span class="h2"><a class="selflink" id="section-2316" href="#section-2316">2316</a> Bellovin </span> Apr 1998 Report of the IAB Security
977 Architecture Workshop
978
979 On 3-5 March 1997, the IAB held a security architecture workshop at Bell
980 Labs in Murray Hill, NJ. We identified the core security components of
981 the architecture, and specified several documents that need to be
982 written. Most importantly, we agreed that security was not optional,
983 and that it needed to be designed in from the beginning. This memo
984 provides information for the Internet community. It does not specify an
985 Internet standard of any kind.
986
987
988 <span class="h2"><a class="selflink" id="section-2315" href="#section-2315">2315</a> Kaliski </span> Mar 1998 PKCS #7: Cryptographic Message
989 Syntax Version 1.5
990
991 This document describes a general syntax for data that may have
992 cryptography applied to it, such as digital signatures and digital
993 envelopes. This memo provides information for the Internet community.
994 It does not specify an Internet standard of any kind.
995
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
1007
1008
1009 <span class="h2"><a class="selflink" id="section-2314" href="#section-2314">2314</a> Kaliski </span> Mar 1998 PKCS #10: Certification
1010 Request Syntax Version 1.5
1011
1012 This document describes a syntax for certification requests. This memo
1013 provides information for the Internet community. It does not specify an
1014 Internet standard of any kind.
1015
1016
1017 <span class="h2"><a class="selflink" id="section-2313" href="#section-2313">2313</a> Kaliski </span> Mar 1998 PKCS #1: RSA Encryption
1018 Version 1.5
1019
1020 This document describes a method for encrypting data using the RSA
1021 public-key cryptosystem. This memo provides information for the
1022 Internet community. It does not specify an Internet standard of any
1023 kind.
1024
1025
1026 <span class="h2"><a class="selflink" id="section-2312" href="#section-2312">2312</a> Dusse </span> Mar 1998 S/MIME Version 2 Certificate
1027 Handling
1028
1029 This memo describes the mechanisms S/MIME uses to create and validate
1030 keys using certificates. This memo provides information for the
1031 Internet community. It does not specify an Internet standard of any
1032 kind.
1033
1034
1035 <span class="h2"><a class="selflink" id="section-2311" href="#section-2311">2311</a> Dusse </span> Mar 1998 S/MIME Version 2 Message
1036 Specification
1037
1038 This document describes a protocol for adding cryptographic signature
1039 and encryption services to MIME data. This memo provides information
1040 for the Internet community. It does not specify an Internet standard of
1041 any kind.
1042
1043
1044 <span class="h2"><a class="selflink" id="section-2310" href="#section-2310">2310</a> Holtman </span> Apr 1998 The Safe Response Header Field
1045
1046 This document defines a HTTP response header field called Safe, which
1047 can be used to indicate that repeating a HTTP request is safe. This
1048 memo defines an Experimental Protocol for the Internet community. It
1049 does not specify an Internet standard of any kind. Discussion and
1050 suggestions for improvement are requested.
1051
1052
1053
1054
1055
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-2309" href="#section-2309">2309</a> Braden </span> Apr 1998 Recommendations on Queue
1066 Management and Congestion Avoidance
1067 in the Internet
1068
1069 This memo presents two recommendations to the Internet community
1070 concerning measures to improve and preserve Internet performance. It
1071 presents a strong recommendation for testing, standardization, and
1072 widespread deployment of active queue management in routers, to improve
1073 the performance of today's Internet. It also urges a concerted effort
1074 of research, measurement, and ultimate deployment of router mechanisms
1075 to protect the Internet from flows that are not sufficiently responsive
1076 to congestion notification. This memo provides information for the
1077 Internet community. It does not specify an Internet standard of any
1078 kind.
1079
1080
1081 <span class="h2"><a class="selflink" id="section-2308" href="#section-2308">2308</a> Andrews </span> Mar 1998 Negative Caching of DNS
1082 Queries (DNS NCACHE)
1083
1084 <a href="./rfc1034">RFC1034</a> provided a description of how to cache negative responses. It
1085 however had a fundamental flaw in that it did not allow a name server to
1086 hand out those cached responses to other resolvers, thereby greatly
1087 reducing the effect of the caching. This document addresses issues
1088 raise in the light of experience and replaces <a href="./rfc1034#section-4.3.4">RFC1034 Section&nbsp;4.3.4</a>.
1089 [STANDARDS-TRACK]
1090
1091
1092 <span class="h2"><a class="selflink" id="section-2307" href="#section-2307">2307</a> Howard </span> Mar 1998 An Approach for Using LDAP as
1093 a Network Information Service
1094
1095 This document describes an experimental mechanism for mapping entities
1096 related to TCP/IP and the UNIX system into X.500 entries so that they
1097 may be resolved with the Lightweight Directory Access Protocol
1098 [<a href="./rfc2251">RFC2251</a>]. This memo defines an Experimental Protocol for the Internet
1099 community. It does not specify an Internet standard of any kind.
1100 Discussion and suggestions for improvement are requested.
1101
1102
1103 <span class="h2"><a class="selflink" id="section-2306" href="#section-2306">2306</a> Parsons </span> Mar 1998 Tag Image File Format (TIFF) -
1104 F Profile for Facsimile
1105
1106 This document describes in detail the definition of TIFF-F that is used
1107 to store facsimile images. This memo provides information for the
1108 Internet community. It does not specify an Internet standard of any
1109 kind.
1110
1111
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="section-2305" href="#section-2305">2305</a> Toyoda </span> Mar 1998 A Simple Mode of Facsimile
1122 Using Internet Mail
1123
1124 This specification provides for "simple mode" carriage of facsimile data
1125 over the Internet. [STANDARDS-TRACK]
1126
1127
1128 <span class="h2"><a class="selflink" id="section-2304" href="#section-2304">2304</a> Allocchio </span> Mar 1998 Minimal FAX address format in
1129 Internet Mail
1130
1131 This memo describes the MINIMAL addressing method and standard
1132 extensions to encode FAX addresses in e-mail addresses. [STANDARDS-
1133 TRACK]
1134
1135
1136 <span class="h2"><a class="selflink" id="section-2303" href="#section-2303">2303</a> Allocchio </span> Mar 1998 Minimal PSTN address format in
1137 Internet Mail
1138
1139 This memo describes the MINIMAL addressing method to encode PSTN
1140 addresses into e-mail addresses and the standard extension mechanism to
1141 allow definition of further standard elements. [STANDARDS-TRACK]
1142
1143
1144 <span class="h2"><a class="selflink" id="section-2302" href="#section-2302">2302</a> Parsons </span> Mar 1998 Tag Image File Format (TIFF) -
1145 image/tiff MIME Sub-type
1146 Registration
1147
1148 This document describes the registration of the MIME sub-type
1149 image/tiff. [STANDARDS-TRACK]
1150
1151
1152 <span class="h2"><a class="selflink" id="section-2301" href="#section-2301">2301</a> McIntyre </span> Mar 1998 File Format for Internet Fax
1153
1154 This document describes the TIFF (Tag Image File Format) representation
1155 of image data specified by the ITU-T Recommendations for black-and-white
1156 and color facsimile. [STANDARDS-TRACK]
1157
1158
1159 <span class="h2"><a class="selflink" id="section-2300" href="#section-2300">2300</a> IAB </span> May 1998 INTERNET OFFICIAL PROTOCOL
1160 STANDARDS
1161
1162 A discussion of the standardization process and the RFC document series
1163 is presented first, followed by an explanation of the terms. Sections
1164 <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>
1165 standardization. Finally are pointers to references and contacts for
1166 further information. [STANDARDS-TRACK]
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
1175
1176
1177 Security Considerations
1178
1179 There are no security issues in this Informational RFC.
1180
1181 Author's Address
1182
1183 Alegre Ramos
1184 University of Southern California
1185 Information Sciences Institute
1186 4676 Admiralty Way
1187 Marina del Rey, CA 90292
1188
1189 Phone: (310) 822-1511
1190 EMail: [email protected]
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
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="./rfc2399">RFC 2399</a> Summary of 2300-2399 January 1999</span>
1231
1232
1233 Full Copyright Statement
1234
1235 Copyright (C) The Internet Society (1999). All Rights Reserved.
1236
1237 This document and translations of it may be copied and furnished to
1238 others, and derivative works that comment on or otherwise explain it
1239 or assist in its implementation may be prepared, copied, published
1240 and distributed, in whole or in part, without restriction of any
1241 kind, provided that the above copyright notice and this paragraph are
1242 included on all such copies and derivative works. However, this
1243 document itself may not be modified in any way, such as by removing
1244 the copyright notice or references to the Internet Society or other
1245 Internet organizations, except as needed for the purpose of
1246 developing Internet standards in which case the procedures for
1247 copyrights defined in the Internet Standards process must be
1248 followed, or as required to translate it into languages other than
1249 English.
1250
1251 The limited permissions granted above are perpetual and will not be
1252 revoked by the Internet Society or its successors or assigns.
1253
1254 This document and the information contained herein is provided on an
1255 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1256 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1257 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1258 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1259 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 Ramos Informational [Page 23]
1285 </pre>