| Network Working Group | C. Holmberg |
| Internet-Draft | J. Axell |
| Intended status: Informational | Ericsson |
| Expires: July 24, 2017 | January 20, 2017 |
IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk service
draft-holmberg-dispatch-mcptt-rp-namespace-05
This document creates an additional Session Initiation Protocol (SIP) Resource-Priority namespace to meet the requirements of the 3GPP defined Mission Critical Push To Talk, and places this namespace in the IANA registry.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any 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 24, 2017.
Copyright (c) 2017 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.
The Third Generation Partnership Project (3GPP) has defined a Mission Critical Push To Talk (MCPTT) over LTE service [TS.3GPP.22.179] . The MCPTT service supports an enhanced PTT service, suitable for mission critical scenarios, based upon 3GPP Evolved Packet System (EPS) services. The requirements for the MCPTT service defined within 3GPP can also form the basis for a non-mission critical Push To Talk (PTT) service.
The MCPTT service is intended to support communication between several users (a group call), where each user can gain permission to talk in an arbitrated manner. However, the MCPTT service also supports private calls between pairs of users.
MCPTT is primarily targeted to provide a professional Push To Talk service to e.g., public safety, transport companies, utilities or industrial and nuclear plants. In addition to this, a commercial PTT service for non-professional use (e.g., groups of people on holiday) may be delivered through an MCPTT system. Based on their operational model, the performance and MCPTT features in use vary per user organization, where functionality which is more mission critical specific (e.g., Imminent Peril Call) might not be available to commercial customers.
The MCPTT service provides its users with different priorities for the access to network resources in order to provide means to prioritize between calls when resources are scarce. These priorities take into account among other things the priority and role of the caller, the priority and type of the group, and the situation in which the call is made.
The SIP level call control procedures using these namespaces are specified in [TS.3GPP.24.379]. The namespaces defined here will support a wide range of queuing options. The namespaces correspond to what can be supported over the 3GPP Rx interface, defined in [TS.3GPP.29.214]. The usage of the namespaces can be tailored to the needs of the operator. The mechanism to do this is to configure which values a specific user is allowed to use. This configuration is specified in [TS.3GPP.24.384].
High priority calls when there is danger of life, for either the public safety worker or any other human, need to be set up immediately and thus require preemption. Other calls may be less sensitive in call set-up time but have a high priority once established. For these calls a queueing mechanism is more appropriate. The MCPTT data transfer service currently under development can benefit from a queueing mechanism. Another example is video only calls that are not critical in call set-up time, but where keeping the call is important.
This document creates additional Session Initiation Protocol (SIP) Resource-Priority namespaces to meet the requirements of the 3GPP defined Mission Critical Push To Talk, and places these namespaces in the IANA registry.
This document defines namespaces applicable for MCPTT services defined by 3GPP that use the network services of a 3GPP defined LTE network. The use of this namespace outside such networks is undefined.
This document introduces the MCPTT namespaces mcpttp and mcpttq, the name coming from the 3GPP defined Mission Critical Push To Talk service.
The mcpttp namespace uses the priority levels listed below from lowest to highest priority.
Intended algorithm for mcpttp is preemption.
New Warning code: No.
New SIP response code: No.
The mcpttq namespace uses the priority levels listed below from lowest to highest priority.
Intended algorithm for mcpttq is queuing.
New Warning code: No.
New SIP response code: No.
This document does not have any impact on the security of the SIP MCPTT protocol. Its purpose is purely administrative in nature.
Abiding by the rules established within [RFC4412] and [RFC7134] , this is an Informative RFC creating two new namespaces, their associated priority-values, and intended algorithms.
The authors would like to thank Bob Fredericks, Baruh Hason, Mary Barnes and Keith Drage for comments and discussions.
[RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-holmberg-dispatch-mcptt-rp-namespace-04.
Changes from draft-holmberg-dispatch-mcptt-rp-namespace-03.
Changes from draft-holmberg-dispatch-mcptt-rp-namespace-01.
Changes from draft-holmberg-dispatch-mcptt-rp-namespace-00.