idnits 2.17.1 draft-holmberg-dispatch-mcptt-rp-namespace-01.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 (June 9, 2016) is 2849 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: December 11, 2016 June 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-01 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 December 11, 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. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. New SIP Resource-Priority Namespaces Created . . . . . . . . 3 56 4.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 3 57 4.2. The MCPTT namespaces . . . . . . . . . . . . . . . . . . 3 58 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 60 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 61 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 9. Normative References . . . . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 The third generation partnership project (3GPP) has defined a Mission 68 Critical Push To Talk (MCPTT) over LTE service [TS.3GPP.22.179]. The 69 MCPTT service supports an enhanced PTT service, suitable for mission 70 critical scenarios, based upon 3GPP Evolved Packet System (EPS) 71 services. The requirements for the MCPTT service defined within 3GPP 72 can also form the basis for a non-mission critical Push To Talk (PTT) 73 service. 75 The MCPTT service is intended to support communication between 76 several users (a group call), where each user has the ability to gain 77 access to the permission to talk in an arbitrated manner. However, 78 the MCPTT service also supports private calls between pairs of users. 80 MCPTT is primarily targeting to provide a professional Push To Talk 81 service to e.g., public safety, transport companies, utilities or 82 industrial and nuclear plants. In addition to this a commercial PTT 83 service for non-professional use (e.g., groups of people on holiday) 84 may be delivered through an MCPTT system. Based on their operational 85 model, the performance and MCPTT features in use vary per user 86 organization, where functionality which is more mission critical 87 specific (e.g., Ambient Listening and Imminent Peril Call) might not 88 be available to commercial customers. 90 The MCPTT service provides its users with different priorities for 91 the access to network resources in order to provide means to 92 prioritize between calls when resources are scarce. These priorities 93 take into account among other things the priority and role of the 94 caller, the priority and type of the group, and the situation in 95 which the call is made. According to [TS.3GPP.22.179] at least 8 and 96 up to 30 priority levels are required. 98 High priority calls when there is danger of life for either the 99 public safety worker or any other human need to be set up immediately 100 and thus require preemption. Other calls may be less sensitive in 101 call set-up time but have a high priority once established. For 102 these calls a queueing mechanism is more appropriate. 104 This document creates additional Session Initiation Protocol (SIP) 105 Resource-Priority namespaces to meet the requirements of the 3GPP 106 defined Mission Critical Push To Talk, and places these namespaces in 107 the IANA registry. 109 2. Conventions 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in [RFC2119]. 115 3. Applicability 117 This document defines namespaces applicable for MCPTT services 118 defined by 3GPP that use the network services of a 3GPP defined LTE 119 network. 121 4. New SIP Resource-Priority Namespaces Created 123 4.1. Introduction 125 This document introduces the MCPTT namespaces mcpttp and mcptt2, the 126 name coming from the 3GPP defined Mission Critical Push To Talk 127 service. 129 4.2. The MCPTT namespaces 131 The mcpttp namespace uses the priority levels listed below from 132 lowest to highest priority. 134 mcpttp.0 (lowest priority) 135 mcpttp.1 136 mcpttp.2 137 mcpttp.3 138 mcpttp.4 139 mcpttp.5 140 mcpttp.6 141 mcpttp.7 142 mcpttp.8 143 mcpttp.9 144 mcpttp.10 145 mcpttp.11 146 mcpttp.12 147 mcpttp.13 148 mcpttp.14 149 mcpttp.15 (highest priority) 151 Intended algorithm for mcpttp is preemption. 153 New Warning code: No. 155 New SIP response code: No. 157 The mcpttq namespace uses the priority levels listed below from 158 lowest to highest priority. 160 mcpttq.0 (lowest priority) 161 mcpttq.1 162 mcpttq.2 163 mcpttq.3 164 mcpttq.4 165 mcpttq.5 166 mcpttq.6 167 mcpttq.7 168 mcpttq.8 169 mcpttq.9 170 mcpttq.10 171 mcpttq.11 172 mcpttq.12 173 mcpttq.13 174 mcpttq.14 175 mcpttq.15 (highest priority) 177 Intended algorithm for mcpttq is queuing. 179 New Warning code: No. 181 New SIP response code: No. 183 5. Security Considerations 185 This document has the same Security Considerations as [RFC4412]. 187 6. IANA Considerations 189 Abiding by the rules established within [RFC4412] and [RFC7134], this 190 is an Informative RFC registering two new namespaces, their 191 associated priority-values, and intended algorithms. 193 7. Acknowledgments 195 The authors would like to thank Bob Fredericks, Baruh Hason, Mary 196 Barnes and Keith Drage for comments and discussions. 198 8. Change Log 200 [RFC EDITOR NOTE: Please remove this section when publishing] 202 Changes from draft-holmberg-dispatch-mcptt-rp-namespace-00. 204 o - The two namespaces have been spelt out explicitly. 205 o - The numbering of priority levels is changed from 1-16 to 0-15. 206 o - Address of one author has changed. 208 9. Normative References 210 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 211 Requirement Levels", BCP 14, RFC 2119, 212 DOI 10.17487/RFC2119, March 1997, 213 . 215 [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource 216 Priority for the Session Initiation Protocol (SIP)", 217 RFC 4412, DOI 10.17487/RFC4412, February 2006, 218 . 220 [RFC7134] Rosen, B., "The Management Policy of the Resource Priority 221 Header (RPH) Registry Changed to "IETF Review"", RFC 7134, 222 DOI 10.17487/RFC7134, March 2014, 223 . 225 [TS.3GPP.22.179] 226 3GPP, "3rd Generation Partnership Project; Technical 227 Specification Group Services and System Aspects; Mission 228 Critical Push To Talk (MCPTT) over LTE; Stage 1", 3GPP 229 TS 22.179 13.2.0, June 2015. 231 Authors' Addresses 233 Christer Holmberg 234 Ericsson 235 Hirsalantie 11 236 Jorvas 02420 237 Finland 239 Email: christer.holmberg@ericsson.com 240 Joergen Axell 241 Ericsson 242 Groenlandsgatan 31 243 Stockholm 16480 244 Sweden 246 Email: jorgen.axell@ericsson.com