US: ADMS - Guaranteed Secure Internet (ITS)

Description

This solution is used within Canada and the U.S.. It combines standards associated with US: ADMS with those for I–I: Guaranteed Secure Internet (ITS). The US: ADMS standards include upper–layer standards required to implement interfaces with an archived data management system. The I–I: Guaranteed Secure Internet (ITS) standards include lower–layer standards that support secure communications with guaranteed delivery 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 EntityASTM E2259–03aStandard Guide for Archiving and Retrieving ITS–Generated DataThis guide deals in general with the questions of what data and information should be considered for archiving as well as what data and information should be considered for retrieval.
ITS Application EntityASTM E2468–05Standard Practice for Metadata to Support Archived Data Management SystemsThis standard describes a hierarchical outline of sections and elements to be used in developing metadata to support archived data management systems. Specifically, the standard establishes the names of metadata elements and compound elements to be used in the metadata, the definitions of these metadata elements and compound elements, and suggested information about and examples of the values that are to be provided for the metadata elements.
ITS Application EntityASTM E2665–08Standard Specification for Archiving ITS–Generated Traffic Monitoring DataThis specification describes data elements and schema for an archived data management system for ITS–generated traffic monitoring data, including conventional traffic monitoring data, data collected directly from ITS systems, and travel–time data from probe vehicles. It establishes the names of the data elements, their interrelationships, and their procedural definitions. These procedural definitions include data collection instrumentation and methodology as well as recommended procedures for calculating traffic statistics.
Facilities Standard(s) need to be developedOne or more standards need to be developed for this subject matter before this is considered a complete solution.
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: 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

IssueSeverityDescriptionAssociated StandardAssociated Triple
Data profile not definedUltraPerformance, functionality, and the upper–layers of the OSI stack have not been defined for this information flow.(None)(All)

Supports Interfaces

SourceDestinationFlow
AMATS Data ArchiveCity of Akron Crash Data Archivearchive coordination
AMATS Data ArchiveCounty and City Traffic Data Archivesarchive coordination
AMATS Data ArchiveODOT Traffic Data Archive Systemarchive coordination
AMATS Data ArchiveOSU Center of Automotive Researcharchive coordination
AMATS Data ArchiveTransportation Research Centersarchive coordination
City of Akron Crash Data ArchiveAMATS Data Archivearchive coordination
City of Akron Crash Data ArchiveODOT Traffic Data Archive Systemarchive coordination
City of Akron Crash Data ArchiveOSU Center of Automotive Researcharchive coordination
City of Akron Crash Data ArchiveTransportation Research Centersarchive coordination
County and City Traffic Data ArchivesAMATS Data Archivearchive coordination
County and City Traffic Data ArchivesODOT Traffic Data Archive Systemarchive coordination
County and City Traffic Data ArchivesOSU Center of Automotive Researcharchive coordination
County and City Traffic Data ArchivesTransportation Research Centersarchive coordination
METRO RTA Transit Data ArchivesOSU Center of Automotive Researcharchive coordination
METRO RTA Transit Data ArchivesTransportation Research Centersarchive coordination
ODOT Traffic Data Archive SystemAMATS Data Archivearchive coordination
ODOT Traffic Data Archive SystemCity of Akron Crash Data Archivearchive coordination
ODOT Traffic Data Archive SystemCounty and City Traffic Data Archivesarchive coordination
ODOT Traffic Data Archive SystemOhio DPS Crash Databasearchive coordination
ODOT Traffic Data Archive SystemOSU Center of Automotive Researcharchive coordination
ODOT Traffic Data Archive SystemTransportation Research Centersarchive coordination
Ohio DPS Crash DatabaseODOT Traffic Data Archive Systemarchive coordination
Ohio DPS Crash DatabaseOSU Center of Automotive Researcharchive coordination
Ohio DPS Crash DatabaseTransportation Research Centersarchive coordination
OSU Center of Automotive ResearchAMATS Data Archivearchive coordination
OSU Center of Automotive ResearchCity of Akron Crash Data Archivearchive coordination
OSU Center of Automotive ResearchCounty and City Traffic Data Archivesarchive coordination
OSU Center of Automotive ResearchMETRO RTA Transit Data Archivesarchive coordination
OSU Center of Automotive ResearchODOT Traffic Data Archive Systemarchive coordination
OSU Center of Automotive ResearchOhio DPS Crash Databasearchive coordination
OSU Center of Automotive ResearchPARTA Transit Data Archivesarchive coordination
OSU Center of Automotive ResearchTransportation Research Centersarchive coordination
PARTA Transit Data ArchivesOSU Center of Automotive Researcharchive coordination
PARTA Transit Data ArchivesTransportation Research Centersarchive coordination
Transportation Research CentersAMATS Data Archivearchive coordination
Transportation Research CentersCity of Akron Crash Data Archivearchive coordination
Transportation Research CentersCounty and City Traffic Data Archivesarchive coordination
Transportation Research CentersMETRO RTA Transit Data Archivesarchive coordination
Transportation Research CentersODOT Traffic Data Archive Systemarchive coordination
Transportation Research CentersOhio DPS Crash Databasearchive coordination
Transportation Research CentersOSU Center of Automotive Researcharchive coordination
Transportation Research CentersPARTA Transit Data Archivesarchive coordination