RFC 3589

Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5

📅 published September 2003, from ietf

🎀 RFC 3589: Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5 💖

Network Working Group

Request for Comments: 3589 🦋 Title: Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5 Author: J. Loughney, from Nokia 🧚 Category: Informational Date: September 2003 Obsoletes / Updates: The header doesn't list anything this one obsoletes or updates 🙈

Status of This Memo ✨

This memo gives info to the Internet community 📚 It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract 🌸

Okay so this doc describes how the IANA handed out a block of Diameter Command Codes for 3GPP Release 5 💅 It does not judge how anyone uses those command codes. Furthermore, these codes are for Release 5 only. For future releases, the codes can't be reused, and they must be allocated according to the Diameter Base specification. Iconic restraint, honestly 👑

Table of Contents 🍓

   1.  Introduction................................................... 2
       1.1.  Abbreviations............................................ 2
   2.  Command Code Allocation........................................ 2
   3.  Security Considerations........................................ 2
   4.  Acknowledgements............................................... 3
   5.  Intellectual Property Statement................................ 3
   6.  References..................................................... 3
       6.1.  Normative References..................................... 3
       6.2.  Informative References................................... 3
   7.  Author's Address............................................... 4
   8.  Full Copyright Statement....................................... 5

1. Introduction 🌈

Bestie, the Third Generation Partnership Project (3GPP) is defining the Internet Multimedia Subsystem (IMS) as part of their Release 5 architecture ✨ As part of that, they defined a Diameter application [29.229] and [29.329] that needs new Diameter Command Codes [DIAM]. Main character energy 🎬

1.1. Abbreviations 💅

  • 3GPP Third Generation Partnership Project
  • IANA Internet Assigned Name Authority
  • IMS Internet Multimedia Subsystem

2. Command Code Allocation 🔥

The IANA gave out Diameter Command Codes 300 through 313 for use in 3GPP Release 5 🫶 Ngl, these protocols haven't gone through careful review by the IETF community, so they aren't considered general mechanisms for broad usage. More work is needed to build general mechanisms, and that could become a work item of an IETF Working Group 🧐 These command codes are meant for 3GPP Release 5 only [29.228], [29.229]. Future 3GPP releases are expected to use alternate mechanisms, so no spoilers, but it's not this 🙈

Command codes for 3GPP Release 6 are expected to be allocated from the standard command space, with IETF documentation. The current plan, as agreed with 3GPP, is to develop a standards track application for the AAA needs of SIP/SDP, covering the requirements of the cellular community 📡✨

3. Security Considerations 🔐

This document is not known to affect the security of the Internet 🫠

4. Intellectual Property Statement ⚖️

The IETF takes no position on 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 on whether any license under such rights might or might not be available. It also doesn't say it has tried to identify any such rights. Info on the IETF's procedures for 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 to get a general license or permission for implementors or users to use such proprietary rights, 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 this standard. Please send that info to the IETF Executive Director [2026] 💌

5. Acknowledgments 🫶

The author would like to thank Bernard Aboba, Randy Bush, Allison Mankin and Stephen Hayes 💖

6. References 📚

6.1. Normative References

  • [2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.

6.2. Informative 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).
  • [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., Loughney, J., Guttman, E., Zorn, G. and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.

7. Author's Address 📮

   John Loughney
   Nokia
   Itamerenkatu 11-13
   00180 Helsinki
   Finland

   EMail: john.Loughney@Nokia.com

Copyright (C) The Internet Society (2003). All Rights Reserved.

You can copy and share this document and its translations with others, and make derivative works that comment on or explain it or help implement it. Those can be prepared, copied, published and distributed, in whole or in part, with no restriction of any kind, as long as the above copyright notice and this paragraph are included on all copies and derivative works. But this document itself can't be modified in any way, like removing the copyright notice or references to the Internet Society or other Internet organizations. The exceptions are when it's needed for developing Internet standards, in which case the copyright procedures in the Internet Standards process must be followed, or when it's needed to translate it into languages other than English 🌍

The permissions above are perpetual and won't be revoked by the Internet Society or its successors or assigns ♾️

This document and the info in it is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. 🙃

Acknowledgement 🧚

Funding for the RFC Editor function is currently provided by the Internet Society 💜

📦 where this page comes from