draft-ietf-geopriv-loc-filters-02.txt   draft-ietf-geopriv-loc-filters-03.txt 
geopriv R. Mahy geopriv R. Mahy
Internet-Draft Plantronics Internet-Draft Plantronics
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: January 15, 2009 NeuStar Expires: May 7, 2009 NeuStar
July 14, 2008 November 3, 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-02 draft-ietf-geopriv-loc-filters-03
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 January 15, 2009. This Internet-Draft will expire on May 7, 2009.
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) Format (PIDF-LO)
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. Rate Control . . . . . . . . . . . . . . . . . . . . . . . 9 3.4. Rate Control . . . . . . . . . . . . . . . . . . . . . . . 9
3.5. XML Schema for filter format . . . . . . . . . . . . . . . 9 3.5. XML Schema for filter format . . . . . . . . . . . . . . . 9
4. Containment schema . . . . . . . . . . . . . . . . . . . . . . 12 4. Containment schema . . . . . . . . . . . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6.1. MIME Registration for 6.1. MIME Registration for
application/location-delta-filter+xml . . . . . . . . . . 15 application/location-delta-filter+xml . . . . . . . . . . 16
6.2. URN Sub-Namespace Registration for 6.2. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:location-filter . . . . . . . . . . 15 urn:ietf:params:xml:ns:location-filter . . . . . . . . . . 16
6.3. Schema Registration For location-filter . . . . . . . . . 16 6.3. Schema Registration For location-filter . . . . . . . . . 17
6.4. URN Sub-Namespace Registration for 6.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:pidf:geopriv10:containment . . . . 16 urn:ietf:params:xml:ns:pidf:geopriv10:containment . . . . 17
6.5. Schema Registration For containment . . . . . . . . . . . 17 6.5. Schema Registration For containment . . . . . . . . . . . 18
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17 8.1. Normative References . . . . . . . . . . . . . . . . . . . 18
8.2. Informational References . . . . . . . . . . . . . . . . . 18 8.2. Informational References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 20 Intellectual Property and Copyright Statements . . . . . . . . . . 21
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 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
2. Overview 2. Overview
Conveying static location in PIDF-LO [RFC4119] bodies is Conveying static location in PIDF-LO [RFC4119] bodies is
skipping to change at page 9, line 18 skipping to change at page 9, line 18
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. Rate Control 3.4. Rate Control
The minRate and maxRate filters control the rate at which Although not part of the loc-filter function, the throttle mechanisms
notifications are sent. minRate can be used to make sure that a [I-D.niemi-sipping-event-throttle] can be used to control the rate of
notification is sent regardless of movement, and maxRate can be used notifications. The "throttle", "force" and "average" settings can
to limit the rate at which notifications are sent even when other filter notications by time
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 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">
skipping to change at page 12, line 7 skipping to change at page 11, line 34
<xs:enumeration value="weeks"></xs:enumeration> <xs:enumeration value="weeks"></xs:enumeration>
<xs:enumeration value="years"></xs:enumeration> <xs:enumeration value="years"></xs:enumeration>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:attribute> </xs:attribute>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:location-filter"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gml="http://www.opengis.net/gml">
<xs:element name="location-filter">
<xs:complexType>
<xs:sequence>
<xs:element name="movedHoriz" type="gml:MeasureType"
minOccurs="0" maxOccurs="1"/>
<xs:element name="movedVert" type="gml:MeasureType"
minOccurs="0" maxOccurs="1"/>
<xs:element name="speedExceeds" type="gml:MeasureType"
minOccurs="0" maxOccurs="1"/>
<!-- this type needs to hold an XPath statement -->
<xs:element name="valueChanges" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="enterOrExit" type="gml:FeaturePropertyType"
minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="minRate" type="xs:rate-spec"
minOccurs="0" maxOccurs="1"/>
<xs:element name="maxRate" type="xs:rate-spec"
minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</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>
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
document. The pidfResource element can contain zero or more document. The pidfResource element can contain zero or more
"containment" elements. Each containment element has a GML Feature "containment" elements. Each containment element has a GML Feature
skipping to change at page 17, line 50 skipping to change at page 18, line 50
8.1. Normative References 8.1. Normative References
[GML] OpenGIS, "Open Geography Markup Language (GML) [GML] OpenGIS, "Open Geography Markup Language (GML)
Implementation Specification", OpenGIS OGC 02-023r4, Implementation Specification", OpenGIS OGC 02-023r4,
January 2003, January 2003,
<http://www.opengis.org/techno/implementation.htm>. <http://www.opengis.org/techno/implementation.htm>.
[I-D.ietf-geopriv-pdif-lo-profile] [I-D.ietf-geopriv-pdif-lo-profile]
Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
PIDF-LO Usage Clarification, Considerations and PIDF-LO Usage Clarification, Considerations and
Recommendations", draft-ietf-geopriv-pdif-lo-profile-11 Recommendations", draft-ietf-geopriv-pdif-lo-profile-13
(work in progress), February 2008. (work in progress), September 2008.
[I-D.niemi-sipping-event-throttle]
Niemi, A., Kiss, K., and S. Loreto, "Session Initiation
Protocol (SIP) Event Notification Extension for
Notification Throttling",
draft-niemi-sipping-event-throttle-07 (work in progress),
October 2008.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. Format", RFC 4119, December 2005.
[W3C.REC-xml] [W3C.REC-xml]
Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler,
"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC- "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-
 End of changes. 10 change blocks. 
45 lines changed or deleted 80 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/