Debian Codegraph @

rfc2074.html

raw
1 <pre>Network Working Group A. Bierman
2 Request for Comments: 2074 Cisco Systems
3 Category: Standards Track R. Iddon
4 AXON Networks,Inc.
5 January 1997
6
7
8 <span class="h1">Remote Network Monitoring MIB Protocol Identifiers</span>
9
10 Status of this Memo
11
12 This document specifies an Internet standards track protocol for the
13 Internet community, and requests discussion and suggestions for
14 improvements. Please refer to the current edition of the "Internet
15 Official Protocol Standards" (STD 1) for the standardization state
16 and status of this protocol. Distribution of this memo is unlimited.
17
18 Table of Contents
19
20 <a href="#section-1">1</a> Introduction .................................................... <a href="#page-3">3</a>
21 <a href="#section-2">2</a> The SNMP Network Management Framework ........................... <a href="#page-3">3</a>
22 <a href="#section-2.1">2.1</a> Object Definitions ............................................ <a href="#page-3">3</a>
23 <a href="#section-3">3</a> Overview ........................................................ <a href="#page-3">3</a>
24 <a href="#section-3.1">3.1</a> Terms ......................................................... <a href="#page-4">4</a>
25 <a href="#section-3.2">3.2</a> Relationship to the Remote Network Monitoring MIB ............. <a href="#page-6">6</a>
26 <a href="#section-3.3">3.3</a> Relationship to the Other MIBs ................................ <a href="#page-6">6</a>
27 <a href="#section-4">4</a> Protocol Identifier Encoding .................................... <a href="#page-7">7</a>
28 <a href="#section-4.1">4.1</a> ProtocolDirTable INDEX Format Examples ........................ <a href="#page-9">9</a>
29 <a href="#section-4.2">4.2</a> Protocol Identifier Macro Format .............................. <a href="#page-10">10</a>
30 <a href="#section-4.2.1">4.2.1</a> Mapping of the Protocol Name ................................ <a href="#page-12">12</a>
31 <a href="#section-4.2.2">4.2.2</a> Mapping of the VARIANT-OF Clause ............................ <a href="#page-13">13</a>
32 <a href="#section-4.2.3">4.2.3</a> Mapping of the PARAMETERS Clause ............................ <a href="#page-13">13</a>
33 <a href="#section-4.2.3.1">4.2.3.1</a> Mapping of the 'countsFragments(0)' BIT ................... <a href="#page-14">14</a>
34 <a href="#section-4.2.3.2">4.2.3.2</a> Mapping of the 'tracksSessions(1)' BIT .................... <a href="#page-15">15</a>
35 <a href="#section-4.2.4">4.2.4</a> Mapping of the ATTRIBUTES Clause ............................ <a href="#page-15">15</a>
36 <a href="#section-4.2.5">4.2.5</a> Mapping of the DESCRIPTION Clause ........................... <a href="#page-15">15</a>
37 <a href="#section-4.2.6">4.2.6</a> Mapping of the CHILDREN Clause .............................. <a href="#page-16">16</a>
38 <a href="#section-4.2.7">4.2.7</a> Mapping of the ADDRESS-FORMAT Clause ........................ <a href="#page-16">16</a>
39 <a href="#section-4.2.8">4.2.8</a> Mapping of the DECODING Clause .............................. <a href="#page-16">16</a>
40 <a href="#section-4.2.9">4.2.9</a> Mapping of the REFERENCE Clause ............................. <a href="#page-17">17</a>
41 <a href="#section-4.2.10">4.2.10</a> Evaluating a Protocol-Identifier INDEX ..................... <a href="#page-17">17</a>
42 <a href="#section-5">5</a> Protocol Identifier Macros ...................................... <a href="#page-18">18</a>
43 <a href="#section-5.1">5.1</a> Base Identifier Encoding ...................................... <a href="#page-18">18</a>
44 <a href="#section-5.1.1">5.1.1</a> Protocol Identifier Functions ............................... <a href="#page-19">19</a>
45 <a href="#section-5.1.1.1">5.1.1.1</a> Function 0: No-op ......................................... <a href="#page-19">19</a>
46 <a href="#section-5.1.1.2">5.1.1.2</a> Function 1: Protocol Wildcard Function .................... <a href="#page-19">19</a>
47 <a href="#section-5.2">5.2</a> Base Layer Protocol Identifiers ............................... <a href="#page-20">20</a>
48 <a href="#section-5.2.1">5.2.1</a> Ether2 Encapsulation ........................................ <a href="#page-21">21</a>
49
50
51
52 <span class="grey">Bierman &amp; Iddon Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
55
56
57 <a href="#section-5.2.2">5.2.2</a> LLC Encapsulation ........................................... <a href="#page-22">22</a>
58 <a href="#section-5.2.3">5.2.3</a> SNAP over LLC (OUI=000) Encapsulation ....................... <a href="#page-23">23</a>
59 <a href="#section-5.2.4">5.2.4</a> SNAP over LLC (OUI != 000) Encapsulation .................... <a href="#page-24">24</a>
60 <a href="#section-5.2.5">5.2.5</a> IANA Assigned Protocols ..................................... <a href="#page-25">25</a>
61 <a href="#section-5.2.5.1">5.2.5.1</a> IANA Assigned Protocol Identifiers ........................ <a href="#page-27">27</a>
62 <a href="#section-5.3">5.3</a> L3: Children of Base Protocol Identifiers ..................... <a href="#page-27">27</a>
63 <a href="#section-5.3.1">5.3.1</a> IP .......................................................... <a href="#page-28">28</a>
64 <a href="#section-5.3.2">5.3.2</a> IPX ......................................................... <a href="#page-29">29</a>
65 <a href="#section-5.3.3">5.3.3</a> ARP ......................................................... <a href="#page-30">30</a>
66 <a href="#section-5.3.4">5.3.4</a> IDP ......................................................... <a href="#page-30">30</a>
67 <a href="#section-5.3.5">5.3.5</a> AppleTalk ARP ............................................... <a href="#page-31">31</a>
68 <a href="#section-5.3.6">5.3.6</a> AppleTalk ................................................... <a href="#page-31">31</a>
69 <a href="#section-5.4">5.4</a> L4: Children of L3 Protocols .................................. <a href="#page-32">32</a>
70 <a href="#section-5.4.1">5.4.1</a> ICMP ........................................................ <a href="#page-32">32</a>
71 <a href="#section-5.4.2">5.4.2</a> TCP ......................................................... <a href="#page-32">32</a>
72 <a href="#section-5.4.3">5.4.3</a> UDP ......................................................... <a href="#page-33">33</a>
73 <a href="#section-5.5">5.5</a> L5: Application Layer Protocols ............................... <a href="#page-33">33</a>
74 <a href="#section-5.5.1">5.5.1</a> FTP ......................................................... <a href="#page-33">33</a>
75 <a href="#section-5.5.1.1">5.5.1.1</a> FTP-DATA .................................................. <a href="#page-33">33</a>
76 <a href="#section-5.5.1.2">5.5.1.2</a> FTP Control ............................................... <a href="#page-34">34</a>
77 <a href="#section-5.5.2">5.5.2</a> Telnet ...................................................... <a href="#page-34">34</a>
78 <a href="#section-5.5.3">5.5.3</a> SMTP ........................................................ <a href="#page-34">34</a>
79 <a href="#section-5.5.4">5.5.4</a> DNS ......................................................... <a href="#page-35">35</a>
80 <a href="#section-5.5.5">5.5.5</a> BOOTP ....................................................... <a href="#page-35">35</a>
81 <a href="#section-5.5.5.1">5.5.5.1</a> Bootstrap Server Protocol ................................. <a href="#page-35">35</a>
82 <a href="#section-5.5.5.2">5.5.5.2</a> Bootstrap Client Protocol ................................. <a href="#page-35">35</a>
83 <a href="#section-5.5.6">5.5.6</a> TFTP ........................................................ <a href="#page-36">36</a>
84 <a href="#section-5.5.7">5.5.7</a> HTTP ........................................................ <a href="#page-36">36</a>
85 <a href="#section-5.5.8">5.5.8</a> POP3 ........................................................ <a href="#page-36">36</a>
86 <a href="#section-5.5.9">5.5.9</a> SUNRPC ...................................................... <a href="#page-37">37</a>
87 <a href="#section-5.5.10">5.5.10</a> NFS ........................................................ <a href="#page-38">38</a>
88 <a href="#section-5.5.11">5.5.11</a> SNMP ....................................................... <a href="#page-38">38</a>
89 <a href="#section-5.5.11.1">5.5.11.1</a> SNMP Request/Response .................................... <a href="#page-38">38</a>
90 <a href="#section-5.5.11.2">5.5.11.2</a> SNMP Trap ................................................ <a href="#page-39">39</a>
91 <a href="#section-6">6</a> Acknowledgements ................................................ <a href="#page-39">39</a>
92 <a href="#section-7">7</a> References ...................................................... <a href="#page-40">40</a>
93 <a href="#section-8">8</a> Security Considerations ......................................... <a href="#page-43">43</a>
94 <a href="#section-9">9</a> Authors' Addresses .............................................. <a href="#page-43">43</a>
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Bierman &amp; Iddon Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 This memo defines an experimental portion of the Management
116 Information Base (MIB) for use with network management protocols in
117 the Internet community. In particular, it describes the algorithms
118 required to identify different protocol encapsulations managed with
119 the Remote Network Monitoring MIB Version 2 [<a href="#ref-RMON2">RMON2</a>]. Although related
120 to the original Remote Network Monitoring MIB [<a href="./rfc1757">RFC1757</a>], this
121 document refers only to objects found in the RMON-2 MIB.
122
123 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMP Network Management Framework</span>
124
125 The SNMP Network Management Framework presently consists of three
126 major components. They are:
127
128 o the SMI, described in <a href="./rfc1902">RFC 1902</a> [<a href="./rfc1902">RFC1902</a>], - the mechanisms used for
129 describing and naming objects for the purpose of management.
130
131 o the MIB-II, STD 17, <a href="./rfc1213">RFC 1213</a> [<a href="./rfc1213">RFC1213</a>], - the core set of managed
132 objects for the Internet suite of protocols.
133
134 o the protocol, STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="./rfc1157">RFC1157</a>] and/or <a href="./rfc1905">RFC 1905</a> [<a href="./rfc1905">RFC1905</a>],
135 - the protocol for accessing managed information.
136
137 Textual conventions are defined in <a href="./rfc1903">RFC 1903</a> [<a href="./rfc1903">RFC1903</a>], and
138 conformance statements are defined in <a href="./rfc1904">RFC 1904</a> [<a href="./rfc1904">RFC1904</a>].
139
140 The Framework permits new objects to be defined for the purpose of
141 experimentation and evaluation.
142
143 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Object Definitions</span>
144
145 Managed objects are accessed via a virtual information store, termed
146 the Management Information Base or MIB. Objects in the MIB are
147 defined using the subset of Abstract Syntax Notation One (ASN.1)
148 defined in the SMI. In particular, each object type is named by an
149 OBJECT IDENTIFIER, an administratively assigned name. The object
150 type together with an object instance serves to uniquely identify a
151 specific instantiation of the object. For human convenience, we
152 often use a textual string, termed the descriptor, to refer to the
153 object type.
154
155 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span>
156
157 The RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>] uses hierarchically formatted OCTET STRINGs to
158 globally identify individual protocol encapsulations in the
159 protocolDirTable.
160
161
162
163
164 <span class="grey">Bierman &amp; Iddon Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
167
168
169 This guide contains algorithms and examples of protocol identifier
170 encapsulations for use as INDEX values in the protocolDirTable.
171
172 This document is not intended to be an authoritative reference on the
173 protocols described herein. Refer to the Official Internet Standards
174 document [<a href="./rfc1800">RFC1800</a>], the Assigned Numbers document [<a href="./rfc1700">RFC1700</a>], or other
175 appropriate RFCs, IEEE documents, etc. for complete and authoritative
176 protocol information.
177
178 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Terms</span>
179
180 Several terms are used throughout this document, as well as in the
181 RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>], that should be introduced:
182
183 layer-identifier:
184 An octet string fragment representing a particular protocol
185 encapsulation layer. A string fragment identifying a particular
186 protocol encapsulation layer. This string is exactly four octets,
187 (except for the 'vsnap' base-layer identifier, which is exactly
188 eight octets) encoded in network byte order. A particular protocol
189 encapsulation can be identified by starting with a base layer
190 encapsulation (see the 'Base Protocol Identifiers' section for more
191 detail), and following the encoding rules specified in the CHILDREN
192 clause and assignment section for that layer. Then repeat for each
193 identified layer in the encapsulation. (See <a href="#section-4.2.10">section 4.2.10</a>
194 'Evaluating a Protocol-Identifier INDEX' for more detail.)
195
196 protocol:
197 A particular protocol layer, as specified by encoding rules in this
198 document. Usually refers to a single layer in a given
199 encapsulation. Note that this term is sometimes used in the RMON-2
200 MIB [<a href="#ref-RMON2">RMON2</a>] to name a fully-specified protocol-identifier string.
201 In such a case, the protocol-identifier string is named for its
202 upper-most layer. A named protocol may also refer to any
203 encapsulation of that protocol.
204
205 protocol-identifier string:
206 An octet string representing a particular protocol encapsulation,
207 as specified by encoding rules in this document. This string is
208 identified in the RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>] as the protocolDirID object. A
209 protocol-identifier string is composed of one or more layer-
210 identifiers.
211
212
213
214
215
216
217
218
219
220 <span class="grey">Bierman &amp; Iddon Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
223
224
225 protocol-identifier macro:
226 A group of formatted text describing a particular protocol layer,
227 as used within the RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>]. The macro serves several
228 purposes:
229
230 - Name the protocol for use within the RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>].
231 - Describe how the protocol is encoded into an octet string.
232 - Describe how child protocols are identified (if applicable),
233 and encoded into an octet string.
234 - Describe which protocolDirParameters are allowed for the protocol.
235 - Describe how the associated protocolDirType object is encoded
236 for the protocol.
237 - Provide reference(s) to authoritative documentation for the
238 protocol.
239
240 protocol-variant-identifier macro:
241 A group of formatted text describing a particular protocol layer,
242 as used within the RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>]. This protocol is a variant
243 of a well known encapsulation that may be present in the
244 protocolDirTable. This macro is used to document the IANA
245 assigned protocols, which are needed to identify protocols which
246 cannot be practically identified by examination of 'appropriate
247 network traffic' (e.g. the packets which carry them). All other
248 protocols (which can be identified by examination of appropriate
249 network traffic) should be documented using the protocol-identifier
250 macro. A protocol-variant-identifier is documented using the
251 protocol-variant version of the protocol-identifier macro.
252
253 protocol-parameter:
254 A single octet, corresponding to a specific layer-identifier in the
255 protocol-identifier. This octet is a bit-mask indicating special
256 functions or capabilities that this agent is providing for the
257 corresponding protocol.
258
259 protocol-parameters string:
260 An octet string, which contains one protocol-parameter for each
261 layer-identifier in the protocol-identifier. See the section
262 'Mapping of the PARAMETERS Clause' for more detail. This string is
263 identified in the RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>] as the protocolDirParameters
264 object.
265
266 protocolDirTable INDEX:
267 A protocol-identifier and protocol-parameters octet string pair
268 that have been converted to an INDEX value, according to the
269 encoding rules in in <a href="./rfc1902#section-7.7">section&nbsp;7.7 of RFC 1902</a> [<a href="./rfc1902">RFC1902</a>].
270
271
272
273
274
275
276 <span class="grey">Bierman &amp; Iddon Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
279
280
281 pseudo-protocol:
282 A convention or algorithm used only within this document for the
283 purpose of encoding protocol-identifier strings.
284
285 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Relationship to the Remote Network Monitoring MIB</span>
286
287 This document is intended to identify possible string values for the
288 OCTET STRING objects protocolDirID and protocolDirParameters. Tables
289 in the new Protocol Distribution, Host, and Matrix groups use a local
290 INTEGER INDEX, in order to remain unaffected by changes in this
291 document. Only the protocolDirTable uses the strings (protocolDirID
292 and protocolDirParameters) described in this document.
293
294 This document is not intended to limit the protocols that may be
295 identified for counting in the RMON-2 MIB. Many protocol
296 encapsulations, not explicitly identified in this document, may be
297 present in an actual implementation of the protocolDirTable. Also,
298 implementations of the protocolDirTable may not include all the
299 protocols identified in the example section below.
300
301 This document is intentionally separated from the MIB objects to
302 allow frequent updates to this document without any republication of
303 MIB objects. Protocol Identifier macros submitted from the RMON
304 working group and community at large (to the RMONMIB WG mailing list
305 at '[email protected]') will be collected and added to this document.
306
307 Macros submissions will be collected in the IANA's MIB files under
308 the directory "<a href="ftp://ftp.isi.edu/mib/rmonmib/rmon2_pi_macros/">ftp://ftp.isi.edu/mib/rmonmib/rmon2_pi_macros/</a>" and in
309 the RMONMIB working group mailing list message archive file
310 "<a href="ftp://ftp.cisco.com/ftp/rmonmib/rmonmib">ftp://ftp.cisco.com/ftp/rmonmib/rmonmib</a>".
311
312 This document does not discuss auto-discovery and auto-population of
313 the protocolDirTable. This functionality is not explicitly defined by
314 the RMON standard. An agent should populate the directory with
315 'interesting' protocols--depending on the intended applications.
316
317 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Relationship to the Other MIBs</span>
318
319 The RMON Protocol Identifiers document is intended for use with the
320 protocolDirTable within the RMON MIB. It is not relevant to any other
321 MIB, or intended for use with any other MIB.
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Bierman &amp; Iddon Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
335
336
337 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol Identifier Encoding</span>
338
339 The protocolDirTable is indexed by two OCTET STRINGs, protocolDirID
340 and protocolDirParameters. To encode the table index, each variable-
341 length string is converted to an OBJECT IDENTIFIER fragment,
342 according to the encoding rules in <a href="./rfc1902#section-7.7">section&nbsp;7.7 of RFC 1902</a> [<a href="./rfc1902">RFC1902</a>].
343 Then the index fragments are simply concatenated. (Refer to figures
344 1a - 1d below for more detail.)
345
346 The first OCTET STRING (protocolDirID) is composed of one or more 4-
347 octet "layer-identifiers". The entire string uniquely identifies a
348 particular protocol encapsulation tree. The second OCTET STRING,
349 (protocolDirParameters) which contains a corresponding number of 1-
350 octet protocol-specific parameters, one for each 4-octet layer-
351 identifier in the first string.
352
353 A protocol layer is normally identified by a single 32-bit value.
354 Each layer-identifier is encoded in the ProtocolDirID OCTET STRING
355 INDEX as four sub-components [ a.b.c.d ], where 'a' - 'd' represent
356 each byte of the 32-bit value in network byte order. If a particular
357 protocol layer cannot be encoded into 32 bits, (except for the
358 'vsnap' base layer) then it must be defined as a 'ianaAssigned'
359 protocol (see below for details on IANA assigned protocols).
360
361 The following figures show the differences between the OBJECT
362 IDENTIFIER and OCTET STRING encoding of the protocol identifier
363 string.
364
365
366 Fig. 1a
367 protocolDirTable INDEX Format
368 -----------------------------
369
370 +---+--------------------------+---+---------------+
371 | c ! | c ! protocolDir |
372 | n ! protocolDirID | n ! Parameters |
373 | t ! | t ! |
374 +---+--------------------------+---+---------------+
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Bierman &amp; Iddon Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
391
392
393 Fig. 1b
394 protocolDirTable OCTET STRING Format
395 ------------------------------------
396
397 protocolDirID
398 +----------------------------------------+
399 | |
400 | 4 * N octets |
401 | |
402 +----------------------------------------+
403
404 protocolDirParameters
405 +----------+
406 | |
407 | N octets |
408 | |
409 +----------+
410
411 Fig. 1c
412 protocolDirTable INDEX Format Example
413 -------------------------------------
414
415 protocolDirID protocolDirParameters
416 +---+--------+--------+--------+--------+---+---+---+---+---+
417 | c | proto | proto | proto | proto | c |par|par|par|par|
418 | n | base | L3 | L4 | L5 | n |ba-| L3| L4| L5|
419 | t |(+flags)| | | | t |se | | | |
420 +---+--------+--------+--------+--------+---+---+---+---+---+ subOID
421 | 1 | 4 or 8 | 4 | 4 | 4 | 1 |1/2| 1 | 1 | 1 | count
422
423 where N is the number of protocol-layer-identifiers required
424 for the entire encapsulation of the named protocol. Note that
425 the 'vsnap' base layer identifier is encoded into 8 sub-identifiers,
426 All other protocol layers are either encoded into 4 sub-identifiers
427 or encoded as a 'ianaAssigned' protocol.
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Bierman &amp; Iddon Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
447
448
449 Fig. 1d
450 protocolDirTable OCTET STRING Format Example
451 --------------------------------------------
452
453 protocolDirID
454 +--------+--------+--------+--------+
455 | proto | proto | proto | proto |
456 | base | L3 | L4 | L5 |
457 | | | | |
458 +--------+--------+--------+--------+ octet
459 | 4 or 8 | 4 | 4 | 4 | count
460
461
462 protocolDirParameters
463 +---+---+---+---+
464 |par|par|par|par|
465 |ba-| L3| L4| L5|
466 |se | | | |
467 +---+---+---+---+ octet
468 |1/2| 1 | 1 | 1 | count
469
470 where N is the number of protocol-layer-identifiers required
471 for the entire encapsulation of the named protocol. Note that
472 the 'vsnap' base layer identifier is encoded into 8
473 protocolDirID sub-identifiers and 2 protocolDirParameters
474 sub-identifiers.
475
476 Although this example indicates four encapsulated protocols, in
477 practice, any non-zero number of layer-identifiers may be present,
478 theoretically limited only by OBJECT IDENTIFIER length restrictions,
479 as specified in <a href="./rfc1902#section-3.5">section&nbsp;3.5 of RFC 1902</a> [<a href="./rfc1902">RFC1902</a>].
480
481 Note that these two strings would not be concatenated together if
482 ever returned in a GetResponse PDU, since they are different MIB
483 objects. However, protocolDirID and protocolDirParameters are not
484 currently readable MIB objects.
485
486 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. ProtocolDirTable INDEX Format Examples</span>
487
488 -- HTTP; fragments counted from IP and above
489 ether2.ip.tcp.www-http =
490 16.0.0.0.1.0.0.8.0.0.0.0.6.0.0.0.80.4.0.1.0.0
491
492 -- SNMP over UDP/IP over SNAP
493 snap.ip.udp.snmp =
494 16.0.0.0.3.0.0.8.0.0.0.0.17.0.0.0.161.4.0.0.0.0
495
496
497
498
499
500 <span class="grey">Bierman &amp; Iddon Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
503
504
505 -- SNMP over IPX over SNAP
506 snap.ipx.snmp =
507 12.0.0.0.3.0.0.129.55.0.0.144.15.3.0.0.0
508
509 -- SNMP over IPX over raw8023
510 -- ianaAssigned(ipxOverRaw8023(1)).snmp =
511 12.0.0.0.5.0.0.0.1.0.0.155.15.3.0.0.0
512
513 -- IPX over LLC
514 llc.ipx =
515 8.0.0.0.2.0.224.224.3.2.0.0
516
517 -- SNMP over UDP/IP over any link layer
518 -- wildcard-ether2.ip.udp.snmp
519 16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161.4.0.0.0.0
520
521 -- IP over any link layer; base encoding is IP over ether2
522 -- wildcard-ether2.ip
523 8.1.0.0.1.0.0.8.0.2.0.0
524
525 -- AppleTalk Phase 2 over ether2
526 -- ether2.atalk
527 8.0.0.0.1.0.0.128.155.2.0.0
528
529 -- AppleTalk Phase 2 over vsnap
530 -- vsnap(apple).atalk
531 12.0.0.0.4.0.8.0.7.0.0.128.155.3.0.0.0
532
533 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Protocol Identifier Macro Format</span>
534
535 The following example is meant to introduce the protocol-identifier
536 macro. (The syntax is not quite ASN.1.) This macro is used to
537 represent both protocols and protocol-variants.
538
539 If the 'VariantOfPart' component of the macro is present, then the
540 macro represents a protocol-variant instead of a protocol. A
541 protocol- variant-identifier is used only for IANA assigned
542 protocols, enumerated under the 'ianaAssigned' base-layer.
543
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Bierman &amp; Iddon Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
559
560
561 RMON-PROTOCOL-IDENTIFIER MACRO ::=
562 BEGIN
563 PIMacroName "PROTOCOL-IDENTIFIER"
564 VariantOfPart
565 "PARAMETERS" ParamPart
566 "ATTRIBUTES" AttrPart
567 "DESCRIPTION" Text
568 ChildDescrPart
569 AddrDescrPart
570 DecodeDescrPart
571 ReferPart
572 "::=" "{" EncapsPart "}"
573
574 PIMacroName ::=
575 identifier
576
577 VariantOfPart ::=
578 "VARIANT-OF" identifier | empty
579
580 ParamPart ::=
581 "{" ParamList "}"
582
583 ParamList ::=
584 Params | empty
585
586 Params ::=
587 Param | Params "," Param
588
589 Param ::=
590 identifier "(" nonNegativeNumber ")"
591
592 AttrPart ::=
593 "{" AttrList "}"
594
595 AttrList ::=
596 Attrs | empty
597
598 Attrs ::=
599 Attr | Attrs "," Attr
600
601 Attr ::=
602 identifier "(" nonNegativeNumber ")"
603
604 ChildDescrPart ::=
605 "CHILDREN" Text | empty
606
607 AddrDescrPart ::=
608 "ADDRESS-FORMAT" Text | empty
609
610
611
612 <span class="grey">Bierman &amp; Iddon Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
615
616
617 DecodeDescrPart ::=
618 "DECODING" Text | empty
619
620 ReferPart ::=
621 "REFERENCE" Text | empty
622
623 EncapsPart ::=
624 "{" Encaps "}"
625
626 Encaps ::=
627 Encap | Encaps "," Encap
628
629 Encap ::=
630 BaseEncap | NormalEncap | VsnapEncap | IanaEncap
631
632 BaseEncap ::=
633 nonNegativeNumber
634
635 NormalEncap ::=
636 identifier nonNegativeNumber
637
638 VsnapEncap ::=
639 identifier "(" nonNegativeNumber ")" nonNegativeNumber
640
641 IanaEncap ::=
642 "ianaAssigned" nonNegativeNumber
643 | "ianaAssigned" identifier
644 | "ianaAssigned" identifier "(" nonNegativeNumber ")"
645
646 Text ::=
647 """" string """"
648 END
649
650 <span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Mapping of the Protocol Name</span>
651
652 The 'PIMacroName' value should be a lower-case ASCII string, and
653 contain the name or acronym identifying the protocol. NMS
654 applications may treat protocol names as case-insensitive strings,
655 and agent implementations must make sure the protocolDirTable does
656 not contain any instances of the protocolDirDescr object which differ
657 only in the case of one of more letters (if the identifiers are
658 intended to represent different protocols).
659
660 It is possible that different encapsulations of the same protocol
661 (which are represented by different entries in the protocolDirTable)
662 will be assigned the same protocol name.
663
664
665
666
667
668 <span class="grey">Bierman &amp; Iddon Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
671
672
673 A protocol name should match the "most well-known" name or acronym
674 for the indicated protocol. For example, the document indicated by
675 the URL:
676
677 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers">ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers</a>
678
679 defines IP Protocol field values, so protocol-identifier macros for
680 children of IP should be given names consistent with the protocol
681 names found in this authoritative document.
682
683 <span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Mapping of the VARIANT-OF Clause</span>
684
685 This clause is present for IANA assigned protocols only. It
686 identifies the protocol-identifier macro that most closely represents
687 this particular protocol, and is known as the "reference protocol".
688 (A protocol-identifier macro must exist for the reference protocol.)
689 When this clause is present in a protocol-identifier macro, the macro
690 is called a 'protocol-variant-identifier'.
691
692 Any clause (e.g. CHILDREN, ADDRESS-FORMAT) in the reference protocol-
693 identifier macro should not be duplicated in the protocol-variant-
694 identifier macro, if the 'variant' protocols' semantics are identical
695 for a given clause.
696
697 Since the PARAMETERS and ATTRIBUTES clauses must be present in a
698 protocol-identifier, an empty 'ParamPart' and 'AttrPart' (i.e.
699 "PARAMETERS {}") must be present in a protocol-variant-identifier
700 macro, and the 'ParamPart' and 'AttrPart' found in the reference
701 protocol- identifier macro examined instead.
702
703 Note that if a 'ianaAssigned' protocol is defined that is not a
704 variant of any other documented protocol, then the protocol-
705 identifier macro should be used instead of the protocol-variant-
706 identifier version of the macro.
707
708 <span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>. Mapping of the PARAMETERS Clause</span>
709
710 The protocolDirParameters object provides an NMS the ability to turn
711 on and off expensive probe resources. An agent may support a given
712 parameter all the time, not at all, or subject to current resource
713 load.
714
715 The PARAMETERS clause is a list of bit definitions which can be
716 directly encoded into the associated ProtocolDirParameters octet in
717 network byte order. Zero or more bit definitions may be present. Only
718 bits 0-7 are valid encoding values. This clause defines the entire
719 BIT set allowed for a given protocol. A conforming agent may choose
720 to implement a subset of zero or more of these PARAMETERS.
721
722
723
724 <span class="grey">Bierman &amp; Iddon Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
727
728
729 By convention, the following common bit definitions are used by
730 different protocols. These bit positions must not be used for other
731 parameters. They should be reserved if not used by a given protocol.
732 Bits are encoded in network-byte order.
733
734 Table 3.1 Reserved PARAMETERS Bits
735 ------------------------------------
736
737 Bit Name Description
738 ---------------------------------------------------------------------
739 <span class="h2"><a class="selflink" id="section-0" href="#section-0">0</a> countsFragments </span> higher-layer protocols encapsulated within
740 this protocol will be counted correctly even
741 if this protocol fragments the upper layers
742 into multiple packets.
743 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> tracksSessions </span> correctly attributes all packets of a protocol
744 which starts sessions on well known ports or
745 sockets and then transfers them to dynamically
746 assigned ports or sockets thereafter (e.g. TFTP).
747
748 The PARAMETERS clause must be present in all protocol-identifier
749 macro declarations, but may be equal to zero (empty). Note that an
750 NMS must determine if a given PARAMETER bit is supported by
751 attempting to create the desired protocolDirEntry The associated
752 ATTRIBUTE bits for 'countsFragments' and 'tracksSessions' do not
753 exist.
754
755 <span class="h5"><a class="selflink" id="section-4.2.3.1" href="#section-4.2.3.1">4.2.3.1</a>. Mapping of the 'countsFragments(0)' BIT</span>
756
757 This bit indicates whether the probe is correctly attributing all
758 fragmented packets of the specified protocol, even if individual
759 frames carrying this protocol cannot be identified as such. Note
760 that the probe is not required to actually present any re-assembled
761 datagrams (for address-analysis, filtering, or any other purpose) to
762 the NMS.
763
764 This bit may only be set in a protocolDirParameters octet which
765 corresponds to a protocol that supports fragmentation and reassembly
766 in some form. Note that TCP packets are not considered 'fragmented-
767 streams' and so TCP is not eligible.
768
769 This bit may be set in at most one protocolDirParameters octet within
770 a protocolDirTable INDEX.
771
772
773
774
775
776
777
778
779
780 <span class="grey">Bierman &amp; Iddon Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
783
784
785 <span class="h5"><a class="selflink" id="section-4.2.3.2" href="#section-4.2.3.2">4.2.3.2</a>. Mapping of the 'tracksSessions(1)' BIT</span>
786
787 The 'tracksSessions(1)' bit indicates whether frames which are part
788 of remapped-sessions (e.g. TFTP download sessions) are correctly
789 counted by the probe. For such a protocol, the probe must usually
790 analyze all packets received on the indicated interface, and maintain
791 some state information, (e.g. the remapped UDP port number for TFTP).
792
793 The semantics of the 'tracksSessions' parameter are independent of
794 the other protocolDirParameters definitions, so this parameter may be
795 combined with any other legal parameter configurations.
796
797 <span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>. Mapping of the ATTRIBUTES Clause</span>
798
799 The protocolDirType object provides an NMS with an indication of a
800 probe's capabilities for decoding a given protocol, or the general
801 attributes of the particular protocol.
802
803 The ATTRIBUTES clause is a list of bit definitions which are encoded
804 into the associated instance of ProtocolDirType. The BIT definitions
805 are specified in the SYNTAX clause of the protocolDirType MIB object.
806
807 Table 3.2 Reserved ATTRIBUTES Bits
808 ------------------------------------
809
810 Bit Name Description
811 ---------------------------------------------------------------------
812 0 hasChildren indicates that there may be children of
813 this protocol defined in the protocolDirTable
814 (by either the agent or the manager).
815 1 addressRecognitionCapable
816 indicates that this protocol can be used
817 to generate host and matrix table entries.
818
819 The ATTRIBUTES clause must be present in all protocol-identifier
820 macro declarations, but may be empty.
821
822 <span class="h4"><a class="selflink" id="section-4.2.5" href="#section-4.2.5">4.2.5</a>. Mapping of the DESCRIPTION Clause</span>
823
824 The DESCRIPTION clause provides a textual description of the protocol
825 identified by this macro. Notice that it should not contain details
826 about items covered by the CHILDREN, ADDRESS-FORMAT, DECODING and
827 REFERENCE clauses.
828
829 The DESCRIPTION clause must be present in all protocol-identifier
830 macro declarations.
831
832
833
834
835
836 <span class="grey">Bierman &amp; Iddon Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
839
840
841 <span class="h4"><a class="selflink" id="section-4.2.6" href="#section-4.2.6">4.2.6</a>. Mapping of the CHILDREN Clause</span>
842
843 The CHILDREN clause provides a description of child protocols for
844 protocols which support them. It has three sub-sections:
845
846 - Details on the field(s)/value(s) used to select the child protocol,
847 and how that selection process is performed
848
849 - Details on how the value(s) are encoded in the protocol identifier
850 octet string
851
852 - Details on how child protocols are named with respect to their
853 parent protocol label(s)
854
855 The CHILDREN clause must be present in all protocol-identifier macro
856 declarations in which the 'hasChildren(0)' BIT is set in the
857 ATTRIBUTES clause.
858
859 <span class="h4"><a class="selflink" id="section-4.2.7" href="#section-4.2.7">4.2.7</a>. Mapping of the ADDRESS-FORMAT Clause</span>
860
861 The ADDRESS-FORMAT clause provides a description of the OCTET-STRING
862 format(s) used when encoding addresses.
863
864 This clause must be present in all protocol-identifier macro
865 declarations in which the 'addressRecognitionCapable(1)' BIT is set
866 in the ATTRIBUTES clause.
867
868 <span class="h4"><a class="selflink" id="section-4.2.8" href="#section-4.2.8">4.2.8</a>. Mapping of the DECODING Clause</span>
869
870 The DECODING clause provides a description of the decoding procedure
871 for the specified protocol. It contains useful decoding hints for the
872 implementor, but should not over-replicate information in documents
873 cited in the REFERENCE clause. It might contain a complete
874 description of any decoding information required.
875
876 For 'extensible' protocols ('hasChildren(0)' BIT set) this includes
877 offset and type information for the field(s) used for child selection
878 as well as information on determining the start of the child
879 protocol.
880
881 For 'addressRecognitionCapable' protocols this includes offset and
882 type information for the field(s) used to generate addresses.
883
884 The DECODING clause is optional, and may be omitted if the REFERENCE
885 clause contains pointers to decoding information for the specified
886 protocol.
887
888
889
890
891
892 <span class="grey">Bierman &amp; Iddon Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
895
896
897 <span class="h4"><a class="selflink" id="section-4.2.9" href="#section-4.2.9">4.2.9</a>. Mapping of the REFERENCE Clause</span>
898
899 If a publicly available reference document exists for this protocol
900 it should be listed here. Typically this will be a URL if possible;
901 if not then it will be the name and address of the controlling body.
902
903 The CHILDREN, ADDRESS-FORMAT, and DECODING clauses should limit the
904 amount of information which may currently be obtained from an
905 'authoritative' document, such as the Assigned Numbers document
906 [<a href="./rfc1700">RFC1700</a>]. Any duplication or paraphrasing of information should be
907 brief and consistent with the authoritative document.
908
909 The REFERENCE clause is optional, but should be implemented if an
910 authoritative reference exists for the protocol (especially for
911 standard protocols).
912
913 <span class="h4"><a class="selflink" id="section-4.2.10" href="#section-4.2.10">4.2.10</a>. Evaluating a Protocol-Identifier INDEX</span>
914
915 The following evaluation is done after protocolDirTable INDEX value
916 has been converted into two OCTET STRINGs according to the INDEX
917 encoding rules specified in the SMI [<a href="./rfc1902">RFC1902</a>].
918
919 Protocol-identifiers are evaluated left to right, starting with the
920 protocolDirID, which length should be evenly divisible by four. The
921 protocolDirParameters length should be exactly one quarter of the
922 protocolDirID string length.
923
924 Protocol-identifier parsing starts with the base layer identifier,
925 which must be present, and continues for one or more upper layer
926 identifiers, until all OCTETs of the protocolDirID have been used.
927 Layers may not be skipped, so identifiers such as 'SNMP over IP' or
928 'TCP over anylink' can not exist.
929
930 The base-layer-identifier also contains a 'special function
931 identifier' which may apply to the rest of the protocol identifier.
932
933 Wild-carding at the base layer within a protocol encapsulation is the
934 only supported special function at this time. Refer to the 'Base
935 Protocol Identifiers' section for wildcard encoding rules.
936
937 After the protocol-tree identified in protocolDirID has been parsed,
938 each parameter bit-mask (one octet for each 4-octet layer-identifier)
939 is evaluated, and applied to the corresponding protocol layer.
940
941 A protocol-identifier label may map to more than one value. For
942 instance, 'ip' maps to 5 distinct values, one for each supported
943 encapsulation. (see the 'IP' section under 'L3 Protocol
944 Identifiers'),
945
946
947
948 <span class="grey">Bierman &amp; Iddon Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
951
952
953 It is important to note that these macros are conceptually expanded
954 at implementation time, not at run time.
955
956 If all the macros are expanded completely by substituting all
957 possible values of each label for each child protocol, a list of all
958 possible protocol-identifiers is produced. So 'ip' would result in 5
959 distinct protocol-identifiers. Likewise each child of 'ip' would map
960 to at least 5 protocol-identifiers, one for each encapsulation (e.g.
961 ip over ether2, ip over LLC, etc.).
962
963 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Protocol Identifier Macros</span>
964
965 The following PROTOCOL IDENTIFIER macros can be used to construct
966 protocolDirID and protocolDirParameters strings.
967
968 The sections defining protocol examples are intended to grow over
969 subsequent releases. Minimal protocol support is included at this
970 time. (Refer to <a href="#section-3.2">section 3.2</a> for details on the protocol macro update
971 procedure.)
972
973 An identifier is encoded by constructing the base-identifier, then
974 adding one layer-identifier for each encapsulated protocol.
975
976 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Base Identifier Encoding</span>
977
978 The first layer encapsulation is called the base identifier and it
979 contains optional protocol-function information and the base layer
980 (e.g. MAC layer) enumeration value used in this protocol identifier.
981
982 The base identifier is encoded as four octets as shown in figure 2.
983
984 Fig. 2
985 base-identifier format
986 +---+---+---+---+
987 | | | | |
988 | f |op1|op2| m |
989 | | | | |
990 +---+---+---+---+ octet
991 | 1 | 1 | 1 | 1 | count
992
993 The first octet ('f') is the special function code, found in table
994 4.1. The next two octets ('op1' and 'op2') are operands for the
995 indicated function. If not used, an operand must be set to zero. The
996 last octet, 'm', is the enumerated value for a particular base layer
997 encapsulation, found in table 4.2. All four octets are encoded in
998 network-byte-order.
999
1000
1001
1002
1003
1004 <span class="grey">Bierman &amp; Iddon Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1007
1008
1009 <span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Protocol Identifier Functions</span>
1010
1011 The base layer identifier contains information about any special
1012 functions to perform during collections of this protocol, as well as
1013 the base layer encapsulation identifier.
1014
1015 The first three octets of the identifier contain the function code
1016 and two optional operands. The fourth octet contains the particular
1017 base layer encapsulation used in this protocol (fig. 2).
1018
1019 Table 4.1 Assigned Protocol Identifier Functions
1020 -------------------------------------------------
1021
1022 Function ID Param1 Param2
1023 ----------------------------------------------------
1024 none 0 not used (0) not used (0)
1025 wildcard 1 not used (0) not used (0)
1026
1027 <span class="h5"><a class="selflink" id="section-5.1.1.1" href="#section-5.1.1.1">5.1.1.1</a>. Function 0: No-op</span>
1028
1029 If the function ID field (1st octet) is equal to zero, the the 'op1'
1030 and 'op2' fields (2nd and 3rd octets) must also be equal to zero.
1031 This special value indicates that no functions are applied to the
1032 protocol identifier encoded in the remaining octets. The identifier
1033 represents a normal protocol encapsulation.
1034
1035 <span class="h5"><a class="selflink" id="section-5.1.1.2" href="#section-5.1.1.2">5.1.1.2</a>. Function 1: Protocol Wildcard Function</span>
1036
1037 The wildcard function (function-ID = 1), is used to aggregate
1038 counters, by using a single protocol value to indicate potentially
1039 many base layer encapsulations of a particular network layer
1040 protocol. A protocolDirEntry of this type will match any base-layer
1041 encapsulation of the same protocol.
1042
1043 The 'op1' field (2nd octet) is not used and must be set to zero.
1044
1045 The 'op2' field (3rd octet) is not used and must be set to zero.
1046
1047 Each wildcard protocol identifier must be defined in terms of a 'base
1048 encapsulation'. This should be as 'standard' as possible for
1049 interoperability purposes. If an encapsulation over 'ether2' is
1050 permitted, than this should be used as the base encapsulation.
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Bierman &amp; Iddon Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1063
1064
1065 The agent may also be requested to count some or all of the
1066 individual encapsulations for the same protocols, in addition to
1067 wildcard counting. Note that the RMON-2 MIB [<a href="#ref-RMON2">RMON2</a>] does not require
1068 that agents maintain counters for multiple encapsulations of the same
1069 protocol. It is an implementation-specific matter as to how an agent
1070 determines which protocol combinations to allow in the
1071 protocolDirTable at any given time.
1072
1073 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Base Layer Protocol Identifiers</span>
1074
1075 The base layer is mandatory, and defines the base encapsulation of
1076 the packet and any special functions for this identifier.
1077
1078 There are no suggested protocolDirParameters bits for the base layer.
1079
1080 The suggested ProtocolDirDescr field for the base layer is given by
1081 the corresponding "Name" field in the table 4.1 below. However,
1082 implementations are only required to use the appropriate integer
1083 identifier values.
1084
1085 For most base layer protocols, the protocolDirType field should
1086 contain bits set for the 'hasChildren(0)' and
1087 'addressRecognitionCapable(1)' attributes. However, the special
1088 'ianaAssigned' base layer should have no parameter or attribute bits
1089 set.
1090
1091 By design, only 255 different base layer encapsulations are
1092 supported. There are five base encapsulation values defined at this
1093 time. New base encapsulations (e.g. for new media types) are expected
1094 to be added over time.
1095
1096 Table 4.2 Base Layer Encoding Values
1097 --------------------------------------
1098
1099 Name ID
1100 ------------------
1101 ether2 1
1102 llc 2
1103 snap 3
1104 vsnap 4
1105 ianaAssigned 5
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Bierman &amp; Iddon Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1119
1120
1121 <span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Ether2 Encapsulation</span>
1122
1123 ether2 PROTOCOL-IDENTIFIER
1124 PARAMETERS { }
1125 ATTRIBUTES {
1126 hasChildren(0),
1127 addressRecognitionCapable(1)
1128 }
1129 DESCRIPTION
1130 "DIX Ethernet, also called Ethernet-II."
1131 CHILDREN
1132 "The Ethernet-II type field is used to select child protocols.
1133 This is a 16-bit field. Child protocols are deemed to start at
1134 the first octet after this type field.
1135
1136 Children of this protocol are encoded as [ 0.0.0.1 ], the
1137 protocol identifier for 'ether2' followed by [ 0.0.a.b ] where
1138 'a' and 'b' are the network byte order encodings of the MSB and
1139 LSB of the Ethernet-II type value.
1140
1141 For example, a protocolDirID-fragment value of:
1142 0.0.0.1.0.0.8.0 defines IP encapsulated in ether2.
1143
1144 Children of are named as 'ether2' followed by the type field
1145 value in hexadecimal. The above example would be declared as:
1146 ether2 0x0800"
1147 ADDRESS-FORMAT
1148 "Ethernet addresses are 6 octets in network order."
1149 DECODING
1150 "Only type values greater than or equal to 1500 decimal indicate
1151 Ethernet-II frames; lower values indicate 802.3 encapsulation
1152 (see below)."
1153 REFERENCE
1154 "A Standard for the Transmission of IP Datagrams over Ethernet
1155 Networks; <a href="./rfc894">RFC 894</a> [<a href="./rfc894">RFC894</a>].
1156
1157 The authoritative list of Ether Type values is identified by the
1158 URL:
1159
1160 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/ethernet-numbers">ftp://ftp.isi.edu/in-notes/iana/assignments/ethernet-numbers</a>"
1161 ::= { 1 }
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Bierman &amp; Iddon Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1175
1176
1177 <span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. LLC Encapsulation</span>
1178
1179 llc PROTOCOL-IDENTIFIER
1180 PARAMETERS { }
1181 ATTRIBUTES {
1182 hasChildren(0),
1183 addressRecognitionCapable(1)
1184 }
1185 DESCRIPTION
1186 "The LLC (802.2) protocol."
1187 CHILDREN
1188 "The LLC SSAP and DSAP (Source/Dest Service Access Points) are
1189 used to select child protocols. Each of these is one octet long,
1190 although the least significant bit is a control bit and should be
1191 masked out in most situations. Typically SSAP and DSAP (once
1192 masked) are the same for a given protocol - each end implicitly
1193 knows whether it is the server or client in a client/server
1194 protocol. This is only a convention, however, and it is possible
1195 for them to be different. The SSAP is matched against child
1196 protocols first. If none is found then the DSAP is matched
1197 instead. The child protocol is deemed to start at the first
1198 octet after the LLC control field(s).
1199
1200 Children of 'llc' are encoded as [ 0.0.0.2 ], the protocol
1201 identifier component for LLC followed by [ 0.0.0.a ] where 'a' is
1202 the SAP value which maps to the child protocol. For example, a
1203 protocolDirID-fragment value of:
1204 0.0.0.2.0.0.0.240
1205
1206 defines NetBios over LLC.
1207
1208 Children are named as 'llc' followed by the SAP value in
1209 hexadecimal. So the above example would have been named:
1210 llc 0xf0"
1211 ADDRESS-FORMAT
1212 "The address consists of 6 octets of MAC address in network
1213 order. Source routing bits should be stripped out of the address
1214 if present."
1215 DECODING
1216 "Notice that LLC has a variable length protocol header; there are
1217 always three octets (DSAP, SSAP, control). Depending on the
1218 value of the control bits in the DSAP, SSAP and control fields
1219 there may be an additional octet of control information.
1220
1221 LLC can be present on several different media. For 802.3 and
1222 802.5 its presence is mandated (but see ether2 and raw802.3
1223 encapsulations). For 802.5 there is no other link layer
1224 protocol.
1225
1226
1227
1228 <span class="grey">Bierman &amp; Iddon Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1231
1232
1233 Notice also that the raw802.3 link layer protocol may take
1234 precedence over this one in a protocol specific manner such that
1235 it may not be possible to utilize all LSAP values if raw802.3 is
1236 also present."
1237 REFERENCE
1238 "The authoritative list of LLC LSAP values is controlled by the
1239 IEEE Registration Authority:
1240 IEEE Registration Authority
1241 c/o Iris Ringel
1242 IEEE Standards Dept
1243 445 Hoes Lane, P.O. Box 1331
1244 Piscataway, NJ 08855-1331
1245 Phone +1 908 562 3813
1246 Fax: +1 908 562 1571"
1247 ::= { 2 }
1248
1249 <span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>. SNAP over LLC (OUI=000) Encapsulation</span>
1250
1251 snap PROTOCOL-IDENTIFIER
1252 PARAMETERS { }
1253 ATTRIBUTES {
1254 hasChildren(0),
1255 addressRecognitionCapable(1)
1256 }
1257 DESCRIPTION
1258 "The Sub-Network Access Protocol (SNAP) is layered on top of LLC
1259 protocol, allowing Ethernet-II protocols to be run over a media
1260 restricted to LLC."
1261 CHILDREN
1262 "Children of 'snap' are identified by Ethernet-II type values;
1263 the SNAP PID (Protocol Identifier) field is used to select the
1264 appropriate child. The entire SNAP protocol header is consumed;
1265 the child protocol is assumed to start at the next octet after
1266 the PID.
1267
1268 Children of 'snap' are encoded as [ 0.0.0.3 ], the protocol
1269 identifier for 'snap', followed by [ 0.0.a.b ] where 'a' and 'b'
1270 are the MSB and LSB of the Ethernet-II type value. For example,
1271 a protocolDirID-fragment value of:
1272 0.0.0.3.0.0.8.0
1273
1274 defines the IP/SNAP protocol.
1275
1276 Children of this protocol are named 'snap' followed by the
1277 Ethernet-II type value in hexadecimal. The above example would
1278 be named:
1279
1280 snap 0x0800"
1281
1282
1283
1284 <span class="grey">Bierman &amp; Iddon Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1287
1288
1289 ADDRESS-FORMAT
1290 "The address format for SNAP is the same as that for LLC"
1291 DECODING
1292 "SNAP is only present over LLC. Both SSAP and DSAP will be 0xAA
1293 and a single control octet will be present. There are then three
1294 octets of OUI and two octets of PID. For this encapsulation the
1295 OUI must be 0x000000 (see 'vsnap' below for non-zero OUIs)."
1296 REFERENCE
1297 "SNAP Identifier values are assigned by the IEEE Standards
1298 Office. The address is:
1299 IEEE Registration Authority
1300 c/o Iris Ringel
1301 IEEE Standards Dept
1302 445 Hoes Lane, P.O. Box 1331
1303 Piscataway, NJ 08855-1331
1304 Phone +1 908 562 3813
1305 Fax: +1 908 562 1571"
1306 ::= { 3 }
1307
1308 <span class="h4"><a class="selflink" id="section-5.2.4" href="#section-5.2.4">5.2.4</a>. SNAP over LLC (OUI != 000) Encapsulation</span>
1309
1310 vsnap PROTOCOL-IDENTIFIER
1311 PARAMETERS { }
1312 ATTRIBUTES {
1313 hasChildren(0),
1314 addressRecognitionCapable(1)
1315 }
1316 DESCRIPTION
1317 "This pseudo-protocol handles all SNAP packets which do not have
1318 a zero OUI. See 'snap' above for details of those that do."
1319 CHILDREN
1320 "Children of 'vsnap' are selected by the 3 octet OUI; the PID is
1321 not parsed; child protocols are deemed to start with the first
1322 octet of the SNAP PID field, and continue to the end of the
1323 packet.
1324
1325 Children of 'vsnap' are encoded as [ 0.0.0.4 ], the protocol
1326 identifier for 'vsnap', followed by [ 0.a.b.c.0.0.d.e ] where
1327 'a', 'b' and 'c' are the 3 octets of the OUI field in network
1328 byte order. This is in turn followed by the 16-bit EtherType
1329 value, where the 'd' and 'e' represent the MSB and LSB of the
1330 EtherType, respectively.
1331
1332 For example, a protocolDirID-fragment value of:
1333 0.0.0.4.0.8.0.7.0.0.128.155
1334 defines the AppleTalk Phase 2 protocol over vsnap.
1335
1336
1337
1338
1339
1340 <span class="grey">Bierman &amp; Iddon Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1343
1344
1345 Note that two protocolDirParameters octets must be present in
1346 protocolDirTable INDEX values for 'vsnap' protocols. The first
1347 protocolDirParameters octet defines the actual parameters. The
1348 second protocolDirParameters octet is not used and must be set to
1349 zero.
1350
1351 Children are named as 'vsnap(&lt;OUI&gt;) &lt;ethertype&gt;', where the
1352 '&lt;OUI&gt;' field is represented as 3 octets in hexadecimal notation
1353 or the ASCII string associated with the OUI value. The
1354 &lt;ethertype&gt; field is represented by the 2 byte EtherType value in
1355 hexadecimal notation. So the above example would be named:
1356
1357 'vsnap(0x080007) 0x809b' or 'vsnap(apple) 0x809b'"
1358 ADDRESS-FORMAT
1359 "The LLC address format is inherited by 'vsnap'. See the 'llc'
1360 protocol identifier for more details."
1361 DECODING
1362 "Same as for 'snap' except the OUI is non-zero."
1363 REFERENCE
1364 "SNAP Identifier values are assigned by the IEEE Standards
1365 Office. The address is:
1366 IEEE Registration Authority
1367 c/o Iris Ringel
1368 IEEE Standards Dept
1369 445 Hoes Lane, P.O. Box 1331
1370 Piscataway, NJ 08855-1331
1371 Phone +1 908 562 3813
1372 Fax: +1 908 562 1571"
1373 ::= { 4 }
1374
1375 <span class="h4"><a class="selflink" id="section-5.2.5" href="#section-5.2.5">5.2.5</a>. IANA Assigned Protocols</span>
1376
1377 ianaAssigned PROTOCOL-IDENTIFIER
1378 PARAMETERS { }
1379 ATTRIBUTES { }
1380 DESCRIPTION
1381 "This branch contains protocols which do not conform easily to
1382 the hierarchical format utilized in the other link layer
1383 branches. Usually, such a protocol 'almost' conforms to a
1384 particular 'well-known' identifier format, but additional
1385 criteria are used (e.g. configuration-based), making protocol
1386 identification difficult or impossible by examination of
1387 appropriate network traffic. preventing the any 'well-known'
1388 protocol-identifier macro from being used.
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Bierman &amp; Iddon Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1399
1400
1401 Sometimes well-known protocols are simply remapped to a different
1402 port number by one or more venders (e.g. SNMP). These protocols
1403 can be identified with the 'user-extensibility' feature of the
1404 protocolDirTable, and do not need special IANA
1405 assignments.
1406
1407 A centrally located list of these enumerated protocols must be
1408 maintained to insure interoperability.
1409 (See <a href="#section-3.2">section 3.2</a> for details on the document update procedure.)
1410 Support for new link-layers will be added explicitly, and only
1411 protocols which cannot possibly be represented in a better way
1412 will be considered as 'ianaEnumerated' protocols.
1413
1414 IANA assigned protocols are identified by the base-layer-selector
1415 value [ 0.0.0.5 ], followed by the four octets [ a.b.c.d ] of the
1416 integer value corresponding to the particular IANA protocol.
1417
1418 Do not create children of this protocol unless you are sure that
1419 they cannot be handled by the more conventional link layers
1420 above."
1421 CHILDREN
1422 "Children of this protocol are identified by implementation-
1423 specific means, described (as best as possible) in the 'DECODING'
1424 clause within the protocol-variant-identifier macro for each
1425 enumerated protocol.
1426
1427 For example, a protocolDirID-fragment value of:
1428 0.0.0.5.0.0.0.1
1429
1430 defines the IPX protocol encapsulated directly in 802.3
1431
1432 Children are named 'ianaAssigned' followed by the name or numeric
1433 of the particular IANA assigned protocol. The above
1434 example would be named:
1435
1436 'ianaAssigned 1' or 'ianaAssigned ipxOverRaw8023'"
1437
1438 DECODING
1439 "The 'ianaAssigned' base layer is a pseudo-protocol and is not
1440 decoded."
1441 REFERENCE
1442 "Refer to individual PROTOCOL-IDENTIFIER macros for information
1443 on each child of the IANA assigned protocol."
1444 ::= { 5 }
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Bierman &amp; Iddon Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1455
1456
1457 <span class="h5"><a class="selflink" id="section-5.2.5.1" href="#section-5.2.5.1">5.2.5.1</a>. IANA Assigned Protocol Identifiers</span>
1458
1459 The following protocol-variant-identifier macro declarations are used
1460 to identify the RMONMIB IANA assigned protocols in a proprietary way,
1461 by simple enumeration. Note that an additional four-octet layer
1462 identifier may be used for some enumerations (as with the 'vsnap'
1463 base-layer identifier). Refer to the 'CHILDREN' clause in the
1464 protocol-identifier macro for a particular protocol to determine the
1465 number of octets in the 'ianaAssigned' layer-identifier.
1466
1467 ipxOverRaw8023 PROTOCOL-IDENTIFIER
1468 VARIANT-OF "ipx"
1469 PARAMETERS { }
1470 ATTRIBUTES { }
1471 DESCRIPTION
1472 "This pseudo-protocol describes an encapsulation of IPX over
1473 802.3, without a type field.
1474
1475 Refer to the macro for IPX for additional information about this
1476 protocol."
1477 DECODING
1478 "Whenever the 802.3 header indicates LLC a set of protocol
1479 specific tests needs to be applied to determine whether this is a
1480 'raw8023' packet or a true 802.2 packet. The nature of these
1481 tests depends on the active child protocols for 'raw8023' and is
1482 beyond the scope of this document."
1483 ::= { ianaAssigned 1 }
1484
1485 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. L3: Children of Base Protocol Identifiers</span>
1486
1487 Network layer protocol identifier macros contain additional
1488 information about the network layer, and is found immediately
1489 following a base layer-identifier in a protocol identifier.
1490
1491 The ProtocolDirParameters supported at the network layer are
1492 'countsFragments(0)', and 'tracksSessions(1). An agent may choose to
1493 implement a subset of these parameters.
1494
1495 The protocol-name should be used for the ProtocolDirDescr field. The
1496 ProtocolDirType ATTRIBUTES used at the network layer are
1497 'hasChildren(0)' and 'addressRecognitionCapable(1)'. Agents may
1498 choose to implement a subset of these attributes for each protocol,
1499 and therefore limit which tables the indicated protocol can be
1500 present (e.g. protocol distribution, host, and matrix tables)..
1501
1502 The following protocol-identifier macro declarations are given for
1503 example purposes only. They are not intended to constitute an
1504 exhaustive list or an authoritative source for any of the protocol
1505
1506
1507
1508 <span class="grey">Bierman &amp; Iddon Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1511
1512
1513 information given. However, any protocol that can encapsulate other
1514 protocols must be documented here in order to encode the children
1515 identifiers into protocolDirID strings. Leaf protocols should be
1516 documented as well, but an implementation can identify a leaf
1517 protocol even if it isn't listed here (as long as the parent is
1518 documented).
1519
1520 <span class="h4"><a class="selflink" id="section-5.3.1" href="#section-5.3.1">5.3.1</a>. IP</span>
1521
1522 ip PROTOCOL-IDENTIFIER
1523 PARAMETERS {
1524 countsFragments(0) -- This parameter applies to all child
1525 -- protocols.
1526 }
1527 ATTRIBUTES {
1528 hasChildren(0),
1529 addressRecognitionCapable(1)
1530 }
1531 DESCRIPTION
1532 "The protocol identifiers for the Internet Protocol (IP). Note
1533 that IP may be encapsulated within itself, so more than one of
1534 the following identifiers may be present in a particular
1535 protocolDirID string."
1536 CHILDREN
1537 "Children of 'ip' are selected by the value in the Protocol field
1538 (one octet), as defined in the PROTOCOL NUMBERS table within the
1539 Assigned Numbers Document.
1540
1541 The value of the Protocol field is encoded in an octet string as
1542 [ 0.0.0.a ], where 'a' is the protocol field .
1543
1544 Children of 'ip' are encoded as [ 0.0.0.a ], and named as 'ip a'
1545 where 'a' is the protocol field value. For example, a
1546 protocolDirID-fragment value of:
1547 0.0.0.1.0.0.8.0.0.0.0.1
1548
1549 defines an encapsulation of ICMP (ether2.ip.icmp)"
1550 ADDRESS-FORMAT
1551 "4 octets of the IP address, in network byte order. Each ip
1552 packet contains two addresses, the source address and the
1553 destination address."
1554 DECODING
1555 "Note: ether2/ip/ipip4/udp is a different protocolDirID than
1556 ether2/ip/udp, as identified in the protocolDirTable. As such,
1557 two different local protocol index values will be assigned by the
1558 agent. E.g. (full INDEX values shown):
1559 ether2/ip/ipip4/udp 16.0.0.0.1.0.0.8.0.0.0.0.4.0.0.0.17.4.0.0.0.0
1560 ether2/ip/udp 12.0.0.0.1.0.0.8.0.0.0.0.17.3.0.0.0 "
1561
1562
1563
1564 <span class="grey">Bierman &amp; Iddon Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1567
1568
1569 REFERENCE
1570 "<a href="./rfc791">RFC 791</a> [<a href="./rfc791">RFC791</a>] defines the Internet Protocol; The following
1571 URL defines the authoritative repository for the PROTOCOL NUMBERS
1572 Table:
1573
1574 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers">ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers</a>"
1575 ::= {
1576 ether2 0x0800,
1577 llc 0x06,
1578 snap 0x0800,
1579 ip 4,
1580 ip 94
1581 }
1582
1583 <span class="h4"><a class="selflink" id="section-5.3.2" href="#section-5.3.2">5.3.2</a>. IPX</span>
1584
1585 ipx PROTOCOL-IDENTIFIER
1586 PARAMETERS { }
1587 ATTRIBUTES {
1588 hasChildren(0),
1589 addressRecognitionCapable(1)
1590 }
1591 DESCRIPTION
1592 "Novell IPX"
1593 CHILDREN
1594 "Children of IPX are defined by the 16 bit value of the
1595 Destination Socket field. The value is encoded into an octet
1596 string as [ 0.0.a.b ], where 'a' and 'b' are the network byte
1597 order encodings of the MSB and LSB of the destination socket
1598 field."
1599 ADDRESS-FORMAT
1600 "4 bytes of Network number followed by the 6 bytes Host address
1601 each in network byte order".
1602 REFERENCE
1603 "The IPX protocol is defined by the Novell Corporation
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620 <span class="grey">Bierman &amp; Iddon Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1623
1624
1625 A complete description of IPX may be secured at the following
1626 address:
1627 Novell, Inc.
1628 122 East 1700 South
1629 P. O. Box 5900
1630 Provo, Utah 84601 USA
1631 800 526 5463
1632 Novell Part # 883-000780-001"
1633 ::= {
1634 ether2 0x8137, -- 0.0.129.55
1635 llc 0xe0e003, -- 0.224.224.3
1636 snap 0x8137, -- 0.0.129.55
1637 ianaAssigned 0x1 -- 0.0.0.1 (ipxOverRaw8023)
1638 }
1639
1640 <span class="h4"><a class="selflink" id="section-5.3.3" href="#section-5.3.3">5.3.3</a>. ARP</span>
1641
1642 arp PROTOCOL-IDENTIFIER
1643 PARAMETERS { }
1644 ATTRIBUTES { }
1645 DESCRIPTION
1646 "An Address Resolution Protocol message (request or response).
1647 This protocol does not include Reverse ARP (RARP) packets, which
1648 are counted separately."
1649 REFERENCE
1650 "<a href="./rfc826">RFC 826</a> [<a href="./rfc826">RFC826</a>] defines the Address Resolution Protocol."
1651 ::= {
1652 ether2 0x806, -- [ 0.0.8.6 ]
1653 snap 0x806
1654 }
1655
1656 <span class="h4"><a class="selflink" id="section-5.3.4" href="#section-5.3.4">5.3.4</a>. IDP</span>
1657
1658 idp PROTOCOL-IDENTIFIER
1659 PARAMETERS { }
1660 ATTRIBUTES {
1661 hasChildren(0),
1662 addressRecognitionCapable(1)
1663 }
1664 DESCRIPTION
1665 "Xerox IDP"
1666 CHILDREN
1667 "Children of IDP are defined by the 8 bit value of the Packet
1668 type field. The value is encoded into an octet string as [
1669 0.0.0.a ], where 'a' is the value of the packet type field in
1670 network byte order."
1671
1672
1673
1674
1675
1676 <span class="grey">Bierman &amp; Iddon Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1679
1680
1681 ADDRESS-FORMAT
1682 "4 bytes of Network number followed by the 6 bytes Host address
1683 each in network byte order".
1684 REFERENCE
1685 "Xerox Corporation, Document XNSS 028112, 1981"
1686 ::= {
1687 ether2 0x600, -- [ 0.0.6.0 ]
1688 snap 0x600
1689 }
1690
1691 <span class="h4"><a class="selflink" id="section-5.3.5" href="#section-5.3.5">5.3.5</a>. AppleTalk ARP</span>
1692
1693 atalkarp PROTOCOL-IDENTIFIER
1694 PARAMETERS { }
1695 ATTRIBUTES { }
1696 DESCRIPTION
1697 "AppleTalk Address Resolution Protocol."
1698 REFERENCE
1699 "AppleTalk Phase 2 Protocol Specification, document ADPA
1700 #C0144LL/A."
1701 ::= {
1702 ether2 0x80f3, -- [ 0.0.128.243 ]
1703 vsnap(0x080007) 0x80f3
1704 }
1705
1706 <span class="h4"><a class="selflink" id="section-5.3.6" href="#section-5.3.6">5.3.6</a>. AppleTalk</span>
1707
1708 atalk PROTOCOL-IDENTIFIER
1709 PARAMETERS { }
1710 ATTRIBUTES {
1711 hasChildren(0),
1712 addressRecognitionCapable(1)
1713 }
1714 DESCRIPTION
1715 "AppleTalk Protocol."
1716 CHILDREN
1717 "Children of ATALK are defined by the 8 bit value of the DDP type
1718 field. The value is encoded into an octet string as [ 0.0.0.a ],
1719 where 'a' is the value of the DDP type field in network byte
1720 order."
1721 ADDRESS-FORMAT
1722 "2 bytes of Network number followed by 1 byte of node id each in
1723 network byte order".
1724
1725
1726
1727
1728
1729
1730
1731
1732 <span class="grey">Bierman &amp; Iddon Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1735
1736
1737 REFERENCE
1738 "AppleTalk Phase 2 Protocol Specification, document ADPA
1739 #C0144LL/A."
1740 ::= {
1741 ether2 0x809b, -- [ 0.0.128.155 ]
1742 vsnap(0x080007) 0x809b
1743 }
1744
1745 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. L4: Children of L3 Protocols</span>
1746
1747 <span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a>. ICMP</span>
1748
1749 icmp PROTOCOL-IDENTIFIER
1750 PARAMETERS { }
1751 ATTRIBUTES { }
1752 DESCRIPTION
1753 "Internet Message Control Protocol."
1754 REFERENCE
1755 "<a href="./rfc792">RFC 792</a> [<a href="./rfc792">RFC792</a>] defines the Internet Control Message Protocol."
1756 ::= { ip 1 }
1757
1758 <span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a>. TCP</span>
1759
1760 tcp PROTOCOL-IDENTIFIER
1761 PARAMETERS { }
1762 ATTRIBUTES {
1763 hasChildren(0)
1764 }
1765 DESCRIPTION
1766 "Transmission Control Protocol."
1767 CHILDREN
1768 "Children of TCP are identified by the 16 bit Destination Port
1769 value as specified in <a href="./rfc793">RFC 793</a>. They are encoded as [ 0.0.a.b],
1770 where 'a' is the MSB and 'b' is the LSB of the Destination Port
1771 value. Both bytes are encoded in network byte order. For
1772 example, a protocolDirId-fragment of:
1773 0.0.0.1.0.0.8.0.0.0.0.6.0.0.0.23
1774
1775 identifies an encapsulation of the telnet protocol
1776 (ether2.ip.tcp.telnet)"
1777 REFERENCE
1778 "<a href="./rfc793">RFC 793</a> [<a href="./rfc793">RFC793</a>] defines the Transmission Control Protocol.
1779
1780 The following URL defines the authoritative repository for
1781 reserved and registered TCP port values:
1782
1783 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers">ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers</a>"
1784 ::= { ip 6 }
1785
1786
1787
1788 <span class="grey">Bierman &amp; Iddon Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1791
1792
1793 <span class="h4"><a class="selflink" id="section-5.4.3" href="#section-5.4.3">5.4.3</a>. UDP</span>
1794
1795 udp PROTOCOL-IDENTIFIER
1796 PARAMETERS { }
1797 ATTRIBUTES {
1798 hasChildren(0)
1799 }
1800 DESCRIPTION
1801 "User Datagram Protocol."
1802 CHILDREN
1803 "Children of UDP are identified by the 16 bit Destination Port
1804 value as specified in <a href="./rfc768">RFC 768</a>. They are encoded as [ 0.0.a.b ],
1805 where 'a' is the MSB and 'b' is the LSB of the Destination Port
1806 value. Both bytes are encoded in network byte order. For
1807 example, a protocolDirId-fragment of:
1808 0.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161
1809
1810 identifies an encapsulation of SNMP (ether2.ip.udp.snmp)"
1811 REFERENCE
1812 "<a href="./rfc768">RFC 768</a> [<a href="./rfc768">RFC768</a>] defines the User Datagram Protocol.
1813
1814 The following URL defines the authoritative repository for
1815 reserved and registered UDP port values:
1816
1817 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers">ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers</a>"
1818 ::= { ip 17 }
1819
1820 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. L5: Application Layer Protocols</span>
1821
1822 <span class="h4"><a class="selflink" id="section-5.5.1" href="#section-5.5.1">5.5.1</a>. FTP</span>
1823
1824 <span class="h5"><a class="selflink" id="section-5.5.1.1" href="#section-5.5.1.1">5.5.1.1</a>. FTP-DATA</span>
1825
1826 ftp-data PROTOCOL-IDENTIFIER
1827 PARAMETERS { }
1828 ATTRIBUTES { }
1829 DESCRIPTION
1830 "The File Transfer Protocol Data Port; the FTP Server process
1831 default data-connection port. "
1832 REFERENCE
1833 "<a href="./rfc959">RFC 959</a> [<a href="./rfc959">RFC959</a>] defines the File Transfer Protocol. Refer to
1834 <a href="./rfc959#section-3.2">section&nbsp;3.2 of [RFC959]</a> for details on FTP data connections."
1835 ::= { tcp 20 }
1836
1837
1838
1839
1840
1841
1842
1843
1844 <span class="grey">Bierman &amp; Iddon Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1847
1848
1849 <span class="h5"><a class="selflink" id="section-5.5.1.2" href="#section-5.5.1.2">5.5.1.2</a>. FTP Control</span>
1850
1851 ftp PROTOCOL-IDENTIFIER
1852 PARAMETERS { }
1853 ATTRIBUTES { }
1854 DESCRIPTION
1855 "The File Transfer Protocol Control Port; An FTP client initiates
1856 an FTP control connection by sending FTP commands from user port
1857 (U) to this port."
1858 REFERENCE
1859 "<a href="./rfc959">RFC 959</a> [<a href="./rfc959">RFC959</a>] defines the File Transfer Protocol."
1860 ::= { tcp 21 }
1861
1862 <span class="h4"><a class="selflink" id="section-5.5.2" href="#section-5.5.2">5.5.2</a>. Telnet</span>
1863
1864 telnet PROTOCOL-IDENTIFIER
1865 PARAMETERS { }
1866 ATTRIBUTES { }
1867 DESCRIPTION
1868 "The Telnet Protocol; The purpose of the TELNET Protocol is to
1869 provide a fairly general, bi-directional, eight-bit byte oriented
1870 communications facility. Its primary goal is to allow a standard
1871 method of interfacing terminal devices and terminal-oriented
1872 processes to each other. "
1873 REFERENCE
1874 "<a href="./rfc854">RFC 854</a> [<a href="./rfc854">RFC854</a>] defines the basic Telnet Protocol."
1875 ::= { tcp 23 }
1876
1877 <span class="h4"><a class="selflink" id="section-5.5.3" href="#section-5.5.3">5.5.3</a>. SMTP</span>
1878
1879 smtp PROTOCOL-IDENTIFIER
1880 PARAMETERS { }
1881 ATTRIBUTES { }
1882 DESCRIPTION
1883 "The Simple Mail Transfer Protocol; SMTP control and data
1884 messages are sent on this port."
1885 REFERENCE
1886 "<a href="./rfc821">RFC 821</a> [<a href="./rfc821">RFC821</a>] defines the basic Simple Mail Transfer
1887 Protocol."
1888 ::= { tcp 25 }
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900 <span class="grey">Bierman &amp; Iddon Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1903
1904
1905 <span class="h4"><a class="selflink" id="section-5.5.4" href="#section-5.5.4">5.5.4</a>. DNS</span>
1906
1907 domain PROTOCOL-IDENTIFIER
1908 PARAMETERS { }
1909 ATTRIBUTES { }
1910 DESCRIPTION
1911 "Domain Name Service Protocol; DNS may be transported by either
1912 UDP [<a href="./rfc768">RFC768</a>] or TCP [<a href="./rfc793">RFC793</a>]. If the transport is UDP, DNS
1913 requests restricted to 512 bytes in length may be sent to this
1914 port."
1915 REFERENCE
1916 "<a href="./rfc1035">RFC 1035</a> [<a href="./rfc1035">RFC1035</a>] defines the Bootstrap Protocol."
1917 ::= { udp 53,
1918 tcp 53 }
1919
1920 <span class="h4"><a class="selflink" id="section-5.5.5" href="#section-5.5.5">5.5.5</a>. BOOTP</span>
1921
1922 <span class="h5"><a class="selflink" id="section-5.5.5.1" href="#section-5.5.5.1">5.5.5.1</a>. Bootstrap Server Protocol</span>
1923
1924 bootps PROTOCOL-IDENTIFIER
1925 PARAMETERS { }
1926 ATTRIBUTES { }
1927 DESCRIPTION
1928 "Bootstrap Protocol Server Protocol; BOOTP Clients send requests
1929 (usually broadcast) to the bootps port."
1930 REFERENCE
1931 "<a href="./rfc951">RFC 951</a> [<a href="./rfc951">RFC951</a>] defines the Bootstrap Protocol."
1932 ::= { udp 67 }
1933
1934 <span class="h5"><a class="selflink" id="section-5.5.5.2" href="#section-5.5.5.2">5.5.5.2</a>. Bootstrap Client Protocol</span>
1935
1936 bootpc PROTOCOL-IDENTIFIER
1937 PARAMETERS { }
1938 ATTRIBUTES { }
1939 DESCRIPTION
1940 "Bootstrap Protocol Client Protocol; BOOTP Server replies are
1941 sent to the BOOTP Client using this destination port."
1942 REFERENCE
1943 "<a href="./rfc951">RFC 951</a> [<a href="./rfc951">RFC951</a>] defines the Bootstrap Protocol."
1944 ::= { udp 68 }
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956 <span class="grey">Bierman &amp; Iddon Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
1959
1960
1961 <span class="h4"><a class="selflink" id="section-5.5.6" href="#section-5.5.6">5.5.6</a>. TFTP</span>
1962
1963 tftp PROTOCOL-IDENTIFIER
1964 PARAMETERS {
1965 tracksSessions(1)
1966 }
1967 ATTRIBUTES { }
1968 DESCRIPTION
1969 "Trivial File Transfer Protocol; Only the first packet of each
1970 TFTP transaction will be sent to port 69. If the tracksSessions
1971 attribute is set, then packets for each TFTP transaction will be
1972 attributed to tftp, instead of the unregistered port numbers that
1973 will be encoded in subsequent packets."
1974 REFERENCE
1975 "<a href="./rfc1350">RFC 1350</a> [<a href="./rfc1350">RFC1350</a>] defines the TFTP Protocol (revision 2); <a href="./rfc1782">RFC</a>
1976 <a href="./rfc1782">1782</a> [<a href="./rfc1782">RFC1782</a>] defines TFTP Option Extensions; <a href="./rfc1783">RFC 1783</a> [<a href="./rfc1783">RFC1783</a>]
1977 defines the TFTP Blocksize Option; <a href="./rfc1784">RFC 1784</a> [<a href="./rfc1784">RFC1784</a>] defines
1978 TFTP Timeout Interval and Transfer Size Options."
1979
1980 ::= { udp 69 }
1981
1982 <span class="h4"><a class="selflink" id="section-5.5.7" href="#section-5.5.7">5.5.7</a>. HTTP</span>
1983
1984 www-http PROTOCOL-IDENTIFIER
1985 PARAMETERS { }
1986 ATTRIBUTES { }
1987 DESCRIPTION
1988 "Hypertext Transfer Protocol; "
1989 REFERENCE
1990 "<a href="./rfc1945">RFC 1945</a> [<a href="./rfc1945">RFC1945</a>] defines the Hypertext Transfer Protocol
1991 (HTTP/1.0)."
1992 ::= { tcp 80 }
1993
1994 <span class="h4"><a class="selflink" id="section-5.5.8" href="#section-5.5.8">5.5.8</a>. POP3</span>
1995
1996 pop3 PROTOCOL-IDENTIFIER
1997 PARAMETERS { }
1998 ATTRIBUTES { }
1999 DESCRIPTION
2000 "Post Office Protocol -- Version 3. Clients establish connections
2001 with POP3 servers by using this destination port number."
2002 REFERENCE
2003 "<a href="./rfc1725">RFC 1725</a> [<a href="./rfc1725">RFC1725</a>] defines Version 3 of the Post Office
2004 Protocol."
2005 ::= { tcp 110 }
2006
2007
2008
2009
2010
2011
2012 <span class="grey">Bierman &amp; Iddon Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
2015
2016
2017 <span class="h4"><a class="selflink" id="section-5.5.9" href="#section-5.5.9">5.5.9</a>. SUNRPC</span>
2018
2019 sunrpc PROTOCOL-IDENTIFIER
2020 PARAMETERS { }
2021 ATTRIBUTES {
2022 hasChildren(0) -- port mapper function numbers
2023 }
2024 DESCRIPTION
2025 "SUN Remote Procedure Call Protocol. Port mapper function
2026 requests are sent to this destination port."
2027 CHILDREN
2028 Specific RPC functions are represented as children of the sunrpc
2029 protocol. Each 'RPC function protocol' is identified by its
2030 function number assignment. RPC function number assignments are
2031 defined by different naming authorities, depending of the
2032 function identifier value.
2033 From [<a href="./rfc1831">RFC1831</a>]:
2034
2035 Program numbers are given out in groups of hexadecimal 20000000
2036 (decimal 536870912) according to the following chart:
2037
2038 0 - 1fffffff defined by [email protected]
2039 20000000 - 3fffffff defined by user
2040 40000000 - 5fffffff transient
2041 60000000 - 7fffffff reserved
2042 80000000 - 9fffffff reserved
2043 a0000000 - bfffffff reserved
2044 c0000000 - dfffffff reserved
2045 e0000000 - ffffffff reserved
2046
2047 Children of 'sunrpc' are encoded as [ 0.0.0.111], the protocol
2048 identifier component for 'sunrpc', followed by [ a.b.c.d ], where
2049 a.b.c.d is the 32 bit binary RPC program number encoded in
2050 network byte order. For example, a protocolDirID-fragment value
2051 of:
2052 0.0.0.111.0.1.134.163
2053
2054 defines the NFS function (and protocol).
2055
2056 Children are named as 'sunrpc' followed by the RPC function
2057 number in base 10 format. For example, NFS would be named:
2058 'sunrpc 100003'.
2059 REFERENCE
2060 "<a href="./rfc1831">RFC 1831</a> [<a href="./rfc1831">RFC1831</a>] defines the Remote Procedure Call Protocol
2061 Version 2. The authoritative list of RPC Functions is identified
2062 by the URL:
2063 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/sun-rpc-numbers">ftp://ftp.isi.edu/in-notes/iana/assignments/sun-rpc-numbers</a>"
2064 ::= { udp 111 }
2065
2066
2067
2068 <span class="grey">Bierman &amp; Iddon Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
2071
2072
2073 <span class="h4"><a class="selflink" id="section-5.5.10" href="#section-5.5.10">5.5.10</a>. NFS</span>
2074
2075 nfs PROTOCOL-IDENTIFIER
2076 PARAMETERS {
2077 countsFragments(0)
2078 }
2079 ATTRIBUTES { }
2080 DESCRIPTION
2081 "Sun Network File System (NFS);"
2082 DECODING
2083 "The first packet in an NFS transaction is sent to the port-
2084 mapper, and therefore decoded statically by monitoring RFC
2085 portmap requests [<a href="./rfc1831">RFC1831</a>]. Any subsequent NFS fragments must be
2086 decoded and correctly identified by 'remembering' the port
2087 assignments used in each RPC function call (as identified
2088 according to the procedures in the RPC Specification Version 2
2089 [<a href="./rfc1831">RFC1831</a>]).
2090
2091 The 'countsFragments(0)' PARAMETER bit is used to indicate
2092 whether the probe can (and should) monitor portmapper activity to
2093 correctly attribute all NFS packets."
2094 REFERENCE
2095 "The NFS Version 3 Protocol Specification is defined in <a href="./rfc1813">RFC 1813</a>
2096 [<a href="./rfc1813">RFC1813</a>]."
2097 ::= {
2098 sunrpc 100003 -- [0.1.134.163]
2099 }
2100
2101 <span class="h4"><a class="selflink" id="section-5.5.11" href="#section-5.5.11">5.5.11</a>. SNMP</span>
2102
2103 <span class="h5"><a class="selflink" id="section-5.5.11.1" href="#section-5.5.11.1">5.5.11.1</a>. SNMP Request/Response</span>
2104
2105 snmp PROTOCOL-IDENTIFIER
2106 PARAMETERS { }
2107 ATTRIBUTES { }
2108 DESCRIPTION
2109 "Simple Network Management Protocol. Includes SNMPv1 and SNMPv2
2110 protocol versions. Does not include SNMP trap packets."
2111 REFERENCE
2112 "The SNMP SMI is defined in <a href="./rfc1902">RFC 1902</a> [<a href="./rfc1902">RFC1902</a>]. The SNMP
2113 protocol is defined in <a href="./rfc1905">RFC 1905</a> [<a href="./rfc1905">RFC1905</a>]. Transport mappings
2114 are defined in <a href="./rfc1906">RFC 1906</a> [<a href="./rfc1906">RFC1906</a>]; <a href="./rfc1420">RFC 1420</a> (SNMP over IPX)
2115 [<a href="./rfc1420">RFC1420</a>]; <a href="./rfc1419">RFC 1419</a> (SNMP over AppleTalk) [<a href="./rfc1419">RFC1419</a>]."
2116 ::= {
2117 udp 161,
2118 ipx 0x900f, -- [ 0.0.144.15 ]
2119 atalk 8
2120 }
2121
2122
2123
2124 <span class="grey">Bierman &amp; Iddon Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
2127
2128
2129 <span class="h5"><a class="selflink" id="section-5.5.11.2" href="#section-5.5.11.2">5.5.11.2</a>. SNMP Trap</span>
2130
2131 snmptrap PROTOCOL-IDENTIFIER
2132 PARAMETERS { }
2133 ATTRIBUTES { }
2134 DESCRIPTION
2135 "Simple Network Management Protocol Trap Port."
2136 REFERENCE
2137 "The SNMP SMI is defined in <a href="./rfc1902">RFC 1902</a> [<a href="./rfc1902">RFC1902</a>]. The SNMP
2138 protocol is defined in <a href="./rfc1905">RFC 1905</a> [<a href="./rfc1905">RFC1905</a>]. Transport mappings
2139 are defined in <a href="./rfc1906">RFC 1906</a> [<a href="./rfc1906">RFC1906</a>]; <a href="./rfc1420">RFC 1420</a> (SNMP over IPX)
2140 [<a href="./rfc1420">RFC1420</a>]; <a href="./rfc1419">RFC 1419</a> (SNMP over AppleTalk) [<a href="./rfc1419">RFC1419</a>]."
2141 ::= {
2142 udp 162,
2143 ipx 0x9010,
2144 atalk 9
2145 }
2146
2147 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
2148
2149 This document was produced by the IETF RMONMIB Working Group.
2150
2151 The authors wish to thank the following people for their
2152 contributions to this document:
2153
2154 Anil Singhal
2155 Frontier Software Development, Inc.
2156
2157 Jeanne Haney
2158 Bay Networks
2159
2160 Dan Hansen
2161 Network General Corp.
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180 <span class="grey">Bierman &amp; Iddon Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
2183
2184
2185 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
2186
2187 [<a id="ref-RFC768">RFC768</a>]
2188 Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>,
2189 USC/Information Sciences Institute, August 1980.
2190
2191 [<a id="ref-RFC791">RFC791</a>]
2192 Postel, J., ed., "Internet Protocol - DARPA Internet Program
2193 Protocol Specification", STD 5, <a href="./rfc791">RFC 791</a>, USC/Information Sciences
2194 Institute, September 1981.
2195
2196 [<a id="ref-RFC792">RFC792</a>]
2197 Postel, J., "Internet Control Message Protocol - DARPA Internet
2198 Program Protocol Specification", STD 5, <a href="./rfc792">RFC 792</a>, USC/Information
2199 Sciences Institute, September 1981.
2200
2201 [<a id="ref-RFC793">RFC793</a>]
2202 Postel, J., "Transmission Control Protocol - DARPA Internet Program
2203 Protocol Specification", STD 5, <a href="./rfc793">RFC 793</a>, USC/Information Sciences
2204 Institute, September 1981.
2205
2206 [<a id="ref-RFC821">RFC821</a>]
2207 Postel, J., "Simple Mail Transfer Protocol", STD 10, <a href="./rfc821">RFC 821</a>,
2208 USC/Information Sciences Institute, August 1982.
2209
2210 [<a id="ref-RFC826">RFC826</a>]
2211 Plummer, D., "An Ethernet Address Resolution Protocol or
2212 "Converting Network Protocol Addresses to 48-bit Ethernet Addresses
2213 for Transmission on Ethernet Hardware", STD 37, <a href="./rfc826">RFC 826</a>, MIT-LCS,
2214 November 1982.
2215
2216 [<a id="ref-RFC854">RFC854</a>]
2217 Postel, J. and J. Reynolds, "Telnet Protocol Specification",
2218 STD 8, <a href="./rfc854">RFC 854</a>, ISI, May 1983.
2219
2220 [<a id="ref-RFC894">RFC894</a>]
2221 Hornig, C., "A Standard for the Transmission of IP Datagrams over
2222 Ethernet Networks", <a href="./rfc894">RFC 894</a>, Symbolics, April 1984.
2223
2224 [<a id="ref-RFC951">RFC951</a>]
2225 Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)", <a href="./rfc951">RFC 951</a>,
2226 Stanford and SUN Microsytems, September 1985.
2227
2228 [<a id="ref-RFC959">RFC959</a>]
2229 Postel, J., and J. Reynolds, "File Transfer Protocol", STD 8,
2230 <a href="./rfc959">RFC 959</a>, USC/Information Sciences Institute, October 1985.
2231
2232
2233
2234
2235
2236 <span class="grey">Bierman &amp; Iddon Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
2239
2240
2241 [<a id="ref-RFC1035">RFC1035</a>]
2242 Mockapetris, P., "Domain Names - Implementation and Specification",
2243 STD 13, <a href="./rfc1035">RFC 1035</a>, USC/Information Sciences Institute, November
2244 1987.
2245
2246 [<a id="ref-RFC1157">RFC1157</a>]
2247 Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network
2248 Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, SNMP Research,
2249 Performance Systems International, MIT Laboratory for Computer
2250 Science, May 1990.
2251
2252 [<a id="ref-RFC1213">RFC1213</a>]
2253 McCloghrie, K., and M. Rose, Editors, "Management Information Base
2254 for Network Management of TCP/IP-based internets: MIB-II", STD 17,
2255 <a href="./rfc1213">RFC 1213</a>, Hughes LAN Systems, Performance Systems International,
2256 March 1991.
2257
2258 [<a id="ref-RFC1350">RFC1350</a>]
2259 Sollins, K., "TFTP Protocol (revision 2)", <a href="./rfc1350">RFC 1350</a>, MIT, July
2260 1992.
2261
2262 [<a id="ref-RFC1419">RFC1419</a>]
2263 Minshall, G., and M. Ritter, "SNMP over AppleTalk", <a href="./rfc1419">RFC 1419</a>,
2264 Novell, Inc., Apple Computer, Inc., March 1993.
2265
2266 [<a id="ref-RFC1420">RFC1420</a>]
2267 Bostock, S., "SNMP over IPX", <a href="./rfc1420">RFC 1420</a>, Novell, Inc., March 1993.
2268
2269 [<a id="ref-RFC1700">RFC1700</a>]
2270 Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1700">RFC 1700</a>,
2271 USC/Information Sciences Institute, October 1994.
2272
2273 [<a id="ref-RFC1725">RFC1725</a>]
2274 Myers, J., and M. Rose, "Post Office Protocol - Version 3", <a href="./rfc1725">RFC</a>
2275 <a href="./rfc1725">1725</a>, Carnegie Mellon, Dover Beach Consulting, November 1994.
2276
2277 [<a id="ref-RFC1757">RFC1757</a>]
2278 S. Waldbusser, "Remote Network Monitoring MIB", <a href="./rfc1757">RFC 1757</a>, Carnegie
2279 Mellon University, February 1995.
2280
2281 [<a id="ref-RFC1782">RFC1782</a>]
2282 Malkin, G., and A. Harkin, T "TFTP Option Extension", <a href="./rfc1782">RFC 1782</a>,
2283 Xylogics, Inc., Hewlett Packard Co., March 1995.
2284
2285 [<a id="ref-RFC1783">RFC1783</a>]
2286 Malkin, G., and A. Harkin, T "TFTP BlockOption Option", <a href="./rfc1783">RFC 1783</a>,
2287 Xylogics, Inc., Hewlett Packard Co., March 1995.
2288
2289
2290
2291
2292 <span class="grey">Bierman &amp; Iddon Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
2295
2296
2297 [<a id="ref-RFC1784">RFC1784</a>]
2298 Malkin, G., and A. Harkin, "TFTP Timeout Interval and Transfer Size
2299 Options", <a href="./rfc1784">RFC 1784</a>, Xylogics, Inc., Hewlett Packard Co., March
2300 1995.
2301
2302 [<a id="ref-RFC1800">RFC1800</a>]
2303 Postel, J., Editor, "Internet Official Protocol Standards", STD 1,
2304 <a href="./rfc1920">RFC 1920</a>, IAB, March 1996.
2305
2306 [<a id="ref-RFC1831">RFC1831</a>]
2307 Srinivasan, R., "Remote Procedure Call Protocol Version 2", <a href="./rfc1831">RFC</a>
2308 <a href="./rfc1831">1831</a>, Sun Microsystems, Inc., August 1995.
2309
2310 [<a id="ref-RFC1902">RFC1902</a>]
2311 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
2312 S. Waldbusser, "Structure of Management Information for version 2
2313 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>,
2314 January 1996.
2315
2316 [<a id="ref-RFC1903">RFC1903</a>]
2317 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
2318 S. Waldbusser, "Textual Conventions for version 2 of the Simple
2319 Network Management Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996.
2320
2321 [<a id="ref-RFC1904">RFC1904</a>]
2322 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
2323 S. Waldbusser, "Conformance Statements for version 2 of the Simple
2324 Network Management Protocol (SNMPv2)", <a href="./rfc1904">RFC 1904</a>, January 1996.
2325
2326 [<a id="ref-RFC1905">RFC1905</a>]
2327 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
2328 S. Waldbusser, "Protocol Operations for version 2 of the Simple
2329 Network Management Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
2330
2331 [<a id="ref-RFC1906">RFC1906</a>]
2332 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
2333 Waldbusser, "Transport Mappings for Version 2 of the Simple Network
2334 Management Protocol (SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996.
2335
2336 [<a id="ref-RFC1945">RFC1945</a>]
2337 Berners-Lee, T., and R. Fielding, "Hypertext Transfer Protocol --
2338 HTTP/1.0", <a href="./rfc1945">RFC 1945</a>, MIT/UC-Irvine, November 1995.
2339
2340 [<a id="ref-RMON2">RMON2</a>]
2341 S. Waldbusser, "Remote Network Monitoring MIB (RMON-2)", <a href="./draft-ietf-rmonmib-rmon2-03.txt">draft-</a>
2342 <a href="./draft-ietf-rmonmib-rmon2-03.txt">ietf-rmonmib-rmon2-03.txt</a>, International Network Services, January
2343 1996.
2344
2345
2346
2347
2348 <span class="grey">Bierman &amp; Iddon Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc2074">RFC 2074</a> RMON Protocol Identifiers January 1997</span>
2351
2352
2353 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
2354
2355 Security issues are not discussed in this memo.
2356
2357 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Authors' Addresses</span>
2358
2359 Andy Bierman
2360 Cisco Systems, Inc.
2361 170 West Tasman Drive
2362 San Jose, CA 95134
2363
2364 Phone: 408-527-3711
2365 EMail: [email protected]
2366
2367
2368 Robin Iddon
2369 3Com/AXON
2370 40/50 Blackfrias Street
2371 Edinburgh, UK
2372
2373 Phone: +44 131.558.3888
2374 EMail: [email protected]
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404 Bierman &amp; Iddon Standards Track [Page 43]
2405 </pre>