This solution is used within the U.S.. It combines standards associated with US: SAE J3067 (J2735 SE) with those for I-M: 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: 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.
Level | DocNum | FullName | Description |
---|---|---|---|
Mgmt | IETF RFC 3411 | An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks | This standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture. |
Mgmt | IETF RFC 3412 | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that assists in managing the message processing and dispatching subsystem of an SNMP entity. |
Mgmt | IETF RFC 3413 | Simple Network Management Protocol (SNMP) Applications | This standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys. |
Mgmt | IETF RFC 3414 | User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) | This standard (RFC) contains a MIB that assists in configuring and managing the user-based security model. |
Mgmt | IETF RFC 3415 | View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that supports the configuration and management of the View-based access control model of SNMP. |
Mgmt | IETF RFC 3416 | Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines the message structure and protocol operations used by SNMPv3. |
Mgmt | IETF RFC 3418 | Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines the MIB to configure and manage an SNMP entity. |
Mgmt | IETF RFC 4293 | Management Information Base for the Internet Protocol (IP) | This standard (RFC) defines the MIB that manages an IP entity. |
Security | IETF RFC 5280 | Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile | This standard (RFC) defines how to use X.509 certificates for secure communications over the Internet. |
Security | IETF RFC 8446 | The Transport Layer Security (TLS) Protocol | This standard (RFC) specifies Version 1.3 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. |
ITS Application Entity | SAE J3067 | Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary [SAE J2735] Using Systems Engineering Methods | This informational report formalized a deliverable received from the USDOT as suggested improvements to SAE J2735:2009. Many of these suggestions have been incorporated into later revisions of SAE J2735 and SAE J2945/x; additional suggestions may be incorporated as the documents are extended to address additional applications. |
Facilities | SAE J2945 | Dedicated Short Range Communication (DSRC) Systems Engineering Process Guidance for J2945/x Documents and Common Design Concepts | This standard defines cross-cutting material which applies to the J2945/x series including generic DSRC interface requirements and guidance on Systems Engineering (SE) content. |
TransNet | IETF RFC 2460 | Internet Protocol, Version 6 (IPv6) Specification | This standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. |
TransNet | IETF RFC 4291 | IP Version 6 Addressing Architecture | This standard (RFC) defines the addressing architecture of the IP Version 6 (IPv6) protocol. It includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. |
TransNet | IETF RFC 4443 | Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification | This standard (RFC) defines the control messages to manage IPv6. |
TransNet | IETF RFC 793 | Transmission Control Protocol | This standard (RFC) defines the main connection-oriented Transport Layer protocol used on Internet-based networks. |
Access | 3GPP Network | 3GPP Cellular Communications Network | This proxy standard represents a variety of 3GPP releases and underlying standards and technologies that rely upon cellular base stations for connectivity, including 3G, 4G, and the emerging 5G technologies. |
Two significant or one significant and several minor issues. For existing deployments, the chosen solution is likely deficient in security or management capabilities and the issues should be reviewed and upgrades developed as needed. For new deployments, the solution may be viable for pilots when applied to the triples it supports; such pilot deployments should consider a path to addressing these issues as a part of their design activities. The solution does not provide sufficient interoperability, management, and security to enable proper, full-scale deployment without additional work.
Issue | Severity | Description | Associated Standard | Associated Triple |
---|---|---|---|---|
Not a standard (severe) | High | 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. | SAE J3067 DSRC Prop Mods to 2735 | (All) |
Secure data access not provided | Medium | The solution does not define rules on how the application entity authenticates requests to accept or provide data. | (None) | (All) |
Source | Destination | Flow |
---|---|---|
CC 911 Center | Local Emergency Vehicles (Fire, EMS, Police) | emergency acknowledge |
CC 911 Center | Local Emergency Vehicles (Fire, EMS, Police) | emergency data request |
CCSO Communications Office | CCSO Vehicles | emergency acknowledge |
CCSO Communications Office | CCSO Vehicles | emergency data request |
CCSO Vehicles | CCSO Communications Office | emergency notification |
Dutchess LOOP Demand Response Transit Vehicles | Dutchess LOOP Transit Facility | emergency notification |
Dutchess LOOP Fixed-Route Transit Vehicles | Dutchess LOOP Transit Facility | emergency notification |
Dutchess LOOP Transit Facility | Dutchess LOOP Demand Response Transit Vehicles | emergency acknowledge |
Dutchess LOOP Transit Facility | Dutchess LOOP Demand Response Transit Vehicles | emergency data request |
Dutchess LOOP Transit Facility | Dutchess LOOP Fixed-Route Transit Vehicles | emergency acknowledge |
Dutchess LOOP Transit Facility | Dutchess LOOP Fixed-Route Transit Vehicles | emergency data request |
Local Emergency Vehicles (Fire, EMS, Police) | CC 911 Center | emergency notification |
NYSBA Command Center | NYSBA Help Line | emergency acknowledge |
NYSBA Help Line | NYSBA Command Center | emergency notification |
NYSDOT H.E.L.P. Vehicles | NYSP Dispatch and Regional Command | emergency notification |
NYSP Dispatch and Regional Command | NYSDOT H.E.L.P. Vehicles | emergency acknowledge |
NYSP Dispatch and Regional Command | NYSDOT H.E.L.P. Vehicles | emergency data request |
NYSP Dispatch and Regional Command | NYSP Emergency Vehicles | emergency acknowledge |
NYSP Dispatch and Regional Command | NYSP Emergency Vehicles | emergency data request |
NYSP Dispatch and Regional Command | NYSP Portable Radio | emergency acknowledge |
NYSP Dispatch and Regional Command | NYSP Troop T Vehicles | emergency acknowledge |
NYSP Dispatch and Regional Command | NYSP Troop T Vehicles | emergency data request |
NYSP Dispatch and Regional Command | NYSTA Emergency Call Boxes | emergency acknowledge |
NYSP Emergency Vehicles | NYSP Dispatch and Regional Command | emergency notification |
NYSP Portable Radio | NYSP Dispatch and Regional Command | emergency notification |
NYSP Troop T Vehicles | NYSP Dispatch and Regional Command | emergency notification |
NYSTA Emergency Call Boxes | NYSP Dispatch and Regional Command | emergency notification |
NYSTA Emergency Call Boxes | NYSTA Statewide Operations Center (TSOC) | emergency notification |
NYSTA Statewide Operations Center (TSOC) | NYSTA Emergency Call Boxes | emergency acknowledge |
PANYNJ Call Boxes | PANYNJ PAPD Communications Center Dispatch | emergency notification |
PANYNJ PAPD Communications Center Dispatch | PANYNJ Call Boxes | emergency acknowledge |
UCAT Dispatch Facility | UCAT Vehicles | emergency acknowledge |
UCAT Vehicles | UCAT Dispatch Facility | emergency notification |