<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="info" docName="draft-jones-dime-3gpp-eps-command-codes-02"
     ipr="trust200902">
  <front>
    <title abbrev="3gpp-eps-command-codes">
	Diameter Command Code Registration for Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)
	</title>

    <author fullname="Mark Jones" initials="M" surname="Jones">
      <organization>Bridgewater Systems</organization>

      <address>
        <email>mark.jones@bridgewatersystems.com</email>
      </address>
    </author>

    <author fullname="Lionel Morand" initials="L" surname="Morand">
      <organization>Orange Labs</organization>

      <address>
        <email>lionel.morand@orange-ftgroup.com</email>
      </address>
    </author>

    <date year="2009" />

    <area>Operations and Management</area>

    <workgroup>Diameter Maintenance and Extensions (DIME)</workgroup>

    <keyword>3GPP</keyword>

    <keyword>Release 8</keyword>

    <keyword>Diameter</keyword>

    <keyword>command codes</keyword>

    <abstract>
      <t>This document registers a set of IANA Diameter
      Command Codes to be used in new vendor-specific Diameter applications
      defined for the Third Generation Partnership Project (3GPP) Evolved 
	  Packet System (EPS). These new Diameter applications are defined for 
	  Mobile Management Entity (MME) and Serving GPRS Support Node (SGSN) 
	  related interfaces in the Release 8 architecture.</t>
    </abstract>

  </front>

  <middle>
    <section title="Introduction">
	
      <t>The Third Generation Partnership Project (3GPP) is defining the
      Evolved Packet System (EPS) as part of their Release 8 architecture. As
      part of this architecture, the interfaces based on the Diameter
      protocol <xref target="RFC3588"></xref> require the definition of two
      new Diameter applications.</t>
	  <t>The 3GPP S6a/S6d application (vendor-specific application id: 1677251) 
	  enables the transfer of subscriber related data between the Mobile Management 
	  Entity (MME) and Home Subscriber Server (HSS) on the S6a interface and 
	  between the Serving GPRS Support Node (SGSN) and Home Subscriber Server 
	  (HSS) on the S6d interface.</t>
	  <t>The 3GPP S13/S13' application (vendor-specific application id: 1677252) 
	  enables the Mobile Equipment Identity check procedure between the Mobile 
	  Management Entity (MME) and Equipment Identity Register (EIR)
	  on the S13 interface and between the Serving GPRS Support Node (SGSN)
	  and Equipment Identity Register (EIR) on the S13' interface.</t>
	  <t>Both Diameter applications are defined under the 3GPP vendor-id "10415" 
	  and are defined in <xref target="TS29.272"/>. This document defines the 
	  assigned values of the command codes used in these applications.</t>	  

    </section>

    <section title="Terminology">
      <t>The base Diameter specification (Section 1.4 of <xref
      target="RFC3588"></xref>) defines most of the terminology used in this
      document. Additionally, the terms and acronyms defined in <xref
      target="TS29.272"></xref> are used in this document.</t>
    </section>

    <section title="Command Codes">
      <t>The 3GPP S6a/S6d application described in section 5 of 
	  <xref target="TS29.272"/> requires the allocation of command code 
	  values for the following command pairs:</t>

      <t><list style="symbols">
          <t>3GPP-Update-Location-Request/Answer (ULR/ULA)</t>

          <t>3GPP-Cancel-Location-Request/Answer (CLR/CLA)</t>

          <t>3GPP-Authentication-Information-Request/ Answer (AIR/AIA)</t>

          <t>3GPP-Insert-Subscriber-Data-Request/Answer (IDR/IDA)</t>

          <t>3GPP-Delete-Subscriber-Data-Request/Answer (DSR/DSA)</t>

          <t>3GPP-Purge-UE-Request/Answer (PUR/PUA)</t>

          <t>3GPP-Reset-Request/Answer (RSR/RSA)</t>

          <t>3GPP-Notify-Request/Answer (NOR/NOA)</t>
        </list>
	  </t>

      <t>The 3GPP S13/S13 application described in section 6 of 
	  <xref target="TS29.272"/> requires the allocation of a command code 
	  value for the following command pair:</t>

      <t><list style="symbols">
          <t>3GPP-ME-Identity-Check-Request/Answer (ECR/ECA)</t>
        </list></t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This section provides guidance to the Internet Assigned Numbers
      Authority (IANA) regarding registration of values related to the
      Diameter protocol, in accordance with BCP 26 <xref target="RFC5226"/>.</t>
	  <t>This document defines values in the namespace that
      has been defined in the Diameter Base specification <xref target="RFC3588"/>. 
	  Section 11 of <xref target="RFC3588"/> (IANA Considerations) details the 
	  assignment criteria. IANA is requested to allocate the following command code
      values:</t>

      <figure>
        <artwork><![CDATA[
+----------------------------------------------------------------------+
| Code Command Name                            Abbrev.  Defined in     |
+----------------------------------------------------------------------+
| tbd  3GPP-Update-Location-Request            ULR      3GPP TS 29.272 |
| tbd  3GPP-Update-Location-Answer             ULA      3GPP TS 29.272 |
| tbd  3GPP-Cancel-Location-Request            CLR      3GPP TS 29.272 |
| tbd  3GPP-Cancel-Location-Answer             CLA      3GPP TS 29.272 |
| tbd  3GPP-Authentication-Information-Request AIR      3GPP TS 29.272 |
| tbd  3GPP-Authentication-Information-Answer  AIA      3GPP TS 29.272 |
| tbd  3GPP-Insert-Subscriber-Data-Request     IDR      3GPP TS 29.272 |
| tbd  3GPP-Insert-Subscriber-Data-Answer      IDA      3GPP TS 29.272 |
| tbd  3GPP-Delete-Subscriber-Data-Request     DSR      3GPP TS 29.272 |
| tbd  3GPP-Delete-Subscriber-Data-Answer      DSA      3GPP TS 29.272 |
| tbd  3GPP-Purge-UE-Request                   PUR      3GPP TS 29.272 |
| tbd  3GPP-Purge-UE-Answer                    PUA      3GPP TS 29.272 |
| tbd  3GPP-Reset-Request                      RSR      3GPP TS 29.272 |
| tbd  3GPP-Reset-Answer                       RSA      3GPP TS 29.272 |
| tbd  3GPP-Notify-Request                     NOR      3GPP TS 29.272 |
| tbd  3GPP-Notify-Answer                      NOA      3GPP TS 29.272 |
| tbd  3GPP-ME-Identity-Check-Request          ECR      3GPP TS 29.272 |
| tbd  3GPP-ME-Identity-Check-Answer           ECA      3GPP TS 29.272 |
+----------------------------------------------------------------------+
]]></artwork>
      </figure>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>This document describes command codes used in applications which
      build on top of the Diameter base protocol and the same security
      considerations described in <xref target="RFC3588"></xref> are
      applicable to this document. No further extensions are required beyond
      the security mechanisms offered by <xref target="RFC3588"></xref>.</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>We would like to thank the 3GPP CT4 delegates, Victor Fajardo and
	  Glen Zorn for their review and comments. We would also like to thank 
	  Dan Romascanu for volunteering to be AD sponsor and Hannes Tschofenig 
	  for volunteering to be Document Shepherd.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.3588"?>
      <reference anchor="TS29.272">
        <front>
          <title>
		  3GPP TS 29.272;
		  Technical Specification Group Core Network and Terminals; 
		  Evolved Packet System; 
		  Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN)
		  Related Interfaces Based on Diameter Protocol (Release 8)
		  </title>

          <author>
            <organization abbrev="3GPP">3rd Generation Partnership
            Project</organization>
          </author>
        </front>

        <seriesInfo name=""
                    value="http://www.3gpp.org/ftp/Specs/html-info/29272.htm" />
      </reference>
	</references>
    <references title="Informative References">
	      <?rfc include="reference.RFC.5226"?>
	</references>
  </back>
</rfc>