draft-cruzgonzalez-ipoac-dns-00 - DNS over Avian Carriers (DoAC)
Skip to main content
Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.<br>Please enable Javascript for full functionality.
DNS over Avian Carriers (DoAC)
draft-cruzgonzalez-ipoac-dns-00
Status
Email expansions
History
Versions:
This document is an Internet-Draft (I-D).<br>Anyone may submit an I-D to the IETF.<br>This I-D is not endorsed by the IETF and has no formal standing in the<br>IETF standards process.
Document<br>Type
Active Internet-Draft<br>(individual)
Author
Christian Elías Cruz González
Last updated
2026-06-08
RFC stream
(None)
Intended RFC status
(None)
Formats
txt
html
xml
htmlized
bibtex
bibxml
Stream
Stream state
(No stream defined)
Consensus boilerplate
Unknown
RFC Editor Note
(None)
IESG
IESG state
I-D Exists
Telechat date
(None)
Responsible AD
(None)
Send notices to
(None)
Email authors
IPR
References
Referenced by
Nits
Search email archive
draft-cruzgonzalez-ipoac-dns-00
Network Working Group C. E. Cruz Gonzalez<br>Internet-Draft Independent Avian Infrastructure Researcher<br>Intended status: Informational 8 June 2026<br>Expires: 10 December 2026
DNS over Avian Carriers (DoAC)<br>draft-cruzgonzalez-ipoac-dns-00
Abstract
The Domain Name System (DNS) was designed under the implicit<br>assumption that the underlying transport would be fast, reliable, and<br>free from predation. This document specifies DNS over Avian Carriers<br>(DoAC), enabling hostname resolution for networks operating over<br>avian-carrier infrastructure. Without DoAC, operators of avian-<br>carrier networks are forced to hardcode IP addresses directly onto<br>their Carriers, a practice that does not scale and is widely<br>considered inelegant.
Status of This Memo
This Internet-Draft is submitted in full conformance with the<br>provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering<br>Task Force (IETF). Note that other groups may also distribute<br>working documents as Internet-Drafts. The list of current Internet-<br>Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months<br>and may be updated, replaced, or obsoleted by other documents at any<br>time. It is inappropriate to use Internet-Drafts as reference<br>material or to cite them other than as "work in progress."
This Internet-Draft will expire on 10 December 2026.
Copyright Notice
Copyright (c) 2026 IETF Trust and the persons identified as the<br>document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal<br>Provisions Relating to IETF Documents (https://trustee.ietf.org/<br>license-info) in effect on the date of publication of this document.<br>Please review these documents carefully, as they describe your rights<br>and restrictions with respect to this document.
Cruz Gonzalez Expires 10 December 2026 [Page 1]<br>Internet-Draft DoAC June 2026
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2<br>2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3<br>3. Message Format . . . . . . . . . . . . . . . . . . . . . . . 4<br>4. The AA Resource Record . . . . . . . . . . . . . . . . . . . 4<br>5. The Bootstrapping Problem . . . . . . . . . . . . . . . . . . 5<br>5.1. The Pigeon of Last Resort (PoLR) . . . . . . . . . . . . 6<br>5.2. Resolver Discovery Without Prior State . . . . . . . . . 6<br>6. Retransmission Behavior . . . . . . . . . . . . . . . . . . . 6<br>7. Negative Caching and SERVFAIL Semantics . . . . . . . . . . . 7<br>8. DNSSEC Considerations . . . . . . . . . . . . . . . . . . . . 7<br>9. Resolution Example . . . . . . . . . . . . . . . . . . . . . 8<br>10. Operational Considerations . . . . . . . . . . . . . . . . . 8<br>11. Security Considerations . . . . . . . . . . . . . . . . . . . 9<br>11.1. Hawk-in-the-Middle (HitM) Attacks . . . . . . . . . . . 9<br>11.2. Pigeon Spoofing and Plumage-Based Authentication . . . . 10<br>11.3. Loft Hijacking . . . . . . . . . . . . . . . . . . . . . 10<br>11.4. Denial of Flight (DoF) . . . . . . . . . . . . . . . . . 10<br>11.5. Migration Season Routing Anomalies . . . . . . . . . . . 11<br>11.6. The Hungry Cat as a Physical Layer Threat . . . . . . . 11<br>11.7. Replay Attacks via Taxidermied Carrier . . . . . . . . . 11<br>11.8. Zone Signing Key Compromise via Pigeon Theft . . . . . . 12<br>11.9. Covert Feather Channel . . . . . . . . . . . . . . . . . 12<br>12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12<br>13. References . . . . . . . . . . . . . . . . . . . . . . . . . 13<br>13.1. Normative References . . . . . . . . . . . . . . . . . . 13<br>Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 14<br>Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
[RFC1149] established a framework for the transmission of IP<br>datagrams using homing pigeons. Subsequent documents extended this<br>work to include Quality of Service [RFC2549] and IPv6...