| 1 |
<pre>Network Working Group J. Elliott |
| 2 |
Request for Comments: 1899 ISI |
| 3 |
Category: Informational January 1997 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Request for Comments Summary</span> |
| 7 |
|
| 8 |
RFC Numbers 1800-1899 |
| 9 |
|
| 10 |
Status of This Memo |
| 11 |
|
| 12 |
This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc1800">RFC 1800</a> |
| 13 |
through RFCs 1899. 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 |
Note |
| 19 |
|
| 20 |
Many RFCs, but not all, are Proposed Standards, Draft Standards, or |
| 21 |
Standards. Since the status of these RFCs may change during the |
| 22 |
standards processing, we note here only that they are on the |
| 23 |
standards track. Please see the latest edition of "Internet Official |
| 24 |
Protocol Standards" for the current state and status of these RFCs. |
| 25 |
In the following, RFCs on the standards track are marked [STANDARDS- |
| 26 |
TRACK]. |
| 27 |
|
| 28 |
RFC Author Date Title |
| 29 |
--- ------ ---- ----- |
| 30 |
|
| 31 |
<span class="h2"><a class="selflink" id="section-1899" href="#section-1899">1899</a> Elliott </span> Jan 97 Requests For Comments Summary |
| 32 |
|
| 33 |
This memo. |
| 34 |
|
| 35 |
|
| 36 |
<span class="h2"><a class="selflink" id="section-1898" href="#section-1898">1898</a> Eastlake </span> Feb 96 CyberCash Credit Card Protocol |
| 37 |
Version 0.8 |
| 38 |
|
| 39 |
This document covers only the current CyberCash system which is one of |
| 40 |
the few operational systems in the rapidly evolving area of Internet |
| 41 |
payments. This memo provides information for the Internet community. |
| 42 |
This memo does not specify an Internet standard of any kind. |
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Elliott Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1897" href="#section-1897">1897</a> Hinden </span> Jan 96 IPv6 Testing Address Allocation |
| 58 |
|
| 59 |
This document describes an allocation plan for IPv6 addresses to be used |
| 60 |
in testing IPv6 prototype software. This document specifies an |
| 61 |
Experimental protocol for the Internet community. |
| 62 |
|
| 63 |
|
| 64 |
<span class="h2"><a class="selflink" id="section-1896" href="#section-1896">1896</a> Resnick </span> Feb 96 The text/enriched MIME Content-type |
| 65 |
|
| 66 |
This document defines one particular type of MIME data, the |
| 67 |
text/enriched MIME type. This memo provides information for the |
| 68 |
Internet community. This memo does not specify an Internet standard of |
| 69 |
any kind. |
| 70 |
|
| 71 |
|
| 72 |
<span class="h2"><a class="selflink" id="section-1895" href="#section-1895">1895</a> Levinson </span> Feb 96 The Application/CALS-1840 Content-type |
| 73 |
|
| 74 |
This memorandum provides guidelines for using the United States |
| 75 |
Department of Defense Military Standard MIL-STD-1840, "Automated |
| 76 |
Interchange of Technical Information," with the Internet electronic mail |
| 77 |
standards, <a href="./rfc822">RFC 822</a> and <a href="./rfc1521">RFC 1521</a>. This memo provides information for the |
| 78 |
Internet community. This memo does not specify an Internet standard of |
| 79 |
any kind. |
| 80 |
|
| 81 |
|
| 82 |
<span class="h2"><a class="selflink" id="section-1894" href="#section-1894">1894</a> Moore </span> Jan 96 An Extensible Message Format for |
| 83 |
Delivery Status Notifications |
| 84 |
|
| 85 |
This memo defines a MIME content-type that may be used by a message |
| 86 |
transfer agent (MTA) or electronic mail gateway to report the result of |
| 87 |
an attempt to deliver a message to one or more recipients. [STANDARDS- |
| 88 |
TRACK] |
| 89 |
|
| 90 |
|
| 91 |
<span class="h2"><a class="selflink" id="section-1893" href="#section-1893">1893</a> Vaudreuil </span> Jan 96 Enhanced Mail System Status Codes |
| 92 |
|
| 93 |
There currently is not a standard mechanism for the reporting of mail |
| 94 |
system errors except for the limited set offered by SMTP and the system |
| 95 |
specific text descriptions sent in mail messages. There is a pressing |
| 96 |
need for a rich machine readable status code for use in delivery status |
| 97 |
notifications [DSN]. This document proposes a new set of status codes |
| 98 |
for this purpose. [STANDARDS-TRACK] |
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Elliott Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1892" href="#section-1892">1892</a> Vaudreuil </span> Jan 96 The Multipart/Report Content Type |
| 114 |
for the Reporting of Mail System |
| 115 |
Administrative Messages |
| 116 |
|
| 117 |
The Multipart/Report MIME content-type is a general "family" or |
| 118 |
"container" type for electronic mail reports of any kind. Although this |
| 119 |
memo defines only the use of the Multipart/Report content-type with |
| 120 |
respect to delivery status reports, mail processing programs will |
| 121 |
benefit if a single content-type is used to for all kinds of reports. |
| 122 |
[STANDARDS-TRACK] |
| 123 |
|
| 124 |
|
| 125 |
<span class="h2"><a class="selflink" id="section-1891" href="#section-1891">1891</a> Moore </span> Jan 96 SMTP Service Extension for Delivery |
| 126 |
Status Notifications |
| 127 |
|
| 128 |
This memo defines an extension to the SMTP service, which allows an SMTP |
| 129 |
client to specify (a) that delivery status notifications (DSNs) should |
| 130 |
be generated under certain conditions, (b) whether such notifications |
| 131 |
should return the contents of the message, and (c) additional |
| 132 |
information, to be returned with a DSN, that allows the sender to |
| 133 |
identify both the recipient(s) for which the DSN was issued, and the |
| 134 |
transaction in which the original message was sent. [STANDARDS-TRACK] |
| 135 |
|
| 136 |
|
| 137 |
<span class="h2"><a class="selflink" id="section-1890" href="#section-1890">1890</a> A.V.T.W.G. </span> Jan 96 RTP Profile for Audio and Video |
| 138 |
Conferences with Minimal Control |
| 139 |
|
| 140 |
This memo describes a profile for the use of the real-time transport |
| 141 |
protocol (RTP), version 2, and the associated control protocol, RTCP, |
| 142 |
within audio and video multiparticipant conferences with minimal |
| 143 |
control. [STANDARDS-TRACK] |
| 144 |
|
| 145 |
|
| 146 |
<span class="h2"><a class="selflink" id="section-1889" href="#section-1889">1889</a> A.V.T.W.G. </span> Jan 96 RTP: A Transport Protocol for |
| 147 |
Real-Time Applications |
| 148 |
|
| 149 |
This memorandum describes RTP, the real-time transport protocol. RTP |
| 150 |
provides end-to-end network transport functions suitable for |
| 151 |
applications transmitting real-time data, such as audio, video or |
| 152 |
simulation data, over multicast or unicast network services. |
| 153 |
[STANDARDS-TRACK] |
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Elliott Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1888" href="#section-1888">1888</a> Bound </span> Aug 96 OSI NSAPs and IPv6 |
| 170 |
|
| 171 |
This document recommends that network implementors who have planned or |
| 172 |
deployed an OSI NSAP addressing plan, and who wish to deploy or |
| 173 |
transition to IPv6, should redesign a native IPv6 addressing plan to |
| 174 |
meet their needs. This memo defines an Experimental Protocol for the |
| 175 |
Internet community. |
| 176 |
|
| 177 |
|
| 178 |
<span class="h2"><a class="selflink" id="section-1887" href="#section-1887">1887</a> Rekhter </span> Dec 95 An Architecture for IPv6 Unicast |
| 179 |
Address Allocation |
| 180 |
|
| 181 |
This document provides an architecture for allocating IPv6 [1] unicast |
| 182 |
addresses in the Internet. This document provides information for the |
| 183 |
Internet community. This memo does not specify an Internet standard of |
| 184 |
any kind. |
| 185 |
|
| 186 |
|
| 187 |
<span class="h2"><a class="selflink" id="section-1886" href="#section-1886">1886</a> Thomson </span> Dec 95 DNS Extensions to support IP version 6 |
| 188 |
|
| 189 |
This document defines the changes that need to be made to the Domain |
| 190 |
Name System to support hosts running IP version 6 (IPv6). [STANDARDS- |
| 191 |
TRACK] |
| 192 |
|
| 193 |
|
| 194 |
<span class="h2"><a class="selflink" id="section-1885" href="#section-1885">1885</a> Conta </span> Dec 95 Internet Control Message Protocol |
| 195 |
(ICMPv6) for the Internet Protocol |
| 196 |
Version 6 (IPv6) |
| 197 |
|
| 198 |
This document specifies a set of Internet Control Message Protocol |
| 199 |
(ICMP) messages for use with version 6 of the Internet Protocol (IPv6). |
| 200 |
[STANDARDS-TRACK] |
| 201 |
|
| 202 |
|
| 203 |
<span class="h2"><a class="selflink" id="section-1884" href="#section-1884">1884</a> Hinden </span> Dec 95 IP Version 6 Addressing Architecture |
| 204 |
|
| 205 |
This specification defines the addressing architecture of the IP Version |
| 206 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> protocol [IPV6]. </span>[STANDARDS-TRACK] |
| 207 |
|
| 208 |
|
| 209 |
<span class="h2"><a class="selflink" id="section-1883" href="#section-1883">1883</a> Deering </span> Dec 95 Internet Protocol, Version 6 (IPv6) |
| 210 |
Specification |
| 211 |
|
| 212 |
This document specifies version 6 of the Internet Protocol (IPv6), also |
| 213 |
sometimes referred to as IP Next Generation or IPng. [STANDARDS-TRACK] |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Elliott Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-1882" href="#section-1882">1882</a> Hancock </span> Dec 95 The 12-Days of Technology Before |
| 226 |
Christmas |
| 227 |
|
| 228 |
This memo provides information for the Internet community. This memo |
| 229 |
does not specify an Internet standard of any kind. |
| 230 |
|
| 231 |
|
| 232 |
<span class="h2"><a class="selflink" id="section-1881" href="#section-1881">1881</a> IAB & IESG </span> Dec 95 IPv6 Address Allocation Management |
| 233 |
|
| 234 |
The IPv6 address space will be managed by the IANA for the good of the |
| 235 |
Internet community, with advice from the IAB and the IESG, by delegation |
| 236 |
to the regional registries. This memo provides information for the |
| 237 |
Internet community. This memo does not specify an Internet standard of |
| 238 |
any kind. |
| 239 |
|
| 240 |
|
| 241 |
<span class="h2"><a class="selflink" id="section-1880" href="#section-1880">1880</a> I.A.B. </span> Nov 95 INTERNET OFFICIAL PROTOCOL STANDARDS |
| 242 |
|
| 243 |
This memo describes the state of standardization of protocols used in |
| 244 |
the Internet as determined by the Internet Architecture Board (IAB). |
| 245 |
[STANDARDS-TRACK] |
| 246 |
|
| 247 |
|
| 248 |
<span class="h2"><a class="selflink" id="section-1879" href="#section-1879">1879</a> Manning </span> Jan 96 Class A Subnet Experiment |
| 249 |
Results and Recommendations |
| 250 |
|
| 251 |
This memo documents some experiences with the <a href="./rfc1797">RFC 1797</a> [1] subnet A |
| 252 |
experiment (performed by the Net39 Test Group (see credits)) and |
| 253 |
provides a number of recommendations on future direction for both the |
| 254 |
Internet Registries and the Operations community. This memo provides |
| 255 |
information for the Internet community. This memo does not specify an |
| 256 |
Internet standard of any kind. |
| 257 |
|
| 258 |
|
| 259 |
<span class="h2"><a class="selflink" id="section-1878" href="#section-1878">1878</a> Pummill </span> Dec 95 Variable Length Subnet Table For IPv4 |
| 260 |
|
| 261 |
This memo clarifies issues surrounding subnetting IP networks by |
| 262 |
providing a standard subnet table. This memo provides information for |
| 263 |
the Internet community. This memo does not specify an Internet standard |
| 264 |
of any kind. |
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Elliott Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-1877" href="#section-1877">1877</a> Cobb </span> Dec 95 PPP Internet Protocol Control Protocol |
| 282 |
Extensions for Name Server Addresses |
| 283 |
|
| 284 |
This document extends the NCP for establishing and configuring the |
| 285 |
Internet Protocol over PPP [2], defining the negotiation of primary and |
| 286 |
secondary Domain Name System (DNS) [3] and NetBIOS Name Server (NBNS) |
| 287 |
[4] addresses. This memo provides information for the Internet |
| 288 |
community. This memo does not specify an Internet standard of any kind. |
| 289 |
|
| 290 |
|
| 291 |
<span class="h2"><a class="selflink" id="section-1876" href="#section-1876">1876</a> Davis </span> Jan 96 A Means for Expressing Location |
| 292 |
Information in the Domain Name System |
| 293 |
|
| 294 |
This memo defines a new DNS RR type for experimental purposes. This RFC |
| 295 |
describes a mechanism to allow the DNS to carry location information |
| 296 |
about hosts, networks, and subnets. This memo defines an Experimental |
| 297 |
Protocol for the Internet community. |
| 298 |
|
| 299 |
|
| 300 |
<span class="h2"><a class="selflink" id="section-1875" href="#section-1875">1875</a> Berge </span> Dec 95 UNINETT PCA Policy Statements |
| 301 |
|
| 302 |
This document provides information about policy statements submitted by |
| 303 |
the UNINETT Policy Certification Authority (UNINETT PCA). This memo |
| 304 |
provides information for the Internet community. This memo does not |
| 305 |
specify an Internet standard of any kind. |
| 306 |
|
| 307 |
|
| 308 |
<span class="h2"><a class="selflink" id="section-1874" href="#section-1874">1874</a> Levinson </span> Dec 95 SGML Media Types |
| 309 |
|
| 310 |
This document proposes new media sub-types of Text/SGML and |
| 311 |
Application/SGML. This memo defines an Experimental Protocol for the |
| 312 |
Internet community. |
| 313 |
|
| 314 |
|
| 315 |
<span class="h2"><a class="selflink" id="section-1873" href="#section-1873">1873</a> Levinson </span> Dec 95 Message/External-Body Content-ID |
| 316 |
Access Type |
| 317 |
|
| 318 |
The existing MIME Content-Type Message/External-Body access-types allow |
| 319 |
a MIME entity (body-part) to refer to an object that is not in the |
| 320 |
message by specifying how to access that object. The Content-ID access |
| 321 |
method described in this document provides the capability to refer to an |
| 322 |
object within the message. This memo defines an Experimental Protocol |
| 323 |
for the Internet community. |
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Elliott Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-1872" href="#section-1872">1872</a> Levinson </span> Dec 95 The MIME Multipart/Related Content-type |
| 338 |
|
| 339 |
The Multipart/Related content-type provides a common mechanism for |
| 340 |
representing objects that are aggregates of related MIME body parts. |
| 341 |
This document defines the Multipart/Related content-type and provides |
| 342 |
examples of its use. This memo defines an Experimental Protocol for the |
| 343 |
Internet community. |
| 344 |
|
| 345 |
|
| 346 |
<span class="h2"><a class="selflink" id="section-1871" href="#section-1871">1871</a> Postel </span> Nov 95 Addendum to <a href="./rfc1602">RFC 1602</a> -- |
| 347 |
Variance Procedure |
| 348 |
|
| 349 |
This document describes a modification to the IETF procedures to allow |
| 350 |
an escape from a situation where the existing procedures are not working |
| 351 |
or do not seem to apply. This document specifies an Internet Best |
| 352 |
Current Practices for the Internet Community, and requests discussion |
| 353 |
and suggestions for improvements. |
| 354 |
|
| 355 |
|
| 356 |
<span class="h2"><a class="selflink" id="section-1870" href="#section-1870">1870</a> Klensin </span> Nov 95 SMTP Service Extension for Message |
| 357 |
Size Declaration |
| 358 |
|
| 359 |
This memo defines an extension to the SMTP service whereby an SMTP |
| 360 |
client and server may interact to give the server an opportunity to |
| 361 |
decline to accept a message (perhaps temporarily) based on the client's |
| 362 |
estimate of the message size. [STANDARDS-TRACK] |
| 363 |
|
| 364 |
|
| 365 |
<span class="h2"><a class="selflink" id="section-1869" href="#section-1869">1869</a> Klensin </span> Nov 95 SMTP Service Extensions |
| 366 |
|
| 367 |
This memo defines a framework for extending the SMTP service by defining |
| 368 |
a means whereby a server SMTP can inform a client SMTP as to the service |
| 369 |
extensions it supports. [STANDARDS-TRACK] |
| 370 |
|
| 371 |
|
| 372 |
<span class="h2"><a class="selflink" id="section-1868" href="#section-1868">1868</a> Malkin </span> Nov 95 ARP Extension - UNARP |
| 373 |
|
| 374 |
This document specifies a trivial modification to the ARP mechanism, not |
| 375 |
the packet format, which allows a node to announce that it is leaving |
| 376 |
the network and that all other nodes should modify their ARP tables |
| 377 |
accordingly. This memo defines an Experimental Protocol for the |
| 378 |
Internet community. |
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Elliott Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-1867" href="#section-1867">1867</a> Nebel </span> Nov 95 Form-based File Upload in HTML |
| 394 |
|
| 395 |
Since file-upload is a feature that will benefit many applications, this |
| 396 |
proposes an extension to HTML to allow information providers to express |
| 397 |
file upload requests uniformly, and a MIME compatible representation for |
| 398 |
file upload responses. This memo defines an Experimental Protocol for |
| 399 |
the Internet community. |
| 400 |
|
| 401 |
|
| 402 |
<span class="h2"><a class="selflink" id="section-1866" href="#section-1866">1866</a> Berners-Lee </span>Nov 95 Hypertext Markup Language - 2.0 |
| 403 |
|
| 404 |
This document defines a HTML 2.0 (to distinguish it from the previous |
| 405 |
informal specifications). [STANDARDS-TRACK] |
| 406 |
|
| 407 |
|
| 408 |
<span class="h2"><a class="selflink" id="section-1865" href="#section-1865">1865</a> Houser </span> Jan 96 EDI Meets the Internet: Frequently Asked |
| 409 |
Questions about Electronic Data |
| 410 |
Interchange (EDI) on the Internet |
| 411 |
|
| 412 |
This memo is targeted towards the EDI community that is unfamiliar with |
| 413 |
the Internet, including EDI software developers, users, and service |
| 414 |
providers. The memo introduces the Internet and assumes a basic |
| 415 |
knowledge of EDI. This memo provides information for the Internet |
| 416 |
community. This memo does not specify an Internet standard of any kind. |
| 417 |
|
| 418 |
|
| 419 |
<span class="h2"><a class="selflink" id="section-1864" href="#section-1864">1864</a> Myers </span> Oct 95 The Content-MD5 Header Field |
| 420 |
|
| 421 |
This memo specifies an optional header field, Content-MD5, for use with |
| 422 |
MIME-conformant messages. [STANDARDS-TRACK] |
| 423 |
|
| 424 |
|
| 425 |
<span class="h2"><a class="selflink" id="section-1863" href="#section-1863">1863</a> Haskin </span> Oct 95 A BGP/IDRP Route Server alternative to a |
| 426 |
full mesh routing |
| 427 |
|
| 428 |
This document describes the use and detailed design of Route Servers for |
| 429 |
dissemination of routing information among BGP/IDRP speaking routers. |
| 430 |
This memo defines an Experimental Protocol for the Internet community. |
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Elliott Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-1862" href="#section-1862">1862</a> McCahill </span> Nov 95 Report of the IAB Workshop on Internet |
| 450 |
Information Infrastructure, |
| 451 |
October 12-14, 1994 |
| 452 |
|
| 453 |
This document is a report on an Internet architecture workshop, |
| 454 |
initiated by the IAB and held at MCI on October 12-14, 1994. This |
| 455 |
workshop generally focused on aspects of the information infrastructure |
| 456 |
on the Internet. This memo provides information for the Internet |
| 457 |
community. This memo does not specify an Internet standard of any kind. |
| 458 |
|
| 459 |
|
| 460 |
<span class="h2"><a class="selflink" id="section-1861" href="#section-1861">1861</a> Gwinn </span> Oct 95 Simple Network Paging Protocol - |
| 461 |
Version 3 - Two-Way Enhanced |
| 462 |
|
| 463 |
This RFC suggests a simple way for delivering wireless messages, both |
| 464 |
one and two-way, to appropriate receiving devices. This memo provides |
| 465 |
information for the Internet community. This memo does not specify an |
| 466 |
Internet standard of any kind. |
| 467 |
|
| 468 |
|
| 469 |
<span class="h2"><a class="selflink" id="section-1860" href="#section-1860">1860</a> Pummill </span> Oct 95 Variable Length Subnet Table For IPv4 |
| 470 |
|
| 471 |
This document itemizes the potential values for IPv4 subnets. This memo |
| 472 |
provides information for the Internet community. This memo does not |
| 473 |
specify an Internet standard of any kind. |
| 474 |
|
| 475 |
|
| 476 |
<span class="h2"><a class="selflink" id="section-1859" href="#section-1859">1859</a> Pouffary </span> Oct 95 ISO Transport Class 2 Non-use of |
| 477 |
Explicit Flow Control over |
| 478 |
TCP <a href="./rfc1006">RFC1006</a> extension |
| 479 |
|
| 480 |
This document is an extension to STD35, <a href="./rfc1006">RFC1006</a>, a standard for the |
| 481 |
Internet community. The document does not duplicate the protocol |
| 482 |
definitions contained in <a href="./rfc1006">RFC1006</a> and in International Standard ISO 8073. |
| 483 |
It supplements that information with the description of how to implement |
| 484 |
ISO Transport Class 2 Non-use of Explicit Flow Control on top of TCP. |
| 485 |
This memo provides information for the Internet community. This memo |
| 486 |
does not specify an Internet standard of any kind. |
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Elliott Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="section-1858" href="#section-1858">1858</a> Ziemba </span> Oct 95 Security Considerations for |
| 506 |
IP Fragment Filtering |
| 507 |
|
| 508 |
IP fragmentation can be used to disguise TCP packets from IP filters |
| 509 |
used in routers and hosts. This document describes two methods of attack |
| 510 |
as well as remedies to prevent them. This memo provides information for |
| 511 |
the Internet community. This memo does not specify an Internet standard |
| 512 |
of any kind. |
| 513 |
|
| 514 |
|
| 515 |
<span class="h2"><a class="selflink" id="section-1857" href="#section-1857">1857</a> Lambert </span> Oct 95 A Model for Common Operational |
| 516 |
Statistics |
| 517 |
|
| 518 |
This memo describes a model for operational statistics in the Internet. |
| 519 |
This memo provides information for the Internet community. This memo |
| 520 |
does not specify an Internet standard of any kind. |
| 521 |
|
| 522 |
|
| 523 |
<span class="h2"><a class="selflink" id="section-1856" href="#section-1856">1856</a> Clark </span> Shpt 95 The Opstat Client-Server Model for |
| 524 |
Statistics Retrieval |
| 525 |
|
| 526 |
This document defines a model and protocol for a set of tools which |
| 527 |
could be used by NSPs and Network Operation Centers (NOCs) to share data |
| 528 |
among themselves and with customers. This memo provides information for |
| 529 |
the Internet community. This memo does not specify an Internet standard |
| 530 |
of any kind. |
| 531 |
|
| 532 |
|
| 533 |
<span class="h2"><a class="selflink" id="section-1855" href="#section-1855">1855</a> Hambridge </span> Oct 95 Netiquette Guidelines |
| 534 |
|
| 535 |
This document provides a minimum set of guidelines for Network Etiquette |
| 536 |
(Netiquette) which organizations may take and adapt for their own use. |
| 537 |
This memo provides information for the Internet community. This memo |
| 538 |
does not specify an Internet standard of any kind. |
| 539 |
|
| 540 |
|
| 541 |
<span class="h2"><a class="selflink" id="section-1854" href="#section-1854">1854</a> Freed </span> Oct 95 SMTP Service Extension for |
| 542 |
Command Pipelining |
| 543 |
|
| 544 |
This memo defines an extension to the SMTP service whereby a server can |
| 545 |
indicate the extent of its ability to accept multiple commands in a |
| 546 |
single TCP send operation. [STANDARDS-TRACK] |
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Elliott Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h2"><a class="selflink" id="section-1853" href="#section-1853">1853</a> Simpson </span> Oct 95 IP in IP Tunneling |
| 562 |
|
| 563 |
This document discusses implementation techniques for using IP |
| 564 |
Protocol/Payload number 4 Encapsulation for tunneling with IP Security |
| 565 |
and other protocols. This memo provides information for the Internet |
| 566 |
community. It does not specify an Internet standard. |
| 567 |
|
| 568 |
|
| 569 |
<span class="h2"><a class="selflink" id="section-1852" href="#section-1852">1852</a> Metzger </span> Spt 95 IP Authentication using Keyed SHA |
| 570 |
|
| 571 |
This document describes the use of keyed SHA with the IP Authentication |
| 572 |
Header. This document defines an Experimental Protocol for the Internet |
| 573 |
community. |
| 574 |
|
| 575 |
|
| 576 |
<span class="h2"><a class="selflink" id="section-1851" href="#section-1851">1851</a> Karn </span> Spt 95 The ESP Triple DES Transform |
| 577 |
|
| 578 |
This document describes the Triple DES-CBC security transform for the IP |
| 579 |
Encapsulating Security Payload (ESP). This document defines an |
| 580 |
Experimental Protocol for the Internet community. |
| 581 |
|
| 582 |
|
| 583 |
<span class="h2"><a class="selflink" id="section-1850" href="#section-1850">1850</a> Baker </span> Nov 95 OSPF Version 2 Management |
| 584 |
Information Base |
| 585 |
|
| 586 |
This memo defines a portion of the Management Information Base (MIB) for |
| 587 |
use with network management protocols in TCP/IP-based internets. In |
| 588 |
particular, it defines objects for managing the Open Shortest Path First |
| 589 |
Routing Protocol. [STANDARDS-TRACK] |
| 590 |
|
| 591 |
|
| 592 |
<span class="h2"><a class="selflink" id="section-1849" href="#section-1849">1849</a> Never Issued.</span> |
| 593 |
|
| 594 |
|
| 595 |
<span class="h2"><a class="selflink" id="section-1848" href="#section-1848">1848</a> Crocker </span> Oct 95 MIME Object Security Services |
| 596 |
|
| 597 |
This document defines MIME Object Security Services (MOSS), a protocol |
| 598 |
that uses the multipart/signed and multipart/encrypted framework [7] to |
| 599 |
apply digital signature and encryption services to MIME objects. |
| 600 |
[STANDARDS-TRACK] |
| 601 |
|
| 602 |
|
| 603 |
<span class="h2"><a class="selflink" id="section-1847" href="#section-1847">1847</a> Galvin </span> Oct 95 Security Multiparts for MIME: |
| 604 |
Multipart/Signed and Multipart/Encrypted |
| 605 |
|
| 606 |
This document defines a framework within which security services may be |
| 607 |
applied to MIME body parts. [STANDARDS-TRACK] |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Elliott Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h2"><a class="selflink" id="section-1846" href="#section-1846">1846</a> Durand </span> Spt 95 SMTP 521 Reply Code |
| 618 |
|
| 619 |
This memo defines a new Simple Mail Transfer Protocol (SMTP) [1] reply |
| 620 |
code, 521, which one may use to indicate that an Internet host does not |
| 621 |
accept incoming mail. This memo defines an Experimental Protocol for |
| 622 |
the Internet community. |
| 623 |
|
| 624 |
|
| 625 |
<span class="h2"><a class="selflink" id="section-1845" href="#section-1845">1845</a> Crocker </span> Spt 95 SMTP Service Extension |
| 626 |
for Checkpoint/Restart |
| 627 |
|
| 628 |
This memo defines an extension to the SMTP service whereby an |
| 629 |
interrupted SMTP transaction can be restarted at a later time without |
| 630 |
having to repeat all of the commands and message content sent prior to |
| 631 |
the interruption. This memo defines an Experimental Protocol for the |
| 632 |
Internet community. |
| 633 |
|
| 634 |
|
| 635 |
<span class="h2"><a class="selflink" id="section-1844" href="#section-1844">1844</a> Huizer </span> Aug 95 Multimedia E-mail (MIME) User |
| 636 |
Agent checklist |
| 637 |
|
| 638 |
This document presents a checklist to facilitate evaluation of MIME |
| 639 |
capable User Agents. This memo provides information for the Internet |
| 640 |
community. This memo does not specify an Internet standard of any kind. |
| 641 |
|
| 642 |
|
| 643 |
<span class="h2"><a class="selflink" id="section-1843" href="#section-1843">1843</a> Lee </span> Aug 95 HZ - A Data Format for Exchanging Files |
| 644 |
of Arbitrarily Mixed Chinese and ASCII |
| 645 |
characters |
| 646 |
|
| 647 |
The content of this memo is identical to an article of the same title |
| 648 |
written by the author on September 4, 1989. This memo provides |
| 649 |
information for the Internet community. This memo does not specify an |
| 650 |
Internet standard of any kind. |
| 651 |
|
| 652 |
|
| 653 |
<span class="h2"><a class="selflink" id="section-1842" href="#section-1842">1842</a> Wei </span> Aug 95 ASCII Printable Characters-Based Chinese |
| 654 |
Character Encoding for Internet Messages |
| 655 |
|
| 656 |
This document describes the encoding used in electronic mail [<a href="./rfc822">RFC822</a>] |
| 657 |
and network news [<a href="./rfc1036">RFC1036</a>] messages over the Internet. This memo |
| 658 |
provides information for the Internet community. This memo does not |
| 659 |
specify an Internet standard of any kind. |
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Elliott Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h2"><a class="selflink" id="section-1841" href="#section-1841">1841</a> Chapman </span> Spt 95 PPP Network Control Protocol for |
| 674 |
LAN Extension |
| 675 |
|
| 676 |
Telecommunications infrastructure is improving to offer higher bandwidth |
| 677 |
connections at lower cost. Access to the network is changing from modems |
| 678 |
to more intelligent devices. This informational RFC discusses a PPP |
| 679 |
Network Control Protocol for one such intelligent device. The protocol |
| 680 |
is the LAN extension interface protocol. This memo provides information |
| 681 |
for the Internet community. This memo does not specify an Internet |
| 682 |
standard of any kind. |
| 683 |
|
| 684 |
|
| 685 |
<span class="h2"><a class="selflink" id="section-1840" href="#section-1840">1840</a> Never Issued.</span> |
| 686 |
|
| 687 |
|
| 688 |
<span class="h2"><a class="selflink" id="section-1839" href="#section-1839">1839</a> Never Issued.</span> |
| 689 |
|
| 690 |
|
| 691 |
<span class="h2"><a class="selflink" id="section-1838" href="#section-1838">1838</a> Kille </span> Aug 95 Use of the X.500 Directory to support |
| 692 |
mapping between X.400 and <a href="./rfc822">RFC 822</a> |
| 693 |
Addresses |
| 694 |
|
| 695 |
This document defines how to use directory to support the mapping |
| 696 |
between X.400 O/R Addresses and mailboxes defined in <a href="./rfc1327">RFC 1327</a> [2]. This |
| 697 |
memo defines an Experimental Protocol for the Internet community. |
| 698 |
|
| 699 |
|
| 700 |
<span class="h2"><a class="selflink" id="section-1837" href="#section-1837">1837</a> Kille </span> Aug 95 Representing Tables and Subtrees in the |
| 701 |
X.500 Directory |
| 702 |
|
| 703 |
This document defines techniques for representing two types of |
| 704 |
information mapping in the OSI Directory. This memo defines an |
| 705 |
Experimental Protocol for the Internet community. |
| 706 |
|
| 707 |
|
| 708 |
<span class="h2"><a class="selflink" id="section-1836" href="#section-1836">1836</a> Kille </span> Aug 95 Representing the O/R Address hierarchy |
| 709 |
in the X.500 Directory Information Tree |
| 710 |
|
| 711 |
This document defines a representation of the O/R Address hierarchy in |
| 712 |
the Directory Information Tree [6, 1]. This memo defines an |
| 713 |
Experimental Protocol for the Internet community. |
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Elliott Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h2"><a class="selflink" id="section-1835" href="#section-1835">1835</a> Deutsch </span> Aug 95 Architecture of the WHOIS++ service |
| 730 |
|
| 731 |
This document describes WHOIS++, an extension to the trivial WHOIS |
| 732 |
service described in <a href="./rfc954">RFC 954</a> to permit WHOIS-like servers to make |
| 733 |
available more structured information to the Internet. [STANDARDS- |
| 734 |
TRACK] |
| 735 |
|
| 736 |
|
| 737 |
<span class="h2"><a class="selflink" id="section-1834" href="#section-1834">1834</a> Gargano </span> Aug 95 Whois and Network Information |
| 738 |
Lookup Service Whois++ |
| 739 |
|
| 740 |
This memo describes new features for WHOIS. This memo provides |
| 741 |
information for the Internet community. This memo does not specify an |
| 742 |
Internet standard of any kind. |
| 743 |
|
| 744 |
|
| 745 |
<span class="h2"><a class="selflink" id="section-1833" href="#section-1833">1833</a> Srinivasan </span> Aug 95 Binding Protocols for ONC RPC Version 2 |
| 746 |
|
| 747 |
This document describes the binding protocols used in conjunction with |
| 748 |
the ONC Remote Procedure Call (ONC RPC Version 2) protocols. |
| 749 |
[STANDARDS-TRACK] |
| 750 |
|
| 751 |
|
| 752 |
<span class="h2"><a class="selflink" id="section-1832" href="#section-1832">1832</a> Srinivasan </span> Aug 95 XDR: External Data Representation |
| 753 |
Standard |
| 754 |
|
| 755 |
This document describes the External Data Representation Standard (XDR) |
| 756 |
protocol as it is currently deployed and accepted. [STANDARDS-TRACK] |
| 757 |
|
| 758 |
|
| 759 |
<span class="h2"><a class="selflink" id="section-1831" href="#section-1831">1831</a> Srinivasan </span> Aug 95 RPC: Remote Procedure Call Protocol |
| 760 |
Specification Version 2 |
| 761 |
|
| 762 |
This document describes the ONC Remote Procedure Call (ONC RPC Version |
| 763 |
2) protocol as it is currently deployed and accepted. [STANDARDS-TRACK] |
| 764 |
|
| 765 |
|
| 766 |
<span class="h2"><a class="selflink" id="section-1830" href="#section-1830">1830</a> Vaudreuil </span> Aug 95 SMTP Service Extensions for Transmission |
| 767 |
of Large and Binary MIME Messages |
| 768 |
|
| 769 |
This memo defines two extensions to the SMTP service. The first service |
| 770 |
enables a SMTP client and server to negotiate the use of an alternate |
| 771 |
DATA command "BDAT" for efficiently sending large MIME messages. The |
| 772 |
second extension takes advantage of the BDAT command to permit the |
| 773 |
negotiated sending of unencoded binary data. This memo defines an |
| 774 |
Experimental Protocol for the Internet community. |
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Elliott Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h2"><a class="selflink" id="section-1829" href="#section-1829">1829</a> Karn </span> Aug 95 The ESP DES-CBC Transform |
| 786 |
|
| 787 |
This document describes the DES-CBC security transform for the IP |
| 788 |
Encapsulating Security Payload (ESP). [STANDARDS-TRACK] |
| 789 |
|
| 790 |
|
| 791 |
<span class="h2"><a class="selflink" id="section-1828" href="#section-1828">1828</a> Metzger </span> Aug 95 IP Authentication using Keyed MD5 |
| 792 |
|
| 793 |
This document describes the use of keyed MD5 with the IP Authentication |
| 794 |
Header. [STANDARDS-TRACK] |
| 795 |
|
| 796 |
|
| 797 |
<span class="h2"><a class="selflink" id="section-1827" href="#section-1827">1827</a> Atkinson </span> Aug 95 IP Encapsulating Security Payload (ESP) |
| 798 |
|
| 799 |
This document describes the IP Encapsulating Security Payload (ESP). |
| 800 |
ESP is a mechanism for providing integrity and confidentiality to IP |
| 801 |
datagrams. [STANDARDS-TRACK] |
| 802 |
|
| 803 |
|
| 804 |
<span class="h2"><a class="selflink" id="section-1826" href="#section-1826">1826</a> Atkinson </span> Aug 95 IP Authentication Header |
| 805 |
|
| 806 |
This document describes a mechanism for providing cryptographic |
| 807 |
authentication for IPv4 and IPv6 datagrams. [STANDARDS-TRACK] |
| 808 |
|
| 809 |
|
| 810 |
<span class="h2"><a class="selflink" id="section-1825" href="#section-1825">1825</a> Atkinson </span> Aug 95 Security Architecture for the Internet |
| 811 |
Protocol |
| 812 |
|
| 813 |
This memo describes the security mechanisms for IP version 4 (IPv4) and |
| 814 |
IP version 6 (IPv6) and the services that they provide. [STANDARDS- |
| 815 |
TRACK] |
| 816 |
|
| 817 |
|
| 818 |
<span class="h2"><a class="selflink" id="section-1824" href="#section-1824">1824</a> Danisch </span> Aug 95 The Exponential Security System TESS: |
| 819 |
An Identity-Based Cryptographic Protocol |
| 820 |
for Authenticated Key-Exchange |
| 821 |
(E.I.S.S.-Report 1995/4) |
| 822 |
|
| 823 |
This informational RFC describes the basic mechanisms and functions of |
| 824 |
an identity based system for the secure authenticated exchange of |
| 825 |
cryptographic keys, the generation of signatures, and the authentic |
| 826 |
distribution of public keys. This memo provides information for the |
| 827 |
Internet community. This memo does not specify an Internet standard of |
| 828 |
any kind. |
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Elliott Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="section-1823" href="#section-1823">1823</a> Howes </span> Aug 95 The LDAP Application Program Interface |
| 842 |
|
| 843 |
This document defines a C language application program interface to the |
| 844 |
lightweight directory access protocol (LDAP). This memo provides |
| 845 |
information for the Internet community. This memo does not specify an |
| 846 |
Internet standard of any kind. |
| 847 |
|
| 848 |
|
| 849 |
<span class="h2"><a class="selflink" id="section-1822" href="#section-1822">1822</a> Lowe </span> Aug 95 A Grant of Rights to Use a Specific IBM |
| 850 |
patent with Photuris |
| 851 |
|
| 852 |
This Request for Comments records a grant by IBM Corporation to permit |
| 853 |
the conditional free use of one of its patents. This memo provides |
| 854 |
information for the Internet community. This memo does not specify an |
| 855 |
Internet standard of any kind. |
| 856 |
|
| 857 |
|
| 858 |
<span class="h2"><a class="selflink" id="section-1821" href="#section-1821">1821</a> Borden </span> Aug 95 Integration of Real-time Services in an |
| 859 |
IP-ATM Network Architecture |
| 860 |
|
| 861 |
The purpose of this paper is to provide a clear statement of what issues |
| 862 |
need to be addressed in interfacing the IP integrated services |
| 863 |
environment with an ATM service environment so as to create a seamless |
| 864 |
interface between the two in support of end users desiring real-time |
| 865 |
networking services. This memo provides information for the Internet |
| 866 |
community. This memo does not specify an Internet standard of any kind. |
| 867 |
|
| 868 |
|
| 869 |
<span class="h2"><a class="selflink" id="section-1820" href="#section-1820">1820</a> Huizer </span> Aug 95 Multimedia E-mail (MIME) User Agent |
| 870 |
Checklist |
| 871 |
|
| 872 |
This document presents a checklist to facilitate evaluation of MIME |
| 873 |
capable User Agents. Access to a MIME test-responder, that generates |
| 874 |
test-messages is described. This memo provides information for the |
| 875 |
Internet community. This memo does not specify an Internet standard of |
| 876 |
any kind. |
| 877 |
|
| 878 |
|
| 879 |
<span class="h2"><a class="selflink" id="section-1819" href="#section-1819">1819</a> ST2 W.G. </span> Aug 95 Internet Stream Protocol Version 2 (ST2) |
| 880 |
Protocol Specification - Version ST2+ |
| 881 |
|
| 882 |
This memo contains a revised specification of the Internet STream |
| 883 |
Protocol Version 2 (ST2). This memo defines an Experimental Protocol |
| 884 |
for the Internet community. |
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Elliott Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="section-1818" href="#section-1818">1818</a> Postel </span> Aug 95 Best Current Practices |
| 898 |
|
| 899 |
This document describes a new series of documents which describe best |
| 900 |
current practices for the Internet community. Documents in this series |
| 901 |
carry the endorsement of the Internet Engineering Steering Group (IESG). |
| 902 |
|
| 903 |
|
| 904 |
<span class="h2"><a class="selflink" id="section-1817" href="#section-1817">1817</a> Rekhter </span> Aug 95 CIDR and Classful Routing |
| 905 |
|
| 906 |
This document represents the IAB's (Internet Architecture Board) |
| 907 |
evaluation of the current and near term implications of CIDR on |
| 908 |
organizations that use Classful routing technology. This memo provides |
| 909 |
information for the Internet community. This memo does not specify an |
| 910 |
Internet standard of any kind. |
| 911 |
|
| 912 |
|
| 913 |
<span class="h2"><a class="selflink" id="section-1816" href="#section-1816">1816</a> F.N.C. </span> Aug 95 U.S. Government Internet Domain Names |
| 914 |
|
| 915 |
This memo provides an update and clarification to <a href="./rfc1811">RFC 1811</a>. This |
| 916 |
document describes the registration policies for the top-level domain |
| 917 |
".GOV". This memo provides information for the Internet community. |
| 918 |
This memo does not specify an Internet standard of any kind. |
| 919 |
|
| 920 |
|
| 921 |
<span class="h2"><a class="selflink" id="section-1815" href="#section-1815">1815</a> Ohta </span> Jul 95 Character Sets ISO-10646 and |
| 922 |
ISO-10646-J-1 |
| 923 |
|
| 924 |
For the practical use of ISO 10646, a lot of external profiling such as |
| 925 |
restriction of characters, restriction of combination of characters and |
| 926 |
addition of language information is necessary. This memo provides |
| 927 |
information on such profiling, along with charset names to each profiled |
| 928 |
instance. This memo provides information for the Internet community. |
| 929 |
This memo does not specify an Internet standard of any kind. |
| 930 |
|
| 931 |
|
| 932 |
<span class="h2"><a class="selflink" id="section-1814" href="#section-1814">1814</a> Gerich </span> Jun 95 Unique Addresses are Good |
| 933 |
|
| 934 |
The IAB suggests that while <a href="./rfc1597">RFC 1597</a> establishes reserved IP address |
| 935 |
space for the use of private networks which are isolated and will remain |
| 936 |
isolated from the Internet, any enterprise which anticipates external |
| 937 |
connectivity to the Internet should apply for a globally unique address |
| 938 |
from an Internet registry or service provider. This memo provides |
| 939 |
information for the Internet community. This memo does not specify an |
| 940 |
Internet standard of any kind. |
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Elliott Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h2"><a class="selflink" id="section-1813" href="#section-1813">1813</a> Callaghan </span> Jun 95 NFS Version 3 Protocol Specification |
| 954 |
|
| 955 |
This paper describes the NFS version 3 protocol. This paper is provided |
| 956 |
so that people can write compatible implementations. This memo provides |
| 957 |
information for the Internet community. This memo does not specify an |
| 958 |
Internet standard of any kind. |
| 959 |
|
| 960 |
|
| 961 |
<span class="h2"><a class="selflink" id="section-1812" href="#section-1812">1812</a> Baker </span> Jun 95 Requirements for IP Version 4 Routers |
| 962 |
|
| 963 |
This memo defines and discusses requirements for devices that perform |
| 964 |
the network layer forwarding function of the Internet protocol suite. |
| 965 |
[STANDARDS-TRACK] |
| 966 |
|
| 967 |
|
| 968 |
<span class="h2"><a class="selflink" id="section-1811" href="#section-1811">1811</a> F.N.C. </span> Jun 95 U.S. Government Internet Domain Names |
| 969 |
|
| 970 |
This document describes the registration policies for the top-level |
| 971 |
domain ".GOV". This memo provides information for the Internet |
| 972 |
community. This memo does not specify an Internet standard of any kind. |
| 973 |
|
| 974 |
|
| 975 |
<span class="h2"><a class="selflink" id="section-1810" href="#section-1810">1810</a> Touch </span> Jun 95 Report on MD5 Performance |
| 976 |
|
| 977 |
This RFC addresses how fast MD5 can be implemented in software and |
| 978 |
hardware, and whether it supports currently available IP bandwidth. |
| 979 |
This memo provides information for the Internet community. This memo |
| 980 |
does not specify an Internet standard of any kind. |
| 981 |
|
| 982 |
|
| 983 |
<span class="h2"><a class="selflink" id="section-1809" href="#section-1809">1809</a> Partridge </span> Jun 95 Using the Flow Label Field in IPv6 |
| 984 |
|
| 985 |
The purpose of this memo is to distill various opinions and suggestions |
| 986 |
of the End-to-End Research Group regarding the handling of Flow Labels |
| 987 |
into a set of suggestions for IPv6. This memo provides information for |
| 988 |
the Internet community. This memo does not specify an Internet standard |
| 989 |
of any kind. |
| 990 |
|
| 991 |
|
| 992 |
<span class="h2"><a class="selflink" id="section-1808" href="#section-1808">1808</a> Fielding </span> Jun 95 Relative Uniform Resource Locators |
| 993 |
|
| 994 |
In situations where the base URL is well-defined and known to the parser |
| 995 |
(human or machine), it is useful to be able to embed URL references |
| 996 |
which inherit that context rather than re-specifying it in every |
| 997 |
instance. This document defines the syntax and semantics for such |
| 998 |
Relative Uniform Resource Locators. [STANDARDS-TRACK] |
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Elliott Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h2"><a class="selflink" id="section-1807" href="#section-1807">1807</a> Lasher </span> Jun 95 A Format for Bibliographic Records |
| 1010 |
|
| 1011 |
This RFC defines a format for bibliographic records describing technical |
| 1012 |
reports. This memo provides information for the Internet community. |
| 1013 |
This memo does not specify an Internet standard of any kind. |
| 1014 |
|
| 1015 |
|
| 1016 |
<span class="h2"><a class="selflink" id="section-1806" href="#section-1806">1806</a> Troost </span> Jun 95 Communicating Presentation Information |
| 1017 |
in Internet Messages: The |
| 1018 |
Content-Disposition Heade |
| 1019 |
|
| 1020 |
This memo provides a mechanism whereby messages conforming to the [RFC |
| 1021 |
1521] ("MIME") specification can convey presentational information. |
| 1022 |
This memo defines an Experimental Protocol for the Internet community. |
| 1023 |
|
| 1024 |
|
| 1025 |
<span class="h2"><a class="selflink" id="section-1805" href="#section-1805">1805</a> Rubin </span> Jun 95 Location-Independent Data/Software |
| 1026 |
Integrity Protocol |
| 1027 |
|
| 1028 |
This memo describes a protocol for adding integrity assurance to files |
| 1029 |
that are distributed across the Internet. This memo provides |
| 1030 |
information for the Internet community. This memo does not specify an |
| 1031 |
Internet standard of any kind. |
| 1032 |
|
| 1033 |
|
| 1034 |
<span class="h2"><a class="selflink" id="section-1804" href="#section-1804">1804</a> Mansfield </span> Jun 95 Schema Publishing in X.500 Directory |
| 1035 |
|
| 1036 |
In this document we propose a solution using the existing mechanisms of |
| 1037 |
the directory [1] itself. We present a naming scheme for naming schema |
| 1038 |
objects and a meta-schema for storing schema objects in the directory. |
| 1039 |
This memo defines an Experimental Protocol for the Internet community. |
| 1040 |
|
| 1041 |
|
| 1042 |
<span class="h2"><a class="selflink" id="section-1803" href="#section-1803">1803</a> Wright </span> Jun 95 Recommendations for an X.500 Production |
| 1043 |
Directory Service |
| 1044 |
|
| 1045 |
This document contains a set of basic recommendations for a country- |
| 1046 |
level X.500 DSA. This memo provides information for the Internet |
| 1047 |
community. It does not specify an Internet standard of any kind. |
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Elliott Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1899">RFC 1899</a> Summary of 1800-1899 January 1997</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h2"><a class="selflink" id="section-1802" href="#section-1802">1802</a> Alvestrand </span> Jun 95 Introducing Project Long Bud: Internet |
| 1066 |
Pilot Project for the Deployment of |
| 1067 |
X.500 Directory Information in Support |
| 1068 |
of X.400 Routing |
| 1069 |
|
| 1070 |
This memo describes a proposed Internet Pilot Project that seeks to |
| 1071 |
prove the MHS-DS approach on a larger scale. This memo provides |
| 1072 |
information for the Internet community. This memo does not specify an |
| 1073 |
Internet standard of any kind. |
| 1074 |
|
| 1075 |
|
| 1076 |
<span class="h2"><a class="selflink" id="section-1801" href="#section-1801">1801</a> Kille </span> Jun 95 X.400-MHS use of the X.500 Directory to |
| 1077 |
support X.400-MHS Routing |
| 1078 |
|
| 1079 |
The key problem in routing is to map from an O/R Address onto an MTA |
| 1080 |
(next hop). This shall be an MTA which in some sense is "nearer" to the |
| 1081 |
destination UA. This is done repeatedly until the message can be |
| 1082 |
directly delivered to the recipient UA. This memo defines an |
| 1083 |
Experimental Protocol for the Internet community. |
| 1084 |
|
| 1085 |
|
| 1086 |
<span class="h2"><a class="selflink" id="section-1800" href="#section-1800">1800</a> I.A.B. </span> Jul 95 INTERNET OFFICIAL PROTOCOL STANDARDS |
| 1087 |
|
| 1088 |
This memo describes the state of standardization of protocols used in |
| 1089 |
the Internet as determined by the Internet Architecture Board (IAB). |
| 1090 |
[STANDARDS-TRACK] |
| 1091 |
|
| 1092 |
|
| 1093 |
Security Considerations |
| 1094 |
|
| 1095 |
Security issues are not discussed in this memo. |
| 1096 |
|
| 1097 |
Author's Address |
| 1098 |
|
| 1099 |
Josh Elliott |
| 1100 |
University of Southern California |
| 1101 |
Information Sciences Institute |
| 1102 |
4676 Admiralty Way |
| 1103 |
Marina del Rey, CA 90292 |
| 1104 |
|
| 1105 |
Phone: (310) 822-1511 |
| 1106 |
|
| 1107 |
EMail: [email protected] |
| 1108 |
|
| 1109 |
|
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
Elliott Informational [Page 20] |
| 1117 |
</pre> |