Concluded WG Geographic Location/Privacy (geopriv)
Note: The data for concluded WGs is occasionally incorrect.
|Real-time Applications and Infrastructure Area (rai)
Additional GEOPRIV Web Page
Issue tracker, Wiki
Final Charter for 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.
|Submit an extension to PIDF-LO for expressing confidence for publication as a PS.
|Submit a flow identity extension for HTTP-Enabled Location Delivery (HELD) for publication as PS.
|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.
|Submit recommendations for civic address extensions as PS
|Submit recommendations for LIS discovery conducted by hosts behind residential gateways as Informational
|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.
|Submit device identity extensions for HTTP-Enabled Location Delivery (HELD) for publication as PS.
|Submit a policy control mechanism for location configuration as Proposed Standard
|Resubmit Geolocation Policy to the IESG for publication as PS
|Submit a Location Dereferencing Protocol for HTTP-Enabled Location Delivery (HELD) to the IESG for publication as PS.
|Submit a DHCP Option for a Location Uniform Resource Identifier (URI) to the IESG for publication as PS
|Submit a Document Format for Filtering and Reporting PIDF-LO Location Notifications to the IESG for publication as PS
|Submit a URI scheme for directly expressing geodetic location to the IESG for publication as PS
|Submit an draft for DHCP geodetic location to the IESG for publication as PS to obsolete 3825
|Submit an Architecture for Location and Location Privacy to the IESG for publication as Informational
|Submit recommendations for representing civic addresses in PIDF-LO to the IESG for publication as BCP
|Submit Recommendations for Retransmission in SIP Location Conveyance to the IESG for publication as Informational
|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
|Submit a LIS Discovery Mechanism to the IESG for publication as a PS
|Submit PIDF-LO Usage Clarifications and Recommendations (updating 4119) to the IESG for publication as PS
|Submit Layer 7 Location Conveyance Protocol Problem Statement and Requirements to the IESG for publication as Informational
|Submit Requirements for Location by Reference Protocols to the IESG for publication as Informational
|Resubmit Conveying Location Objects in RADIUS and Diameter to the IESG for publication as PS
|Submit Additional Civic PIDF-LO types (updating 4119) to the IESG for publication as PS
|Submit DHCP Civil draft as a PS
|Submit PIDF-LO basic geopriv object draft as a PS
|Initial Common Ruels GEOPRIV object draft
|Initial Common Rules base object draft
|Submit security/privacy requirements I-D to IESG for publication as Informational RFC.
|Initial i-d on geographic information protocol design, including privacy and security techniques.
|Submit geopriv scenarios and application requirements to IESG for publicaiton as Informational RFCs
|Review charter and initial i-ds with AD, and have IESG consider rechartering if necessary.
|Discuss initial geopriv scenarios and application requirements i-d's
|Discuss initial geographic location privacy and security requirements i-d.