RE: Security/Privacy/Location payload (AKA CAP) Use cases from IETF

As discused on the concall today:

 

http://www.ietf.org/rfc/rfc3693.txt -   
Geopriv Requirements

 

Abstract: 

 

Location-based services, navigation applications, emergency 
services,
   management of equipment in the field, and other 
location-dependent
   services need geographic location information 
about a Target (such as
   a user, resource or other entity).  
There is a need to securely
   gather and transfer location 
information for location services, while
   at the same time 
protect the privacy of the individuals involved.

   This 
document focuses on the authorization, security and privacy
   
requirements for such location-dependent services.  Specifically, 
it
   describes the requirements for the Geopriv Location Object 
(LO) and
   for the protocols that use this Location Object.  
This LO is
   envisioned to be the primary data structure used in 
all Geopriv
   protocol exchanges to securely transfer location 
data.

 

AND 

 

http://www.ietf.org/rfc/rfc3694.txt - 
Threat Analysis of the Geopriv Protocol

 

Abstract

   This document provides some analysis of 
threats against the Geopriv
   protocol architecture.  It 
focuses on protocol threats, threats that
   result from the 
storage of data by entities in the architecture, and
   threats 
posed by the abuse of information yielded by Geopriv.  Some
   
security properties that meet these threats are enumerated as a
   
reference for Geopriv requirements.

Carl Reed, PhD
CTO and Executive Director Specification 
Program
OGC

 

The OGC: Helping the World to Communicate Geographically

 

---------------------

 

 

 

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential or privileged information. 
If you are not the intended recipient, any use, copying, disclosure, 
dissemination or distribution is strictly prohibited. If you are not the 
intended recipient, please notify the sender  immediately by return email 
and delete this communication and destroy all copies.