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

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 01

Network Working Group                                        J. Loughney
Request for Comments: 3589                                         Nokia
Category: Informational                                   September 2003

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

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

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

Abstract

   This document describes the IANA's allocation of a block of Diameter
   Command Codes for the Third Generation Partnership Project (3GPP)
   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.

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

Loughney                     Informational                      [Page 1]
RFC 3589       Diameter Command Codes for 3GPP Release 5 September 2003

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

   The IANA has allocated 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 Considerations

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

Loughney                     Informational                      [Page 2]
RFC 3589       Diameter Command Codes for 3GPP Release 5 September 2003

4.  Intellectual Property Statement

   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
   this standard.  Please address the information to the IETF Executive
   Director [2026].

5.  Acknowledgments

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