US: Misbehavior reporting - Secure Internet (ITS)

Description:

This solution is used within the U.S.. It combines standards associated with US: Misbehavior reporting with those for I-I: Secure Internet (ITS). The US: Misbehavior reporting standards include upper-layer standards required to support misbehavior reporting services. The I-I: Secure Internet (ITS) standards include lower-layer standards that support secure communications between ITS equipment using X.509 or IEEE 1609.2 security certificates.

Comm Profile: I-I: Secure Internet (ITS)

Standards in Profile:

Level	Standard	Description
Access	Internet Subnet Alternatives	A set of alternative standards that includes any Subnet Layer method of connecting to the Internet.
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	Secure Session Alternatives	A set of alternative standards that identifies standards that are used to establish and maintain secure Internet sessions. If an information exchange does not require encryption, the (D)TLS session can negotiate NULL encryption. NOTE: If TCP is selected in the TransNet Layer, one of the TLS alternatives must be selected from this alternative set; if UDP is selected in the TransNet Layer, one of the DTLS alternatives must be selected from this alternative set.
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: Misbehavior reporting

Standards in Profile:

Level	Doc #	Standard	Description
ITS Application Entity		Application Specific	A placeholder representing that an ITS Information Entity is not required for this support service.

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: 2/7/2024