IANA Registration of New Session Initiation Protocol (SIP) Resource- Priority Namespace for Mission Critical Push To Talk service
draft-holmberg-dispatch-mcptt-rp-namespace-01

Network Working Group                                        C. Holmberg
Internet-Draft                                                  J. Axell
Intended status: Informational                                  Ericsson
Expires: December 11, 2016                                  June 9, 2016

  IANA Registration of New Session Initiation Protocol (SIP) Resource-
      Priority Namespace for Mission Critical Push To Talk service
             draft-holmberg-dispatch-mcptt-rp-namespace-01

Abstract

   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.

Status of This Memo

   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 December 11, 2016.

Copyright Notice

   Copyright (c) 2016 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.

Holmberg & Axell        Expires December 11, 2016               [Page 1]
Internet-Draft             MCPTT R-P namespace                 June 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  New SIP Resource-Priority Namespaces Created  . . . . . . . .   3
     4.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  The MCPTT namespaces  . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   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 has the ability to gain
   access to the permission to talk in an arbitrated manner.  However,
   the MCPTT service also supports private calls between pairs of users.

   MCPTT is primarily targeting 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., Ambient Listening and 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.  According to [TS.3GPP.22.179] at least 8 and
   up to 30 priority levels are required.

Holmberg & Axell        Expires December 11, 2016               [Page 2]
Internet-Draft             MCPTT R-P namespace                 June 2016

   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.

   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.

2.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Applicability

   This document defines namespaces applicable for MCPTT services
   defined by 3GPP that use the network services of a 3GPP defined LTE
   network.

4.  New SIP Resource-Priority Namespaces Created

4.1.  Introduction

   This document introduces the MCPTT namespaces mcpttp and mcptt2, the
   name coming from the 3GPP defined Mission Critical Push To Talk
   service.

4.2.  The MCPTT namespaces

   The mcpttp namespace uses the priority levels listed below from
   lowest to highest priority.

      mcpttp.0 (lowest priority)
      mcpttp.1
      mcpttp.2
      mcpttp.3
      mcpttp.4
      mcpttp.5
      mcpttp.6
      mcpttp.7
      mcpttp.8
      mcpttp.9
      mcpttp.10
      mcpttp.11

Holmberg & Axell        Expires December 11, 2016               [Page 3]
Internet-Draft             MCPTT R-P namespace                 June 2016

      mcpttp.12
      mcpttp.13
      mcpttp.14
      mcpttp.15 (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.

      mcpttq.0 (lowest priority)
      mcpttq.1
      mcpttq.2
      mcpttq.3
      mcpttq.4
      mcpttq.5
      mcpttq.6
      mcpttq.7
      mcpttq.8
      mcpttq.9
      mcpttq.10
      mcpttq.11
      mcpttq.12
      mcpttq.13
      mcpttq.14
      mcpttq.15 (highest priority)

   Intended algorithm for mcpttq is queuing.

   New Warning code: No.

   New SIP response code: No.

5.  Security Considerations

   This document has the same Security Considerations as [RFC4412].

6.  IANA Considerations

   Abiding by the rules established within [RFC4412] and [RFC7134], this
   is an Informative RFC registering two new namespaces, their
   associated priority-values, and intended algorithms.

Holmberg & Axell        Expires December 11, 2016               [Page 4]
Internet-Draft             MCPTT R-P namespace                 June 2016

7.  Acknowledgments

   The authors would like to thank Bob Fredericks, Baruh Hason, Mary
   Barnes and Keith Drage for comments and discussions.

8.  Change Log

   [RFC EDITOR NOTE: Please remove this section when publishing]

   Changes from draft-holmberg-dispatch-mcptt-rp-namespace-00.

   o  - The two namespaces have been spelt out explicitly.
   o  - The numbering of priority levels is changed from 1-16 to 0-15.
   o  - Address of one author has changed.

9.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC4412]  Schulzrinne, H. and J. Polk, "Communications Resource
              Priority for the Session Initiation Protocol (SIP)",
              RFC 4412, DOI 10.17487/RFC4412, February 2006,
              <http://www.rfc-editor.org/info/rfc4412>.

   [RFC7134]  Rosen, B., "The Management Policy of the Resource Priority
              Header (RPH) Registry Changed to "IETF Review"", RFC 7134,
              DOI 10.17487/RFC7134, March 2014,
              <http://www.rfc-editor.org/info/rfc7134>.

   [TS.3GPP.22.179]
              3GPP, "3rd Generation Partnership Project; Technical
              Specification Group Services and System Aspects; Mission
              Critical Push To Talk (MCPTT) over LTE; Stage 1", 3GPP
              TS 22.179 13.2.0, June 2015.

Authors' Addresses

   Christer Holmberg
   Ericsson
   Hirsalantie 11
   Jorvas  02420
   Finland

   Email: christer.holmberg@ericsson.com

Holmberg & Axell        Expires December 11, 2016               [Page 5]
Internet-Draft             MCPTT R-P namespace                 June 2016

   Joergen Axell
   Ericsson
   Groenlandsgatan 31
   Stockholm  16480
   Sweden

   Email: jorgen.axell@ericsson.com

Holmberg & Axell        Expires December 11, 2016               [Page 6]