draft-ietf-geopriv-loc-filters-01.txt   draft-ietf-geopriv-loc-filters-02.txt 
WG R. Mahy geopriv R. Mahy
Internet-Draft Plantronics Internet-Draft Plantronics
Intended status: Standards Track March 4, 2007 Intended status: Standards Track B. Rosen
Expires: September 5, 2007 Expires: January 15, 2009 NeuStar
July 14, 2008
A Document Format for Filtering and Reporting Location Notications in A Document Format for Filtering and Reporting Location Notications in
the Presence Information Document Format Location Object (PIDF-LO) the Presence Information Document Format Location Object (PIDF-LO)
draft-ietf-geopriv-loc-filters-01.txt draft-ietf-geopriv-loc-filters-02
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 35 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 September 5, 2007. This Internet-Draft will expire on January 15, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes filters which limit asynchronous location This document describes filters which limit asynchronous location
notifications to compelling events. The resulting location notifications to compelling events. The resulting location
information is conveyed in existing location formats wrapped in information is conveyed in existing location formats wrapped in
GEOPRIV privacy extensions to the Presence Information Document GEOPRIV privacy extensions to the Presence Information Document
Format (PIDF-LO). Location disclosure is limited to voluntary Format (PIDF-LO)
disclosure by a notifier that possesses credentials for the named
resource.
Table of Contents Table of Contents
1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Definition of Location Filter Format . . . . . . . . . . . . . 3 3. Definition of Location Filter Format . . . . . . . . . . . . . 3
3.1. Horizontal and Vertical Movement . . . . . . . . . . . . . 4 3.1. Horizontal and Vertical Movement . . . . . . . . . . . . . 4
3.2. Changes in value . . . . . . . . . . . . . . . . . . . . . 5 3.2. Changes in value . . . . . . . . . . . . . . . . . . . . . 5
3.3. Containment Within a Region . . . . . . . . . . . . . . . 6 3.3. Containment Within a Region . . . . . . . . . . . . . . . 6
3.4. XML Schema for filter format . . . . . . . . . . . . . . . 9 3.4. Rate Control . . . . . . . . . . . . . . . . . . . . . . . 9
4. Containment schema . . . . . . . . . . . . . . . . . . . . . . 10 3.5. XML Schema for filter format . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 4. Containment schema . . . . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
6.1. MIME Registration for 6.1. MIME Registration for
application/location-delta-filter+xml . . . . . . . . . . 13 application/location-delta-filter+xml . . . . . . . . . . 15
6.2. URN Sub-Namespace Registration for 6.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:location-filter . . . . . . . . . . 13 urn:ietf:params:xml:ns:location-filter . . . . . . . . . . 15
6.3. Schema Registration For location-filter . . . . . . . . . 14 6.3. Schema Registration For location-filter . . . . . . . . . 16
6.4. URN Sub-Namespace Registration for 6.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:pidf:geopriv10:containment . . . . 14 urn:ietf:params:xml:ns:pidf:geopriv10:containment . . . . 16
6.5. Schema Registration For containment . . . . . . . . . . . 15 6.5. Schema Registration For containment . . . . . . . . . . . 17
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.2. Informational References . . . . . . . . . . . . . . . . . 16 8.2. Informational References . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 17 Intellectual Property and Copyright Statements . . . . . . . . . . 20
1. Conventions 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [2]. document are to be interpreted as described in RFC-2119 [RFC2119].
2. Overview 2. Overview
Conveying static location in PIDF-LO [1] bodies is straightforward. Conveying static location in PIDF-LO [RFC4119] bodies is
However the difficult part about asynchronous notification of straightforward. However the difficult part about asynchronous
location information is that many forms of location are measured as a notification of location information is that many forms of location
continuous gradient. Unlike notifications using discreet quantities, are measured as a continuous gradient. Unlike notifications using
it is difficult to know when a change in location is large enough to discreet quantities, it is difficult to know when a change in
warrant a notification. Moreover, different applications require a location is large enough to warrant a notification. Moreover,
wide variety of location resolutions. Any optimization made for one different applications require a wide variety of location
application would ultimately result in wasteful polling or a sluggish resolutions. Any optimization made for one application would
user interface for other applications. ultimately result in wasteful polling or a sluggish user interface
for other applications.
The mechanism described here defines filters in XML [3] documents The mechanism described here defines filters in XML [W3C.REC-xml]
which limit location notification to events which are of relevance to documents which limit location notification to events which are of
the subscriber. These filters persist until they are changed with a relevance to the subscriber. These filters persist until they are
replacement filter. changed with a replacement filter.
In addition to the relevant filters, this document also defines a new In addition to the relevant filters, this document also defines a new
XML schema [4] which can be included in PIDF-LO documents to indicate XML schema [W3C.REC-xmlschema-1] which can be included in PIDF-LO
that the resource is inside or outside of a container region. documents to indicate that the resource is inside or outside of a
container region.
3. Definition of Location Filter Format 3. Definition of Location Filter Format
The granularity of notifications necessary for various geographic The granularity of notifications necessary for various geographic
location applications varies dramatically. The subscriber should be location applications varies dramatically. The subscriber should be
able to get asynchronous notifications with appropriate granularity able to get asynchronous notifications with appropriate granularity
and accuracy, without having to poll or flood the network with and accuracy, without having to poll or flood the network with
notifications which are not important to the application. notifications which are not important to the application.
Notifications should only happen when the notification would be Notifications should only happen when the notification would be
considered an Interesting Event to the subscriber. This section of considered an Interesting Event to the subscriber. This section of
this document defines an XML filter format to describe interesting this document defines an XML filter format to describe interesting
conditions or events. The terminal elements in this format are conditions or events. The terminal elements in this format are
defined in terms of existing Geographic Markup Language (GML) [9] defined in terms of existing Geographic Markup Language (GML) [GML]
data types. data types or civic address elements.
This document also defines a MIME type for this location filter This document also defines a MIME type for this location filter
format: application/location-delta-filter+xml. format: application/location-delta-filter+xml.
This document defines the following as an initial list of Interesting This document defines the following as an initial list of Interesting
Events: Events:
1. the resource moves more than a specific distance horizontally or 1. the resource moves more than a specific distance horizontally or
vertically since the last notification vertically since the last notification
2. the resource exceeds a specific speed 2. the resource exceeds a specific speed
3. the resource enters or exits one or more GML objects (for 3. the resource enters or exits one or more GML objects (for
example, a set of 2-dimensional or 3-dimensional regions) example, a set of 2-dimensional or 3-dimensional regions)
included or referenced in the filter. included or referenced in the filter.
4. one or more of the values of the specified address labels has 4. one or more of the values of the specified address labels has
changed for the resource (for example, the A1 value of the changed for the resource (for example, the A1 value of the
civilAddress has changed from California to Nevada) civilAddress has changed from California to Nevada)
This specification makes use of XML namespaces [5] for identifying 5. a mininum and maximum rate of reports regardless of movement
location filter documents and document fragments. The namespace URI This specification makes use of XML namespaces [W3C.REC-xml-names]
for elements defined by this specification is a URN [10], using the for identifying location filter documents and document fragments.
namespace identifier 'ietf' defined by [11] and extended by [12]. The namespace URI for elements defined by this specification is a URN
This URN is: [RFC2141], using the namespace identifier 'ietf' defined by [RFC2648]
and extended by [RFC3688]. This URN is:
urn:ietf:params:xml:ns:location-filter urn:ietf:params:xml:ns:location-filter
The filter format starts with a top-level XML element called The filter format starts with a top-level XML element called
"<location-filter>", which contains one or more filter events. The "<location-filter>", which contains one or more filter events. The
semantics of multiple elements inside a location-filter is a logical semantics of multiple elements inside a location-filter generally is
OR. In other words, if any of the individual filter events occurs, a logical OR. In other words, if any of the individual filter events
the event satisfies the location-filter and triggers a notification. occurs, the event satisfies the location-filter and triggers a
notification. However the "maxRate" parameter is a logical AND, and
will limit events that otherwise would have been reported.
3.1. Horizontal and Vertical Movement 3.1. Horizontal and Vertical Movement
The movedHoriz and movedVert filter events each indicate a minimum The movedHoriz and movedVert filter events each indicate a minimum
horizontal motion or vertical distance (respectively) that the horizontal motion or vertical distance (respectively) that the
resource must have moved from the location of the resource when the resource must have moved from the location of the resource when the
last notification was sent in order to trigger this event. The last notification was sent in order to trigger this event. The
distance is measured absolutely from the point of last notification distance is measured absolutely from the point of last notification
rather than in terms of cumulative motion (For example, someone rather than in terms of cumulative motion (For example, someone
pacing inside a room will not trigger an event if the trigger pacing inside a room will not trigger an event if the trigger
skipping to change at page 5, line 22 skipping to change at page 5, line 29
If the resource exceeds 3 meters per second (10.8 km/h), send a If the resource exceeds 3 meters per second (10.8 km/h), send a
notification: notification:
<location-filter> <location-filter>
<speedExceeds uom="#mps">3</speedExceeds> <speedExceeds uom="#mps">3</speedExceeds>
</location-filter> </location-filter>
3.2. Changes in value 3.2. Changes in value
The valueChanges filter event contains a string which is interpreted The valueChanges filter event contains a string which is interpreted
as an XPath [6] expression evaluated within the context of the as an XPath [W3C.xpath] expression evaluated within the context of
location-info element of the PIDF-LO document which would be the location-info element of the PIDF-LO document which would be
generated by the notification. The XPath expression MUST evaluate to generated by the notification. The XPath expression MUST evaluate to
only a single Xpath node. If the value of any of the elements in the only a single Xpath node. If the value of any of the elements in the
resulting node changes, then the filter event is triggered. Note resulting node changes, then the filter event is triggered. Note
that the value of the resulting node changes if any of those nodes or that the value of the resulting node changes if any of those nodes or
subnodes transitions from having a value to having no value or vice subnodes transitions from having a value to having no value or vice
versa. A location-filter may contain multiple valueChanges filters. versa. A location-filter may contain multiple valueChanges filters.
Note that the example below needs to be updated to use the revised
civic location format.
For example, given the following logical PIDF-LO document, If the For example, given the following logical PIDF-LO document, If the
state (A1), county (A2), city (A3), or postal code (PC) changes, send state (A1), county (A2), city (A3), or postal code (PC) changes, send
a notification: a notification:
PIDF-LO Location Document: PIDF-LO Location Document:
<?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: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:civilLoc" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc"
entity="pres:geotarget@example.com"> entity="pres:geotarget@example.com">
<tuple id="sg89ae"> <tuple id="sg89ae">
<status> <status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<cl:civilAddress> <cl:civilAddress>
<cl:country>US</cl:country> <cl:country>US</cl:country>
<cl:A1>New York</cl:A1> <cl:A1>NY</cl:A1>
<cl:A3>New York</cl:A3> <cl:A3>New York</cl:A3>
<cl:A6>Broadway</cl:A6> <cl:RD>Broadway</cl:RD>
<cl:HNO>123</cl:HNO> <cl:HNO>123</cl:HNO>
<cl:LOC>Suite 75</cl:LOC> <cl:UNIT>Suite 75</cl:UNIT>
<cl:PC>10027</cl:PC> <cl:PC>10027</cl:PC>
</cl:civilAddress> </cl:civilAddress>
</gp:location-info> </gp:location-info>
<gp:usage-rules> <gp:usage-rules>
<gp:retransmission-allowed>yes</gp:retransmission-allowed> <gp:retransmission-allowed>yes</gp:retransmission-allowed>
<gp:retention-expiry>2003-06-23T04:57:29Z <gp:retention-expiry>2003-06-23T04:57:29Z
</gp:retention-expiry> </gp:retention-expiry>
</gp:usage-rules> </gp:usage-rules>
</gp:geopriv> </gp:geopriv>
</status> </status>
skipping to change at page 6, line 48 skipping to change at page 6, line 48
xmlns="urn:ietf:params:xml:ns:location-filter" xmlns="urn:ietf:params:xml:ns:location-filter"
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc"> xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc">
<valueChanges>cl:civilAddress/cl:A1</valueChanges> <valueChanges>cl:civilAddress/cl:A1</valueChanges>
<valueChanges>cl:civilAddress/cl:A2</valueChanges> <valueChanges>cl:civilAddress/cl:A2</valueChanges>
<valueChanges>cl:civilAddress/cl:A3</valueChanges> <valueChanges>cl:civilAddress/cl:A3</valueChanges>
<valueChanges>cl:civilAddress/cl:PC</valueChanges> <valueChanges>cl:civilAddress/cl:PC</valueChanges>
</location-filter> </location-filter>
3.3. Containment Within a Region 3.3. Containment Within a Region
Finally, the "enterOrExit" filter event is satisfied when the The "enterOrExit" filter event is satisfied when the resource enters
resource enters or exits a named 2-dimensional or 3-dimensional or exits a named 2-dimensional or 3-dimensional region described by
region described by one of the shapes defined in [8]. These regions one of the shapes defined in section 5 of
can be defined using inline snippets of GML, or externally referenced [I-D.ietf-geopriv-pdif-lo-profile]. These regions can be defined
using a URI (Uniform Resource Identifier). using inline snippets of GML, or externally referenced using a URI
(Uniform Resource Identifier).
These regions need a unique name or identifier so location with These regions need a unique name or identifier so location with
respect to these regions can be described later (for example in a respect to these regions can be described later (for example in a
notification). These regions are currently described as GML notification). These regions are currently described as GML
Features so they can be named with a GML Name. Ideally each Features so they can be named with a GML Name. Ideally each
region could be described instead as a GML geometry with some region could be described instead as a GML geometry with some
associated name or identifier. associated name or identifier.
Any 2-dimensional region MUST be defined using the EPSG 4326 Any 2-dimensional region MUST be defined using the EPSG 4326
coordinate reference system. Any 3-dimensional region MUST be coordinate reference system. Any 3-dimensional region MUST be
defined using the EPSG 4979 coordinate reference system. A location- defined using the EPSG 4979 coordinate reference system. A location-
skipping to change at page 9, line 16 skipping to change at page 9, line 16
<enterOrExit> <enterOrExit>
<my:ParkingGarage <my:ParkingGarage
xlink:href="http://server.example.com/loc-defs/bldg-mgr/parking"/> xlink:href="http://server.example.com/loc-defs/bldg-mgr/parking"/>
</enterOrExit> </enterOrExit>
<enterOrExit> <enterOrExit>
<my:ConferenceRooms <my:ConferenceRooms
xlink:href="http://server.example.com/loc-defs/userdef/confrooms"/> xlink:href="http://server.example.com/loc-defs/userdef/confrooms"/>
</enterOrExit> </enterOrExit>
</location-filter> </location-filter>
3.4. XML Schema for filter format 3.4. Rate Control
The minRate and maxRate filters control the rate at which
notifications are sent. minRate can be used to make sure that a
notification is sent regardless of movement, and maxRate can be used
to limit the rate at which notifications are sent even when other
filters would cause many notifications. Each of these events can
only appear once in a location-filter. These events have an
attribute "uom" (for "units of measure"), which indicates the units
of the element. The default unit for these events is minutes. Rates
are averaged over one unit of the next larger unit of measure. For
example if the uom="minutes", then the rate is measured over one
hour.
Examples of minRate and maxRate:
<location-filter>
<movedHoriz uom="urn:ogc:def:uom:EPSG::9001">10</movedHoriz>
<minRate uom="seconds">1</minRate>
<maxRate uom="seconds">10</maxRate>
</location-filter>
This filter specifies that notifications should be sent if the target
moves by more than 10 meters, but no more than 5 notifications per
second should be sent. In addition, if the target is not moving fast
enough to generate notifications due to movedHoriz, then extra
notications are sent to achieve approximately 1 notification per
second averaged over a minute.
3.5. XML Schema for filter format
The XML Schema for this format is defined below. The XML Schema for this format is defined below.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:location-filter" targetNamespace="urn:ietf:params:xml:ns:location-filter"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml"> xmlns:gml="http://www.opengis.net/gml">
<xs:element name="location-filter"> <xs:element name="location-filter">
skipping to change at page 9, line 42 skipping to change at page 10, line 22
minOccurs="0" maxOccurs="1"/> minOccurs="0" maxOccurs="1"/>
<xs:element name="speedExceeds" type="gml:MeasureType" <xs:element name="speedExceeds" type="gml:MeasureType"
minOccurs="0" maxOccurs="1"/> minOccurs="0" maxOccurs="1"/>
<!-- this type needs to hold an XPath statement --> <!-- this type needs to hold an XPath statement -->
<xs:element name="valueChanges" type="xs:string" <xs:element name="valueChanges" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="enterOrExit" type="gml:FeaturePropertyType" <xs:element name="enterOrExit" type="gml:FeaturePropertyType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="minRate" type="xs:rate-spec"
<!-- Do we want to include this to allow new filters? --> minOccurs="0" maxOccurs="1"/>
<xs:element name="maxRate" type="xs:rate-spec"
minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:element name="rate-spec">
<xs:complexType>
<xs:sequence>
<xs:attribute name="uom" use="required">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="seconds"></xs:enumeration>
<xs:enumeration value="minutes"></xs:enumeration>
<xs:enumeration value="hours"></xs:enumeration>
<xs:enumeration value="days"></xs:enumeration>
<xs:enumeration value="weeks"></xs:enumeration>
<xs:enumeration value="years"></xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema> </xs:schema>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:location-filter" targetNamespace="urn:ietf:params:xml:ns:location-filter"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml"> xmlns:gml="http://www.opengis.net/gml">
<xs:element name="location-filter"> <xs:element name="location-filter">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
skipping to change at page 10, line 26 skipping to change at page 11, line 26
minOccurs="0" maxOccurs="1"/> minOccurs="0" maxOccurs="1"/>
<xs:element name="speedExceeds" type="gml:MeasureType" <xs:element name="speedExceeds" type="gml:MeasureType"
minOccurs="0" maxOccurs="1"/> minOccurs="0" maxOccurs="1"/>
<!-- this type needs to hold an XPath statement --> <!-- this type needs to hold an XPath statement -->
<xs:element name="valueChanges" type="xs:string" <xs:element name="valueChanges" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="enterOrExit" type="gml:FeaturePropertyType" <xs:element name="enterOrExit" type="gml:FeaturePropertyType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="minRate" type="xs:rate-spec"
<!-- Do we want to include this to allow new filters? --> minOccurs="0" maxOccurs="1"/>
<xs:element name="maxRate" type="xs:rate-spec"
minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:element name="rate-spec">
<xs:complexType>
<xs:sequence>
<xs:attribute name="uom" use="required">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="seconds"></xs:enumeration>
<xs:enumeration value="minutes"></xs:enumeration>
<xs:enumeration value="hours"></xs:enumeration>
<xs:enumeration value="days"></xs:enumeration>
<xs:enumeration value="weeks"></xs:enumeration>
<xs:enumeration value="years"></xs:enumeration>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema> </xs:schema>
4. Containment schema 4. Containment schema
This section describes a schema for describing the resource's This section describes a schema for describing the resource's
location relative to a region or list of regions which might contain location relative to a region or list of regions which might contain
the resource. (These regions can be defined dynamically in an the resource. (These regions can be defined dynamically in an
"enterOrExit" element in a subscription filter, or defined on the "enterOrExit" element in a subscription filter, or defined on the
notifier using some out-of-band mechanism.) The "pidfResource" notifier using some out-of-band mechanism.) The "pidfResource"
element is placed inside the location-info element in a PIDF-LO element is placed inside the location-info element in a PIDF-LO
skipping to change at page 13, line 6 skipping to change at page 14, line 48
</tuple> </tuple>
</presence> </presence>
5. Security Considerations 5. Security Considerations
Location information is typically very privacy sensitive. As such, Location information is typically very privacy sensitive. As such,
GEOPRIV requires that notifications MUST be encrypted and integrity GEOPRIV requires that notifications MUST be encrypted and integrity
protected. protected.
Additional privacy and security considerations are discussed in Additional privacy and security considerations are discussed in
detail in [7]. detail in [I-D.ietf-geopriv-pdif-lo-profile].
6. IANA Considerations 6. IANA Considerations
6.1. MIME Registration for application/location-delta-filter+xml 6.1. MIME Registration for application/location-delta-filter+xml
MIME media type name: application MIME media type name: application
MIME subtype name: application/location-delta-filter+xml MIME subtype name: application/location-delta-filter+xml
Required parameters: none. Required parameters: none.
skipping to change at page 13, line 46 skipping to change at page 15, line 43
1. Magic number(s): N/A 1. Magic number(s): N/A
2. File extension(s): N/A 2. File extension(s): N/A
3. Macintosh file type code: N/A 3. Macintosh file type code: N/A
6.2. URN Sub-Namespace Registration for 6.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:location-filter urn:ietf:params:xml:ns:location-filter
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
[12]. [RFC3688].
URI: The URI for this namespace is URI: The URI for this namespace is
urn:ietf:params:xml:ns:location-filter. urn:ietf:params:xml:ns:location-filter.
Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>, Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>,
as delegated by the IESG <iesg@ietf.org>. as delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
skipping to change at page 14, line 29 skipping to change at page 16, line 27
<body> <body>
<h1>Namespace for PIDF-LO Location Filters</h1> <h1>Namespace for PIDF-LO Location Filters</h1>
<h2>urn:ietf:params:xml:ns:location-filter</h2> <h2>urn:ietf:params:xml:ns:location-filter</h2>
<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p> <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
6.3. Schema Registration For location-filter 6.3. Schema Registration For location-filter
This specification registers a schema, as per the guidelines in [12]. This specification registers a schema, as per the guidelines in
[RFC3688].
URI: please assign. URI: please assign.
Registrant Contact: IETF, GEOPRIV Working Group Registrant Contact: IETF, GEOPRIV Working Group
(geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org). (geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org).
XML: The XML can be found as the sole content of Section 3.4. XML: The XML can be found as the sole content of Section 3.5.
6.4. URN Sub-Namespace Registration for 6.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:pidf:geopriv10:containment urn:ietf:params:xml:ns:pidf:geopriv10:containment
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
[12]. [RFC3688].
URI: The URI for this namespace is URI: The URI for this namespace is
urn:ietf:params:xml:ns:pidf:geopriv10:containment. urn:ietf:params:xml:ns:pidf:geopriv10:containment.
Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>, Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>,
as delegated by the IESG <iesg@ietf.org>. as delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
skipping to change at page 15, line 25 skipping to change at page 17, line 25
<body> <body>
<h1>Namespace for PIDF-LO location containment elements</h1> <h1>Namespace for PIDF-LO location containment elements</h1>
<h2>urn:ietf:params:xml:ns:pidf:geopriv10:containment</h2> <h2>urn:ietf:params:xml:ns:pidf:geopriv10:containment</h2>
<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p> <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
6.5. Schema Registration For containment 6.5. Schema Registration For containment
This specification registers a schema, as per the guidelines in [12]. This specification registers a schema, as per the guidelines in
[RFC3688].
URI: please assign. URI: please assign.
Registrant Contact: IETF, GEOPRIV Working Group Registrant Contact: IETF, GEOPRIV Working Group
(geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org). (geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org).
XML: The XML can be found as the sole content of Section 4. XML: The XML can be found as the sole content of Section 4.
7. Acknowledgments 7. Acknowledgments
Thanks to Allan Thompson, James Winterbottom, and Martin Thomson for Thanks to Allan Thompson, James Winterbottom, and Martin Thomson for
their comments. their comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[1] Peterson, J., "A Presence-based GEOPRIV Location Object [GML] OpenGIS, "Open Geography Markup Language (GML)
Format", RFC 4119, December 2005. Implementation Specification", OpenGIS OGC 02-023r4,
January 2003,
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement <http://www.opengis.org/techno/implementation.htm>.
Levels", BCP 14, RFC 2119, March 1997.
[3] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, [I-D.ietf-geopriv-pdif-lo-profile]
"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
October 2000, <http://www.w3.org/TR/REC-xml>. PIDF-LO Usage Clarification, Considerations and
Recommendations", draft-ietf-geopriv-pdif-lo-profile-11
(work in progress), February 2008.
[4] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001, Requirement Levels", BCP 14, RFC 2119, March 1997.
<http://www.w3.org/TR/xmlschema-1/>.
[5] Bray, T., Hollander, D., and A. Layman, "Namespaces in XML", [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
W3C REC-xml-names, January 1999, Format", RFC 4119, December 2005.
<http://www.w3.org/TR/REC-xml-names>.
[6] Clark, J. and S. DeRose, "XML Path Language (XPath) Version [W3C.REC-xml]
1.0", W3C Recommendation xpath, November 1999, Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler,
<http://www.w3.org/TR/xpath>. "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-
xml, October 2000, <http://www.w3.org/TR/REC-xml>.
[7] Tschofenig, H., "GEOPRIV PIDF-LO Usage Clarification, [W3C.REC-xml-names]
Considerations and Recommendations", Bray, T., Hollander, D., and A. Layman, "Namespaces in
draft-ietf-geopriv-pdif-lo-profile-05 (work in progress), XML", W3C REC-xml-names, January 1999,
October 2006. <http://www.w3.org/TR/REC-xml-names>.
[8] Thomson, M., "Geodetic Shapes for the Representation of [W3C.REC-xmlschema-1]
Uncertainty in PIDF-LO", draft-thomson-geopriv-geo-shape-03 Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
(work in progress), December 2006. "XML Schema Part 1: Structures", W3C REC-xmlschema-1,
May 2001, <http://www.w3.org/TR/xmlschema-1/>.
[9] OpenGIS, "Open Geography Markup Language (GML) Implementation [W3C.xpath]
Specification", OpenGIS OGC 02-023r4, January 2003, Clark, J. and S. DeRose, "XML Path Language (XPath)
<http://www.opengis.org/techno/implementation.htm>. Version 1.0", W3C Recommendation xpath, November 1999,
<http://www.w3.org/TR/xpath>.
8.2. Informational References 8.2. Informational References
[10] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[11] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, [RFC2648] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
August 1999. August 1999.
[12] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
Author's Address Authors' Addresses
Rohan Mahy Rohan Mahy
Plantronics Plantronics
345 Encincal Street 345 Encincal Street
Santa Cruz, CA Santa Cruz, CA
USA USA
Email: rohan@ekabal.com Email: rohan@ekabal.com
Brian Rosen
NeuStar
470 Conrad Dr.
Mars, PA 16046
US
Phone: +1 724 382 1051
Email: br@brianrosen.net
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 17, line 44 skipping to change at line 835
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. 51 change blocks. 
111 lines changed or deleted 195 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/