Geographic Location/Privacy (geopriv) ------------------------------------- Charter Last Modified: 2009-11-17 Current Status: Active Working Group Chair(s): Richard Barnes Alissa Cooper Real-time Applications and Infrastructure Area Director(s): Robert Sparks Cullen Jennings Real-time Applications and Infrastructure Area Advisor: Cullen Jennings Technical Advisor(s): Lisa Dusseault 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 Jan 2010 Submit civic address registry values for street name and house number prefixes to the IESG for publication as Informational Jun 2010 Submit recommendations for LIS discovery through residential gateways as Informational Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Nov 2003 Jan 2010 Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information Mar 2006 Mar 2010 Filtering Location Notifications in the Session Initiation Protocol (SIP) Jan 2007 Jul 2009 GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and Requirements Jun 2007 Aug 2009 HTTP Enabled Location Delivery (HELD) Sep 2007 Nov 2009 Requirements for a Location-by-Reference Mechanism Dec 2007 Feb 2010 Discovering the Local Location Information Server (LIS) Feb 2008 Sep 2009 Dynamic Host Configuration Protocol (DHCP) IPv4 and IPv6 Option for a Location Uniform Resource Identifier (URI) Oct 2008 Jul 2009 Considerations for Civic Addresses in PIDF-LO - Guidelines and IANA Registry Definition Jun 2009 Nov 2009 A Uniform Resource Identifier for Geographic Locations ('geo' URI) Jun 2009 Feb 2010 Dynamic Host Configuration Protocol Options for Coordinate-based Location Configuration Information Jul 2009 Oct 2009 An Architecture for Location and Location Privacy in Internet Applications Sep 2009 Feb 2010 Use of Device Identity in HTTP-Enabled Location Delivery (HELD) Jan 2010 Jan 2010 Prefix elements for Road and House Numbers in PIDF-LO Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC3693 I Feb 2004 Geopriv requirements RFC3694 I Feb 2004 Threat Analysis of the geopriv Protocol RFC3825Standard Jul 2004 Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information RFC4079 I Jul 2005 A Presence Architecture for the Distribution of GEOPRIV Location Objects RFC4119Standard Dec 2005 A Presence-based GEOPRIV Location Object Format RFC4589 PS Jul 2006 Location Types Registry RFC4676 PS Oct 2006 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information RFC4776 PS Nov 2006 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information RFC4745 PS Feb 2007 Common Policy: A Document Format for Expressing Privacy Preferences RFC5139 PS Feb 2008 Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO) RFC5491 PS Mar 2009 GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations RFC5580 PS Aug 2009 Carrying Location Objects in RADIUS and Diameter RFC5606 I Aug 2009 Implications of 'retransmission-allowed' for SIP Location Conveyance