<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc 
	submissionType="IETF" 
	category="info" 
	docName="draft-choi-6lo-owc-security-01" 
	ipr="trust200902" 
	obsoletes="" 
	updates="" 
	xml:lang="en" 
	tocInclude="true" 
	tocDepth="4" 
	symRefs="true" 
	sortRefs="true" 
	version="3">

<front>
	
	<title abbrev="Security for IPv6 over OWC">Security considerations for IPv6 Packets over Short-Range Optical Wireless Communications</title>
	
	<author fullname="Munhwan Choi" role="editor" initials="M." surname="Choi">
		<organization abbrev="ETRI">Electronics and Telecommunications Research Institute</organization>
			<address>
			<postal>
				<street>218 Gajeongno, Yuseung-gu</street>
				<city>Daejeon</city>
				<code>34129</code>
				<country>South Korea</country>
			</postal>
			<phone>+82 42 860 6539</phone>
			<email>mhchoi@etri.re.kr</email>
			</address>
	</author>
	<author fullname="Younghwan Choi" initials="Y." surname="Choi">
		<organization abbrev="ETRI">Electronics and Telecommunications Research Institute</organization>
			<address>
			<postal>
				<street>218 Gajeongno, Yuseung-gu</street>
				<city>Daejeon</city>
				<code>34129</code>
				<country>South Korea</country>
			</postal>
			<phone>+82 42 860 1429</phone>
			<email>yhc@etri.re.kr</email>
			</address>
	</author>

	<date day="26" month="February" year="2025"/>
	<area>int</area>
	<workgroup>6lo</workgroup>
	
	<keyword>Short-Range Optical Wireless Communications</keyword>
	<keyword>OWC</keyword>
	<keyword>IEEE 802.15.7</keyword>
	<keyword>6LowPAN</keyword>
	<keyword>IPv6</keyword>
	<keyword>Adaptation Layer</keyword>
	<keyword>IoT</keyword>
	<keyword>Internet of Things</keyword>
	<keyword>Security considerations</keyword>

	<abstract>
		<t>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.</t>
	</abstract>

</front>
  
<middle>

<!-- Introduction --> 
	<section numbered="true" toc="default">
		<name>Introduction</name>
		<t>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.</t>
		<t>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.</t>
		<t>This document describes security considerations for IPv6 over Optical Wireless Communications.</t>
	</section>

<!-- Conventions and Terminology 
	<section numbered="true" toc="default">
		<name>Conventions and Terminology</name>
		<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
	</section>
--> 

<!-- Security Considerations -->
<section numbered="true" toc="default">
	<name>Security Considerations</name>
	<t>Optical Wireless Communication (OWC) systems introduce unique security concerns due to their reliance on visible or infrared light. Below are key security considerations.</t>
	<section>
		<name>Eavesdropping and Data Interception</name>		
		<t>Since OWC relies on optical signals, communications can be susceptible to interception when the line-of-sight (LOS) path is unobstructed. Mitigation techniques include directional communication, encryption of data, and limiting transmission power to reduce signal leakage. Additionally, employing beam steering technologies, narrow optical beam divergence, and robust end-to-end encryption at the IPv6 adaptation layer are recommended to further enhance confidentiality.</t>
	</section>
	<section>
		<name>Data Integrity</name>		
		<t>Environmental factors such as ambient light interference, obstacles, multipath reflections, and LED modulation inconsistencies can degrade OWC data integrity. Strong error detection and correction mechanisms at the PHY layer combined with IPv6-level integrity protection are recommended. In addition, to ensure the integrity of header-compressed IPv6 packets, the SCHC compression context should be securely managed and protected from unauthorized modifications or corruptions.
</t>
	</section>
	<section>
		<name>Denial of Service (DoS) Attacks</name>		
		<t>OWC can experience physical jamming attacks via high-intensity optical noise or physical obstruction, potentially disrupting communications. Mitigations include incorporating PHY-layer interference detection mechanisms and adaptive modulation schemes, as well as implementing network-layer redundancy through alternative IPv6 routing paths via multi-hop OWC topologies.</t>
	</section>
	<section>
		<name>Authentication and Access Control</name>		
		<t>Unauthorized OWC device access can lead to unauthorized data transmissions or network compromise. Mutual authentication through IPv6-based Datagram Transport Layer Security [RFC9147] and device identity verification utilizing IEEE 802.15.7 link-layer addresses combined with IPv6 interface identifiers are recommended.</t>
	</section>
	<section>
		<name>Energy Efficiency and Security Trade-off</name>		
		<t>Due to limited energy resources in OWC devices, security mechanisms must minimize energy overhead. Lightweight cryptographic protocols optimized for low-power microcontrollers (e.g., lightweight authenticated encryption schemes, minimal DTLS[RFC9147] handshake overhead) and adaptive security levels depending on the device's operational context should be considered.</t>
	</section>	
	<section>
		<name>Secure Routing in Multi-hop Networks</name>		
		<t>In multi-hop OWC networks, the integrity and authenticity of routing information is essential. Attacks on intermediate nodes or routing messages can compromise data delivery, causing eavesdropping, packet dropping, or routing loops. Therefore, secure routing protocols, such as secure extensions of RPL ([RFC6550] security mechanisms), and node authentication methods must be implemented to ensure reliable and trustworthy communication paths.</t>
	</section>	
</section>

<!-- IANA Considerations -->
<section anchor="IANA" numbered="true" toc="default">
	<name>IANA Considerations</name>
	<t>None.</t>
</section>

</middle>

<back>
<!-- References -->
<references title='Normative References' anchor="sec-normative-references">
	<name>References</name>
        <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
        <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml"?>
	<!--
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6282.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6775.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6550.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4944.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4086.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4919.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4862.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4861.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7136.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7217.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7400.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8505.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8201.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8724.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7668.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9147.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-schc-architecture.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-6lo-schc-15dot4.xml"/>
	-->
</references>

<!-- Acknowledgements -->
<section anchor="Acknowledgements" numbered="false" toc="default">
	<name>Acknowledgements</name>
	<t>We are grateful to the members of the IETF 6lo Working Group.</t>
<!--      <t><contact fullname="Michael Richardson"/>, <contact fullname="Suresh Krishnan"/>, <contact fullname="Pascal Thubert"/>, <contact fullname="Carsten Bormann"/>, <contact fullname="Alexandru Petrescu"/>, <contact fullname="James Woodyatt"/>, <contact fullname="Dave Thaler"/>, <contact fullname="Samita Chakrabarti"/>, <contact fullname="Gabriel Montenegro"/>, <contact fullname="Erik Kline"/>, and <contact fullname="Carles Gomez Montenegro"/> have provided valuable feedback for this document.</t> -->
</section>

</back>
</rfc>

