Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rsuMsgRepeatOptions",
"OBJECT-TYPE",
"SYNTAX",
"BITS",
"{",
"bypass",
"(",
"0",
")",
",",
"secure",
"(",
"1",
")",
",",
"shortTerm",
"(",
"2",
")",
",",
"longTerm",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> A bit-mapped value as defined below for configuring the message. Bit 0 0=Bypass1609.2, 1=Process1609.2 Bit 1 0=Secure, 1=Unsecure Bit 2 0=ContXmit, 1=NoXmitShortTermXceeded Bit 3 0=ContXmit, 1=NoXmitLongTermXceeded Bit 0 - Indicates if the RSU is to bypass 1609.2 processing of the message to the V2X interface. This allows the RSU to send the message that has been signed and/or encrypted by the TMC. Note the RSU would still wrap the message payload in a WSMP header. Bit 1 - Indicates if the message should be secured (signed or encrypted) prior to transmission to the V2X Interface. How the message is to be secured is determined by its security profile for that PSID. This bit is ignored if Bit 0=0 (bypass). Bit 2 - Indicates if the message should continue to be transmitted if the short-term communications loss period (rsuShortCommLossTime) is exceeded. 0 indicates the message should continue to be transmitted. Default value is 0. Bit 3 - Indicates if the message should continue to be transmitted if the long-term communications loss period (rsuLongCommLossTime) is exceeded. 0 indicates the message should continue to be transmitted unless Bit 2 is a value of 1, which indicates the message has stopped transmitting after short-term communications loss period (rsuShortCommLossTime) is exceeded. Default value is 0. See Section 2.5 of RFC 3416 for encoding. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.3.2.1.11\"",
"::=",
"{",
"rsuMsgRepeatStatusEntry",
"11",
"}"
],
"syntax_tree": [
[
"BITS",
[
[
"bypass",
0
],
[
"secure",
1
],
[
"shortTerm",
2
],
[
"longTerm",
3
]
]
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> A bit-mapped value as defined below for configuring the message. Bit 0 0=Bypass1609.2, 1=Process1609.2 Bit 1 0=Secure, 1=Unsecure Bit 2 0=ContXmit, 1=NoXmitShortTermXceeded Bit 3 0=ContXmit, 1=NoXmitLongTermXceeded Bit 0 - Indicates if the RSU is to bypass 1609.2 processing of the message to the V2X interface. This allows the RSU to send the message that has been signed and/or encrypted by the TMC. Note the RSU would still wrap the message payload in a WSMP header. Bit 1 - Indicates if the message should be secured (signed or encrypted) prior to transmission to the V2X Interface. How the message is to be secured is determined by its security profile for that PSID. This bit is ignored if Bit 0=0 (bypass). Bit 2 - Indicates if the message should continue to be transmitted if the short-term communications loss period (rsuShortCommLossTime) is exceeded. 0 indicates the message should continue to be transmitted. Default value is 0. Bit 3 - Indicates if the message should continue to be transmitted if the long-term communications loss period (rsuLongCommLossTime) is exceeded. 0 indicates the message should continue to be transmitted unless Bit 2 is a value of 1, which indicates the message has stopped transmitting after short-term communications loss period (rsuShortCommLossTime) is exceeded. Default value is 0. See Section 2.5 of RFC 3416 for encoding. <Object Identifier> 1.3.6.1.4.1.1206.4.2.18.3.2.1.11"
],
null,
null,
null,
null
]
}