draft-ietf-geopriv-loc-filters-08.txt   draft-ietf-geopriv-loc-filters-09.txt 
GEOPRIV R. Mahy GEOPRIV R. Mahy
Internet-Draft Individual Internet-Draft Individual
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: May 12, 2010 NeuStar Expires: July 1, 2010 NeuStar
H. Tschofenig H. Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
November 8, 2009 December 28, 2009
Filtering Location Notifications in the Session Initiation Protocol Filtering Location Notifications in the Session Initiation Protocol
(SIP) (SIP)
draft-ietf-geopriv-loc-filters-08.txt draft-ietf-geopriv-loc-filters-09.txt
Abstract Abstract
This document describes filters that limit asynchronous location This document describes filters that limit asynchronous location
notifications to compelling events, designed as an extension to RFC notifications to compelling events, designed as an extension to RFC
4661, an XML-based format for event notification filtering, and based 4661, an XML-based format for event notification filtering, and based
on RFC 3856, the SIP presence event package. The resulting location on RFC 3856, the SIP presence event package. The resulting location
information is conveyed in existing location formats wrapped in the information is conveyed in existing location formats wrapped in the
Presence Information Data Format Location Object (PIDF-LO). Presence Information Data Format Location Object (PIDF-LO).
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 May 12, 2010. This Internet-Draft will expire on July 1, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 31 skipping to change at page 6, line 31
trigger this event. The distance MUST be measured in meters trigger this event. The distance MUST be measured in meters
absolutely from the point of last notification. The <moved> element absolutely from the point of last notification. The <moved> element
MUST NOT appear more than once as a child element of the <filter> MUST NOT appear more than once as a child element of the <filter>
element. element.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<filter-set <filter-set
xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns="urn:ietf:params:xml:ns:simple-filter"
xmlns:lf="urn:ietf:params:xml:ns:location-filter"> xmlns:lf="urn:ietf:params:xml:ns:location-filter">
<filter id="123" uri="sip:presentity@example.com"> <filter id="123" uri="sip:presentity@example.com">
<lf:moved>300</lf:moved> <trigger>
<lf:moved>300</lf:moved>
</trigger>
</filter> </filter>
</filter-set> </filter-set>
Figure 1: Movement Filter Example Figure 1: Movement Filter Example
3.2. Speed Changes 3.2. Speed Changes
Speed changes can be filtered with the help of RFC 4661 and the Speed changes can be filtered with the help of RFC 4661 and the
functionality provided in [I-D.singh-geopriv-pidf-lo-dynamic], which functionality provided in [I-D.singh-geopriv-pidf-lo-dynamic], which
extends the PIDF-LO with support for spatial orientation, speed, extends the PIDF-LO with support for spatial orientation, speed,
skipping to change at page 9, line 35 skipping to change at page 9, line 35
describes an area using a polygon. describes an area using a polygon.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<filter-set <filter-set
xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns="urn:ietf:params:xml:ns:simple-filter"
xmlns:lf="urn:ietf:params:xml:ns:location-filter" xmlns:lf="urn:ietf:params:xml:ns:location-filter"
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">
<filter id="123" uri="sip:presentity@example.com"> <filter id="123" uri="sip:presentity@example.com">
<lf:enterOrExit> <trigger>
<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326"> <lf:enterOrExit>
<gml:pos>42.5463 -73.2512</gml:pos> <gs:Circle
<gs:radius uom="urn:ogc:def:uom:EPSG::9001"> srsName="urn:ogc:def:crs:EPSG::4326">
850.24 <gml:pos>42.5463 -73.2512</gml:pos>
</gs:radius> <gs:radius
</gs:Circle> uom="urn:ogc:def:uom:EPSG::9001">
</lf:enterOrExit> 850.24
</gs:radius>
</gs:Circle>
</lf:enterOrExit>
</trigger>
</filter> </filter>
</filter-set> </filter-set>
Figure 5: <enterOrExit> Circle Filter Example Figure 5: <enterOrExit> Circle Filter Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<filter-set xmlns="urn:ietf:params:xml:ns:simple-filter" <filter-set
xmlns="urn:ietf:params:xml:ns:simple-filter"
xmlns:lf="urn:ietf:params:xml:ns:location-filter" xmlns:lf="urn:ietf:params:xml:ns:location-filter"
xmlns:gml="http://www.opengis.net/gml"> xmlns:gml="http://www.opengis.net/gml">
<filter id="123" uri="sip:presentity@example.com"> <filter id="123" uri="sip:presentity@example.com">
<lf:enterOrExit> <trigger>
<gml:Polygon srsName="urn:ogc:def:crs:EPSG::4326"> <lf:enterOrExit>
<gml:exterior> <gml:Polygon srsName="urn:ogc:def:crs:EPSG::4326">
<gml:LinearRing> <gml:exterior>
<gml:pos>43.311 -73.422</gml:pos> <!--A--> <gml:LinearRing>
<gml:pos>43.111 -73.322</gml:pos> <!--F--> <gml:pos>43.311 -73.422</gml:pos>
<gml:pos>43.111 -73.222</gml:pos> <!--E--> <!--A-->
<gml:pos>43.311 -73.122</gml:pos> <!--D--> <gml:pos>43.111 -73.322</gml:pos>
<gml:pos>43.411 -73.222</gml:pos> <!--C--> <!--F-->
<gml:pos>43.411 -73.322</gml:pos> <!--B--> <gml:pos>43.111 -73.222</gml:pos>
<gml:pos>43.311 -73.422</gml:pos> <!--A--> <!--E-->
</gml:LinearRing> <gml:pos>43.311 -73.122</gml:pos>
</gml:exterior> <!--D-->
</gml:Polygon> <gml:pos>43.411 -73.222</gml:pos>
</lf:enterOrExit> <!--C-->
<gml:pos>43.411 -73.322</gml:pos>
<!--B-->
<gml:pos>43.311 -73.422</gml:pos>
<!--A-->
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</lf:enterOrExit>
</trigger>
</filter> </filter>
</filter-set> </filter-set>
Figure 6: <enterOrExit> Polygon Filter Example Figure 6: <enterOrExit> Polygon Filter Example
3.5. Location Type 3.5. Location Type
The <locationType> element MAY be included as a child element of the The <locationType> element MAY be included as a child element of the
<filter> element and it contains a list of location information types <what> element and it contains a list of location information types
that are requested by the subscriber. The following list describes that are requested by the subscriber. The following list describes
the possible values: the possible values:
any: The Notifier SHOULD attempt to provide LI in all forms any: The Notifier SHOULD attempt to provide LI in all forms
available to it. available to it.
geodetic: The Notifier SHOULD return a location by value in the form geodetic: The Notifier SHOULD return a location by value in the form
of a geodetic location. of a geodetic location.
civic: The Notifier SHOULD return a location by value in the form of civic: The Notifier SHOULD return a location by value in the form of
a civic address. a civic address.
The Notifier SHOULD return the requested location type or types. The The Notifier SHOULD return the requested location type or types. The
location types the Notifier returns also depends on the setting of location types the Notifier returns also depends on the setting of
the optional "exact" attribute. If the 'exact' attribute is set to the optional 'exact' attribute. If the 'exact' attribute is set to
"true" then the Notifier MUST return either the requested location "true" then the Notifier MUST return either the requested location
type or no location information. The 'exact' attribute does not type or no location information. The 'exact' attribute does not
apply (is ignored) for a request for a location type of "any". apply (is ignored) for a request for a location type of "any".
In the case of a request for specific locationType(s) and the 'exact' In the case of a request for specific locationType(s) and the 'exact'
attribute is false, the Notifier MAY provide additional location attribute is "false", the Notifier MAY provide additional location
types, or it MAY provide alternative types if the request cannot be types, or it MAY provide alternative types if the request cannot be
satisfied for a requested location type. satisfied for a requested location type.
If the <locationType> element is absent, a value of "any" MUST be If the <locationType> element is absent, a value of "any" MUST be
assumed as the default. assumed as the default.
The Notifier SHOULD provide location in the response in the same The Notifier SHOULD provide location in the response in the same
order in which they were included in the "locationType" element in order in which they were included in the "locationType" element in
the request. Indeed, the primary advantage of including specific the request. Indeed, the primary advantage of including specific
location types in a request when the 'exact' attribute is set to location types in a request when the 'exact' attribute is set to
skipping to change at page 11, line 41 skipping to change at page 12, line 10
requested. requested.
An example is shown in Figure 7 that utilizes the <locationType> An example is shown in Figure 7 that utilizes the <locationType>
element with the 'exact' and the 'responseTime' attribute. element with the 'exact' and the 'responseTime' attribute.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<filter-set <filter-set
xmlns="urn:ietf:params:xml:ns:simple-filter" xmlns="urn:ietf:params:xml:ns:simple-filter"
xmlns:lf="urn:ietf:params:xml:ns:location-filter"> xmlns:lf="urn:ietf:params:xml:ns:location-filter">
<filter id="123" uri="sip:presentity@example.com"> <filter id="123" uri="sip:presentity@example.com">
<lf:locationType exact="true"> <what>
geodetic <lf:locationType exact="true"> geodetic
</lf:locationType> </lf:locationType>
</what>
</filter> </filter>
</filter-set> </filter-set>
Figure 7: <locationType> Filter Example Figure 7: <locationType> Filter Example
3.6. Rate Control 3.6. Rate Control
[I-D.ietf-sipcore-event-rate-control] defines an extension to the SIP [I-D.ietf-sipcore-event-rate-control] defines an extension to the SIP
events framework defining the following three "Event" header field events framework defining the following three "Event" header field
parameters that allow a subscriber to set a minimum, a maximum and an parameters that allow a subscriber to set a minimum, a maximum and an
skipping to change at page 14, line 14 skipping to change at page 14, line 14
4. XML Schema 4. XML 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:filter="urn:ietf:params:xml:ns:location-filter" xmlns:filter="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">
<!-- These elements are child elements of the RFC 4661
<filter> element.
-->
<xs:element name="enterOrExit" type="gml:GeometryPropertyType"/> <xs:element name="enterOrExit" type="gml:GeometryPropertyType"/>
<xs:element name="moved" type="filter:movedType"/> <xs:element name="moved" type="filter:movedType"/>
<xs:complexType name="movedType"> <xs:complexType name="movedType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="xs:double"> <xs:extension base="xs:double">
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
skipping to change at page 21, line 25 skipping to change at page 21, line 25
Barnes, R., Lepinski, M., Cooper, A., Morris, J., Barnes, R., Lepinski, M., Cooper, A., Morris, J.,
Tschofenig, H., and H. Schulzrinne, "An Architecture for Tschofenig, H., and H. Schulzrinne, "An Architecture for
Location and Location Privacy in Internet Applications", Location and Location Privacy in Internet Applications",
draft-ietf-geopriv-arch-01 (work in progress), draft-ietf-geopriv-arch-01 (work in progress),
October 2009. October 2009.
[I-D.ietf-sipcore-event-rate-control] [I-D.ietf-sipcore-event-rate-control]
Niemi, A., Kiss, K., and S. Loreto, "Session Initiation Niemi, A., Kiss, K., and S. Loreto, "Session Initiation
Protocol (SIP) Event Notification Extension for Protocol (SIP) Event Notification Extension for
Notification Rate Control", Notification Rate Control",
draft-ietf-sipcore-event-rate-control-00 (work in draft-ietf-sipcore-event-rate-control-01 (work in
progress), May 2009. progress), November 2009.
[I-D.singh-geopriv-pidf-lo-dynamic] [I-D.singh-geopriv-pidf-lo-dynamic]
Schulzrinne, H., Singh, V., Tschofenig, H., and M. Schulzrinne, H., Singh, V., Tschofenig, H., and M.
Thomson, "Dynamic Extensions to the Presence Information Thomson, "Dynamic Extensions to the Presence Information
Data Format Location Object (PIDF-LO)", Data Format Location Object (PIDF-LO)",
draft-singh-geopriv-pidf-lo-dynamic-07 (work in progress), draft-singh-geopriv-pidf-lo-dynamic-07 (work in progress),
August 2009. August 2009.
[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.
 End of changes. 15 change blocks. 
42 lines changed or deleted 54 lines changed or added

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