Toledo Regional ITS Architecture (2021)

(None-Data) - WAVE IPv6

Description

This solution is used within the U.S.. It combines standards associated with (None–Data) with those for V–X: WAVE IPv6. The (None–Data) standards include an unspecified set of standards at the upper layers. The V–X: WAVE IPv6 standards include lower–layer standards that support connectionless vehicle–to–any communications within ~300m using the Internet Protocol version 6 (IPv6) over IEEE WAVE in the 5.9GHz spectrum.

Includes Standards

Level	DocNum	FullName	Description
Mgmt	Addressed Elsewhere	Addressed Elsewhere in Stack	The services related to this portion of the stack are defined in the other standards listed for this solution.
Security	IEEE 1609.2	IEEE Standard for Wireless Access in Vehicular Environments – Security Services for Applications and Management Messages	This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.
Security	IEEE 1609.2a	IEEE 1609.2a–2017 – IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 1	This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.
Security	IEEE 1609.2b	IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 2––PDU Functional Types and Encryption Key Management	This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.
ITS Application Entity		Standard(s) need to be developed	One or more standards need to be developed for this subject matter before this is considered a complete solution.
Facilities		Standard(s) need to be developed	One or more standards need to be developed for this subject matter before this is considered a complete solution.
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 4861	Neighbor Discovery for IP version 6 (IPv6)	This standard (RFC) specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link–layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors.
TransNet	IETF RFC 4862	IPv6 Stateless Address Autoconfiguration	This standard (RFC) specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link–local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link.
TransNet	IETF RFC 793	Transmission Control Protocol	This standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks.
TransNet	IEEE 1609.3	IEEE Standard for Wireless Access in Vehicular Environments (WAVE) – Networking Services	This standard defines the network and transport layer options for the WAVE environment. The standard defines three options: a bandwidth efficient single–hop solution known as WSMP, UDP/IP, and TCP/IP. It has been harmonized with ISO FNTP and FSAP – a common message format specified in ISO 16460.
Access	IEEE 1609.4	IEEE Draft Standard for Wireless Access in Vehicular Environments – Multi–Channel Operation	This standard primarily defines the data link layer of the WAVE communications stack.
Access	IEEE 802.11	IEEE Draft Standard for Information technology––Telecommunications and information exchange between systems Local and metropolitan area networks––Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specificatio	This standard defines the physical and data link layers for wireless Ethernet, including WiFi and DSRC.
Access	ISO/IEC 8802–2	IEEE Standard for Information technology –– Telecommunications and information exchange between systems––Local and metropolitan area networks –– Specific requirements –– Part 2: Logical Link Control	ISO/IEC 8802–2 describes the logical link control (LLC) sublayer, which constitutes the top sublayer in the data link layer of the ISO 8802 Local Area Network Protocol (also known as IEEE 802.2).

Readiness: Lowest

Readiness Description

Many serious issues. This category includes solutions that have not been standardized, or do not have a basic level of interoperability or security. Consider selecting a different communications solution or if this is not possible (eg. a pilot of a new application that has not been standardized), take additional measures to provide an acceptable level of security or interoperability.

Issues

Issue	Severity	Description	Associated Standard	Associated Triple
Data profile not defined	Ultra	Performance, functionality, and the upper–layers of the OSI stack have not been defined for this information flow.	(None)	(All)
Data not fully defined (medium)	Medium	Some of the data elements for this information flow are not fully defined.	(None)	Commercial Vehicles=>freight equipment information=>OSHP Weigh–in–Motion Stations
Data not fully defined (medium)	Medium	Some of the data elements for this information flow are not fully defined.	(None)	Commercial Vehicles=>freight equipment information=>OSHP Weigh Station
Overlap of standards	Medium	Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.	Bundle: WAVE – Subnet	(All)
Uncertainty about trust revocation mechanism	Medium	The mechanisms used to prevent bad actors from sending authorized messages is unproven.	Bundle: IEEE 1609.2	(All)

Supports Interfaces

Source	Destination	Flow
Bowling Green State University Shuttle Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
City of Bowling Green Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	access request
City of Bowling Green Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
City of Bowling Green Maintenance Vehicles	County and City Connected Vehicles Roadside Equipment	access request
City of Toledo Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	access request
City of Toledo Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
City of Toledo Maintenance Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Commercial Vehicles	OSHP Weigh Station	freight equipment information
Commercial Vehicles	OSHP Weigh–in–Motion Stations	freight equipment information
Connected/Automated Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Connected/Automated Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
Connected/Automated Vehicles	OTIC Connected Vehicles Roadside Equipment	access request
Connected/Automated Vehicles	Toledo–Lucas County Port Authority Connected Vehicle Roadside Equipment	access request
County and City Connected Vehicles Roadside Equipment	City of Bowling Green Emergency Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	City of Bowling Green Maintenance Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	City of Toledo Emergency Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	City of Toledo Maintenance Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Connected/Automated Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Lucas County EMS Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Lucas County Fire Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Lucas County Maintenance Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Lucas County Sheriff Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Municipal Emergency Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Municipal Maintenance Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Wood County Emergency Vehicles	access permission
County and City Connected Vehicles Roadside Equipment	Wood County Maintenance Vehicles	access permission
Lucas County EMS Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Lucas County EMS Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
Lucas County Fire Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Lucas County Fire Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
Lucas County Maintenance Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Lucas County Sheriff Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Lucas County Sheriff Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
Municipal Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Municipal Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
Municipal Maintenance Vehicles	County and City Connected Vehicles Roadside Equipment	access request
ODOT Connected Vehicles Roadside Equipment	Bowling Green State University Shuttle Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	City of Bowling Green Emergency Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	City of Toledo Emergency Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	Connected/Automated Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	Lucas County EMS Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	Lucas County Fire Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	Lucas County Sheriff Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	Municipal Emergency Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	ODOT District 2 Maintenance Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	ODOT Freeway Safety Patrol Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	OSHP District 1 and 2 Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	OSHP District 10 Vehicles	access permission
ODOT Connected Vehicles Roadside Equipment	Wood County Emergency Vehicles	access permission
ODOT District 2 Maintenance Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
ODOT Freeway Safety Patrol Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
OSHP District 1 and 2 Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
OSHP District 1 and 2 Vehicles	OTIC Connected Vehicles Roadside Equipment	access request
OSHP District 10 Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
OSHP District 10 Vehicles	OTIC Connected Vehicles Roadside Equipment	access request
OTIC Connected Vehicles Roadside Equipment	Connected/Automated Vehicles	access permission
OTIC Connected Vehicles Roadside Equipment	OSHP District 1 and 2 Vehicles	access permission
OTIC Connected Vehicles Roadside Equipment	OSHP District 10 Vehicles	access permission
OTIC Connected Vehicles Roadside Equipment	OTIC Maintenance and Construction Vehicles	access permission
OTIC Connected Vehicles Roadside Equipment	OTIC Public Service Vehicles	access permission
OTIC Maintenance and Construction Vehicles	OTIC Connected Vehicles Roadside Equipment	access request
OTIC Public Service Vehicles	OTIC Connected Vehicles Roadside Equipment	access request
Toledo–Lucas County Port Authority Connected Vehicle Roadside Equipment	Connected/Automated Vehicles	access permission
Wood County Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	access request
Wood County Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	access request
Wood County Maintenance Vehicles	County and City Connected Vehicles Roadside Equipment	access request