headers
Richard Barnes | 11 Mar 2008 04:26
Picon

GEOPRIV Experiment at IETF 71

Hi all,

Wanted to let folks know about an experiment that some participants from 
the GEOPRIV working group have put together for this IETF.  Using the 
IETF network infrastructure as a location source, we've set up a 
location server [1] that offers location information over the HTTP-based 
HELD protocol [2].  It works like this:

+--------+           +-----+           +---------------------+
| Client |---HELD----| LIS |-----------| IETF (NetDisco [3]) |
+--------+           +-----+           +---------------------+

1. Client submits HELD request
2. LIS queries NetDisco (over an ad-hoc interface) for location of an IP
3. NetDisco returns civicAddress XML for the AP to which the requested
IP is connected, e.g.:
<civicAddress
    xmlns="urn:params:xml:ns:pidf:geopriv10:civicAddr">
    <country>US</country>
    <A1>Pennsylvania</A1>
    <A3>Philadelphia</A3>
    <A6>Market</A6>
    <STS>Street</STS>
    <HNO>1201</HNO>
    <PC>19107</PC>
    <ROOM>Franknlin 1/2</ROOM>
</civicAddress>
4. LIS inserts civicAddress into PIDF-LO into locationResponse and
returns to Client
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 29 Mar 2008 18:00
Picon
Favicon

I-D Action:draft-ietf-geopriv-policy-15.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

	Title           : Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information
	Author(s)       : H. Schulzrinne, et al.
	Filename        : draft-ietf-geopriv-policy-15.txt
	Pages           : 35
	Date            : 2008-03-29

This document defines an authorization policy language for
controlling access to location information.  It extends the Common
Policy authorization framework to provide location-specific access
control.  More specifically, this document defines condition elements
specific to location information in order to restrict access based on
the current location of the Target.  Furthermore, it offers location-
specific transformation elements to reduce the granularity of the
returned location information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-policy-15.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment (draft-ietf-geopriv-policy-15.txt): message/external-body, 70 bytes
(Continue reading)






Permalink
| Reply
| 0 comments  
| 



  

  

  





headers


Internet-Drafts
 | 
29 Mar 2008 18:30






Picon

Favicon





I-D Action:draft-ietf-geopriv-l7-lcp-ps-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Geographic Location/Privacy Working Group of the IETF.

	Title           : GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and Requirements
	Author(s)       : H. Tschofenig, H. Schulzrinne
	Filename        : draft-ietf-geopriv-l7-lcp-ps-07.txt
	Pages           : 25
	Date            : 2008-03-29

This document provides a problem statement, lists requirements and
captures design aspects for a Geopriv Layer 7 Location Configuration
Protocol L7 (LCP).  This protocol aims to allow an end host to obtain
location information, by value or by reference, from a Location
Information Server (LIS) that is located in the access network.  The
obtained location information can then be used for a variety of
different protocols and purposes.  For example, it can be used as
input to the Location-to-Service Translation Protocol (LoST) or to
convey location within SIP to other entities.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-l7-lcp-ps-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.



Attachment (draft-ietf-geopriv-l7-lcp-ps-07.txt): message/external-body, 70 bytes

(Continue reading)






Permalink
| Reply
| 0 comments  
| 



  

  

  

  


  





    



Gmane