idnits 2.17.1 draft-ietf-ecrit-service-urn-policy-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 17, 2012) is 4147 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Forte 3 Internet-Draft AT&T 4 Intended status: BCP H. Schulzrinne 5 Expires: June 20, 2013 Columbia University 6 December 17, 2012 8 Policy for defining new service-identifying lables 9 draft-ietf-ecrit-service-urn-policy-01.txt 11 Abstract 13 In order to provide location-based services, descriptive terms for 14 services need to be defined. This document updates the policy for 15 defining new service-identifying labels. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on June 20, 2013. 34 Copyright Notice 36 Copyright (c) 2012 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3 53 3. Guidelines for the creation of new top-level services . . . . . 3 54 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 56 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 59 1. Introduction 61 Nowadays location-based services are widespread. Devices can detect 62 a user location and retrieve all available services in the 63 sourroundings of that location. A particular service can be 64 described by one or multiple terms such as "restaurant", "parking" 65 and "ATM machine". All such terms, however, need to be formally 66 defined so that a registry can be built and used to assure 67 consistency and compatibility between devices and between service 68 providers. Since descriptive terms for services are almost 69 unbounded, such registry would contain the most common terms. In 70 this document we update the policy for defining new terms, that is 71 new service-identifying labels. 73 2. Requirements notation 75 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 76 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 77 document are to be interpreted as described in [RFC2119]. 79 3. Guidelines for the creation of new top-level services 81 The number of services that can be defined is very large. New 82 services, however, SHOULD at least satisfy the following guidelines. 84 - The service has to be of general interest; 86 - It should not be specific to a particular country or region; 88 - The language in which the new service is defined MUST be English 89 (this is a protocol token, not meant to be shown to humans); 91 - The newly defined services SHOULD correspond to a standard 92 statistical classification of enterprises or services, such as the 93 North American Industry Classification System (NAICS). 95 4. IANA Considerations 97 This document updates Section 4.1 of [RFC5031] in that the policy for 98 adding top-level service labels is "Expert Review". The expert is 99 designated by the RAI Area Director. 101 5. Security Considerations 103 This document does not raise security issues. 105 6. References 107 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 108 Requirement Levels", BCP 14, RFC 2119, March 1997. 110 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 111 Emergency and Other Well-Known Services", RFC 5031, 112 January 2008. 114 Authors' Addresses 116 Andrea G. Forte 117 AT&T 118 Security Research Center 119 33 Thomas Street 120 New York, NY 10007 121 USA 123 Email: forte@att.com 125 Henning Schulzrinne 126 Columbia University 127 Department of Computer Science 128 1214 Amsterdam Avenue, MC 0401 129 New York, NY 10027 130 USA 132 Email: hgs@cs.columbia.edu