[Docs] [txt|pdf|xml|html] [Tracker] [Email] [Nits]

Versions: 00 01 RFC 5224

Diameter Maintenance and                                      M. Brenner
Extensions (DIME)                                         Alcatel-Lucent
Internet-Draft                                         December 15, 2007
Intended status: Informational
Expires: June 17, 2008


                 Diameter Policy Processing Application
                       draft-brenner-dime-peem-00

Status of this Memo

   By 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 of the Internet Engineering
   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.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on June 17, 2008.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document describes the Diameter protocol application used for
   invocation of Policy Processing (Policy Evaluation, or Evaluation and
   Enforcement).  This application is needed as one of the
   implementations of the Open Mobile Aliance (OMA) Policy Evaluation,
   Enforcement and Management (PEEM) enabler, namely for the PEM-1
   interface used to send a request/responses for Policy Processing.
   When combined with the Diameter Base protocol, this application



Brenner                   Expires June 17, 2008                 [Page 1]

Internet-Draft                    PEEM                     December 2007


   specification satisfies the OMA PEEM requirements for sending a
   request for policy processing and receiving a response with the
   policy processing result.

   The Diameter realization of this application assumes the use of
   Diameter Base protocol, as per RFC 3588, and extends it only for the
   with an application using a vendor-id, a vendor-specific application
   ID, a new Command Code, 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.


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3

   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3

   3.  Diameter Policy Processing Application  . . . . . . . . . . . . 3

   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3

   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
     5.1.  Command Codes . . . . . . . . . . . . . . . . . . . . . . . 4
     5.2.  AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 4
     5.3.  Application Identifier  . . . . . . . . . . . . . . . . . . 4

   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4

   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 5

   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 5
   Intellectual Property and Copyright Statements  . . . . . . . . . . 6















Brenner                   Expires June 17, 2008                 [Page 2]

Internet-Draft                    PEEM                     December 2007


1.  Introduction

   This document describes the Diameter protocol application used for
   invocation of Policy Processing for resources in a Service Provider's
   environment.  When combined with the Diameter Base protocol, this
   application specification satisfies the Open Mobile Alliance (OMA)
   Policy Evaluation, Enforcement and Management (PEEM) requirements
   [PEEM-RD] for sending a request for policy processing and receiving a
   response with the policy processing result.

   The Diameter realization of this application assumes the use of
   Diameter Base protocol, as per RFC 3588, and extends it only for with
   a specific application using a vendor-id, a vendor-specific
   application ID, a new Command Code, 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

   In this document, several words are used to signify the requirements
   of the specification.  These words are often capitalized.  The key
   words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
   "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
   are to be interpreted as described in [RFC2119].

   The base Diameter specification [RFC3588] Section 1.4 defines most of
   the terminology used in this document.  Additionally, the terms and
   acronyms defined in [PEEM-AD] and [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



Brenner                   Expires June 17, 2008                 [Page 3]

Internet-Draft                    PEEM                     December 2007


   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 value TBD-Cmd-code from the Command
   Code namespace defined in [RFC3588].  See Section 5.4.1.3.1 of
   [PEM-1-TS] for the assignment of the TBD-Cmd-code.

5.2.  AVP Codes

   This specification assigns the value TBD-AVP-Code 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





Brenner                   Expires June 17, 2008                 [Page 4]

Internet-Draft                    PEEM                     December 2007


7.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3588]  Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
              Arkko, "Diameter Base Protocol", RFC 3588, September 2003.

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.

   [RFC2234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", RFC 2234, November 1997.

   [PEEM-RD]  Open Mobile Alliance, "Open Mobile Alliance, "Policy
              Evaluation, Enforcement and Management Requirements",
              Candidate Version 1.0, 12 January 2005, available at
              http://www.openmobilealliance.org", November 2005.

   [PEEM-AD]  Open Mobile Alliance, "Open Mobile Alliance, "Policy
              Evaluation, Enforcement and Management Architecture",
              Draft Version 1.0, available at
              http://www.openmobilealliance.org", June 2006.

   [PEM-1-TS]
              Open Mobile Alliance, "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-20071205-D.zip", November 2007.


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.com





Brenner                   Expires June 17, 2008                 [Page 5]

Internet-Draft                    PEEM                     December 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   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).





Brenner                   Expires June 17, 2008                 [Page 6]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/