ECRIT                                                             Q. Sun
Internet-Draft                                                 R. George
Intended status: Standards Track                     Huawei Technologies
Expires: January 4, 2009                                    July 3, 2008


                   Shelter Service And Classification
                   draft-sun-ecrit-shelter-service-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 4, 2009.

Abstract

   This document defines a new service registration 'shelter', and
   describes how to find, what instances of shelter service are closest
   to the user's location.












Sun & George             Expires January 4, 2009                [Page 1]


Internet-Draft               Shelter Service                   July 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
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 6
   Intellectual Property and Copyright Statements  . . . . . . . . . . 8






































Sun & George             Expires January 4, 2009                [Page 2]


Internet-Draft               Shelter Service                   July 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.

   We introduce new services to find the safe areas near to a client's
   location.  And a LoST client can request for the particular service
   to know about the shelters near his location.  A user can go to any
   shelter and ask for help, normally the nearest is the best.  This is
   not like the police service, which has a clearly defined
   jurisdictional boundaries.  So it's always advised to search for a
   shelter near to a specified location.


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 registration using the top-
   level service label 'shelter'.  This kind of service could be
   required in a wide range and in a short period.

           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

   Note: The corresponding description for each service will be added in
   the later version.


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



Sun & George             Expires January 4, 2009                [Page 3]


Internet-Draft               Shelter Service                   July 2008


   <serviceLocation> element contains the geodetic coordinates of a
   point of service and must be contained in a <mapping> element.  In
   responses such as <findServiceResponse>, a list of service URIs, each
   with its own <serviceLocation> element, must be returned.




        <?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">
          <location id="6020688f1ce1896d" profile="geodetic-2d">
            <p2:Circle srsName="urn:ogc:def:crs:EPSG::4326">
              <p2:pos>37.775 -122.422</p2:pos>
              <p2:radius uom="urn:ogc:def:uom:EPSG::9001">
                 2000.24
              </p2:radius>
            </p2:Circle>
          </location>
          <service>urn:service:shelter.earthquake</service>
        </findService>

              Figure 1: A <findService> query


   The client is asking the LoST server to send a list of service URNs
   and earthquake shelter places within 2000.24 meters from its
   approximate position specified in <p2:pos>.




















Sun & George             Expires January 4, 2009                [Page 4]


Internet-Draft               Shelter Service                   July 2008


         <?xml version="1.0" encoding="UTF-8"?>
         <findServiceResponse xmlns="urn:ietf:params:xml:ns:lost1"
           xmlns:p2="http://www.opengis.net/gml">
           <mapping
             expires="2007-01-01T01:44:33Z"
             lastUpdated="2006-11-01T01:00:00Z"
             source="authoritative.example"
             sourceId="7e3f40b098c711dbb6060800200c9a66">
             <displayName xml:lang="en">
               Emergency Earthquake shelter camp 1
             </displayName>
             <service>urn:service:shelter.earthquake</service>
             <uri>sip: earthquake_camp1@example.com</uri>
             <uri>xmpp:shelter_1@example.com</uri>
             <serviceNumber>2129397040</serviceNumber>
             <serviceLocation profile="geodetic-2d">
               <p2:Point id="point1"srsName="urn:ogc:def:crs:EPSG:4326">
                 <p2:pos>37.725 -122.432</p2:pos>
               </p2:Point>
             </serviceLocation>
           </mapping>
           <mapping
             expires="2007-01-01T01:44:33Z"
             lastUpdated="2006-11-01T01:00:00Z"
             source="authoritative.example"
             sourceId="7e3f40b098c711dbb6060800200c9b356">
             <displayName xml:lang="en">
               Emergency Earthquake shelter camp 2
             </displayName>
             <service>urn:service:shelter.earthquake</service>
             <uri>sip:earthquake_camp2@example.com</uri>
             <uri>xmpp:shelter_2@example.com</uri>
             <serviceNumber>2129397157</serviceNumber>
             <serviceLocation profile="geodetic-2d">
               <p2:Point id="point1"srsName="urn:ogc:def:crs:EPSG:4326">
                 <p2:pos>37.665 -122.321</p2:pos>
               </p2:Point>
             </serviceLocation>
           </mapping>
           <path>
             <via source="resolver.example"/>
             <via source="authoritative.example"/>
           </path>
           <locationUsed id="6020688f1ce1896d"/>
         </findServiceResponse>

                   Figure 2: A <findServiceResponse>




Sun & George             Expires January 4, 2009                [Page 5]


Internet-Draft               Shelter Service                   July 2008


   It 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

   TBD


6.  IANA Considerations

   TBD


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-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.










Sun & George             Expires January 4, 2009                [Page 6]


Internet-Draft               Shelter Service                   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 4, 2009                [Page 7]


Internet-Draft               Shelter Service                   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 4, 2009                [Page 8]