[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 draft-ietf-ecrit-service-urn-policy

Network Working Group                                           A. Forte
Internet-Draft                                            H. Schulzrinne
Intended status: Standards Track                     Columbia University
Expires: September 24, 2009                               March 23, 2009


           Policy for defining new service-identifying labels
              draft-forte-ecrit-service-urn-policy-00.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 September 24, 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

   In order to provide location-based services, descriptive terms for
   services need to be defined.  This document updates the policy for
   defining new service-identifying labels.



Forte & Schulzrinne    Expires September 24, 2009               [Page 1]


Internet-Draft             Service URN Policy                 March 2009


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
     3.1.  New Service-Identifying Labels  . . . . . . . . . . . . . . 3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 3










































Forte & Schulzrinne    Expires September 24, 2009               [Page 2]


Internet-Draft             Service URN Policy                 March 2009


1.  Introduction

   Nowadays location-based services are widespread.  Devices can detect
   a user location and retrieve all available services in the
   sourroundings of that location.  A particular service can be
   described by one or multiple terms such as "restaurant", "parking"
   and "ATM machine".  All such terms, however, need to be formally
   defined so that a registry can be built and used to assure
   consistency and compatibility between devices and between service
   providers.  Since descriptive terms for services are almost
   unbounded, such registry would contain the most common terms.  In
   this document we update the policy for defining new terms, that is
   new service-identifying labels.


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.  IANA Considerations

3.1.  New Service-Identifying Labels

   This document updates Section 4.1 of [RFC5031] in that the policy for
   adding top-level service labels is "Expert Review".  The expert is
   designated by the RAI Area Director.


4.  Security Considerations

   This document does not raise security issues.


5.  References

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

   [RFC5031]  Schulzrinne, H., "A Uniform Resource Name (URN) for
              Emergency and Other Well-Known Services", RFC 5031,
              January 2008.







Forte & Schulzrinne    Expires September 24, 2009               [Page 3]


Internet-Draft             Service URN Policy                 March 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 September 24, 2009               [Page 4]


Html markup produced by rfcmarkup 1.127, available from https://tools.ietf.org/tools/rfcmarkup/