US: NTCIP Warning Device - Wireless SNMPv3/TLS
Description:
This solution is used within the U.S.. It combines standards associated with US: NTCIP Warning Device with those for I-M: Wireless SNMPv3/TLS. The US: NTCIP Warning Device standards include a composite of upper-layer standards that support monitoring for unsafe traffic activities and displaying warning to drivers. The I-M: Wireless SNMPv3/TLS standards include lower-layer standards that support secure infrastructure-to-mobile communications using simple network management protocol (SNMPv3).
Comm Profile: I-M: Wireless SNMPv3/TLS
Standards in Profile:
Level | Doc # | Standard | Description |
Access
|
|
Wireless Internet Alternatives (NA)
|
A set of alternative standards that supports any technology that allows a mobile device (e.g., a vehicle) to connect to the Internet (or an intranet) while stationary or moving within a limited area. For example, this would include both Wi-Fi and cellular technologies among others. NOTE: Use of the WAVE Subnet should be coupled with use of IEEE 1609.3 at the TransNet Layer.
|
Facilities
|
ISO 15784-2
|
Bundle: ISO 15784-2
|
ISO 15784-2 specifies the standards that provide a mechanism to exchange data and messages in the following cases: a) between a traffic management center(s) and roadside modules for traffic management; and b) between roadside modules used for traffic management.
|
Mgmt
|
|
Bundle: SNMPv3 MIB
|
A bundle of standards (RFCs) that groups the common management information bases (MIBs) used to manage IP networks at the transport layer and below using SNMPv3.
|
Security
|
IETF RFC 6353
|
IETF RFC 6353 TLS for SNMP
|
This standard (RFC) defines how to use the TLS authentication service to provide authentication within the access control mechanism of SNMP.
|
TransNet
|
|
Internet Transport Alternatives
|
A set of alternative standards that identifies the two major options for the transport layer for mainstream IP-based deployments.
|
TransNet
|
|
IP Alternatives
|
A set of alternative standards that allows for the selection of IPv4 or IPv6.
|
Data Profile: US: NTCIP Warning Device
Standards in Profile:
Level | Doc # | Standard | Description |
Facilities
|
NTCIP 1205
|
NTCIP CCTV Objects
|
This standard defines SNMP objects (data elements) for control and monitoring of closed-circuit television (CCTV) camera controllers.
|
Facilities
|
NTCIP 1203
|
NTCIP Message Sign Objects
|
This standard defines SNMP objects (data elements) for monitoring and controlling dynamic message signs (such as variable message signs).
|
Facilities
|
NTCIP 1209
|
NTCIP Transportation Sensor Objects
|
This standard defines SNMP objects (data elements) to monitor and control transportation system sensors that measure real-time vehicular traffic information.
|
ITS Application Entity
|
NTCIP 1205
|
NTCIP CCTV Objects
|
This standard defines SNMP objects (data elements) for control and monitoring of closed-circuit television (CCTV) camera controllers.
|
ITS Application Entity
|
NTCIP 1203
|
NTCIP Message Sign Objects
|
This standard defines SNMP objects (data elements) for monitoring and controlling dynamic message signs (such as variable message signs).
|
ITS Application Entity
|
NTCIP 1209
|
NTCIP Transportation Sensor Objects
|
This standard defines SNMP objects (data elements) to monitor and control transportation system sensors that measure real-time vehicular traffic information.
|
Mgmt
|
NTCIP 1201
|
NTCIP Global Objects
|
This standard defines SNMP objects (data elements) used by a wide range of field devices like time and versioning information.
|
Readiness Description:
One significant or possibly a couple minor issues. For existing deployments, the chosen solution likely has identified security or management issues not addressed by the communications solution. Deployers should consider additional security measures, such as communications link and physical security as part of these solutions. They should also review the management issues to see if they are relevant to their deployment and would require mitigation. For new deployments, the deployment efforts should consider a path to addressing these issues as a part of their design activities. The solution does not by itself provide a fully secure implementation without additional work.
Last Updated 4/29/2024