US: TCIP - Secure Internet (ITS)

Description:

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

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

Level	Doc #	Standard	Description
Access		Internet Subnet Alternatives	A set of alternative standards that includes any Subnet Layer method of connecting to the Internet.
Mgmt		Bundle: SNMPv3 MIB	A bundle of standards (RFCs) that groups the common management information bases (MIBs) used to manage IP networks at the transport layer and below using SNMPv3.
Security		Secure Session Alternatives	A set of alternative standards that identifies standards that are used to establish and maintain secure Internet sessions. If an information exchange does not require encryption, the (D)TLS session can negotiate NULL encryption. NOTE: If TCP is selected in the TransNet Layer, one of the TLS alternatives must be selected from this alternative set; if UDP is selected in the TransNet Layer, one of the DTLS alternatives must be selected from this alternative set.
TransNet		Internet Transport Alternatives	A set of alternative standards that identifies the two major options for the transport layer for mainstream IP-based deployments.
TransNet		IP Alternatives	A set of alternative standards that allows for the selection of IPv4 or IPv6.

Data Profile: US: TCIP

Level	Doc #	Standard	Description
Facilities		Encoding Alternatives	A set of alternative standards for encoding schemes that can be used to transfer data.
Facilities	APTA TCIP-S-001 Vol 2	TCIP - Data	This standard defines the data concepts used by the TCIP standard.
ITS Application Entity	APTA TCIP-S-001 Vol 2	TCIP - Data	This standard defines the data concepts used by the TCIP standard.

Readiness Description:

Multiple significant and minor issues.  For existing deployments, the chosen solution is likely deficient in security or management capabilities, and the issues should be reviewed and upgrades developed as needed. Some solutions in this category may also be becoming obsolete from an interoperability perspective and if this is the case, then upgrades should be planned as soon as possible. For new deployments, the solution may be viable for pilots when applied to the triples it supports; such pilot deployments should consider a path to addressing these issues as a part of their design activities. The solution does not provide sufficient interoperability, management, and security to enable proper, full-scale deployment without  additional work.