Diameter Maintenance andNetwork Working Group M. BrennerExtensions (DIME)Request for Comments: 5224 Alcatel-LucentIntended status:Category: InformationalExpires: July 5,March 2008 Diameter Policy Processing Applicationdraft-brenner-dime-peem-01Status ofthisThis MemoBy submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents ofThis memo provides information for the InternetEngineering 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.community. Itis inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The listdoes not specify an Internet standard ofcurrent Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The listany kind. Distribution ofInternet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on July 5, 2008. Copyright Notice Copyright (C) The IETF Trust (2008).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 MobileAlianceAlliance (OMA) Policy Evaluation, Enforcement and Management (PEEM) enabler, namely for the PEM-1 interface used to send arequest/responsesrequest/response for Policy Processing. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . .32 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . .32 3. Diameter Policy Processing Application . . . . . . . . . . . .32 4. Security Considerations . . . . . . . . . . . . . . . . . . . .32 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . .43 5.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . .43 5.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . .43 5.3. Application Identifier . . . . . . . . . . . . . . . . . .43 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .43 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 7.2. Informative References . . . . . . . . . . . . . . . . . .5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 Intellectual Property and Copyright Statements . . . . . . . . . . 64 1. Introduction This document summarizes the use of Diameter codes in a newly defined realization of a specification for invocation of policy processing (PEM-1). A new Command Codeis requested to behas been assigned by IANA. The document summarizes the uses of newly defined Diameter codes(Command 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,EnforcementEnforcement, 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 per RFC 3588, and extends it only for a specific application using a vendor-id (PEN), a vendor-specific application ID, a new Command Code(TBD),(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[RFC3588] Section(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 in Section 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 in RFC 3588 [RFC3588] are applicable to this document. No further extensions are required beyond the security mechanisms offered by RFC 3588. 5. IANA Considerations This section provides guidance to the Internet Assigned Numbers Authority (IANA) regarding registration of values related to the Diameter protocol, in accordance with BCP 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 valueTBD-Cmd-code314 from the Command Code namespace defined in [RFC3588]. See Section 5.4.1.3.1 of [PEM-1-TS] for the assignment of 314. IANA has made theTBD-Cmd-code.following assignment in the "Authentication, Authorization, and Accounting (AAA) Parameters" registry located at http://www.iana.org/assignments/aaa-parameters, in the sub-registry "Command Codes". Code Value Name Reference -------------- ------------------------------- --------- 314 PDR / PDA [RFC5224] 5.2. AVP Codes This specificationassignsuses the valueTBD-AVP-Code1 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. 7. References 7.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 at http:// www.openmobilealliance.org/ftp/Public_documents/ARCH/ Permanent_documents/ OMA-TS-PEEM_PEM1-V1_0-20071218-D.zip", December 2007. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.[PEM-1-TS]7.2. Informative References [PEEM-AD] Open Mobile Alliance, "Policy Evaluation, Enforcement and ManagementCallable Interface (PEM-1) Technical Specification,Architecture, Draft Version 1.0, available athttp:// www.openmobilealliance.org/ftp/Public_documents/ARCH/ Permanent_documents/OMA-TS-PEEM_PEM1-V1_0-20071218-D.zip", December 2007. 7.2. Informative References [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.http://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/http:// www.openmobilealliance.org/ftp/Public_documents/ARCH/ permanent_documents/ OMA-RD-Policy_Evaluation_Enforcement_Management-V1_0- 20050112-C.zip", November 2005.[PEEM-AD] Open Mobile Alliance, "Policy Evaluation, Enforcement[RFC2434] Narten, T. andManagement Architecture, Draft Version 1.0, available at h ttp://www.openmobilealliance.org/ftp/Public_documents/ ARCH/Permanent_documents/ OMA-AD-Policy_Evaluation_Enforcement_Management-V1_0_0- 20060625-D.zip", June 2006.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-8753Email:EMail: mrbrenner@alcatel-lucent.com Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 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 in BCP 78 and BCP 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 at http://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.Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).