Network Working Group M. Brenner
Request for Comments: 5224 Alcatel-Lucent
Category: Informational March 2008
Network Working Group M. Brenner
Request for Comments: 5224 Alcatel-Lucent
Category: Informational March 2008
Diameter Policy Processing Application
Diameter策略处理应用程序
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.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
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.
本文档描述了在特定于供应商的新应用程序中使用新IANA Diameter命令代码以调用策略处理（策略评估，或评估和实施）的需求。此应用程序需要作为开放移动联盟（OMA）策略评估、实施和管理（PEEM）启用码的实现之一，即用于发送策略处理请求/响应的PEM-1接口。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Diameter Policy Processing Application . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 2
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . . 3
5.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.3. Application Identifier . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . . 4
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Diameter Policy Processing Application . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 2
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Command Codes . . . . . . . . . . . . . . . . . . . . . . . 3
5.2. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.3. Application Identifier . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . . 4
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].
本文档总结了Diameter代码在新定义的策略处理调用规范实现中的使用。IANA分配了一个新的命令代码。本文档总结了新定义的直径代码（命令代码、AVP和特定于供应商的应用程序id）的使用。当与Diameter基本协议结合使用时，该应用程序的规范满足开放移动联盟（OMA）策略评估、实施和管理（PEEM）要求，用于发送策略处理请求和接收带有策略处理结果的响应。直径的标准用法见[PEM-1-TS]。PEEM需求记录在[PEEM-RD]中，PEEM架构记录在[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 (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.
根据RFC 3588，此应用程序的Diameter实现假定使用Diameter基本协议，并仅使用供应商id（PEN）、供应商特定应用程序id、新命令代码（314）和供应商特定命名空间中定义的新AVP，将其扩展到特定应用程序。策略处理的输入通过新的AVP传递，策略结果通过相同的新AVP和实验结果AVP的组合传递。
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.
底座直径规范（RFC3588第1.4节）定义了本文件中使用的大部分术语。此外，本文件使用了[PEM-1-TS]中定义的术语和首字母缩略词。
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].
有关Diameter策略处理应用程序的详细说明，请参见策略评估、实施和管理可调用接口（PEM-1）技术规范[PEM-1-TS]第5.4.1节。
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.
本文档介绍Diameter策略处理应用程序。它建立在Diameter基础协议之上，RFC 3588[RFC3588]中描述的相同安全注意事项适用于本文档。除RFC 3588提供的安全机制外，无需进一步扩展。
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].
本节根据BCP 26[RFC2434]为互联网分配号码管理局（IANA）提供有关Diameter协议相关值注册的指南。
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.
本文档定义了在Diameter Base[RFC3588]中创建和定义的名称空间中的值。该文件的IANA注意事项部分详细说明了分配标准。本文档中分配的值或未来IANA操作分配的值必须在此共享命名空间中进行协调。
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.
本规范从[RFC3588]中定义的命令代码命名空间中指定值314。参见[PEM-1-TS]第5.4.1.3.1节，了解如何使用命令代码。
IANA has made the following assignment in the "Authentication, Authorization, and Accounting (AAA) Parameters" registry, in the sub-registry "Command Codes".
IANA在“认证、授权和记帐（AAA）参数”注册表中的子注册表“命令代码”中进行了以下分配。
Code Value Name Reference
-------------- ------------------------------- ---------
314 PDR / PDA [RFC5224]
Code Value Name Reference
-------------- ------------------------------- ---------
314 PDR / PDA [RFC5224]
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.
此规范使用OMA供应商ID（PEN）AVP命名空间中策略数据AVP的值1。有关本规范中名称空间的分配，请参见[PEM-1-TS]第5.4.1.3.3节。
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.
此规范使用在IANA中为策略处理应用程序注册的应用程序标识符命名空间中的值16777243。详见[PEM-1-TS]第5.4.1.3节。
The author would like to thank Dan Romascanu and Hannes Tschofenig for their help and support.
作者要感谢Dan Romascanu和Hannes Tschofenig的帮助和支持。
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.
最后，作者要感谢阿尔卡特朗讯公司，因为在这份文件中投入的大部分精力都是在他受雇期间完成的。
[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-20080325-D.zip", December 2007.
[PEM-1-TS]开放移动联盟，“政策评估、执行和管理可调用接口（PEM-1）技术规范草案，第1.0版，可在http://www.openmobilealliance.org/ftp/Public_documents/ARCH/Permanent_documents/OMA-TS-PEEM_PEM1-V1_0-20080325;-D.zip上获得”，2007年12月。
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3588]Calhoun，P.，Loughney，J.，Guttman，E.，Zorn，G.，和J.Arkko，“直径基础协议”，RFC 3588，2003年9月。
[PEEM-AD] Open Mobile Alliance, "Policy Evaluation, Enforcement and Management Architecture, Draft Version 1.0, available at 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-AD]开放式移动联盟，“政策评估、实施和管理体系结构，草案版本1.0”，可在http://www.openmobilealliance.org/ftp/Public_documents/ ARCH/Permanent_documents/OMA-AD-Policy_Evaluation_Enforcement_Management-V1_0_0-20060625-D.zip”，2006年6月。
[PEEM-RD] Open Mobile Alliance, "Policy Evaluation, Enforcement and Management Requirements, Candidate Version 1.0, 12 January 2005, available at http:// www.openmobilealliance.org/ftp/Public_documents/ARCH/ permanent_documents/ OMA-RD-Policy_Evaluation_Enforcement_Management-V1_0- 20050112-C.zip", November 2005.
[PEEM-RD]开放移动联盟，“政策评估、执行和管理要求，候选版本1.0，2005年1月12日，可在http://www.openmobilealliance.org/ftp/Public_documents/ARCH/permanent_documents/OMA-RD-Policy_评估_执行_管理-V1_0-20050112-C.zip上查阅”，2005年11月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
Author's Address
作者地址
Michael Brenner Alcatel-Lucent 600-700 Mountain Avenue, 2D-148 Murray Hill, NJ 07974-0636 USA
迈克尔·布伦纳·阿尔卡特·朗讯美国新泽西州默里山2D-148山地大道600-700号，邮编：07974-0636
Phone: +1 908-582-8753
EMail: mrbrenner@alcatel-lucent.com
Phone: +1 908-582-8753
EMail: mrbrenner@alcatel-lucent.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（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.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和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.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为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.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.