STIR

STIR Working Group Interim Meeting Date: July 10, 2026 Chairs: Russ Housley, Ben Campbell

## Summary

The STIR working group held an interim meeting to discuss the progress of active drafts, explore two new proposals for identity and trust frameworks (Vesper and Verifiable Voice Protocol), and begin drafting a new charter for the working group. The session emphasized the need to integrate more diverse identifiers—specifically domain names and verifiable credentials—into the STIR ecosystem while maintaining compatibility with the existing SHAKEN framework.

## Key Discussion Points

### WG Document Status: draft-ietf-stir-8588bis

Presenter: Mary Barnes Mary Barnes provided an update on draft-ietf-stir-8588bis. The changes made following the Working Group Last Call (WGLC) were minor. A follow-up last call is currently active and ends on Monday. One editorial nit was identified during the meeting. Mary Barnes will submit a final update once the last call period concludes.

### Vesper

Presenter: Chris Wendt Slides: Vesper Slides

Chris Wendt presented Vesper, a profile of STIR technologies (including delegate certificates, RCD, and Connected Identity) intended to secure telephone identity beyond base SHAKEN.

Identifiers: The proposal focuses on using domain names (Web PKI) as identifiers to bridge the gap between telephone numbers and the entities calling from them.
Discussion: Jon Peterson noted that the core requirement appears to be coupling a new identifier with the PaSSporT that isn't the originator (orig). He questioned how this differs from "third-party RCD" as defined in existing specifications. Chris Wendt clarified that Vesper aims to use the domain trust anchor to enhance trust in the entity's association with a telephone number.
Right to Use (RTU): The draft includes an "RTU token" as a digital alternative to Letters of Authorization (LOA) for telephone number assignments.

### Verifiable Voice Protocol (VVP)

Presenter: Daniel Hardman Slides: VVP slides

Daniel Hardman introduced VVP, which proposes a new PaSSporT type incorporating a kid header (key state link) and an EVD claim (a hyperlink to a "dossier" of evidence).

Accountability: The PaSSporT is signed by an "accountable party" (the entity legally responsible for the call).
Forensics: Unlike standard STIR PaSSports, VVP is designed for long-term verifiability (e.g., for regulatory audits months after the call).
Trust Model: Jon Peterson raised concerns regarding the signing model, specifically whether VVP would require carriers to stop signing PaSSports in favor of enterprises. He noted that in most jurisdictions, carriers remain the accountable parties to regulators.
STIR Integration: Daniel Hardman suggested VVP as a bridge between STIR and the Decentralized Identity (DID) / DPKI communities.

### STIR Recharter Discussion

Lead: Chris Wendt / Chairs Slides: STIR Recharter Discussion

The group discussed the scope for a revised charter.

Proposed Scope: Extensions to support new identifiers, multi-modal communication, and the inclusion of draft-ietf-stir-certificate-transparency as a formal deliverable.
Process: Ben Campbell and Jon Peterson agreed that while the group isn't ready for a final consensus, there is enough common ground to move forward. The group will focus on defining the requirements for "additional identifiers" in the PaSSporT.
Tooling: Russ Housley and Chris Wendt agreed to move the charter wordsmithing to a GitHub repository to allow for collaborative editing before the upcoming meeting in Vienna.

## Decisions and Action Items

Action Item: Mary Barnes to submit an updated version of draft-ietf-stir-8588bis after the last call ends on Monday to address the final editorial nit.
Decision: The working group will continue to exist; there was no support for closing the group.
Action Item: Russ Housley to set up an official STIR Working Group GitHub repository for drafting the new charter.
Action Item: Chris Wendt to upload the current draft of the charter text to the GitHub repository once it is established.

## Next Steps

The working group will use the mailing list and GitHub to refine the charter text.
The goal is to have a near-final charter proposal ready for discussion and potential consensus at IETF 126 in Vienna.

Automatic IETF Minutes