Movatterモバイル変換

Network Working Group                                         M. BrennerRequest for Comments: 5224                                Alcatel-LucentCategory: Informational                                       March 2008Diameter Policy Processing ApplicationStatus 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.Abstract   This document describes the need for a new IANA Diameter Command Code   to be used in a vendor-specific new application for invocation of   Policy Processing (Policy Evaluation, or Evaluation and Enforcement).   This application is needed as one of the implementations of the Open   Mobile Alliance (OMA) Policy Evaluation, Enforcement and Management   (PEEM) enabler, namely for the PEM-1 interface used to send a   request/response for Policy Processing.Table of Contents1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .22.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . .23.  Diameter Policy Processing Application  . . . . . . . . . . . .24.  Security Considerations . . . . . . . . . . . . . . . . . . . .25.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .35.1.  Command Codes . . . . . . . . . . . . . . . . . . . . . . .35.2.  AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . .35.3.  Application Identifier  . . . . . . . . . . . . . . . . . .36.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . .37.  References  . . . . . . . . . . . . . . . . . . . . . . . . . .47.1.  Normative References  . . . . . . . . . . . . . . . . . . .47.2.  Informative References  . . . . . . . . . . . . . . . . . .4Brenner                      Informational                      [Page 1]

RFC 5224                          PEEM                        March 20081.  Introduction   This document summarizes the use of Diameter codes in a newly defined   realization of a specification for invocation of policy processing.   A new Command Code has been assigned by IANA.  The document   summarizes the uses of newly defined Diameter codes (a Command Code,   an AVP, and a vendor-specific application id).  When combined with   the Diameter Base protocol, this application's specification   satisfies the Open Mobile Alliance (OMA) Policy Evaluation,   Enforcement, and Management (PEEM) requirements for sending a request   for policy processing and receiving a response with the policy   processing result.  See [PEM-1-TS] for the normative use of Diameter.   PEEM requirements are documented in [PEEM-RD] and PEEM Architecture   is documented in [PEEM-AD].   The Diameter realization of this application assumes the use of the   Diameter Base protocol, as perRFC 3588, and extends it only for a   specific application using a vendor-id (PEN), a vendor-specific   application ID, a new Command Code (314), and a new AVP defined in   the vendor-specific namespace.  Input to policy processing are being   passed through a new AVP, and policy results are being passed through   a combination of the same new AVP, and the Experimental-Result AVP.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 [PEM-1-TS] are used in this document.3.  Diameter Policy Processing Application   A detailed description of the Diameter Policy Processing Application   can be found inSection 5.4.1 of the Policy Evaluation, Enforcement   and Management Callable Interface (PEM-1) Technical Specification   [PEM-1-TS].4.  Security Considerations   This document describes the Diameter Policy Processing Application.   It builds on top of the Diameter Base protocol and the same security   considerations described inRFC 3588 [RFC3588] are applicable to this   document.  No further extensions are required beyond the security   mechanisms offered byRFC 3588.Brenner                      Informational                      [Page 2]

RFC 5224                          PEEM                        March 20085.  IANA Considerations   This section provides guidance to the Internet Assigned Numbers   Authority (IANA) regarding registration of values related to the   Diameter protocol, in accordance withBCP 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.5.1.  Command Codes   This specification assigns the value 314 from the Command Code   namespace defined in [RFC3588].  See Section 5.4.1.3.1 of [PEM-1-TS]   to see how the command code is used.   IANA has made the following assignment in the "Authentication,   Authorization, and Accounting (AAA) Parameters" registry, in the sub-   registry "Command Codes".   Code Value          Name                            Reference   --------------      ------------------------------- ---------   314                 PDR / PDA                       [RFC5224]5.2.  AVP Codes   This specification uses the value 1 for the Policy-Data AVP, in the   OMA Vendor-ID (PEN) AVP namespace.  See Section 5.4.1.3.3 of   [PEM-1-TS] for the assignment of the namespace in this specification.5.3.  Application Identifier   This specification uses the value 16777243 in the Application   Identifier namespace as registered in IANA for the Policy Processing   Application.  See Section 5.4.1.3 of [PEM-1-TS] for more information.6.  Acknowledgements   The author would like to thank Dan Romascanu and Hannes Tschofenig   for their help and support.   Finally, the author would like to thank Alcatel-Lucent, as most of   the effort put into this document was done while he was in their   employ.Brenner                      Informational                      [Page 3]

RFC 5224                          PEEM                        March 20087.  References7.1.  Normative References   [PEM-1-TS]  Open Mobile Alliance, "Policy Evaluation, Enforcement and               Management Callable Interface (PEM-1) Technical               Specification, Draft Version 1.0, available athttp://www.openmobilealliance.org/ftp/Public_documents/ARCH/               Permanent_documents/               OMA-TS-PEEM_PEM1-V1_0-20080325-D.zip", December 2007.   [RFC3588]   Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.               Arkko, "Diameter Base Protocol",RFC 3588,               September 2003.7.2.  Informative References   [PEEM-AD]   Open Mobile Alliance, "Policy Evaluation, Enforcement and               Management Architecture, Draft Version 1.0, available athttp://www.openmobilealliance.org/ftp/Public_documents/ARCH/Permanent_documents/               OMA-AD-Policy_Evaluation_Enforcement_Management-V1_0_0-               20060625-D.zip", June 2006.   [PEEM-RD]   Open Mobile Alliance, "Policy Evaluation, Enforcement and               Management Requirements, Candidate Version 1.0, 12               January 2005, available athttp://www.openmobilealliance.org/ftp/Public_documents/ARCH/               permanent_documents/               OMA-RD-Policy_Evaluation_Enforcement_Management-V1_0-               20050112-C.zip", November 2005.   [RFC2434]   Narten, T. and H. Alvestrand, "Guidelines for Writing an               IANA Considerations Section in RFCs",BCP 26,RFC 2434,               October 1998.Author's Address   Michael Brenner   Alcatel-Lucent   600-700 Mountain Avenue, 2D-148   Murray Hill, NJ  07974-0636   USA   Phone: +1 908-582-8753   EMail: mrbrenner@alcatel-lucent.comBrenner                      Informational                      [Page 4]

RFC 5224                          PEEM                        March 2008Full Copyright Statement   Copyright (C) The IETF Trust (2008).   This document is subject to the rights, licenses and restrictions   contained inBCP 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 inBCP 78 andBCP 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 athttp://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.Brenner                      Informational                      [Page 5]