When a hurricane knocks out cell towers, a coup paralyzes a capital, or a stadium full of people simultaneously dial out after a bombing, ordinary phone calls fail with "all circuits busy." Yet the FEMA coordinator, the White House staffer, and the hospital chief still get through. RFC 4412 is the plumbing that makes that work in the SIP era.

The RFC defines two new SIP header fields: Resource-Priority and Accept-Resource-Priority. They carry a namespace (which authority's priority scheme is in use) and a priority value within it. A call carrying Resource-Priority: ets.0 is claiming the highest priority under the U.S. Emergency Telecommunications Service. A proxy that supports it must give that INVITE preferential treatment when allocating bandwidth, trunk capacity, or processor cycles — and, crucially, may preempt ordinary calls already in progress.

The named namespaces are the interesting part:

• dsn — Defense Switched Network (US DoD)
• drsn — Defense Red Switched Network (the classified/nuclear-command side)
• q735 — ITU-T's international MLPP scheme
• ets — civilian emergency telecom (FEMA, GETS calling cards)
• wps — Wireless Priority Service (the cellular analog)

Each namespace has its own ordered priority levels (typically five, from routine through flash-override). The MLPP — Multi-Level Precedence and Preemption — concept dates back to AUTOVON in the 1960s, where a senior officer's "flash override" call would literally drop a colonel's existing conversation. RFC 4412 ports that 1960s Cold War semantic onto modern SIP.

Key design decisions:

• Namespaces, not a global scale. A DoD "priority" doesn't mean the same thing as a civilian "priority," and the authors refused to flatten them. A proxy advertises which namespaces it understands via Accept-Resource-Priority; unknown namespaces must be rejected with 417, not silently downgraded.
• Authentication is out of scope. The RFC defines the syntax and the proxy behavior but punts the question of "is this caller actually entitled to claim ets.0?" to other mechanisms — typically S/MIME, TLS-authenticated peers, or out-of-band provisioning. This is why the actual GETS deployment relies on PIN-authenticated calling cards layered on top.
• Preemption is policy, not protocol. RFC 4412 says a higher-priority call may preempt a lower one; it deliberately doesn't mandate when. Carriers tune that knob.

Why it's still relevant in 2026: as the PSTN finishes its long death and TDM trunks get decommissioned, every government MLPP feature has to be re-implemented on top of SIP. RFC 4412 is the substrate. It's also why your VoIP PBX vendor's data sheet has a "GETS/WPS compliant" checkbox you've probably never thought about. And the same mechanism gets reused for non-emergency QoS: some enterprise deployments use private namespaces to mark CEO calls or trading-floor lines as preempt-capable.

The quirky footnote: RFC 4412 is one of very few IETF specs that explicitly contemplates nuclear command and control as a use case (via drsn). It sits in a strange corner of the standards landscape where Henning Schulzrinne's SIP research collides with USSTRATCOM's continuity-of-government requirements.