Standards Development

Scope

This document specifies the minimum requirements for a secured ship network over Ethernet protocols that is used to collect data from the bridge, engine room, and cargo system based on Ethernet protocols of IPv6, even if the data are collected with different protocols based on IPv4 or IEC 61162- series, other ISO, and industrial standards.

To communicate with different IP address families, this document uses NAT64 network address translation specified in RFC 6144 (Framework for NAT), and RFC 6146 (Stateful NAT64). But utilizing NAT 64 may not be the only method, the other method such as the utilization of dual stack, tunneling and other methods may be utilized by the shipbuilder, ship owner, or system integrator with consideration of the effectiveness of the ship networks communications and data collections and integrations.

If a device has a Dual Stack, then devices are able to run IPv4 and IPv6 in parallel. It allows hosts to simultaneously reach IPv4 and IPv6 content, so it offers a very flexible coexistence strategy. However there are some constraints in interoperability.

Address Family Translation (AFT) may not be a long-term support strategy. However it is a medium-term coexistence strategy for integrating IPv6 and IPv4 networks on board. Almost all network standards in the maritime domain are based on IPv4, but this standard may be able to maintain interoperability with IPv4 standards and other industrial standards such as Modbus, which may be used for SCADA systems, SAE J1939 which may be used for the internal combustion engine systems.

ISA99 Cyber security on board has become vital, especially in smart and autonomous ships. This document specifies how to build up security in data acquisition through the network by authentication, integrity checking and confidentiality by utilizing recent encryption algorithms.