Diameter Predicted Units
draft-bertz-dime-predictunits-02

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                                                    Sprint
Intended status: Standards Track                           June 29, 2017
Expires: December 31, 2017

                        Diameter Predicted Units
                    draft-bertz-dime-predictunits-02

Abstract

   This document specifies the conveyance of predicted usage information
   for proper dimensioning of network services that use Diameter based
   authorization.

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.

Bertz                   Expires December 31, 2017               [Page 1]
Internet-Draft          Diameter Predicted Units               June 2017

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Predicted Service AVPs  . . . . . . . . . . . . . . . . . . .   3
     3.1.  Predicted-Service-Units . . . . . . . . . . . . . . . . .   3
     3.2.  Predicted-Service-Units-Series  . . . . . . . . . . . . .   4
   4.  Usage Examples  . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   When a User is authorized to use a service via Diameter applications
   such as [RFC4006] or [RFC7155], the Client is not aware of the
   average load placed upon it by the User.  This can lead to overload
   situations or Diameter Clients being too conservative and denying
   services to valid Users even whose presence would not overload the
   service.

   Given virtualization and the use of many software based services the
   service capacity varies on a service instance, i.e. Diameter Client,
   basis.  Even though the Diameter Client is the same softawre it will
   vary in terms of the load it can accept.  Thus, a Diameter Server
   cannot depend upon consistent capacities of a Diameter Client.

   This specification introduces the Predicted-Service-Units Attribute
   Value Pair (AVP).  This information conveys the predicted usage
   introduced on the service by the authorized User.  Such information
   can be used by the Diameter Client to estimate future load and
   proactively manage its resources.

Bertz                   Expires December 31, 2017               [Page 2]
Show full document text