ECRIT Q. Sun Internet-Draft R. George Intended status: Standards Track Huawei Technologies Expires: January 11, 2010 H. Schulzrinne Columbia University July 10, 2009 Shelter Service And Classification draft-sun-ecrit-shelter-service-02 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. 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 11, 2010. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. Sun, et al. Expires January 11, 2010 [Page 1] Internet-Draft Shelter Service July 2009 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract This document defines and registers a new service 'shelter', for the service URN to find, what instances of shelter service are closest to the user's location. The Location-to-Service Translation (LoST) protocol can provide these information for a geographical region. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology used in this document . . . . . . . . . . . . . . . 3 3. Sub-Services for the 'shelter' service . . . . . . . . . . . . 3 4. Example for finding shelters . . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 6.1. Sub-Services for the 'shelter' Service . . . . . . . . . . 6 6.2. Initial IANA Registration . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Sun, et al. Expires January 11, 2010 [Page 2] Internet-Draft Shelter Service July 2009 1. Introduction It happens to announce shelter areas or locations before or after nature disasters occur. A hill area could be declared as a shelter area for being safe from a flood threat. LoST client can find out what instances of this service are closest to users. Examples include earthquake shelter, flood shelter, air-raid shelter, wildfire etc. To prepare for or to respond to natural and man-made disasters, the public needs access to information about emergency shelters. Different types of emergencies call for different types of shelters. For example, residents should flee to an elevated building for a flood, but to an underground area for a hurricane. To locate appropriate near-by shelters, we can use the location-to-service translation protocol (LoST) [RFC5222], using a set of service URNs defined in this document. 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. Sub-Services for the 'shelter' service This section defines the shelter service using the top-level service label 'shelter'. urn:service:shelter urn:service:shelter.airraid urn:service:shelter.earthquake urn:service:shelter.flood urn:service:shelter.heatwave urn:service:shelter.homeless urn:service:shelter.hurricane urn:service:shelter.wildfire 4. Example for finding shelters In this example, we use the circular shape in queries and serviceLocation element in responses introduced by [LOST-EXT]. The element contains the geodetic coordinates of a point of service and must be contained in a element. In responses such as , a list of service URIs, each Sun, et al. Expires January 11, 2010 [Page 3] Internet-Draft Shelter Service July 2009 with its own element, must be returned. 37.775 -122.422 2000.24 urn:service:shelter.earthquake Figure 1: A query The client is asking the LoST server to send URIs and other information of earthquake shelter places within 2000.24 meters from its approximate position specified in . Sun, et al. Expires January 11, 2010 [Page 4] Internet-Draft Shelter Service July 2009 Emergency Earthquake shelter camp 1 urn:service:shelter.earthquake sip: earthquake_camp1@example.com xmpp:shelter_1@example.com 2129397040 37.725 -122.432 Emergency Earthquake shelter camp 2 urn:service:shelter.earthquake sip:earthquake_camp2@example.com xmpp:shelter_2@example.com 2129397157 37.665 -122.321 Figure 2: A Sun, et al. Expires January 11, 2010 [Page 5] Internet-Draft Shelter Service July 2009 In response to the query the LoST server says that the given shelters specified by these service locations are safe area from earth quake. In the same way he can request for other shelter services. 5. Security Considerations The security considerations of [RFC5031] and [RFC5222] are relevant to this document. 6. IANA Considerations 6.1. Sub-Services for the 'shelter' Service This section defines the service registration within the IANA registry, using the top-level service label 'shelter'. urn:service:shelter 'shelter' service denotes a top-level service, and it encompasses all of the services listed below. urn:service:shelter.airraid This service identifier is used to find a safe place from the air-raid. (example: bunker) urn:service:shelter.earthquake A safe place from the earthquake can be found by using this identifier (example: tent) urn:service:shelter.flood Sub-service is used to identify shelters from the flood disaster (example: a hill) urn:service:shelter.heatwave Heat wave shelters are identified by using this identifier (example: cool places can be a shelter from heat wave) urn:service:shelter.homeless This service identifier can be used by homeless people to find shelters (example: Usually located in urban neighborhoods) urn:service:shelter.wildfire Wild fire shelters can be located by using this sub-service (example: safety device carried by wildland firefighter) urn:service:shelter.hurricane This service identifier is used to search for safe places from the hurricane (example: storm rooms) Sun, et al. Expires January 11, 2010 [Page 6] Internet-Draft Shelter Service July 2009 6.2. Initial IANA Registration The following table contains the initial IANA registration for shelter services. Service Reference Description -------------------------------------------------------------------- urn:service:shelter TBD Shelter services urn:service:shelter.airraid TBD Air-raid shelter urn:service:shelter.earthquake TBD Earth quake shelter urn:service:shelter.flood TBD Flood shelter urn:service:shelter.heatwave TBD Heat wave shelter urn:service:shelter.homeless TBD Homeless shelter urn:service:shelter.wildfire TBD Wild fire shelter urn:service:shelter.hurricane TBD Hurricane shelter 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 7.2. Informative References [I-D.forte-ecrit-lost-extensions] Forte, A. and H. Schulzrinne, "Location-to-Service Translation Protocol (LoST) Extensions", draft-forte-ecrit-lost-extensions-02 (work in progress), March 2009. [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services", RFC 5031, January 2008. [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. Tschofenig, "LoST: A Location-to-Service Translation Protocol", RFC 5222, August 2008. [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations", RFC 5491, March 2009. Sun, et al. Expires January 11, 2010 [Page 7] Internet-Draft Shelter Service July 2009 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-28788314 Email: robinsg@huawei.com Henning Schulzrinne Columbia University Department of Computer Science 450 Computer Science Building, New York NY, 10027 US Phone: +1 212 939 7004 Email: hgs+ecrit@cs.columbia.edu URI: http://www.cs.columbia.edu Sun, et al. Expires January 11, 2010 [Page 8]