Diameter Policy Groups and Sets

Document Type Active Internet-Draft (individual)
Last updated 2017-06-29
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: December 31, 2017                                 June 29, 2017

                    Diameter Policy Groups and Sets


   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 December 31, 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 December 31, 2017               [Page 1]
Internet-Draft       Diameter Policy Groups and Sets           June 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

   As Users connect to a network, policy applications often apply common
   policies to them.  In some cases policies are grouped and applied
   through the use of AVPs, e.g. 3GPP Base Name.  Other options include
   sending identifiers, usually a list of integers, associated with
   rules to apply a group to a single user.  This compacts the over the
   wire representation but requires strong coordination between policy
   based Clients and Servers.

   Application of common policy if further limited when the filters
   overlap.  This requires partitioning policies into non-overlapping
   namespaces, e.g. tables in a Software Defined Networking (SDN)
   switch.  To reduce the need to partition sets of policies some SDN
   technologies, e.g.  OpenFlow, rely on metadata that is applied as
   part of the filter or metadata that is specific to the packet, e.g.
   OpenFlow Registers.

   This document defines grouping mechanisms to allow users or groups of
   users to share policies or groups of policies.  The mechanism also
   extends filters to include a metadata matching field that permits
   filters that overlap at the protocol level to coexist in the same
   policy enforcement space.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   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.

Bertz & Bales           Expires December 31, 2017               [Page 2]
Internet-Draft       Diameter Policy Groups and Sets           June 2017
Show full document text