US: ATIS - Secure Internet (ITS)

Description

This solution is used within the U.S.. It combines standards associated with US: ATIS with those for I–I: Secure Internet (ITS). The US: ATIS standards include upper–layer standards required to implement traveler information communications. 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.

Includes Standards

LevelDocNumFullNameDescription
MgmtIETF RFC 3411An Architecture for Describing Simple Network Management Protocol (SNMP) Management FrameworksThis standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture.
MgmtIETF RFC 3412Message 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.
MgmtIETF RFC 3413Simple Network Management Protocol (SNMP) ApplicationsThis standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys.
MgmtIETF RFC 3414User–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.
MgmtIETF RFC 3415View–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.
MgmtIETF RFC 3416Version 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.
MgmtIETF RFC 3418Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)This standard (RFC) defines the MIB to configure and manage an SNMP entity.
MgmtIETF RFC 4293Management Information Base for the Internet Protocol (IP)This standard (RFC) defines the MIB that manages an IP entity.
SecurityIETF RFC 5280Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileThis standard (RFC) defines how to use X.509 certificates for secure communications over the Internet.
SecurityIETF RFC 8446The Transport Layer Security (TLS) ProtocolThis 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 EntitySAE J2353Data Dictionary for Advanced Traveler Information Systems (ATIS)This document provides a set of core data elements needed by information service providers for Advanced Traveler Information Systems (ATIS). The data dictionary herein provides the foundation for ATIS message sets for all stages of travel (pre–trip and en route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in–vehicle, portable devices, kiosks, etc.). The elements of this document are the basis for the SAE ATIS Message Set Standard J2354 and are entered into the SAE Data Registry for ITS wide coordination.
FacilitiesIETF RFC 7230Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and RoutingThis standard (RFC) defines the main Application Layer protocol used for the world–wide web.
FacilitiesW3C XMLExtensible Markup Language (XML) 1.0 (Fifth Edition)This standard defines a generic markup language that can be used to share customizable information by using start and stop tags within the text.
FacilitiesSAE J2354Message Sets for Advanced Traveler Information System (ATIS)This standard defines how to exchange data for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (pre–trip and en–route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in–vehicle, portable devices, kiosks, etc.).
TransNetIETF RFC 2460Internet Protocol, Version 6 (IPv6) SpecificationThis standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng.
TransNetIETF RFC 4291IP Version 6 Addressing ArchitectureThis 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.
TransNetIETF RFC 4443Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationThis standard (RFC) defines the control messages to manage IPv6.
TransNetIETF RFC 793Transmission Control ProtocolThis standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks.
Access Internet Subnet AlternativesA set of alternative standards that includes any Subnet Layer method of connecting to the Internet.

Readiness: Low

Readiness Description

One serious or several significant issues. This category often includes proprietary or partial solutions. The communications solution may fail to provide even a base level of interoperability and security. Consider alternative solutions, or define specific revisions or upgrades that would provide a level of interoperability or security that are needed for the deployment.

Issues

IssueSeverityDescriptionAssociated StandardAssociated Triple
Encoding rules not definedHighThe standards do not unambiguously define which set of encoding rules to use.(None)(All)
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)PARTA Transit Information Displays=>trip request=>Ohio Smart Mobility Program
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Ohio Smart Mobility Program=>trip plan=>METRO RTA Transit Information Displays
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Ohio Smart Mobility Program=>trip plan=>PARTA Transit Information Displays
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)METRO RTA Transit Information Displays=>trip request=>Ohio Smart Mobility Program
Exception handling not definedMediumThe dialogs do not define how to handle exceptions (e.g., error codes, permission denied, etc).(None)(All)
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Akron Parking Management System=>parking information=>City of Akron Parking App
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)ODOT Rest Area Truck Parking Availability System=>parking information=>ODOT ATMS
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)ODOT Rest Area Truck Parking Availability System=>parking information=>ODOT OHGO Traveler Information System
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Kent Parking Management System=>parking information=>City of Kent Traffic Operations Center
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Cuyahoga Falls Parking Management System=>parking information=>City of Cuyahoga Falls Traffic Operations Center
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Cuyahoga Falls Parking Management System=>parking information=>City of Cuyahoga Falls Parking App
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Akron Parking Management System=>parking information=>DriveAkron
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Hudson Parking Management System=>parking information=>City of Hudson Traffic Operations Center
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Hudson Parking Management System=>parking information=>City of Hudson Parking App
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Barberton Parking Management System=>parking information=>City of Barberton Traffic Operations Center
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)Akron–Canton Airport Parking Management System=>parking information=>Akron–Canton Airport
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)OTIC Service Plaza Truck Parking Management System=>parking information=>OTIC Website
Overlap of standardsMediumMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.(None)City of Akron Parking Management System=>parking information=>City of Akron Traffic Operations Center
Performance not fully defined (medium)MediumThe performance rules are not fully defined for this information flow.(None)(All)
Secure data access not providedMediumThe solution does not define rules on how the application entity authenticates requests to accept or provide data.(None)(All)
Data not defined in standard formatLowThe definition of data concepts should conform to ISO 14817–1 to promote reuse among ITS.SAE J2353 ATIS DD(All)

Supports Interfaces

SourceDestinationFlow
Akron–Canton Airport Parking Management SystemAkron–Canton Airportparking information
City of Akron Parking Management SystemCity of Akron Parking Appparking information
City of Akron Parking Management SystemCity of Akron Traffic Operations Centerparking information
City of Akron Parking Management SystemDriveAkronparking information
City of Barberton Parking Management SystemCity of Barberton Traffic Operations Centerparking information
City of Cuyahoga Falls Parking Management SystemCity of Cuyahoga Falls Parking Appparking information
City of Cuyahoga Falls Parking Management SystemCity of Cuyahoga Falls Traffic Operations Centerparking information
City of Green Traffic Information WebsiteLocal Mediatraveler information for media
City of Hudson Parking Management SystemCity of Hudson Parking Appparking information
City of Hudson Parking Management SystemCity of Hudson Traffic Operations Centerparking information
City of Kent Parking Management SystemCity of Kent Traffic Operations Centerparking information
DriveAkronLocal Mediatraveler information for media
METRO RTA Transit Information DisplaysOhio Smart Mobility Programtrip request
ODOT OHGO Traveler Information SystemLocal Mediatraveler information for media
ODOT Rest Area Truck Parking Availability SystemODOT ATMSparking information
ODOT Rest Area Truck Parking Availability SystemODOT OHGO Traveler Information Systemparking information
Ohio Smart Mobility ProgramMETRO RTA Transit Information Displaystrip plan
Ohio Smart Mobility ProgramPARTA Transit Information Displaystrip plan
OTIC Service Plaza Truck Parking Management SystemOTIC Websiteparking information
OTIC WebsiteLocal Mediatraveler information for media
PARTA Transit Information DisplaysOhio Smart Mobility Programtrip request
Portage County WebsiteLocal Mediatraveler information for media
Summit County Engineer WebsiteLocal Mediatraveler information for media