1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Network Working Group B. Wijnen
Request for Comments: 3737 Lucent Technologies
Category: Standards Track A. Bierman
Cisco Systems, Inc.
April 2004
<span class="h1">IANA Guidelines for the Registry of</span>
<span class="h1">Remote Monitoring (RMON) MIB modules</span>
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract
This document defines the procedures for IANA to administer and
maintain the Object Identifier (OID) tree under the Remote Monitoring
(rmon) root. This memo also documents the currently assigned values.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The RMONMIB Working Group so far has maintained its own registry for
OID assignments for new MIB modules under the root OID for rmon
[<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]. This has worked reasonably well, although errors had to
be corrected at a late stage one or two times, and a few now defunct
assignments have been made as well.
It is also a somewhat non-standard way of doing things, because
normally a new standards track MIB module will get a MIB root
assigned at the time that the module is being published as part of an
RFC.
This document lists the currently assigned rmon OIDs. It also
describes the procedures and rules for new assignments and asks IANA
to take over the responsibility for existing and future assignments.
The current assignments are not all too logical. Initially normal
MIB OIDs were assigned under rmon, but at a later time the WG used
the rmon root OID to create new MIB modules underneath it. Some
<span class="grey">Wijnen & Bierman Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3737">RFC 3737</a> IANA Guidelines for the RMON Registry April 2004</span>
people will claim 'an OID is just an OID', and while this is true, it
does not make things easier if the organisation of OIDs is not
logical. However, we cannot change what has been assigned in the
past. From now on, only MODULE-IDENTITY macro (MIB root) assignments
will be made (by IANA) under the 'rmon' node. Within a MIB module,
the working group authors/editors can then assign their own OIDs
according to normal procedures.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Currently assigned OIDs under the rmon root</span>
At the time of this writing, the following OIDs have been assigned
and IANA has picked up this information in their public registry of
assigned values. They are listed as part of the already existing
smi-numbers registry at:
<a href="http://www.iana.org/assignments/smi-numbers">http://www.iana.org/assignments/smi-numbers</a>
...mib-2.rmon (1.3.6.1.2.1.16)
The assignments under ...mib-2.rmon were maintained by the RMONMIB
Working Group until publication of <a href="./rfc3737">RFC 3737</a>. Some (early)
assignments may not look all too logical. That is true, but that is
history and cannot be changed. From now on, only MODULE-IDENTITY
macro (MIB root) assignments will be made (by IANA) under the 'rmon'
node.
<span class="grey">Wijnen & Bierman Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3737">RFC 3737</a> IANA Guidelines for the RMON Registry April 2004</span>
Key: nnn == { rmon nnn }
nnn descriptor OID Type Document
0 rmonEventsV2 Notifications root [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
1 statistics OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
2 history OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
3 alarm OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
4 hosts OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
5 hostTopN OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
6 matrix OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
7 filter OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
8 capture OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
9 event OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
10 tokenRing OID [<a href="./rfc1513" title=""Token Ring Extensions to the Remote Network Monitoring MIB"">RFC1513</a>]
11 protocolDir OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
12 protocolDist OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
13 addressMap OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
14 nlHost OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
15 nlMatrix OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
16 alHost OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
17 alMatrix OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
18 usrHistory OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
19 probeConfig OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
20 rmonConformance OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
21 mediaIndependentStats OID [<a href="./rfc3273" title=""Remote Network Monitoring Management Information Base for High Capacity Networks"">RFC3273</a>]
22 switchRMON M-I [<a href="./rfc2613" title=""Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0"">RFC2613</a>]
23 apm M-I [<a href="./rfc3729" title=""Application Performance Measurement MIB"">RFC3729</a>]
24 available
25 pmCapsMIB M-I (defunct)
26 dsmonMIB M-I [<a href="./rfc3287" title=""Remote Monitoring MIB Extensions for Differentiated Services"">RFC3287</a>]
27 interfaceTopNMIB M-I [<a href="./rfc3144" title=""Remote Monitoring MIB Extensions for Interface Parameters Monitoring"">RFC3144</a>]
28 reserved for sspmMIB M-I [..rmonmib-sspm-mib-nn.txt]
29 hcAlarmMIB M-I [<a href="./rfc3434" title=""Remote Monitoring MIB Extensions for High Capacity Alarms"">RFC3434</a>]
30 reserved for tpmMIB M-I [..rmonmib-tpm-mib-nn.txt]
31 reserved for raqmon M-I [..rmonmib-raqmon-mib-nn.txt]
32 reserved for raqmonDs M-I [..rmonmib-raqmon-pdu-nn.txt]
<span class="grey">Wijnen & Bierman Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3737">RFC 3737</a> IANA Guidelines for the RMON Registry April 2004</span>
Key: xxx == { rmon.rmonConformance xxx }
...mib-2.rmon.conformance (1.3.6.1.2.1.16.20)
xxx descriptor OID Type Document
1 rmon2MIBCompliances OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
2 rmon2MIBGroups OID [<a href="./rfc2021" title=""Remote Network Monitoring Management Information Base Version 2 using SMIv2"">RFC2021</a>]
3 smonMIBCompliances OID [<a href="./rfc2613" title=""Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0"">RFC2613</a>]
4 smonMIBGroups OID [<a href="./rfc2613" title=""Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0"">RFC2613</a>]
5 hcRMON M-I [<a href="./rfc3273" title=""Remote Network Monitoring Management Information Base for High Capacity Networks"">RFC3273</a>]
6 hcRmonMIBCompliances OID [<a href="./rfc3273" title=""Remote Network Monitoring Management Information Base for High Capacity Networks"">RFC3273</a>]
7 hcRmonMIBGroups OID [<a href="./rfc3273" title=""Remote Network Monitoring Management Information Base for High Capacity Networks"">RFC3273</a>]
8 rmonMibModule M-I [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
9 rmonCompliances OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
10 rmonGroups OID [<a href="./rfc2819" title=""Remote Network Monitoring Management Information Base"">RFC2819</a>]
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. How to request a new assignment for a MIB module</span>
When anyone is writing a internet-draft for which a new assignment is
needed/wanted under the rmon OID, then the proper way to do so is as
follows:
EXAMPLE-MIB DEFINITIONS ::= BEGIN
IMPORTS
rmon FROM RMON-MIB
.. other imports ..
exampleMIB MODULE-IDENTITY
... other normal MODULE-IDENTITY stuff ...
::= { rmon nnn } -- IANA: please assign nnn
-- RFC-Editor: replace nnn with IANA-assigned
-- number and remove this note
IANA will assign the number as part of the RFC publication process.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This memo describes procedures for IANA assignment of OBJECT
IDENTIFIER values, and has no impact on the security of the Internet.
<span class="grey">Wijnen & Bierman Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3737">RFC 3737</a> IANA Guidelines for the RMON Registry April 2004</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has picked up the initial set of assignments and integrated them
into the existing registry for smi-numbers at:
<a href="http://www.iana.org/assignments/smi-numbers">http://www.iana.org/assignments/smi-numbers</a>
The list is presented in <a href="#section-2">Section 2</a>.
IANA is requested to maintain this registry for future assignments.
New assignments can only be made via Standards Action as described in
[<a href="./rfc2434" title="">RFC2434</a>].
IANA will assign the number as part of the RFC publication process.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span>
This document was produced as a result of discussion between the
Operations and Management AD responsible for Network Management and
the WG chair for the RMONMIB Working Group. Thanks to Andy Bierman
for keeping and administering the registry up to this point in time.
The document has been reviewed by the RMONMIB Working Group.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Normative References</span>
[<a id="ref-RFC1513">RFC1513</a>] Waldbusser, S., "Token Ring Extensions to the Remote
Network Monitoring MIB", <a href="./rfc1513">RFC 1513</a>, September 1993.
[<a id="ref-RFC2021">RFC2021</a>] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 using SMIv2", <a href="./rfc2021">RFC 2021</a>, January
1997.
[<a id="ref-RFC2434">RFC2434</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>,
October 1998.
[<a id="ref-RFC2613">RFC2613</a>] Waterman, R., Lahaye, B., Romascanu, D. and S. Waldbusser,
"Remote Network Monitoring MIB Extensions for Switched
Networks Version 1.0", <a href="./rfc2613">RFC 2613</a>, June 1999.
[<a id="ref-RFC2819">RFC2819</a>] Waldbusser, S., "Remote Network Monitoring Management
Information Base", STD 59, <a href="./rfc2819">RFC 2819</a>, May 2000.
[<a id="ref-RFC3144">RFC3144</a>] Romascanu, D., "Remote Monitoring MIB Extensions for
Interface Parameters Monitoring", <a href="./rfc3144">RFC 3144</a>, August 2001.
<span class="grey">Wijnen & Bierman Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3737">RFC 3737</a> IANA Guidelines for the RMON Registry April 2004</span>
[<a id="ref-RFC3273">RFC3273</a>] Waldbusser, S., "Remote Network Monitoring Management
Information Base for High Capacity Networks", <a href="./rfc3273">RFC 3273</a>,
July 2002.
[<a id="ref-RFC3287">RFC3287</a>] Bierman, A., "Remote Monitoring MIB Extensions for
Differentiated Services", <a href="./rfc3287">RFC 3287</a>, July 2002.
[<a id="ref-RFC3434">RFC3434</a>] Bierman, A. and K. McCloghrie, "Remote Monitoring MIB
Extensions for High Capacity Alarms", <a href="./rfc3434">RFC 3434</a>, December
2002.
[<a id="ref-RFC3729">RFC3729</a>] Waldbusser, S., "Application Performance Measurement
MIB", <a href="./rfc3729">RFC 3729</a>, March 2004.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span>
Bert Wijnen
Lucent Technologies
Schagen 33
3461 GL Linschoten
Netherlands
Phone: +31-348-407-775
EMail: bwijnen@lucent.com
Andy Bierman
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA
USA
Phone: +1-408-527-3711
EMail: abierman@cisco.com
<span class="grey">Wijnen & Bierman Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3737">RFC 3737</a> IANA Guidelines for the RMON Registry April 2004</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed
to pertain to the implementation or use of the technology
described in this document or the extent to which any license
under such rights might or might not be available; nor does it
represent that it has made any independent effort to identify any
such rights. Information on the procedures with respect to
rights in RFC documents can be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository
at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention
any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required
to implement this standard. Please address the information to the
IETF at ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Wijnen & Bierman Standards Track [Page 7]
</pre>
|
