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: 2009-06-23

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

Chair(s):

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

Real-time Applications and Infrastructure Area Advisor:

Technical Advisor(s):

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:

The IETF has recognized that many applications are emerging that
require geographic and civic location information about resources and
entities, and that the representation and transmission of that
information has significant privacy and security implications. We have
created a suite of protocols that allow such applications to represent
and transmit such location objects and to allow users to express
policies on how these representations are exposed and used. The IETF
has also begun working on creating applications that use these
capabilities, for emergency services, general real-time communication,
and other usages.

The GEOPRIV working group is chartered to continue to develop and
refine representations of location in Internet protocols, and to
analyze the authorization, integrity, and privacy requirements that
must be met when these representations of location are created,
stored, and used. The group will create and refine mechanisms for the
transmission of these representations that address the requirements
that have been identified.

The working group will work with other IETF working groups and other
standards development organizations that are building applications
that use location information to ensure that the requirements are well
understood and met, and that no additional security or privacy issues
related to location are left unaddressed as these location information
is incorporated into other protocols.

It remains a goal of the GEOPRIV working group to deliver
specifications of broad applicability that will become mandatory to
implement for IETF protocols that are location aware.

This working group will not develop location-determining technology.
However, the IETF acknowledges that information used in the location-
determination process will in some cases need to be carried over the
Internet. Where necessary, this working group will develop protocols
or protocol extensions to encode location-determination data
structures defined elsewhere. This working group will not develop
technologies to directly address any particular regulatory
requirements (e.g. 9-1-1). The group will continue to coordinate with
any other IETF entities that are working on those problems to ensure
the technologies created here meet the needs of those entities, and
that the authorization, integrity, and privacy requirements on the
mechanisms provided by these technologies continue to be met.

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
Done  Resubmit Conveying Location Objects in RADIUS and Diameter to the IESG for publication as PS
Done  Submit Additional Civic PIDF-LO types (updating 4119) to the IESG for publication as PS
Done  Submit Layer 7 Location Conveyance Protocol Problem Statement and Requirements to the IESG for publication as Informational
Done  Submit Requirements for Location by Reference Protocols to the IESG for publication as Informational
Done  Submit PIDF-LO Usage Clarifications and Recommendations (updating 4119) to the IESG for publication as PS
Done  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
Done  Submit a LIS Discovery Mechanism to the IESG for publication as a PS
Done  Submit Recommendations for Retransmission in SIP Location Conveyance to the IESG for publication as Informational
Done  Submit recommendations for representing civic addresses in PIDF-LO to the IESG for publication as BCP
Jun 2009  Resubmit Geolocation Policy to the IESG for publication as PS
Sep 2009  Submit an draft for DHCP geodetic location to the IESG for publication as PS to obsolete 3825
Sep 2009  Submit an Architecture for Location and Location Privacy to the IESG for publication as Informational
Dec 2009  Submit a Document Format for Filtering and Reporting PIDF-LO Location Notifications to the IESG for publication as PS
Dec 2009  Submit a URI scheme for directly expressing geodetic location to the IESG for publication as PS
Dec 2009  Submit a DHCP Option for a Location Uniform Resource Identifier (URI) to the IESG for publication as PS

Internet-Drafts:

Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information (61566 bytes)
A Document Format for Filtering and Reporting Location Notications in the Presence Information Document Format Location Object (PIDF-LO) (25866 bytes)
GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and Requirements (43030 bytes)
HTTP Enabled Location Delivery (HELD) (106492 bytes)
Requirements for a Location-by-Reference Mechanism (39332 bytes)
Discovering the Local Location Information Server (LIS) (36317 bytes)
Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI) (32557 bytes)
Considerations for Civic Addresses in PIDF-LO - Guidelines and IANA Registry Definition (69307 bytes)
A Uniform Resource Identifier for Geographic Locations ('geo' URI) (31940 bytes)
Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information (37045 bytes)
An Architecture for Location and Location Privacy in Internet Applications (103529 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,RFC 5491
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
GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations (RFC 5491) (51681 bytes) updates RFC 4119
Carrying Location Objects in RADIUS and Diameter (RFC 5580) (119753 bytes)
Implications of 'retransmission-allowed' for SIP Location Conveyance (RFC 5606) (27960 bytes)

Internet SocietyAMSHome - Tools - Datatracker - IASA - IAB - RFC Editor - IANA - IRTF - IETF Trust - ISOC - Contact Us
Secretariat services provided by Association Management Solutions, LLC (AMS).
Please send problem reports to: ietf-action@ietf.org.