]> Electronics and Telecommunications Research Institute

218 Gajeongno, Yuseung-gu Daejeon 34129 South Korea +82 42 860 6539 mhchoi@etri.re.kr

Electronics and Telecommunications Research Institute

218 Gajeongno, Yuseung-gu Daejeon 34129 South Korea +82 42 860 1429 yhc@etri.re.kr

int 6lo Short-Range Optical Wireless Communications OWC IEEE 802.15.7 6LowPAN IPv6 Adaptation Layer IoT Internet of Things Security considerations IEEE 802.15.7, "Short-Range Optical Wireless Communications" defines wireless communication using visible light. It defines how data is transmitted, modulated, and organized in order to enable reliable and efficient communication in various environments. The standard is designed to work alongside other wireless communication systems and supports both line-of-sight (LOS) and non-line-of-sight (NLOS) communications. This document describes security considerations for short-range optical wireless communications (OWC) using IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) techniques.

Introduction The rapid growth of the Internet of Things (IoT) has led to a significant increase in the number of wireless communication technologies utilized for real-time data collection and monitoring in various industrial domains, such as manufacturing, agriculture, healthcare, transportation, and so on. This trend highlights the importance of wireless communication in facilitating real-time data exchange and analysis, ultimately contributing to enhanced operational efficiency and decision-making processes across different industrial sectors. Optical Wireless Communications (OWC) stands as one of the potential candidates for IoT wireless communication technologies, extensively applied across various industrial domains. The IEEE802.15.7 standard outlines the procedures for establishing bidirectional communications between two OWC devices. Furthermore, IEEE 802.15.7 delineates a comprehensive OWC standard, encompassing features like Visible Light Communication (VLC), Short-Range Communication, Line-of-Sight (LOS) and Non-Line-of-Sight (NLOS) Support, High and Low Data Rates, Energy Efficiency, and Secure Communication. This document describes security considerations for IPv6 over Optical Wireless Communications.

Security Considerations Optical Wireless Communication (OWC) systems introduce unique security concerns due to their reliance on visible or infrared light. Below are key security considerations.

Eavesdropping and Data Interception Since OWC transmissions occur via light, they are more prone to interception if there is an unobstructed line of sight. Mitigation includes using directional communication, encryption of data, and limiting transmission power to reduce signal leakage.

Data Integrity OWC may be affected by environmental factors like obstacles, reflections, or interference, which could corrupt data. Error detection and correction techniques such as checksums or cryptographic hashing are necessary to ensure data integrity.

Denial of Service (DoS) Attacks OWC systems are susceptible to physical blockages or jamming attacks, where an attacker disrupts communication by introducing noise or obstructions. To mitigate this, the system could implement fallback mechanisms or use alternative communication pathways when a block is detected.

Authentication and Access Control Devices connecting to the OWC network must be authenticated to prevent unauthorized access. Using mutual authentication protocols like DTLS (Datagram Transport Layer Security) can secure device communication.

Key Management Secure key management is essential to ensure encryption and integrity. Methods like public-key infrastructure (PKI) or pre-shared keys should be employed to establish trust between OWC nodes.

Energy Efficiency and Security Trade-off Given the low power nature of OWC systems, security protocols should be lightweight to minimize additional energy consumption while still providing sufficient security. Optimized encryption algorithms for resource-constrained environments, such as lightweight ciphers, can be considered.

IANA Considerations None.

References

Acknowledgements We are grateful to the members of the IETF 6lo Working Group.