draft-ietf-geopriv-pdif-lo-profile-11.txt   draft-ietf-geopriv-pdif-lo-profile-12.txt 
Geopriv J. Winterbottom Geopriv J. Winterbottom
Internet-Draft M. Thomson Internet-Draft M. Thomson
Updates: 4119 (if approved) Andrew Corporation Updates: 4119 (if approved) Andrew Corporation
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: August 23, 2008 Nokia Siemens Networks Expires: March 16, 2009 Nokia Siemens Networks
February 20, 2008 September 12, 2008
GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations
draft-ietf-geopriv-pdif-lo-profile-11.txt draft-ietf-geopriv-pdif-lo-profile-12.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 23, 2008. This Internet-Draft will expire on March 16, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
The Presence Information Data Format Location Object (PIDF-LO) The Presence Information Data Format Location Object (PIDF-LO)
specification provides a flexible and versatile means to represent specification provides a flexible and versatile means to represent
location information. There are, however, circumstances that arise location information. There are, however, circumstances that arise
when information needs to be constrained in how it is represented. when information needs to be constrained in how it is represented.
In these circumstances the range of options that need to be In these circumstances the range of options that need to be
implemented are reduced. There is growing interest in being able to implemented are reduced. There is growing interest in being able to
use location information contained in a PIDF-LO for routing use location information contained in a PIDF-LO for routing
skipping to change at page 4, line 11 skipping to change at page 4, line 11
9.2. Informative References . . . . . . . . . . . . . . . . . . 32 9.2. Informative References . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
Intellectual Property and Copyright Statements . . . . . . . . . . 34 Intellectual Property and Copyright Statements . . . . . . . . . . 34
1. Introduction 1. Introduction
The Presence Information Data Format Location Object (PIDF-LO) The Presence Information Data Format Location Object (PIDF-LO)
[RFC4119] is the recommended way of encoding location information and [RFC4119] is the recommended way of encoding location information and
associated privacy policies. Location information in a PIDF-LO may associated privacy policies. Location information in a PIDF-LO may
be described in a geospatial manner based on a subset of GMLv3, or as be described in a geospatial manner based on a subset of GMLv3, or as
civic location information [I-D.ietf-geopriv-revised-civic-lo]. A civic location information [RFC5139]. A GML profile for expressing
GML profile for expressing geodetic shapes in a PIDF-LO is described geodetic shapes in a PIDF-LO is described in [GeoShape]. Uses for
in [GeoShape]. Uses for PIDF-LO are envisioned in the context of PIDF-LO are envisioned in the context of numerous location based
numerous location based applications. This document makes applications. This document makes recommendations for formats and
recommendations for formats and conventions to make interoperability conventions to make interoperability less problematic.
less problematic.
The PIDF-LO provides a general presence format for representing The PIDF-LO provides a general presence format for representing
location information, and permits specification of location location information, and permits specification of location
information relating to a whole range of aspects of a Target. The information relating to a whole range of aspects of a Target. The
general presence data model is described in [RFC4479] and caters for general presence data model is described in [RFC4479] and caters for
a presence document to describe different aspects of the reachability a presence document to describe different aspects of the reachability
of a presentity. Continuing this approach, a presence document may of a presentity. Continuing this approach, a presence document may
contain several GEOPRIV objects that specify different locations and contain several GEOPRIV objects that specify different locations and
aspects of reachability relating to a presentity. This degree of aspects of reachability relating to a presentity. This degree of
flexibility is important, and recommendations in this document make flexibility is important, and recommendations in this document make
skipping to change at page 6, line 39 skipping to change at page 6, line 39
location chunk #n location chunk #n
<usage-rules> <usage-rules>
</geopriv> </geopriv>
<geopriv> -- #2 <geopriv> -- #2
<geopriv> -- #3 <geopriv> -- #3
... ...
<geopriv> -- #m <geopriv> -- #m
</status> </status>
</tuple> </tuple>
<device> <device>
<status>
<geopriv> -- #1 <geopriv> -- #1
<location-info> <location-info>
location chunk #1 location chunk #1
location chunk #2 location chunk #2
... ...
location chunk #n location chunk #n
<usage-rules> <usage-rules>
</geopriv> </geopriv>
<geopriv> -- #2 <geopriv> -- #2
<geopriv> -- #3 <geopriv> -- #3
... ...
<geopriv> -- #m <geopriv> -- #m
</status>
</device> </device>
<person> <person>
<status>
<geopriv> -- #1 <geopriv> -- #1
<location-info> <location-info>
location chunk #1 location chunk #1
location chunk #2 location chunk #2
... ...
location chunk #n location chunk #n
<usage-rules> <usage-rules>
</geopriv> </geopriv>
<geopriv> -- #2 <geopriv> -- #2
<geopriv> -- #3 <geopriv> -- #3
... ...
<geopriv> -- #m <geopriv> -- #m
</status>
</person> </person>
<tuple> -- #2 <tuple> -- #2
<device> -- #2 <device> -- #2
<person> -- #2 <person> -- #2
... ...
<tuple> -- #o <tuple> -- #o
</presence> </presence>
Figure 1: Structure of a PIDF-LO Document Figure 1: Structure of a PIDF-LO Document
skipping to change at page 7, line 43 skipping to change at page 7, line 39
Emergency Number Association (NENA) in trying to solve these Emergency Number Association (NENA) in trying to solve these
ambiguities led to a set of conventions being adopted. These rules ambiguities led to a set of conventions being adopted. These rules
do not have any particular order, but should be followed by creators do not have any particular order, but should be followed by creators
and consumers of location information contained in a PIDF-LO to and consumers of location information contained in a PIDF-LO to
ensure that a consistent interpretation of the data can be achieved. ensure that a consistent interpretation of the data can be achieved.
Rule #1: A <geopriv> element MUST describe a discrete location. Rule #1: A <geopriv> element MUST describe a discrete location.
Rule #2: Where a discrete location can be uniquely described in more Rule #2: Where a discrete location can be uniquely described in more
than one way, each location description SHOULD reside in a than one way, each location description SHOULD reside in a
separate <tuple>, <device>, or <person> element. separate <tuple>, <device>, or <person> element; only one geopriv
element per tuple.
Rule #3: Providing more than one <geopriv> element in a single Rule #3: Providing more than one <geopriv> element in a single
presence document (PIDF) MUST only be done if the locations refer presence document (PIDF) MUST only be done if the locations refer
to the same place or are put into different element types. For to the same place or are put into different element types. For
example, one location in a <tuple>, a second location in a example, one location in a <tuple>, a second location in a
<device> element, and a third location in a <person> element. <device> element, and a third location in a <person> element.
This may occur if a Target's location is determined using a This may occur if a Target's location is determined using a
series of different techniques, or the Target wishes to series of different techniques, or the Target wishes to
represent her location as well as the location of her PC. In represent her location as well as the location of her PC. In
skipping to change at page 10, line 13 skipping to change at page 10, line 13
resulting compound location information is shown in Figure 2. resulting compound location information is shown in Figure 2.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
entity="pres:mike@seattle.example.com"> entity="pres:mike@seattle.example.com">
<dm:device id="mikepc"> <dm:device id="mikepc">
<status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"> <gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-43.5723 153.21760</gml:pos> <gml:pos>-43.5723 153.21760</gml:pos>
</gml:Point> </gml:Point>
<cl:civicAddress> <cl:civicAddress>
<cl:FLR>2</cl:FLR> <cl:FLR>2</cl:FLR>
</cl:civicAddress> </cl:civicAddress>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<method>Wiremap</method> <method>Wiremap</method>
</gp:geopriv> </gp:geopriv>
</status>
<timestamp>2007-06-22T20:57:29Z</timestamp> <timestamp>2007-06-22T20:57:29Z</timestamp>
<dm:deviceID>mac:8asd7d7d70cf</dm:deviceID> <dm:deviceID>mac:8a-sd-7d-7d-70-cf</dm:deviceID>
</dm:device> </dm:device>
</presence> </presence>
Figure 2 Figure 2
3.3. Manual/Automatic Configuration of Location Information 3.3. Manual/Automatic Configuration of Location Information
Loraine has a predefined civic location stored in her laptop, since Loraine has a predefined civic location stored in her laptop, since
she normally lives in Sydney, the address is for her Sydney-based she normally lives in Sydney, the address is for her Sydney-based
apartment. Loraine decides to visit sunny San Francisco, and when apartment. Loraine decides to visit sunny San Francisco, and when
skipping to change at page 11, line 22 skipping to change at page 11, line 22
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
entity="pres:ness@example.com"> entity="pres:ness@example.com">
<dm:device id="nesspc-1"> <dm:device id="nesspc-1">
<status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326"> <gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-34.410649 150.87651</gml:pos> <gml:pos>-34.410649 150.87651</gml:pos>
<gs:radius uom="urn:ogc:def:uom:EPSG::9001"> <gs:radius uom="urn:ogc:def:uom:EPSG::9001">
30 30
</gs:radius> </gs:radius>
</gs:Circle> </gs:Circle>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<method>GPS</method> <method>GPS</method>
</gp:geopriv> </gp:geopriv>
</status>
<timestamp>2007-06-22T20:57:29Z</timestamp> <timestamp>2007-06-22T20:57:29Z</timestamp>
<dm:deviceID>mac:1234567890ab</dm:deviceID> <dm:deviceID>mac:12-34-56-78-90-ab</dm:deviceID>
</dm:device> </dm:device>
<dm:person id="ness"> <dm:person id="ness">
<status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<civicAddress xml:lang="en-AU"> <civicAddress xml:lang="en-AU">
<country>AU</country> <country>AU</country>
<A1>NSW</A1> <A1>NSW</A1>
<A3> Wollongong <A3>Wollongong</A3>
</A3><A4>North Wollongong <A4>North Wollongong</A4>
</A4>
<RD>Flinders</RD><STS>Street</STS> <RD>Flinders</RD><STS>Street</STS>
<RDBR>Campbell Street</RDBR> <RDBR>Campbell Street</RDBR>
<LMK> <LMK>
Gilligan's Island Gilligan's Island
</LMK> <LOC>Corner</LOC> </LMK>
<LOC>Corner</LOC>
<NAM> Main Bank </NAM> <NAM> Main Bank </NAM>
<PC>2500</PC> <PC>2500</PC>
<ROOM> 398 </ROOM> <ROOM> 398 </ROOM>
<PLC>store</PLC> <PLC>store</PLC>
<POBOX>Private Box 15</POBOX> <POBOX>Private Box 15</POBOX>
</civicAddress> </civicAddress>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<method>Manual</method> <method>Manual</method>
</gp:geopriv> </gp:geopriv>
</status>
<timestamp>2007-06-24T12:28:04Z</timestamp> <timestamp>2007-06-24T12:28:04Z</timestamp>
</dm:person> </dm:person>
</presence> </presence>
Figure 3 Figure 3
4. Geodetic Coordinate Representation 4. Geodetic Coordinate Representation
The geodetic examples provided in RFC 4119 [RFC4119] are illustrated The geodetic examples provided in RFC 4119 [RFC4119] are illustrated
using the <gml:location> element, which uses the <gml:coordinates> using the <gml:location> element, which uses the <gml:coordinates>
skipping to change at page 16, line 34 skipping to change at page 16, line 34
Figure 4 shows a 2d point: Figure 4 shows a 2d point:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
entity="pres:point2d@example.com"> entity="pres:point2d@example.com">
<dm:device id="point2d"> <dm:device id="point2d">
<status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"> <gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-34.407 150.883</gml:pos> <gml:pos>-34.407 150.883</gml:pos>
</gml:Point> </gml:Point>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<method>Wiremap</method> <method>Wiremap</method>
</gp:geopriv> </gp:geopriv>
</status>
<timestamp>2007-06-22T20:57:29Z</timestamp> <timestamp>2007-06-22T20:57:29Z</timestamp>
<dm:deviceID>mac:1234567890ab</dm:deviceID> <dm:deviceID>mac:12-34-56-78-90-ab</dm:deviceID>
</dm:device> </dm:device>
</presence> </presence>
Figure 4 Figure 4
Figure 5 shows a 3d point: Figure 5 shows a 3d point:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:gml="http://www.opengis.net/gml" xmlns:gml="http://www.opengis.net/gml"
entity="pres:point3d@example.com"> entity="pres:point3d@example.com">
<dm:device id="point3d"> <dm:device id="point3d">
<status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4979" <gml:Point srsName="urn:ogc:def:crs:EPSG::4979"
xmlns:gml="http://www.opengis.net/gml"> xmlns:gml="http://www.opengis.net/gml">
<gml:pos>-34.407 150.883 24.8</gml:pos> <gml:pos>-34.407 150.883 24.8</gml:pos>
</gml:Point> </gml:Point>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<method>Wiremap</method> <method>Wiremap</method>
</gp:geopriv> </gp:geopriv>
</status>
<timestamp>2007-06-22T20:57:29Z</timestamp> <timestamp>2007-06-22T20:57:29Z</timestamp>
<dm:deviceID>mac:1234567890ab</dm:deviceID> <dm:deviceID>mac:12-34-56-78-90-ab</dm:deviceID>
</dm:device> </dm:device>
</presence> </presence>
Figure 5 Figure 5
5.2.2. Polygon 5.2.2. Polygon
The polygon shape may be used to represent a building outline or The polygon shape may be used to represent a building outline or
coverage area. The first and last points of the polygon have to be coverage area. The first and last points of the polygon have to be
the same. For example, looking at the hexagon in Figure 6 with the same. For example, looking at the hexagon in Figure 6 with
skipping to change at page 32, line 24 skipping to change at page 32, line 24
[RFC4479] Rosenberg, J., "A Data Model for Presence", RFC 4479, [RFC4479] Rosenberg, J., "A Data Model for Presence", RFC 4479,
July 2006. July 2006.
[GeoShape] [GeoShape]
Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape
Application Schema for use by the Internet Engineering Application Schema for use by the Internet Engineering
Task Force (IETF)", Candidate OpenGIS Implementation Task Force (IETF)", Candidate OpenGIS Implementation
Specification 06-142r1, Version: 1.0, April 2007. Specification 06-142r1, Version: 1.0, April 2007.
[I-D.ietf-geopriv-revised-civic-lo] [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location
Thomson, M. and J. Winterbottom, "Revised Civic Location Format for Presence Information Data Format Location
Format for PIDF-LO", Object (PIDF-LO)", RFC 5139, February 2008.
draft-ietf-geopriv-revised-civic-lo-07 (work in progress),
December 2007.
9.2. Informative References 9.2. Informative References
[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
(DHCPv4 and DHCPv6) Option for Civic Addresses (DHCPv4 and DHCPv6) Option for Civic Addresses
Configuration Information", RFC 4776, November 2006. Configuration Information", RFC 4776, November 2006.
[RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and
J. Polk, "Geopriv Requirements", RFC 3693, February 2004. J. Polk, "Geopriv Requirements", RFC 3693, February 2004.
skipping to change at page 34, line 44 skipping to change at line 1149
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 27 change blocks. 
42 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/