Geographic Location/Privacy (geopriv)

Interim Meeting of

Note: This is a snapshot as of 2011-09-13. It may now be out of date.

Minutes | Agenda | Jabber Logs | Mailing List Archives

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

Chair(s):

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

Real-time Applications and Infrastructure Area Advisor(s)



Meeting Slides:

No Slides Present

Internet-Drafts:

Request for Comments:

RFCStatusTitle
RFC3693 I Geopriv requirements
RFC3694 I Threat Analysis of the geopriv Protocol
RFC3825 S Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information
RFC4079 I A Presence Architecture for the Distribution of GEOPRIV Location Objects
RFC4119 S A Presence-based GEOPRIV Location Object Format
RFC4589 PS Location Types Registry
RFC4676 PS Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information
RFC4745 PS Common Policy: A Document Format for Expressing Privacy Preferences
RFC4776 PS Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information
RFC5139 PS Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)
RFC5491 PS GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations
RFC5580 PS Carrying Location Objects in RADIUS and Diameter
RFC5606 I Implications of 'retransmission-allowed' for SIP Location Conveyance
RFC5687 I GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
RFC5774 BCP Considerations for Civic Addresses in the Presence Information Data Format Location Object (PIDF-LO): Guidelines and IANA Registry Definition
RFC5808 I Requirements for a Location-by-Reference Mechanism
RFC5870 PS A Uniform Resource Identifier for Geographic Locations ('geo' URI)
RFC5985 PS HTTP-Enabled Location Delivery (HELD)
RFC5986 PS Discovering the Local Location Information Server (LIS)
RFC6155 PS Use of Device Identity in HTTP-Enabled Location Delivery (HELD)
RFC6225 PS Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration Information
RFC6280 BCP An Architecture for Location and Location Privacy in Internet Applications

Charter:

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
Done   Submit an draft for DHCP geodetic location to the IESG for publication as PS to obsolete 3825
Done   Submit an Architecture for Location and Location Privacy to the IESG for publication as Informational
Done   Submit a Document Format for Filtering and Reporting PIDF-LO Location Notifications to the IESG for publication as PS
Done   Submit a URI scheme for directly expressing geodetic location to the IESG for publication as PS
01-2011   Submit a DHCP Option for a Location Uniform Resource Identifier (URI) to the IESG for publication as PS
03-2011   Resubmit Geolocation Policy to the IESG for publication as PS
03-2011   Submit civic address registry values for street name and house number prefixes to the IESG for publication as Informational
03-2011   Submit a Location Dereferencing Protocol for HTTP-Enabled Location Delivery (HELD) to the IESG for publication as PS.
06-2011   Submit recommendations for LIS discovery conducted by hosts behind residential gateways as Informational
06-2011   Submit a draft that defines civic address parameters to allow the expression of a location relative to a reference point to the IESG for publication as PS.
06-2011   Submit a method that can be used to provide location-related measurement data to a Location Information Server (LIS) within a request for location information to the IESG for publication as PS.
06-2011   Submit a policy control mechanism for location configuration as Proposed Standard
12-2012   Submit recommendations for civic address extensions as PS