ECRIT Q. Sun
Internet-Draft R. George
Intended status: Standards Track Huawei Technologies
Expires: January 2, 2009 July 1, 2008
Specifying Unsafe Areas in LoST Service Boundary
draft-sun-ecrit-unsafe-areas-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 2, 2009.
Abstract
This document describes how to specify unsafe areas in LoST for
emergency services, such as police, mountain, marine and fire.
Sun & George Expires January 2, 2009 [Page 1]
Internet-Draft LoST Unsafe Areas July 2008
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology used in this document . . . . . . . . . . . . . . . 3
3. LoST extensions . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Request unsafe areas . . . . . . . . . . . . . . . . . . . 4
3.2. Specifying unsafe areas in the response . . . . . . . . . . 4
3.3. Additional information about the <unsafeArea> . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . . 8
Sun & George Expires January 2, 2009 [Page 2]
Internet-Draft LoST Unsafe Areas July 2008
1. Introduction
The Location-to-Service Translation Protocol (LoST) describes a
protocol for mapping service identifiers and location information to
URLs of the service instance. The region of a service instance can
also be provided in one or more serviceBoundary elements.
According to the research of patterns of crime, the spatial
differentiation of crimes occurred in the city is obvious. There are
a few pretty dangerous areas with high crime rate in many big cities,
which may be identified and published by police departments. For
example monthly crime hot spots identified by phoenix police
department [Monthly_Violent].
This document helps to find out unsafe areas in the service region.
These unsafe areas are the one where frequent crime (e.g. theft,
robbery, pickpockets), accidents or some other incidents are
happening. There may be more than one unsafe area in a service
region, and of course, may be zero.
When the user enters in to an unsafe area where frequent pickpockets
are happening, the user's device will prompt him the warning "many
pick-pockets are in this area, especially at bus stops" and the
seriousness of the problem. So that he can take necessary
precautions to handle the given situation after entering in this
area. To achieve this task, we add new elements named unsafeArea,
note, and rank in the <findServiceResponse>. the unsafe area is
requested by the client, using the 'unsafeArea' attribute in the
<findService> request with the value set to "value" or "reference".
The LoST client's device can prompt a user when he enters in to an
area which has or might have a natural disaster threats like flood,
snowslide, landslip, wild fire etc, or when he drives in to an
accident prone area. Sailing or swimming people can also find out
the dangerous areas with submerged rocks or sharks.
2. Terminology used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
3. LoST extensions
The LoST client can ask the server to return unsafe areas. And we
introduce a new attribute in LoST request <findService> named
Sun & George Expires January 2, 2009 [Page 3]
Internet-Draft LoST Unsafe Areas July 2008
'unsafeArea' for this purpose.
We introduce new elements in LoST response <findServiceResponse>
named, <unsafeArea>, <note> and <rank> to describe the unsafe areas
and its information.
3.1. Request unsafe areas
The new attribute 'unsafeArea' in LoST request <findService>
indicates the LoST client wants to get the unsafe areas information
of the determined service instance.
<?xml version="1.0" encoding="UTF-8"?>
<findService
xmlns="urn:ietf:params:xml:ns:lost1"
xmlns:p2="http://www.opengis.net/gml"
serviceBoundary="value"
recursive="true"
unsafeArea="value">
<location id="6020688f1ce1896d" profile="geodetic-2d">
<p2:Point id="point1" srsName="urn:ogc:def:crs:EPSG::4326">
<p2:pos>37.775 -122.422</p2:pos>
</p2:Point>
</location>
<service>urn:service:sos.police</service>
</findService>
Figure 1: A <findService> query
3.2. Specifying unsafe areas in the response
The new element <unsafeArea> is used to specify the dangerous areas
in the service region. A <unsafeArea> element contains at least one
<areaBoundary> element. An area boundary circumscribes the unsafe
region. It has the similar semantics with serviceBoundary element.
And he gets the response with the <unsafeArea> details:
<?xml version="1.0" encoding="UTF-8"?>
<findServiceResponse xmlns="urn:ietf:params:xml:ns:lost1"
xmlns:p2="http://www.opengis.net/gml">
Sun & George Expires January 2, 2009 [Page 4]
Internet-Draft LoST Unsafe Areas July 2008
<mapping
expires="2007-01-01T01:44:33Z"
lastUpdated="2006-11-01T01:00:00Z"
source="authoritative.example"
sourceId="7e3f40b098c711dbb6060800200c9a66">
<displayName xml:lang="en">
New York City Police Department
</displayName>
<service>urn:service:sos.police</service>
<serviceBoundary profile="geodetic-2d">
<p2:Polygon srsName="urn:ogc:def::crs:EPSG::4326">
<p2:exterior>
<p2:LinearRing>
<p2:pos>37.775 -122.4194</p2:pos>
<p2:pos>37.555 -122.4194</p2:pos>
<p2:pos>37.555 -122.4264</p2:pos>
<p2:pos>37.775 -122.4264</p2:pos>
<p2:pos>37.775 -122.4194</p2:pos>
</p2:LinearRing>
</p2:exterior>
</p2:Polygon>
</serviceBoundary>
<uri>sip:nypd@example.com</uri>
<uri>xmpp:nypd@example.com</uri>
<serviceNumber>911</serviceNumber>
<unsafeArea>
<areaBoundary profile="geodetic-2d">
<p2:Circle srsName="urn:ogc:def:crs:EPSG::4326">
<p2:pos>37.565 -122.4224</p2:pos>
<p2:radius uom="urn:ogc:def:uom:EPSG::9001">
250.12
</p2:radius>
</p2:Circle>
</areaBoundary>
<rank>5</rank>
<note>robbery often happens in the night</note>
<unsafeArea>
</mapping>
<path>
<via source="resolver.example"/>
<via source="authoritative.example"/>
</path>
<locationUsed id="6020688f1ce1896d"/>
</findServiceResponse>
Figure 2: A <findServiceResponse>
Sun & George Expires January 2, 2009 [Page 5]
Internet-Draft LoST Unsafe Areas July 2008
3.3. Additional information about the <unsafeArea>
The new element <note> can be used to specify the additional
information about the unsafe area. It could be some suggestion or
warning text about this area. This <note> message in the response
may be prompted when the LoST client enters in to the given unsafe
area, together with the seriousness, i.e. the <rank> element. The
value of the <rank> element is a number from 1 to 5, 5 means the most
serious situation.
4. Security Considerations
TBD
5. IANA Considerations
TBD
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
6.2. Informative References
[I-D.ietf-ecrit-lost]
Hardie, T., Newton, A., Schulzrinne, H., and H.
Tschofenig, "LoST: A Location-to-Service Translation
Protocol", draft-ietf-ecrit-lost-09 (work in progress),
March 2008.
[I-D.ietf-geopriv-pdif-lo-profile]
Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
PIDF-LO Usage Clarification, Considerations and
Recommendations", draft-ietf-geopriv-pdif-lo-profile-11
(work in progress), February 2008.
[Monthly_Violent]
Police Headquarters, Phoenix,
"http://phoenix.gov/POLICE/ucr_monthly_violent.pdf".
Sun & George Expires January 2, 2009 [Page 6]
Internet-Draft LoST Unsafe Areas July 2008
Authors' Addresses
Qian Sun
Huawei Technologies
Huawei Base, Bantian, Longgang District
Shenzhen, Guangdong 518129
P. R. China
Phone: +86-755-28787351
Email: sunqian@huawei.com
Robins George
Huawei Technologies
Huawei Base, Bantian, Longgang District
Shenzhen, Guangdong 518129
P. R. China
Phone: +86-755-28789961
Email: robinsg@huawei.com
Sun & George Expires January 2, 2009 [Page 7]
Internet-Draft LoST Unsafe Areas July 2008
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Sun & George Expires January 2, 2009 [Page 8]