view release on metacpan or  search on metacpan

NPAdmin/MIBs/Printer-MIB.txt  view on Meta::CPAN

            State is On-Line                 0
            State is Off-Line               32

    Transitioning

            Currently at intended state      0
            Transitioning to intended state 64  "

    SYNTAX       INTEGER (0..126)

PresentOnOff ::= TEXTUAL-CONVENTION
    -- This is a type 1 enumeration.
    STATUS       current
    DESCRIPTION
        "Presence and configuration of a device or feature."
    SYNTAX       INTEGER {
                     other(1),
                     on(3),
                     off(4),
                     notPresent(5)
                 }

CodedCharSet ::= TEXTUAL-CONVENTION
      -- This is a type 3 enumeration.
      STATUS     current
      DESCRIPTION
         "A coded character set value that specifies both a set
         of characters that may be used and an encoding (as one
         or more octets) that is used to represent the characters
         in the set. These values are to be used to identify the
         encoding employed for strings in the MIB where this is
         not fixed by the MIB.

         Some objects that allow a choice of coded character set
         are: the prtLocalizationCharacterSet object in the
         LocalizationTable and prtInterpreterDefaultCharSetIn.
         The prtGeneralCurrentLocalization and
         prtConsoleLocalization objects in turn contain the index
         in the LocalizationTable of the current localization
         (country, language, and coded character set) of the
         'description' objects and the console, respectively.

         The space of the coded character set enumeration has
         been divided into three regions. The first region (3-
         999) consists of coded character sets that have been
         standardized by some standard setting organization. This
         region is intended for standards that do not have subset
         implementations. The second region (1000-1999) is for
         the Unicode and ISO/IEC 10646 coded character sets
         together with a specification of a (set of) sub-
         repertoires that may occur.  The third region (>1999) is
         intended for vendor specific coded character sets.

         NOTE: Unicode and ISO 10646 character coded data may be
         processed and stored in either Big Endian (most
         significant octet first) or Little Endian (least
         significant octet first) order.  Intel x86, VAX, and
         Alpha/AXP architectures are examples of Little Endian
         processor architectures. Furthermore, in environments
         where either order may occur, so-called Unicode BYTE
         ORDER MARK (BOM) character (which is ISO 10646 ZERO
         WIDTH NO BREAK SPACE), coded as FEFF in two octets and
         0000FEFF in four octets is used at the beginning of the
         data as a signature to indicate the order of the
         following data (See ISO 10646 Annex F).  Thus either
         ordering and BOM may occur in print data streams sent to
         the interpreter.  However, ISO 8824/8825 (ASN.1/BER)
         used by SNMP is quite clear that Big Endian order shall
         be used and BOM shall NOT be used in transmission in the
         protocol. Transmitting Unicode in Big Endian order in
         SNMP should not prove to be a hardship for Little Endian
         machines, since SNMP ASN.1/BER requires integers to be
         transmitted in Big Endian order as well.  So SNMP
         implementations on Little Endian machines are already
         reversing the order of integers to make them Big Endian
         for transmission via SNMP.  Also Unicode characters are
         usually treated as two-octet integers, not short text
         strings, so that it will be straightforward for Little
         Endian machines to reverse the order of Unicode
         character octets as well before transmitting them and
         after receiving them via the SNMP protocol.

         Where a given coded character set may be known by more
         than one name, the most commonly known name is used as
         the name of the enumeration and other names are shown in
         the comments.  The comments also indicate where to find
         detailed information on the coded character set and
         briefly characterize its relationship to other similar
         coded character sets.

         The current list of character sets and their enumerated
         values used to reference them is contained in the IANA
         Character Set registry.  The enum value is indicated by
         the MIB enum entry in the registry.  The enum symbol is
         indicated by the Alias that starts with 'cs' for
         character set.

         The IANA character sets registry is available via
         anonymous ftp.

         The ftp server is ftp.isi.edu. The subdirectory is /in-
         notes/iana/assignments/.

         The file name is character-sets.

         To add a character set to the IANA Registry:

         1. Format an entry like those in the current list,
         omitting the MIBenum value.
         2. Send the entry with a request to add the entry to the
         character set list to iana@ISI.EDU.
         3. The IANA will supply a unique MIBenum value and
         update the list."

     SYNTAX     INTEGER {
        other(1)      -- used if the designated coded
                      -- character set is not currently in
                      -- the enumeration

      -- See IANA Registry for standard character sets in the
      -- MIBenum range of 3-999.
      -- See IANA Registry for Unicode and vendor-supplied
      -- combinations of ISO collections and character sets based
      -- on Unicode in the MIBenum range of 1000-1999.
      -- See IANA Registry for vendor developed character sets
      -- in the MIBenum range of 2000-xxxx.
   }