<?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-03" 
	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="20" month="October" 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 have unique security considerations arising from their directional and line-of-sight (LOS) or non-line-of-sight (NLOS) operation and from the physical characteristics of optical media. These characteristics may lead to signal leakage, environmental interference, fragmentation-related vulnerabilities due to small-MTU PHYs, and limited support for multicast transmission.</t>
	<t>This section summarizes the main security considerations for IPv6 transmission over OWC, particularly in 6LoWPAN-based deployments using IEEE 802.15.7.</t>	
	<section>
		<name>Eavesdropping and Data Interception</name>		
		<t>OWC communications may be susceptible to interception when the line-of-sight (LOS) or non-line-of-sight (NLOS) optical path is unobstructed or partially reflective. Signal leakage through transparent or reflective surfaces can expose transmitted data to unauthorized observation.</t>
		<t>Mitigation techniques include the use of directional transmission, end-to-end encryption, and optimized transmission power to reduce unintended optical exposure. Beam steering, adaptive modulation, and narrow beam divergence can further enhance confidentiality by limiting signal spread beyond the intended receiver's field of view.</t>
	</section>
	<section>
		<name>Denial of Service (DoS) Attacks</name>		
		<t>OWC networks may experience service disruption caused by high-intensity optical interference, physical obstruction, or excessive background illumination. Such conditions can reduce link availability or, in severe cases, lead to a denial of service.</t>
		<t>To maintain network availability, OWC devices should detect abnormal interference, adjust modulation parameters, or reroute traffic through alternate multi-hop paths when optical links are impaired.</t>
	</section>
	<section>
		<name>Authentication and Access Control</name>		
		<t>Unauthorized participation or message manipulation within an OWC network can compromise network trust and stability. Mutual authentication using IPv6-based Datagram Transport Layer Security [RFC9147] and device identity verification based on IEEE 802.15.7 link-layer addresses should be implemented to ensure that only legitimate devices can join and exchange IPv6 traffic.</t>
		<t>Address registration and Neighbor Discovery procedures must be protected against spoofing, replay, and unauthorized modification. Proof of address ownership and link-layer binding are recommended in multi-hop topologies to prevent address hijacking or impersonation.</t>
	</section>
	<section>
		<name>Energy Efficiency and Security Trade-off</name>		
		<t>OWC devices often operate under strict energy constraints, so security mechanisms must minimize computational and transmission overhead while maintaining the required protection level.</t>
		<t>Lightweight cryptographic protocols, such as authenticated encryption schemes and reduced-overhead DTLS 1.3 handshakes [RFC9147], are recommended for low-power microcontrollers to reduce processing cost without compromising data confidentiality or integrity.</t>
		<t>When designing for constrained nodes, the general principles for limited-resource environments should be applied so that protocol complexity does not exceed available power or processing capacity. Adaptive adjustment of security parameters, including encryption strength or key lifetime, can help maintain an effective balance between energy efficiency and security robustness throughout network operation.</t>
	</section>	
	<section>
		<name>Secure Routing in Multi-hop Networks</name>		
		<t>In multi-hop OWC networks, the integrity and authenticity of routing information must be preserved to ensure reliable data forwarding. Attacks on intermediate nodes or routing control messages can cause packet loss, route manipulation, or network partitioning. Routing protocols should authenticate participating nodes and validate routing updates to prevent the injection of false routes or unauthorized relays.</t>
		<t>OWC devices are expected to apply lightweight security mechanisms that verify routing information while minimizing processing and energy overhead.</t>
	</section>	
	<section>
		<name>RF/Optical Interference and Jamming</name>	
		<t>Although OWC operates primarily in the optical domain, practical deployments often coexist with RF-based wireless systems in the same environment.</t>
		<t>In such mixed conditions, high-intensity optical signals or strong RF emissions may interfere with OWC transceivers, causing service disruption or degraded performance. OWC systems need mechanisms to detect and respond to abnormal interference levels-such as adaptive modulation control, alternative routing, or temporary link isolation-to maintain network availability.</t>
		<t>When interference is detected, recovery procedures should restore normal operation without compromising ongoing secure sessions or data integrity.</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>

