idnits 2.17.1 draft-holmberg-dispatch-mcptt-rp-namespace-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 : ---------------------------------------------------------------------------- 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 (August 12, 2016) is 2807 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: February 13, 2017 August 12, 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-02 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 February 13, 2017. 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. 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 . . . . . . . . . . . . . . . . . . . . . 4 59 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 60 7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 8. Normative References . . . . . . . . . . . . . . . . . . . . 5 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., 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. 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. Applicability 110 This document defines namespaces applicable for MCPTT services 111 defined by 3GPP that use the network services of a 3GPP defined LTE 112 network. 114 3. New SIP Resource-Priority Namespaces Created 116 3.1. Introduction 118 This document introduces the MCPTT namespaces mcpttp and mcpttq, the 119 name coming from the 3GPP defined Mission Critical Push To Talk 120 service. 122 3.2. The MCPTT namespaces 124 The mcpttp namespace uses the priority levels listed below from 125 lowest to highest priority. 127 mcpttp.0 (lowest priority) 128 mcpttp.1 129 mcpttp.2 130 mcpttp.3 131 mcpttp.4 132 mcpttp.5 133 mcpttp.6 134 mcpttp.7 135 mcpttp.8 136 mcpttp.9 137 mcpttp.10 138 mcpttp.11 139 mcpttp.12 140 mcpttp.13 141 mcpttp.14 142 mcpttp.15 (highest priority) 144 Intended algorithm for mcpttp is preemption. 146 New Warning code: No. 148 New SIP response code: No. 150 The mcpttq namespace uses the priority levels listed below from 151 lowest to highest priority. 153 mcpttq.0 (lowest priority) 154 mcpttq.1 155 mcpttq.2 156 mcpttq.3 157 mcpttq.4 158 mcpttq.5 159 mcpttq.6 160 mcpttq.7 161 mcpttq.8 162 mcpttq.9 163 mcpttq.10 164 mcpttq.11 165 mcpttq.12 166 mcpttq.13 167 mcpttq.14 168 mcpttq.15 (highest priority) 170 Intended algorithm for mcpttq is queuing. 172 New Warning code: No. 174 New SIP response code: No. 176 4. Security Considerations 178 This document has the same Security Considerations as [RFC4412]. 180 5. IANA Considerations 182 Abiding by the rules established within [RFC4412] and [RFC7134], this 183 is an Informative RFC registering two new namespaces, their 184 associated priority-values, and intended algorithms. 186 6. Acknowledgments 188 The authors would like to thank Bob Fredericks, Baruh Hason, Mary 189 Barnes and Keith Drage for comments and discussions. 191 7. Change Log 193 [RFC EDITOR NOTE: Please remove this section when publishing] 195 Changes from draft-holmberg-dispatch-mcptt-rp-namespace-01. 197 o - Removal of Conventions section. 198 o - Editorial changes. 200 Changes from draft-holmberg-dispatch-mcptt-rp-namespace-00. 202 o - The two namespaces have been spelt out explicitly. 203 o - The numbering of priority levels is changed from 1-16 to 0-15. 204 o - Address of one author has changed. 206 8. Normative References 208 [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource 209 Priority for the Session Initiation Protocol (SIP)", 210 RFC 4412, DOI 10.17487/RFC4412, February 2006, 211 . 213 [RFC7134] Rosen, B., "The Management Policy of the Resource Priority 214 Header (RPH) Registry Changed to "IETF Review"", RFC 7134, 215 DOI 10.17487/RFC7134, March 2014, 216 . 218 [TS.3GPP.22.179] 219 3GPP, "3rd Generation Partnership Project; Technical 220 Specification Group Services and System Aspects; Mission 221 Critical Push To Talk (MCPTT) over LTE; Stage 1", 3GPP 222 TS 22.179 13.2.0, June 2015. 224 Authors' Addresses 226 Christer Holmberg 227 Ericsson 228 Hirsalantie 11 229 Jorvas 02420 230 Finland 232 Email: christer.holmberg@ericsson.com 233 Ji?1/2rgen Axell 234 Ericsson 235 Gri?1/2nlandsgatan 31 236 Stockholm 16480 237 Sweden 239 Email: jorgen.axell@ericsson.com