ECRIT Q. Sun Internet-Draft R. George Intended status: Standards Track Huawei Technologies Expires: May 2, 2009 H. Schulzrinne Columbia University October 29, 2008 Shelter Service And Classification draft-sun-ecrit-shelter-service-01 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 May 2, 2009. 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. Sun, et al. Expires May 2, 2009 [Page 1] Internet-Draft Shelter Service October 2008 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 Intellectual Property and Copyright Statements . . . . . . . . . . 9 Sun, et al. Expires May 2, 2009 [Page 2] Internet-Draft Shelter Service October 2008 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 May 2, 2009 [Page 3] Internet-Draft Shelter Service October 2008 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 May 2, 2009 [Page 4] Internet-Draft Shelter Service October 2008 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 May 2, 2009 [Page 5] Internet-Draft Shelter Service October 2008 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 RFC 5031 [RFC5031] and RFC 5222 [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 May 2, 2009 [Page 6] Internet-Draft Shelter Service October 2008 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-00 (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-13 (work in progress), September 2008. [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. Sun, et al. Expires May 2, 2009 [Page 7] Internet-Draft Shelter Service October 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-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 Sun, et al. Expires May 2, 2009 [Page 8] Internet-Draft Shelter Service October 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, et al. Expires May 2, 2009 [Page 9]