ECRIT R. George Internet-Draft Q. Sun Intended status: Standards Track Huawei Technologies Expires: January 2, 2009 July 1, 2008 Location-to-Service Translation Protocol (LoST) Sub-Services draft-robins-ecrit-sub-services-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 a LoST client can ask LoST server for the list of sub services that it supports, and to incorporate additional information about the service provider in response. Sun & George Expires January 2, 2009 [Page 1] Internet-Draft LoST Sub-Services July 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology used in this document . . . . . . . . . . . . . . . 3 3. LoST extension . . . . . . . . . . . . . . . . . . . . . . . . 3 4. sub-service . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. sub-service in Request . . . . . . . . . . . . . . . . . . . . 4 6. sub-service in Response . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 9.1. Normative References . . . . . . . . . . . . . . . . . . . 6 9.2. Informative References . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . . . 8 Sun & George Expires January 2, 2009 [Page 2] Internet-Draft LoST Sub-Services July 2008 1. Introduction The Location-to-Service Translation (LoST) protocol [LOST] maps service identifiers (URNs) and civic or geospatial information to service URIs based on service regions. This extension allows a LoST client to find the instances of the services and it's sub services, by asking a LoST server for the list of sub services that it supports. Even the deaf & dumb people or foreigner can make use of the advantages of this draft to contact the sub service of the instances of service, in which the LoST client is interested. It provides an indication of which service and sub services the server can look up. The sub services are the capabilities of the given service. For example the sub service list of a PSAP can be urn:service:sos.police.terrorist, urn:service:sos.police.arson, urn:service:sos.police.robbery. This means that the given PSAP is able to handle terrorist attack, robbery, and a wild fire. So the clients come to know in advance whether a required sub service is offered for a particular area. This document describes how to get sub service list of the instance of service, it can be accomplished by specifying additional information in the query using the extension named, 'sub-service'. Which will return all the sub services of requested service. 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 extension A LoST client can ask a LoST server for the list of sub services it knows about for a particular services in the given area. And he can find the sub-service information from the . The LoST client will be interested in any one of them or combination of listed subservices. It will help a LoST client to locate the instances of services, those match more closely to his interest. It avoids the clients to query the service URIs returned to obtain additional information about the services, thus reducing the number of queries to be done to get the accurate search for the instances of service. In the current scenario, the client doesn't know what kind of subservices the returned service uri supports, so he can't contact Sun & George Expires January 2, 2009 [Page 3] Internet-Draft LoST Sub-Services July 2008 the service uri with additional information(i.e. sub services or service options the client wants) to get a better and timely service. We Introduce a new attribute and element to achieve this task. 'getsubservice' for the element and for the element. 4. sub-service Suppose a LoST client is seeking help from the police to get protection from a thief. Currently, the Location-to-Service Translation (LoST) protocol only supports mapping of the locations of police stations. There are no options to know any particular information about the capabilities of the instance of the service. Using the sub-service information, the LoST client can get the details of a specific police station, which can handle a thief or arson etc. 5. sub-service in Request Germany Bavaria Munich Otto-Hahn-Ring 6 81675 urn:service:sos.police Figure 1: A query with the new attribute. Here the LoST client is searching for police stations in the given area and finds it's capabilities. Sun & George Expires January 2, 2009 [Page 4] Internet-Draft LoST Sub-Services July 2008 6. sub-service in Response Muenchen Polizei-Abteilung urn:service:sos.police urn:service:sos.police.terrorist urn:service:sos.police.arson urn:service:sos.police.robbery Germany Bavaria Munich 81675 sip:munich-police@example.com xmpp:munich-police@example.com 110 Figure 3: A civic address answer with the new attribute. The response of the previous query contains the details of the PSAP in the specified service region and it's sub-service list. This indicates that, the given instance of requested service is capable of handling terrorist, theft and arson. And it tells a mobile device Sun & George Expires January 2, 2009 [Page 5] Internet-Draft LoST Sub-Services July 2008 what kind of sub services are available close by that location. The LoST client can contact the service uri with additional information (i.e. sub services or service options the client wants) so that he will get a better and timely service from the requested uri. 7. Security Considerations The same security considerations as in [LOST] apply. 8. IANA Considerations TBD 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 9.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. Sun & George Expires January 2, 2009 [Page 6] Internet-Draft LoST Sub-Services July 2008 Authors' Addresses Robins George Huawei Technologies Huawei Base, Bantian, Longgang District Shenzhen, Guangdong 518129 P. R. China Phone: +86-755-28787584 Email: robinsg@huawei.com Qian Sun Huawei Technologies Huawei Base, Bantian, Longgang District Shenzhen, Guangdong 518129 P. R. China Phone: +86-755-28787351 Email: sunqian@huawei.com Sun & George Expires January 2, 2009 [Page 7] Internet-Draft LoST Sub-Services 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]