US: SAE J3067 (J2735 SE) - Guaranteed Secure Wireless Internet (ITS)
Description:
This solution is used within Canada and the U.S.. It combines standards associated with US: SAE J3067 (J2735 SE) with those for I-M: Guaranteed Secure Wireless Internet (ITS). The US: SAE J3067 (J2735 SE) standards include a proposed solution for the upper-layers to implement V2X information flows that do not yet have fully standardized messages, functionality or performance characteristics. The I-M: Guaranteed Secure Wireless Internet (ITS) standards include lower-layer standards that support secure communications with guaranteed delivery between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 or IEEE 1609.2 certificates. A non-mobile (if any) endpoint may connect to the service provider using any Internet connection method.Relevant Regions:
- Canada
- United States
Comm Profile: I-M: Guaranteed Secure Wireless Internet (ITS)
Comm Class: WAN - Wide Area Network
Standards in Profile:
| Level | Standard |
|---|---|
| Access | Wireless Internet Alternatives (NA) |
| Mgmt | Bundle: SNMPv3 MIB |
| Security | Secure Session Alternatives |
| TransNet | IETF RFC 9293 TCP |
| TransNet | IP Alternatives |
Data Profile: US: SAE J3067 (J2735 SE)
Standards in Profile:
| Level | Standard |
|---|---|
| Facilities | SAE J2945/0 DSRC Common Design Elements |
| ITS Application Entity | SAE J3067 DSRC Prop Mods to 2735 |
Solution Issues Severity: 14
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
| Default | Severity | Name | Type | Description |
|---|---|---|---|---|
| False | Medium | Option not standardized | Standardization Gap | The option set includes at least one option that is not (yet) defined in a standard. |
| False | Medium | Overlap of standards | Overlap | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. |
| False | Medium | Regulatory Permission Needed | Standardization Gap | Deployment of this standard requires regulatory approval, which is currently subject to significant delays. |
| False | Medium | Uncertainty about trust revocation mechanism | Security Gap | The mechanisms used to prevent bad actors from sending authorized messages is unproven. |
| False | High | Regulatory Issue | Standardization Gap | Deployment of this standard is subject to regulatory approval, which is not currently expected to be granted for deployments in the near-term. |
| True | Medium | Outdated security reference | Security Gap | The standard solution includes an outdated security reference. |
| True | Medium | Secure data access not provided | Security Gap | The solution does not define rules on how the application entity authenticates requests to accept or provide data. |
| True | High | Not a standard (severe) | Standardization Gap | Although the document is publicly available, it has not been the subject of a rigorous industry review and is only provided as informal guidance. It is expected that details will change significantly prior to adoption as a standard. |