Source note · Branded calling and CNAM delivery
RFC 9795 leaves the UAS's handling of a received rcd claim largely to implementation policy and does not make rendering mandatory.
Checked 2026-09-24
In most cases, implementations would render this calling party name information to the user while alerting.
- Vendor
- IETF
- Product
- STIR PASSporT
- Subsystem
- verification-service
- 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 12.2 (verification service behaviour)
Cite this note
APA
WarmTransfer. (2026, September 24). Branded calling and CNAM delivery: source note branded-calling-cnam-rcd-render-local-policy. WarmTransfer. https://warmtransfer.net/knowledge/claims/branded-calling-cnam-rcd-render-local-policy
BibTeX
@misc{warmtransfer-claim-branded-calling-cnam-rcd-render-local-policy,
title = {Branded calling and CNAM delivery: source note branded-calling-cnam-rcd-render-local-policy},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/branded-calling-cnam-rcd-render-local-policy},
note = {Source note branded-calling-cnam-rcd-render-local-policy, checked 2026-09-24}
}