User-Agent-Driven Privacy Mechanism for SIP

Abstract

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. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5767.

A SIP Usage for REsource LOcation And Discovery (RELOAD)

“…Anonymous GRUUs [RFC5767] are constructed analogously, but require either that the enrollment server issues a different Node-ID for each anonymous GRUU required, or that a destination list be used that includes a Peer that compresses the destination list to stop the Node-ID from being revealed.…”

A survey on anonymous voice over IP communication: attacks and defenses

“…Finally, implementation and evaluation has not yet been done. [29] RFC 5767 [29] discussed a framework to conceal users' real identity based on Globally Routable User Agent URIs (GRUU) and Traversal Using Relays around NAT (TURN). GRUU [37] works as a temporary globally unique identifier for a specific UA instance.…”

Requirements from Session Initiation Protocol (SIP) Session Border Control (SBC) Deployments

“…One of the ways is the UA-driven privacy mechanism [8], where the UA can facilitate the concealment of topology information.…”