Source note · Branded calling and CNAM delivery
RFC 9795 lets an authentication service either send rcd in its own PASSporT with a separate Identity header or add rcd claims directly to another extension PASSporT such as shaken; verifiers that support only the base extension ignore the extra claims.
Checked 2026-09-24
- Vendor
- IETF
- Product
- STIR PASSporT
- Subsystem
- rich-call-data
- Deployment
- carrier-network
- Region
- not restricted
- Release range
- RFC 9795
- Checked
- 2026-09-24
Sources
- RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data — IETF / RFC Editor · tier 1 standards and regulators · Section 13 (using rcd with other PASSporT extensions)
Cite this note
APA
WarmTransfer. (2026, September 24). Branded calling and CNAM delivery: source note branded-calling-cnam-rcd-in-shaken-passport. WarmTransfer. https://warmtransfer.net/knowledge/claims/branded-calling-cnam-rcd-in-shaken-passport
BibTeX
@misc{warmtransfer-claim-branded-calling-cnam-rcd-in-shaken-passport,
title = {Branded calling and CNAM delivery: source note branded-calling-cnam-rcd-in-shaken-passport},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/branded-calling-cnam-rcd-in-shaken-passport},
note = {Source note branded-calling-cnam-rcd-in-shaken-passport, checked 2026-09-24}
}