Common Policy: A Document Format for Expressing Privacy Preferences

Schulzrinne, Henning; Tschofenig, Hannes; Morris, James F.; Cuéllar, Jorge; Polk, James; Rosenberg, Jonathan

doi:10.17487/rfc4745

Cited by 62 publications

(75 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The IETF (Internet Engineering Task Force) Geopriv [44] identified the need of processing and transferring the location information among location-based services and applications preserving the privacy of the involved users. Geopriv creates a location object that encapsulates the users' location information and the requirements of privacy associated to the information.…”

Section: Resultsmentioning

confidence: 99%

A privacy service for location-based collaboration among mobile users

2008

View full text Add to dashboard Cite

The potential loss of privacy due to the use of locationbased applications may be one of the greatest obstacles to their wider acceptance. Nevertheless, most research about privacy management to-date has not taken into consideration the complexity in the utilization of collaborative applications that may require users' location sharing among participants. In this article, we propose a privacy service that helps users to maintain their privacy policy in a flexible and incremental way. We also carried out a qualitative evaluation study whose results illustrate several challenges that should be handled in the design of such a service.

show abstract

Section: Resultsmentioning

confidence: 99%

A privacy service for location-based collaboration among mobile users

2008

View full text Add to dashboard Cite

show abstract

“…It inherits and enhances the common policy document defined in [RFC4745]. A common policy document contains a set of rules.…”

Section: Formatmentioning

confidence: 99%

“…Since the problem space of this specification is different from that of [RFC4745], the [RFC4745] <identity> element is not sufficient for use with load filtering. First, load filtering may be applied to different identities contained in a request, including identities of both the receiving entity and the sending entity.…”

Section: Call Identitymentioning

confidence: 99%

A Session Initiation Protocol (SIP) Load-Control Event Package

Schulzrinne¹,

Shen²,

Koike³

2014

Self Cite

View full text Add to dashboard Cite

This specification defines a load-control event package for the Session Initiation Protocol (SIP). It allows SIP entities to distribute load-filtering policies to other SIP entities in the network. The load-filtering policies contain rules to throttle calls from a specific user or based on their source or destination domain, telephone number prefix. The mechanism helps to prevent signaling overload and complements feedback-based SIP overload control efforts.

show abstract

“…A policy URI always identifies a resource that can be represented as a commonpolicy document [RFC4745] (possibly including some extensions; e.g., for geolocation policy [RFC6772] A PUT request to a policy URI is a request to replace the current policy. The entity-body of a PUT request includes a complete policy document.…”

Section: Policy Urismentioning

confidence: 99%

“…The Location Server MUST support policy documents in the commonpolicy format [RFC4745], as identified by the MIME media type of "application/auth-policy+xml". The common-policy format MUST be provided as the default format in response to GET requests that do not include specific "Accept" headers, but content negotiation MAY be used to allow for other formats.…”

Section: Policy Urismentioning

confidence: 99%