X.1373 - Secure Wireless Internet (ITS)
Description:
This solution is used within Canada and the U.S.. It combines standards associated with X.1373 with those for I-M: Secure Wireless Internet (ITS). The X.1373 standards include upper-layer standards required to update software according to ITU-T approach. The I-M: Secure Wireless Internet (ITS) standards include lower-layer standards that support secure communications 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: 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 | Internet Transport Alternatives |
TransNet | IP Alternatives |
Data Profile: X.1373
Standards in Profile:
Level | Standard |
---|---|
Facilities | ITU-T ITS Secure Software Update |
ITS Application Entity | ITU-T ITS Secure Software Update |
Solution Issues Severity: 10
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
Default | Severity | Name | Type | Description |
---|---|---|---|---|
True | Low | Data may not be fully defined (low) | ITS Info Gap | The information flow is unclear as to what precisely is needed; the standard may not fully support the needs of the information flow, depending on how it is interpreted. |
True | Low | Relatively new technology | Standardization Gap | The standard is finalized but has not been widely deployed. Deployment experience may result in further revisions in the technology, although it is expected that the standards group will make reasonable efforts to make any changes backwards compatible. |
True | High | Data/comm profile pairing | Standardization Gap | There are ambiguities as to how to (or if one should) couple the upper-layer standards defined in this solution with the indicated lower-layer standards. |
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. |
Solution to Triples
This solution is used on the following information flow triples:
Source | Flow | Destination |
---|---|---|
Vehicle Service Center | vehicle software install/upgrade | Vehicle |