ECRIT Working GroupInternet Engineering Task Force (IETF) C. HolmbergInternet-DraftRequest for Comments: 7163 I. Sedlacek Updates: 5031(if approved)EricssonIntended status:Category: Standards TrackJanuary 8, 2014 Expires: July 12,March 2014 ISSN: 2070-1721 URN For Country Specific Emergency Servicesdraft-ietf-ecrit-country-emg-urn-03.txtAbstract Section 4.2 of RFC 5031 allows the registration of service URNs with the 'sos' service type only for emergency services "that are offered widely and in different countries". This document updates those instructionsin RFC 5031to allow such registrations when, at the time of registration, those services are offered in only onecountry only.country. Status of This Memo ThisInternet-Draftissubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsan Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe IETF community. It has received public review and has been approved fora maximumpublication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status ofsix monthsthis document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on July 12, 2014.http://www.rfc-editor.org/info/rfc7163. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Update to RFC 5031 . . . . . . . . . . . . . . . . . . . . . 3 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.2. Newtext replacingText Replacing thetextText of the 2ndparagraphParagraph ofsectionSection 4.2 of RFC 5031 . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 5.Change LogSecurity Considerations . . . . . . . . . . . . . . . . . . . 3 6. References . . . . . .4 6. Security Considerations. . . . . . . . . . . . . . . . . . . 47.6.1. Normative References . . . . . . . . . . . . . . . . . .. . 5 Authors' Addresses . . . . .4 6.2. Informative Reference . . . . . . . . . . . . . . . . . .54 1. IntroductionTable 1 shows the policyThe advice to experts forregistration ofregistering sub-services of the service URN with the 'sos' servicetype, as definedtype is provided insection 4.2.Section 4.2 of RFC 5031[RFC5031]. +-------------------------------------------------------------------+ |[RFC5031] as follows: The 'sos' service type describes emergency services requiring an| |immediate response, typically offered by various branches of the| |government or other public institutions. Additional sub-services| |can be added after expert review and must be of general public| |interest and have a similar emergency nature. The expert is| |designated by the ECRIT working group, its successor, or, in| |their absence, the IESG. The expert review should only approve| |emergency services that are offered widely and in different| |countries, with approximately the same caller expectation in| |terms of services rendered. The 'sos' service is not meant to| |invoke general government, public information, counseling, or| |social services.| +-------------------------------------------------------------------+ Table 1: Excerpt from RFC 5031 section 4.2.Some existing emergency services are, at least initially, offered in only onecountry only.country. Examples are the "Reporting spies" emergency service offered in South Korea and the "GAULA (anti-kidnapping)" emergency service offered in Colombia according tohttp:// en.wikipedia.org/wiki/Emergency_telephone_number (as per January 8th 2014).[WIKIPEDIA]. Future emergency service might also initially be introduced in only onecountry only.country. Thepolicy for registrationadvice to experts of sub-services of the service URN with the 'sos' servicetype, as definedtype provided in RFC 5031[RFC5031],[RFC5031] prevents the registration of a sub-service of the service URN with the 'sos' service type for a service that, at the time of registration, is offered in one country only. This document updates the 2nd paragraph ofsectionSection 4.2 of RFC 5031 [RFC5031], in order to allow the registration of service URNs with the 'sos' service type for emergency services that, at the time of registration, are offered in one country only. 2. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119]. 3. Update to RFC 5031 3.1. General Section 3.2 of this document replaces the text of the 2nd paragraph ofsectionSection 4.2 (Sub-Services for the 'sos' Service) of RFC 5031 [RFC5031]. 3.2. Newtext replacingText Replacing thetextText of the 2ndparagraphParagraph ofsectionSection 4.2 of RFC 5031 The 'sos' service type describes emergency services requiring an immediate response, typically offered by various branches of the government or other public institutions. Additional sub-services can be added after expert review. The expert is designated by the ECRIT working group, its successor, or, in their absence, the IESG. The designated expert should only approve services thathaveare to be used for emergencynature,purposes, that are offered in at least one country, that do not match the description of any existing service URN with the 'sos' service type, and where the service description and the URN are defined as broadly as possible to encourage reuse. The 'sos' service is not meant to invoke general government, public information, counseling, or social services. 4. IANA Considerations This document updates the advice to the expertfor the registry of sub-servicesof the"sos" service."'sos' Sub- Services" registry. IANAis requested to updatehas updated the reference for that registryfrom RFC 5031 [RFC5031]tothis document. http://www.iana.org/assignments/urn-serviceid-labels 5. Change Log [RFC EDITOR NOTE: Please remove this section when publishing] Changes from draft-ietf-ecrit-country-emg-urn-02 o Changes based on IESG review. o - Old section 3, 4 and 5.2 removed. o - Only modified paragraph kept in section 5.3. o - Date addedpoint toWikipedia reference. Changes from draft-ietf-ecrit-country-emg-urn-01 o Security Considerations section updated. Changes from draft-ietf-ecrit-country-emg-urn-00 o IANA Considerations section updated. Open issue removed. Changes from draft-holmberg-ecrit-country-emg-urn-02 o Minor editorial fixes. Changes from draft-holmberg-ecrit-country-emg-urn-01 o Technical fix: Insteadthis document (instead ofcreating a new sub-tree, the 'sos' registration rules inRFCare updated, to allow registration of URNs that, at the time of registration, are specific to a single country. Changes from draft-holmberg-ecrit-country-emg-urn-00 o Editorial fix: cannot be not fulfilled -> cannot be fulfilled 6.5031 [RFC5031]). http://www.iana.org/assignments/urn-serviceid-labels 5. Security Considerations This document does not update the Security Considerations of RFC 5031.7.6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services", RFC 5031, January 2008. 6.2. Informative Reference [WIKIPEDIA] Wikipedia, "Emergency telephone number", March 2014, <http://en.wikipedia.org/w/index.php?title=Emergency_telep hone_number&oldid=599435311>. Authors' Addresses Christer Holmberg Ericsson Hirsalantie 11 Jorvas 02420 FinlandEmail:EMail: christer.holmberg@ericsson.com Ivo Sedlacek Ericsson Sokolovska 79 Praha 18600 Czech RepublicEmail:EMail: ivo.sedlacek@ericsson.com