idnits 2.17.1 draft-rosen-ecrit-service-urn-subregistries-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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 16, 2016) is 2687 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- 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 ecrit B. Rosen 3 Internet-Draft Neustar, Inc 4 Intended status: Informational December 16, 2016 5 Expires: June 19, 2017 7 A Subregistry for urn:service:sos.police, fire and ambulance 8 draft-rosen-ecrit-service-urn-subregistries-00 10 Abstract 12 In most countries, there are multiple kinds of police forces. 13 RFC5031 defines a "Service URN" which is used to route emergency 14 calls. The urn has a sub registry for different kinds of emergency 15 services that may be reached from different telephone numbers or 16 service numbers (as opposed to a single number like 112). In many 17 countries, the "police" service is not a single service, but more 18 than one service where the service area and/or types of emergencies 19 they respond to are different. In some countries there are multiple 20 ambulance services. This document defines sub registries for 21 urn:service:sos.police, urn:service:sos.ambulance and, for 22 completeness, urn:service:sos.fire. It also provides an initial set 23 of entries for these sub registries. These services are in addition 24 to the base urn:service:sos.police, etc. services. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on June 19, 2017. 43 Copyright Notice 45 Copyright (c) 2016 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. Police Force Types . . . . . . . . . . . . . . . . . . . 2 62 1.2. Ambulance Types . . . . . . . . . . . . . . . . . . . . . 3 63 1.3. Fire Types . . . . . . . . . . . . . . . . . . . . . . . 4 64 2. Security Considerations . . . . . . . . . . . . . . . . . . . 4 65 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 66 4. Normative References . . . . . . . . . . . . . . . . . . . . 4 67 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 69 1. IANA Considerations 71 1.1. Police Force Types 73 This document extends the urn:service:sos.police to allow the type of 74 police force. The type of force is a token separated from 75 urn:service.sos.police by a period. The token names are suggestive 76 of the names for different kinds of police forces but is not supposed 77 to be the literal name of the force. 79 IANA is requested to add a sub registry to the Service URN Labels 80 under sos Sub-Services entitled sos.police Sub-Services. The 81 registry should have Service, Description and References as in the 82 other sub registries for the service urn. The Registration Procedure 83 is Expert review. The expert shall use the same criteria as the 84 other urn:service:sos entries. The initial values of the sub 85 registry are: 87 +------------+-----------+------------------------------------------+ 88 | Service | Reference | Description | 89 +------------+-----------+------------------------------------------+ 90 | federal | this | A police force serving an entire nation | 91 | | document | | 92 | | | | 93 | provincial | this | A police force serving a province or | 94 | | document | state | 95 | | | | 96 | county | this | A police force serving a county | 97 | | document | | 98 | | | | 99 | municipal | this | A police force serving a city, town or | 100 | | document | other incorporated municipality | 101 +------------+-----------+------------------------------------------+ 103 Table 1: urn:service:sos.police sub registry initial contents 105 1.2. Ambulance Types 107 This document extends the urn:service:sos.ambulance to allow the type 108 of ambulance. The type of service is a token separated from 109 urn:service.sos.ambulance by a period. The token names are 110 suggestive of the names for different kinds of ambulance services but 111 is not supposed to be the literal name of the service. 113 IANA is requested to add a sub registry to the Service URN Labels 114 under sos Sub-Services entitled sos.ambulance Sub-Services. The 115 registry should have Service, Description and References as in the 116 other sub registries for the service urn. The Registration Procedure 117 is Expert review. The expert shall use the same criteria as the 118 other urn:service:sos entries. The initial values of the sub 119 registry are: 121 +---------+------------+--------------------------------------------+ 122 | Service | Reference | Description | 123 +---------+------------+--------------------------------------------+ 124 | public | this | An ambulance service that is operated by a | 125 | | document | government agency | 126 | | | | 127 | private | this | An ambulance service that is operated by a | 128 | | document | private company | 129 | | | | 130 | air | this | An ambulance service that uses a | 131 | | document | helicopter or airplane | 132 +---------+------------+--------------------------------------------+ 134 Table 2: urn:service:sos.ambulance sub registry initial contents 136 1.3. Fire Types 138 This document extends the urn:service:sos.fire to allow the type of 139 fire service. The type of service is a token separated from 140 urn:service.sos.fire by a period. The token names are suggestive of 141 the names for different kinds of fire services but is not supposed to 142 be the literal name of the service. 144 IANA is requested to add a sub registry to the Service URN Labels 145 under sos Sub-Services entitled sos.fire Sub-Services. The registry 146 should have Service, Description and References as in the other sub 147 registries for the service urn. The Registration Procedure is Expert 148 review. The expert shall use the same criteria as the other 149 urn:service:sos entries. The initial values of the sub registry are: 151 +----------+-----------+--------------------------------------------+ 152 | Service | Reference | Description | 153 +----------+-----------+--------------------------------------------+ 154 | wildfire | this | A fire service that specializes in wild | 155 | | document | fires, for example, forest fires | 156 +----------+-----------+--------------------------------------------+ 158 Table 3: urn:service:sos.fire sub registry initial contents 160 2. Security Considerations 162 This document has the same security considerations as those in 163 [RFC5031]. 165 3. Acknowledgements 167 Ivo Sedlacek described the problem and attempted to register a 168 service with a specific police force as distinct from 169 urn:service:sos.police. This work was inspired by his problem. 171 4. Normative References 173 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 174 Emergency and Other Well-Known Services", RFC 5031, 175 DOI 10.17487/RFC5031, January 2008, 176 . 178 Author's Address 179 Brian Rosen 180 Neustar, Inc 181 470 Conrad Dr 182 Mars, PA 16046 183 US 185 Phone: +1 724-382-1051 186 Email: br@brianrosen.net