This solution is used within Canada and the U.S.. It combines standards associated with US: ADMS with those for I–I: Secure Internet (ITS). The US: ADMS standards include upper–layer standards required to implement interfaces with an archived data management system. 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.
| 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 | ASTM E2259–03a | Standard Guide for Archiving and Retrieving ITS–Generated Data | This 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 Entity | ASTM E2468–05 | Standard Practice for Metadata to Support Archived Data Management Systems | This 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 Entity | ASTM E2665–08 | Standard Specification for Archiving ITS–Generated Traffic Monitoring Data | This 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 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 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 | | Internet Subnet Alternatives | A set of alternative standards that includes any Subnet Layer method of connecting to the Internet. |
|---|
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.
| Source | Destination | Flow |
|---|
| Ankeny Central Signal Management System | Ankeny Traffic Management Center | archive analysis results |
|---|
| Ankeny Central Signal Management System | Ankeny Traffic Management Center | archive status |
|---|
| Ankeny Central Signal Management System | Ankeny Traffic Management Center | archived data products |
|---|
| Ankeny Traffic Management Center | Ankeny Central Signal Management System | archive analysis requests |
|---|
| Ankeny Traffic Management Center | Ankeny Central Signal Management System | archived data product requests |
|---|
| Ankeny Traffic Management Center | Ankeny Central Signal Management System | traffic archive data |
|---|
| DART Dart Way Maintenance Garage | DART TransTrack Data System | transit archive data |
|---|
| DART Dart Way Maintenance Garage | DART TransTrack Data System | traveler archive data |
|---|
| DART TransTrack Data System | DART Dart Way Maintenance Garage | archive status |
|---|
| Des Moines Police Department | Des Moines Police Department CAD/RMS | traffic archive data |
|---|
| Des Moines Police Department | Iowa DOT TRACS | traffic archive data |
|---|
| Des Moines Police Department CAD/RMS | Des Moines Police Department | archive status |
|---|
| Iowa DOT TRACS | Des Moines Police Department | archive status |
|---|
| Iowa DOT TRACS | Windsor Heights Public Safety | archive status |
|---|
| Polk County Emergency Management DisasterLAN | Polk County IT Department Data Storage | asset archive data |
|---|
| Polk County IT Department Data Storage | Polk County Emergency Management DisasterLAN | archive status |
|---|
| Waukee Public Works Building | Waukee Public Works Elements XS | maint and constr archive data |
|---|
| Waukee Public Works Building | Waukee Public Works Elements XS | traffic archive data |
|---|
| Waukee Public Works Elements XS | Waukee Public Works Building | archive status |
|---|
| Windsor Heights Public Safety | Iowa DOT TRACS | traffic archive data |
|---|