Geographic Location/Privacy (geopriv)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional GEOPRIV Web Page

Last Modified: 2008-10-24

Additional information is available at tools.ietf.org/wg/geopriv

Chair(s):

  • Robert Sparks <RjS@estacado.net>

    Real-time Applications and Infrastructure Area Director(s):

  • Jon Peterson <jon.peterson@neustar.biz>
  • Cullen Jennings <fluffy@cisco.com>

    Real-time Applications and Infrastructure Area Advisor:

  • Cullen Jennings <fluffy@cisco.com>

    Technical Advisor(s):

  • Lisa Dusseault <lisa@osafoundation.org>

    Mailing Lists:

    General Discussion: geopriv@ietf.org
    To Subscribe: geopriv-request@ietf.org
    In Body: subscribe
    Archive: http://www.ietf.org/mail-archive/web/geopriv/index.html

    Description of Working Group:

    As more and more resources become available on the Internet, some
    applications need to acquire geographic location information about
    certain resources or entities. These applications include navigation,
    emergency services, management of equipment in the field, and other
    location-based services.

    But while the formatting and transfer of such information is in some
    sense a straightforward process, the implications of doing it,
    especially in regards to privacy and security, are anything but.

    The primary task of this working group will be to assess the the
    authorization, integrity and privacy requirements that must be met in
    order to transfer such information, or authorize the release or
    representation of such information through an agent.

    In addition, the working group will select an already standardized
    format to recommend for use in representing location per se.  A key
    task will be to enhance this format and protocol approaches using the
    enhanced format, to ensure that the security and privacy methods are
    available to diverse location-aware applications.  Approaches to be
    considered will include (among others) data formats incorporating
    fields directing the privacy handling of the location information and
    possible methods of specifying variable precision of location.

    Also to be considered will be:  authorization of requestors and
    responders; authorization of proxies (for instance, the ability to
    authorize a carrier to reveal what timezone one is in, but not what
    city.  An approach to the taxonomy of requestors, as well as to the
    resolution or precision of information given them, will be part of this
    deliverable.

    The combination of these elements should provide a service capable of
    transferring geographic location information in a private and secure
    fashion (including the option of denying transfer).

    For reasons of both future interoperability and assurance of the
    security and privacy goals, it is a goal of the working group to
    deliver a specification that has broad applicablity and will become
    mandatory to implement for IETF protocols that are location-aware.


    Two further deliverables of the WG will be:

    o An example API for application-level access to/management
      of link-based location information.  That is, for instance, the WG
      may describe an API for secure, privacy-enabling user/ application
      handling of location information specific to a 3G wireless link
      technology.

    o Development of i-ds that make security and privacy integral to
      location information in HTTP and HTML, based on the work in
      draft-daviel-html-geo-tag-05.txt and
      draft-daviel-http-geo-header-03.txt.

    Out of Scope:

    This WG won't develop location-determining technology.  It will work
    from existing technologies and where the technology is undeveloped,
    will state that applicability may await others' developments.

    This WG won't develop technology to support any particular regulatory
    requirement [e.g. E.911] but will provide a framework that might be
    used for private/secure definition of such technologies by other
    bodies.

    Coordination:

    The WG will coordinate with other WGs developing general privacy and
    location-aware functions, e.g. the SIP WG, so that the WG deliverables
    can be used by them.  Other coordination should include the NymIP
    research community, WC3, and the Location Information Forum.

    Goals and Milestones:

    Done  Discuss initial geopriv scenarios and application requirements i-d's
    Done  Discuss initial geographic location privacy and security requirements i-d.
    Done  Initial i-d on geographic information protocol design, including privacy and security techniques.
    Done  Review charter and initial i-ds with AD, and have IESG consider rechartering if necessary.
    Done  Submit geopriv scenarios and application requirements to IESG for publicaiton as Informational RFCs
    Done  Submit security/privacy requirements I-D to IESG for publication as Informational RFC.
    Done  Submit PIDF-LO basic geopriv object draft as a PS
    Done  Initial Common Rules base object draft
    Done  Initial Common Ruels GEOPRIV object draft
    Done  Submit DHCP Civil draft as a PS
    Nov 2007  Resubmit Geolocation Policy to the IESG for publication as PS
    Nov 2007  Resubmit Conveying Location Objects in RADIUS and Diameter to the IESG for publication as PS
    Nov 2007  Submit Additional Civic PIDF-LO types (updating 4119) to the IESG for publication as PS
    Dec 2007  Submit Layer 7 Location Conveyance Protocol Problem Statement and Requirements to the IESG for publication as Informational
    Dec 2007  Submit a Document Format for Filtering and Reporting PIDF-LO Location Notifications to the IESG for publication as PS
    Dec 2007  Submit Requirements for Location by Reference Protocols to the IESG for publication as Informational
    Jan 2008  Submit PIDF-LO Usage Clarifications and Recommendations (updating 4119) to the IESG for publication as PS
    Feb 2008  Submit minimal HTTP based protocol satisfying baseline requirements specified in the Layer 7 Location Conveyance Protocol Problem Statement and Requirements to the IESG for publication as PS
    Feb 2008  Submit a LIS Discovery Mechanism to the IESG for publication as a PS
    Jul 2008  Submit Recommendations for Retransmission in SIP Location Conveyance to the IESG for publication as Informational
    Dec 2008  Submit recommendations for representing civic addresses in PIDF-LO to the IESG for publication as BCP

    Internet-Drafts:

    Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information (56621 bytes)
    Carrying Location Objects in RADIUS and Diameter (124024 bytes)
    GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations (57108 bytes)
    A Document Format for Filtering and Reporting Location Notications in the Presence Information Document Format Location Object (PIDF-LO) (37580 bytes)
    GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and Requirements (40108 bytes)
    HTTP Enabled Location Delivery (HELD) (97883 bytes)
    Requirements for a Location-by-Reference Mechanism (36641 bytes)
    Discovering the Local Location Information Server (LIS) (49348 bytes)
    Dynamic Host Configuration Protocol (DHCP) Option for a Location Uniform Resource Identifier (URI) (27378 bytes)
    Implications of for SIP Location Conveyance (30112 bytes)
    Considerations for Civic Addresses in PIDF-LO (58447 bytes)

    Request For Comments:

    Geopriv requirements (RFC 3693) (68881 bytes)
    Threat Analysis of the geopriv Protocol (RFC 3694) (44364 bytes)
    Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information (RFC 3825) (31715 bytes)
    A Presence Architecture for the Distribution of GEOPRIV Location Objects (RFC 4079) (16718 bytes)
    A Presence-based GEOPRIV Location Object Format (RFC 4119) (53522 bytes) updated by RFC 5139
    Location Types Registry (RFC 4589) (24037 bytes)
    Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information (RFC 4676) (45208 bytes) obsoleted by RFC 4776
    Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information (RFC 4776) (45495 bytes) obsoletes RFC 4676
    Common Policy: A Document Format for Expressing Privacy Preferences (RFC 4745) (63602 bytes)
    Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO) (RFC 5139) (27470 bytes) updates RFC 4119
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.