OID reference

defaultCharacterSet

1.3.6.1.4.1.1206.4.2.6.4.10

Description

<Definition> Indicates the algorithm used to encode each characterNumber within a MULTI string. <Format> other (1): a read-only value indicating an encoding scheme other than those listed below, refer to the device manual. Implementations that support other encodings shall provide a parallel manufacturer-specific obje…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.6.4 (globalReport, multiCfg)
Node code
10
Node name
defaultCharacterSet
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.6.4.10
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.6.4.10
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 6 4 10}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) multiCfg(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) globalReport(4) defaultCharacterSet(10)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) multiCfg(4) defaultCharacterSet(10)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/6/4/10
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/4/10
  • /ISO/3/6/1/4/1/1206/4/2/6/4/10
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/multiCfg/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/multiCfg/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/multiCfg/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/multiCfg/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/multiCfg/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/multiCfg/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/multiCfg/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/globalReport/defaultCharacterSet
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/multiCfg/defaultCharacterSet
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
eightBit

Enumerated values

ValueName
1other
2eightBit
3utf8Style

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.6.4.10.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

defaultCharacterSet  OBJECT-TYPE 
SYNTAX      INTEGER {
                 other (1),
                 eightBit (2),
                 utf8Style (3)} 
MAX-ACCESS  read-write 
STATUS      current  
DESCRIPTION  
"<Definition> Indicates the algorithm used to encode each characterNumber 
within a MULTI string.
<Format>
  other (1): a read-only value indicating an encoding scheme other than those 
listed below, refer to the device manual. Implementations that support other 
encodings shall provide a parallel manufacturer-specific object that provides 
a read-only enumeration for 'standard' along with any custom enumerations.  A 
set to the parallel manufacturer-specific object shall cause this object to 
transition to 'other' and a set of this object shall cause the parallel 
manufacturer-specific object to transition to 'standard'.
  eightBit (2): each characterNumber of the current font is encoded as an 8-
bit unsigned integer. This encoding scheme only supports native 
representation of character numbers 1 through 255. Higher character numbers 
can only be displayed using the hexadecimal character tag ([hcx]).
  utf8Style (4): each characterNumber of the current font is encoded as if it     
were a Unicode codepoint encoded according to the rules of UTF-8     
(however, there is no verification that the character bitmap actually     
resembles the character defined by that code point). However, as the font     
table is limited to 65,535 characters, only codes up to 3-octets in     
length are supported. These rules can be summarized as follows: 
    - Values less than 128 are encoded in the 7 available bits in 
      the mask '0xxx xxxx';
    - Values greater than 127 but less than 2048 are encoded in the 
      eleven available bits of the mask '110x xxxx 10xx xxxx'; and 
    - Remaining values are ecoded in the 16 available bits in the 
      mask '1110 xxxx 10xx xxxx 10xx xxxx' 
    - This format does not support 4-octet UTF-8 codes because each
      font is limited to 65535 characters.

This object may be sub-ranged by an implementation (e.g., an implementation 
might only support eightBit encoding); see Section 3.5.2.2.2.8 for more 
information.
<Informative>  
The eightBit and utf8Style formats are conceptually similar to well-known 
encoding formats (i.e., ASCII and UTF-8) but allow the fonts to be customized 
by the user through the use of the font table so that different signs can 
produce similar glyphs (i.e., to define the pixel-level representation of 
each character). However, it is important to note that the resulting 
multistring does not necessarily reflect a genuine ASCII or UTF-8 string, as 
there is no guarantee that the character bitmaps called by the multistring 
will correspond to the conceptual characters identified by their ASCII and 
Unicode codepoints.
Example 1: A MULTI string with an encoded value of 0x41 E2 9C 8B, 
would be decoded as follows according to the different encoding 
schemes: 
  eightBit: four 8-bit characters with codes 65, 226, 156, and 139
  utf8Style: an 8-bit character followed by a 24-bit character. The 
    first character is code 65 and the second character is:
      E    2    9    C    8    B     in hex
    1110 0010 1001 1100 1000 1011    in binary
         0010   01 1100   00 1011    removing mask
              0010 0111 0000 1011    compressing
                2    7    0    B     in hex
                             9995    in decimal

Example 2: The MULTI string  '[fo2]', which is a tag to indicate font 2, is 
encoded as '0x5b 66 6f 32 5d' in both the eightBit and utf8Style encoding 
(i.e., all characters have codes less than 128)
 
Example 3: While it is often convenient to align characterNumbers and 
characterBitmaps with ASCII or UTF-8 character codes, this is not a 
requirement. For example, Character 65 in one font might represent the letter 
'A', but in another font it can represent the grinning face emoticon. As 
such, any character bitmap (including those represented by Unicode codepoints 
greater than 65535) can be defined and supported for display.
 
Example 4: Per the rules of Multistring syntax, the left and right bracket 
characters ('[' and ']') are reserved for tags and to display either, the 
character must appear two times in a row within the MULTI string. Thus, to 
display '[', the MULTI string would be '0x5b5b' for both 'eightBit' and 
'utf8Style' encoding.
<Parameter Type> Configuration
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.4.10"
DEFVAL  {eightBit} 
::= { multiCfg 10 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

<Definition> Indicates the algorithm used to encode each characterNumber within a MULTI string. <Format> other (1): a read-only value indicating an encoding scheme other than those listed below, refer to the device manual. Implementations that support other encodings shall provide a parallel manufacturer-specific object that provides a read-only enumeration for 'standard' along with any custom enumerations. A set to the parallel manufacturer-specific object shall cause this object to transition to 'other' and a set of this object shall cause the parallel manufacturer-specific object to transition to 'standard'. eightBit (2): each characterNumber of the current font is encoded as an 8- bit unsigned integer. This encoding scheme only supports native representation of character numbers 1 through 255. Higher character numbers can only be displayed using the hexadecimal character tag ([hcx]). utf8Style (4): each characterNumber of the current font is encoded as if it were a Unicode codepoint encoded according to the rules of UTF-8 (however, there is no verification that the character bitmap actually resembles the character defined by that code point). However, as the font table is limited to 65,535 characters, only codes up to 3-octets in length are supported. These rules can be summarized as follows: - Values less than 128 are encoded in the 7 available bits in the mask '0xxx xxxx'; - Values greater than 127 but less than 2048 are encoded in the eleven available bits of the mask '110x xxxx 10xx xxxx'; and - Remaining values are ecoded in the 16 available bits in the mask '1110 xxxx 10xx xxxx 10xx xxxx' - This format does not support 4-octet UTF-8 codes because each font is limited to 65535 characters. This object may be sub-ranged by an implementation (e.g., an implementation might only support eightBit encoding); see Section 3.5.2.2.2.8 for more information. <Informative> The eightBit and utf8Style formats are conceptually similar to well-known encoding formats (i.e., ASCII and UTF-8) but allow the fonts to be customized by the user through the use of the font table so that different signs can produce similar glyphs (i.e., to define the pixel-level representation of each character). However, it is important to note that the resulting multistring does not necessarily reflect a genuine ASCII or UTF-8 string, as there is no guarantee that the character bitmaps called by the multistring will correspond to the conceptual characters identified by their ASCII and Unicode codepoints. Example 1: A MULTI string with an encoded value of 0x41 E2 9C 8B, would be decoded as follows according to the different encoding schemes: eightBit: four 8-bit characters with codes 65, 226, 156, and 139 utf8Style: an 8-bit character followed by a 24-bit character. The first character is code 65 and the second character is: E 2 9 C 8 B in hex 1110 0010 1001 1100 1000 1011 in binary 0010 01 1100 00 1011 removing mask 0010 0111 0000 1011 compressing 2 7 0 B in hex 9995 in decimal Example 2: The MULTI string '[fo2]', which is a tag to indicate font 2, is encoded as '0x5b 66 6f 32 5d' in both the eightBit and utf8Style encoding (i.e., all characters have codes less than 128) Example 3: While it is often convenient to align characterNumbers and characterBitmaps with ASCII or UTF-8 character codes, this is not a requirement. For example, Character 65 in one font might represent the letter 'A', but in another font it can represent the grinning face emoticon. As such, any character bitmap (including those represented by Unicode codepoints greater than 65535) can be defined and supported for display. Example 4: Per the rules of Multistring syntax, the left and right bracket characters ('[' and ']') are reserved for tags and to display either, the character must appear two times in a row within the MULTI string. Thus, to display '[', the MULTI string would be '0x5b5b' for both 'eightBit' and 'utf8Style' encoding. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.4.10

Sources for this description

ITE public NTCIP working repository MIBs

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1ITE public NTCIP working repository MIBs1 record · 1 source

Description 1

defaultCharacterSet · unconfirmedITE public NTCIP working repository MIBs1 source

Status in source: unconfirmed.

Names: defaultCharacterSet

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "defaultCharacterSet",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "other",
    "(",
    "1",
    ")",
    ",",
    "eightBit",
    "(",
    "2",
    ")",
    ",",
    "utf8Style",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Indicates the algorithm used to encode each characterNumber within a MULTI string. <Format> other (1): a read-only value indicating an encoding scheme other than those listed below, refer to the device manual. Implementations that support other encodings shall provide a parallel manufacturer-specific object that provides a read-only enumeration for 'standard' along with any custom enumerations. A set to the parallel manufacturer-specific object shall cause this object to transition to 'other' and a set of this object shall cause the parallel manufacturer-specific object to transition to 'standard'. eightBit (2): each characterNumber of the current font is encoded as an 8- bit unsigned integer. This encoding scheme only supports native representation of character numbers 1 through 255. Higher character numbers can only be displayed using the hexadecimal character tag ([hcx]). utf8Style (4): each characterNumber of the current font is encoded as if it were a Unicode codepoint encoded according to the rules of UTF-8 (however, there is no verification that the character bitmap actually resembles the character defined by that code point). However, as the font table is limited to 65,535 characters, only codes up to 3-octets in length are supported. These rules can be summarized as follows: - Values less than 128 are encoded in the 7 available bits in the mask '0xxx xxxx'; - Values greater than 127 but less than 2048 are encoded in the eleven available bits of the mask '110x xxxx 10xx xxxx'; and - Remaining values are ecoded in the 16 available bits in the mask '1110 xxxx 10xx xxxx 10xx xxxx' - This format does not support 4-octet UTF-8 codes because each font is limited to 65535 characters. This object may be sub-ranged by an implementation (e.g., an implementation might only support eightBit encoding); see Section 3.5.2.2.2.8 for more information. <Informative> The eightBit and utf8Style formats are conceptually similar to well-known encoding formats (i.e., ASCII and UTF-8) but allow the fonts to be customized by the user through the use of the font table so that different signs can produce similar glyphs (i.e., to define the pixel-level representation of each character). However, it is important to note that the resulting multistring does not necessarily reflect a genuine ASCII or UTF-8 string, as there is no guarantee that the character bitmaps called by the multistring will correspond to the conceptual characters identified by their ASCII and Unicode codepoints. Example 1: A MULTI string with an encoded value of 0x41 E2 9C 8B, would be decoded as follows according to the different encoding schemes: eightBit: four 8-bit characters with codes 65, 226, 156, and 139 utf8Style: an 8-bit character followed by a 24-bit character. The first character is code 65 and the second character is: E 2 9 C 8 B in hex 1110 0010 1001 1100 1000 1011 in binary 0010 01 1100 00 1011 removing mask 0010 0111 0000 1011 compressing 2 7 0 B in hex 9995 in decimal Example 2: The MULTI string '[fo2]', which is a tag to indicate font 2, is encoded as '0x5b 66 6f 32 5d' in both the eightBit and utf8Style encoding (i.e., all characters have codes less than 128) Example 3: While it is often convenient to align characterNumbers and characterBitmaps with ASCII or UTF-8 character codes, this is not a requirement. For example, Character 65 in one font might represent the letter 'A', but in another font it can represent the grinning face emoticon. As such, any character bitmap (including those represented by Unicode codepoints greater than 65535) can be defined and supported for display. Example 4: Per the rules of Multistring syntax, the left and right bracket characters ('[' and ']') are reserved for tags and to display either, the character must appear two times in a row within the MULTI string. Thus, to display '[', the MULTI string would be '0x5b5b' for both 'eightBit' and 'utf8Style' encoding. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.4.10\"",
    "DEFVAL",
    "{",
    "eightBit",
    "}",
    "::=",
    "{",
    "multiCfg",
    "10",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "other",
            1
          ],
          [
            "eightBit",
            2
          ],
          [
            "utf8Style",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Indicates the algorithm used to encode each characterNumber within a MULTI string. <Format> other (1): a read-only value indicating an encoding scheme other than those listed below, refer to the device manual. Implementations that support other encodings shall provide a parallel manufacturer-specific object that provides a read-only enumeration for 'standard' along with any custom enumerations. A set to the parallel manufacturer-specific object shall cause this object to transition to 'other' and a set of this object shall cause the parallel manufacturer-specific object to transition to 'standard'. eightBit (2): each characterNumber of the current font is encoded as an 8- bit unsigned integer. This encoding scheme only supports native representation of character numbers 1 through 255. Higher character numbers can only be displayed using the hexadecimal character tag ([hcx]). utf8Style (4): each characterNumber of the current font is encoded as if it were a Unicode codepoint encoded according to the rules of UTF-8 (however, there is no verification that the character bitmap actually resembles the character defined by that code point). However, as the font table is limited to 65,535 characters, only codes up to 3-octets in length are supported. These rules can be summarized as follows: - Values less than 128 are encoded in the 7 available bits in the mask '0xxx xxxx'; - Values greater than 127 but less than 2048 are encoded in the eleven available bits of the mask '110x xxxx 10xx xxxx'; and - Remaining values are ecoded in the 16 available bits in the mask '1110 xxxx 10xx xxxx 10xx xxxx' - This format does not support 4-octet UTF-8 codes because each font is limited to 65535 characters. This object may be sub-ranged by an implementation (e.g., an implementation might only support eightBit encoding); see Section 3.5.2.2.2.8 for more information. <Informative> The eightBit and utf8Style formats are conceptually similar to well-known encoding formats (i.e., ASCII and UTF-8) but allow the fonts to be customized by the user through the use of the font table so that different signs can produce similar glyphs (i.e., to define the pixel-level representation of each character). However, it is important to note that the resulting multistring does not necessarily reflect a genuine ASCII or UTF-8 string, as there is no guarantee that the character bitmaps called by the multistring will correspond to the conceptual characters identified by their ASCII and Unicode codepoints. Example 1: A MULTI string with an encoded value of 0x41 E2 9C 8B, would be decoded as follows according to the different encoding schemes: eightBit: four 8-bit characters with codes 65, 226, 156, and 139 utf8Style: an 8-bit character followed by a 24-bit character. The first character is code 65 and the second character is: E 2 9 C 8 B in hex 1110 0010 1001 1100 1000 1011 in binary 0010 01 1100 00 1011 removing mask 0010 0111 0000 1011 compressing 2 7 0 B in hex 9995 in decimal Example 2: The MULTI string '[fo2]', which is a tag to indicate font 2, is encoded as '0x5b 66 6f 32 5d' in both the eightBit and utf8Style encoding (i.e., all characters have codes less than 128) Example 3: While it is often convenient to align characterNumbers and characterBitmaps with ASCII or UTF-8 character codes, this is not a requirement. For example, Character 65 in one font might represent the letter 'A', but in another font it can represent the grinning face emoticon. As such, any character bitmap (including those represented by Unicode codepoints greater than 65535) can be defined and supported for display. Example 4: Per the rules of Multistring syntax, the left and right bracket characters ('[' and ']') are reserved for tags and to display either, the character must appear two times in a row within the MULTI string. Thus, to display '[', the MULTI string would be '0x5b5b' for both 'eightBit' and 'utf8Style' encoding. <Parameter Type> Configuration <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.4.10"
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "eightBit"
    ]
  ]
}
  • ITE public NTCIP working repository MIBs · Publisher's source file: NTCIP-1203 — NTCIP1203-Dms.mib

    Module: NTCIP1203-Dms

    See published definition above

    Module imports
    {'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'StorageType', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'ISO26048-1-Srsa': ['fdSrsaTypeCode', 'fdSrsaPortIndex'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'ISO26048-1-Global-TC': ['ITSDirection', 'ITSInteger8', 'ITSLatitude84', 'ITSLongitude84', 'ITSBitmap'], 'TRANSPORT-ADDRESS-MIB': ['TransportAddressType', 'TransportAddress'], 'NTCIP8004-Transportation': ['NtcipOwnerString', 'NtcipIntegerBitmap8', 'NtcipIntegerBitmap16', 'NtcipTwoColors', 'devices']}

    Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.

    Source data warning: Published module-root disagreement: dms has an SMI assignment resolving to 1.3.6.1.4.1.1206.4.2.6, while its DESCRIPTION explicitly prints 1.3.6.1.4.1.1206.4.2.3. All dependent assignments from this module require verification. No root number has been silently corrected.

    Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.6.4.10, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.4.10. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.

    · Download NTCIP-1203 — NTCIP1203-Dms.mib

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (26)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.6.4.1 maxEventLogConfigs, defaultBackgroundColor00
1.3.6.1.4.1.1206.4.2.6.4.2 eventLogConfigTable, defaultForegroundColor110
1.3.6.1.4.1.1206.4.2.6.4.3 maxEventLogSize, defaultFlashOn00
1.3.6.1.4.1.1206.4.2.6.4.4 eventLogTable, defaultFlashOff17
1.3.6.1.4.1.1206.4.2.6.4.5 maxEventClasses, defaultFont00
1.3.6.1.4.1.1206.4.2.6.4.6 eventClassTable, defaultJustificationLine17
1.3.6.1.4.1.1206.4.2.6.4.7 numEvents, defaultJustificationPage00
1.3.6.1.4.1.1206.4.2.6.4.8 eventTimeLatency, defaultPageOnTime00
1.3.6.1.4.1.1206.4.2.6.4.9 defaultPageOffTime00
1.3.6.1.4.1.1206.4.2.6.4.11 dmsColorScheme00
1.3.6.1.4.1.1206.4.2.6.4.12 defaultBackgroundRGB00
1.3.6.1.4.1.1206.4.2.6.4.13 defaultForegroundRGB00
1.3.6.1.4.1.1206.4.2.6.4.14 dmsSupportedMultiTags00
1.3.6.1.4.1.1206.4.2.6.4.15 dmsMaxNumberPages00
1.3.6.1.4.1.1206.4.2.6.4.16 dmsMaxMultiStringLength00
1.3.6.1.4.1.1206.4.2.6.4.17 defaultFlashOnActivate00
1.3.6.1.4.1.1206.4.2.6.4.18 defaultFlashOffActivate00
1.3.6.1.4.1.1206.4.2.6.4.19 defaultFontActivate00
1.3.6.1.4.1.1206.4.2.6.4.20 defaultJustificationLineActivate00
1.3.6.1.4.1.1206.4.2.6.4.21 defaultJustificationPageActivate00
1.3.6.1.4.1.1206.4.2.6.4.22 defaultPageOnTimeActivate00
1.3.6.1.4.1.1206.4.2.6.4.23 defaultPageOffTimeActivate00
1.3.6.1.4.1.1206.4.2.6.4.24 defaultBackgroundRGBActivate00
1.3.6.1.4.1.1206.4.2.6.4.25 defaultForegroundRGBActivate00
1.3.6.1.4.1.1206.4.2.6.4.26 dmsSupportedMultiTagsV400
1.3.6.1.4.1.1206.4.2.6.4.127 reportConformance24