appliedbits
LIBRARY  ·  STIR/SHAKEN LIBRARY ENTRY
Last updated 2026-05-03 drafted

ATIS/SIP Forum IP-NNI Joint Task Force

The ATIS/SIP Forum IP-NNI Joint Task Force is the joint working group that produces the SHAKEN specifications, along with the foundational IP interconnection documents that preceded SHAKEN and the ongoing operational specifications that extend it. Despite the way the work is often discussed in shorthand — “ATIS specs” or “the ATIS IP-NNI committee” — the task force is genuinely joint between two parent organizations. ATIS contributes through its Packet Technologies and Systems Committee (PTSC); the SIP Forum contributes through its Technical Working Group (TWG). Documents are published under both bodies’ identifiers (ATIS-1000063 is also published as SIP Forum TWG-6, for instance). Participation is open to members of either organization.

I co-chair the joint task force. The framing on this page is from the inside.

What the task force is and how it’s structured

The joint task force was formed in January 2014 to define a common SIP profile for IP interconnection between North American service providers, along with a companion document on interconnection routing. The two outputs that resulted — ATIS-1000063 (the IP-NNI Profile) and ATIS-1000062 (IP Interconnection Routing) — addressed those two needs directly.

The joint structure brings together two complementary constituencies. ATIS represents the North American carrier and service provider community; the SIP Forum represents the broader SIP eco-system, including endpoint vendors, software implementers, and protocol contributors. The unique collaboration between the two combines both into very broad participation, and work developed jointly carries weight across both communities.

Original focus: the IP-NNI Profile and IP Interconnection Routing

The task force’s first two outputs were ratified in mid-2015 and remain the foundational documents:

  • ATIS-1000063 (also published as SIP Forum TWG-6) — the IP-NNI Profile. Defines a reference architecture and the on-the-wire protocol and media specifications at interconnection points between SIP service providers. References commonly used IETF, 3GPP, and related industry specifications, and identifies the protocol extensions and capability information needed for all-IP telephony peering.
  • ATIS-1000062 — the IP Interconnection Routing technical report. Documents mechanisms for identifying the preferred IP interconnection point for a given telephone number. Covers multiple approaches: aggregate PSTN-style constructs, all-IP per-TN registries, and hybrid models for the transition period.

The IP-NNI Profile is currently undergoing a revision. The original document predates STIR/SHAKEN, and a decade of operational deployment has surfaced refinements that the revision will incorporate. A revised version will be published when ratified.

Phase 2: SHAKEN

The task force’s second major work product was SHAKEN — the North American operational profile of STIR. When the IETF STIR working group published its core specifications (RFC 8224, RFC 8225, RFC 8226), the question of how to deploy those primitives in carrier networks was deliberately left unanswered, because deployment is jurisdictionally specific. The joint task force took on that work for North America under what was framed at the time as Phase 2 of the IP-NNI effort.

The result is the body of ATIS-1000xxx specifications that operationalize STIR for North American carriers, anchored by ATIS-1000074 (the SHAKEN base specification) and ATIS-1000080 (governance and certificate management). The SHAKEN attestation extension was contributed back to the IETF as RFC 8588, which is the bridge between the joint task force’s operational profile and the IETF protocol suite.

SHAKEN — operational profile and governance covers the framework in depth. The catalog at the bottom of this page lists the joint task force’s published outputs.

Current work

Several efforts are active in the task force as of 2026:

  • IP-NNI Profile update. A revision of ATIS-1000063 is in progress, incorporating refinements identified over a decade of deployment experience and aligning with the post-STIR/SHAKEN reality.
  • Non-negotiated IP interconnection (ALIII). A new effort addressing a structural limitation of the original IP-NNI framework: that interconnection between carriers, while protocol-specified, still requires bilateral negotiation between the parties. ALIII addresses scenarios where service providers should be able to interconnect without that negotiation overhead. The work-in-progress documents may not be publicly accessible until ratified; the ATIS public access portal will reflect publication state.
  • Messaging. A messaging-specific document is in progress, extending the joint task force’s voice-focused work into the text and multimedia messaging domain. Messaging trust has been a steadily growing area of attention, with the IETF STIR work on messaging extensions (RFC 9475) and the GSMA RCS community both addressing related questions; the joint task force’s contribution complements those efforts on the carrier-interconnection side. As with ALIII, the working drafts may not be publicly accessible until published.

The work-in-progress slice is the most fluid part of the task force’s portfolio. For ratified specifications, the catalog below is authoritative.

The published specifications

The catalog below covers the joint task force’s published outputs along with closely-related work from adjacent ATIS PTSC groups (notably the Non-IP Call Authentication Task Force, which has produced TDM-related work that complements SHAKEN). The specifications are organized by topic. Each entry will get its own per-spec page in this library; for now, the catalog establishes the references.

Foundational IP-NNI

Core SHAKEN framework

  • ATIS-1000074.v003 — Standard on Signature-based Handling of Asserted information using toKENs (SHAKEN) — the base specification
  • ATIS-1000080.v006 — SHAKEN Governance Model and Certificate Management
  • ATIS-1000084.v003 — Operational and Management Considerations for SHAKEN STI Certification Authorities and Policy Administrators
  • ATIS-1000088 — Framework for SHAKEN Attestation and Origination Identifier

Display and rich call data

  • ATIS-1000081 — Framework for Display of Verified Caller
  • ATIS-1000094.v002 — SHAKEN: Calling Name and Rich Call Data Handling Procedures (complements RFC 9795; supplementary RFC 9796 covers SIP Call-Info delivery over the UNI)

Specific call and customer scenarios

  • ATIS-1000085.v003 — SHAKEN Support of “div” PASSporT (operational profile of RFC 8946)
  • ATIS-1000089.v002 — Full Attestation Alternatives for Enterprises and Business Entities with Multi-Homing
  • ATIS-1000092.v002 — SHAKEN: Delegate Certificates (operational profile of RFC 9060)
  • ATIS-1000093 — Toll-Free Numbers in the SHAKEN Framework
  • ATIS-1000099 — Robocall Call Blocking Notification

Cross-border and international

  • ATIS-1000087.v002 — Mechanism for Initial Cross-Border SHAKEN (includes CB-TACL coordination)
  • ATIS-1000091 — Mechanism for International SHAKEN

TDM and non-IP

Most of these come from the Non-IP Call Authentication Task Force (NIPCA-TF), an adjacent ATIS PTSC group whose work complements the joint task force’s IP-focused output.

  • ATIS-1000095.v002 — Extending STIR/SHAKEN over TDM
  • ATIS-1000096 — SHAKEN: Out-of-Band PASSporT Transmission Involving TDM Networks
  • ATIS-1000097.v004 — Alternatives for Caller Authentication for Non-IP Traffic
  • ATIS-1000105 — SHAKEN: Out-of-Band PASSporT Transmission Between Service Providers that Interconnect using TDM
  • ATIS-1000106.v002 — Viability of Non-IP Call Authentication Standards
  • ATIS-1000107 — STI-CPS Discovery for Out-of-Band PASSporT Transmission Involving TDM Networks

Resource priority and emergency services

  • ATIS-1000078.v002 — NS/EP Priority Service SIP RPH Signing and Verification (operational counterpart to RFC 8443)
  • ATIS-1000098 — SIP RPH and Priority Header Signing for Emergency Calling (operational counterpart to RFC 9027)

Implementation and adjacent

  • ATIS-1000082.v002 — SHAKEN APIs for a Centralized Signing and Signature Validation Server
  • ATIS-1000101 — SMS Unwanted Message Mitigation Landscape

A note on versions and access

ATIS specifications go through revisions. Version notation appears in the document number itself (ATIS-1000074.v003 is the third revision of ATIS-1000074). The latest version supersedes earlier versions; the list above reflects the latest published version as of this page’s last update. The ATIS public access portal is authoritative for the current version of any ratified document. SIP Forum members can also access joint task force outputs through the SIP Forum’s website at no charge.

Per-spec pages will fill in detail individually as they’re written. Where a spec maps directly to an IETF RFC (1000092 ↔ 9060 for delegation, 1000085 ↔ 8946 for diversion, 1000094 ↔ 9795 for RCD — with supplementary 9796 covering SIP-side delivery — etc.), the per-spec page will surface that mapping.