idnits 2.17.1 draft-holmberg-dispatch-mcptt-rp-namespace-05.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 date (January 20, 2017) is 2624 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 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: July 24, 2017 January 20, 2017 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-05 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 July 24, 2017. 35 Copyright Notice 37 Copyright (c) 2017 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. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . 5 59 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 60 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 8. Normative References . . . . . . . . . . . . . . . . . . . . 5 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 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 can gain permission to 76 talk in an arbitrated manner. However, the MCPTT service also 77 supports private calls between pairs of users. 79 MCPTT is primarily targeted 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., Imminent Peril Call) might not be available to 87 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. 96 The SIP level call control procedures using these namespaces are 97 specified in [TS.3GPP.24.379]. The namespaces defined here will 98 support a wide range of queuing options. The namespaces correspond 99 to what can be supported over the 3GPP Rx interface, defined in 100 [TS.3GPP.29.214]. The usage of the namespaces can be tailored to the 101 needs of the operator. The mechanism to do this is to configure 102 which values a specific user is allowed to use. This configuration 103 is specified in [TS.3GPP.24.384]. 105 High priority calls when there is danger of life, for either the 106 public safety worker or any other human, need to be set up 107 immediately and thus require preemption. Other calls may be less 108 sensitive in call set-up time but have a high priority once 109 established. For these calls a queueing mechanism is more 110 appropriate. The MCPTT data transfer service currently under 111 development can benefit from a queueing mechanism. Another example 112 is video only calls that are not critical in call set-up time, but 113 where keeping the call is important. 115 This document creates additional Session Initiation Protocol (SIP) 116 Resource-Priority namespaces to meet the requirements of the 3GPP 117 defined Mission Critical Push To Talk, and places these namespaces in 118 the IANA registry. 120 2. Applicability 122 This document defines namespaces applicable for MCPTT services 123 defined by 3GPP that use the network services of a 3GPP defined LTE 124 network. The use of this namespace outside such networks is 125 undefined. 127 3. New SIP Resource-Priority Namespaces Created 129 3.1. Introduction 131 This document introduces the MCPTT namespaces mcpttp and mcpttq, the 132 name coming from the 3GPP defined Mission Critical Push To Talk 133 service. 135 3.2. The MCPTT namespaces 137 The mcpttp namespace uses the priority levels listed below from 138 lowest to highest priority. 140 mcpttp.0 (lowest priority) 141 mcpttp.1 142 mcpttp.2 143 mcpttp.3 144 mcpttp.4 145 mcpttp.5 146 mcpttp.6 147 mcpttp.7 148 mcpttp.8 149 mcpttp.9 150 mcpttp.10 151 mcpttp.11 152 mcpttp.12 153 mcpttp.13 154 mcpttp.14 155 mcpttp.15 (highest priority) 157 Intended algorithm for mcpttp is preemption. 159 New Warning code: No. 161 New SIP response code: No. 163 The mcpttq namespace uses the priority levels listed below from 164 lowest to highest priority. 166 mcpttq.0 (lowest priority) 167 mcpttq.1 168 mcpttq.2 169 mcpttq.3 170 mcpttq.4 171 mcpttq.5 172 mcpttq.6 173 mcpttq.7 174 mcpttq.8 175 mcpttq.9 176 mcpttq.10 177 mcpttq.11 178 mcpttq.12 179 mcpttq.13 180 mcpttq.14 181 mcpttq.15 (highest priority) 183 Intended algorithm for mcpttq is queuing. 185 New Warning code: No. 187 New SIP response code: No. 189 4. Security Considerations 191 This document does not have any impact on the security of the SIP 192 MCPTT protocol. Its purpose is purely administrative in nature. 194 5. IANA Considerations 196 Abiding by the rules established within [RFC4412] and [RFC7134] , 197 this is an Informative RFC creating two new namespaces, their 198 associated priority-values, and intended algorithms. 200 6. Acknowledgments 202 The authors would like to thank Bob Fredericks, Baruh Hason, Mary 203 Barnes and Keith Drage for comments and discussions. 205 7. Change Log 207 [RFC EDITOR NOTE: Please remove this section when publishing] 209 Changes from draft-holmberg-dispatch-mcptt-rp-namespace-04. 211 o - Editorial changes based on gen-art review. Renderin of authors 212 name and address fixed. 214 Changes from draft-holmberg-dispatch-mcptt-rp-namespace-03. 216 o - Editorial changes based on sec- and opt- directorate reviews. 218 Changes from draft-holmberg-dispatch-mcptt-rp-namespace-01. 220 o - Removal of Conventions section. 221 o - Editorial changes. 223 Changes from draft-holmberg-dispatch-mcptt-rp-namespace-00. 225 o - The two namespaces have been spelt out explicitly. 226 o - The numbering of priority levels is changed from 1-16 to 0-15. 227 o - Address of one author has changed. 229 8. Normative References 231 [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource 232 Priority for the Session Initiation Protocol (SIP)", 233 RFC 4412, DOI 10.17487/RFC4412, February 2006, 234 . 236 [RFC7134] Rosen, B., "The Management Policy of the Resource Priority 237 Header (RPH) Registry Changed to "IETF Review"", RFC 7134, 238 DOI 10.17487/RFC7134, March 2014, 239 . 241 [TS.3GPP.22.179] 242 3GPP, "3rd Generation Partnership Project; Technical 243 Specification Group Services and System Aspects; Mission 244 Critical Push To Talk (MCPTT) over LTE; Stage 1", 3GPP 245 TS 22.179 13.3.0, December 2015. 247 [TS.3GPP.29.214] 248 3GPP, "3rd Generation Partnership Project; Technical 249 Specification Group Core Network and Terminals; Policy and 250 Charging Control over Rx reference point;", 3GPP TS 29.314 251 13.7.0, September 2016. 253 [TS.3GPP.24.379] 254 3GPP, "3rd Generation Partnership Project; Technical 255 Specification Group Core Network and Terminals; Mission 256 Critical Push To Talk (MCPTT) call control; Protocol 257 specification;", 3GPP TS 24.379 13.2.0, September 2016. 259 [TS.3GPP.24.384] 260 3GPP, "3rd Generation Partnership Project; Technical 261 Specification Group Core Network and Terminals; Mission 262 Critical Push To Talk (MCPTT) configuration management; 263 Protocol specification", 3GPP TS 24.384 13.2.0, September 264 2016. 266 Authors' Addresses 268 Christer Holmberg 269 Ericsson 270 Hirsalantie 11 271 Jorvas 02420 272 Finland 274 Email: christer.holmberg@ericsson.com 276 Joergen Axell 277 Ericsson 278 Groenlandsgatan 31 279 Stockholm 16480 280 Sweden 282 Email: jorgen.axell@ericsson.com