| rfc9795v2.txt | rfc9795.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) C. Wendt | Internet Engineering Task Force (IETF) C. Wendt | |||
| Request for Comments: 9795 Somos Inc. | Request for Comments: 9795 Somos Inc. | |||
| Category: Standards Track J. Peterson | Category: Standards Track J. Peterson | |||
| ISSN: 2070-1721 Neustar Inc. | ISSN: 2070-1721 TransUnion | |||
| June 2025 | July 2025 | |||
| Personal Assertion Token (PASSporT) Extension for Rich Call Data | Personal Assertion Token (PASSporT) Extension for Rich Call Data | |||
| Abstract | Abstract | |||
| This document extends Personal Assertion Token (PASSporT), a token | This document extends Personal Assertion Token (PASSporT), a token | |||
| for conveying cryptographically signed call information about | for conveying cryptographically signed call information about | |||
| personal communications, to include rich metadata about a call and | personal communications, to include rich metadata about a call and | |||
| caller that can be signed and integrity protected, transmitted, and | caller that can be signed and integrity protected, transmitted, and | |||
| subsequently rendered to the called party. This framework is | subsequently rendered to the called party. This framework is | |||
| skipping to change at line 1183 ¶ | skipping to change at line 1183 ¶ | |||
| service MUST additionally compare the string value of the "rcd" claim | service MUST additionally compare the string value of the "rcd" claim | |||
| "nam" key value with the From header field value or the preferred | "nam" key value with the From header field value or the preferred | |||
| value. The preferred value depends on local policy of the SIP | value. The preferred value depends on local policy of the SIP | |||
| network technique that conveys the display name string through a | network technique that conveys the display name string through a | |||
| field other than the From header field to interoperate with this | field other than the From header field to interoperate with this | |||
| specification (e.g., P-Asserted-Identity) as discussed in [RFC8224]. | specification (e.g., P-Asserted-Identity) as discussed in [RFC8224]. | |||
| Similarly, "jcd", "jcl", "icn", "apn", or "crn" elements can be used | Similarly, "jcd", "jcl", "icn", "apn", or "crn" elements can be used | |||
| optionally (based on local policy for devices that support it) to | optionally (based on local policy for devices that support it) to | |||
| populate a Call-Info header field following the format of [RFC9796]. | populate a Call-Info header field following the format of [RFC9796]. | |||
| If PASSporT RCD claims types defined in the future are present, they | If PASSporT RCD claims types defined in the future are present, they | |||
| should follow similar defined proceedures and policies. | should follow similar defined procedures and policies. | |||
| The behavior of a SIP User Agent Server (UAS) upon receiving an | The behavior of a SIP User Agent Server (UAS) upon receiving an | |||
| INVITE or other type of session initiation request containing a | INVITE or other type of session initiation request containing a | |||
| PASSporT object with an "rcd" claim largely remains a matter of | PASSporT object with an "rcd" claim largely remains a matter of | |||
| implementation policy. In most cases, implementations would render | implementation policy. In most cases, implementations would render | |||
| this calling party name information to the user while alerting. Any | this calling party name information to the user while alerting. Any | |||
| user interface additions to express confidence in the veracity of | user interface additions to express confidence in the veracity of | |||
| this information are outside the scope of this specification. | this information are outside the scope of this specification. | |||
| 13. Using "rcd", "rcdi", and "crn" as Additional Claims to Other | 13. Using "rcd", "rcdi", and "crn" as Additional Claims to Other | |||
| skipping to change at line 1505 ¶ | skipping to change at line 1505 ¶ | |||
| [RFC9060] Peterson, J., "Secure Telephone Identity Revisited (STIR) | [RFC9060] Peterson, J., "Secure Telephone Identity Revisited (STIR) | |||
| Certificate Delegation", RFC 9060, DOI 10.17487/RFC9060, | Certificate Delegation", RFC 9060, DOI 10.17487/RFC9060, | |||
| September 2021, <https://www.rfc-editor.org/info/rfc9060>. | September 2021, <https://www.rfc-editor.org/info/rfc9060>. | |||
| [RFC9118] Housley, R., "Enhanced JSON Web Token (JWT) Claim | [RFC9118] Housley, R., "Enhanced JSON Web Token (JWT) Claim | |||
| Constraints for Secure Telephone Identity Revisited (STIR) | Constraints for Secure Telephone Identity Revisited (STIR) | |||
| Certificates", RFC 9118, DOI 10.17487/RFC9118, August | Certificates", RFC 9118, DOI 10.17487/RFC9118, August | |||
| 2021, <https://www.rfc-editor.org/info/rfc9118>. | 2021, <https://www.rfc-editor.org/info/rfc9118>. | |||
| [RFC9796] Wendt, C. and J. Peterson, "SIP Call-Info Parameters for | [RFC9796] Wendt, C. and J. Peterson, "SIP Call-Info Parameters for | |||
| Rich Call Data", RFC 9796, DOI 10.17487/RFC9796, June | Rich Call Data", RFC 9796, DOI 10.17487/RFC9796, July | |||
| 2025, <https://www.rfc-editor.org/info/rfc9796>. | 2025, <https://www.rfc-editor.org/info/rfc9796>. | |||
| 17.2. Informative References | 17.2. Informative References | |||
| [ATIS-1000074.v003] | [ATIS-1000074.v003] | |||
| Alliance for Telecommunications Industry Solutions, | Alliance for Telecommunications Industry Solutions, | |||
| "Signature-based Handling of Asserted information using | "Signature-based Handling of Asserted information using | |||
| toKENs (SHAKEN)", ATIS-1000074.v003, August 2022, | toKENs (SHAKEN)", ATIS-1000074.v003, August 2022, | |||
| <https://access.atis.org/higherlogic/ws/public/ | <https://access.atis.org/higherlogic/ws/public/ | |||
| download/67436>. | download/67436>. | |||
| skipping to change at line 1563 ¶ | skipping to change at line 1563 ¶ | |||
| Eric Burger, Alec Fenichel, Ben Campbell, Jack Rickard, Jordan | Eric Burger, Alec Fenichel, Ben Campbell, Jack Rickard, Jordan | |||
| Simpson for helpful suggestions, review, and comments. | Simpson for helpful suggestions, review, and comments. | |||
| Authors' Addresses | Authors' Addresses | |||
| Chris Wendt | Chris Wendt | |||
| Somos Inc. | Somos Inc. | |||
| Email: chris-ietf@chriswendt.net | Email: chris-ietf@chriswendt.net | |||
| Jon Peterson | Jon Peterson | |||
| Neustar Inc. | TransUnion | |||
| Email: jon.peterson@neustar.biz | Email: jon.peterson@transunion.com | |||
| End of changes. 4 change blocks. | ||||
| 4 lines changed or deleted | 4 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||