idnits 2.17.1 draft-rosen-ecrit-service-urn-subregistries-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 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 (October 30, 2017) is 2370 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 H. Schulzrinne 5 Expires: May 3, 2018 Columbia University 6 October 30, 2017 8 A Subregistry for urn:service:sos.police, fire and ambulance 9 draft-rosen-ecrit-service-urn-subregistries-01 11 Abstract 13 In most countries, there are multiple kinds of police forces. 14 RFC5031 defines a "Service URN" which is used to route emergency 15 calls. The urn has a sub registry for different kinds of emergency 16 services that may be reached from different telephone numbers or 17 service numbers (as opposed to a single number like 112). In many 18 countries, the "police" service is not a single service, but more 19 than one service where the service area and/or types of emergencies 20 they respond to are different. In some countries there are multiple 21 ambulance services. This document defines sub registries for 22 urn:service:sos.police, urn:service:sos.ambulance and, for 23 completeness, urn:service:sos.fire. It also provides an initial set 24 of entries for these sub registries. These services are in addition 25 to the base urn:service:sos.police, etc. services. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on May 3, 2018. 44 Copyright Notice 46 Copyright (c) 2017 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 62 1.1. Police Force Types . . . . . . . . . . . . . . . . . . . 2 63 1.2. Ambulance Types . . . . . . . . . . . . . . . . . . . . . 3 64 1.3. Fire Types . . . . . . . . . . . . . . . . . . . . . . . 4 65 1.4. Additional Services in Counseling . . . . . . . . . . . . 4 66 1.5. Other sos services . . . . . . . . . . . . . . . . . . . 6 67 1.6. Government services top level entry . . . . . . . . . . . 8 68 1.7. Government services sub registry . . . . . . . . . . . . 8 69 2. Security Considerations . . . . . . . . . . . . . . . . . . . 9 70 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 71 4. Normative References . . . . . . . . . . . . . . . . . . . . 9 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 74 1. IANA Considerations 76 1.1. Police Force Types 78 This document extends the urn:service:sos.police to allow the system 79 to distinguish law enforcement agencies. The type of law enforcement 80 agency is a token separated from urn:service.sos.police by a period. 81 The token names are suggestive of the names for different kinds of 82 police forces but is not supposed to be the literal name of the 83 force. 85 IANA is requested to add a sub registry to the Service URN Labels 86 under sos Sub-Services entitled sos.police Sub-Services. The 87 registry should have Service, Description and References as in the 88 other sub registries for the service urn. The Registration Procedure 89 is Expert review. The expert shall use the same criteria as the 90 other urn:service:sos entries. The initial values of the sub 91 registry are: 93 +-----------------------+-----------+-------------------------------+ 94 | Service | Reference | Description | 95 +-----------------------+-----------+-------------------------------+ 96 | sos.police.national | this | A police force serving an | 97 | | document | entire nation | 98 | | | | 99 | sos.police.provincial | this | A police force serving a | 100 | | document | province or state | 101 | | | | 102 | sos.police.county | this | A police force serving a | 103 | | document | county | 104 | | | | 105 | sos.police.municipal | this | A police force serving a | 106 | | document | city, town or other | 107 | | | incorporated municipality | 108 | | | | 109 | sos.police.tourist | this | A police force serving the | 110 | | document | needs of international | 111 | | | tourists | 112 | | | | 113 | sos.police.traffic | this | A police force ensuring | 114 | | document | compliance with traffic laws, | 115 | | | directing traffic and | 116 | | | handling vehicular accidents | 117 +-----------------------+-----------+-------------------------------+ 119 Table 1: urn:service:sos.police sub registry initial contents 121 1.2. Ambulance Types 123 This document extends the urn:service:sos.ambulance to allow the 124 system to distinguish ambulance services. The type of service is a 125 token separated from urn:service.sos.ambulance by a period. The 126 token names are suggestive of the names for different kinds of 127 ambulance services but is not supposed to be the literal name of the 128 service. 130 IANA is requested to add a sub registry to the Service URN Labels 131 under sos Sub-Services entitled sos.ambulance Sub-Services. The 132 registry should have Service, Description and References as in the 133 other sub registries for the service urn. The Registration Procedure 134 is Expert review. The expert shall use the same criteria as the 135 other urn:service:sos entries. The initial values of the sub 136 registry are: 138 +-----------------------+-----------+-------------------------------+ 139 | Service | Reference | Description | 140 +-----------------------+-----------+-------------------------------+ 141 | sos.ambulance.public | this | An ambulance service that is | 142 | | document | operated by a government | 143 | | | agency | 144 | | | | 145 | sos.ambulance.private | this | An ambulance service that is | 146 | | document | operated by a private company | 147 | | | | 148 | sos.ambulance.air | this | An ambulance service that | 149 | | document | uses a helicopter or airplane | 150 +-----------------------+-----------+-------------------------------+ 152 Table 2: urn:service:sos.ambulance sub registry initial contents 154 1.3. Fire Types 156 This document extends the urn:service:sos.fire to allow the type of 157 fire service. The type of service is a token separated from 158 urn:service.sos.fire by a period. The token names are suggestive of 159 the names for different kinds of fire services but is not supposed to 160 be the literal name of the service. 162 IANA is requested to add a sub registry to the Service URN Labels 163 under sos Sub-Services entitled sos.fire Sub-Services. The registry 164 should have Service, Description and References as in the other sub 165 registries for the service urn. The Registration Procedure is Expert 166 review. The expert shall use the same criteria as the other 167 urn:service:sos entries. The initial values of the sub registry are: 169 +-------------------+-----------------------------------+-----------+ 170 | Service | Description | Reference | 171 +-------------------+-----------------------------------+-----------+ 172 | sos.fire.wildfire | A fire service that specializes | this | 173 | | in wild fires, for example, | document | 174 | | forest fires | | 175 +-------------------+-----------------------------------+-----------+ 177 Table 3: urn:service:sos.fire sub registry initial contents 179 1.4. Additional Services in Counseling 181 IANA is requested to add the following services in the 'counseling' 182 Sub-Services registry: 184 +-----------------------------+-----------------------+-------------+ 185 | Service | Reference | Description | 186 +-----------------------------+-----------------------+-------------+ 187 | counseling.shelter | Provides advice and | this | 188 | | referrals to callers | document | 189 | | needing non-emergency | | 190 | | medical information. | | 191 | | | | 192 | counseling.parents | Provides advice and | this | 193 | | referrals to parents | document | 194 | | needing assistance. | | 195 | | | | 196 | counseling.women | Provides advice and | this | 197 | | referrals to women | document | 198 | | | | 199 | counseling.missing-children | Provides reporting | this | 200 | | ability and accepts | document | 201 | | information about | | 202 | | missing children. | | 203 | | | | 204 | counseling.missing-person | Provides reporting | this | 205 | | ability and accepts | document | 206 | | information about | | 207 | | missing persons. | | 208 | | | | 209 | counseling.crime-victim | Provides advice and | this | 210 | | referrals to crime | document | 211 | | victims. | | 212 | | | | 213 | counseling.tourists | Provides advice and | this | 214 | | referrals to | document | 215 | | tourists. | | 216 | | | | 217 | counseling.social-services | Provides advice and | this | 218 | | referrals to callers | document | 219 | | needing social | | 220 | | services. | | 221 | | | | 222 | counseling.shelter | Provides advice and | this | 223 | | referrals to callers | document | 224 | | needing shelter. | | 225 +-----------------------------+-----------------------+-------------+ 227 Table 4 229 1.5. Other sos services 231 IANA is requested to add the following entries to the 'sos' Sub- 232 Services registry: 234 +----------------------+------------------------------+-------------+ 235 | Service | Reference | Description | 236 +----------------------+------------------------------+-------------+ 237 | sos.water | Water main breaks and other | this | 238 | | water emergencies | document | 239 | | | | 240 | sos.electric | Emergencies related to | this | 241 | | utility electric power | document | 242 | | | | 243 | sos.aeronautical | aeronautical emergencies | this | 244 | | sos.aeronautical reaches | document | 245 | | services that handle | | 246 | | emergencies related to | | 247 | | aircraft, such as plane | | 248 | | crashes, rather than air | | 249 | | ambulance services. | | 250 | | | | 251 | sos.child-protection | Summon help for abused or | this | 252 | | neglected children | document | 253 | | | | 254 | sos.disaster | Help during natural and man- | this | 255 | | made disasters such as | document | 256 | | storms, earthquakes and | | 257 | | floods | | 258 | | | | 259 | sos.message | Emergency services reached | this | 260 | | using message-based | document | 261 | | communication, e.g., short | | 262 | | message service (SMS) or | | 263 | | fax. sos.message is only | | 264 | | meant to be used in cases | | 265 | | where a country has | | 266 | | established a separate | | 267 | | emergency number to be used | | 268 | | for fax, TTY or text | | 269 | | messages, e.g., for people | | 270 | | who are Deaf or hard-of- | | 271 | | hearing. The URN should not | | 272 | | be used if text messages can | | 273 | | be sent to the general | | 274 | | service:sos URN or if real- | | 275 | | time text or TTY calls can | | 276 | | reach the general | | 277 | | service:sos URN | | 278 +----------------------+------------------------------+-------------+ 280 Table 5 282 1.6. Government services top level entry 284 IANA is requested to add a new entry to the URN Service Labels 285 Registry: 287 +------------+----------------------------------------+-------------+ 288 | Service | Reference | Description | 289 +------------+----------------------------------------+-------------+ 290 | government | non-emergency services offered by | this | 291 | | various branches of government | document | 292 +------------+----------------------------------------+-------------+ 294 Table 6 296 1.7. Government services sub registry 298 IANA is requested to create a new 'government Sub-Services' sub 299 registry in the URN Service Labels registry. The 'government' 300 service is used for general informational services that provide 301 residents access and information about government services relevant 302 to their current location. For example, in the United States and 303 Canada, 311 is used for this purpose. 305 Additional sub-services can be added after expert review and must be 306 of general public interest. The expert is designated by the ECRIT 307 working group, its successor, or, in their absence, the IESG. The 308 expert review should only approve government services that are 309 offered widely and in different countries, with approximately the 310 same caller expectation in terms of services rendered. 312 A new entry must specify the service name, description and a 313 reference similar to other Sub Registries in the URN Service Label 314 registry. The initial values in this sub registry are: 316 +---------------------------+-------------------------+-------------+ 317 | Service | Reference | Description | 318 +---------------------------+-------------------------+-------------+ 319 | government.police | Used for non-emergency | this | 320 | | calls, e.g., to report | document | 321 | | a crime that took place | | 322 | | in the past | | 323 | | | | 324 | government.ambulance> | A non-emergency medical | this | 325 | | transport service | document | 326 | | | | 327 | government.crime-reports> | A non-emergency medical | this | 328 | | transport service | document | 329 +---------------------------+-------------------------+-------------+ 331 Table 7 333 2. Security Considerations 335 This document has the same security considerations as those in 336 [RFC5031]. 338 3. Acknowledgements 340 Ivo Sedlacek described the problem and attempted to register a 341 service with a specific police force as distinct from 342 urn:service:sos.police. This work was inspired by his problem. 344 4. Normative References 346 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 347 Emergency and Other Well-Known Services", RFC 5031, 348 DOI 10.17487/RFC5031, January 2008, 349 . 351 Authors' Addresses 353 Brian Rosen 354 Neustar, Inc 355 470 Conrad Dr 356 Mars, PA 16046 357 US 359 Phone: +1 724-382-1051 360 Email: br@brianrosen.net 361 Henning Schulzrinne 362 Columbia University 363 Department of Computer Science 364 450 Computer Science Building 365 New York, NY 10027 366 US 368 Phone: +1 212 939 7004 369 Email: hgs+ecrit@cs.columbia.edu 370 URI: http://www.cs.columbia.edu