Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/internet-drafts/draft-holmberg-dispatch-mcptt-rp-namespace-00.txt Дата изменения: Tue Feb 9 16:46:38 2016 Дата индексирования: Sun Apr 10 08:14:05 2016 Кодировка:

Network Working Group C. Holmberg
Internet-Draft J. Axell
Intended status: Informational Ericsson
Expires: August 12, 2016 February 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-00

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 August 12, 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 August 12, 2016 [Page 1]

Internet-Draft MCPTT R-P namespace February 2016


Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. New SIP Resource-Priority Namespaces Created . . . . . . . . 3
3.1. Introduction . . . . . . . . . . . . . . . . . . . . . . 3
3.2. The MCPTT namespaces . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
7. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . 4
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 August 12, 2016 [Page 2]

Internet-Draft MCPTT R-P namespace February 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. New SIP Resource-Priority Namespaces Created

3.1. Introduction

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

3.2. The MCPTT namespaces

The MCPTT namespaces use the priority levels listed below from lowest
to highest priority.

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

where N is 1 or 2.



Holmberg & Axell Expires August 12, 2016 [Page 3]

Internet-Draft MCPTT R-P namespace February 2016


Intended algorithm for mcptt1 is preemption, and for mcptt2 is
queueing.

New Warning code: No.

New SIP response code: No.

4. Security Considerations

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

5. 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.

6. Acknowledgments

TBD

7. Change Log

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

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

o - Some change

8. 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,
.

[RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource
Priority for the Session Initiation Protocol (SIP)",
RFC 4412, DOI 10.17487/RFC4412, February 2006,
.

[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,
.






Holmberg & Axell Expires August 12, 2016 [Page 4]

Internet-Draft MCPTT R-P namespace February 2016


[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


Joergen Axell
Ericsson
Kistavaegen 25
Stockholm 16480
Sweden

Email: jorgen.axell@ericsson.com



























Holmberg & Axell Expires August 12, 2016 [Page 5]