Last Modified: 2004-06-15
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.
| 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. | |
| Feb 04 | Submit PIDF-LO basic geopriv object draft as a PS | |
| Feb 04 | Initial Common Rules base object draft | |
| Feb 04 | Initial Common Ruels GEOPRIV object draft | |
| Mar 04 | Submit Common Rules base object draft as a PS | |
| Mar 04 | Submit Common Rules GEOPRIV object draft as a PS | |
| Apr 04 | Submit DHCP Civil draft as a PS | |
| Jun 04 | Initial Geo-tag/Geo-Header draft | |
| Jun 04 | Initial HTTP using protocol draft | |
| Jun 04 | Initial SIP using protocol draft | |
| Jul 04 | Initial Using protocol guideline | |
| Nov 04 | Submit Geo-tag/Geo-Header draft as a PS | |
| Nov 04 | Submit HTTP using protocol draft as a PS | |
| Nov 04 | Submit SIP using protocol draft as a PS | |
| Nov 04 | Submit Using protocol guidelines draft as a BCP | |
| Nov 04 | Conclude working group |
| RFC | Status | Title |
|---|---|---|
| RFC3693 | I | Geopriv requirements |
| RFC3694 | I | Threat Analysis of the geopriv Protocol |
| RFC3825 | Standard | Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information |