[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-forte-ecrit-service-urn-policy) 00 01 02 03 04

Network Working Group                                           A. Forte
Internet-Draft                                                      AT&T
Intended status: BCP                                      H. Schulzrinne
Expires: December 13, 2012                           Columbia University
                                                           June 11, 2012


           Policy for defining new service-identifying lables
               draft-ietf-ecrit-service-urn-policy-00.txt

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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on December 13, 2012.

Copyright Notice

   Copyright (c) 2012 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.




Forte & Schulzrinne     Expires December 13, 2012               [Page 1]


Internet-Draft             Service URN Policy                  June 2012


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 3











































Forte & Schulzrinne     Expires December 13, 2012               [Page 2]


Internet-Draft             Service URN Policy                  June 2012


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

   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 December 13, 2012               [Page 3]


Internet-Draft             Service URN Policy                  June 2012


Authors' Addresses

   Andrea G. Forte
   AT&T
   Security Research Center
   33 Thomas Street
   New York, NY  10007
   USA

   Email: forte@att.com


   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 December 13, 2012               [Page 4]


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