Diameter Maintenance and M. Jones Extensions (DIME) Bridgewater Systems Internet-Draft L. Morand Intended status: Informational Orange Labs Expires: April 17, 2009 October 14, 2008 Diameter Command Codes for 3GPP EPS Diameter Applications draft-jones-3gpp-eps-command-codes-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 17, 2009. Abstract 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). Requirements Language 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 RFC 2119 [RFC2119]. Jones & Morand Expires April 17, 2009 [Page 1] Internet-Draft 3gpp-eps-command-codes October 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 7. Normative References . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 6 Jones & Morand Expires April 17, 2009 [Page 2] Internet-Draft 3gpp-eps-command-codes October 2008 1. Introduction 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 [RFC3588] 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 [TS29.272]. 2. Terminology The base Diameter specification (Section 1.4 of [RFC3588]) defines most of the terminology used in this document. Additionally, the terms and acronyms defined in [TS29.272] are used in this document. 3. Command Codes As described in [TS29.272], the 3GPP S6a application specifies the following command pairs: o Update-Location-Request/Answer (ULR/ULA) o Cancel-Location-Request/Answer (CLR/CLA) o Authentication-Information-Request/ Answer (AIR/AIA) o Insert-Subscriber-Data-Request/Answer (IDR/IDA) o Delete-Subscriber-Data-Request/Answer (DSR/DSA) o Purge-UE-Request/Answer (PUR/PUA) o Reset-Request/Answer (RSR/RSA) o Notify-Request/Answer (NOR/NOA) Also described in [TS29.272], the 3GPP S13 application specifies the following command pair: o ME-Identity-Check-Request/Answer (ECR/ECA) Jones & Morand Expires April 17, 2009 [Page 3] Internet-Draft 3gpp-eps-command-codes October 2008 4. IANA Considerations 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 [RFC2434]. This document defines values in the namespaces that have been created and defined in the Diameter Base [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. 4.1. Command Codes IANA is requested to allocate the following command code values: +------------------------------------------------------------------------+ | 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 | +------------------------------------------------------------------------+ 5. Security Considerations This document describes command codes used in applications which build on top of the Diameter base protocol and the same security considerations described in [RFC3588] are applicable to this document. No further extensions are required beyond the security mechanisms offered by [RFC3588]. 6. Acknowledgements We would like to thank the 3GPP CT4 delegates for their review and comments. Jones & Morand Expires April 17, 2009 [Page 4] Internet-Draft 3gpp-eps-command-codes October 2008 7. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003. [TS29.272] 3rd Generation Partnership Project, "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)", http://www.3gpp.org/ftp/Specs/html-info/29272.htm, 09 2008. Authors' Addresses Mark Jones Bridgewater Systems Email: mark.jones@bridgewatersystems.com Lionel Morand Orange Labs Email: lionel.morand@orange-ftgroup.com Jones & Morand Expires April 17, 2009 [Page 5] Internet-Draft 3gpp-eps-command-codes October 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Jones & Morand Expires April 17, 2009 [Page 6]