Internet DRAFT - draft-ietf-geopriv-location-types-registry


Geopriv                                                   H. Schulzrinne
Internet-Draft                                               Columbia U.
Expires: November 22, 2006                                 H. Tschofenig
                                                            May 21, 2006

                        Location Types Registry

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-

   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

   The list of Internet-Draft Shadow Directories can be accessed at

   This Internet-Draft will expire on November 22, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2006).


   This document creates a registry for describing the types of places a
   human or end system might be found.  The registry is then referenced
   by other protocols that need a common set of location terms as
   protocol constants.  Examples of location terms defined in this
   document include aircraft, office and train station.

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 1]
Internet-Draft           Location Types Registry                May 2006

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Location Types . . . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
     5.1   Registering Tokens . . . . . . . . . . . . . . . . . . . . 11
     5.2   URN Sub-Namespace Registration for
           'urn:ietf:params:xml:ns:location-type' . . . . . . . . . . 12
     5.3   Schema Registration for Schema
           urn:ietf:params:xml:ns:location-type . . . . . . . . . . . 12
   6.  Internationalization Considerations  . . . . . . . . . . . . . 13
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 14
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     9.1   Normative References . . . . . . . . . . . . . . . . . . . 16
     9.2   Informative References . . . . . . . . . . . . . . . . . . 16
       Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16
       Intellectual Property and Copyright Statements . . . . . . . . 18

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 2]
Internet-Draft           Location Types Registry                May 2006

1.  Introduction

   This document creates a registry for location type tokens.  We
   anticipate that the network, through configuration or management
   protocols, tells a mobile device what kind of location it finds
   itself in.  The device and associated software can then tailor its
   behavior to the environment.  For example, this document defines the
   terms "classroom", "place-of-worship" and "theater".  A considerate
   owner of a cell phone might program the device to switch from ringer
   to vibrate mode in such environments.  Just knowing the geographic
   location, be it as civic (street address) or geospatial coordinates
   would generally not allow the device to make a similar decision.

   Naturally, the number of descriptive terms for physical environments
   is almost unbounded.  This registry tries to identify common terms
   that are likely to be useful for communications devices and for
   controlling and guiding communication behavior.  The terms roughly
   correspond to the level of details of location descriptions and icons
   found on geographic maps, for example, and are meant to be in common
   use across a variety of cultures and countries.  The registration
   process described in the IANA Considerations section allows to extend
   this list as needed, while aiming to prevent an unnecessary explosion
   in the registry.

   The use of tokens, i.e., protocol constants, makes it easier to build
   systems across multiple languages.  A user interface can readily
   translate a finite set of tokens to user-appropriate textual or
   iconic representations.  Protocols using this registry are encouraged
   to provide additional mechanisms to accommodate location types not
   currently registered via free-text fields with appropriate language
   and character set labeling.

   The terms defined in this registry do not attempt to provide a
   hierarchy of location descriptions, except in certain special cases.
   For example, the term "restaurant" is defined to include the term
   "cafe" and the term "public" encompasses a range of descriptors, as
   noted below.  The registry makes these more generic terms available
   as often the more detailed distinctions may not be available, or
   privacy concerns suggest the use of less precise terms that are still
   sufficient to guide communications behavior or evaluate the source of
   a phone call or message, say.

   In many cases, a location might be described by multiple terms that
   apply at the same time.  For example, the combination of "restaurant"
   and "airport" is immediately recognizable.  This registry makes no
   attempt to limit the number of terms that can be used to describe a
   single place or to restrict what combinations are allowed, given that
   there are few combinations that are physically impossible.  Common

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 3]
Internet-Draft           Location Types Registry                May 2006

   sense is probably a better guide here; the authors would not want to
   rule out creative business models such as combinations of "parking"
   and "restaurant" or "bar" and "hospital".  The number of terms that
   can be used within the same protocol element is left to the protocol

   This document does not describe how the values of the registry are to
   be used, as this description is provided by other documents.  For
   example, [4], describes a options for carrying civic address
   information, including the place-type attributes listed in this
   document, using the Dynamic Host Configuration Protocol (DHCPv4 and
   DHCPv6).  A usage for RADIUS is described in [5], where this
   information is conveyed from the RADIUS client to the RADIUS server.
   Rich presence (RPID [6]) also utilizes the values of the location
   type registry.

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 4]
Internet-Draft           Location Types Registry                May 2006

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in [1].

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 5]
Internet-Draft           Location Types Registry                May 2006

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 or end system.

   aircraft: A device that is used or intended to be used for flight in
      the air, such as an airplane, helicopter, gyroplane, glider or
      lighter-than-air devices like a balloon.

   airport: A place from which aircraft operate, such as an airport or

   arena: Enclosed area used for sports events.

   automobile: A usually four-wheeled automotive vehicle designed for
      passenger transportation, such as a car.

   bank: Business establishment in which money is kept for saving or
      commercial purposes or is invested, supplied for loans, or

   bar: A bar or saloon.

   bus: A large motor vehicle designed to carry passengers.

   bicycle: A vehicle with two wheels tandem, a steering handle, a
      saddle seat, and pedals by which it is propelled.

   bus-station: Terminal that serves bus passengers, such as a bus depot
      or bus terminal.

   cafe: Usually small and informal establishment serving various
      refreshments (such as coffee); coffee shop.

   classroom: Academic classroom or lecture hall.

   club: Dance club, nightclub or discotheque.

   construction: Construction site.

   convention-center: Convention center or exhibition hall.

   government: Government building, such as those used by the
      legislative, executive, or judicial branches of governments,
      including court houses, police stations and military

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 6]
Internet-Draft           Location Types Registry                May 2006

   hospital: Hospital, hospice, medical clinic, mental institution, or
      doctor's office.

   hotel: Hotel, motel, inn or other lodging establishment.

   industrial: Industrial setting, such as a manufacturing floor or
      power plant.

   library: Library or other public place in which literary and artistic
      materials, such as books, music, periodicals, newspapers,
      pamphlets, prints, records, and tapes, are kept for reading,
      reference, or lending.

   motorcycle: A two-wheeled automotive vehicle, including a scooter.

   office: Business setting, such as an office.

   other: A place without a registered place type representation.

   outdoors: Outside a building, in or into the open air, such as a park
      or city streets.

   parking: A parking lot or parking garage.

   place-of-worship: A religious site where congregations gather for
      religious observances, such as a church, chapel, meetinghouse,
      mosque, shrine, synagogue, or temple.

   prison: Correctional institution where persons are confined while on
      trial or for punishment, such as a prison, penitentiary, jail,

   public: 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', 'bus', 'bus-station', 'train', 'train-station',
      'airport', 'shopping-area', 'outdoors', and 'watercraft'.

   public-transport: Any form of public transport, including aircraft,
      bus, train or ship.

   residence: A private or residential setting, not necessarily the
      personal residence of the entity, e.g., including a friend's home.

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 7]
Internet-Draft           Location Types Registry                May 2006

   restaurant: Restaurant, coffee shop or other public dining

   school: School or university property, but not necessarily a
      classroom or library.

   shopping-area: Shopping mall or shopping area.  This area is a large,
      often enclosed shopping complex containing various stores,
      businesses, and restaurants usually accessible by common

   stadium: Large, usually open structure for sports events, including a

   store: Place where merchandise is offered for sale, such as a shop.

   street: A public thoroughfare, such as a avenue, street, alley, lane,
      road, including any sidewalks.

   theater: Theater, lecture hall, auditorium, class room, movie theater
      or similar facility designed for presentations, talks, plays,
      music performances and other events involving an audience.

   train: Train, monorail, maglev, cable car or similar conveyance.

   train-station: Terminal where trains load or unload passengers or
      goods; railway station, railroad station, railroad terminal, train

   truck: An automotive vehicle suitable for hauling, used primarily to
      carry goods rather than people.

   underway: In a land, water, or air craft which is underway (in

   unknown: The type of place is unknown.

   warehouse: Place in which goods or merchandise are stored, such as a
      storehouse or self-storage facility.

   water: In, on or above bodies of water, such as an ocean, lake,
      river, canal or other waterway.

   watercraft: On a vessel for travel on water such as a boat or ship.

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 8]
Internet-Draft           Location Types Registry                May 2006

4.  Schema

   This registry can be used in two ways, first,as a list of tokens, to
   be referenced by appropriate protocols that accept textual tokens and
   secondly as a schema, with its own namespace, referenced by other
   schema, either explicity or via namespace="##other".

   <?xml version="1.0" encoding="UTF-8"?>
   <xs:schema targetNamespace="urn:ietf:params:xml:ns:location-type"

     <xs:complexType name="empty"/>

     <xs:element name="aircraft" type="empty" />
     <xs:element name="airport" type="empty" />
     <xs:element name="arena" type="empty" />
     <xs:element name="automobile" type="empty" />
     <xs:element name="bank" type="empty" />
     <xs:element name="bar" type="empty" />
     <xs:element name="bus" type="empty" />
     <xs:element name="bicyle" type="empty" />
     <xs:element name="bus-station" type="empty" />
     <xs:element name="cafe" type="empty" />
     <xs:element name="classroom" type="empty" />
     <xs:element name="club" type="empty" />
     <xs:element name="construction" type="empty" />
     <xs:element name="convention-center" type="empty" />
     <xs:element name="government" type="empty" />
     <xs:element name="hospital" type="empty" />
     <xs:element name="hotel" type="empty" />
     <xs:element name="industrial" type="empty" />
     <xs:element name="library" type="empty" />
     <xs:element name="motorcyle" type="empty" />
     <xs:element name="office" type="empty" />
     <xs:element name="outdoors" type="empty" />
     <xs:element name="parking" type="empty" />
     <xs:element name="place-of-worship" type="empty" />
     <xs:element name="prison" type="empty" />
     <xs:element name="public" type="empty" />
     <xs:element name="public-transport" type="empty" />
     <xs:element name="residence" type="empty" />
     <xs:element name="restaurant" type="empty" />
     <xs:element name="school" type="empty" />

Schulzrinne & Tschofenig    Expires November 22, 2006           [Page 9]
Internet-Draft           Location Types Registry                May 2006

     <xs:element name="shopping-area" type="empty" />
     <xs:element name="stadium" type="empty" />
     <xs:element name="store" type="empty" />
     <xs:element name="street" type="empty" />
     <xs:element name="theater" type="empty" />
     <xs:element name="train" type="empty" />
     <xs:element name="train-station" type="empty" />
     <xs:element name="truck" type="empty" />
     <xs:element name="underway" type="empty" />
     <xs:element name="unknown" type="empty" />
     <xs:element name="warehouse" type="empty" />
     <xs:element name="water" type="empty" />
     <xs:element name="watercraft" type="empty" />

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 10]
Internet-Draft           Location Types Registry                May 2006

5.  IANA Considerations

5.1  Registering Tokens

   This document creates new IANA registries for location types as
   listed in Section 3 starting with 'aircraft' and finishing with

   IANA will maintain this registry both in the form of an XML schema
   and a list of tokens, with the same content.

   Following the policies outline in RFC 2434 [2], new tokens are
   assigned after Expert Review by the Expert Reviewer appointed by the
   IESG.  The same procedure applies to updates of tokens within the
   registry and to deleting tokens from the registry.

   The expert review should be guided by a few common-sense
   considerations.  For example, tokens should not be specific to a
   country, region, organization or company, should be well-defined and
   should be widely recognized.  The Expert's support of IANA will
   include providing IANA with the new token(s) when the update is
   provided only in the form of a schema, and providing IANA with the
   new schema element(s) when the update is provided only in the form of
   a token.

   To ensure widespread usability across protocols, tokens MUST follow
   the character set restrictions for XML Names [3].

   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:

   Token Identifier: Identifier of the token.

   Description: Brief description indicating the meaning of the token,
      including one or more examples where the term encompasses several
      more precise terms.

   XML namespace: Tokens MAY be used as elements within other
      appropriate XML documents.  Each token lists the namespace it is
      part of, typically urn:ietf:params:xml:ns:location-type:ext, where
      'ext' is the name of the extension.

   Note that the usage of these tokens is not limited to XML and the
   'Token Identifier' is the XML element content and not the XML element

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 11]
Internet-Draft           Location Types Registry                May 2006

5.2  URN Sub-Namespace Registration for

   URI: urn:ietf:params:xml:ns:location-type

   Description: This is the XML namespace for XML elements defined by
      RFCXXXX [RFC editor:  replace with RFC number] to describe
      location types within XML documents.

   Registrant Contact: IETF, GEOPRIV working group,,
      Henning Schulzrinne,


      <?xml version="1.0"?>
      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
      <html xmlns="
           <meta http-equiv="content-type"
           <title>Location Types Registry</title>
          <h1>Namespace for Location Types</h1>
          <p>See <a href="URL of published RFC">RFC&rfc.number; [RFC
   editor: replace with RFC number]</a>.</p>

5.3  Schema Registration for Schema urn:ietf:params:xml:ns:location-type

   URI: please assign

   Registrant Contact: IESG

   XML: See Section 4

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 12]
Internet-Draft           Location Types Registry                May 2006

6.  Internationalization Considerations

   The location-type values listed in this document MUST NOT be
   presented to the user.  The values therefore have the characteristic
   of tokens or tags and no internationalization support is required.

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 13]
Internet-Draft           Location Types Registry                May 2006

7.  Security Considerations

   This document defines a registry for location types and as such does
   not raise security issues.

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 14]
Internet-Draft           Location Types Registry                May 2006

8.  Acknowledgements

   Vijay Gurbani, Paul Kyzivat and Jonathan Rosenberg contributed to
   RPID [6], which lead to the location types listed in this document.
   Many thanks to Harald Alvestrand, Frank Ellermann, Bill Fenner, Ted
   Hardie, David Kessens, Allison Mankin, Jon Peterson and Sam Hartman
   for their suggestions.  Rick Jones pointed us to the Global Justice
   XML work (see that helped us to add more
   values to the location registry.

   Some of the definitions are derived from the Merriam-Webster Online

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 15]
Internet-Draft           Location Types Registry                May 2006

9.  References

9.1  Normative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
        Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.

   [3]  Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T., and E.
        Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)",
        W3C REC REC-xml-20040204, February 2004.

9.2  Informative References

   [4]  Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4
        and DHCPv6) Option for Civic  Addresses Configuration
        Information", draft-ietf-geopriv-dhcp-civil-09 (work in
        progress), January 2006.

   [5]  Tschofenig, H., "Carrying Location Objects in RADIUS",
        draft-ietf-geopriv-radius-lo-06 (work in progress), March 2006.

   [6]  Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence
        Information Data Format  (PIDF)", draft-ietf-simple-rpid-10
        (work in progress), December 2005.

Authors' Addresses

   Henning Schulzrinne
   Columbia University
   Department of Computer Science
   450 Computer Science Building
   New York, NY  10027

   Phone: +1 212 939 7042

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 16]
Internet-Draft           Location Types Registry                May 2006

   Hannes Tschofenig
   Otto-Hahn-Ring 6
   Munich, Bavaria  81739


Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 17]
Internet-Draft           Location Types Registry                May 2006

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

   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

Disclaimer of Validity

   This document and the information contained herein are provided on an

Copyright Statement

   Copyright (C) The Internet Society (2006).  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.


   Funding for the RFC Editor function is currently provided by the
   Internet Society.

Schulzrinne & Tschofenig    Expires November 22, 2006          [Page 18]