| CARVIEW |
Select Language
HTTP/2 200
date: Sun, 12 Oct 2025 00:34:38 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=_LVRUskxq9NUN4vNSCsbqcQbUSCTwcvuPZq61zmzZCQ-1760229278-1.0.1.1-VmwD4eJEpRJeHN5_8BSM_kD96uG6HwxBNxu4.nD5aZOQtF6fh.sEW3em750ifAZGtPoUDo4ZAVnh2LzzgWC_hEGqx2.4cvooZTKgDaGWbrY; path=/; expires=Sun, 12-Oct-25 01:04:38 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98d283399fbe999b-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 3323 » RFC Editor
Search RFCs
RFC 3323
A Privacy Mechanism for the Session Initiation Protocol (SIP), November 2002
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3323
Discuss this RFC: Send questions or comments to the mailing list sipcore@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3323
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us