idnits 2.17.00 (12 Aug 2021) /tmp/idnits741/draft-lumbreras-ees-urn-00.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 14, 2012) is 3499 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2119' is defined on line 313, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Lumbreras 3 Internet-Draft European Emergency Number 4 Intended status: Standards Track Association (EENA) 5 Expires: April 17, 2013 H. Tschofenig 6 October 14, 2012 8 Uniform Resource Name (URN) Namespace for the European Emergency 9 Services 10 draft-lumbreras-ees-urn-00.txt 12 Abstract 14 This document describes the Namespace Identifier (NID) "eena" for 15 Uniform Resource Name (URN) resources published by the European 16 Emergency Number Association (EENA). EENA defines and manages 17 resources that utilize this URN model. Management activities for 18 these and other resource types are provided by the European Emergency 19 Services Registry (EESR). 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on April 17, 2013. 38 Copyright Notice 40 Copyright (c) 2012 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. URN Specification for 'ees' NID . . . . . . . . . . . . . . . 4 57 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 58 4. Namespace Considerations . . . . . . . . . . . . . . . . . . . 8 59 5. Community Considerations . . . . . . . . . . . . . . . . . . . 9 60 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 61 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 62 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 64 9.1. Normative References . . . . . . . . . . . . . . . . . . . 13 65 9.2. Informative References . . . . . . . . . . . . . . . . . . 13 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 68 1. Introduction 70 The European Emergency Number Association (EENA) is currently in the 71 process of setting standards, processes, and procedures for the use 72 of an IP-based Emergency Services IP Network (ESInet) for all public 73 safety entities in Europe. Some of the solutions being developed by 74 EENA require namespaces that are managed so that they are unique and 75 persistent. To assure that the uniqueness is absolute, the 76 registration of a specific Uniform Resource Name (URN) [RFC2141] 77 Namespace ID (NID) for use by EENA is required. This document 78 defines and registers such a namespace in accordance with the 79 procedures in [RFC3406]. 81 2. URN Specification for 'ees' NID 83 Namespace ID: ees 85 Registration information: 87 Registration version number: 1 89 Registration date: 2012-09-26 91 Declared registrant of the namespace: 93 Registering organization 95 Name: European Emergency Number Association (EENA) 97 Address: 99 Avenue de la Toison d'Or 79, 101 1060 Brussels 103 Belgium 105 Designated contact: 107 Role: European Emergency Services Registry Administrator 109 Email: eesr-admin@eena.org 111 Declaration of syntactic structure: 113 The Namespace Specific String (NSS) of all URNs that use the 114 "eena" NID will have the following structure: {EESclass}: 115 {ClassSpecificString} 117 The "EESclass" conforms to the URN syntax requirements [RFC2141] 118 and defines a specific class of resource type. Each class will 119 have a specific labeling scheme that is covered by 120 "ClassSpecificString", which also conforms to the naming 121 requirements of [RFC2141]. 123 EENA maintains a naming authority, the European Emergency Service 124 Registry (EESR), that will manage the assignment of "EESclass" and 125 the specific registration values assigned for each class. Other 126 EENA standards documents will define the "ClassSpecificStrings" 127 for a given "EESclass". 129 Relevant ancillary documentation: 131 The European Emergency Service Registry (EESR) provides 132 information on the registered resources and the registrations for 133 each. More information about the EESR and the registration 134 activities and procedures to be followed are defined in the "EENA 135 Registry System Standard" [EENA-RSS]. 137 Identifier uniqueness considerations: 139 The EESR will manage resources using the "ees" NID and will be the 140 authority for managing the resources and subsequent strings 141 associated. The EESR shall ensure the uniqueness of all ees URNs 142 by checking such names against the list of existing namespace 143 names, as documented in [EENA-RSS]. 145 Identifier persistence considerations: 147 The EESR will provide clear documentation of the registered uses 148 of the "ees" NID. The EESR will establish a registry for 149 "EESclass", as defined in [EENA-RSS]. Each "EESclass" will have a 150 separate description in the registry and may have its own sub- 151 registry. In particular, new "EESclass" registry entries will 152 require a full EENA Technical Standard document. 154 The EESR will maintain a website at a stable address that provides 155 XML and text renderings of the urn:ees registry. 157 Process of identifier assignment: 159 The EESR processes and procedures for identifier assignment are 160 documented in [EENA-RSS]. The registry that will control the 161 urn:ees namespace is defined in [EENA-RSS]. In particular, 162 assignments to the "EESclass" registry will require a EENA 163 Technical Standard document. Subregistries for particular 164 "EENAclasses" may be established by such technical standards. 165 Subregistries may be defined to have more liberal management 166 policies as defined in [EENA-RSS], but must be EESR managed and 167 will not be permitted to be delegated to any other organization or 168 registry. Thus, the EESR will manage the entire urn:ees tree. 170 Process for identifier resolution: 172 The namespace is not currently listed with a Resolution Discovery 173 System (RDS), but nothing about the namespace prohibits the future 174 definition of appropriate resolution methods or listing with an 175 RDS. 177 Rules for lexical equivalence: 179 No special considerations; the rules for lexical equivalence of 180 [RFC2141] apply. 182 Conformance with URN syntax: 184 No special considerations. 186 Validation mechanism: 188 None specified. URN assignment will be handled by procedures 189 implemented in support of EENA activities. 191 Scope: 193 Global 195 3. Examples 197 The following examples are representative URNs that could be assigned 198 by the ERS. They may not be the actual strings that would be 199 assigned. 201 Resource "psaproute" 203 Syntax: "urn:ees:emergencyresponders:" 205 ResourceSpecificString: simple string with name of responder, defined 206 in a subregistry 208 Use: Defines the URN to be used for queries to an NG112 Emergency 209 Call Routing Function that provides URIs for responding agencies. 211 Examples: 213 urn:ees:emergencyresponders:ambulance 215 urn:ees:emergencyresponders:fire 217 urn:ees:emergencyresponders:police 219 urn:ees:emergencyresponders:poison 221 urn:ees:emergencyresponders:coastguard 223 urn:ees:emergencyresponders:marine 225 4. Namespace Considerations 227 The European Emergency Number Association is a Brussels-based NGO set 228 up in 1999 dedicated to promoting high-quality emergency services 229 reached by the number 112 throughout the EU. EENA serves as a 230 discussion platform for emergency services, public authorities, 231 decision makers, associations and solution providers in view of 232 improving emergency response in accordance with citizens' 233 requirements. EENA is also promoting the establishment of an 234 efficient system for alerting citizens about imminent or developing 235 emergencies. 237 The EENA memberships include about 655 emergency services 238 representatives from 43 European countries, 56 solution providers, 9 239 international associations/organisations as well as 26 Members of the 240 European Parliament. 242 EENA members do their work in committees, which also includes a 243 technical committee that develops a variety of applications and 244 services using Internet protocols built upon IETF standards. Some of 245 these services require that supporting information (e.g., data 246 descriptions, attributes, etc.) be fully specified. For proper 247 operation, descriptions of the needed supporting information must 248 exist and be available in a unique, reliable, and persistent manner. 249 These dependencies provide the basis of the need for namespaces, in 250 one form or another, and will enable EENA to define URNs that are to 251 assign cleaner, more general, more permanent, more reliable, and more 252 controllable namespace names related to EENA standards, while keeping 253 URNs defined by EENA properly separate from the IETF-defined URNs. 255 As the European Emergency Number Association work is ongoing and 256 covers many technical areas, the possibility of binding to various 257 other namespace repositories has been deemed impractical. Each 258 object or description, as defined in EENA, could possibly be related 259 to multiple different namespaces, so further conflicts of association 260 could occur. Thus, the intent is to utilize the European Emergency 261 Services Registry, operated by EENA, as the naming authority for 262 EENA-defined objects and descriptions. 264 5. Community Considerations 266 The European public safety organizations will benefit from 267 publication of this namespace by having permanent and reliable URNs 268 to be used with protocols defined by EENA. The objects and 269 descriptions required for services defined by EENA are generally 270 available for use by other organizations. The European Emergency 271 Number Association will provide access and support for name requests 272 by these organizations within the constraints of the defined ERS 273 processes and the specific urn:eena registry and subregistries. This 274 support can be enabled in a timely and responsive fashion as new 275 objects and descriptions are produced. These will be enabled in a 276 fashion similar to current IANA processes, as documented in 277 [EENA-RSS]. 279 The EESR establishes registries when called for in a EENA Technical 280 Standard. Such standards must provide clear and concise instructions 281 on creating and maintaining such registries. Defined management 282 policies include "EENA Technical Standard Required", "EENA Document 283 Required", "Expert Review", and "First Come First Served", which 284 correspond to similar IANA management policies. EENA is establishing 285 a website that provides controlled entry of new registries and 286 entries in registries, and automatically produces HTML and XML 287 descriptions of registry contents that are used by vendors and other 288 consumers of the content. 290 6. Security Considerations 292 There are no additional security considerations other than those 293 normally associated with the use and resolution of URNs in general. 295 7. IANA Considerations 297 This document adds a new entry in the URN Namespaces registry. The 298 namespace is "eena". The defining document is this RFC. The entry 299 can be found in the Uniform Resource Names (URN) Namespaces registry 300 available from http://www.iana.org and any associated mirrors. 302 8. Acknowledgements 304 We would like to thank Brian Rosen for his work on RFC 6061. We have 305 re-used his writeup since it aims to accomplish the same goal. His 306 work was focused on the National Emergency Number Association, a 307 partner organization of EENA. 309 9. References 311 9.1. Normative References 313 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 314 Requirement Levels", March 1997. 316 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 318 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 319 "Uniform Resource Names (URN) Namespace Definition 320 Mechanisms", BCP 66, RFC 3406, October 2002. 322 9.2. Informative References 324 [EENA-RSS] 325 EENA, "EENA Registry System Standard", October 2012. 327 Authors' Addresses 329 Cristina Lumbreras 330 European Emergency Number Association (EENA) 332 Phone: 333 Email: cl@eena.org 335 Hannes Tschofenig 337 Email: Hannes.Tschofenig@gmx.net