US: GTFS - Secure Wireless Internet (ITS)

Description:

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

Relevant Regions:

Comm Profile: I-M: Secure Wireless Internet (ITS)

Comm Class: WAN - Wide Area Network

Standards in Profile:
LevelStandard
AccessWireless Internet Alternatives (NA)
MgmtBundle: SNMPv3 MIB
SecuritySecure Session Alternatives
TransNetInternet Transport Alternatives
TransNetIP Alternatives

Data Profile: US: GTFS

Standards in Profile:
LevelStandard
FacilitiesIETF RFC 4180 CSV Files
FacilitiesIETF RFC 7159 JSON
FacilitiesIETF RFC 9110 HTTP Semantics
FacilitiesIETF RFC 9112 HTTP/1.1
FacilitiesISO 21320-1 ZIP
ITS Application EntityGeneral Transit Feed Specification - Realtime
ITS Application EntityGeneral Transit Feed Specification - Schedule

Solution Issues Severity: 13

The severity issue score calculation only includes issues associated with standards that are included by default.

Solution Issues:

DefaultSeverityNameTypeDescription
FalseLowOverlap of standards (Minor)OverlapMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. However, as this information transfer is infrastructure-based, agencies can deploy a solution throughout their jurisdiction with minimal downside and can use gateways to connect to other technologies.
FalseLowTime synchronizationPerformance / Applicability GapThe standard requires a highly accurate time shared between participants.
FalseMediumOverlap of standardsOverlapMultiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.
FalseMediumUncertainty about trust revocation mechanismSecurity GapThe mechanisms used to prevent bad actors from sending authorized messages is unproven.
FalseMediumUnvetted by communityStandardization GapThe proposed solution uses a suite of standards that is accepted within some communities, but has not necessarily been accepted for use within the context of this information triple.
FalseHighRegulatory IssueStandardization GapDeployment of this standard is subject to regulatory approval, which is not currently expected to be granted for deployments in the near-term.
TrueLowNot a standard (minor)Standardization GapThe document is publicly available and widely used but it is not currently a formal standard.
TrueMediumOutdated security referenceSecurity GapThe standard solution includes an outdated security reference.
TrueHighApplication specification not definedITS Info GapThe logic, performance, and application security rules are not defined for this information flow.

Solution to Triples

SourceFlowDestination
Transit Management Center personal transit information Personal Information Device
Transit Management Center transit traveler information Transit Vehicle OBE