1. -- file: SNMP-TARGET-MIB.my
2. -- Extracted from RFC3413 by MG-SOFT Corp.
3. -- Changes:
4. --      No changes needed.
5. -- http://www.mg-soft.com/
6.  
7. SNMP-TARGET-MIB DEFINITIONS ::= BEGIN
8.  
9.    IMPORTS
10.        MODULE-IDENTITY,
11.        OBJECT-TYPE,
12.        snmpModules,
13.        Counter32,
14.        Integer32
15.            FROM SNMPv2-SMI
16.  
17.        TEXTUAL-CONVENTION,
18.        TDomain,
19.        TAddress,
20.        TimeInterval,
21.        RowStatus,
22.        StorageType,
23.  
24.  
25.        TestAndIncr
26.            FROM SNMPv2-TC
27.  
28.        SnmpSecurityModel,
29.        SnmpMessageProcessingModel,
30.        SnmpSecurityLevel,
31.        SnmpAdminString
32.            FROM SNMP-FRAMEWORK-MIB
33.  
34.        MODULE-COMPLIANCE,
35.        OBJECT-GROUP
36.            FROM SNMPv2-CONF;
37.  
38.    snmpTargetMIB MODULE-IDENTITY
39.        LAST-UPDATED "200210140000Z"
40.        ORGANIZATION "IETF SNMPv3 Working Group"
41.        CONTACT-INFO
42.            "WG-email:   snmpv3@lists.tislabs.com
43.             Subscribe:  majordomo@lists.tislabs.com
44.                         In message body:  subscribe snmpv3
45.  
46.             Co-Chair:   Russ Mundy
47.                         Network Associates Laboratories
48.             Postal:     15204 Omega Drive, Suite 300
49.                         Rockville, MD 20850-4601
50.                         USA
51.             EMail:      mundy@tislabs.com
52.             Phone:      +1 301-947-7107
53.  
54.             Co-Chair:   David Harrington
55.                         Enterasys Networks
56.             Postal:     35 Industrial Way
57.                         P. O. Box 5004
58.                         Rochester, New Hampshire 03866-5005
59.                         USA
60.             EMail:      dbh@enterasys.com
61.             Phone:      +1 603-337-2614
62.  
63.             Co-editor:  David B. Levi
64.                         Nortel Networks
65.             Postal:     3505 Kesterwood Drive
66.                         Knoxville, Tennessee 37918
67.             EMail:      dlevi@nortelnetworks.com
68.             Phone:      +1 865 686 0432
69.  
70.             Co-editor:  Paul Meyer
71.                         Secure Computing Corporation
72.             Postal:     2675 Long Lake Road
73.  
74.  
75.                         Roseville, Minnesota 55113
76.             EMail:      paul_meyer@securecomputing.com
77.             Phone:      +1 651 628 1592
78.  
79.             Co-editor:  Bob Stewart
80.                         Retired"
81.        DESCRIPTION
82.            "This MIB module defines MIB objects which provide
83.             mechanisms to remotely configure the parameters used
84.             by an SNMP entity for the generation of SNMP messages.
85.  
86.             Copyright (C) The Internet Society (2002). This
87.             version of this MIB module is part of RFC 3413;
88.             see the RFC itself for full legal notices.
89.            "
90.        REVISION    "200210140000Z"             -- 14 October 2002
91.        DESCRIPTION "Fixed DISPLAY-HINTS for UTF-8 strings, fixed hex
92.                     value of LF characters, clarified meaning of zero
93.                     length tag values, improved tag list examples.
94.                     Published as RFC 3413."
95.        REVISION    "199808040000Z"             -- 4 August 1998
96.        DESCRIPTION "Clarifications, published as
97.                     RFC 2573."
98.        REVISION    "199707140000Z"             -- 14 July 1997
99.        DESCRIPTION "The initial revision, published as RFC2273."
100.        ::= { snmpModules 12 }
101.  
102.    snmpTargetObjects       OBJECT IDENTIFIER ::= { snmpTargetMIB 1 }
103.    snmpTargetConformance   OBJECT IDENTIFIER ::= { snmpTargetMIB 3 }
104.  
105.    SnmpTagValue ::= TEXTUAL-CONVENTION
106.        DISPLAY-HINT "255t"
107.        STATUS       current
108.        DESCRIPTION
109.            "An octet string containing a tag value.
110.             Tag values are preferably in human-readable form.
111.  
112.             To facilitate internationalization, this information
113.             is represented using the ISO/IEC IS 10646-1 character
114.             set, encoded as an octet string using the UTF-8
115.             character encoding scheme described in RFC 2279.
116.  
117.             Since additional code points are added by amendments
118.             to the 10646 standard from time to time,
119.             implementations must be prepared to encounter any code
120.             point from 0x00000000 to 0x7fffffff.
121.  
122.             The use of control codes should be avoided, and certain
123.  
124.  
125.             control codes are not allowed as described below.
126.  
127.             For code points not directly supported by user
128.             interface hardware or software, an alternative means
129.             of entry and display, such as hexadecimal, may be
130.             provided.
131.  
132.             For information encoded in 7-bit US-ASCII, the UTF-8
133.             representation is identical to the US-ASCII encoding.
134.  
135.             Note that when this TC is used for an object that
136.             is used or envisioned to be used as an index, then a
137.             SIZE restriction must be specified so that the number
138.             of sub-identifiers for any object instance does not
139.             exceed the limit of 128, as defined by [RFC1905].
140.  
141.             An object of this type contains a single tag value
142.             which is used to select a set of entries in a table.
143.  
144.             A tag value is an arbitrary string of octets, but
145.             may not contain a delimiter character.  Delimiter
146.             characters are defined to be one of the following:
147.  
148.                 -  An ASCII space character (0x20).
149.  
150.                 -  An ASCII TAB character (0x09).
151.  
152.                 -  An ASCII carriage return (CR) character (0x0D).
153.  
154.                 -  An ASCII line feed (LF) character (0x0A).
155.  
156.             Delimiter characters are used to separate tag values
157.             in a tag list.  An object of this type may only
158.             contain a single tag value, and so delimiter
159.             characters are not allowed in a value of this type.
160.  
161.             Note that a tag value of 0 length means that no tag is
162.             defined.  In other words, a tag value of 0 length would
163.             never match anything in a tag list, and would never
164.             select any table entries.
165.  
166.             Some examples of valid tag values are:
167.  
168.                 - 'acme'
169.  
170.                 - 'router'
171.  
172.                 - 'host'
173.  
174.  
175.             The use of a tag value to select table entries is
176.             application and MIB specific."
177.        SYNTAX       OCTET STRING (SIZE (0..255))
178.  
179.    SnmpTagList ::= TEXTUAL-CONVENTION
180.        DISPLAY-HINT "255t"
181.        STATUS       current
182.        DESCRIPTION
183.            "An octet string containing a list of tag values.
184.             Tag values are preferably in human-readable form.
185.  
186.             To facilitate internationalization, this information
187.             is represented using the ISO/IEC IS 10646-1 character
188.             set, encoded as an octet string using the UTF-8
189.             character encoding scheme described in RFC 2279.
190.  
191.             Since additional code points are added by amendments
192.             to the 10646 standard from time to time,
193.             implementations must be prepared to encounter any code
194.             point from 0x00000000 to 0x7fffffff.
195.  
196.             The use of control codes should be avoided, except as
197.             described below.
198.  
199.             For code points not directly supported by user
200.             interface hardware or software, an alternative means
201.             of entry and display, such as hexadecimal, may be
202.             provided.
203.  
204.             For information encoded in 7-bit US-ASCII, the UTF-8
205.             representation is identical to the US-ASCII encoding.
206.  
207.             An object of this type contains a list of tag values
208.             which are used to select a set of entries in a table.
209.  
210.             A tag value is an arbitrary string of octets, but
211.             may not contain a delimiter character.  Delimiter
212.             characters are defined to be one of the following:
213.  
214.                 -  An ASCII space character (0x20).
215.  
216.                 -  An ASCII TAB character (0x09).
217.  
218.                 -  An ASCII carriage return (CR) character (0x0D).
219.  
220.                 -  An ASCII line feed (LF) character (0x0A).
221.  
222.             Delimiter characters are used to separate tag values
223.  
224.  
225.             in a tag list.  Only a single delimiter character may
226.             occur between two tag values.  A tag value may not
227.             have a zero length.  These constraints imply certain
228.             restrictions on the contents of this object:
229.  
230.                 - There cannot be a leading or trailing delimiter
231.                   character.
232.  
233.                 - There cannot be multiple adjacent delimiter
234.                   characters.
235.  
236.             Some examples of valid tag lists are:
237.  
238.                 - ''                        -- an empty list
239.  
240.                 - 'acme'                    -- list of one tag
241.  
242.                 - 'host router bridge'      -- list of several tags
243.  
244.             Note that although a tag value may not have a length of
245.             zero, an empty string is still valid.  This indicates
246.             an empty list (i.e. there are no tag values in the list).
247.  
248.             The use of the tag list to select table entries is
249.             application and MIB specific.  Typically, an application
250.             will provide one or more tag values, and any entry
251.             which contains some combination of these tag values
252.             will be selected."
253.        SYNTAX       OCTET STRING (SIZE (0..255))
254.  
255.    --
256.    --
257.    -- The snmpTargetObjects group
258.    --
259.    --
260.  
261.    snmpTargetSpinLock OBJECT-TYPE
262.        SYNTAX      TestAndIncr
263.        MAX-ACCESS  read-write
264.        STATUS      current
265.        DESCRIPTION
266.            "This object is used to facilitate modification of table
267.             entries in the SNMP-TARGET-MIB module by multiple
268.             managers.  In particular, it is useful when modifying
269.             the value of the snmpTargetAddrTagList object.
270.  
271.             The procedure for modifying the snmpTargetAddrTagList
272.             object is as follows:
273.  
274.  
275.                 1.  Retrieve the value of snmpTargetSpinLock and
276.                     of snmpTargetAddrTagList.
277.  
278.                 2.  Generate a new value for snmpTargetAddrTagList.
279.  
280.                 3.  Set the value of snmpTargetSpinLock to the
281.                     retrieved value, and the value of
282.                     snmpTargetAddrTagList to the new value.  If
283.                     the set fails for the snmpTargetSpinLock
284.                     object, go back to step 1."
285.        ::= { snmpTargetObjects 1 }
286.  
287.    snmpTargetAddrTable OBJECT-TYPE
288.        SYNTAX      SEQUENCE OF SnmpTargetAddrEntry
289.        MAX-ACCESS  not-accessible
290.        STATUS      current
291.        DESCRIPTION
292.            "A table of transport addresses to be used in the generation
293.             of SNMP messages."
294.        ::= { snmpTargetObjects 2 }
295.  
296.    snmpTargetAddrEntry OBJECT-TYPE
297.        SYNTAX      SnmpTargetAddrEntry
298.        MAX-ACCESS  not-accessible
299.        STATUS      current
300.        DESCRIPTION
301.            "A transport address to be used in the generation
302.             of SNMP operations.
303.  
304.             Entries in the snmpTargetAddrTable are created and
305.             deleted using the snmpTargetAddrRowStatus object."
306.        INDEX { IMPLIED snmpTargetAddrName }
307.        ::= { snmpTargetAddrTable 1 }
308.  
309.    SnmpTargetAddrEntry ::= SEQUENCE {
310.        snmpTargetAddrName         SnmpAdminString,
311.        snmpTargetAddrTDomain      TDomain,
312.        snmpTargetAddrTAddress     TAddress,
313.        snmpTargetAddrTimeout      TimeInterval,
314.        snmpTargetAddrRetryCount   Integer32,
315.        snmpTargetAddrTagList      SnmpTagList,
316.        snmpTargetAddrParams       SnmpAdminString,
317.        snmpTargetAddrStorageType  StorageType,
318.        snmpTargetAddrRowStatus    RowStatus
319.    }
320.  
321.    snmpTargetAddrName OBJECT-TYPE
322.        SYNTAX      SnmpAdminString (SIZE(1..32))
323.  
324.  
325.        MAX-ACCESS  not-accessible
326.        STATUS      current
327.        DESCRIPTION
328.            "The locally arbitrary, but unique identifier associated
329.             with this snmpTargetAddrEntry."
330.        ::= { snmpTargetAddrEntry 1 }
331.  
332.    snmpTargetAddrTDomain OBJECT-TYPE
333.        SYNTAX      TDomain
334.        MAX-ACCESS  read-create
335.        STATUS      current
336.        DESCRIPTION
337.            "This object indicates the transport type of the address
338.             contained in the snmpTargetAddrTAddress object."
339.        ::= { snmpTargetAddrEntry 2 }
340.  
341.    snmpTargetAddrTAddress OBJECT-TYPE
342.        SYNTAX      TAddress
343.        MAX-ACCESS  read-create
344.        STATUS      current
345.        DESCRIPTION
346.            "This object contains a transport address.  The format of
347.             this address depends on the value of the
348.             snmpTargetAddrTDomain object."
349.        ::= { snmpTargetAddrEntry 3 }
350.  
351.    snmpTargetAddrTimeout OBJECT-TYPE
352.        SYNTAX      TimeInterval
353.        MAX-ACCESS  read-create
354.        STATUS      current
355.        DESCRIPTION
356.            "This object should reflect the expected maximum round
357.             trip time for communicating with the transport address
358.             defined by this row.  When a message is sent to this
359.             address, and a response (if one is expected) is not
360.             received within this time period, an implementation
361.             may assume that the response will not be delivered.
362.  
363.             Note that the time interval that an application waits
364.             for a response may actually be derived from the value
365.             of this object.  The method for deriving the actual time
366.             interval is implementation dependent.  One such method
367.             is to derive the expected round trip time based on a
368.             particular retransmission algorithm and on the number
369.             of timeouts which have occurred.  The type of message may
370.             also be considered when deriving expected round trip
371.             times for retransmissions.  For example, if a message is
372.             being sent with a securityLevel that indicates both
373.  
374.  
375.             authentication and privacy, the derived value may be
376.             increased to compensate for extra processing time spent
377.             during authentication and encryption processing."
378.        DEFVAL { 1500 }
379.        ::= { snmpTargetAddrEntry 4 }
380.  
381.    snmpTargetAddrRetryCount OBJECT-TYPE
382.        SYNTAX      Integer32 (0..255)
383.        MAX-ACCESS  read-create
384.        STATUS      current
385.        DESCRIPTION
386.            "This object specifies a default number of retries to be
387.             attempted when a response is not received for a generated
388.             message.  An application may provide its own retry count,
389.             in which case the value of this object is ignored."
390.        DEFVAL { 3 }
391.        ::= { snmpTargetAddrEntry 5 }
392.  
393.    snmpTargetAddrTagList OBJECT-TYPE
394.        SYNTAX      SnmpTagList
395.        MAX-ACCESS  read-create
396.        STATUS      current
397.        DESCRIPTION
398.            "This object contains a list of tag values which are
399.             used to select target addresses for a particular
400.             operation."
401.        DEFVAL { "" }
402.        ::= { snmpTargetAddrEntry 6 }
403.  
404.    snmpTargetAddrParams OBJECT-TYPE
405.        SYNTAX      SnmpAdminString (SIZE(1..32))
406.        MAX-ACCESS  read-create
407.        STATUS      current
408.        DESCRIPTION
409.            "The value of this object identifies an entry in the
410.             snmpTargetParamsTable.  The identified entry
411.             contains SNMP parameters to be used when generating
412.             messages to be sent to this transport address."
413.        ::= { snmpTargetAddrEntry 7 }
414.  
415.    snmpTargetAddrStorageType OBJECT-TYPE
416.        SYNTAX      StorageType
417.        MAX-ACCESS  read-create
418.        STATUS      current
419.        DESCRIPTION
420.            "The storage type for this conceptual row.
421.             Conceptual rows having the value 'permanent' need not
422.             allow write-access to any columnar objects in the row."
423.  
424.  
425.        DEFVAL { nonVolatile }
426.        ::= { snmpTargetAddrEntry 8 }
427.  
428.    snmpTargetAddrRowStatus OBJECT-TYPE
429.        SYNTAX      RowStatus
430.        MAX-ACCESS  read-create
431.        STATUS      current
432.        DESCRIPTION
433.            "The status of this conceptual row.
434.  
435.             To create a row in this table, a manager must
436.             set this object to either createAndGo(4) or
437.             createAndWait(5).
438.  
439.             Until instances of all corresponding columns are
440.             appropriately configured, the value of the
441.             corresponding instance of the snmpTargetAddrRowStatus
442.             column is 'notReady'.
443.  
444.             In particular, a newly created row cannot be made
445.             active until the corresponding instances of
446.             snmpTargetAddrTDomain, snmpTargetAddrTAddress, and
447.             snmpTargetAddrParams have all been set.
448.  
449.             The following objects may not be modified while the
450.             value of this object is active(1):
451.                 - snmpTargetAddrTDomain
452.                 - snmpTargetAddrTAddress
453.             An attempt to set these objects while the value of
454.             snmpTargetAddrRowStatus is active(1) will result in
455.             an inconsistentValue error."
456.        ::= { snmpTargetAddrEntry 9 }
457.  
458.    snmpTargetParamsTable OBJECT-TYPE
459.        SYNTAX      SEQUENCE OF SnmpTargetParamsEntry
460.        MAX-ACCESS  not-accessible
461.        STATUS      current
462.        DESCRIPTION
463.            "A table of SNMP target information to be used
464.             in the generation of SNMP messages."
465.        ::= { snmpTargetObjects 3 }
466.  
467.    snmpTargetParamsEntry OBJECT-TYPE
468.        SYNTAX      SnmpTargetParamsEntry
469.        MAX-ACCESS  not-accessible
470.        STATUS      current
471.        DESCRIPTION
472.            "A set of SNMP target information.
473.  
474.  
475.             Entries in the snmpTargetParamsTable are created and
476.             deleted using the snmpTargetParamsRowStatus object."
477.        INDEX { IMPLIED snmpTargetParamsName }
478.        ::= { snmpTargetParamsTable 1 }
479.  
480.    SnmpTargetParamsEntry ::= SEQUENCE {
481.        snmpTargetParamsName           SnmpAdminString,
482.        snmpTargetParamsMPModel        SnmpMessageProcessingModel,
483.        snmpTargetParamsSecurityModel  SnmpSecurityModel,
484.        snmpTargetParamsSecurityName   SnmpAdminString,
485.        snmpTargetParamsSecurityLevel  SnmpSecurityLevel,
486.        snmpTargetParamsStorageType    StorageType,
487.        snmpTargetParamsRowStatus      RowStatus
488.    }
489.  
490.    snmpTargetParamsName OBJECT-TYPE
491.        SYNTAX      SnmpAdminString (SIZE(1..32))
492.        MAX-ACCESS  not-accessible
493.        STATUS      current
494.        DESCRIPTION
495.            "The locally arbitrary, but unique identifier associated
496.             with this snmpTargetParamsEntry."
497.        ::= { snmpTargetParamsEntry 1 }
498.  
499.    snmpTargetParamsMPModel OBJECT-TYPE
500.        SYNTAX      SnmpMessageProcessingModel
501.        MAX-ACCESS  read-create
502.        STATUS      current
503.        DESCRIPTION
504.            "The Message Processing Model to be used when generating
505.             SNMP messages using this entry."
506.        ::= { snmpTargetParamsEntry 2 }
507.  
508.    snmpTargetParamsSecurityModel OBJECT-TYPE
509.        SYNTAX      SnmpSecurityModel (1..2147483647)
510.        MAX-ACCESS  read-create
511.        STATUS      current
512.        DESCRIPTION
513.            "The Security Model to be used when generating SNMP
514.              messages using this entry.  An implementation may
515.              choose to return an inconsistentValue error if an
516.              attempt is made to set this variable to a value
517.              for a security model which the implementation does
518.              not support."
519.        ::= { snmpTargetParamsEntry 3 }
520.  
521.    snmpTargetParamsSecurityName OBJECT-TYPE
522.        SYNTAX      SnmpAdminString
523.  
524.  
525.        MAX-ACCESS  read-create
526.        STATUS      current
527.        DESCRIPTION
528.            "The securityName which identifies the Principal on
529.             whose behalf SNMP messages will be generated using
530.             this entry."
531.        ::= { snmpTargetParamsEntry 4 }
532.  
533.    snmpTargetParamsSecurityLevel OBJECT-TYPE
534.        SYNTAX      SnmpSecurityLevel
535.        MAX-ACCESS  read-create
536.        STATUS      current
537.        DESCRIPTION
538.            "The Level of Security to be used when generating
539.             SNMP messages using this entry."
540.        ::= { snmpTargetParamsEntry 5 }
541.  
542.    snmpTargetParamsStorageType OBJECT-TYPE
543.        SYNTAX      StorageType
544.        MAX-ACCESS  read-create
545.        STATUS      current
546.        DESCRIPTION
547.            "The storage type for this conceptual row.
548.             Conceptual rows having the value 'permanent' need not
549.             allow write-access to any columnar objects in the row."
550.        DEFVAL { nonVolatile }
551.        ::= { snmpTargetParamsEntry 6 }
552.  
553.    snmpTargetParamsRowStatus OBJECT-TYPE
554.        SYNTAX      RowStatus
555.        MAX-ACCESS  read-create
556.        STATUS      current
557.        DESCRIPTION
558.            "The status of this conceptual row.
559.  
560.             To create a row in this table, a manager must
561.             set this object to either createAndGo(4) or
562.             createAndWait(5).
563.  
564.             Until instances of all corresponding columns are
565.             appropriately configured, the value of the
566.             corresponding instance of the snmpTargetParamsRowStatus
567.             column is 'notReady'.
568.  
569.             In particular, a newly created row cannot be made
570.             active until the corresponding
571.             snmpTargetParamsMPModel,
572.             snmpTargetParamsSecurityModel,
573.  
574.  
575.             snmpTargetParamsSecurityName,
576.             and snmpTargetParamsSecurityLevel have all been set.
577.  
578.             The following objects may not be modified while the
579.             value of this object is active(1):
580.                 - snmpTargetParamsMPModel
581.                 - snmpTargetParamsSecurityModel
582.                 - snmpTargetParamsSecurityName
583.                 - snmpTargetParamsSecurityLevel
584.             An attempt to set these objects while the value of
585.             snmpTargetParamsRowStatus is active(1) will result in
586.             an inconsistentValue error."
587.        ::= { snmpTargetParamsEntry 7 }
588.  
589.    snmpUnavailableContexts OBJECT-TYPE
590.        SYNTAX       Counter32
591.        MAX-ACCESS   read-only
592.        STATUS       current
593.        DESCRIPTION
594.            "The total number of packets received by the SNMP
595.             engine which were dropped because the context
596.             contained in the message was unavailable."
597.        ::= { snmpTargetObjects 4 }
598.  
599.    snmpUnknownContexts OBJECT-TYPE
600.        SYNTAX       Counter32
601.        MAX-ACCESS   read-only
602.        STATUS       current
603.        DESCRIPTION
604.            "The total number of packets received by the SNMP
605.             engine which were dropped because the context
606.             contained in the message was unknown."
607.        ::= { snmpTargetObjects 5 }
608.  
609.    --
610.    --
611.    -- Conformance information
612.    --
613.    --
614.  
615.    snmpTargetCompliances OBJECT IDENTIFIER ::=
616.                                            { snmpTargetConformance 1 }
617.    snmpTargetGroups      OBJECT IDENTIFIER ::=
618.                                            { snmpTargetConformance 2 }
619.  
620.    --
621.    --
622.    -- Compliance statements
623.  
624.  
625.    --
626.    --
627.  
628.    snmpTargetCommandResponderCompliance MODULE-COMPLIANCE
629.        STATUS      current
630.        DESCRIPTION
631.            "The compliance statement for SNMP entities which include
632.             a command responder application."
633.        MODULE -- This Module
634.            MANDATORY-GROUPS { snmpTargetCommandResponderGroup }
635.        ::= { snmpTargetCompliances 1 }
636.  
637.    snmpTargetBasicGroup OBJECT-GROUP
638.        OBJECTS {
639.            snmpTargetSpinLock,
640.            snmpTargetAddrTDomain,
641.            snmpTargetAddrTAddress,
642.            snmpTargetAddrTagList,
643.            snmpTargetAddrParams,
644.            snmpTargetAddrStorageType,
645.            snmpTargetAddrRowStatus,
646.            snmpTargetParamsMPModel,
647.            snmpTargetParamsSecurityModel,
648.            snmpTargetParamsSecurityName,
649.            snmpTargetParamsSecurityLevel,
650.            snmpTargetParamsStorageType,
651.            snmpTargetParamsRowStatus
652.        }
653.        STATUS      current
654.        DESCRIPTION
655.            "A collection of objects providing basic remote
656.             configuration of management targets."
657.        ::= { snmpTargetGroups 1 }
658.  
659.    snmpTargetResponseGroup OBJECT-GROUP
660.        OBJECTS {
661.            snmpTargetAddrTimeout,
662.            snmpTargetAddrRetryCount
663.        }
664.        STATUS      current
665.        DESCRIPTION
666.            "A collection of objects providing remote configuration
667.             of management targets for applications which generate
668.             SNMP messages for which a response message would be
669.             expected."
670.        ::= { snmpTargetGroups 2 }
671.  
672.    snmpTargetCommandResponderGroup OBJECT-GROUP
673.  
674.  
675.        OBJECTS {
676.            snmpUnavailableContexts,
677.            snmpUnknownContexts
678.        }
679.        STATUS      current
680.        DESCRIPTION
681.            "A collection of objects required for command responder
682.             applications, used for counting error conditions."
683.        ::= { snmpTargetGroups 3 }
684.  
685. END
686.