(None-Data) - Guaranteed Secure Internet (ITS)
Description
This solution is used within Australia, the E.U. and the U.S.. It combines standards associated with (None–Data) with those for I–I: Guaranteed Secure Internet (ITS). The (None–Data) standards include an unspecified set of standards at the upper layers. The I–I: Guaranteed Secure Internet (ITS) standards include lower–layer standards that support secure communications with guaranteed delivery between ITS equipment using X.509 or IEEE 1609.2 security certificates.
Includes Standards
| 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 | 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. | |
| 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 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 8200 | Internet Protocol, Version 6 | This document specifies version 6 of the Internet Protocol (IPv6). |
| TransNet | IETF RFC 9293 | Transmission Control Protocol | This document specifies the Transmission Control Protocol (TCP). TCP is an important transport–layer protocol in the Internet protocol stack, and it has continuously evolved over decades of use and growth of the Internet. Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793. This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793. It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements. It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN–RECEIVED state. The TCP header control bits from RFC 793 have also been updated based on RFC 3168. |
| Access | Internet Subnet Alternatives | A set of alternative standards that includes any Subnet Layer method of connecting to the Internet. |
Readiness: Lowest
Readiness Description
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.
Supports Interfaces
| Source | Destination | Flow |
|---|---|---|
| CAT Operations Center | EGF Dispatch | transit emergency data |
| CAT Operations Center | GF PSAP | alert status |
| CAT Operations Center | GF PSAP | transit emergency data |
| CAT Operations Center | GF–EGF Emergency Management | emergency plan coordination |
| EGF Dispatch | GF PIC | alert notification |
| EGF Dispatch | GF TOC | emergency route request |
| EGF Dispatch | MnDOT D2 Office | alert notification |
| GF PIC | EGF Dispatch | alert status |
| GF PIC | GF PSAP | alert status |
| GF PSAP | CAT Operations Center | alert notification |
| GF PSAP | CAT Operations Center | threat information |
| GF PSAP | GF PIC | alert notification |
| GF PSAP | GF TOC | alert notification |
| GF PSAP | GF TOC | emergency route request |
| GF PSAP | NDDOT GF District Office | alert notification |
| GF PW Operations Center | GF PSAP | alert status |
| GF TOC | EGF Dispatch | alert status |
| GF TOC | EGF Dispatch | emergency routes |
| GF TOC | GF PSAP | alert status |
| GF TOC | GF PSAP | emergency routes |
| GF TOC | GF–EGF Emergency Management | emergency plan coordination |
| GF TOC | GF–EGF Emergency Management | road network status assessment |
| GF TOC | GF–EGF Maintenance | road network status assessment |
| GF TOC Field Devices | GF TOC | rail crossing blockage notification |
| GF–EGF Emergency Management | CAT Operations Center | emergency plan coordination |
| GF–EGF Emergency Management | GF TOC | emergency plan coordination |
| GF–EGF Emergency Management | GF–EGF Maintenance | emergency plan coordination |
| GF–EGF Maintenance | GF TOC | road network status assessment |
| GF–EGF Maintenance | GF–EGF Emergency Management | emergency plan coordination |
| GF–EGF Maintenance | GF–EGF Emergency Management | road network status assessment |
| MnDOT D2 Field Devices | MnDOT D2 Office | rail crossing blockage notification |
| MnDOT D2 Office | EGF Dispatch | alert status |
| NDDOT GF District Office | EGF Dispatch | alert status |
| NDDOT GF District Office | GF PSAP | alert status |
| State Radio | GF PIC | alert notification |