<?xml version="1.0" encoding="iso-8859-1"?>
<!-- comment -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[]>
<?rfc toc="yes" ?>
<?rfc compact="yes" ?>
<?rfc sortrefs="no" ?>
<?rfc subcompact="yes" ?>
<rfc ipr="trust200902" category="info" docName="draft-holmberg-dispatch-mcptt-rp-namespace-01" submissionType="IETF" xml:lang="en">
	<front>
		<title abbrev="MCPTT R-P namespace">
		IANA Registration of New Session Initiation Protocol (SIP)

                      Resource-Priority Namespace for Mission Critical Push To Talk service
		</title>
		<author fullname="Christer Holmberg" initials="C.H." surname="Holmberg">
			<organization abbrev="Ericsson">Ericsson</organization>
			<address>
				<postal>
					<street>Hirsalantie 11</street>
					<city>Jorvas</city>
					<region/>
					<code>02420</code>
					<country>Finland</country>
				</postal>
				<phone/>
				<email>christer.holmberg@ericsson.com</email>
			</address>
		</author>
		<author fullname="Jörgen Axell" initials="J.A" surname="Axell">
			<organization abbrev="Ericsson">Ericsson</organization>
			<address>
				<postal>
					<street>Grönlandsgatan 31</street>
					<city>Stockholm</city>
					<region/>
					<code>16480</code>
					<country>Sweden</country>
				</postal>
				<phone/>
				<email>jorgen.axell@ericsson.com</email>
			</address>
		</author>
		<date year="2016"/>
		<area>Applications and Real-Time</area>
		<keyword>Resource-Priority</keyword>
		<keyword>namespace</keyword>
		<keyword>Resource-priorith</keyword>
		<keyword>3GPP</keyword>
		<keyword>IMS</keyword>
		<keyword>MCPTT</keyword>
		<abstract>

	<t>
	   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.
        </t>
		</abstract>
	</front>
	<middle>
		<section title="Introduction">
	<t>
           The third generation partnership project (3GPP) has defined a Mission Critical
           Push To Talk (MCPTT) over LTE service <xref target="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.
        </t>
	<t>
	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.
	</t>
	<t>
         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.
        </t>
	<t>
         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 <xref target="TS.3GPP.22.179" /> at least 8 and up to 30 priority 
         levels are required.
	</t>
        <t>
         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.
        </t>
	<t>
	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.
        </t>		</section>
		<section title="Conventions">
			<t>
			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 <xref target="RFC2119"/>.
		</t>
		</section>
<section title="Applicability">
       <t>
    This document defines namespaces applicable for MCPTT services defined by 3GPP
    that use the network services of a 3GPP defined LTE network.
       </t>
</section>
		<section title="New SIP Resource-Priority Namespaces Created">
<section title="Introduction">
	<t> 
         This document introduces the MCPTT namespaces mcpttp and mcptt2, the name coming from
         the 3GPP defined Mission Critical Push To Talk service.
        </t>
</section>

<section title="The MCPTT namespaces">
       <t>
    The mcpttp namespace uses the priority levels listed below from lowest to highest
    priority.
   <list style="empty">
    <t>mcpttp.0 (lowest priority)</t>
    <t>mcpttp.1</t>
    <t>mcpttp.2</t>
    <t>mcpttp.3</t>
    <t>mcpttp.4</t>
    <t>mcpttp.5</t>
    <t>mcpttp.6</t>
    <t>mcpttp.7</t>
    <t>mcpttp.8</t>
    <t>mcpttp.9</t>
    <t>mcpttp.10</t>
    <t>mcpttp.11</t>
    <t>mcpttp.12</t>
    <t>mcpttp.13</t>
    <t>mcpttp.14</t>
    <t>mcpttp.15  (highest priority)</t>
   </list>
       </t>
       <t>
    Intended algorithm for mcpttp is preemption.
       </t>
       <t>
    New Warning code: No.
       </t>
       <t>
    New SIP response code: No.
       </t>
       <t>
    The mcpttq namespace uses the priority levels listed below from lowest to highest
    priority.
   <list style="empty">
    <t>mcpttq.0 (lowest priority)</t>
    <t>mcpttq.1</t>
    <t>mcpttq.2</t>
    <t>mcpttq.3</t>
    <t>mcpttq.4</t>
    <t>mcpttq.5</t>
    <t>mcpttq.6</t>
    <t>mcpttq.7</t>
    <t>mcpttq.8</t>
    <t>mcpttq.9</t>
    <t>mcpttq.10</t>
    <t>mcpttq.11</t>
    <t>mcpttq.12</t>
    <t>mcpttq.13</t>
    <t>mcpttq.14</t>
    <t>mcpttq.15  (highest priority)</t>
   </list>
       </t>
       <t>
    Intended algorithm for mcpttq is queuing.
       </t>
       <t>
    New Warning code: No.
       </t>
       <t>
    New SIP response code: No.
       </t>
		</section>
			</section>
<section title="Security Considerations">
		<t>
   This document has the same Security Considerations as <xref target="RFC4412" />.
		</t>
		</section>
		<section anchor="section.iana" title="IANA Considerations">
	<t>
   Abiding by the rules established within <xref target="RFC4412" /> and
    <xref target="RFC7134" />, this is an
   Informative RFC registering two new namespaces, their associated
   priority-values, and intended algorithms.
	</t>
	</section>

    <section title="Acknowledgments">
        <t>
            The authors would like to thank Bob Fredericks, Baruh Hason, Mary Barnes and
            Keith Drage for comments and discussions.
        </t>
    </section>
    <section title="Change Log">
        <t>[RFC EDITOR NOTE: Please remove this section when publishing]</t>
        <t>Changes from draft-holmberg-dispatch-mcptt-rp-namespace-00.  
            <list style="symbols">
                <t>- The two namespaces have been spelt out explicitly.</t>
                <t>- The numbering of priority levels is changed from 1-16 to 0-15.</t>
                <t>- Address of one author has changed.</t>
            </list>
        </t>
    </section>
	</middle>
	<back>
		<references title="Normative References">
			<?rfc include="reference.RFC.2119"?>
			<?rfc include="reference.RFC.4412"?>
			<?rfc include="reference.RFC.7134"?>
			<reference anchor="TS.3GPP.22.179">
				<front>
					<title>
                    3rd Generation Partnership Project;
                    Technical Specification Group Services and System Aspects;
                    Mission Critical Push To Talk (MCPTT) over LTE;
                    Stage 1
                </title>
					<author>
						<organization>3GPP</organization>
					</author>
					<date year="2015" month="June"/>
				</front>
				<seriesInfo value="22.179 13.2.0" name="3GPP TS"/>
				<format type="HTML" target="http://www.3gpp.org/ftp/Specs/html-info/22179.htm"/>
			</reference>

		</references>
	</back>
</rfc>
