idnits 2.17.1 draft-ietf-ecrit-country-emg-urn-03.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 == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. (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 (January 8, 2014) is 3754 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 (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT Working Group C. Holmberg 3 Internet-Draft I. Sedlacek 4 Updates: 5031 (if approved) Ericsson 5 Intended status: Standards Track January 8, 2014 6 Expires: July 12, 2014 8 URN For Country Specific Emergency Services 9 draft-ietf-ecrit-country-emg-urn-03.txt 11 Abstract 13 Section 4.2 of RFC 5031 allows the registration of service URNs with 14 the 'sos' service type only for emergency services "that are offered 15 widely and in different countries". This document updates those 16 instructions in RFC 5031 to allow such registrations when, at the 17 time of registration, those services are offered in one country only. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on July 12, 2014. 36 Copyright Notice 38 Copyright (c) 2014 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Update to RFC 5031 . . . . . . . . . . . . . . . . . . . . . 3 56 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3.2. New text replacing the text of the 2nd paragraph of 58 section 4.2 of RFC 5031 . . . . . . . . . . . . . . . . . 3 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 60 5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 62 7. Normative References . . . . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 Table 1 shows the policy for registration of sub-services of the 68 service URN with the 'sos' service type, as defined in section 4.2. 69 of RFC 5031 [RFC5031]. 71 +-------------------------------------------------------------------+ 72 | The 'sos' service type describes emergency services requiring an | 73 | immediate response, typically offered by various branches of the | 74 | government or other public institutions. Additional sub-services | 75 | can be added after expert review and must be of general public | 76 | interest and have a similar emergency nature. The expert is | 77 | designated by the ECRIT working group, its successor, or, in | 78 | their absence, the IESG. The expert review should only approve | 79 | emergency services that are offered widely and in different | 80 | countries, with approximately the same caller expectation in | 81 | terms of services rendered. The 'sos' service is not meant to | 82 | invoke general government, public information, counseling, or | 83 | social services. | 84 +-------------------------------------------------------------------+ 86 Table 1: Excerpt from RFC 5031 section 4.2. 88 Some existing emergency services are, at least initially, offered in 89 one country only. Examples are the "Reporting spies" emergency 90 service offered in South Korea and the "GAULA (anti-kidnapping)" 91 emergency service offered in Colombia according to http:// 92 en.wikipedia.org/wiki/Emergency_telephone_number (as per January 8th 93 2014). Future emergency service might also initially be introduced 94 in one country only. 96 The policy for registration of sub-services of the service URN with 97 the 'sos' service type, as defined in RFC 5031 [RFC5031], prevents 98 the registration of a sub-service of the service URN with the 'sos' 99 service type for a service that, at the time of registration, is 100 offered in one country only. 102 This document updates the 2nd paragraph of section 4.2 of RFC 5031 103 [RFC5031], in order to allow the registration of service URNs with 104 the 'sos' service type for emergency services that, at the time of 105 registration, are offered in one country only. 107 2. Conventions 109 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 110 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 111 document are to be interpreted as described in BCP 14, RFC 2119 112 [RFC2119]. 114 3. Update to RFC 5031 116 3.1. General 118 Section 3.2 of this document replaces the text of the 2nd paragraph 119 of section 4.2 (Sub-Services for the 'sos' Service) of RFC 5031 120 [RFC5031]. 122 3.2. New text replacing the text of the 2nd paragraph of section 4.2 of 123 RFC 5031 125 The 'sos' service type describes emergency services requiring an 126 immediate response, typically offered by various branches of the 127 government or other public institutions. Additional sub-services can 128 be added after expert review. The expert is designated by the ECRIT 129 working group, its successor, or, in their absence, the IESG. The 130 designated expert should only approve services that have emergency 131 nature, that are offered in at least one country, that do not match 132 description of any existing service URN with the 'sos' service type, 133 and where the service description and the URN are defined as broadly 134 as possible to encourage reuse. The 'sos' service is not meant to 135 invoke general government, public information, counseling, or social 136 services. 138 4. IANA Considerations 140 This document updates the advice to the expert for the registry of 141 sub-services of the "sos" service. IANA is requested to update the 142 reference for that registry from RFC 5031 [RFC5031] to this document. 144 http://www.iana.org/assignments/urn-serviceid-labels 146 5. Change Log 148 [RFC EDITOR NOTE: Please remove this section when publishing] 150 Changes from draft-ietf-ecrit-country-emg-urn-02 152 o Changes based on IESG review. 154 o - Old section 3, 4 and 5.2 removed. 156 o - Only modified paragraph kept in section 5.3. 158 o - Date added to Wikipedia reference. 160 Changes from draft-ietf-ecrit-country-emg-urn-01 162 o Security Considerations section updated. 164 Changes from draft-ietf-ecrit-country-emg-urn-00 166 o IANA Considerations section updated. Open issue removed. 168 Changes from draft-holmberg-ecrit-country-emg-urn-02 170 o Minor editorial fixes. 172 Changes from draft-holmberg-ecrit-country-emg-urn-01 174 o Technical fix: Instead of creating a new sub-tree, the 'sos' 175 registration rules in RFC are updated, to allow registration of 176 URNs that, at the time of registration, are specific to a single 177 country. 179 Changes from draft-holmberg-ecrit-country-emg-urn-00 181 o Editorial fix: cannot be not fulfilled -> cannot be fulfilled 183 6. Security Considerations 185 This document does not update the Security Considerations of RFC 186 5031. 188 7. Normative References 190 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 191 Requirement Levels", BCP 14, RFC 2119, March 1997. 193 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 194 Emergency and Other Well-Known Services", RFC 5031, 195 January 2008. 197 Authors' Addresses 199 Christer Holmberg 200 Ericsson 201 Hirsalantie 11 202 Jorvas 02420 203 Finland 205 Email: christer.holmberg@ericsson.com 207 Ivo Sedlacek 208 Ericsson 209 Sokolovska 79 210 Praha 18600 211 Czech Republic 213 Email: ivo.sedlacek@ericsson.com