TPEG2 - Secure Internet (ITS)

Description:

This solution is used within Australia, the E.U. and the U.S.. It combines standards associated with TPEG2 with those for I-I: Secure Internet (ITS). The TPEG2 standards include upper-layer standards required to support multi-modal information services.. 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: TPEG2

Level	Doc #	Standard	Description
Facilities	No Standard Needed	Not Needed	The services related to this portion of the stack are not critical within the scope of this solution.
ITS Application Entity	ISO 21219-15	ISO 21219-15 TPEG2 - Traffic Event	ISO/TS 21219-15 specifies the TPEG application: Traffic Event Compact. This application has been specifically designed to support information about traffic events (e.g. road works, traffic jams). A specific form of traffic events are local hazard warnings which, being safety-related messages, are sent with high priority to warn a driver that may encounter dangerous situations (e.g. black-ice, accident beyond curves, obstacles on road, etc.) unexpectedly.
Mgmt	ISO 21219-6	ISO 21219-6 TPEG2 - Message Mgmt	ISO 21219-6 adds a basic toolkit definition to the ISO 21219 series specifying the Message Management Container (MMC), which is used by all TPEG applications to provide information about the handling of messages on the TPEG client side. The MMC holds administrative information allowing a decoder to handle the message appropriately. This information is not aimed at the end user. The MMC is a toolkit and not a stand-alone application but is included in TPEG applications.
Security	ISO 21219-24	ISO 21219-24 TPEG2 - Light Encryption	ISO/TS 21219-24 defines the LTE encryption mechanism for TPEG Service Data Frames. It has been specifically designed for use with Business-to-Business (B2B) business models. The objective of this document is to provide a simple to use, yet effective Conditional Access mechanism for TPEG including encryption for use with both broadcast and/or point-to-point delivery. For both service providers and device manufacturers, a standardized conditional access mechanism is beneficial to avoid a proliferation of proprietary methods with multiplied implementation effort and lead times.

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.