Movatterモバイル変換

Network Working Group                                        J. LoughneyRequest for Comments: 3589                                         NokiaCategory: Informational                                   September 2003Diameter Command Codes forThird Generation Partnership Project (3GPP) Release 5Status 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 Contents1.  Introduction...................................................21.1.  Abbreviations............................................22.  Command Code Allocation........................................23.  Security Considerations........................................24.  Acknowledgements...............................................35.  Intellectual Property Statement................................36.  References.....................................................36.1.  Normative References.....................................36.2.  Informative References...................................37.  Author's Address...............................................48.  Full Copyright Statement.......................................5Loughney                     Informational                      [Page 1]

RFC 3589       Diameter Command Codes for 3GPP Release 5 September 20031.  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 Subsystem2.  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 20034.  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 inBCP-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.6.  References6.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.Loughney                     Informational                      [Page 3]

RFC 3589       Diameter Command Codes for 3GPP Release 5 September 20037.  Author's Address   John Loughney   Nokia   Itamerenkatu 11-13   00180 Helsinki   Finland   EMail: john.Loughney@Nokia.comLoughney                     Informational                      [Page 4]

RFC 3589       Diameter Command Codes for 3GPP Release 5 September 20038.  Full Copyright Statement   Copyright (C) The Internet Society (2003).  All Rights Reserved.   This document and translations of it may be copied and furnished to   others, and derivative works that comment on or otherwise explain it   or assist in its implementation may be prepared, copied, published   and distributed, in whole or in part, without restriction of any   kind, provided that the above copyright notice and this paragraph are   included on all such copies and derivative works.  However, this   document itself may not be modified in any way, such as by removing   the copyright notice or references to the Internet Society or other   Internet organizations, except as needed for the purpose of   developing Internet standards in which case the procedures for   copyrights defined in the Internet Standards process must be   followed, or as required to translate it into languages other than   English.   The limited permissions granted above are perpetual and will not be   revoked by the Internet Society or its successors or assigns.   This document and the information contained herein 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.Loughney                     Informational                      [Page 5]