draft-ietf-geopriv-location-types-registry-03.txt   draft-ietf-geopriv-location-types-registry-04.txt 
Geopriv H. Schulzrinne Geopriv H. Schulzrinne
Internet-Draft Columbia U. Internet-Draft Columbia U.
Expires: February 16, 2006 H. Tschofenig Expires: August 17, 2006 H. Tschofenig
Siemens Siemens
August 15, 2005 February 13, 2006
Location Types Registry Location Types Registry
draft-ietf-geopriv-location-types-registry-03.txt draft-ietf-geopriv-location-types-registry-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 16, 2006. This Internet-Draft will expire on August 17, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document creates a registry for location types. The place types This document creates a registry for describing the types of places a
'aircraft', 'airport', 'arena', 'bus', 'bus-station', 'automobile', human or end system might be found. The registry is then referenced
'bank', 'bar', 'cafe', 'classroom', 'club', 'construction', by other protocols that need a common set of location terms as
'convention-center', 'cycle', 'residence', 'hotel', 'industrial', protocol constants. Examples of location terms defined in this
'library', 'shopping-area', 'government', 'stadium', 'office', document include aircraft, office and train station.
'outdoors', 'parking', 'prison', 'restaurant', 'school', , 'street',
'theater', 'hospital', 'store', 'train', 'train-station', 'underway',
'truck', 'public', 'place-of-worship', 'warehourse', 'water',
'watercraft', 'unknown', 'other' and 'public-transport' are created
with this document.
Additional place types can be added on a 'First Come First Served'
policy.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Internationalization Considerations . . . . . . . . . . . . . 13
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
7.1 Normative References . . . . . . . . . . . . . . . . . . . 14 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2 Informative References . . . . . . . . . . . . . . . . . . 14 8.1. Normative References . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18
1. Introduction 1. Introduction
This document creates a registry for location types. The place types This document creates a registry for location type tokens. We
'aircraft', 'airport', 'arena', 'bus', 'bus-station', 'automobile', anticipate that the network, through configuration or management
'bank', 'bar', 'cafe', 'classroom', 'club', 'construction', protocols, tells a mobile device what kind of location it finds
'convention-center', 'cycle', 'residence', 'hotel', 'industrial', itself in. The device and associated software can then tailor its
'library', 'shopping-area', 'government', 'stadium', 'office', behavior to the environment. For example, this document defines the
'outdoors', 'parking', 'prison', 'restaurant', 'school', , 'street', terms "classroom", "place-of-worship" and "theater". A considerate
'theater', 'hospital', 'store', 'train', 'train-station', 'underway', owner of a cell phone might program the device to switch from ringer
'truck', 'public', 'place-of-worship', 'warehourse', 'water', to vibrate mode in such environments. Just knowing the geographic
'watercraft', 'unknown', 'other' and 'public-transport' are created location, be it as civic (street address) or geospatial coordinates
with this document. would generally not allow the device to make a similar decision.
Additional place types can be added on a 'First Come First Served' Naturally, the number of descriptive terms for physical environments
policy. 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
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
description.
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, [3], 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 [4], where this
information is conveyed from the RADIUS client to the RADIUS server.
Rich presence (RPID [5]) also utilizes the values of the location
type registry.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [1]. document are to be interpreted as described in [1].
3. Location Types 3. Location Types
This section describes types of location where an entity is located. This section describes types of location where an entity is located.
skipping to change at page 5, line 21 skipping to change at page 6, line 21
aircraft: aircraft:
The entity is in a plane, helicopter or balloon. The entity is in a plane, helicopter or balloon.
airport: airport:
The entity is located in an airport, heliport or similar location. The entity is located in an airport, heliport or similar location.
arena: arena:
The entitz is in an enclosed area used for sports events. The entity is in an enclosed area used for sports events.
bus:
The entity is travling in a public or charter bus.
bus-station:
The entity is in a terminal that serves bus passengers; bus depot
or bus terminal.
automobile: automobile:
The entity is in a railroad car. The entity is in a self-propelled passenger vehicle.
bank: bank:
The entity is in a business establishment in which money is kept The entity is in a business establishment in which money is kept
for saving or commercial purposes or is invested, supplied for for saving or commercial purposes or is invested, supplied for
loans, or exchanged. loans, or exchanged.
bar: bar:
The entity is in a bar or saloon. The entity is in a bar or saloon.
bus:
The entity is traveling in a public or charter bus.
bus-station:
The entity is in a terminal that serves bus passengers; bus depot
or bus terminal.
cafe: cafe:
The entity is in a cafe or coffeeshop. The entity is in a cafe or coffeeshop.
classroom: classroom:
The person is in an academic classroom or lecture hall. The person is in an academic classroom or lecture hall.
club: club:
skipping to change at page 6, line 33 skipping to change at page 7, line 29
The entity is on a construction site. The entity is on a construction site.
convention-center: convention-center:
The entity is in a convention center. The entity is in a convention center.
cycle: cycle:
The entity is riding a bicycle, motorcycle or similar vehicle. The entity is riding a bicycle, motorcycle or similar vehicle.
residence: government:
The entity is in a private or residential setting, not necessarily The person is in a government building, such as those used by the
the personal residence of the entity, e.g., including a friend's legislative, executive, or judicial branches of governments,
home. including court houses, police stations and military
installations.
hospital:
The entity is in a hospital, hospice, medical clinic, mental
institution, or doctor's office.
hotel: hotel:
The entity is in a hotel, motel, inn or other lodging The entity is in a hotel, motel, inn or other lodging
establishment. establishment.
industrial: industrial:
The entity is in an industrial setting, such as a manufacturing The entity is in an industrial setting, such as a manufacturing
floor or power plant. floor or power plant.
library: library:
The entity is in a library or other public place that provides The entity is in a library or other public place in which literary
access to books, music, periodicals, newspapers, pamphlets, and artistic materials, such as books, music, periodicals,
prints, records, and tapes, are kept for reading, reference, or newspapers, pamphlets, prints, records, and tapes, are kept for
lending. reading, reference, or lending.
shopping-area:
The entity is frequenting a shopping mall or shopping area. This
area is a large, often enclosed shopping complex containing
various stores, businesses, and restaurants usually accessible by
common passageways.
government:
The person is in a government building, such as those used by the
legislative, executive, or judicial branches of governments,
including court houses, police stations and military
installations.
stadium:
The person is in a large, usually open structure for sports
events, including a racetrack.
office: office:
The entity is in a business setting, such as an office. The entity is in a business setting, such as an office.
other:
The entity is in a place without a registered place type
representation.
outdoors: outdoors:
The entity is in a general outdoors area, such as a park or city The entity is in a general outdoors area, such as a park or city
streets. streets.
parking: parking:
The person is in a parking lot or parking garage. The person is in a parking lot or parking garage.
place-of-worship:
The entity is at a religious rites where congregations gather for
religious observances, such as a church, chapel, meetinghouse,
mosque, shrine, synagogue, or temple.
prison: prison:
The person is in a prison, penitentiary, jail, brig, or criminal The person is in a prison, penitentiary, jail, brig, or criminal
mental institution. mental institution.
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', 'bus', 'bus-station', 'train',
'train-station', 'airport', 'shopping-area', 'outdoors', and
'watercraft'.
public-transport:
The entity is using any form of public transport, including
aircraft, bus, train or ship.
residence:
The entity is in a private or residential setting, not necessarily
the personal residence of the entity, e.g., including a friend's
home.
restaurant: restaurant:
The entity is in a restaurant, coffee shop or other public dining The entity is in a restaurant, coffee shop or other public dining
establishment. establishment.
school: school:
The entity is in a school or university, but not necessarily in a The entity is in a school or university, but not necessarily in a
classroom or library. classroom or library.
shopping-area:
The entity is frequenting a shopping mall or shopping area. This
area is a large, often enclosed shopping complex containing
various stores, businesses, and restaurants usually accessible by
common passageways.
stadium:
The person is in a large, usually open structure for sports
events, including a racetrack.
store:
The person is located in a place where merchandise is offered for
sale; a shop.
street: street:
The entity is walking in a street. The entity is walking in a street.
theater: theater:
The entity is in a theater, lecture hall, auditorium, class room, The entity is in a theater, lecture hall, auditorium, class room,
movie theater or similar facility designed for presentations, movie theater or similar facility designed for presentations,
talks, plays, music performances and other events involving an talks, plays, music performances and other events involving an
audience. audience.
hospital:
The entity is in a hospital, hospice, medical clinic, mental
institution, or doctor's office.
store:
The person is located in a place where merchandise is offered for
sale; a shop.
train: train:
The entity is traveling in a train, monorail, maglev, cable car or The entity is traveling in a train, monorail, maglev, cable car or
similar conveyance. similar conveyance.
train-station: train-station:
The person is in a terminal where trains load or unload passengers The person is in a terminal where trains load or unload passengers
or goods; railway station, railroad station, railroad terminal, or goods; railway station, railroad station, railroad terminal,
train depot. train depot.
underway:
The person is in a land, water, or air craft which is underway (in
motion).
truck: truck:
The entity is in a truck, used primarily to carry goods rather The entity is in a truck, used primarily to carry goods rather
than people. than people.
place-of-worship: underway:
The entity is at a religious rites where congregations gather for The person is in a land, water, or air craft which is underway (in
religious observances, such as a church, chapel, meetinghouse, motion).
mosque, shrine, synagogue, or temple.
unknown:
The type of place is unknown.
warehouse: warehouse:
The person is in a place in which goods or merchandise are stored; The person is in a place in which goods or merchandise are stored;
a storehouse or self-storage facility. a storehouse or self-storage facility.
water: water:
The person is on water, such as an ocean, lake, river, canal or The person is on water, such as an ocean, lake, river, canal or
other waterway. other waterway.
watercraft: watercraft:
The person is traveling in a boat or ship. The person is traveling in a boat or ship.
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'.
unknown:
The type of place is unknown.
other:
The entity is in a place without a registered place type
representation.
public-transport:
The entity is using any form of public transport, including
aircraft, bus, train or ship.
4. IANA Considerations 4. IANA Considerations
This document creates new IANA registries for location types as This document creates new IANA registries for location types as
listed in Section 3 starting with 'aircraft' and finishing with listed in Section 3 starting with 'aircraft' and finishing with
'public-transport'. 'watercraft'.
Following the policies outline in RFC 2434 [2], these tokens are Following the policies outline in RFC 2434 [2], new tokens are
assigned on a 'First Come First Served' policy. Each registration assigned after Expert Review by the IETF GEOPRIV working group or its
must include the name of the token and a brief description similar to designated successor. The same procedure applies to updates of
the ones offered in for the initial registrations contained this tokens within the registry and to deleting tokens from the registry.
document: There are no restrictions regarding the update of location-type
values in 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.
To ensure widespread usability across protocols, tokens should follow
the character set restrictions for XML Names.
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: Token Identifier:
Identifier of the token Identifier of the token
Description: Description:
Brief description indicating the meaning of the token. Brief description indicating the meaning of the token.
Note that the usage of these tokens is not limited to XML and the 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 'Token Identifier' is the XML element content and not the XML element
name. name.
5. Security Considerations 5. 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/tags and no internationalization support is required.
6. Security Considerations
This document defines a registry for location types and as such does This document defines a registry for location types and as such does
not raise security issues. not raise security issues.
6. Acknowledgements 7. Acknowledgements
We would like to thank V. Gurbani, P. Kyzivat and J. Rosenberg for We would like to thank V. Gurbani, P. Kyzivat and J. Rosenberg for
their work on RPID [3] which lead to the location types listed in their work on RPID [5] which lead to the location types listed in
this document. Many thanks to Allison Mankin for her guidance. Rick this document. Many thanks to Allison Mankin for her guidance. Rick
Jones pointed us to the Global Justice XML work (see Jones pointed us to the Global Justice XML work (see
http://it.ojp.gov/jxdm/) that helped us to add more values to the http://it.ojp.gov/jxdm/) that helped us to add more values to the
location registry. location registry.
7. References During the IETF last call, Harald Tveit Alvestrand, Frank Ellermann
and Sam Hartman provided useful feedback.
7.1 Normative References 8. References
8.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", March 1997. Levels", March 1997.
[2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
7.2 Informative References 8.2. Informative References
[3] Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence [3] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4
Information Data Format", draft-ietf-simple-rpid-08 (work in and DHCPv6) Option for Civic Addresses Configuration
progress), July 2005. Information", draft-ietf-geopriv-dhcp-civil-09 (work in
progress), January 2006.
[4] Tschofenig, H., "Carrying Location Objects in RADIUS",
draft-ietf-geopriv-radius-lo-04 (work in progress), July 2005.
[5] 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 Authors' Addresses
Henning Schulzrinne Henning Schulzrinne
Columbia University Columbia University
Department of Computer Science Department of Computer Science
450 Computer Science Building 450 Computer Science Building
New York, NY 10027 New York, NY 10027
USA USA
skipping to change at page 15, line 41 skipping to change at page 18, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 34 change blocks. 
136 lines changed or deleted 208 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/