<?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-3gpp-eps-command-codes-00"
     ipr="full3978">
  <front>
    <title abbrev="3gpp-eps-command-codes">Diameter Command Codes for 3GPP EPS
    Diameter Applications</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="2008" />

    <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 describes a set of new 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).</t>
    </abstract>

    <note title="Requirements Language">
      <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">RFC 2119</xref>.</t>
    </note>
  </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> required the definition of two
      new Diameter applications: the 3GPP S6a application (vendor-specific
      application id: 1677251) and 3GPP S13 application (vendor-specific
      application id: 1677252), both defined under the 3GPP vendor-id "10415". 
	  These Diameter applications are described in <xref
      target="TS29.272"></xref>.</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>As described in <xref target="TS29.272"/>, the 3GPP S6a
	  application specifies the following command pairs:</t>

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

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

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

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

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

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

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

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

      <t>Also described in <xref target="TS29.272"/>, the 3GPP S13
      application specifies the following command pair:</t>

      <t><list style="symbols">
          <t>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="RFC2434"/>.<vspace
      blankLines="1" />This document defines values in the namespaces that
      have been created and defined in the Diameter Base <xref target="RFC3588"/>. The IANA
      Considerations section of that document details the assignment criteria.
      Values assigned in this document, or by future IANA action, must be
      coordinated within this shared namespace.</t>

      <section title="Command Codes">
        <t>IANA is requested to allocate the following command code
        values:</t>

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

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>
      <?rfc include="reference.RFC.2434"?>

      <reference anchor="RFC3588">
        <front>
          <title>Diameter Base Protocol</title>

          <author fullname="P. Calhoun" initials="P." surname="Calhoun">
            <organization></organization>
          </author>

          <author fullname="J. Loughney" initials="J." surname="Loughney">
            <organization></organization>
          </author>

          <author fullname="E. Guttman" initials="E." surname="Guttman">
            <organization></organization>
          </author>

          <author fullname="G. Zorn" initials="G." surname="Zorn">
            <organization></organization>
          </author>

          <author fullname="J. Arkko" initials="J." surname="Arkko">
            <organization></organization>
          </author>

          <date month="September" year="2003" />

          <abstract>
            <t>The Diameter base protocol is intended to provide an
            Authentication, Authorization and Accounting (AAA) framework for
            applications such as network access or IP mobility. Diameter is
            also intended to work in both local Authentication, Authorization
            &amp;amp; Accounting and roaming situations. This document
            specifies the message format, transport, error reporting,
            accounting and security services to be used by all Diameter
            applications. The Diameter base application needs to be supported
            by all Diameter implementations. [STANDARDS TRACK]</t>
          </abstract>
        </front>

        <seriesInfo name="RFC" value="3588" />

        <format octets="341261"
                target="ftp://ftp.isi.edu/in-notes/rfc3588.txt" type="TXT" />
      </reference>

      <reference anchor="TS29.272">
        <front>
          <title>
		  3GPP TS 29.272 V8.0.0;
		  Technical Specification Group Core Network and Terminals; 
		  Evolved Packet System; 
		  MME and SGSN Related Interfaces Based on Diameter Protocol
		  (Release 8)
		  </title>

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

          <date month="09" year="2008" />
        </front>

        <seriesInfo name=""
                    value="http://www.3gpp.org/ftp/Specs/html-info/29272.htm" />
      </reference>
    </references>
  </back>
</rfc>