One document matched: draft-thomson-geopriv-lying-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="info" ipr="trust200902">
  <front>
    <title abbrev="Lying About Location">A Privacy-Preserving Policy Transformation for Location</title>
    <author initials="M." surname="Thomson" fullname="Martin Thomson">
      <organization>Commscope</organization>
      <address>
	<postal>
	  <street>Andrew Building (39)</street>
	  <street>Wollongong University Campus</street>
	  <street>Northfields Avenue</street>
	  <city>Wollongong</city>
	  <region>NSW</region>
	  <code>2522</code>
	  <country>AU</country>
	</postal>
	<phone>+61 2 4221 2915</phone>
	<email>martin.thomson@commscope.com</email>
      </address>
    </author>

    <date month="June" year="2011" />

    <area>RAI</area>

    <workgroup>GEOPRIV</workgroup>

    <keyword>geopriv, geolocation, privacy, location, lying, liar, liar, pantsonfire</keyword>

    <abstract>
      <t>Obscuring location effectively is difficult.  Falsehood offers a simpler, more effective method of location privacy protection.  A mechanism is defined whereby a rule maker can request that a location server lie about location.
      </t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>Obscuring location has applications for protecting privacy, as described in <xref target="I-D.ietf-geopriv-policy"/>.
      </t>

      <t>Effectively protecting privacy through obscuring location information is difficult.  Given an obscured location and enough supplementary information, a location recipient can recover a great deal of information about the known location despite obfuscation being used.  This supplementary information might include data on geographic features and their characteristics, past behavior of the target or aggregated data.
      </t>

      <t>Solving the difficult obscuring problem might be possible, but the effort required to try is significant.  A more expedient solution to the overall problem is to provide a way for a rule maker to select the location that is reported to location recipients.
      </t>

      <t>This privacy solution presents a trade-off.  While finer control is thereby given to rule makers over the location information that is shared, it also presents a greater burden on the rule maker developing policy rules.
      </t>

      <t>An extension to the <provide-location> element defined in <xref target="I-D.ietf-geopriv-policy"/> is described.
      </t>

      <t>This policy extension is most useful where an automated system generates location information.  In systems where the rule maker already is presented with an opportunity to alter location information, such as where the rule maker role is assumed by the entity generating (e.g. <xref target="RFC5985"/>) or publishing (e.g. <xref target="RFC3903"/>) location, such a mechanism is redundant.
      </t>

    </section>

    <section anchor="conventions" title="Conventions used in this document">
      <t>Familiarity with the terminology outlined in <xref target="I-D.ietf-geopriv-arch"/> is helpful.
      </t>

      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119"/>.
      </t>
    </section>

    <section anchor="liar" title="Location Information Absolute Replacement">
      <t>The location information absolute replacement (<spanx style="verb">liar</spanx>) element is a transformation element that is included in the <spanx style="verb">provide-location</spanx> element of a policy document.  When a <spanx style="verb">liar</spanx> element is included, the <spanx style="verb">profile</spanx> attribute MUST be set to <spanx style="verb">replacement-transformation</spanx>.
      </t>

      <t>The <spanx style="verb">liar</spanx> element can contain any form of location information that is valid for the <spanx style="verb">location-info</spanx> element in a <xref target="RFC4119">PIDF-LO</xref> (see also <xref target="RFC5491"/>).
      </t>

      <t>In order to apply the transformation, replace the content of any selected <spanx style="verb">location-info</spanx> element in the presence document with the content of the <spanx style="verb">liar</spanx> element in the policy document.  Content is copied verbatim.
      </t>

      <section title="Interaction with Other Transformations">
	<t>The <xref target="RFC4745">common policy</xref> framework permits the application of policy rules in any order.  Precedence is used to determine which transformation is finally applied.
	</t>

	<t>When combining multiple <spanx style="verb">provide-location</spanx> transformations, the location information absolute replacement transformation is assigned the highest available precedence.
	</t>
      </section>

      <section title="Example">
<figure><artwork><![CDATA[
  <ruleset
      xmlns="urn:ietf:params:xml:ns:common-policy"
      xmlns:gp="urn:ietf:params:xml:ns:geolocation-policy"
      xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
      xmlns:liar="urn:ietf:params:xml:ns:pidf:geopriv:liar">
    <rule id="drinking">
      <conditions>
	<identity>
	  <one id="sip:wife@example.com"/>
	</identity>
	<gp:location-condition>
	  <gp:location profile="civic-condition"
		       label="My Happy Place">
	    <ca:civicAddress>
	      <ca:NAM>The Pub</ca:NAM>
	    </ca:civicAddress>
	  </gp:location>
	</gp:location-condition>
      </conditions>
      <actions/>
      <transformations>
	<gp:provide-location profile="replacement-transformation">
	  <liar:liar>
	    <ca:civicAddress>
	      <ca:NAM>Work</ca:NAM>
	    </ca:civicAddress>
	  </liar:liar>
	</gp:provide-location>
      </transformations>
    </rule>
  </ruleset>
]]></artwork>
</figure>
      </section>
    </section>

    <section anchor="schema" title="XML Schema">
<figure><artwork><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:geopriv:liar"
	   xmlns:liar="urn:ietf:params:xml:ns:geopriv:liar"
	   xmlns:xs="http://www.w3.org/2001/XMLSchema"
	   elementFormDefault="qualified"
	   attributeFormDefault="unqualified">

  <xs:element name="liar" type="liar:liarType"/>
  <xs:complexType name="liarType">
    <xs:complexContent>
      <xs:restriction base="xs:anyType">
	<xs:sequence>
	  <!-- The content model is equivalent to that of
	       <location-info> in RFC 4119: very permissive -->
	  <xs:any namespace="##any" processContents="lax"
		  minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
      </xs:restriction>
    </xs:complexContent>
  </xs:complexType>

</xs:schema>
]]></artwork></figure>
    </section>

    <section anchor="ack" title="Acknowledgements">
      <t>Richard Barnes provided input on the original idea.
      </t>
    </section>

    <section anchor="iana" title="IANA Considerations">
      <t>This section registers an XML schema for the location information absolute replacement element, the corresponding namespace and <spanx style="verb">replacement-transformation</spanx> token.
      </t>
      <section title="URN Sub-Namespace Registration for urn:ietf:params:xml:ns:geopriv:liar">
	<t>This section registers a new XML namespace, <spanx style="verb">urn:ietf:params:xml:ns:geopriv:liar</spanx>, as per the guidelines in <xref target="RFC3688"/>.
	<list style="empty">
	  <t>URI: urn:ietf:params:xml:ns:geopriv:liar</t>
	  <t>Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org), Martin Thomson (martin.thomson@commscope.com).</t>

	  <t>XML:
	  <figure>
	    <artwork><![CDATA[
      BEGIN
	<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
	  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
	  <head>
	    <title>Location Information Absolute Replacement</title>
	  </head>
	  <body>
	    <h1>Namespace</h1>
	    <h2>urn:ietf:params:xml:ns:geopriv:liar</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
    with the RFC number for this specification.]]
	    <p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
	  </body>
	</html>
      END
      ]]></artwork>
	  </figure>
	  </t>
	</list>
	</t>
      </section>

      <section title="XML Schema Registration for Location Information Absolute Replacement Schema">
	<t>This section registers an XML schema as per the guidelines in <xref target="RFC3688"/>.
	<list style="hanging">
	  <t hangText="URI:">urn:ietf:params:xml:schema:geopriv:liar</t>
	  <t hangText="Registrant Contact:">IETF, GEOPRIV working group, (geopriv@ietf.org), Martin Thomson (martin.thomson@commscope.com).</t>
	  <t hangText="Schema:">The XML for this schema can be found in <xref target="schema"/> of this document.
	  </t>
	</list>
	</t>
      </section>

      <section title="Location Transformation Token Registration">
	<t>The token <spanx style="verb">replacement-transformation</spanx> is registered in the Geolocation Policy Location Profile Registry, as defined in <xref target="I-D.ietf-geopriv-policy"/>.  This token is used for the <spanx style="verb">provide-location</spanx> element as described in <xref target="liar"/>.
	</t>
      </section>

    </section>

    <section anchor="security" title="Security Considerations">
      <t>Policy documents include privacy-sensitive information.  The additional capabilities added by this document do not change this fact, but expand the possibilities for embarassment if policy documents are revealed.
      </t>
    </section>
  </middle>

  <!--  *****BACK MATTER ***** -->

  <back>
    <references title="Informative References">
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.3903.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.4119.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.4745.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5491.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5985.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-geopriv-arch"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-geopriv-policy"?>
    </references>
  </back>
</rfc>