RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc9795.html

Published

2025-07-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust Legal Provisions (BCP 78); no-redistribution; short excerpts and locators only

Source notes citing this source

• RFC 9795 defines an optional crn claim that carries a single string describing the reason for the call. in context
• RFC 9795 makes the jcd and jcl keys mutually exclusive, so a jCard is either inline or referenced by URL but not both. in context
• Under RFC 9795 the authentication service takes nam from the SIP From display-name by default; if the nam it generates differs from that display-name it must use the full PASSporT form rather than the compact form. in context
• Under RFC 9795 a PASSporT whose header carries ppt rcd must contain at least one rcd or crn claim. in context
• RFC 9795 defines a JWT claim named rcd whose value is a JSON object holding one or more key-value pairs of caller information. in context
• 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. in context
• In RFC 9795 the nam key of the rcd claim is mandatory and carries the display name, set to an empty string when there is no name. in context
• RFC 9795 lists the optional rcd keys as apn (alternate presentation number), icn (HTTPS URL of an image), jcd (inline jCard) and jcl (HTTPS URL of a jCard). in context
• RFC 9795 leaves the UAS's handling of a received rcd claim largely to implementation policy and does not make rendering mandatory. in context
• RFC 9795 defines an rcdi claim of cryptographic digests addressed by JSON pointer; it is required when the rcd claim contains URI references, and SHA-256, SHA-384 and SHA-512 must be supported. in context
• RFC 9795, the PASSporT extension for Rich Call Data, was published in July 2025 on the Standards Track, authored by C. Wendt and J. Peterson. in context

Cite this source record

APA

WarmTransfer. (2025, July 1). RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-9795-passport-rcd

BibTeX

@misc{warmtransfer-rfc-9795-passport-rcd,
  title  = {RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-9795-passport-rcd},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}