datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Labels for Common Location-Based Services
draft-forte-ecrit-service-classification-03

Document type: Active Internet-Draft (individual)
Document stream: ISE
Last updated: 2013-02-11 (latest revision 2010-01-15)
Intended RFC status: Unknown
Other versions: plain text, pdf, html

ISE State: Response to Review Needed
Revised I-D Needed
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

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

[include full document text]