US: NTCIP Roadside Unit - SNMPv3/TLS

Description:

This solution is used within Canada and the U.S.. It combines standards associated with US: NTCIP Roadside Unit with those for I-F: SNMPv3/TLS. The US: NTCIP Roadside Unit standards include upper-layer standards required to implement center-to-field roadside unit communications. The I-F: SNMPv3/TLS standards include lower-layer standards that support secure center-to-field and field-to-field communications using simple network management protocol (SNMPv3); implementations are strongly encouraged to use the TLS for SNMP security option for this solution to ensure adequate security.

Comm Profile: I-F: SNMPv3/TLS

Level	Doc #	Standard	Description
Access		Field SubNet Alternatives	A set of alternative standards that defines various SubNet Layer alternatives for use in center-to-field and field-to-field connections.
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.
Security	IETF RFC 9456	IETF RFC 9456 TLS Updates for SNMP	Null
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 Roadside Unit

Level	Doc #	Standard	Description
Facilities	NTCIP 1218	NTCIP 1218 RSUs	This standard defines SNMP objects (data elements) for monitoring and efficiently controlling roadside units.
ITS Application Entity	CTI 4001	CTI 4001 RSU	This document establishes a non-proprietary, communications-agnostic, industry consensus Roadside Unit (RSU) Standard. An RSU is a transportation infrastructure communications device that is a part of a Cooperative Intelligent Transportation Systems (C-ITS) transportation environment. The goal of such an environment is to reduce the number of fatalities and injuries on roadways, improve mobility, and reduce environmental impacts of transportation systems. Commonly known as the Connected Vehicle (CV) environment in the United States (US), it includes both connected human-driven vehicles and connected automated vehicles (CAVs). The terms Vehicle-to-Infrastructure (V2I) and Vehicle-to-Vehicle (V2V) are used to reflect the exchanges of messages within the CV environment. The vision for this technology has expanded to include all types of travelers including pedestrians, cyclists, multimodal travelers, and other vulnerable road users (VRUs), and is referred to as Vehicle-to-Everything (V2X) technology and V2X communications.
ITS Application Entity	CTI 4501	CTI 4501 CI Implementation Guide	This Connected Intersection (CI) Implementation Guide defines the key capabilities and interfaces a connected signalized intersection must support to ensure interoperability with production vehicles for state and local IOOs. A connected intersection is defined as an infrastructure system that broadcasts SPaT, MAP, and position correction data to vehicles.
ITS Application Entity	NTCIP 1218	NTCIP 1218 RSUs	This standard defines SNMP objects (data elements) for monitoring and efficiently controlling roadside units.
Mgmt	NTCIP 1201	NTCIP 1201 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.