idnits 2.17.1 draft-holmberg-ecrit-country-emg-urn-02.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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. -- The draft header indicates that this document updates RFC5031, but the abstract doesn't seem to directly say this. It does mention RFC5031 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5031, updated by this document, for RFC5378 checks: 2006-02-17) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 19, 2013) is 4055 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT Working Group C.H. Holmberg 3 Internet-Draft I.S. Sedlacek 4 Updates: 5031 (if approved) Ericsson 5 Intended status: Standards Track March 19, 2013 6 Expires: September 20, 2013 8 URN For Country Specific Emergency Services 9 draft-holmberg-ecrit-country-emg-urn-02.txt 11 Abstract 13 This document updates section 4.2 of RFC 5031, in order to allow the 14 registration of service URNs with the 'sos' service type for 15 emergency services that, at the time of registration, are offered in 16 one country only. 18 Status of This Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on September 20, 2013. 35 Copyright Notice 37 Copyright (c) 2013 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. 47 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 49 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 3. Problem statement . . . . . . . . . . . . . . . . . . . . . . 3 51 4. Requirement . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 5. Update to RFC 5031 . . . . . . . . . . . . . . . . . . . . . 3 53 5.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 5.2. Original text of section 4.2 of RFC 5031 . . . . . . . . 3 55 5.3. New text replacing section 4.2 of RFC 5031 . . . . . . . 5 56 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 57 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 59 9. Normative References . . . . . . . . . . . . . . . . . . . . 7 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 62 1. Introduction 64 Table 1 shows the policy for registration of sub-services of the 65 service URN with the 'sos' service type, as defined in section 4.2. 66 of RFC 5031 [RFC5031]. 68 +-------------------------------------------------------------------+ 69 | | 70 +-------------------------------------------------------------------+ 71 | The 'sos' service type describes emergency services requiring an | 72 | immediate response, typically offered by various branches of the | 73 | government or other public institutions. Additional sub-services | 74 | can be added after expert review and must be of general public | 75 | interest and have a similar emergency nature. The expert is | 76 | designated by the ECRIT working group, its successor, or, in | 77 | their absence, the IESG. The expert review should only approve | 78 | emergency services that are offered widely and in different | 79 | countries, with approximately the same caller expectation in | 80 | terms of services rendered. The 'sos' service is not meant to | 81 | invoke general government, public information, counseling, or | 82 | social services. | 83 +-------------------------------------------------------------------+ 85 Table 1: Excerpt from RFC 5031 section 4.2. 87 Some existing emergency services are, at least initially, offered in 88 one country only. Examples are the "Reporting spies" emergency 89 service offered in South Korea and the "GAULA (anti-kidnapping)" 90 emergency service offered in Colombia according to http:// 91 en.wikipedia.org/wiki/Emergency_telephone_number. Future emergency 92 service might also initially be introduced in one country only. 94 The policy for registration of sub-services of the service URN with 95 the 'sos' service type, as defined in RFC 5031 [RFC5031], prevents 96 the registration of a sub-service of the service URN with the 'sos' 97 service type for a service that, at the time of registration, is 98 offered in one country only. 100 This document updates section 4.2 of RFC 5031, in order to allow the 101 registration of service URNs with the 'sos' service type for 102 emergency services that, at the time of registration, are offered in 103 one country only. 105 2. Conventions 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in BCP 14, RFC 2119 110 [RFC2119]. 112 3. Problem statement 114 The policy for registration of sub-services of the service URN with 115 the 'sos' service type, as defined in RFC 5031 [RFC5031], prevents 116 the registration of a sub-service of the service URN with the 'sos' 117 service type for an emergency service that, at the time of 118 registration, is offered in one country only. 120 4. Requirement 122 REQ-1: It MUST be possible to register with IANA a sub-service of the 123 service URN with the 'sos' service type as, defined in RFC 5031 124 [RFC5031], for an emergency service offered in one country only. 126 5. Update to RFC 5031 128 5.1. General 130 This section document updates replaces the text of the section 4.2 131 (Sub-Services for the 'sos' Service) of RFC 5031 with the text of 132 section 6.3 of this document. 134 5.2. Original text of section 4.2 of RFC 5031 136 This section defines the first service registration within the IANA 137 registry defined in Section 4.1, using the top-level service label 138 'sos'. 140 The 'sos' service type describes emergency services requiring an 141 immediate response, typically offered by various branches of the 142 government or other public institutions. Additional sub-services can 143 be added after expert review and must be of general public interest 144 and have a similar emergency nature. The expert is designated by the 145 ECRIT working group, its successor, or, in their absence, the IESG. 146 The expert review should only approve emergency services that are 147 offered widely and in different countries, with approximately the 148 same caller expectation in terms of services rendered. The 'sos' 149 service is not meant to invoke general government, public 150 information, counseling, or social services. 152 urn:service:sos The generic 'sos' service reaches a public safety 153 answering point (PSAP), which in turn dispatches aid appropriate 154 to the emergency. It encompasses all of the services listed 155 below. 157 urn:service:sos.ambulance This service identifier reaches an 158 ambulance service that provides emergency medical assistance and 159 transportation. 161 urn:service:sos.animal-control Animal control typically enforces 162 laws and ordinances pertaining to animal control and management, 163 investigates cases of animal abuse, educates the community in 164 responsible pet ownership and wildlife care, and provides for the 165 housing and care of homeless animals, among other animal-related 166 services. 168 urn:service:sos.fire The 'fire' service identifier summons the fire 169 service, also known as the fire brigade or fire department. 171 urn:service:sos.gas The 'gas' service allows the reporting of 172 natural gas (and other flammable gas) leaks or other natural gas 173 emergencies. 175 urn:service:sos.marine The 'marine' service refers to maritime 176 search and rescue services such as those offered by the coast 177 guard, lifeboat, or surf lifesavers. 179 urn:service:sos.mountain The 'mountain' service refers to mountain 180 rescue services (i.e., search and rescue activities that occur in 181 a mountainous environment), although the term is sometimes also 182 used to apply to search and rescue in other wilderness 183 environments. 185 urn:service:sos.physician The 'physician' emergency service connects 186 the caller to a physician referral service. 188 urn:service:sos.poison The 'poison' service refers to special 189 information centers set up to inform citizens about how to respond 190 to potential poisoning. These poison control centers maintain a 191 database of poisons and appropriate emergency treatment. 193 urn:service:sos.police The 'police' service refers to the police 194 department or other law enforcement authorities. 196 5.3. New text replacing section 4.2 of RFC 5031 198 This section defines the first service registration within the IANA 199 registry defined in Section 4.1, using the top-level service label 200 'sos'. 202 The 'sos' service type describes emergency services requiring an 203 immediate response, typically offered by various branches of the 204 government or other public institutions. Additional sub-services can 205 be added after expert review. The expert is designated by the ECRIT 206 working group, its successor, or, in their absence, the IESG. The 207 expert review should only approve services that have emergency 208 nature, that are offered in at least one country, that do not match 209 description of any existing service URN with the 'sos' service type, 210 and where the service description and the URN are defined as broadly 211 as possible to encourage reuse. The 'sos' service is not meant to 212 invoke general government, public information, counseling, or social 213 services. 215 urn:service:sos The generic 'sos' service reaches a public safety 216 answering point (PSAP), which in turn dispatches aid appropriate 217 to the emergency. It encompasses all of the services listed 218 below. 220 urn:service:sos.ambulance This service identifier reaches an 221 ambulance service that provides emergency medical assistance and 222 transportation. 224 urn:service:sos.animal-control Animal control typically enforces 225 laws and ordinances pertaining to animal control and management, 226 investigates cases of animal abuse, educates the community in 227 responsible pet ownership and wildlife care, and provides for the 228 housing and care of homeless animals, among other animal-related 229 services. 231 urn:service:sos.fire The 'fire' service identifier summons the fire 232 service, also known as the fire brigade or fire department. 234 urn:service:sos.gas The 'gas' service allows the reporting of 235 natural gas (and other flammable gas) leaks or other natural gas 236 emergencies. 238 urn:service:sos.marine The 'marine' service refers to maritime 239 search and rescue services such as those offered by the coast 240 guard, lifeboat, or surf lifesavers. 242 urn:service:sos.mountain The 'mountain' service refers to mountain 243 rescue services (i.e., search and rescue activities that occur in 244 a mountainous environment), although the term is sometimes also 245 used to apply to search and rescue in other wilderness 246 environments. 248 urn:service:sos.physician The 'physician' emergency service connects 249 the caller to a physician referral service. 251 urn:service:sos.poison The 'poison' service refers to special 252 information centers set up to inform citizens about how to respond 253 to potential poisoning. These poison control centers maintain a 254 database of poisons and appropriate emergency treatment. 256 urn:service:sos.police The 'police' service refers to the police 257 department or other law enforcement authorities. 259 6. IANA Considerations 261 OPEN ISSUE: Do we need to request IANA to take the updated section 262 into consideration, or is IANA expected to do that by default, as the 263 document updates the RFC 5031 procedures? 265 7. Change Log 267 [RFC EDITOR NOTE: Please remove this section when publishing] 269 Changes from draft-holmberg-ecrit-country-emg-urn-01 271 o Technical fix: Instead of creating a new sub-tree, the 'sos' 272 registration rules in RFC 5031 are updated, to allow registration 273 of URNs that, at the time of registration, are specific to a 274 single country. 276 Changes from draft-holmberg-ecrit-country-emg-urn-00 278 o Editorial fix: cannot be not fulfilled -> cannot be fulfilled 280 8. Security Considerations 281 TBD 283 9. Normative References 285 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 286 Requirement Levels", BCP 14, RFC 2119, March 1997. 288 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 289 Emergency and Other Well-Known Services", RFC 5031, 290 January 2008. 292 Authors' Addresses 294 Christer Holmberg 295 Ericsson 296 Hirsalantie 11 297 Jorvas 02420 298 Finland 300 Email: christer.holmberg@ericsson.com 302 Ivo Sedlacek 303 Ericsson 304 Sokolovska 79 305 Praha 18600 306 Czech Republic 308 Email: ivo.sedlacek@ericsson.com