<?xml version='1.0' encoding='utf-8'?>
<?xml-model href="rfc7991bis.rnc"?>
<!DOCTYPE rfc [
        <!ENTITY nbsp    "&#160;">
        <!ENTITY zwsp   "&#8203;">
        <!ENTITY nbhy   "&#8209;">
        <!ENTITY wj     "&#8288;">
        ]>
<rfc
        xmlns:xi="http://www.w3.org/2001/XInclude"
        category="info"
        docName="draft-zhixin-tech-ip-oac-drone-00"
        ipr="trust200902"
        obsoletes=""
        updates=""
        submissionType="IETF"
        xml:lang="en"
        version="3">
    <front>
        <title abbrev="IPoAC-Drone">Drone-Based IP over Avian Carriers</title>
        <author fullname="YangWeichen" initials="Y." role="editor" surname="Yang">
            <organization>Zhixin Technology Co., Ltd. (Kercore)</organization>
            <address>
                <postal>
                    <region>ShiJiazhuang</region>
                    <country>China</country>
                </postal>
                <email>hbzx@kercore.com.cn</email>
                <uri>http://www.kercore.com.cn</uri>
            </address>
        </author>

        <date month="April" day="5" year="2025"/>
        <keyword>UAV, IPoAC, Drone Communication, Delay/Disruption Tolerant Network, Emergency Communication, Rural Networking, Disaster Recovery, Data Transmission Protocol, Autonomous Drones, IPv6-Compatible Network</keyword>
        <abstract>
            <t>This document proposes an experimental protocol, IP over Avian Carriers using Drones (IPoAC-Drone), as
                an extension to the classic IPoAC (RFC 1149) for modern low-altitude economy applications. It describes
                how UAVs (Unmanned Aerial Vehicles) can be utilized as network carriers to provide a store-and-forward
                data transmission model. The document covers protocol design, operational considerations, and potential
                applications, including emergency communication, rural networking, and disaster recovery.</t>
        </abstract>
    </front>

    <middle>
        <section>
            <name>Introduction</name>
            <t>
                IPoAC (RFC 1149) introduced a method for transmitting IP packets via avian carriers (pigeons). Later,
                RFC 2549 improved its reliability with Quality of Service (QoS). However, the limited payload capacity
                and unpredictable behavior of biological carriers make them impractical for modern high-speed
                communication.
                The advancement of drone technology enables a more reliable and scalable implementation of the IPoAC
                concept. IPoAC-Drone replaces avian carriers with autonomous UAVs, providing a programmable,
                high-bandwidth, and predictable alternative.
            </t>
        </section>

        <section>
            <name>Protocol Overview</name>
            <section>
                <name>Transmission Mechanism</name>
                <ol>
                    <li>Data packets are encapsulated into storage devices (e.g., SSD, microSD, or encrypted flash
                        drives) attached to UAVs.
                    </li>
                    <li>UAVs operate on pre-defined flight paths to relay packets between nodes.</li>
                    <li>Upon reaching the destination, UAVs transfer the data to ground stations via wireless or physical
                        offloading.
                    </li>
                    <li>Acknowledgments (ACKs) are either relayed back via the same UAVs or an alternative communication
                        channel.
                    </li>
                </ol>
            </section>

            <section>
                <name>Addressing &amp; Routing</name>
                <ol>
                    <li>IPv6-Compatible Headers: UAVs are assigned virtual IP addresses for tracking.</li>
                    <li>Routing Protocol: Modified Delay/Disruption Tolerant Network (DTN) approach with a scheduled
                        delivery model.
                    </li>
                    <li>Multi-hop Support: Drones act as relays between ground stations, ensuring wider network
                        coverage.
                    </li>
                </ol>
            </section>
        </section>

        <section>
            <name>Implementation Considerations</name>
            <section>
                <name>Drone Specifications</name>
                <ol>
                    <li>Payload Capacity: Sufficient to carry lightweight storage devices.</li>
                    <li>Flight Range: Dependent on battery efficiency and weight distribution.</li>
                    <li>Communication Interface: Wi-Fi, LoRa, 5G, or direct physical offloading.</li>
                    <li>Autonomous Navigation: Pre-defined routes with GPS &amp; AI-based adjustments.</li>
                </ol>
            </section>

            <section>
                <name>Security Concerns</name>
                <ol>
                    <li>Data Encryption: AES-256 encryption to prevent unauthorized access.</li>
                    <li>Tamper-Proofing: Secure storage compartments for physical data integrity.</li>
                    <li>Access Control: Only authorized stations can read/write data.</li>
                </ol>
            </section>

            <section>
                <name>Network Performance</name>
                <ol>
                    <li>Latency: Variable based on drone speed and travel distance.</li>
                    <li>Packet Loss: Mitigated by redundant UAVs or re-transmission policies.</li>
                    <li>Throughput: Higher than traditional IPoAC, but constrained by drone storage limits.</li>
                </ol>
            </section>
        </section>

        <section>
            <name>Applications</name>
            <section>
                <name>Emergency &amp; Disaster Recovery</name>
                <t>UAVs can establish a temporary communication network where traditional infrastructure is damaged.</t>
            </section>

            <section>
                <name>Rural Internet Deployment</name>
                <t>Drones can serve as periodic data carriers between remote villages and urban data centers.</t>
            </section>

            <section>
                <name>Military &amp; Secure Data Transport</name>
                <t>In high-risk areas, IPoAC-Drone provides a secure and physically isolated communication method.</t>
            </section>
        </section>

        <section>
            <name>Conclusion</name>
            <t>IPoAC-Drone offers a modernized approach to packet transport in areas where conventional networking is
                unavailable. While latency remains high, its predictable routing, security enhancements, and scalability
                make it a viable solution for specialized use cases.
            </t>
            <t>Future work includes optimizing flight paths for reduced delays, AI-driven adaptive routing, and hybrid
                networks integrating UAVs with existing infrastructure.
            </t>
        </section>

        <section>
            <name>IANA Considerations</name>
            <t>This document does not request any changes to IANA registries.</t>
        </section>

        <section>
            <name>Security Considerations</name>
            <ol>
                <li>Data Integrity: Storage devices must implement cryptographic verification.</li>
                <li>Physical Interception: Drones must employ anti-tampering mechanisms.</li>
                <li>Interference &amp; Jamming: UAVs should support frequency-hopping for secure communication.</li>
            </ol>
        </section>

    </middle>

    <back>
        <references>
            <name>Normative References</name>
            <reference anchor="RFC1149">
                <front>
                    <title>Standard for the transmission of IP datagrams on avian carriers</title>
                    <author initials="RFC" surname="1149">
                        <organization/>
                    </author>
                    <date year="1990" month="April"/>
                </front>
            </reference>
            <reference anchor="RFC2549">
                <front>
                    <title>IPoAC with QoS</title>
                    <author initials="RFC" surname="2549">
                        <organization/>
                    </author>
                    <date year="1999" month="March"/>
                </front>
            </reference>
            <reference anchor="RFC4838">
                <front>
                    <title>Delay-Tolerant Networking Architecture</title>
                    <author initials="RFC" surname="4838">
                        <organization/>
                    </author>
                    <date year="2007" month="April"/>
                </front>
            </reference>
            <reference anchor="IEEE2023">
                <front>
                    <title>UAV-based Communication Networks: A Survey</title>
                    <author initials="IEEE" surname="2023">
                        <organization/>
                    </author>
                    <date year="2023"/>
                </front>
            </reference>
        </references>
    </back>
</rfc>
