SNMP-TARGET-MIB DEFINITIONS ::= BEGIN

IMPORTS

MODULE-IDENTITY,
OBJECT-TYPE,
snmpModules,
Counter32,
Integer32
    FROM SNMPv2-SMI

TEXTUAL-CONVENTION,
TDomain,
TAddress,
TimeInterval,
RowStatus,
StorageType,
TestAndIncr
    FROM SNMPv2-TC

SnmpSecurityModel,
SnmpMessageProcessingModel,
SnmpSecurityLevel,
SnmpAdminString
    FROM SNMP-FRAMEWORK-MIB

MODULE-COMPLIANCE,
OBJECT-GROUP
    FROM SNMPv2-CONF;

snmpTargetMIB MODULE-IDENTITY

LAST-UPDATED "200210140000Z"
ORGANIZATION "IETF SNMPv3 Working Group"
CONTACT-INFO
    "WG-email:   snmpv3@lists.tislabs.com
     Subscribe:  majordomo@lists.tislabs.com
                 In message body:  subscribe snmpv3

     Co-Chair:   Russ Mundy
                 Network Associates Laboratories
     Postal:     15204 Omega Drive, Suite 300
                 Rockville, MD 20850-4601
                 USA
     EMail:      mundy@tislabs.com
     Phone:      +1 301-947-7107

     Co-Chair:   David Harrington
                 Enterasys Networks
     Postal:     35 Industrial Way
                 P. O. Box 5004
                 Rochester, New Hampshire 03866-5005
                 USA
     EMail:      dbh@enterasys.com
     Phone:      +1 603-337-2614

     Co-editor:  David B. Levi
                 Nortel Networks
     Postal:     3505 Kesterwood Drive
                 Knoxville, Tennessee 37918
     EMail:      dlevi@nortelnetworks.com
     Phone:      +1 865 686 0432

     Co-editor:  Paul Meyer
                 Secure Computing Corporation
     Postal:     2675 Long Lake Road

                 Roseville, Minnesota 55113
     EMail:      paul_meyer@securecomputing.com
     Phone:      +1 651 628 1592

     Co-editor:  Bob Stewart
                 Retired"
DESCRIPTION
    "This MIB module defines MIB objects which provide
     mechanisms to remotely configure the parameters used
     by an SNMP entity for the generation of SNMP messages.

     Copyright (C) The Internet Society (2002). This
     version of this MIB module is part of RFC 3413;
     see the RFC itself for full legal notices.
    "
REVISION    "200210140000Z"             -- 14 October 2002
DESCRIPTION "Fixed DISPLAY-HINTS for UTF-8 strings, fixed hex
             value of LF characters, clarified meaning of zero
             length tag values, improved tag list examples.
             Published as RFC 3413."
REVISION    "199808040000Z"             -- 4 August 1998
DESCRIPTION "Clarifications, published as
             RFC 2573."
REVISION    "199707140000Z"             -- 14 July 1997
DESCRIPTION "The initial revision, published as RFC2273."
::= { snmpModules 12 }

snmpTargetObjects OBJECT IDENTIFIER ::= { snmpTargetMIB 1 } snmpTargetConformance OBJECT IDENTIFIER ::= { snmpTargetMIB 3 }

SnmpTagValue ::= TEXTUAL-CONVENTION

DISPLAY-HINT "255t"
STATUS       current
DESCRIPTION
    "An octet string containing a tag value.
     Tag values are preferably in human-readable form.

     To facilitate internationalization, this information
     is represented using the ISO/IEC IS 10646-1 character
     set, encoded as an octet string using the UTF-8
     character encoding scheme described in RFC 2279.

     Since additional code points are added by amendments
     to the 10646 standard from time to time,
     implementations must be prepared to encounter any code
     point from 0x00000000 to 0x7fffffff.

     The use of control codes should be avoided, and certain

     control codes are not allowed as described below.

     For code points not directly supported by user
     interface hardware or software, an alternative means
     of entry and display, such as hexadecimal, may be
     provided.

     For information encoded in 7-bit US-ASCII, the UTF-8
     representation is identical to the US-ASCII encoding.

     Note that when this TC is used for an object that
     is used or envisioned to be used as an index, then a
     SIZE restriction must be specified so that the number
     of sub-identifiers for any object instance does not
     exceed the limit of 128, as defined by [RFC1905].

     An object of this type contains a single tag value
     which is used to select a set of entries in a table.

     A tag value is an arbitrary string of octets, but
     may not contain a delimiter character.  Delimiter
     characters are defined to be one of the following:

         -  An ASCII space character (0x20).

         -  An ASCII TAB character (0x09).

         -  An ASCII carriage return (CR) character (0x0D).

         -  An ASCII line feed (LF) character (0x0A).

     Delimiter characters are used to separate tag values
     in a tag list.  An object of this type may only
     contain a single tag value, and so delimiter
     characters are not allowed in a value of this type.

     Note that a tag value of 0 length means that no tag is
     defined.  In other words, a tag value of 0 length would
     never match anything in a tag list, and would never
     select any table entries.

     Some examples of valid tag values are:

         - 'acme'

         - 'router'

         - 'host'

     The use of a tag value to select table entries is
     application and MIB specific."
SYNTAX       OCTET STRING (SIZE (0..255))

SnmpTagList ::= TEXTUAL-CONVENTION

DISPLAY-HINT "255t"
STATUS       current
DESCRIPTION
    "An octet string containing a list of tag values.
     Tag values are preferably in human-readable form.

     To facilitate internationalization, this information
     is represented using the ISO/IEC IS 10646-1 character
     set, encoded as an octet string using the UTF-8
     character encoding scheme described in RFC 2279.

     Since additional code points are added by amendments
     to the 10646 standard from time to time,
     implementations must be prepared to encounter any code
     point from 0x00000000 to 0x7fffffff.

     The use of control codes should be avoided, except as
     described below.

     For code points not directly supported by user
     interface hardware or software, an alternative means
     of entry and display, such as hexadecimal, may be
     provided.

     For information encoded in 7-bit US-ASCII, the UTF-8
     representation is identical to the US-ASCII encoding.

     An object of this type contains a list of tag values
     which are used to select a set of entries in a table.

     A tag value is an arbitrary string of octets, but
     may not contain a delimiter character.  Delimiter
     characters are defined to be one of the following:

         -  An ASCII space character (0x20).

         -  An ASCII TAB character (0x09).

         -  An ASCII carriage return (CR) character (0x0D).

         -  An ASCII line feed (LF) character (0x0A).

     Delimiter characters are used to separate tag values

     in a tag list.  Only a single delimiter character may
     occur between two tag values.  A tag value may not
     have a zero length.  These constraints imply certain
     restrictions on the contents of this object:

         - There cannot be a leading or trailing delimiter
           character.

         - There cannot be multiple adjacent delimiter
           characters.

     Some examples of valid tag lists are:

         - ''                        -- an empty list

         - 'acme'                    -- list of one tag

         - 'host router bridge'      -- list of several tags

     Note that although a tag value may not have a length of
     zero, an empty string is still valid.  This indicates
     an empty list (i.e. there are no tag values in the list).

     The use of the tag list to select table entries is
     application and MIB specific.  Typically, an application
     will provide one or more tag values, and any entry
     which contains some combination of these tag values
     will be selected."
SYNTAX       OCTET STRING (SIZE (0..255))