RFC 5767: User-Agent-Driven Privacy Mechanism for SIP
In plain English — editorial summary, not part of the RFC
This document defines a guideline for a User Agent (UA) to generate an anonymous Session Initiation Protocol (SIP) message by utilizing mechanisms such as Globally Routable User Agent URIs (GRUUs) and Traversal Using Relays around NAT (TURN) without the need for a privacy service defined in RFC 3323. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5767
- Published
- April 2010
- Authors
- M. Munakata; S. Schubert; T. Ohba
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5552SIP Interface to VoiceXML Media ServicesCurrent
May 2009
- RFC 5688A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application SubtypesCurrent
January 2010
- RFC 7255Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance IDCurrent
May 2014
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 8498A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)Current
February 2019
- RFC 5768Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5874An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) ResourcesCurrent
May 2010
- RFC 5876Updates to Asserted Identity in the Session Initiation Protocol (SIP)Current
April 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?