draft-ietf-geopriv-arch-01.txt   draft-ietf-geopriv-arch-02.txt 
GEOPRIV R. Barnes GEOPRIV R. Barnes
Internet-Draft M. Lepinski Internet-Draft M. Lepinski
Updates: 3693, 3694 BBN Technologies Updates: 3693, 3694 BBN Technologies
(if approved) A. Cooper (if approved) A. Cooper
Intended status: BCP J. Morris Intended status: BCP J. Morris
Expires: April 29, 2010 Center for Democracy & Expires: November 28, 2010 Center for Democracy &
Technology Technology
H. Tschofenig H. Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
H. Schulzrinne H. Schulzrinne
Columbia University Columbia University
October 26, 2009 May 27, 2010
An Architecture for Location and Location Privacy in Internet An Architecture for Location and Location Privacy in Internet
Applications Applications
draft-ietf-geopriv-arch-01 draft-ietf-geopriv-arch-02
Abstract
Location-based services (such as navigation applications, emergency
services, management of equipment in the field) need geographic
location information about Internet hosts, their users, and other
related entities. These applications need to securely gather and
transfer location information for location services, and at the same
time protect the privacy of the individuals involved. This document
describes an architecture for privacy-preserving location-based
services in the Internet, focusing on authorization, security, and
privacy requirements for the data formats and protocols used by these
services.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on November 28, 2010.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 29, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Location-based services (such as navigation applications, emergency described in the Simplified BSD License.
services, management of equipment in the field) need geographic
location information about Internet hosts, their users, and other
related entities. These applications need to securely gather and
transfer location information for location services, and at the same
time protect the privacy of the individuals involved. This document
describes an architecture for privacy-preserving location-based
services in the Internet, focusing on authorization, security, and
privacy requirements for the data formats and protocols used by these
services.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Binding Rules to Data . . . . . . . . . . . . . . . . . . 4 1.1. Binding Rules to Data . . . . . . . . . . . . . . . . . . 4
1.2. Location-Specific Privacy Risks . . . . . . . . . . . . . 5 1.2. Location-Specific Privacy Risks . . . . . . . . . . . . . 5
1.3. Privacy Paradigms . . . . . . . . . . . . . . . . . . . . 6 1.3. Privacy Paradigms . . . . . . . . . . . . . . . . . . . . 6
2. Overview of the Architecture . . . . . . . . . . . . . . . . . 7 2. Overview of the Architecture . . . . . . . . . . . . . . . . . 7
2.1. Basic Geopriv Scenario . . . . . . . . . . . . . . . . . . 8 2.1. Basic Geopriv Scenario . . . . . . . . . . . . . . . . . . 8
2.2. Roles and Data Formats . . . . . . . . . . . . . . . . . . 9 2.2. Roles and Data Formats . . . . . . . . . . . . . . . . . . 9
skipping to change at page 36, line 48 skipping to change at page 36, line 48
[4] U.S. Department of Defense, "National Industrial Security [4] U.S. Department of Defense, "National Industrial Security
Program Operating Manual", DoD 5220-22M, January 1995. Program Operating Manual", DoD 5220-22M, January 1995.
[5] Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J., Polk, [5] Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J., Polk,
J., and J. Rosenberg, "Common Policy: A Document Format for J., and J. Rosenberg, "Common Policy: A Document Format for
Expressing Privacy Preferences", RFC 4745, February 2007. Expressing Privacy Preferences", RFC 4745, February 2007.
[6] Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J., and [6] Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J., and
J. Polk, "Geolocation Policy: A Document Format for Expressing J. Polk, "Geolocation Policy: A Document Format for Expressing
Privacy Preferences for Location Information", Privacy Preferences for Location Information",
draft-ietf-geopriv-policy-21 (work in progress), July 2009. draft-ietf-geopriv-policy-21 (work in progress), January 2010.
[7] Rosenberg, J., "The Extensible Markup Language (XML) [7] Rosenberg, J., "The Extensible Markup Language (XML)
Configuration Access Protocol (XCAP)", RFC 4825, May 2007. Configuration Access Protocol (XCAP)", RFC 4825, May 2007.
[8] Tschofenig, H. and H. Schulzrinne, "GEOPRIV Layer 7 Location [8] Tschofenig, H. and H. Schulzrinne, "GEOPRIV Layer 7 Location
Configuration Protocol; Problem Statement and Requirements", Configuration Protocol; Problem Statement and Requirements",
draft-ietf-geopriv-l7-lcp-ps-10 (work in progress), July 2009. draft-ietf-geopriv-l7-lcp-ps-10 (work in progress), July 2009.
[9] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic Host [9] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic Host
Configuration Protocol Option for Coordinate-based Location Configuration Protocol Option for Coordinate-based Location
Configuration Information", RFC 3825, July 2004. Configuration Information", RFC 3825, July 2004.
[10] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4 [10] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4
and DHCPv6) Option for Civic Addresses Configuration and DHCPv6) Option for Civic Addresses Configuration
Information", RFC 4776, November 2006. Information", RFC 4776, November 2006.
[11] Polk, J., "Dynamic Host Configuration Protocol (DHCP) IPv4 and [11] Polk, J., "Dynamic Host Configuration Protocol (DHCP) IPv4 and
IPv6 Option for a Location Uniform Resource Identifier (URI)", IPv6 Option for a Location Uniform Resource Identifier (URI)",
draft-ietf-geopriv-dhcp-lbyr-uri-option-06 (work in progress), draft-ietf-geopriv-dhcp-lbyr-uri-option-07 (work in progress),
September 2009. March 2010.
[12] Barnes, M., Winterbottom, J., Thomson, M., and B. Stark, "HTTP [12] Barnes, M., Winterbottom, J., Thomson, M., and B. Stark, "HTTP
Enabled Location Delivery (HELD)", Enabled Location Delivery (HELD)",
draft-ietf-geopriv-http-location-delivery-16 (work in draft-ietf-geopriv-http-location-delivery-16 (work in
progress), August 2009. progress), August 2009.
[13] Marshall, R., "Requirements for a Location-by-Reference [13] Marshall, R., "Requirements for a Location-by-Reference
Mechanism", draft-ietf-geopriv-lbyr-requirements-08 (work in Mechanism", draft-ietf-geopriv-lbyr-requirements-09 (work in
progress), September 2009. progress), November 2009.
[14] World Wide Web Consortium, "The XMLHttpRequest Object", W3C [14] World Wide Web Consortium, "The XMLHttpRequest Object", W3C
document http://www.w3.org/TR/XMLHttpRequest/, April 2008. document http://www.w3.org/TR/XMLHttpRequest/, April 2008.
[15] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, "Framework [15] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, "Framework
for Emergency Calling using Internet Multimedia", for Emergency Calling using Internet Multimedia",
draft-ietf-ecrit-framework-10 (work in progress), July 2009. draft-ietf-ecrit-framework-10 (work in progress), July 2009.
[16] Rosen, B. and J. Polk, "Best Current Practice for [16] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in support of Emergency Calling", Communications Services in support of Emergency Calling",
draft-ietf-ecrit-phonebcp-13 (work in progress), July 2009. draft-ietf-ecrit-phonebcp-14 (work in progress), January 2010.
[17] Hardie, T., Newton, A., Schulzrinne, H., and H. Tschofenig, [17] Hardie, T., Newton, A., Schulzrinne, H., and H. Tschofenig,
"LoST: A Location-to-Service Translation Protocol", RFC 5222, "LoST: A Location-to-Service Translation Protocol", RFC 5222,
August 2008. August 2008.
[18] Schulzrinne, H., "Location-to-URL Mapping Architecture and [18] Schulzrinne, H., "Location-to-URL Mapping Architecture and
Framework", draft-ietf-ecrit-mapping-arch-04 (work in Framework", draft-ietf-ecrit-mapping-arch-04 (work in
progress), March 2009. progress), March 2009.
[19] Peterson, J., "A Presence-based GEOPRIV Location Object [19] Peterson, J., "A Presence-based GEOPRIV Location Object
 End of changes. 13 change blocks. 
53 lines changed or deleted 41 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/