| 1 |
<pre>Network Working Group M. Kennedy |
| 2 |
Request for Comments: 1299 ISI |
| 3 |
Category: Informational January 1997 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Request for Comments Summary</span> |
| 7 |
|
| 8 |
RFC Numbers 1200-1299 |
| 9 |
|
| 10 |
Status of This Memo |
| 11 |
|
| 12 |
This RFC is a slightly annotated list of the 100 RFCs from <a href="./rfc1200">RFC 1200</a> |
| 13 |
through RFCs 1299. 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-1299" href="#section-1299">1299</a> Kennedy </span> Jan 97 Requests For Comments Summary |
| 32 |
|
| 33 |
This memo. |
| 34 |
|
| 35 |
|
| 36 |
<span class="h2"><a class="selflink" id="section-1298" href="#section-1298">1298</a> Wormley </span> Feb 92 SNMP over IPX |
| 37 |
|
| 38 |
This memo defines a convention for encapsulating Simple Network |
| 39 |
Management Protocol (SNMP) packets over the transport mechanism provided |
| 40 |
via the Internetwork Packet Exchange (IPX) protocol. This memo provides |
| 41 |
information for the Internet community. It does not specify an Internet |
| 42 |
standard. |
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Kennedy Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1297" href="#section-1297">1297</a> Johnson </span> Jan 92 NOC Internal Integrated Trouble Ticket |
| 58 |
System |
| 59 |
Functional Specification Wishlist |
| 60 |
|
| 61 |
This document explores competing uses, architectures, and desirable |
| 62 |
features of integrated internal trouble ticket systems for Network and |
| 63 |
other Operations Centers. This memo provides information for the |
| 64 |
Internet community. It does not specify an Internet standard. |
| 65 |
|
| 66 |
|
| 67 |
<span class="h2"><a class="selflink" id="section-1296" href="#section-1296">1296</a> Lottor </span> Jan 92 Internet Growth (1981-1991) |
| 68 |
|
| 69 |
This document illustrates the growth of the Internet by examination of |
| 70 |
entries in the Domain Name System (DNS) and pre-DNS host tables. This |
| 71 |
memo provides information for the Internet community. It does not |
| 72 |
specify an Internet standard. |
| 73 |
|
| 74 |
|
| 75 |
|
| 76 |
<span class="h2"><a class="selflink" id="section-1295" href="#section-1295">1295</a> N.A.D.F. </span> Jan 92 User Bill of Rights for entries |
| 77 |
and listings in the Public Directory |
| 78 |
|
| 79 |
This RFC is a near-verbatim copy of a document, known as NADF-265, which |
| 80 |
has been produced by the North American Directory Forum (NADF). This |
| 81 |
memo provides information for the Internet community. It does not |
| 82 |
specify an Internet standard. |
| 83 |
|
| 84 |
|
| 85 |
<span class="h2"><a class="selflink" id="section-1294" href="#section-1294">1294</a> Bradley </span> Jan 92 Multiprotocol Interconnect over Frame |
| 86 |
Relay |
| 87 |
|
| 88 |
This memo describes an encapsulation method for carrying network |
| 89 |
interconnect traffic over a Frame Relay backbone. It covers aspects of |
| 90 |
both Bridging and Routing. [STANDARDS-TRACK] |
| 91 |
|
| 92 |
|
| 93 |
<span class="h2"><a class="selflink" id="section-1293" href="#section-1293">1293</a> Bradley </span> Jan 92 Inverse Address Resolution Protocol |
| 94 |
|
| 95 |
This memo describes additions to ARP that will allow a station to |
| 96 |
request a protocol address corresponding to a given hardware address. |
| 97 |
[STANDARDS-TRACK] |
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Kennedy Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1292" href="#section-1292">1292</a> Lang </span> Jan 92 A Catalog of Available X.500 |
| 114 |
Implementations |
| 115 |
|
| 116 |
The goal of this document is to provide information regarding the |
| 117 |
availability and capability of implementations of X.500. This memo |
| 118 |
provides information for the Internet community. It does not specify an |
| 119 |
Internet standard. |
| 120 |
|
| 121 |
|
| 122 |
<span class="h2"><a class="selflink" id="section-1291" href="#section-1291">1291</a> Aggarwal </span> Dec 91 Mid-Level Networks Potential |
| 123 |
Technical Services |
| 124 |
|
| 125 |
This document proposes a set of technical services that each Internet |
| 126 |
mid-level network can offer within the mid-level network itself and and |
| 127 |
to its peer networks. This RFC provides information for the Internet |
| 128 |
community. It does not specify an Internet standard. |
| 129 |
|
| 130 |
|
| 131 |
<span class="h2"><a class="selflink" id="section-1290" href="#section-1290">1290</a> Martin </span> Dec 91 There's Gold in them thar Networks! |
| 132 |
or Searching for Treasure in all the |
| 133 |
Wrong Places |
| 134 |
|
| 135 |
This paper will present some of the "gold nuggets" of information and |
| 136 |
file repositories on the network that could be of use to end users. This |
| 137 |
RFC provides information for the Internet community. It does not specify |
| 138 |
an Internet standard. |
| 139 |
|
| 140 |
|
| 141 |
<span class="h2"><a class="selflink" id="section-1289" href="#section-1289">1289</a> Saperia </span> Dec 91 DECnet Phase IV MIB Extensions |
| 142 |
|
| 143 |
This memo is an extension to the SNMP MIB. This memo defines a set of |
| 144 |
DECnet Phase IV extensions that have been created for the Internet MIB. |
| 145 |
[STANDARDS-TRACK] |
| 146 |
|
| 147 |
|
| 148 |
<span class="h2"><a class="selflink" id="section-1288" href="#section-1288">1288</a> Zimmerman </span> Dec 91 The Finger User Informational Protocol |
| 149 |
|
| 150 |
This memo describes the Finger user information protocol.This is a |
| 151 |
simple protocol which provides an interface to a remote user information |
| 152 |
program. [STANDARDS-TRACK] |
| 153 |
|
| 154 |
|
| 155 |
<span class="h2"><a class="selflink" id="section-1287" href="#section-1287">1287</a> Clark </span> Dec 91 Towards the Future Internet Architecture |
| 156 |
|
| 157 |
This informational RFC discusses important directions for possible |
| 158 |
future evolution of the Internet architecture, and suggests steps |
| 159 |
towards the desired goals. This memo provides information for the |
| 160 |
Internet community. It does not specify an Internet standard. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Kennedy Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1286" href="#section-1286">1286</a> Decker </span> Dec 91 Definitions of Managed Objects for |
| 170 |
Bridges |
| 171 |
|
| 172 |
This memo defines a portion of the Management Information Base (MIB) for |
| 173 |
use with network management protocols in TCP/IP based internets. In |
| 174 |
particular it defines objects for managing bridges based on the IEEE |
| 175 |
802.1d draft standard between Local Area Network (LAN) segments. This |
| 176 |
memo is an extension to the SNMP MIB. [STANDARDS-TRACK] |
| 177 |
|
| 178 |
|
| 179 |
<span class="h2"><a class="selflink" id="section-1285" href="#section-1285">1285</a> Case </span> Jan 92 FDDI Management Information Base |
| 180 |
|
| 181 |
This memo defines a portion of the Management Information Base (MIB) for |
| 182 |
use with network management protocols in TCP/IP-based internets. In |
| 183 |
particular, it defines objects for managing devices which implement the |
| 184 |
FDDI. [STANDARDS-TRACK] |
| 185 |
|
| 186 |
|
| 187 |
<span class="h2"><a class="selflink" id="section-1284" href="#section-1284">1284</a> Cook </span> Dec 91 Definitions of Managed Objects for the |
| 188 |
Ethernet-like Interface Types |
| 189 |
|
| 190 |
This memo defines a portion of the Management Information Base (MIB) for |
| 191 |
use with network management protocols in TCP/IP-based internets. In |
| 192 |
particular, it defines objects for managing ethernet-like objects. |
| 193 |
[STANDARDS-TRACK] |
| 194 |
|
| 195 |
|
| 196 |
<span class="h2"><a class="selflink" id="section-1283" href="#section-1283">1283</a> Rose </span> Dec 91 SNMP over OSI |
| 197 |
|
| 198 |
This memo describes mappings from the SNMP onto both the COTS and the |
| 199 |
CLTS. This memo defines an Experimental Protocol for the Internet |
| 200 |
community. It does not specify an Internet Standard. |
| 201 |
|
| 202 |
|
| 203 |
<span class="h2"><a class="selflink" id="section-1282" href="#section-1282">1282</a> Kantor </span> Dec 91 BSD Rlogin |
| 204 |
|
| 205 |
This memo documents an existing protocol and common implementation that |
| 206 |
is extensively used on the Internet. This memo provides information for |
| 207 |
the Internet community. It does not specify an Internet standard. |
| 208 |
|
| 209 |
|
| 210 |
<span class="h2"><a class="selflink" id="section-1281" href="#section-1281">1281</a> Pethia </span> Nov 91 Guidelines for the Secure Operation of |
| 211 |
the Internet |
| 212 |
|
| 213 |
The purpose of this document is to provide a set of guidelines to aid in |
| 214 |
the secure operation of the Internet. This memo provides information for |
| 215 |
the Internet community. It does not specify an Internet standard. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Kennedy Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-1280" href="#section-1280">1280</a> IAB </span> Mar 92 IAB Official Protocol Standards |
| 226 |
|
| 227 |
This memo describes the state of standardization of protocols used in |
| 228 |
the Internet as determined by the Internet Activities Board (IAB). This |
| 229 |
memo provides information for the Internet community. It does not |
| 230 |
specify an Internet standard. |
| 231 |
|
| 232 |
|
| 233 |
<span class="h2"><a class="selflink" id="section-1279" href="#section-1279">1279</a> Hardcastle-Kille </span>Nov 91 X.500 and Domains |
| 234 |
|
| 235 |
This RFC considers X.500 in relation to Internet and UK Domains. This |
| 236 |
memo defines an Experimental Protocol for the Internet community. It |
| 237 |
does not specify an Internet standard. |
| 238 |
|
| 239 |
|
| 240 |
<span class="h2"><a class="selflink" id="section-1278" href="#section-1278">1278</a> Hardcastle-Kille </span>Nov 91 A string encoding of Presentation |
| 241 |
Address |
| 242 |
|
| 243 |
There are a number of environments where a simple string encoding of |
| 244 |
Presentation Address is desirable. This specification defines such a |
| 245 |
representation. This memo provides information for the Internet |
| 246 |
community. It does not specify an Internet standard. |
| 247 |
|
| 248 |
|
| 249 |
<span class="h2"><a class="selflink" id="section-1277" href="#section-1277">1277</a> Hardcastle-Kille </span>Nov 91 Encoding Network Addresses |
| 250 |
to support operation over non-OSI |
| 251 |
lower layers |
| 252 |
|
| 253 |
This document defines a new network address format, and rules for using |
| 254 |
some existing network address formats. [STANDARDS-TRACK] |
| 255 |
|
| 256 |
|
| 257 |
<span class="h2"><a class="selflink" id="section-1276" href="#section-1276">1276</a> Hardcastle-Kille </span>Nov 91 Replication and Distributed |
| 258 |
Operations extensions to provide |
| 259 |
an Internet Directory using X.500 |
| 260 |
|
| 261 |
Some requirements on extensions to X.500 are described in the |
| 262 |
RFC[HK91b], in order to build an Internet Directory using X.500(1988). |
| 263 |
This document specifies a set of solutions to the problems raised. |
| 264 |
[STANDARDS-TRACK] |
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Kennedy Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-1275" href="#section-1275">1275</a> Hardcastle-Kille </span>Nov 91 Replication Requirements to provide |
| 282 |
an Internet Directory using X.500 |
| 283 |
|
| 284 |
This RFC considers certain deficiencies of the 1988 X.500 standard, |
| 285 |
which need to be addressed before an effective open Internet Directory |
| 286 |
can be established using these protocols and services [CCI88]. This memo |
| 287 |
provides information for the Internet community. It does not specify an |
| 288 |
Internet standard. |
| 289 |
|
| 290 |
|
| 291 |
<span class="h2"><a class="selflink" id="section-1274" href="#section-1274">1274</a> Barker </span> Nov 91 The COSINE and Internet X.500 Schema |
| 292 |
|
| 293 |
This document suggests an X.500 Directory Schema, or Naming |
| 294 |
Architecture, for use in the COSINE and Internet X.500 pilots. |
| 295 |
[STANDARDS-TRACK] |
| 296 |
|
| 297 |
|
| 298 |
<span class="h2"><a class="selflink" id="section-1273" href="#section-1273">1273</a> Schwartz </span>Nov 91 A Measurement Study of Changes in |
| 299 |
Service-Level Reachability in the Global |
| 300 |
TCP/IP Internet: Goals, Experimental Design, |
| 301 |
Implementation, and Policy Considerations |
| 302 |
|
| 303 |
This memo describes plans to carry out a longitudinal measurement study |
| 304 |
of changes in service-level reachability in the global TCP/IP Internet. |
| 305 |
This memo provides information for the Internet community. It does not |
| 306 |
specify an Internet standard. |
| 307 |
|
| 308 |
|
| 309 |
<span class="h2"><a class="selflink" id="section-1272" href="#section-1272">1272</a> Mills </span> Nov 91 Internet Accounting: Background |
| 310 |
|
| 311 |
This document provides background information for the "Internet |
| 312 |
Accounting Architecture". This memo provides information for the |
| 313 |
Internet community. It does not specify an Internet standard. |
| 314 |
|
| 315 |
|
| 316 |
<span class="h2"><a class="selflink" id="section-1271" href="#section-1271">1271</a> Waldbusser </span>Nov 91 Remote Network Monitoring Management |
| 317 |
Information Base |
| 318 |
|
| 319 |
This memo defines a portion of the Management Information Base (MIB) for |
| 320 |
use with network management protocols in TCP/IP-based internets. In |
| 321 |
particular, it defines objects for managing remote network monitoring |
| 322 |
devices. [STANDARDS-TRACK] |
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Kennedy Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-1270" href="#section-1270">1270</a> Kastenholz </span>Oct 91 SNMP Communications Services |
| 338 |
|
| 339 |
This document discusses various issues to be considered when determining |
| 340 |
the underlying communications services to be used by an SNMP |
| 341 |
implementation. This memo provides information for the Internet |
| 342 |
community. It does not specify an Internet standard. |
| 343 |
|
| 344 |
|
| 345 |
<span class="h2"><a class="selflink" id="section-1269" href="#section-1269">1269</a> Willis </span> Oct 91 Definitions of Managed Objects |
| 346 |
for the Border Gateway Protocol (Version 3) |
| 347 |
|
| 348 |
This memo defines a portion of the Management Information Base (MIB) for |
| 349 |
use with network management protocols in TCP/IP-based internets. In |
| 350 |
particular, it defines objects for managing the Border Gateway Protocol. |
| 351 |
[STANDARDS-TRACK] |
| 352 |
|
| 353 |
|
| 354 |
<span class="h2"><a class="selflink" id="section-1268" href="#section-1268">1268</a> Rekhter </span> Oct 91 Application of the Border Gateway Protocol |
| 355 |
in the Internet |
| 356 |
|
| 357 |
This document describes the usage of the BGP in the Internet. |
| 358 |
[STANDARDS-TRACK] |
| 359 |
|
| 360 |
|
| 361 |
<span class="h2"><a class="selflink" id="section-1267" href="#section-1267">1267</a> Lougheed </span> Oct 91 A Border Gateway Protocol 3 (BGP-3) |
| 362 |
|
| 363 |
This memo, together with its companion document, "Application of the |
| 364 |
Border Gateway Protocol in the Internet", define an inter-autonomous |
| 365 |
system routing protocol for the Internet. [STANDARDS-TRACK] |
| 366 |
|
| 367 |
|
| 368 |
<span class="h2"><a class="selflink" id="section-1266" href="#section-1266">1266</a> Rekhter </span> Oct 91 Experience with the BGP Protocol |
| 369 |
|
| 370 |
The purpose of this memo is to document how the requirements for |
| 371 |
advancing a routing protocol to Draft Standard have been satisfied by |
| 372 |
Border Gateway Protocol (BGP). This memo provides information for the |
| 373 |
Internet community. It does not specify an Internet standard. |
| 374 |
|
| 375 |
|
| 376 |
<span class="h2"><a class="selflink" id="section-1265" href="#section-1265">1265</a> Rekhter </span> Oct 91 BGP Protocol Analysis |
| 377 |
|
| 378 |
This report summarizes the key feature of BGP, and analyzes the protocol |
| 379 |
with respect to scaling and performance. This memo provides information |
| 380 |
for the Internet community. It does not specify an Internet standard. |
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Kennedy Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-1264" href="#section-1264">1264</a> Hinden </span> Oct 91 Internet Engineering Task Force |
| 394 |
Internet Routing Protocol Standardization |
| 395 |
Criteria |
| 396 |
|
| 397 |
This informational RFC presents procedures for creating and documenting |
| 398 |
Internet standards on routing protocols. These procedures have been |
| 399 |
established by the Internet Activities Board (IAB) in consultation with |
| 400 |
the Internet Engineering Steering Group (IESG). This memo provides |
| 401 |
information for the Internet community. It does not specifiy an Internet |
| 402 |
standard. |
| 403 |
|
| 404 |
|
| 405 |
<span class="h2"><a class="selflink" id="section-1263" href="#section-1263">1263</a> O'Malley </span>Oct 91 TCP Extensions Considered Harmful |
| 406 |
|
| 407 |
This RFC comments on recent proposals to extend TCP. It argues that the |
| 408 |
backward compatible extensions proposed in RFC's 1072 and 1185 should |
| 409 |
not be pursued, and proposes an alternative way to evolve the Internet |
| 410 |
protocol suite. This memo provides information for the Internet |
| 411 |
community. It does not specify an Internet standard. |
| 412 |
|
| 413 |
|
| 414 |
<span class="h2"><a class="selflink" id="section-1262" href="#section-1262">1262</a> IAB </span> Oct 91 Guidelines for Internet Measurement Activities |
| 415 |
|
| 416 |
This RFC represents IAB guidance for researchers considering measurement |
| 417 |
experiments on the Internet. This memo provides information for the |
| 418 |
Internet community. It does not specify an Internet standard. |
| 419 |
|
| 420 |
|
| 421 |
<span class="h2"><a class="selflink" id="section-1261" href="#section-1261">1261</a> Williamson </span>Sept 91 Transition of NIC Services |
| 422 |
|
| 423 |
This memo outlines the transition of NIC Services. This memo provides |
| 424 |
information for the Internet community. It does not specify an Internet |
| 425 |
standard. |
| 426 |
|
| 427 |
|
| 428 |
<span class="h2"><a class="selflink" id="section-1260" href="#section-1260">1260</a> Never issued.</span> |
| 429 |
|
| 430 |
|
| 431 |
<span class="h2"><a class="selflink" id="section-1259" href="#section-1259">1259</a> Kapor </span> Sept 91 Building The Open Road: |
| 432 |
The NREN As Test-Bed For The National |
| 433 |
Public Network |
| 434 |
|
| 435 |
This memo discusses the background and importance of NREN. This memo |
| 436 |
provides information for the Internet community. It does not specify an |
| 437 |
Internet standard. |
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Kennedy Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-1258" href="#section-1258">1258</a> Kantor </span> Sept 91 BSD Rlogin |
| 450 |
|
| 451 |
The rlogin facility provides a remote-echoed, locally flow-controlled |
| 452 |
virtual terminal with proper flushing of output.This memo documents an |
| 453 |
existing protocol and common implementation that is extensively used on |
| 454 |
the Internet. This memo provides information for the Internet |
| 455 |
community. It does not specify an Internet standard. |
| 456 |
|
| 457 |
|
| 458 |
<span class="h2"><a class="selflink" id="section-1257" href="#section-1257">1257</a> Partridge </span>Sept 91 Isochronous Applications Do Not Require |
| 459 |
Jitter-Controlled Networks |
| 460 |
|
| 461 |
This memo argues that jitter control is not required for networks to |
| 462 |
support isochronous applications. This memo provides information for the |
| 463 |
Internet community. It does not specify an Internet standard. |
| 464 |
|
| 465 |
|
| 466 |
<span class="h2"><a class="selflink" id="section-1256" href="#section-1256">1256</a> Deering </span> Sept 91 ICMP Router Discovery Messages |
| 467 |
|
| 468 |
This document specifies an extension of the Internet Control Message |
| 469 |
Protocol (ICMP) to enable hosts attached to multicast or broadcast |
| 470 |
networks to discover the IP addresses of their neighboring routers. |
| 471 |
[STANDARDS-TRACK] |
| 472 |
|
| 473 |
|
| 474 |
<span class="h2"><a class="selflink" id="section-1255" href="#section-1255">1255</a> N.A.D.F. </span> Sept 91 A Naming Scheme for c=US |
| 475 |
|
| 476 |
This memo documents the NADF's agreement as to how entries are named in |
| 477 |
the public portions of the North American Directory. This memo provides |
| 478 |
information for the Internet community. It does not specify an Internet |
| 479 |
standard. |
| 480 |
|
| 481 |
|
| 482 |
<span class="h2"><a class="selflink" id="section-1254" href="#section-1254">1254</a> Mankin </span> Aug 91 Gateway Congestion Control Survey |
| 483 |
|
| 484 |
The purpose of this paper is to present a review of the congestion |
| 485 |
control approaches, as a way of encouraging new discussion and |
| 486 |
experimentation. Included in the survey are Source Quench, Random Drop, |
| 487 |
Congestion Indication (DEC Bit), and Fair Queueing. |
| 488 |
|
| 489 |
|
| 490 |
<span class="h2"><a class="selflink" id="section-1253" href="#section-1253">1253</a> Baker </span> Aug 91 OSPF Version 2 Management Information Base |
| 491 |
|
| 492 |
This memo defines a portion of the Management Information Base (MIB) for |
| 493 |
use with network management protocols in TCP/IP-based internets. In |
| 494 |
particular, it defines objects for managing OSPF Version 2. [STANDARDS- |
| 495 |
TRACK] |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Kennedy Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h2"><a class="selflink" id="section-1252" href="#section-1252">1252</a> Baker </span> Aug 91 OSPF Version 2 Management Information Base |
| 506 |
|
| 507 |
This memo defines a portion of the Management Information Base (MIB) for |
| 508 |
use with network management protocols in TCP/IP-based internets. In |
| 509 |
particular, it defines objects for managing OSPF Version 2. [STANDARDS- |
| 510 |
TRACK] |
| 511 |
|
| 512 |
|
| 513 |
<span class="h2"><a class="selflink" id="section-1251" href="#section-1251">1251</a> Malkin </span>Aug 91 Who's Who in the Internet |
| 514 |
Biographies of IAB, IESG and IRSG Members |
| 515 |
|
| 516 |
This FYI RFC contains biographical information about members of the |
| 517 |
Internet Activities Board (IAB), the Internet Engineering Steering Group |
| 518 |
(IESG) of the Internet Engineering Task Force (IETF), and the the |
| 519 |
Internet Research Steering Group (IRSG) of the Internet Research Task |
| 520 |
Force (IRTF). This memo provides information for the Internet community. |
| 521 |
It does not specify an Internet standard. [FYI 9] |
| 522 |
|
| 523 |
|
| 524 |
<span class="h2"><a class="selflink" id="section-1250" href="#section-1250">1250</a> IAB </span> Aug 91 IAB Official Protocol Standards |
| 525 |
|
| 526 |
This memo describes the state of standardization of protocols used in |
| 527 |
the Internet as determined by the Internet Activities Board (IAB). This |
| 528 |
memo provides information for the Internet community. It does not |
| 529 |
specify an Internet standard. |
| 530 |
|
| 531 |
|
| 532 |
<span class="h2"><a class="selflink" id="section-1249" href="#section-1249">1249</a> Howes </span> Aug 91 DIXIE Protocol Specification |
| 533 |
|
| 534 |
This RFC defines a mechanism by which TCP/UDP based clients can access |
| 535 |
OSI Directory Service without the overhead of the ISO transport and |
| 536 |
presentation protocols required to implement full-blown DAP. This memo |
| 537 |
provides information for the Internet community. It does not specify |
| 538 |
any standard. |
| 539 |
|
| 540 |
|
| 541 |
<span class="h2"><a class="selflink" id="section-1248" href="#section-1248">1248</a> Baker </span> Jul 91 OSPF Version 2 Management Information Base |
| 542 |
|
| 543 |
This memo defines an experimental portion of the Management Information |
| 544 |
Base (MIB) for use with network management protocols in TCP/IP-based |
| 545 |
internets. In particular, it defines objects for managing OSPF Version |
| 546 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. [STANDARDS-TRACK]</span> |
| 547 |
|
| 548 |
|
| 549 |
<span class="h2"><a class="selflink" id="section-1247" href="#section-1247">1247</a> Moy </span> Jul 91 OSPF Version 2 |
| 550 |
|
| 551 |
This memo documents version 2 of the OSPF protocol. OSPF is a link- |
| 552 |
state based routing protocol. [STANDARDS-TRACK] |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Kennedy Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h2"><a class="selflink" id="section-1246" href="#section-1246">1246</a> Moy </span> Jul 91 Experience with the OSPF protocol |
| 562 |
|
| 563 |
This report documents experience with OSPF V2. This includes reports on |
| 564 |
interoperability testing, field experience, simulations and the current |
| 565 |
state of OSPF implementations. This memo provides information for the |
| 566 |
Internet community. It does not specify any Internet standard. |
| 567 |
|
| 568 |
|
| 569 |
<span class="h2"><a class="selflink" id="section-1245" href="#section-1245">1245</a> Moy </span> Jul 91 OSPF protocol analysis |
| 570 |
|
| 571 |
This report attempts to summarize the key features of OSPF V2. It also |
| 572 |
attempts to analyze how the protocol will perform and scale in the |
| 573 |
Internet. This memo provides information for the Internet community. It |
| 574 |
does not specify any Internet standard. |
| 575 |
|
| 576 |
|
| 577 |
<span class="h2"><a class="selflink" id="section-1244" href="#section-1244">1244</a> Holbrook </span>Jul 91 Site Security Handbook |
| 578 |
|
| 579 |
This FYI RFC is a first attempt at providing Internet users guidance on |
| 580 |
how to deal with security issues in the Internet. This FYI RFC provides |
| 581 |
information for the Internet community. It does not specify an Internet |
| 582 |
standard. [FYI 8] |
| 583 |
|
| 584 |
|
| 585 |
<span class="h2"><a class="selflink" id="section-1243" href="#section-1243">1243</a> Waldbusser </span>Jul 91 AppleTalk Management Information Base |
| 586 |
|
| 587 |
This memo defines objects for managing AppleTalk objects for use with |
| 588 |
the SNMP protocol. [STANDARDS-TRACK] |
| 589 |
|
| 590 |
|
| 591 |
<span class="h2"><a class="selflink" id="section-1242" href="#section-1242">1242</a> Bradner </span> Jul 91 Benchmarking Terminology for Network |
| 592 |
Interconnection Devices |
| 593 |
|
| 594 |
This memo discusses and defines a number of terms that are used in |
| 595 |
describing performance benchmarking tests and the results of such tests. |
| 596 |
This memo provides information for the Internet community. It does not |
| 597 |
specify an Internet standard. |
| 598 |
|
| 599 |
|
| 600 |
<span class="h2"><a class="selflink" id="section-1241" href="#section-1241">1241</a> Woodburn </span> Jul 91 A Scheme for an Internet Encapsulation |
| 601 |
Protocol: Version 1 |
| 602 |
|
| 603 |
This memo defines an Experimental Protocol for the Internet community. |
| 604 |
It does not specify an Internet standard. |
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Kennedy Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h2"><a class="selflink" id="section-1240" href="#section-1240">1240</a> Shue </span> Jun 91 OSI Connectionless Transport Services |
| 618 |
on top of UDP |
| 619 |
Version: 1 |
| 620 |
|
| 621 |
This document describes a protocol for running OSI Connectionless |
| 622 |
service on UDP. [STANDARDS-TRACK] |
| 623 |
|
| 624 |
|
| 625 |
<span class="h2"><a class="selflink" id="section-1239" href="#section-1239">1239</a> Reynolds </span>Jun 91 Reassignment of Experimental MIBs to |
| 626 |
Standard MIBs |
| 627 |
|
| 628 |
This memo specifically updates <a href="./rfc1229">RFC 1229</a>, <a href="./rfc1230">RFC 1230</a>, <a href="./rfc1231">RFC 1231</a>, <a href="./rfc1232">RFC 1232</a> |
| 629 |
and <a href="./rfc1233">RFC 1233</a> with new codes. [STANDARDS-TRACK] |
| 630 |
|
| 631 |
|
| 632 |
<span class="h2"><a class="selflink" id="section-1238" href="#section-1238">1238</a> Satz </span> Jun 91 CLNS MIB for use with Connectionless |
| 633 |
Network Protocol (ISO 8473) and |
| 634 |
End System to Intermediate System (ISO 9542) |
| 635 |
|
| 636 |
This memo defines an experimental portion of the Management Information |
| 637 |
Base (MIB) for use with network management protocols in TCP/IP-based |
| 638 |
internets. This is an Experimental Protocol for the Internet community. |
| 639 |
It does not specify an Internet standard. |
| 640 |
|
| 641 |
|
| 642 |
<span class="h2"><a class="selflink" id="section-1237" href="#section-1237">1237</a> Colella </span> Jul 91 Guidelines for OSI NSAP Allocation |
| 643 |
in the Internet |
| 644 |
|
| 645 |
This paper provides guidelines for allocating NSAPs in the |
| 646 |
Internet.[STANDARDS-TRACK] |
| 647 |
|
| 648 |
|
| 649 |
<span class="h2"><a class="selflink" id="section-1236" href="#section-1236">1236</a> Morales </span> Jun 91 IP to X.121 Address Mapping for DDN |
| 650 |
A Model for Routing in the Internet |
| 651 |
|
| 652 |
This memo defines a standard way of converting IP addresses to CCITT |
| 653 |
<span class="h3"><a class="selflink" id="appendix-X.121" href="#appendix-X.121">X.121</a> addresses and is the recommended standard for use on the Internet,</span> |
| 654 |
specifically for the Defense Data Network (DDN). This memo provides |
| 655 |
information for the Internet community. It does not specify an Internet |
| 656 |
standard. |
| 657 |
|
| 658 |
|
| 659 |
<span class="h2"><a class="selflink" id="section-1235" href="#section-1235">1235</a> Ioannidis </span>Jun 91 The Coherent File Distribution Protocol |
| 660 |
|
| 661 |
This memo describes the Coherent File Distribution Protocol (CFDP). |
| 662 |
This is an Experimental Protocol for the Internet community. It does not |
| 663 |
specify an Internet standard. |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Kennedy Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h2"><a class="selflink" id="section-1234" href="#section-1234">1234</a> Provan </span> Jun 91 Tunneling IPX Traffic through IP Networks |
| 674 |
|
| 675 |
This memo describes a method of encapsulating IPX datagrams within UDP |
| 676 |
packets so that IPX traffic can travel across an IP internet. |
| 677 |
[STANDARDS-TRACK] |
| 678 |
|
| 679 |
|
| 680 |
<span class="h2"><a class="selflink" id="section-1233" href="#section-1233">1233</a> Cox </span> May 91 Definitions of Managed Objects for the DS3 |
| 681 |
Interface Type |
| 682 |
|
| 683 |
This memo defines objects for managing DS3 Interface objects for use |
| 684 |
with the SNMP protocol. [STANDARDS-TRACK] |
| 685 |
|
| 686 |
|
| 687 |
<span class="h2"><a class="selflink" id="section-1234" href="#section-1234">1234</a> Baker </span> May 91 Definitions of Managed Objects |
| 688 |
for the DS1 Interface Type |
| 689 |
|
| 690 |
This memo defines objects for managing DS1 Interface objects for use |
| 691 |
with the SNMP protocol. [STANDARDS-TRACK] |
| 692 |
|
| 693 |
|
| 694 |
<span class="h2"><a class="selflink" id="section-1231" href="#section-1231">1231</a> McCloghrie </span>May 91 IEEE 802.5 Token Ring MIB |
| 695 |
|
| 696 |
This memo defines an experimental portion of the Management Information |
| 697 |
Base (MIB) for use with network management protocols in TCP/IP-based |
| 698 |
internets. In particular, this memo defines managed objects used for |
| 699 |
managing subnetworks which use the IEEE 802.5 Token Ring technology |
| 700 |
described in 802.5 Token Ring Access Method and Physical Layer |
| 701 |
Specifications, IEEE Standard 802.5-1989. [STANDARDS-TRACK] |
| 702 |
|
| 703 |
|
| 704 |
<span class="h2"><a class="selflink" id="section-1230" href="#section-1230">1230</a> McCloghrie </span> May 91 IEEE 802.4 Token Bus MIB |
| 705 |
|
| 706 |
This memo defines an experimental portion of the Management Information |
| 707 |
Base (MIB) for use with network management protocols in TCP/IP-based |
| 708 |
internets. In particular, this memo defines managed objects used for |
| 709 |
managing subnetworks which use the IEEE 802.4 Token Bus technology |
| 710 |
described in 802.4 Token-Passing Bus Access Method and Physical Layer |
| 711 |
Specifications, IEEE Standard 802.4. [STANDARDS-TRACK] |
| 712 |
|
| 713 |
|
| 714 |
<span class="h2"><a class="selflink" id="section-1229" href="#section-1229">1229</a> McCloghrie </span> May 91 Extensions to the Generic-Interface MIB |
| 715 |
|
| 716 |
This RFC contains definitions of managed objects used as experimental |
| 717 |
extensions to the generic interfaces structure of MIB-II. [STANDARDS- |
| 718 |
TRACK] |
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Kennedy Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h2"><a class="selflink" id="section-1228" href="#section-1228">1228</a> Carpenter </span> May 91 Simple Network Management Protocol |
| 730 |
Distributed Program Interface |
| 731 |
|
| 732 |
This RFC describes a protocol that International Business Machines |
| 733 |
Corporation (IBM) has been implementing in most of its SNMP agents to |
| 734 |
allow dynamic extension of supported MIBs. This is an Experimental |
| 735 |
Protocol for the Internet community. It does not specify an Internet |
| 736 |
standard. |
| 737 |
|
| 738 |
|
| 739 |
<span class="h2"><a class="selflink" id="section-1227" href="#section-1227">1227</a> Rose </span> May 91 SNMP MUX Protocol and MIB |
| 740 |
|
| 741 |
This memo suggests a mechanism by which a user process may associate |
| 742 |
itself with the local SNMP agent on a host, in order to implement |
| 743 |
portions of the MIB. This mechanism would be local to the host.This is |
| 744 |
an Experimental Protocol for the Internet community. It does not specify |
| 745 |
an Internet standard. |
| 746 |
|
| 747 |
|
| 748 |
<span class="h2"><a class="selflink" id="section-1226" href="#section-1226">1226</a> Kantor </span> May 91 Internet Protocol Encapsulation of AX.25 Frame |
| 749 |
|
| 750 |
This memo describes a method for the encapsulation of AX.25 (the Amateur |
| 751 |
Packet-Radio Link-Layer Protocol) frames within IP packets. This |
| 752 |
technique is an Experimental Protocol for the Internet community. It |
| 753 |
does not specify an Internet standard. |
| 754 |
|
| 755 |
|
| 756 |
<span class="h2"><a class="selflink" id="section-1225" href="#section-1225">1225</a> Rose </span> May 91 Post Office Protocol - Version 3 |
| 757 |
|
| 758 |
This memo suggests a simple method for workstations to dynamically |
| 759 |
access mail from a mailbox server. [STANDARDS-TRACK] |
| 760 |
|
| 761 |
|
| 762 |
<span class="h2"><a class="selflink" id="section-1224" href="#section-1224">1224</a> Steinberg </span>May 91 Techniques for Managing Asynchronously |
| 763 |
Generated Alerts |
| 764 |
|
| 765 |
This memo defines common mechanisms for managing asynchronously produced |
| 766 |
alerts in a manner consistent with current network management protocols. |
| 767 |
This memo specifies an Experimental Protocol for the Internet community. |
| 768 |
It does not specify an Internet standard. |
| 769 |
|
| 770 |
|
| 771 |
|
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Kennedy Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h2"><a class="selflink" id="section-1223" href="#section-1223">1223</a> Halpern </span>May 91 OSI CLNS and LLC1 Protocols on Network Systems |
| 786 |
HYPERchannel |
| 787 |
|
| 788 |
The intent of this document is to provide a complete discussion of the |
| 789 |
protocols and techniques used to transmit OSI CLNS and LLC1 datagrams |
| 790 |
(and any associated higher level protocols) on Network Systems |
| 791 |
Corporation's HYPERchannel equipment.This memo provides information for |
| 792 |
the Internet community. It does not specify an Internet standard. |
| 793 |
|
| 794 |
|
| 795 |
<span class="h2"><a class="selflink" id="section-1222" href="#section-1222">1222</a> Braun </span> May 91 Advancing the NSFNET Routing Architecture |
| 796 |
|
| 797 |
This RFC suggests improvements in the NSFNET routing architecture to |
| 798 |
accommodate a more flexible interface to the Backbone clients. This |
| 799 |
memo provides information for the Internet community. It does not |
| 800 |
specify an Internet standard. |
| 801 |
|
| 802 |
|
| 803 |
<span class="h2"><a class="selflink" id="section-1221" href="#section-1221">1221</a> Edmond </span> Apr 91 Host Access Protocol (HAP) Specification |
| 804 |
- Version 2 |
| 805 |
|
| 806 |
This memo describes the Host Access Protocol implemented in the |
| 807 |
Terrestrial Wideband Network (TWBNET). This memo provides information |
| 808 |
for the Internet community. It does not specify an Internet standard. |
| 809 |
|
| 810 |
|
| 811 |
<span class="h2"><a class="selflink" id="section-1220" href="#section-1220">1220</a> Baker </span> Apr 91 Point-to-Point Protocol Extensions |
| 812 |
for Bridging |
| 813 |
|
| 814 |
This document defines an extension of the Internet Point-to-Point |
| 815 |
Protocol (PPP) described in <a href="./rfc1171">RFC 1171</a>, targeting the use of Point-to- |
| 816 |
Point lines for Remote Bridging. [STANDARDS-TRACK] |
| 817 |
|
| 818 |
|
| 819 |
<span class="h2"><a class="selflink" id="section-1219" href="#section-1219">1219</a> Tsuchiya </span> Apr 91 On the Assignment of Subnet Numbers |
| 820 |
|
| 821 |
This memo suggests a new procedure for assigning subnet numbers. Use of |
| 822 |
this assignment technique within a network would be a purely local |
| 823 |
matter, and would not effect other networks. This memo provides |
| 824 |
information for the Internet community. It does not specify an Internet |
| 825 |
standard. |
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Kennedy Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="section-1218" href="#section-1218">1218</a> N.A.D.F. </span> Apr 91 A Naming Scheme for c=US |
| 842 |
|
| 843 |
This RFC is a near-verbatim copy of a document, known as NADF-123, which |
| 844 |
has been produced by the North American Directory Forum (NADF). As a |
| 845 |
part of its charter, the NADF must reach agreement as to how entries are |
| 846 |
named in the public portions of the North American Directory. This memo |
| 847 |
provides information for the Internet community. It does not specify an |
| 848 |
Internet standard. |
| 849 |
|
| 850 |
|
| 851 |
<span class="h2"><a class="selflink" id="section-1217" href="#section-1217">1217</a> Cerf </span> Apr 91 Memo from the Consortium for Slow |
| 852 |
Commotion Research (CSCR) |
| 853 |
|
| 854 |
|
| 855 |
This RFC is in response to <a href="./rfc1216">RFC 1216</a>, "Gigabit Network Economics and |
| 856 |
Paradigm Shifts". This memo provides information for the Internet |
| 857 |
community. It does not specify an Internet standard. |
| 858 |
|
| 859 |
|
| 860 |
<span class="h2"><a class="selflink" id="section-1216" href="#section-1216">1216</a> P.R.A.I. </span> Apr 91 Gigabit Network Economics and Paradigm Shifts |
| 861 |
|
| 862 |
This memo proposes a new standard paradigm for the Internet Activities |
| 863 |
Board (IAB) standardization track. [STANDARDS-TRACK] |
| 864 |
|
| 865 |
|
| 866 |
<span class="h2"><a class="selflink" id="section-1215" href="#section-1215">1215</a> Rose </span> Mar 91 A Convention for Defining Traps |
| 867 |
for use with the SNMP |
| 868 |
|
| 869 |
This memo suggests a straight-forward approach towards defining traps |
| 870 |
used with the SNMP. This memo provides information for the Internet |
| 871 |
community. It does not specify any standard. |
| 872 |
|
| 873 |
|
| 874 |
<span class="h2"><a class="selflink" id="section-1214" href="#section-1214">1214</a> Labarre </span> Apr 91 OSI Internet Management: Management |
| 875 |
Information Base |
| 876 |
|
| 877 |
This RFC documents a MIB for use with CMIP, either over pure OSI stacks |
| 878 |
or with the CMIP over TCP specification. It redefines objects comprised |
| 879 |
by the second revision of the Management Information Base for Network |
| 880 |
Management of TCP/IP-based internets: MIB-II so as to conform to the OSI |
| 881 |
structure of management information. [STANDARDS-TRACK] |
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Kennedy Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="section-1213" href="#section-1213">1213</a> McCloghrie </span>Mar 91 Management Information Base for Network |
| 898 |
Management of TCP/IP-based internets: |
| 899 |
MIB-II |
| 900 |
|
| 901 |
This memo defines the second version of the Management Information Base |
| 902 |
(MIB-II) for use with network management protocols in TCP/IP-based |
| 903 |
internets. [STANDARDS-TRACK] |
| 904 |
|
| 905 |
|
| 906 |
<span class="h2"><a class="selflink" id="section-1212" href="#section-1212">1212</a> Rose </span> Mar 91 Concise MIB Definitions |
| 907 |
|
| 908 |
This memo describes a straight-forward approach toward producing |
| 909 |
concise, yet descriptive, MIB modules. This memo defines a format for |
| 910 |
producing MIB modules. [STANDARDS-TRACK] |
| 911 |
|
| 912 |
|
| 913 |
<span class="h2"><a class="selflink" id="section-1211" href="#section-1211">1211</a> Westine </span> Mar 91 Problems with the Maintenance of Large |
| 914 |
Mailing Lists |
| 915 |
|
| 916 |
This RFC discusses problems with maintaining large mailing lists, |
| 917 |
especially the processing of error reports. This memo provides |
| 918 |
information for the Internet community. It does not specify an Internet |
| 919 |
standard. |
| 920 |
|
| 921 |
|
| 922 |
<span class="h2"><a class="selflink" id="section-1210" href="#section-1210">1210</a> Cerf </span> Mar 91 Network and Infrastructure User |
| 923 |
Requirements for Transatlantic Research |
| 924 |
Collaboration |
| 925 |
|
| 926 |
This report complements a shorter printed version which appeared in a |
| 927 |
summary report of all the committees which met in Brussels and |
| 928 |
Washington last July, 1990. This memo provides information for the |
| 929 |
Internet community. It does not specify an Internet standard. |
| 930 |
|
| 931 |
|
| 932 |
<span class="h2"><a class="selflink" id="section-1209" href="#section-1209">1209</a> Piscitello </span> Mar 91 The Transmission of IP Datagrams over the |
| 933 |
SMDS Service |
| 934 |
|
| 935 |
This memo defines a protocol for the transmission of IP and ARP packets |
| 936 |
over a Switched Multi-megabit Data Service Network configured as a |
| 937 |
logical IP subnetwork. [STANDARDS-TRACK] |
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Kennedy Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h2"><a class="selflink" id="section-1208" href="#section-1208">1208</a> Jacobsen </span> Mar 91 A Glossary of Networking Terms |
| 954 |
|
| 955 |
This RFC is a glossary adapted from "The INTEROP Pocket Glossary of |
| 956 |
Networking Terms" distributed at Interop '90. This memo provides |
| 957 |
information for the Internet community. It does not specify an Internet |
| 958 |
standard. |
| 959 |
|
| 960 |
|
| 961 |
<span class="h2"><a class="selflink" id="section-1207" href="#section-1207">1207</a> Malkin </span> Feb 91 FYI on Questions and Answers |
| 962 |
Answers to Commonly asked "Experienced |
| 963 |
Internet User" Questions |
| 964 |
|
| 965 |
This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A), |
| 966 |
produced by the User Services Working Group of the Internet Engineering |
| 967 |
Task Force (IETF). The goal is to document the most commonly asked |
| 968 |
questions and answers in the Internet. This memo provides information |
| 969 |
for the Internet community. It does not specify any standard. |
| 970 |
|
| 971 |
|
| 972 |
<span class="h2"><a class="selflink" id="section-1206" href="#section-1206">1206</a> Malkin </span> Feb 91 FYI on Questions and Answers |
| 973 |
Answers to Commonly asked "New |
| 974 |
Internet User" Questions |
| 975 |
|
| 976 |
This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A). |
| 977 |
The goal is to document the most commonly asked questions and answers in |
| 978 |
the Internet. This memo provides information for the Internet community. |
| 979 |
It does not specify any standard. [FYI 4] |
| 980 |
|
| 981 |
|
| 982 |
<span class="h2"><a class="selflink" id="section-1205" href="#section-1205">1205</a> Chmielewski </span>Feb 91 5250 Telnet Interface |
| 983 |
|
| 984 |
This RFC is being distributed in order to document the interface to the |
| 985 |
IBM 5250 Telnet implementation. This memo provides information for the |
| 986 |
Internet community. It does not specify any standard. |
| 987 |
|
| 988 |
|
| 989 |
<span class="h2"><a class="selflink" id="section-1204" href="#section-1204">1204</a> Yeh </span> Feb 91 Message Posting Protocol (MPP) |
| 990 |
|
| 991 |
This memo describes a protocol for posting messages from workstations |
| 992 |
(e.g., PCs) to a mail service host. This RFC specifies an Experimental |
| 993 |
Protocol for the Internet community. It does not specify any standard. |
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Kennedy Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h2"><a class="selflink" id="section-1203" href="#section-1203">1203</a> Rice </span> Feb 91 Interactive Mail Access Protocol |
| 1010 |
- Version 3 |
| 1011 |
|
| 1012 |
This RFC suggests a method for workstations to access mail dynamically |
| 1013 |
from a mailbox server ("repository"). The following document is a |
| 1014 |
modified version of <a href="./rfc1064">RFC 1064</a>, the definition of the IMAP2 protocol. This |
| 1015 |
RFC specifies an Experimental Protocol for the Internet community. It |
| 1016 |
does not specify any standard. |
| 1017 |
|
| 1018 |
|
| 1019 |
<span class="h2"><a class="selflink" id="section-1202" href="#section-1202">1202</a> Rose </span> Feb 91 Directory Assistance Service |
| 1020 |
|
| 1021 |
This document defines a mechanism by which a user-interface may access a |
| 1022 |
textual DAP-like interface over a TCP/IP connection. This is a local |
| 1023 |
mechanism. This memo provides information for the Internet community. |
| 1024 |
It does not specify any standard. |
| 1025 |
|
| 1026 |
|
| 1027 |
<span class="h2"><a class="selflink" id="section-1201" href="#section-1201">1201</a> Provan </span> Feb 91 Transmitting IP Traffic over ARCNET |
| 1028 |
Networks |
| 1029 |
|
| 1030 |
This memo defines a protocol for the transmission of IP and ARP packets |
| 1031 |
over the ARCnet Local Area Network.This memo specifies a method of |
| 1032 |
encapsulating Internet Protocol (IP) and Address Resolution Protocol |
| 1033 |
(ARP) datagrams for transmission across ARCNET using the "ARCNET Packet |
| 1034 |
Header Definition Standard". [STANDARDS-TRACK] |
| 1035 |
|
| 1036 |
|
| 1037 |
<span class="h2"><a class="selflink" id="section-1200" href="#section-1200">1200</a> IAB </span> Apr 91 IAB Official Protocol Standards |
| 1038 |
|
| 1039 |
This memo describes the state of standardization of protocols used in |
| 1040 |
the Internet as determined by the Internet Activities Board (IAB). An |
| 1041 |
overview of the standards procedures is presented first, followed by |
| 1042 |
discussions of the standardization process and the RFC document series, |
| 1043 |
then the explanation of the terms is presented, the lists of protocols |
| 1044 |
in each stage of standardization follows, and finally pointers to |
| 1045 |
references and contacts for further information. |
| 1046 |
|
| 1047 |
|
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Kennedy Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc1299">RFC 1299</a> Summary of 1200-1299 January 1997</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
Security Considerations |
| 1066 |
|
| 1067 |
Security issues are not discussed in this memo. |
| 1068 |
|
| 1069 |
Author's Address |
| 1070 |
|
| 1071 |
Mary Kennedy |
| 1072 |
University of Southern California |
| 1073 |
Information Sciences Institute |
| 1074 |
4676 Admiralty Way |
| 1075 |
Marina del Rey, CA 90292 |
| 1076 |
|
| 1077 |
Phone: (310) 822-1511 |
| 1078 |
|
| 1079 |
EMail: [email protected] |
| 1080 |
|
| 1081 |
|
| 1082 |
|
| 1083 |
|
| 1084 |
|
| 1085 |
|
| 1086 |
|
| 1087 |
|
| 1088 |
|
| 1089 |
|
| 1090 |
|
| 1091 |
|
| 1092 |
|
| 1093 |
|
| 1094 |
|
| 1095 |
|
| 1096 |
|
| 1097 |
|
| 1098 |
|
| 1099 |
|
| 1100 |
|
| 1101 |
|
| 1102 |
|
| 1103 |
|
| 1104 |
|
| 1105 |
|
| 1106 |
|
| 1107 |
|
| 1108 |
|
| 1109 |
|
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
Kennedy Informational [Page 20] |
| 1117 |
</pre> |