Internet DRAFT - draft-forte-ecrit-service-classification
draft-forte-ecrit-service-classification
Network Working Group A. Forte
Internet-Draft H. Schulzrinne
Intended status: Standards Track Columbia University
Expires: July 5, 2009 January 2009
Labels for Common Location-Based Services
draft-forte-ecrit-service-classification-03.txt
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and 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 July 5, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This document creates a registry for describing the types of services
available at a specific location. The registry is expected to be
referenced by other protocols that need a common set of service terms
Forte & Schulzrinne Expires July 5, 2009 [Page 1]
Internet-Draft Service Classification January 2009
as protocol constants. In particular, we define location-based
service as either a point at a specific geographic location (e.g.,
bus stop) or a service covering a specific region (e.g., pizza
delivery).
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
3. Location-based services . . . . . . . . . . . . . . . . . . . 3
4. Guidelines for the creation of new top-level services . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
5.1. Registering new tokens . . . . . . . . . . . . . . . . . . 11
5.2. Internationalization Considerations . . . . . . . . . . . 11
5.3. Security Considerations . . . . . . . . . . . . . . . . . 11
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Forte & Schulzrinne Expires July 5, 2009 [Page 2]
Internet-Draft Service Classification January 2009
1. Introduction
Many mobile devices are now equipped to determine the user's
geographic location, either through GPS, cell-tower mapping or a
network-based triangulation mechanism. Once location information is
available, it is natural to want to look up near-by places that
provide a specific service, sometimes called points-of-interest
(POI). Examples of such services include restaurants, stores,
hospitals, automatic teller machines and museums.
To allow such systems to operate across large geographic areas and
for multiple languages, it is useful to define a common set of terms,
so that the same service is labeled with the same token regardless of
who created a particular location service. The number of different
labels is clearly potentially very large, but only a relatively small
subset of common services is of particular interest to mobile users,
such as travelers and commuters. This document focuses on labels
commonly found on maps or in navigation devices.
This document creates a registry of service labels and an initial set
of values. The registry is protocol-agnostic and should work for all
protocols that can handle alphanumeric strings, including LoST
[RFC5222].
2. Requirements notation
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. Location-based services
When not obvious, the definition of a particular service will be
specified in the future. In the following we enumerate a sub-set of
the most common location-based services, some of which are also
present in [RFC4589].
urn:service:business
- business.convention-center
urn:service:communication
- communication.internet.802.-11
- communication.internet.802.-16
Forte & Schulzrinne Expires July 5, 2009 [Page 3]
Internet-Draft Service Classification January 2009
- communication.internet.802.-3
- communication.public-phone
urn:service:cultural
- cultural.art-gallery
- cultural.library
- cultural.monument
- cultural.museum
- cultural.theater
urn:service:education
- education.college
- education.day-care-center
- education.nursery
- education.primary-school
- education.school
- education.secondary-school
urn:service:entertainment
- entertainment.arena
- entertainment.basketball-court
- entertainment.bingo-hall
- entertainment.casino
- entertainment.cinema
- entertainment.club
- entertainment.field.ice-hockey
- entertainment.field.soccer
Forte & Schulzrinne Expires July 5, 2009 [Page 4]
Internet-Draft Service Classification January 2009
- entertainment.park
- entertainment.race-track
- entertainment.stadium
- entertainment.stadium.baseball
- entertainment.stadium.football
- entertainment.stadium.soccer
urn:service:financial
- financial.atm
- financial.bank
- financial.currency-exchange
urn:service:food
- food.bakery
- food.bar
- food.beer-garden
- food.cafe
- food.cafeteria
- food.coffee-house
- food.doughnut-shop
- food.fast-service
- food.ice-cream-parlor
- food.pancake-house
- food.pizza
- food.pub
- food.root-beer-stand
Forte & Schulzrinne Expires July 5, 2009 [Page 5]
Internet-Draft Service Classification January 2009
- food.street-vendor
- food.tea-house
- food.restaurant.barbecue
- food.restaurant.buffet
- food.restaurant.cn
- food.restaurant.creole [Louisiana cuisine]
- food.restaurant.de
- food.restaurant.diner
- food.restaurant.drive-in
- food.restaurant.es
- food.restaurant.ethnic
- food.restaurant.fast-casual
- food.restaurant.fast-food
- food.restaurant.fr
- food.restaurant.gr
- food.restaurant.hamburger
- food.restaurant.hot-dog
- food.restaurant.it
- food.restaurant.kosher
- food.restaurant.kr
- food.restaurant.other
- food.restaurant.pizzeria
- food.restaurant.revolving
- food.restaurant.seafood
Forte & Schulzrinne Expires July 5, 2009 [Page 6]
Internet-Draft Service Classification January 2009
- food.restaurant.steakhouse
- food.restaurant.tavern
- food.restaurant.theme [Such as Disney restaurants]
- food.restaurant.us
- food.restaurant.vegan
- food.restaurant.vegetarian
[Generally speaking, one "restaurant" entry per country can be
added, each with its own country suffix. Suffixes to be used here
are specified in [ISO3166].]
urn:service:fuel
- fuel.biodiesel-station
- fuel.cng-station
- fuel.diesel-station
- fuel.electricity-station
- fuel.ethanol-station
- fuel.gasoline-station
- fuel.hydrogen-station
- fuel.lng-station
- fuel.lpg-station
urn:service:government
- government.courthouse
- government.military-base
- government.prison
urn:service:lodging
- lodging.bed-and-breakfast
Forte & Schulzrinne Expires July 5, 2009 [Page 7]
Internet-Draft Service Classification January 2009
- lodging.hostel
- lodging.hotel
- lodging.motel
urn:service:medical
- medical.dentist
- medical.emergency-room
- medical.hospital
- medical.veterinarian
urn:service:religious
- religious.church.adventist
- religious.church.anabaptist
- religious.church.anglican
- religious.church.baptist.national
- religious.church.baptist.southern
- religious.church.congregationalist
- religious.church.episcopalian
- religious.church.greek-orthodox
- religious.church.latter-day-saints [Also known as Mormon church]
- religious.church.lutheran
- religious.church.methodist
- religious.church.pentecostal
- religious.church.presbyterian
- religious.church.protestant
["Protestant" comprises: Adventist, Anabaptist, Baptist,
Congregationalist, Lutheran, Methodist, Presbyterian, Reformed,
Forte & Schulzrinne Expires July 5, 2009 [Page 8]
Internet-Draft Service Classification January 2009
Pentecostal, Restorationist]
- religious.church.reformed
- religious.church.restorationist
- religious.church.roman-catholic
- religious.house-of-worship
- religious.kingdom-hall
- religious.mosque
- religious.synagogue
- religious.temple.buddhist
- religious.temple.hindu
- religious.temple.masonic
urn:service:retail
- retail.bakery
- retail.barber
- retail.books
- retail.butcher
- retail.car-repair
- retail.clothing
- retail.electronics
- retail.fish
- retail.flowers
- retail.food
- retail.games
- retail.glass
Forte & Schulzrinne Expires July 5, 2009 [Page 9]
Internet-Draft Service Classification January 2009
- retail.jewelry
- retail.movies
- retail.music
- retail.news
- retail.optician
- retail.other
- retail.shoes
- retail.shopping-mall
- retail.spirits
- retail.tailor
- retail.travel
urn:service:transportation
- transportation.airport
- transportation.bycicle-rental
- transportation.bus-stop
- transportation.car-rental
- transportation.mechanic
- transportation.parking
- transportation.port
- transportation.subway
- transportation.taxi-stand
- transportation.train-station
4. Guidelines for the creation of new top-level services
The number of services that can be defined is very large. New
Forte & Schulzrinne Expires July 5, 2009 [Page 10]
Internet-Draft Service Classification January 2009
services, however, SHOULD at least satisfy the following guidelines.
- The service has to be of general interest;
- It should not be specific to a particular country or region;
- The language in which the new service is defined MUST be English
(this is a protocol token, not meant to be shown to humans);
- The newly defined services SHOULD correspond to a standard
statistical classification of enterprises or services, such as the
North American Industry Classification System (NAICS).
5. IANA Considerations
Registration template and URN scheme for emergency and non-emergency
services have been defined in [RFC5031] in Sections 3 and 4,
respectively.
5.1. Registering new tokens
This document creates new IANA registries for location-based services
as listed in Section 3, starting with
'urn:service:business.convention-center' and finishing with
'urn:service:transportation.train-station'.
Aside from the labels defined here, document
[draft-ietf-ecrit-service-urn-policy] defines the registration policy
for new service-identifying labels.
5.2. Internationalization Considerations
The service 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.
5.3. Security Considerations
This document defines a registry for location-based services and as
such does not raise security issues. The same security
considerations as in [RFC5031] apply.
6. References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Forte & Schulzrinne Expires July 5, 2009 [Page 11]
Internet-Draft Service Classification January 2009
[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031,
January 2008.
[RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H.
Tschofenig, "LoST: A Location-to-Service Translation
Protocol", RFC 5222, August 2008.
[RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types
Registry", July 2006.
[ISO3166] International Organization for Standardization (ISO),
"English country names and code elements", July 2006.
[draft-ietf-ecrit-service-urn-policy]
Forte, A. and H. Schulzrinne, "Policy for defining new
service-identifying labels for non-emergency services
(Internet draft - work in progress)", December 2009.
Authors' Addresses
Andrea G. Forte
Columbia University
Department of Computer Science
1214 Amsterdam Avenue, MC 0401
New York, NY 10027
USA
Email: andreaf@cs.columbia.edu
Henning Schulzrinne
Columbia University
Department of Computer Science
1214 Amsterdam Avenue, MC 0401
New York, NY 10027
USA
Email: hgs@cs.columbia.edu
Forte & Schulzrinne Expires July 5, 2009 [Page 12]
