appliedbits
LIBRARY LIBRARY TOPIC
Last updated 2026-05-06 29 entries

IETF — RFCs and active drafts

This page is the catalog of IETF documents referenced across the library — published RFCs and active working-group drafts. Each document has its own page; the topic pages elsewhere on the site (STIR, SHAKEN, SIP, ENUM, ACME, vCon, and others) link here as the canonical home for what each document specifies.

The list is curated, not exhaustive. A document earns a place here when it’s referenced in a topic page somewhere on the site. The topic pages provide framing — what this document does for the context that matters there. The per-document pages provide depth — what the document actually says, who authored it, and which design choices are worth understanding.

Where I am a co-author of a document, the per-document page says so explicitly. Authority claims are positional: I’m describing the document I helped write, not summarizing from outside.

STIR family

The Secure Telephone Identity Revisited working group’s output — the cryptographic protocol for caller authentication and its extensions. For framing on how these documents relate to each other and what order to read them in, see STIR and SHAKEN.

Published RFCs

Active working group drafts

VESPER

VESPER (Verifiable STI Presentation and Evidence for RTU) is being developed across a coordinated set of individual drafts at the IETF. The conceptual home for VESPER on this site is the VESPER topic page — what VESPER is, why it’s structured the way it is, the four roles, the certificate profile, the relationship to STIR/SHAKEN, and the ten use cases all live there. The per-draft pages below cover what’s specific to each individual draft (current revision, status in the IETF process, technical scope, what changed in each iteration). The sliwa CPS URI extension is grouped here because it’s the discovery substrate that VESPER OOB consumes.

ACME and certificate issuance

The Automated Certificate Management Environment family. ACME shows up in STIR/SHAKEN because the authority-token extensions are how SHAKEN certificate authorities prove a delegate’s authority over a specific number range at issuance time. The same documents apply broadly to other ACME-style issuance flows.

SIP

The session-initiation foundation underneath everything else on this site. See SIP for topical framing.

ENUM and DNS

The DNS-based mappings used for telephone-number-to-URI resolution and emerging agent-identity discovery work. See ENUM and DNS and domain trust for topical framing.

  • RFC 3761 — The E.164 to URI DDDS Application (page forthcoming, obsoleted by 6116)
  • RFC 6116 — The E.164 to URI DDDS Application (ENUM) (page forthcoming)
  • RFC 8484 — DNS Queries over HTTPS (DoH) (page forthcoming)

vCon (Virtualized Conversations)

The vCon working group’s output — a JSON container format for conversation data, with metadata about participants, content, analysis, and provenance. I co-chair this working group with Brian Rosen. See vCon for topical framing.

The working group has not yet produced any published RFCs; all documents are active or recently-active drafts.

Active working group drafts

  • draft-ietf-vcon-vcon-core — The JSON format for vCon (the core specification) (active working group document, currently -02, heading toward WG Last Call)
  • draft-ietf-vcon-overview — vCon Overview (active working group document, Informational, currently -01)
  • draft-ietf-vcon-cc-extension — vCon Contact Center Extension (WG document, currently -01, technically expired pending refresh)
  • draft-ietf-vcon-privacy-primer — Privacy Primer for vCon Developers (page forthcoming — recently expired, expected to revive)
  • draft-ietf-vcon-mimi-messages — vCon for MIMI Messages (page forthcoming — recently expired, expected to revive)

A note on the “page forthcoming” markers

Many of the documents listed here are placeholders pending their own per-document page. The structure of this catalog is what’s being established first; pages fill in incrementally. The list is expected to grow and shrink as the topical coverage of the site matures — documents drop off when no topic page references them anymore, and new ones appear as new work is integrated.

In this section