| 1 |
<pre>Network Working Group V. Cerf |
| 2 |
Request for Comments: 1052 NRI |
| 3 |
April 1988 |
| 4 |
|
| 5 |
<span class="h1">IAB Recommendations for the Development of</span> |
| 6 |
<span class="h1">Internet Network Management Standards</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo is intended to convey to the Internet community and other |
| 11 |
interested parties the recommendations of the Internet Activities |
| 12 |
Board (IAB) for the development of network management protocols for |
| 13 |
use in the TCP/IP environment. The memo does NOT, in and of itself, |
| 14 |
define or propose an Official Internet Protocol. It does reflect, |
| 15 |
however, the policy of the IAB with respect to further network |
| 16 |
management development in the short and the long term. Distribution |
| 17 |
of this memo is unlimited. |
| 18 |
|
| 19 |
Background |
| 20 |
|
| 21 |
At the IAB meeting on 21 March 88 in videoconference, the report of |
| 22 |
the Ad Hoc Network Management Review Committee was reviewed. The |
| 23 |
recommendations of the committee were endorsed by the IAB and |
| 24 |
direction given to the chairman of the Internet Engineering Task |
| 25 |
Force to take the necessary steps to implement the recommendations. |
| 26 |
|
| 27 |
The IAB expressed its gratitude for the efforts of the HEMS, SNMP and |
| 28 |
CMIP/CMIS working groups and urged that parties with technical |
| 29 |
interest in the outcome of the network management working groups |
| 30 |
convey their ideas and issues to the relevant working group chairmen. |
| 31 |
|
| 32 |
The IETF chairman was directed to form two new working groups, one of |
| 33 |
which would be responsible for the further specification and |
| 34 |
definition of elements to be included in the Management Information |
| 35 |
Base (MIB). The other would be responsible for defining extensions |
| 36 |
to the Simple Network Management Protocol to accommodate the short- |
| 37 |
term needs of the network vendor and operator communities. The |
| 38 |
longer-term needs of the Internet community are to be met using the |
| 39 |
ISO CMIS/CMIP framework as a basis. A working group of the IETF |
| 40 |
exists for this work and would continue its work, coordinating with |
| 41 |
the two new groups and reporting to the IETF chairman for guidance. |
| 42 |
|
| 43 |
The output of the MIB working group is to be provided to both the |
| 44 |
SNMP working group and the CMIS/CMIP ["Netman"] working group so as |
| 45 |
to assure compatibility of monitored items for both network |
| 46 |
management frameworks. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Cerf [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 55 |
|
| 56 |
|
| 57 |
Specific Recommendations |
| 58 |
|
| 59 |
The IAB recommends that the Simple Network Management Protocol be |
| 60 |
adopted as the BASIS for network management in the short-term. |
| 61 |
Extensions may be required to the existing SNMP specification to |
| 62 |
accommodate additional data types or to deal with functional or |
| 63 |
performance issues arising as multiple SNMP implementations are |
| 64 |
deployed and applied, especially in multi-vendor applications. |
| 65 |
|
| 66 |
The SNMP working group constituted by the IETF is charged with |
| 67 |
considering requirements not met by the present SNMP definition, |
| 68 |
defining extensions, if necessary, to accommodate these needs, and |
| 69 |
preparing revisions of the SNMP specifications to address any new |
| 70 |
extensions. |
| 71 |
|
| 72 |
The IAB urges the working group to be extremely sensitive to the need |
| 73 |
to keep SNMP simple, to work quickly to come to concensus on any |
| 74 |
revisions needed and to promulgate expeditiously the results of its |
| 75 |
work in one or more RFCs within the next 90 days. The IETF chairman |
| 76 |
is responsible for resolving disagreements arising if they cannot be |
| 77 |
resolved within the working group and is instructed to escalate |
| 78 |
problems quickly to the IAB should resolution not be forthcoming. |
| 79 |
|
| 80 |
The IAB further recommends that the MIB working group begin its work |
| 81 |
equally expeditiously, taking as its starting inputs the MIB |
| 82 |
definitions found in the existing High-Level Entity Management |
| 83 |
Systems (HEMS) <a href="./rfc1024">RFC-1024</a>, the SNMP IDEA-11, and CMIS/CMIP IDEAs. |
| 84 |
|
| 85 |
It is the intention of the IAB that the MIB definitions be applied |
| 86 |
both to the SNMP system in the short term and CMIS/CMIP for TCP/IP in |
| 87 |
the longer term. The three working groups will have to coordinate |
| 88 |
their efforts carefully to achieve these objectives: |
| 89 |
|
| 90 |
1. Rapid convergence and definition for SNMP. |
| 91 |
|
| 92 |
2. Rapid convergence and definition for the TCP/IP MIB. |
| 93 |
|
| 94 |
3. Provision for transitioning from SNMP to CMIP/CMIS. |
| 95 |
|
| 96 |
4. Early demonstration of the CMIP/CMIS capability using the |
| 97 |
TCP/IP MIB. |
| 98 |
|
| 99 |
The IAB remains extremely interested in progress towards these goals |
| 100 |
and intends to have representation, whenever possible, in the various |
| 101 |
working group and IETF plenary activities. |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Cerf [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 111 |
|
| 112 |
|
| 113 |
REPORT OF THE AD HOC NETWORK MANAGEMENT REVIEW COMMITTEE |
| 114 |
|
| 115 |
Edited by Vinton Cerf, Chairman |
| 116 |
|
| 117 |
March 1988 |
| 118 |
|
| 119 |
EXECUTIVE SUMMARY |
| 120 |
|
| 121 |
On 29 February 88, an ad hoc committee was convened to review the |
| 122 |
network management options for the Internet in particular and the |
| 123 |
TCP/IP protocol suite in general. This meeting was called at the |
| 124 |
request of the Internet Activities Board in the course of exercising |
| 125 |
its responsibilities to the Federal Research Internet Coordinating |
| 126 |
Council (FRICC) and by the MITRE Corporation as a consequence of its |
| 127 |
work for the U.S. Air Force on the ULANA project. |
| 128 |
|
| 129 |
At the conclusion of the one day meeting, it was agreed that the |
| 130 |
following recommendations be forwarded to the Internet Activities |
| 131 |
Board chairman, Dr. David C. Clark, for consideration at the next IAB |
| 132 |
meeting scheduled for 21 March: |
| 133 |
|
| 134 |
1. In the short term, the Internet community should adopt and |
| 135 |
adapt the Simple Network Management Protocol (SNMP) for use as the |
| 136 |
basis of common network management throughout the system. |
| 137 |
|
| 138 |
(Rationale: The software is available and in operation.) |
| 139 |
|
| 140 |
2. In the longer term, the Internet research community and the |
| 141 |
vendors should develop, deploy and test a network management |
| 142 |
system based on the International Standards Organization (ISO) |
| 143 |
Common Management Information Services/Common Management |
| 144 |
Information Protocol (CMIS/CMIP). |
| 145 |
|
| 146 |
(Rationale: The Internet community can take the high ground in |
| 147 |
protocol development by virtue of the experimental environment in |
| 148 |
which it can operate. Recommendations to the ISO from this |
| 149 |
community, the IAB and the vendors will carry great weight if they |
| 150 |
are in the language of the ISO common network management system |
| 151 |
and if they are rooted in actual experience with implementation |
| 152 |
and use in the field.) |
| 153 |
|
| 154 |
3. Responsibility for the SNMP effort should be placed in the |
| 155 |
hands of an IETF task force. |
| 156 |
|
| 157 |
(Rationale: Eliminate vendor-specific bias or control over the |
| 158 |
SNMP and its evolution and harmonize inputs from the Internet |
| 159 |
community.) |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Cerf [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 167 |
|
| 168 |
|
| 169 |
4. As a high priority effort, define an extended Management |
| 170 |
Information Base (MIB) for SNMP and TCP/IP CMIP to bring them into |
| 171 |
closer conformance with the MIB defined for the experimental |
| 172 |
HighLevel Entity Management System (HEMS). |
| 173 |
|
| 174 |
(Rationale: The HEMS effort produced a very thorough and widely- |
| 175 |
discussed set of elements to monitor, along with definitions of |
| 176 |
the semantics of these elements. The current SNMP definitions are |
| 177 |
more restricted and the CMIP definitions less precise. |
| 178 |
Implementation of SNMP in a timely and useful fashion through the |
| 179 |
Internet cannot be satisfactorily completed without such a |
| 180 |
definition of information elements in hand.) |
| 181 |
|
| 182 |
The ad hoc committee therefore recommends immediate action by the |
| 183 |
IAB on all four of these points. It should be noted that this |
| 184 |
resolution would not have been possible in such a timely way |
| 185 |
without the statesman-like efforts of Craig Partridge who, at the |
| 186 |
end of the day, recommended that the HEMS effort be withdrawn from |
| 187 |
consideration so as to pave the way for an Internet-wide |
| 188 |
agreement. In consideration of this unselfish act, the ad hoc |
| 189 |
committee urges the IAB to approve the recommendations above and |
| 190 |
to instruct the IETF to move quickly to accept and act on the SNMP |
| 191 |
items requiring completion. |
| 192 |
|
| 193 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. INTRODUCTION</span> |
| 194 |
|
| 195 |
During its development history, the community of researchers, |
| 196 |
developers, implementors and users of the DARPA/DoD TCP/IP protocol |
| 197 |
suite have experimented with a wide range of protocols in a variety |
| 198 |
of different networking environments. The Internet has grown, |
| 199 |
especially in the last few years, as a result of the widespread |
| 200 |
availability of software and hardware supporting this system. The |
| 201 |
scaling of the size and scope of the Internet and increased use of |
| 202 |
its technology in commercial applications has underscored for |
| 203 |
researchers, developers and vendors the need for a common network |
| 204 |
management framework within which TCP/IP products can be made to |
| 205 |
work. |
| 206 |
|
| 207 |
In recognition of this need, several efforts were started to develop |
| 208 |
network management concepts which might be applied to the Internet |
| 209 |
and to the internet technology in general. Three of these efforts |
| 210 |
had made sufficient progress by the end of 1987 that it became clear |
| 211 |
that some choices had to be made or the community would find itself |
| 212 |
with a set of incompatible network management tools. These efforts |
| 213 |
included the High-Level Entity Management System (HEMS), the Simple |
| 214 |
Gateway Monitoring Protocol (SGMP) and the Common Management |
| 215 |
Information Service/Protocol. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Cerf [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 223 |
|
| 224 |
|
| 225 |
The latter is an ISO initiative which was adapted to Internet use in |
| 226 |
a vendor-initiated effort. The HEMS work was carried out in the |
| 227 |
context of the Gateway Monitoring group of the Internet Engineering |
| 228 |
Task Force. The SGMP effort was carried out largely in the practical |
| 229 |
context of the NYSERNET and SURAnet regional networks which needed |
| 230 |
network management facilities to operate satisfactorily. |
| 231 |
|
| 232 |
Independent of the general Internet situation and requirements, the |
| 233 |
U.S. Air Force has been pursuing a Universal Local Area Network |
| 234 |
Architecture (ULANA) for its own use. The principal agent for the |
| 235 |
development of the ULANA specifications is the MITRE Corporation. |
| 236 |
Faced with several long and short term network management options, |
| 237 |
the MITRE ULANA specification team initiated an effort with |
| 238 |
substantial vendor participation called the NETMAN working group. |
| 239 |
|
| 240 |
It was against this fabric of various options that the IAB appointed |
| 241 |
a chairman to convene a review committee to discuss these various |
| 242 |
options and to make recommendations on long and short term choices. |
| 243 |
The MITRE Corporation co-sponsored this work to further its aims in |
| 244 |
the specification of the ULANA design. |
| 245 |
|
| 246 |
Reference material listed at the end of this report was provided in |
| 247 |
advance of the meeting. |
| 248 |
|
| 249 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. DISCUSSION</span> |
| 250 |
|
| 251 |
Rather than attempting to produce minutes of the meeting, this |
| 252 |
section summarizes in very high level terms the substance of the |
| 253 |
discussion which took place during most of the meeting. Presentation |
| 254 |
viewgraphs can be made available to IAB/FRICC members interested in |
| 255 |
their contents. |
| 256 |
|
| 257 |
The agenda was followed fairly closely with the technical |
| 258 |
presentations made in the order suggested: HEMS, SGMP, CMIP/CMIS. |
| 259 |
|
| 260 |
The HEMS effort has established a benchmark for other network |
| 261 |
management work in the sense that it took a comprehensive conceptual |
| 262 |
view of the problem and went into considerable detail on the design |
| 263 |
of the underlying management information database, the mechanics of |
| 264 |
access to and reporting of information, considerations of scaling and |
| 265 |
performance (e.g., Query Language vs Remote Procedure Call style), |
| 266 |
definition of information required and so on. HEMS has been |
| 267 |
implemented in an experimental version from which some encouraging |
| 268 |
performance measurements were taken. Serious vendor interest in this |
| 269 |
protocol was expressed by Cisco Systems and implementation efforts |
| 270 |
were under way as of the meeting. |
| 271 |
|
| 272 |
The SGMP effort, though somewhat less documented, was rooted in a |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Cerf [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 279 |
|
| 280 |
|
| 281 |
practical need for network management tools for the NYSERNET, |
| 282 |
SURAnet, and, by extension, other components of the Internet. |
| 283 |
Implementations of it exist, in its <a href="./rfc1028">RFC-1028</a> form (probably with some |
| 284 |
experimental extensions based on experience gained from the initial |
| 285 |
work), and are in use today. Serious vendor support for this work is |
| 286 |
found at Proteon and, more recently, in the NSFNET effort by MERIT, |
| 287 |
IBM and MCI, specifically in the IBM Network Switching System (NSS) |
| 288 |
nodes. Applications running above SGMP exist and provide useful |
| 289 |
monitoring information, presented in easily grasped form. |
| 290 |
|
| 291 |
The ISO CMIS/CMIP effort, voluminously documented, has had almost no |
| 292 |
implementation as yet. Reports from Unisys/SDC about an experimental |
| 293 |
implementation were heard at the meeting. There is substantial |
| 294 |
momentum in the international community for the adoption of this |
| 295 |
service and protocol suite for network management. The Draft |
| 296 |
Proposal is out for its second ballot (it failed to make Draft |
| 297 |
International Standard on its first ballot). There is vocal vendor |
| 298 |
support for this work, based on the premise that ultimately the ISO |
| 299 |
protocol suite will propagate and the vendors must support it. |
| 300 |
|
| 301 |
In general, all of the network management proposals make use of the |
| 302 |
Abstract Syntax Notation 1 (ASN.1) which has emerged from the ISO |
| 303 |
efforts as a kind of lingua franca for the representation of |
| 304 |
arbitrary data structures. The data types used in the SGMP |
| 305 |
Management Information Base (aspects of network components to be |
| 306 |
monitored) are the most restricted of the three proposals, confined |
| 307 |
to integers and octet strings only. HEMS has the most extensive |
| 308 |
Management Information Base and added some rather unique ideas such |
| 309 |
as self-knowledge about what could be monitored so that a |
| 310 |
device/unit/component could respond to a query asking "what can you |
| 311 |
tell me about yourself and your operation and how is it represented?" |
| 312 |
(!). CMIS/CMIP is probably the broadest in scope, but less precisely |
| 313 |
defined at this point, with respect to information which should be |
| 314 |
monitored. The draft RFCs referenced above relating to the CMIS/CMIP |
| 315 |
concerning items to be monitored are still in the definition stages. |
| 316 |
|
| 317 |
A point made strongly by the HEMS team was their concern that a |
| 318 |
Remote Operations basis for CMIP may not scale well into a very large |
| 319 |
Internet which needs to be monitored from a few central sites. |
| 320 |
Remote Operations is a term used by ISO and means, roughly, what the |
| 321 |
Internet community has long referred to as Remote Procedure Calls. |
| 322 |
If each atomic action is a Remote Procedure Call, the HEMS team |
| 323 |
argues that increasing Internet size and potential delays may vastly |
| 324 |
constrain the amount and timeliness of information which can be |
| 325 |
collected. The HEMS design uses, instead, a general query language |
| 326 |
approach which permits more elaborate, multi-variable queries to be |
| 327 |
formulated at the requesting site and processed at the responding |
| 328 |
site(s). |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Cerf [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 335 |
|
| 336 |
|
| 337 |
Although it does substantial injustice to the very lucid and helpful |
| 338 |
presentations by representatives of each of the network management |
| 339 |
research groups, I have chosen to leave out much of the detail from |
| 340 |
this report and move directly to the points of agreement which were |
| 341 |
reached by the Committee. |
| 342 |
|
| 343 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. POINTS OF AGREEMENT</span> |
| 344 |
|
| 345 |
(i) Future Internet development is a joint interest of the R&D |
| 346 |
community, the vendor community and the user community. |
| 347 |
|
| 348 |
[Editor's comment: The development of the Internet is now not only |
| 349 |
dependent on research work, but on the hardware and software of |
| 350 |
vendors selling to both commercial ("internet") and the research |
| 351 |
environment ("Internet"). Moreover, the Internet users are not all |
| 352 |
concerned with network research; many of the components of the |
| 353 |
Internet are based on vendor-supplied and supported subsystems.] |
| 354 |
|
| 355 |
(ii) We still don't have a common understanding of what |
| 356 |
[Inter]Network Management really is. |
| 357 |
|
| 358 |
[Editor's comment: We haven't tried to manage the Internet as a |
| 359 |
collection of autonomous systems in an effective way, yet.] |
| 360 |
|
| 361 |
(iii) We will learn what [Inter]Network Management is by doing it. |
| 362 |
|
| 363 |
(a) in as large a scale as is possible |
| 364 |
|
| 365 |
(b) with as much diversity of implementation as possible |
| 366 |
|
| 367 |
(c) over as wide a range of protocol layers as possible |
| 368 |
|
| 369 |
(d) with as much administrative diversity as we can stand. |
| 370 |
|
| 371 |
(iv) There are more than HEMS, SGMP and CMIS/CMIP as potential |
| 372 |
candidates: |
| 373 |
|
| 374 |
HEMS, SGMP, CMIS/CMIP [multiple profiles], NETVIEW, |
| 375 |
LANMANAGER, Network Computing Forum "Fat Document"... |
| 376 |
|
| 377 |
[Editor's comment: The multiplicity of options is motivation for |
| 378 |
coalescing the energy of the Internet environment around single short |
| 379 |
and long term foci so as to make more substantial progress in really |
| 380 |
understanding network management per point (iii).] |
| 381 |
|
| 382 |
(v) Define the Management Information Base for TCP/IP suite NOW! |
| 383 |
|
| 384 |
(vi) Seek a seat for IETF on ANSI, ISO and/or CCITT!!! |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Cerf [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 391 |
|
| 392 |
|
| 393 |
[Editor's comment: This may actually be feasible.] |
| 394 |
|
| 395 |
(vii) Define a CMIS interface to any of the surviving network |
| 396 |
management schemes so as to provide a migration path to ISO. |
| 397 |
|
| 398 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. RESOLUTION AND CONCLUSIONS</span> |
| 399 |
|
| 400 |
In a dramatic act of statesmanship, Craig Partridge volunteered that |
| 401 |
the HEMS proposal be dropped in favor of the other two efforts, SGMP |
| 402 |
and CMIS/CMIP - IF THIS WOULD LEAD TO INTERNET-WIDE AGREEMENT ON A |
| 403 |
NETWORK MANAGEMENT PLAN FOR THE SHORT AND LONG TERM. |
| 404 |
|
| 405 |
A rationale for the long term was proposed, based on the assumption |
| 406 |
that the ISO initiatives, and the U.S. Government issuance of the |
| 407 |
GOSIP guidelines, would ultimately require at least the Government |
| 408 |
users, and hence their vendor suppliers, to use ISO-based protocols |
| 409 |
and tools. In this rationale, the Internet research community and its |
| 410 |
vendors would "take the high ground" in network management by |
| 411 |
implementing the CMIS/CMIP on top of the TCP/IP protocol suite and |
| 412 |
deploy it widely for experimental use in the Internet. |
| 413 |
|
| 414 |
Neither the ISO nor any other organization, including the Corporation |
| 415 |
for Open Systems (COS) has anything close to the laboratory in large |
| 416 |
that the Internet represents. By taking the initiative, the Internet |
| 417 |
working groups can establish credibility based on experience which |
| 418 |
will make it far more feasible to affect the evolution of the ISO |
| 419 |
network management and other related efforts. The Internet community |
| 420 |
will be able to speak with authority about problems with the design |
| 421 |
or definition of CMIS/CMIP based on real implementation experience |
| 422 |
and use, rather than solely analytic means. |
| 423 |
|
| 424 |
In the short term, however, the Internet desperately needs tools to |
| 425 |
apply to the operational management problems associated with its |
| 426 |
rapid growth. Given the present state of advanced implementation of |
| 427 |
the SGMP and its relative simplicity, the general agreement was that |
| 428 |
SGMP (or its re-named successor, SNMP) should be quickly brought to |
| 429 |
more complete specification for widespread implementation and use. |
| 430 |
|
| 431 |
In short, the ad hoc committee recommends: |
| 432 |
|
| 433 |
1. In the short term, the Internet community should adopt and |
| 434 |
adapt the Simple Network Management Protocol (SNMP) for use as the |
| 435 |
basis of common network management throughout the system. |
| 436 |
|
| 437 |
(Rationale: The software is available and in operation.) |
| 438 |
|
| 439 |
2. In the longer term, the Internet research community and the |
| 440 |
vendors should develop, deploy and test a network management |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Cerf [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 447 |
|
| 448 |
|
| 449 |
system based on the International Standards Organization (ISO) |
| 450 |
Common Management Information Services/Common Management |
| 451 |
Information Protocol (CMIS/CMIP). |
| 452 |
|
| 453 |
(Rationale: The Internet community can take the high ground in |
| 454 |
protocol development by virtue of the experimental environment in |
| 455 |
which it can operate. Recommendations to the ISO from this |
| 456 |
community, the IAB and the vendors will carry great weight if they |
| 457 |
are in the language of the ISO common network management system |
| 458 |
and if they are rooted in actual experience with implementation |
| 459 |
and use in the field.) |
| 460 |
|
| 461 |
3. Responsibility for the SNMP effort should be placed in the |
| 462 |
hands of an IETF task force. |
| 463 |
|
| 464 |
(Rationale: Eliminate vendor-specific bias or control over the |
| 465 |
SNMP and its evolution and harmonize inputs from the Internet |
| 466 |
community.) |
| 467 |
|
| 468 |
4. As a high priority effort, define an extended Management |
| 469 |
Information Base (MIB) for SNMP and TCP/IP CMIP to bring them into |
| 470 |
closer conformance with the MIB defined for the experimental |
| 471 |
HighLevel Entity Management System (HEMS). (Rationale: |
| 472 |
The HEMS effort produced a very thorough and widely-discussed set |
| 473 |
of elements to monitor, along with definitions of the semantics of |
| 474 |
these elements. The current SNMP definitions are more restricted |
| 475 |
and the CMIP definitions less precise. Implementation of SNMP in a |
| 476 |
timely and useful fashion through the Internet cannot be |
| 477 |
satisfactorily completed without such a definition of information |
| 478 |
elements in hand.) |
| 479 |
|
| 480 |
|
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Cerf [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 503 |
|
| 504 |
|
| 505 |
MEMBERS OF THE AD HOC NET MANAGEMENT REVIEW COMMITTEE |
| 506 |
|
| 507 |
Amatzia Ben-Artzi |
| 508 |
Sytek Corp. |
| 509 |
1225 Charleston Rd. |
| 510 |
Mountain View, CA 94043 |
| 511 |
[email protected] |
| 512 |
|
| 513 |
Bob Braden |
| 514 |
USC-ISI |
| 515 |
4676 Admiralty Way |
| 516 |
Marina del Rey, CA 90292 |
| 517 |
[email protected] |
| 518 |
|
| 519 |
Jeff Case |
| 520 |
University of Tennessee |
| 521 |
200 Stokely Management Center |
| 522 |
Knoxville, TN 37996 |
| 523 |
[email protected] |
| 524 |
|
| 525 |
Vint Cerf - Chairman |
| 526 |
Corp. for National Research Initiatives |
| 527 |
1895 Preston White Dr., Suite 100 |
| 528 |
Reston, VA 22091 |
| 529 |
(703) 620-8990 |
| 530 |
[email protected] |
| 531 |
|
| 532 |
Chuck Davin |
| 533 |
Proteon, Inc. |
| 534 |
2 Technology Dr. |
| 535 |
Westborough, MA 01536 |
| 536 |
[email protected] |
| 537 |
|
| 538 |
Stephen Dunford |
| 539 |
UNISYS Corp. |
| 540 |
System Development Corporation |
| 541 |
5151 Camino Road |
| 542 |
Camarillo, CA 93010 |
| 543 |
[email protected] |
| 544 |
|
| 545 |
Mark Fedor |
| 546 |
NYSERNET |
| 547 |
125 Jordan Road |
| 548 |
Troy, NY 12180 |
| 549 |
[email protected] |
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Cerf [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 559 |
|
| 560 |
|
| 561 |
Phill Gross - IETF Chairman |
| 562 |
MITRE Corporation |
| 563 |
1820 Dolley Madison Blvd. |
| 564 |
McLean, VA 22012 |
| 565 |
[email protected] |
| 566 |
|
| 567 |
Lee LaBarre |
| 568 |
MITRE Corporation |
| 569 |
Burlington Road |
| 570 |
Bedford, MA 01730 |
| 571 |
[email protected] |
| 572 |
|
| 573 |
Dan Lynch |
| 574 |
Advanced Computing Environments |
| 575 |
480 San Antonio Rd. |
| 576 |
Mountain View, CA 94040 |
| 577 |
[email protected] |
| 578 |
|
| 579 |
Jim Mathis |
| 580 |
Apple Computer, Inc. |
| 581 |
MS 27-0 |
| 582 |
20525 Mariani Ave. |
| 583 |
Cupertino, CA 95014 |
| 584 |
[email protected] |
| 585 |
|
| 586 |
Craig Partridge |
| 587 |
BBN Labs |
| 588 |
10 Moulton St. |
| 589 |
Cambridge, MA 02238 |
| 590 |
[email protected] |
| 591 |
|
| 592 |
Marshall T. Rose |
| 593 |
The Wollongong Group, Inc. |
| 594 |
1129 San Antonio Road |
| 595 |
Palo Alto, CA 94043 |
| 596 |
[email protected] |
| 597 |
|
| 598 |
Greg Satz |
| 599 |
Cisco Systems |
| 600 |
1360 Willow Rd., Suite 201 |
| 601 |
Menlo Park, CA 94301 |
| 602 |
[email protected] |
| 603 |
|
| 604 |
Martin Lee Schoffstall |
| 605 |
NYSERNET |
| 606 |
125 Jordan Road |
| 607 |
Troy, NY 12180 |
| 608 |
[email protected] |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Cerf [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 615 |
|
| 616 |
|
| 617 |
Glenn Trewitt |
| 618 |
Center for Integrated Systems, Room 216 |
| 619 |
Stanford University |
| 620 |
Stanford, CA 94305 |
| 621 |
[email protected] |
| 622 |
|
| 623 |
MEETING LOCATION: San Diego Supercomputer Center, UC San Diego |
| 624 |
|
| 625 |
LOCAL ARRANGEMENTS: Paul Love, SDSC |
| 626 |
|
| 627 |
MEETING DATE: 29 February 1988 |
| 628 |
|
| 629 |
AGENDA ITEMS: |
| 630 |
|
| 631 |
0900 Introductions and Objectives/Cerf |
| 632 |
|
| 633 |
0915 HEMS: Craig Partridge and Glenn Trewitt |
| 634 |
|
| 635 |
1030 Break |
| 636 |
|
| 637 |
1045 SGMP - Jeff Case |
| 638 |
|
| 639 |
1145 CMIP/CMIS - Amatzia Ben-Artzi |
| 640 |
|
| 641 |
1245 Lunch Break |
| 642 |
|
| 643 |
1430 TCP/IP and ISO: Politics, Technology, Penetration/Cerf |
| 644 |
|
| 645 |
1530 Break |
| 646 |
|
| 647 |
1545 Tradeoffs among alternate paths (Discussion) |
| 648 |
|
| 649 |
1700 Resolution of alternatives |
| 650 |
|
| 651 |
1730 Summary of conclusions/actions |
| 652 |
|
| 653 |
1800 Adjourn |
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Cerf [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 671 |
|
| 672 |
|
| 673 |
REFERENCES |
| 674 |
|
| 675 |
The following reference material was provided in advance of the |
| 676 |
meeting. Note that some of the citations include informal |
| 677 |
descriptors (such as IDEA numbers or DRAFT letter codes), for |
| 678 |
example, IDEA-13 or DRAFT-AAAA. IDEA notes may be updated from time |
| 679 |
to time reusing the same number. The IDEA notes are the working |
| 680 |
notes of the Engineering Task Force. The DRAFT is a temporary |
| 681 |
notation and may not be meaningful for more than a few months. |
| 682 |
|
| 683 |
HEMS |
| 684 |
|
| 685 |
(1) Craig Partridge, "A UNIX Implementation of HEMS", USENIX, |
| 686 |
February 1988. [Available from C. Partridge, BBN Labs] |
| 687 |
|
| 688 |
(2) Craig Partridge and Glenn Trewitt, "The High-Level Entity |
| 689 |
Management System", <a href="./rfc1021">RFC-1021</a>. |
| 690 |
|
| 691 |
(3) Craig Partridge and Glenn Trewitt, "The High-Level Entity |
| 692 |
Management Protocol", <a href="./rfc1022">RFC-1022</a>. |
| 693 |
|
| 694 |
(4) Glenn Trewitt and Craig Partridge, "The HEMS Monitoring and |
| 695 |
Control Language", <a href="./rfc1023">RFC-1023</a>. |
| 696 |
|
| 697 |
(5) Craig Partridge and Glenn Trewitt, "HEMS Variable |
| 698 |
Definitions", <a href="./rfc1024">RFC-1024</a>. |
| 699 |
|
| 700 |
(6) Craig Partridge and Glenn Trewitt, "The High-Level Entity |
| 701 |
Management System", IEEE Network magazine, March 1988. |
| 702 |
|
| 703 |
SGMP/SNMP |
| 704 |
|
| 705 |
(1) James Davin, Jeff Case, Mark Fedor and Martin Schoffstall, "A |
| 706 |
Simple Gateway Monitoring Protocol", <a href="./rfc1028">RFC-1028</a>, November 1987. |
| 707 |
|
| 708 |
(2) James Davin, Jeff Case, Mark Fedor and Martin Schoffstall, "A |
| 709 |
Simple Network Management Protocol", IDEA-11, February 1988, |
| 710 |
obsoletes <a href="./rfc1028">RFC-1028</a> when issued. |
| 711 |
|
| 712 |
(3) Jeffrey R. Case, James R. Davin, Mark S. Fedor, Martin L. |
| 713 |
Schoffstall, "Introduction to the Simple Gateway Monitoring |
| 714 |
Protocol", IEEE Network Magazine, March 1988. |
| 715 |
|
| 716 |
CMIS/CMIP |
| 717 |
|
| 718 |
(1) Amatzia Ben-Artzi, "Network Management for TCP/IP Network: An |
| 719 |
Overview", IDEA-12, February 1988. |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Cerf [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc1052">RFC 1052</a> Internet Management April 1988</span> |
| 727 |
|
| 728 |
|
| 729 |
(2) Lee LaBarre, " TCP/IP Network Management Implementors |
| 730 |
Agreements", IDEA-13, January 1988. |
| 731 |
|
| 732 |
(3) Lee LaBarre, "Data Link Layer Management Information: |
| 733 |
MAC802.3", DRAFT-MMMM, February 1988. |
| 734 |
|
| 735 |
(4) Lee LaBarre, "Network Layer Management Information: IP", |
| 736 |
DRAFT-NNNN, February 1988. |
| 737 |
|
| 738 |
(5) Marshall Rose, "ISO Presentation Services on Top of TCP/IP- |
| 739 |
based Internets", DRAFT-PPPP, February 1988. |
| 740 |
|
| 741 |
(6) Lee LaBarre, "Structure and Identification of Management |
| 742 |
Information for the Internet", DRAFT-SMI, February 1988. |
| 743 |
|
| 744 |
(7) Lee LaBarre, "Transport Layer Management Information: TCP", |
| 745 |
DRAFT-TTTT, February 1988. |
| 746 |
|
| 747 |
(8) Lee LaBarre, "Transport Layer Management Information: UDP", |
| 748 |
DRAFT-UUUU, February 1988. |
| 749 |
|
| 750 |
(9) ISO/IEC JTC 1/21 N 2058, "2nd DP 9595-1 Information Processing |
| 751 |
Systems - Open Systems Interconnection - Management Information |
| 752 |
Service Definition - Part 1: Overview", December 1987. |
| 753 |
|
| 754 |
(10) ISO/IEC JTC 1/21 N 2059, "2nd DP 9595-2, Information |
| 755 |
Processing Systems - Open Systems Interconnection - Management |
| 756 |
Information Service Definition - Part 2: Common Management |
| 757 |
Information Service Definition", December 1987. |
| 758 |
|
| 759 |
(11) ISO/IEC JTC 1/21 N 2060, "2nd DP 9596-2, Information |
| 760 |
Processing Systems - Open Systems Interconnection - Management |
| 761 |
Information Protocol Specification - Part 2: Common Management |
| 762 |
Information Protocol", December 1987. |
| 763 |
|
| 764 |
(12) ISO/TC97/SC21/WG4 N 472, "US Comments on the Proposal for |
| 765 |
Extension of the Common Management Information Services and |
| 766 |
Protocol: Creation and Deletion Functions", November 1987. |
| 767 |
|
| 768 |
(13) JTC1/SC21/WG4 N 482, "Proposal to extend M-Set and M- |
| 769 |
Confirmed-Set to allow adding and removing values of a multi- |
| 770 |
valued attribute", November 1987. |
| 771 |
|
| 772 |
(14) S. Mark Klerer, "The OSI Management Architecture: An |
| 773 |
Overview", IEEE Network Magazine, March 1988. |
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
Cerf [Page 14] |
| 781 |
</pre> |