Internet Internet Draft J. Loughney Document: draft-loughney-aaa-cc-3gpp-01.txt Nokia Expires: 2002 June 2003 Diameter Command Codes for 3GPP Release 5 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. 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. Abstract This document requests IANA to allocate a block of Diameter command codes for the Third Generation Partnership Project Release 5. This document does not pass judgment on the usage of these command codes. Further more, these command codes are for use for Release 5. For future releases, these codes cannot be reused, but must be allocated according to the Diameter Base specification. Loughney Expires - June 2003 [Page 1] Provisional Diameter Command Codes for 3GPP Release 5 Table of Contents 1. Introduction...................................................3 1.1 Conventions used in this document..........................3 1.2 Abbreviations..............................................3 2. Command Code Allocation........................................3 3. Security Consideration.........................................3 4. References.....................................................3 5. Acknowledgments................................................4 6. Author's Addresses.............................................4 Loughney Expires - June 2003 [Page 2] Provisional Diameter Command Codes for 3GPP Release 5 1. Introduction The Third Generation Partnership Project (3GPP) is defining the Internet Multimedia Subsystem (IMS) as part of their Release 5 architecture. As part of this architecture, they have defined a Diameter application [29.229] and [29.329] which requires the use of new Diameter command codes [DIAM]. 1.1 Abbreviations 3GPP Third Generation Partnership Project IANA Internet Assigned Name Authority IMS Internet Multimedia Subsystem 2. Command Code Allocation This document requests IANA to allocate Diameter Command Codes 300 through 313, for use in 3GPP Release 5. The protocols defined by these command codes have not been carefully reviewed by the IETF community and are not considered to be general mechanisms appropriate for broad usage. More work is needed to develop general mechanisms and may become a work item of an IETF Working Group. These command codes are intended to be used for 3GPP Release 5 only [29.228], [29.229]. Future 3GPP releases are expected to make use of alternate mechanisms. Command codes for 3GPP Release 6 are expected to be allocated from the standard command space, with IETF documentation. The current intent as agreed with 3GPP is to develop a standards track application addressing the needs of AAA for SIP/SDP and encompassing the requirements of the cellular community. 3. Security Consideration This document is not known to affect the security of the Internet. 4. References 4.1 Non-Normative References [29.229] 3GPP TS 29.229 V5.1.0 (2002-09); Technical Specification; Technical Specification Group Core Network; Cx and Dx interfaces based on the Diameter protocol; Protocol details; (Release 5). Loughney Expires - June 2003 [Page 3] Provisional Diameter Command Codes for 3GPP Release 5 [29.329] 3GPP TS 29.329 V5.1.0 (2002-09); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network; Sh Interface based on the Diameter protocol; Protocol details; (Release 5) [DIAM] Calhoun, P., et. al., "Diameter Base Protocol", IETF work in progress. 4.2 Non-Normative References [2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 5. Acknowledgments The author would like to thank Bernard Aboba, Randy Bush, Allison Mankin and Stephen Hayes. 6. Author's Addresses John Loughney Nokia It„merenkatu 11-13 00180 Helsinki Finland Email: john.Loughney@Nokia.com 7. Notices The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights, which may cover technology that may be required to practice Loughney Expires - June 2003 [Page 4] Provisional Diameter Command Codes for 3GPP Release 5 this standard. Please address the information to the IETF Executive Director. Loughney Expires - June 2003 [Page 5]