Browse Prior Art Database

IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk Service (RFC8101)

IP.com Disclosure Number: IPCOM000249704D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-23
Document File: 12 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Holmberg: AUTHOR [+2]

Abstract

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 Push To Talk (PTT) service that is suitable for mission critical scenarios and is based upon 3GPP Evolved Packet System (EPS) services. The requirements for the MCPTT service defined within 3GPP can also form the basis for other PTT services.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 25% of the total text.

Internet Engineering Task Force (IETF)                       C. Holmberg Request for Comments: 8101                                      J. Axell Category: Informational                                         Ericsson ISSN: 2070-1721                                               March 2017

        IANA Registration of New Session Initiation Protocol (SIP)  Resource-Priority Namespace for Mission Critical Push To Talk Service

Abstract

   This document creates additional Session Initiation Protocol (SIP)    Resource-Priority namespaces to meet the requirements of the    3GPP-defined Mission Critical Push To Talk (MCPTT) and places these    namespaces in the corresponding IANA registry.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8101.

Copyright Notice

   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.

Holmberg & Axell              Informational                     [Page 1]
 RFC 8101                   MCPTT R-P Namespace                March 2017

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   3    3.  New SIP Resource-Priority Namespaces Created  . . . . . . . .   3      3.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   3      3.2.  The MCPTT Namespaces  . . . . . . . . . . . . . . . . . .   3    4.  Security Considerations . . . . . . . . . . . ....