Home / TLS, SRTP, identity, and abuse / Privacy and asserted identity
Privacy and asserted identity
Privacy is RFC 3323. P-Asserted-Identity and P-Preferred-Identity are for trusted networks, not cryptographic identity.
Learn in 5 minutes
- Name the Privacy header and the id token
- Keep PAI and PPI inside a trust domain
- Refuse to treat PAI as a signature
Visual
PPI is a hint from the UA. PAI is inserted by a trusted element. Both stop at the edge.
Worked example
See PAI on the wrong hop This INVITE is addressed to the carrier and still contains P-Asserted-Identity and Privacy: id.
- Press Dissect.
- Find Privacy and P-Asserted-Identity.
- Decide whether this hop is still inside a trust domain.
Fault
The carrier shows alice@example.com as a verified network identity. The SBC forwarded PAI on a request that also asked for Privacy id.
P-Asserted-Identity is a trusted-network header. It is not cryptographic identity, and Privacy id asks that it be withheld.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
Analytics Amazon Connect can attach conversational analytics to an external voice system with a SIPREC connector. The analytics plane is not a second SIP proxy for the customer call.