idnits 2.17.1 draft-holmberg-dispatch-mcptt-rp-namespace-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 : ---------------------------------------------------------------------------- No issues found here. 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. -- The document date (February 9, 2016) is 2970 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Holmberg 3 Internet-Draft J. Axell 4 Intended status: Informational Ericsson 5 Expires: August 12, 2016 February 9, 2016 7 IANA Registration of New Session Initiation Protocol (SIP) Resource- 8 Priority Namespace for Mission Critical Push To Talk service 9 draft-holmberg-dispatch-mcptt-rp-namespace-00 11 Abstract 13 This document creates an additional Session Initiation Protocol (SIP) 14 Resource-Priority namespace to meet the requirements of the 3GPP 15 defined Mission Critical Push To Talk, and places this namespace in 16 the IANA registry. 18 Status of This Memo 20 This Internet-Draft is submitted 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 August 12, 2016. 35 Copyright Notice 37 Copyright (c) 2016 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. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. New SIP Resource-Priority Namespaces Created . . . . . . . . 3 55 3.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 3 56 3.2. The MCPTT namespaces . . . . . . . . . . . . . . . . . . 3 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 60 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 8. Normative References . . . . . . . . . . . . . . . . . . . . 4 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 The third generation partnership project (3GPP) has defined a Mission 67 Critical Push To Talk (MCPTT) over LTE service [TS.3GPP.22.179]. The 68 MCPTT service supports an enhanced PTT service, suitable for mission 69 critical scenarios, based upon 3GPP Evolved Packet System (EPS) 70 services. The requirements for the MCPTT service defined within 3GPP 71 can also form the basis for a non-mission critical Push To Talk (PTT) 72 service. 74 The MCPTT service is intended to support communication between 75 several users (a group call), where each user has the ability to gain 76 access to the permission to talk in an arbitrated manner. However, 77 the MCPTT service also supports private calls between pairs of users. 79 MCPTT is primarily targeting to provide a professional Push To Talk 80 service to e.g., public safety, transport companies, utilities or 81 industrial and nuclear plants. In addition to this a commercial PTT 82 service for non-professional use (e.g., groups of people on holiday) 83 may be delivered through an MCPTT system. Based on their operational 84 model, the performance and MCPTT features in use vary per user 85 organization, where functionality which is more mission critical 86 specific (e.g., Ambient Listening and Imminent Peril Call) might not 87 be available to commercial customers. 89 The MCPTT service provides its users with different priorities for 90 the access to network resources in order to provide means to 91 prioritize between calls when resources are scarce. These priorities 92 take into account among other things the priority and role of the 93 caller, the priority and type of the group, and the situation in 94 which the call is made. According to [TS.3GPP.22.179] at least 8 and 95 up to 30 priority levels are required. 97 High priority calls when there is danger of life for either the 98 public safety worker or any other human need to be set up immediately 99 and thus require preemption. Other calls may be less sensitive in 100 call set-up time but have a high priority once established. For 101 these calls a queueing mechanism is more appropriate. 103 This document creates additional Session Initiation Protocol (SIP) 104 Resource-Priority namespaces to meet the requirements of the 3GPP 105 defined Mission Critical Push To Talk, and places these namespaces in 106 the IANA registry. 108 2. Conventions 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 112 document are to be interpreted as described in [RFC2119]. 114 3. New SIP Resource-Priority Namespaces Created 116 3.1. Introduction 118 This document introduces the MCPTT namespaces mcptt1 and mcptt2, the 119 name coming from the 3GPP defined Mission Critical Push To Talk 120 service. 122 3.2. The MCPTT namespaces 124 The MCPTT namespaces use the priority levels listed below from lowest 125 to highest priority. 127 mcpttN.1 (lowest priority) 128 mcpttN.2 129 mcpttN.3 130 mcpttN.4 131 mcpttN.5 132 mcpttN.6 133 mcpttN.7 134 mcpttN.8 135 mcpttN.9 136 mcpttN.10 137 mcpttN.11 138 mcpttN.12 139 mcpttN.13 140 mcpttN.14 141 mcpttN.15 142 mcpttN.16 (highest priority) 144 where N is 1 or 2. 146 Intended algorithm for mcptt1 is preemption, and for mcptt2 is 147 queueing. 149 New Warning code: No. 151 New SIP response code: No. 153 4. Security Considerations 155 This document has the same Security Considerations as [RFC4412]. 157 5. IANA Considerations 159 Abiding by the rules established within [RFC4412] and [RFC7134], this 160 is an Informative RFC registering two new namespaces, their 161 associated priority-values, and intended algorithms. 163 6. Acknowledgments 165 TBD 167 7. Change Log 169 [RFC EDITOR NOTE: Please remove this section when publishing] 171 Changes from draft-holmberg-dispatch-mcptt-namespace-00 173 o - Some change 175 8. Normative References 177 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 178 Requirement Levels", BCP 14, RFC 2119, 179 DOI 10.17487/RFC2119, March 1997, 180 . 182 [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource 183 Priority for the Session Initiation Protocol (SIP)", 184 RFC 4412, DOI 10.17487/RFC4412, February 2006, 185 . 187 [RFC7134] Rosen, B., "The Management Policy of the Resource Priority 188 Header (RPH) Registry Changed to "IETF Review"", RFC 7134, 189 DOI 10.17487/RFC7134, March 2014, 190 . 192 [TS.3GPP.22.179] 193 3GPP, "3rd Generation Partnership Project; Technical 194 Specification Group Services and System Aspects; Mission 195 Critical Push To Talk (MCPTT) over LTE; Stage 1", 3GPP 196 TS 22.179 13.2.0, June 2015. 198 Authors' Addresses 200 Christer Holmberg 201 Ericsson 202 Hirsalantie 11 203 Jorvas 02420 204 Finland 206 Email: christer.holmberg@ericsson.com 208 Joergen Axell 209 Ericsson 210 Kistavaegen 25 211 Stockholm 16480 212 Sweden 214 Email: jorgen.axell@ericsson.com