US: GTFS static - Secure Wireless Internet (ITS)


This solution is used within the U.S.. It combines standards associated with US: GTFS static with those for I–M: Secure Wireless Internet (ITS). The US: GTFS static standards include upper–layer standards required to implement static, public, transit–related communications. 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.

Includes Standards

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 EntityGTFSGeneral Transit Feed SpecificationThis document defines a common (open data) format for exchanging public transportation schedules and associated geographic information.
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.
FacilitiesISO 21320–1Information technology — Document Container File — Part 1: CoreISO/IEC 21320–1 specifies the core requirements for 1) document container files, and 2) implementations that produce and/or consume document container files. It normatively references the Zip File Format Specification version 6.3.3 of PKWARE(R) Inc. Document container files are conforming Zip files as specified by that document.
FacilitiesIETF RFC 4180Common Format and MIME Type for Comma–Separated Values (CSV) FilesThis standard (RFC) documents the format used for Comma–Separated Values (CSV) files and registers the associated MIME type "text/csv".
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.
Access3GPP Network3GPP Cellular Communications NetworkThis 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.

Readiness: High–Moderate

Readiness Description

One significant or possibly a couple minor issues. For existing deployments, the chosen solution likely has identified security or management issues not addressed by the communications solution. Deployers should consider additional security measures, such as communications link and physical security as part of these solutions. They should also review the management issues to see if they are relevant to their deployment and would require mitigation. For new deployments, the deployment efforts should consider a path to addressing these issues as a part of their design activities. The solution does not by itself provide a fully secure implementation without additional work.


IssueSeverityDescriptionAssociated StandardAssociated Triple
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)
Not a standard (minor)LowThe document is publicly available and widely used but it is not currently a formal standard.General Transit Feed Specification(All)

Supports Interfaces

METRO RTA Fixed–Route DispatchMETRO RTA Fixed–Route Vehiclestransit schedule information
METRO RTA Paratransit DispatchMETRO RTA Fixed–Route Vehiclestransit schedule information
METRO RTA Paratransit DispatchMETRO RTA Paratransit Vehiclestransit schedule information
PARTA Fixed–Route DispatchPARTA Fixed–Route Vehiclestransit schedule information
PARTA Paratransit DispatchPARTA Paratransit Vehiclestransit schedule information
University of Akron Roo Express Dispatch CenterUniversity of Akron Roo Express Shuttle Service Vehiclestransit schedule information