Diameter Policy Groups and Sets
draft-bertz-dime-policygroups-03

Document Type Active Internet-Draft (individual)
Last updated 2017-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Diameter Maintenance and Extensions                             L. Bertz
Internet-Draft                                                  M. Bales
Intended status: Standards Track                                  Sprint
Expires: September 10, 2017                                March 9, 2017

                    Diameter Policy Groups and Sets
                    draft-bertz-dime-policygroups-03

Abstract

   This document defines optional Diameter attributes for efficient
   policy provisioning.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

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

   This Internet-Draft will expire on September 10, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November

Bertz & Bales          Expires September 10, 2017               [Page 1]
Internet-Draft       Diameter Policy Groups and Sets          March 2017

   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

1.  Introduction

   Policy applications often apply common policies to multiple
   authorized users.  Bulk operations are often applied through the use
   of group naming, e.g. 3GPP's use of Base Name.

   This document defines a grouping mechanism to apply common operations
   to a group of policies and a membership set that can be used to
   quickly apply one or more Diameter based policies, e.g.  Filter-Rule
   [RFC5777] to authorized users.

2.  Requirements Language

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

3.  Terminology

   Authorized Users  An Entity that has been authorized to use a service
      via a Diamater Application.

   Base Name  An organizational structure used to define a domain for
      multiple Policy Groups or Membership Domains.

   Determination Type  The matching policy applied, e.g.  ANDMASK, AND,
      etc, for Membership Determination.

   Policy Entity  A type that may be assigned to a Policy Group or
      Membership.  This includes but is not limited to Filters [RFC7155]
      or Filter-Rules [RFC5777].

   Membership Determination  The process by which Policy Entities are
      selected to be applied to an authorized User.

   Membership Domain  A name assigned to a Membership Set.

Bertz & Bales          Expires September 10, 2017               [Page 2]
Internet-Draft       Diameter Policy Groups and Sets          March 2017

   Membership Value  A binary set of values where each bit represents a
      specific membership pattern.

4.  Concepts

   Policy Groups represent a union of Policy Entities.  These entities
   MUST be of the same type, e.g.  Filters [RFC7155] or Filter-Rules
Show full document text