-- extracted from rfc1903.txtSNMPv2-TC DEFINITIONS ::= BEGINIMPORTS    ObjectSyntax, TimeTicks        FROM SNMPv2-SMI;-- definition of textual conventionsTEXTUAL-CONVENTION MACRO ::=BEGIN    TYPE NOTATION ::=                  DisplayPart                  "STATUS" Status                  "DESCRIPTION" Text                  ReferPart                  "SYNTAX" Syntax    VALUE NOTATION ::=                  value(VALUE Syntax)    DisplayPart ::=                  "DISPLAY-HINT" Text                | empty    Status ::=                  "current"                | "deprecated"                | "obsolete"    ReferPart ::=                  "REFERENCE" Text                | empty    -- uses the NVT ASCII character set    Text ::= """" string """"    Syntax ::=                  type(ObjectSyntax)                | "BITS" "{" Kibbles "}"    Kibbles ::=                  Kibble                | Kibbles "," Kibble    Kibble ::=                  identifier "(" nonNegativeNumber ")"ENDDisplayString ::= TEXTUAL-CONVENTION    DISPLAY-HINT "255a"    STATUS       current    DESCRIPTION            "Represents textual information taken from the NVT ASCII            character set, as defined in pages 4, 10-11 of RFC 854.            To summarize RFC 854, the NVT ASCII repertoire specifies:              - the use of character codes 0-127 (decimal)              - the graphics characters (32-126) are interpreted as                US ASCII              - NUL, LF, CR, BEL, BS, HT, VT and FF have the special                meanings specified in RFC 854              - the other 25 codes have no standard interpretation              - the sequence 'CR LF' means newline              - the sequence 'CR NUL' means carriage-return              - an 'LF' not preceded by a 'CR' means moving to the                same column on the next line.              - the sequence 'CR x' for any x other than LF or NUL is                illegal.  (Note that this also means that a string may                end with either 'CR LF' or 'CR NUL', but not with CR.)            Any object defined using this syntax may not exceed 255            characters in length."    SYNTAX       OCTET STRING (SIZE (0..255))PhysAddress ::= TEXTUAL-CONVENTION    DISPLAY-HINT "1x:"    STATUS       current    DESCRIPTION            "Represents media- or physical-level addresses."    SYNTAX       OCTET STRINGMacAddress ::= TEXTUAL-CONVENTION    DISPLAY-HINT "1x:"    STATUS       current    DESCRIPTION            "Represents an 802 MAC address represented in the            `canonical' order defined by IEEE 802.1a, i.e., as if it            were transmitted least significant bit first, even though            802.5 (in contrast to other 802.x protocols) requires MAC            addresses to be transmitted most significant bit first."    SYNTAX       OCTET STRING (SIZE (6))TruthValue ::= TEXTUAL-CONVENTION    STATUS       current    DESCRIPTION            "Represents a boolean value."    SYNTAX       INTEGER { true(1), false(2) }TestAndIncr ::= TEXTUAL-CONVENTION    STATUS       current    DESCRIPTION            "Represents integer-valued information used for atomic            operations.  When the management protocol is used to specify            that an object instance having this syntax is to be            modified, the new value supplied via the management protocol            must precisely match the value presently held by the            instance.  If not, the management protocol set operation            fails with an error of `inconsistentValue'.  Otherwise, if            the current value is the maximum value of 2^31-1 (2147483647            decimal), then the value held by the instance is wrapped to            zero; otherwise, the value held by the instance is            incremented by one.  (Note that regardless of whether the            management protocol set operation succeeds, the variable-            binding in the request and response PDUs are identical.)            The value of the ACCESS clause for objects having this            syntax is either `read-write' or `read-create'.  When an            instance of a columnar object having this syntax is created,            any value may be supplied via the management protocol.            When the network management portion of the system is re-            initialized, the value of every object instance having this            syntax must either be incremented from its value prior to            the re-initialization, or (if the value prior to the re-            initialization is unknown) be set to a pseudo-randomly            generated value."    SYNTAX       INTEGER (0..2147483647)AutonomousType ::= TEXTUAL-CONVENTION    STATUS       current    DESCRIPTION            "Represents an independently extensible type identification            value.  It may, for example, indicate a particular sub-tree            with further MIB definitions, or define a particular type of            protocol or hardware."    SYNTAX       OBJECT IDENTIFIERInstancePointer ::= TEXTUAL-CONVENTION    STATUS       obsolete    DESCRIPTION            "A pointer to either a specific instance of a MIB object or            a conceptual row of a MIB table in the managed device.  In            the latter case, by convention, it is the name of the            particular instance of the first accessible columnar object            in the conceptual row.            The two uses of this textual convention are replaced by            VariablePointer and RowPointer, respectively."    SYNTAX       OBJECT IDENTIFIERVariablePointer ::= TEXTUAL-CONVENTION    STATUS       current    DESCRIPTION            "A pointer to a specific object instance.  For example,            sysContact.0 or ifInOctets.3."    SYNTAX       OBJECT IDENTIFIERRowPointer ::= TEXTUAL-CONVENTION    STATUS       current    DESCRIPTION            "Represents a pointer to a conceptual row.  The value is the            name of the instance of the first accessible columnar object            in the conceptual row.            For example, ifIndex.3 would point to the 3rd row in the            ifTable (note that if ifIndex were not-accessible, then            ifDescr.3 would be used instead)."    SYNTAX       OBJECT IDENTIFIERRowStatus ::= TEXTUAL-CONVENTION    STATUS       current    DESCRIPTION            "The RowStatus textual convention is used to manage the            creation and deletion of conceptual rows, and is used as the            value of the SYNTAX clause for the status column of a            conceptual row (as described in Section 7.7.1 of [2].)            The status column has six defined values:                 - `active', which indicates that the conceptual row is                 available for use by the managed device;                 - `notInService', which indicates that the conceptual                 row exists in the agent, but is unavailable for use by                 the managed device (see NOTE below);                 - `notReady', which indicates that the conceptual row                 exists in the agent, but is missing information                 necessary in order to be available for use by the                 managed device;                 - `createAndGo', which is supplied by a management                 station wishing to create a new instance of a                 conceptual row and to have its status automatically set                 to active, making it available for use by the managed                 device;                 - `createAndWait', which is supplied by a management                 station wishing to create a new instance of a                 conceptual row (but not make it available for use by                 the managed device); and,                 - `destroy', which is supplied by a management station                 wishing to delete all of the instances associated with                 an existing conceptual row.            Whereas five of the six values (all except `notReady') may            be specified in a management protocol set operation, only            three values will be returned in response to a management            protocol retrieval operation:  `notReady', `notInService' or            `active'.  That is, when queried, an existing conceptual row            has only three states:  it is either available for use by            the managed device (the status column has value `active');            it is not available for use by the managed device, though            the agent has sufficient information to make it so (the            status column has value `notInService'); or, it is not            available for use by the managed device, and an attempt to            make it so would fail because the agent has insufficient            information (the state column has value `notReady').                                     NOTE WELL                 This textual convention may be used for a MIB table,                 irrespective of whether the values of that table's                 conceptual rows are able to be modified while it is                 active, or whether its conceptual rows must be taken                 out of service in order to be modified.  That is, it is                 the responsibility of the DESCRIPTION clause of the                 status column to specify whether the status column must                 not be `active' in order for the value of some other                 column of the same conceptual row to be modified.  If                 such a specification is made, affected columns may be                 changed by an SNMP set PDU if the RowStatus would not