RFC 5379 privacy guidelines state that a privacy service must delete P-Asserted-Identity headers when user privacy is requested with Privacy: id.
Checked 2026-10-02
A privacy service MUST delete the P-Asserted-Identity headers when user privacy is requested with Privacy:id
- Vendor
- not restricted
- Product
- not restricted
- Subsystem
- Privacy header
- Deployment
- multi-tenant, on-premises
- Region
- not restricted
- Release range
- RFC 5379
- Checked
- 2026-10-02
Sources
- Guidelines for Using the Privacy Mechanism for SIP — IETF / RFC Editor · tier 1 standards and regulators · Section 5.1.8 (P-Asserted-Identity)
Cite this note
APA
WarmTransfer. (2026, October 2). SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-rfc5379-pai-delete-id. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-identity-headers-rfc5379-pai-delete-id
BibTeX
@misc{warmtransfer-claim-sip-identity-headers-rfc5379-pai-delete-id,
title = {SIP identity headers: P-Asserted-Identity and Diversion and History-Info: source note sip-identity-headers-rfc5379-pai-delete-id},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-identity-headers-rfc5379-pai-delete-id},
note = {Source note sip-identity-headers-rfc5379-pai-delete-id, checked 2026-10-02}
}