OID reference

rsuReceivedMsgAuthMsgInterval

1.3.6.1.4.1.1206.4.2.18.5.2.1.12

Description

<Definition> Interval with which the RSU authenticates messages received from a specific device over the V2X Interface and to be forwarded to the Server (as controlled by rsuDsrcFwdMsgInterval). If enabled, the RSU authenticates the first valid (e.g., as defined by rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart, rsuDsrcFwdDe…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.18.5.2.1 (rsuReceivedMsgEntry)
Node code
12
Node name
rsuReceivedMsgAuthMsgInterval
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.18.5.2.1.12
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.18.5.2.1.12
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 18 5 2 1 12}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) rsu(18) rsuReceivedMsg(5) rsuReceivedMsgTable(2) rsuReceivedMsgEntry(1) rsuReceivedMsgAuthMsgInterval(12)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/18/5/2/1/12
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/18/5/2/1/12
  • /ISO/3/6/1/4/1/1206/4/2/18/5/2/1/12
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/rsu/rsuReceivedMsg/rsuReceivedMsgTable/rsuReceivedMsgEntry/rsuReceivedMsgAuthMsgInterval
  • Additional combinations skipped.

SNMP properties

Value type
Integer32
Maximum access defined by MIB
read-create
Status in MIB
current
Allowed ranges
0–10

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. The index encoding is not inferred here.

Published row index: rsuReceivedMsgIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.18.5.2.1.12

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

rsuReceivedMsgAuthMsgInterval · current

rsuReceivedMsgAuthMsgInterval OBJECT-TYPE
    SYNTAX       Integer32 (0..10)
    MAX-ACCESS   read-create
    STATUS       current
    DESCRIPTION "<Definition> Interval with which the RSU authenticates
         messages received from a specific device over the V2X Interface and
         to be forwarded to the Server (as controlled by
         rsuDsrcFwdMsgInterval). If enabled, the RSU authenticates the first
         valid (e.g., as defined by rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart,
         rsuDsrcFwdDeliveryStop for this row) message received from a
         specific device. For a value of 4, the RSU then authenticates every



                                                                                          

                 
        

            4th message (after the first message) for that specific device that
            is marked for forwarding (as determined by rsuDsrcFwdMsgInterval). A
            value of 0 disables authentication of message to be forward for this
            particular entry.

         For example, an RSU receives 12 messages that satisfies the criteria
         for this row (rsuDsrcFwdPsid, rsuDsrcFwdRssi,
         rsuDsrcFwdDeliveryStart, rsuDsrcFwdDeliveryStop). Messages 1, 2, 5,
         6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9 and 11 are
         from device B. Assuming rsuDsrcFwdMsgInterval has a value of 2, only
         messages 1, 3, 5, 7, 9, and 11 are 'marked' for forwarding. Of these
         messages, only messages 1 (the first message from device A), 3 (the
         first message from device B), 7 (the 2nd message from device A after
         the first message), and 11 (the 2nd message from device B after the
         first message) are authenticated.
    <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12"
::= { rsuReceivedMsgEntry 12 }

rsuReceivedMsgAuthMsgInterval · current

rsuReceivedMsgAuthMsgInterval OBJECT-TYPE
    SYNTAX       Integer32 (0..10)
    MAX-ACCESS   read-create
    STATUS       current
    DESCRIPTION "<Definition> Interval with which the RSU authenticates
         messages received from a specific device over the V2X Interface and
         to be forwarded to the Server (as controlled by
         rsuReceivedMsgInterval). If enabled, the RSU authenticates the first
         valid (e.g., as defined by rsuReceivedMsgRssi,
         rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop for this
         row) message received from a specific device. For a value of 4, the
         RSU then authenticates every 4th message (after the first message)
         for that specific device that is marked for forwarding (as
         determined by rsuReceivedMsgInterval). A value of 0 disables
         authentication of message to be forward for this particular entry.

         For example, an RSU receives 12 messages that satisfies the criteria
         for this row (rsuReceivedMsgPsid, rsuReceivedMsgRssi,
         rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop). Messages
         1, 2, 5, 6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9
         and 11 are from device B. Assuming rsuReceivedMsgInterval has a
         value of 2, only messages 1, 3, 5, 7, 9, and 11 are 'marked' for
         forwarding. Of these messages, only messages 1 (the first message
         from device A), 3 (the first message from device B), 7 (the 2nd
         message from device A after the first message), and 11 (the 2nd
         message from device B after the first message) are authenticated.
    <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12"
::= { rsuReceivedMsgEntry 12 }

Meaning

Descriptions

2 unique

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

Description 1

<Definition> Interval with which the RSU authenticates messages received from a specific device over the V2X Interface and to be forwarded to the Server (as controlled by rsuDsrcFwdMsgInterval). If enabled, the RSU authenticates the first valid (e.g., as defined by rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart, rsuDsrcFwdDeliveryStop for this row) message received from a specific device. For a value of 4, the RSU then authenticates every 4th message (after the first message) for that specific device that is marked for forwarding (as determined by rsuDsrcFwdMsgInterval). A value of 0 disables authentication of message to be forward for this particular entry. For example, an RSU receives 12 messages that satisfies the criteria for this row (rsuDsrcFwdPsid, rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart, rsuDsrcFwdDeliveryStop). Messages 1, 2, 5, 6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9 and 11 are from device B. Assuming rsuDsrcFwdMsgInterval has a value of 2, only messages 1, 3, 5, 7, 9, and 11 are 'marked' for forwarding. Of these messages, only messages 1 (the first message from device A), 3 (the first message from device B), 7 (the 2nd message from device A after the first message), and 11 (the 2nd message from device B after the first message) are authenticated. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> Interval with which the RSU authenticates messages received from a specific device over the V2X Interface and to be forwarded to the Server (as controlled by rsuReceivedMsgInterval). If enabled, the RSU authenticates the first valid (e.g., as defined by rsuReceivedMsgRssi, rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop for this row) message received from a specific device. For a value of 4, the RSU then authenticates every 4th message (after the first message) for that specific device that is marked for forwarding (as determined by rsuReceivedMsgInterval). A value of 0 disables authentication of message to be forward for this particular entry. For example, an RSU receives 12 messages that satisfies the criteria for this row (rsuReceivedMsgPsid, rsuReceivedMsgRssi, rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop). Messages 1, 2, 5, 6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9 and 11 are from device B. Assuming rsuReceivedMsgInterval has a value of 2, only messages 1, 3, 5, 7, 9, and 11 are 'marked' for forwarding. Of these messages, only messages 1 (the first message from device A), 3 (the first message from device B), 7 (the 2nd message from device A after the first message), and 11 (the 2nd message from device B after the first message) are authenticated. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 1

rsuReceivedMsgAuthMsgInterval · currentNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: current.

Names: rsuReceivedMsgAuthMsgInterval

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rsuReceivedMsgAuthMsgInterval",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "10",
    ")",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Interval with which the RSU authenticates messages received from a specific device over the V2X Interface and to be forwarded to the Server (as controlled by rsuDsrcFwdMsgInterval). If enabled, the RSU authenticates the first valid (e.g., as defined by rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart, rsuDsrcFwdDeliveryStop for this row) message received from a specific device. For a value of 4, the RSU then authenticates every 4th message (after the first message) for that specific device that is marked for forwarding (as determined by rsuDsrcFwdMsgInterval). A value of 0 disables authentication of message to be forward for this particular entry. For example, an RSU receives 12 messages that satisfies the criteria for this row (rsuDsrcFwdPsid, rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart, rsuDsrcFwdDeliveryStop). Messages 1, 2, 5, 6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9 and 11 are from device B. Assuming rsuDsrcFwdMsgInterval has a value of 2, only messages 1, 3, 5, 7, 9, and 11 are 'marked' for forwarding. Of these messages, only messages 1 (the first message from device A), 3 (the first message from device B), 7 (the 2nd message from device A after the first message), and 11 (the 2nd message from device B after the first message) are authenticated. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12\"",
    "::=",
    "{",
    "rsuReceivedMsgEntry",
    "12",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            10
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Interval with which the RSU authenticates messages received from a specific device over the V2X Interface and to be forwarded to the Server (as controlled by rsuDsrcFwdMsgInterval). If enabled, the RSU authenticates the first valid (e.g., as defined by rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart, rsuDsrcFwdDeliveryStop for this row) message received from a specific device. For a value of 4, the RSU then authenticates every 4th message (after the first message) for that specific device that is marked for forwarding (as determined by rsuDsrcFwdMsgInterval). A value of 0 disables authentication of message to be forward for this particular entry. For example, an RSU receives 12 messages that satisfies the criteria for this row (rsuDsrcFwdPsid, rsuDsrcFwdRssi, rsuDsrcFwdDeliveryStart, rsuDsrcFwdDeliveryStop). Messages 1, 2, 5, 6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9 and 11 are from device B. Assuming rsuDsrcFwdMsgInterval has a value of 2, only messages 1, 3, 5, 7, 9, and 11 are 'marked' for forwarding. Of these messages, only messages 1 (the first message from device A), 3 (the first message from device B), 7 (the 2nd message from device A after the first message), and 11 (the 2nd message from device B after the first message) are authenticated. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12"
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2NTCIP published standard MIB annexes (reviewed modules)1 record · 1 source

Description 2

rsuReceivedMsgAuthMsgInterval · currentNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: current.

Names: rsuReceivedMsgAuthMsgInterval

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rsuReceivedMsgAuthMsgInterval",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "10",
    ")",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"<Definition> Interval with which the RSU authenticates messages received from a specific device over the V2X Interface and to be forwarded to the Server (as controlled by rsuReceivedMsgInterval). If enabled, the RSU authenticates the first valid (e.g., as defined by rsuReceivedMsgRssi, rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop for this row) message received from a specific device. For a value of 4, the RSU then authenticates every 4th message (after the first message) for that specific device that is marked for forwarding (as determined by rsuReceivedMsgInterval). A value of 0 disables authentication of message to be forward for this particular entry. For example, an RSU receives 12 messages that satisfies the criteria for this row (rsuReceivedMsgPsid, rsuReceivedMsgRssi, rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop). Messages 1, 2, 5, 6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9 and 11 are from device B. Assuming rsuReceivedMsgInterval has a value of 2, only messages 1, 3, 5, 7, 9, and 11 are 'marked' for forwarding. Of these messages, only messages 1 (the first message from device A), 3 (the first message from device B), 7 (the 2nd message from device A after the first message), and 11 (the 2nd message from device B after the first message) are authenticated. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12\"",
    "::=",
    "{",
    "rsuReceivedMsgEntry",
    "12",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            10
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "<Definition> Interval with which the RSU authenticates messages received from a specific device over the V2X Interface and to be forwarded to the Server (as controlled by rsuReceivedMsgInterval). If enabled, the RSU authenticates the first valid (e.g., as defined by rsuReceivedMsgRssi, rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop for this row) message received from a specific device. For a value of 4, the RSU then authenticates every 4th message (after the first message) for that specific device that is marked for forwarding (as determined by rsuReceivedMsgInterval). A value of 0 disables authentication of message to be forward for this particular entry. For example, an RSU receives 12 messages that satisfies the criteria for this row (rsuReceivedMsgPsid, rsuReceivedMsgRssi, rsuReceivedMsgDeliveryStart, rsuReceivedMsgDeliveryStop). Messages 1, 2, 5, 6, 7, 10 and 12 are from device A and messages 3, 4, 8, 9 and 11 are from device B. Assuming rsuReceivedMsgInterval has a value of 2, only messages 1, 3, 5, 7, 9, and 11 are 'marked' for forwarding. Of these messages, only messages 1 (the first message from device A), 3 (the first message from device B), 7 (the 2nd message from device A after the first message), and 11 (the 2nd message from device B after the first message) are authenticated. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.5.2.1.12"
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1218 v01A, Object Definitions for Roadside Units (RSUs) — original PDF · Official record

    Module: NTCIP1218-v01

    See published definition above

    Module imports
    {'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DateAndTime', 'RowStatus', 'DisplayString', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'NOTIFICATION-TYPE', 'enterprises'], 'URI-TC-MIB': ['Uri255', 'Uri1024'], 'NTCIP8004v02': ['devices', 'OerString'], 'SYSLOG-TC-MIB': ['SyslogSeverity'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}

    Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.

    Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.

    · Download NTCIP-1218-v01A-2024-AsPublished.pdf — NTCIP1218-v01 (MIB transcription)

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (11)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.18.5.2.1.1 rsuReceivedMsgIndex00
1.3.6.1.4.1.1206.4.2.18.5.2.1.2 rsuReceivedMsgPsid00
1.3.6.1.4.1.1206.4.2.18.5.2.1.3 rsuReceivedMsgDestIpAddr00
1.3.6.1.4.1.1206.4.2.18.5.2.1.4 rsuReceivedMsgDestPort00
1.3.6.1.4.1.1206.4.2.18.5.2.1.5 rsuReceivedMsgProtocol00
1.3.6.1.4.1.1206.4.2.18.5.2.1.6 rsuReceivedMsgRssi00
1.3.6.1.4.1.1206.4.2.18.5.2.1.7 rsuReceivedMsgInterval00
1.3.6.1.4.1.1206.4.2.18.5.2.1.8 rsuReceivedMsgDeliveryStart00
1.3.6.1.4.1.1206.4.2.18.5.2.1.9 rsuReceivedMsgDeliveryStop00
1.3.6.1.4.1.1206.4.2.18.5.2.1.10 rsuReceivedMsgStatus00
1.3.6.1.4.1.1206.4.2.18.5.2.1.11 rsuReceivedMsgSecure00