Policy Quality of Service (QoS) Information Model
RFC 3644

Document Type RFC - Proposed Standard (November 2003; No errata)
Last updated 2015-10-14
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3644 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Bert Wijnen
IESG note Published as RFC 3644
Send notices to <joel@stevecrocker.com>
Network Working Group                                            Y. Snir
Request for Comments: 3644                                    Y. Ramberg
Category: Standards Track                                  Cisco Systems
                                                            J. Strassner
                                                              Intelliden
                                                                R. Cohen
                                                               Ntear LLC
                                                                B. Moore
                                                                     IBM
                                                           November 2003

           Policy Quality of Service (QoS) Information Model

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   This document presents an object-oriented information model for
   representing Quality of Service (QoS) network management policies.
   This document is based on the IETF Policy Core Information Model and
   its extensions.  It defines an information model for QoS enforcement
   for differentiated and integrated services using policy.  It is
   important to note that this document defines an information model,
   which by definition is independent of any particular data storage
   mechanism and access protocol.

Snir, et al.                Standards Track                     [Page 1]
RFC 3644              Policy QoS Information Model         November 2003

Table of Contents

   1.   Introduction. . . . . . . . . . . . . . . . . . . . . . . . .  5
        1.1.  The Process of QoS Policy Definition. . . . . . . . . .  5
        1.2.  Design Goals and Their Ramifications. . . . . . . . . .  8
              1.2.1.  Policy-Definition Oriented. . . . . . . . . . .  8
                      1.2.1.1.  Rule-based Modeling . . . . . . . . .  9
                      1.2.1.2.  Organize Information Hierarchically .  9
                      1.2.1.3.  Goal-Oriented Policy Definition . . . 10
              1.2.2. Policy Domain Model. . . . . . . . . . . . . . . 11
                      1.2.2.1.  Model QoS Policy in a Device- and
                                Vendor-Independent Manner . . . . . . 11
                      1.2.2.2.  Use Roles for Mapping Policy to
                                Network Devices . . . . . . . . . . . 11
                      1.2.2.3.  Reusability . . . . . . . . . . . . . 12
              1.2.3.  Enforceable Policy. . . . . . . . . . . . . . . 12
              1.2.4.  QPIM Covers Both Signaled And Provisioned QoS . 14
              1.2.5.  Interoperability for PDPs and Management
                      Applications. . . . . . . . . . . . . . . . . . 14
        1.3.  Modeling Abstract QoS Policies. . . . . . . . . . . . . 15
        1.4.  Rule Hierarchy. . . . . . . . . . . . . . . . . . . . . 17
              1.4.1.  Use of Hierarchy Within Bandwidth Allocation
                      Policies. . . . . . . . . . . . . . . . . . . . 17
              1.4.2.  Use of Rule Hierarchy to Describe Drop
                      Threshold Policies. . . . . . . . . . . . . . . 21
              1.4.3.  Restrictions of the Use of Hierarchy Within
                      QPIM. . . . . . . . . . . . . . . . . . . . . . 22
        1.5.  Intended Audiences. . . . . . . . . . . . . . . . . . . 23
   2.   Class Hierarchies . . . . . . . . . . . . . . . . . . . . . . 23
        2.1.  Inheritance Hierarchy . . . . . . . . . . . . . . . . . 23
        2.2.  Relationship Hierarchy. . . . . . . . . . . . . . . . . 26
   3.   QoS Actions . . . . . . . . . . . . . . . . . . . . . . . . . 26
        3.1.  Overview. . . . . . . . . . . . . . . . . . . . . . . . 26
        3.2.  RSVP Policy Actions . . . . . . . . . . . . . . . . . . 27
              3.2.1.  Example: Controlling COPS Stateless Decision. . 28
              3.2.2.  Example: Controlling the COPS Replace Decision. 29
        3.3.  Provisioning Policy Actions . . . . . . . . . . . . . . 29
              3.3.1.  Admission Actions: Controlling Policers and
                      Shapers . . . . . . . . . . . . . . . . . . . . 29
              3.3.2.  Controlling Markers . . . . . . . . . . . . . . 32
              3.3.3.  Controlling Edge Policies - Examples. . . . . . 33
        3.4.  Per-Hop Behavior Actions. . . . . . . . . . . . . . . . 34
              3.4.1.  Controlling Bandwidth and Delay . . . . . . . . 35
              3.4.2.  Congestion Control Actions. . . . . . . . . . . 35
              3.4.3.  Using Hierarchical Policies: Examples for PHB
Show full document text