Geopriv H. Schulzrinne Internet-Draft Columbia U. Expires:
May 29, 2005January 6, 2006 H. Tschofenig Siemens November 28, 2004July 5, 2005 Location Types Registry draft-ietf-geopriv-location-types-registry-00.txtdraft-ietf-geopriv-location-types-registry-01.txt Status of this Memo This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667.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 becomebecomes aware will be disclosed, in accordance with RFC 3668.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. 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 29, 2005.January 6, 2006. Copyright Notice Copyright (C) The Internet Society (2004).(2005). Abstract This document creates a registry for location types. The place types 'aircraft', 'airport', 'bus', 'car', home', 'hotel', 'industrial', 'library', 'mall', 'office', 'restaurant', 'school', 'ship', 'station', 'street', 'theater', 'hospital', 'train', 'truck', 'public' and 'public-transport' are created with this document. Additional place types can be added on a 'First Come First Served' policy. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1 Normative References . . . . . . . . . . . . . . . . . . . .11 7.2 Informative References . . . . . . . . . . . . . . . . . . .11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11 Intellectual Property and Copyright Statements . . . . . . . . 12 1. Introduction This document creates a registry for location types, such as bus, airport or hotel. 2. Terminology 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 . 3. Location Types This section describes types of location where an entity is located. The entity is not further specified and can be a person or an object such as a network access point. aircraft: The entity is in a plane, helicopter or balloon. airport: The entity is located in an airport, heliport or similar location. bus: The entity is travling in a public or charter bus. car: The entity is in an automobile. home: The entity is in a private or residential setting, not necessarily the personal residence of the entity, e.g., including hotel or a friend's home. hotel: The entity is in a hotel, motel, inn or other lodging establishment. industrial: The entity is in an industrial setting, such as a manufacturing floor or power plant. library: The entity is in a library or other public place that provides access to books, music and reference materials. mall: The entity is frequenting a shopping mall or shopping area. office: The entity is in a business setting, such as an office. outdoors: The entity is in a general outdoors area, such as a park or city streets. restaurant: The entity is in a restaurant, coffee shop or other public dining establishment. school: The entity is in a school or university, but not necessarily in a classroom or library. ship: The entity is traveling in a water vessel or boat. station: The entity is located in a bus or train station. street: The entity is walking in a street. theater: The entity is in a theater, lecture hall, auditorium, class room, movie theater or similar facility designed for presentations, talks, plays, music performances and other events involving an audience. hospital: The entity is located in a medical facility. train: The entity is traveling in a train, monorail, maglev, cable car or similar conveyance. truck: The entity is in a truck, used primarily to carry goods rather than people. public: The entity is in a public area such as a shopping mall, street, park, public building, train station, airport or in public conveyance such as a bus, train, plane or ship. This general description encompasses the more precise descriptors 'street', 'public-transport', 'aircraft', 'ship', 'bus', 'train', 'airport', 'mall' and 'outdoors'. public-transport: The entity is using any form of public transport, including aircraft, bus, train or ship. 4. IANA Considerations This document creates new IANA registries for location types as listed in Section 3 starting with 'aircraft' and finishing with 'public-transport' . Following the policies outline in RFC 2434 , these tokens are assigned on a 'First Come First Served' policy. Each registration must include the name of the token and a brief description similar to the ones offered in for the initial registrations contained this document: XML Schema Name Data Type:Token Identifier: Identifier of the token Description: Brief description indicating the meaning of the token. UsageNote that the usage of these tokens is not limited to XML. However, it is expected thatXML imposesand the most restrictions on'Token Identifier' is the allowable syntaxXML element content and thus all tokens must conform tonot the rules forXML Names.element name. 5. Security Considerations This document defines a registry for location types and as such does not raise security issues. 6. Acknowledgements We would like to thank V. Gurbani, P. Kyzivat and J. Rosenberg for their work on RPID  which lead to the location types listed in this document. Many thanks to Allison Mankin for her guidance. 7. References 7.1 Normative References  Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", March 1997.  Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. 7.2 Informative References  Schulzrinne, H., Gurbani, V., Kyzivat, P. and J. Rosenberg,"RPID: Rich Presence:Presence Extensions to the Presence Information Data Format (PIDF)", draft-ietf-simple-rpid-04draft-ietf-simple-rpid-07 (work in progress), October 2004.June 2005. Authors' Addresses Henning Schulzrinne Columbia University Department of Computer Science 450 Computer Science Building New York, NY 10027 USA Phone: +1 212 939 7042 EMail:Email: email@example.com URI: http://www.cs.columbia.edu/~hgs Hannes Tschofenig Siemens Otto-Hahn-Ring 6 Munich, Bavaria 81739 Germany EMail:Email: Hannes.Tschofenig@siemens.com URI: http://www.tschofenig.com Intellectual Property Statement 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 firstname.lastname@example.org. Disclaimer of Validity 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 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. Copyright Statement Copyright (C) The Internet Society (2004).(2005). 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society.