OID reference

dmsMessageCRC

1.3.6.1.4.1.1206.4.2.6.5.8.1.5

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.6.5.8.1 (dmsMessageEntry)
Node code: 5
Node name: dmsMessageCRC
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.6.5.8.1.5
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.6.5.8.1.5

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 1206 4 2 6 5 8 1 5}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) security(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) dmsMessage(5) dmsMessageTable(8) dmsMessageEntry(1) dmsMessageCRC(5)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/1206/4/2/6/5/8/1/5
/ISO/Identified-Organization/6/1/4/1/1206/4/2/6/5/8/1/5
/ISO/3/6/1/4/1/1206/4/2/6/5/8/1/5

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/security/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/dmsMessage/dmsMessageTable/dmsMessageEntry/dmsMessageCRC
Additional combinations skipped.

SNMP properties

Value type: Integer32
Maximum access defined by MIB: read-only
Status in MIB: current

Allowed ranges: 0–65535

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In NTCIP1203-Dms, the row index consists of these components in order:

dmsMessageMemoryType (INTEGER): one numeric subidentifier for the non-negative value.
dmsMessageNumber (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.1206.4.2.6.5.8.1.5.<dmsMessageMemoryType>.<dmsMessageNumber>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.6.5.8.1.5

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.

Published definition

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

dmsMessageCRC  OBJECT-TYPE 
SYNTAX      Integer32 (0..65535) 
MAX-ACCESS  read-only 
STATUS      current  
DESCRIPTION  
"<Definition> Indicates the CRC-16 (polynomial defined in ISO/IEC 3309) value 
created using the values of the dmsMessageMultiString (MULTI-Message), the 
dmsMessageBeacon, and the dmsMessagePixelService objects in the order listed, 
not including the OER type or length fields. For messages of the 'blank' 
message type, the above algorithm shall be ignored and the dmsMessageCRC 
value shall always be zero (0). For messages of the 'schedule' message type, 
the CRC value of the currently scheduled message shall always be returned 
(regardless whether this message is actually being displayed).
<Informative> Prior to NTCIP 1203 v04, dmsMessageBeacon and 
dmsMessagePixelService could be interpretted as being optional to support. In 
this case, the calculated CRC assumed the value zero for the missing data. 
Starting with v04, all implementations are required to support these objects, 
even if they do not support the related functionality.
<Parameter Type> Status
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.5"
::= { dmsMessageEntry 5 }

Meaning

Descriptions

1 unique

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

<Definition> Indicates the CRC-16 (polynomial defined in ISO/IEC 3309) value created using the values of the dmsMessageMultiString (MULTI-Message), the dmsMessageBeacon, and the dmsMessagePixelService objects in the order listed, not including the OER type or length fields. For messages of the 'blank' message type, the above algorithm shall be ignored and the dmsMessageCRC value shall always be zero (0). For messages of the 'schedule' message type, the CRC value of the currently scheduled message shall always be returned (regardless whether this message is actually being displayed). <Informative> Prior to NTCIP 1203 v04, dmsMessageBeacon and dmsMessagePixelService could be interpretted as being optional to support. In this case, the calculated CRC assumed the value zero for the missing data. Starting with v04, all implementations are required to support these objects, even if they do not support the related functionality. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.5

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

dmsMessageCRC · unconfirmedITE public NTCIP working repository MIBs1 source

Status in source: unconfirmed.

Names: dmsMessageCRC

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dmsMessageCRC",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Indicates the CRC-16 (polynomial defined in ISO/IEC 3309) value created using the values of the dmsMessageMultiString (MULTI-Message), the dmsMessageBeacon, and the dmsMessagePixelService objects in the order listed, not including the OER type or length fields. For messages of the 'blank' message type, the above algorithm shall be ignored and the dmsMessageCRC value shall always be zero (0). For messages of the 'schedule' message type, the CRC value of the currently scheduled message shall always be returned (regardless whether this message is actually being displayed). <Informative> Prior to NTCIP 1203 v04, dmsMessageBeacon and dmsMessagePixelService could be interpretted as being optional to support. In this case, the calculated CRC assumed the value zero for the missing data. Starting with v04, all implementations are required to support these objects, even if they do not support the related functionality. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.5\"",
    "::=",
    "{",
    "dmsMessageEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Indicates the CRC-16 (polynomial defined in ISO/IEC 3309) value created using the values of the dmsMessageMultiString (MULTI-Message), the dmsMessageBeacon, and the dmsMessagePixelService objects in the order listed, not including the OER type or length fields. For messages of the 'blank' message type, the above algorithm shall be ignored and the dmsMessageCRC value shall always be zero (0). For messages of the 'schedule' message type, the CRC value of the currently scheduled message shall always be returned (regardless whether this message is actually being displayed). <Informative> Prior to NTCIP 1203 v04, dmsMessageBeacon and dmsMessagePixelService could be interpretted as being optional to support. In this case, the calculated CRC assumed the value zero for the missing data. Starting with v04, all implementations are required to support these objects, even if they do not support the related functionality. <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.5.8.1.5"
    ],
    null,
    null,
    null,
    null
  ]
}

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.5.8.1.5, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.5.8.1.5. 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 (8)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.6.5.8.1.1	dmsMessageMemoryType	0	0
1.3.6.1.4.1.1206.4.2.6.5.8.1.2	dmsMessageNumber	0	0
1.3.6.1.4.1.1206.4.2.6.5.8.1.3	dmsMessageMultiString	0	0
1.3.6.1.4.1.1206.4.2.6.5.8.1.4	dmsMessageOwner	0	0
1.3.6.1.4.1.1206.4.2.6.5.8.1.6	dmsMessageBeacon	0	0
1.3.6.1.4.1.1206.4.2.6.5.8.1.7	dmsMessagePixelService	0	0
1.3.6.1.4.1.1206.4.2.6.5.8.1.8	dmsMessageRunTimePriority	0	0
1.3.6.1.4.1.1206.4.2.6.5.8.1.9	dmsMessageStatus	0	0