The Differentiated Services Configuration MIB
RFC 3747

Document Type RFC - Proposed Standard (April 2004; 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 3747 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Bert Wijnen
Send notices to (None)
Network Working Group                                 H. Hazewinkel, Ed.
Request for Comments: 3747                                         I.Net
Category: Standards Track                                D. Partain, Ed.
                                                                Ericsson
                                                              April 2004

             The Differentiated Services Configuration MIB

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 (2004).  All Rights Reserved.

Abstract

   This memo describes a MIB module that provides a conceptual layer
   between high-level "network-wide" policy definitions that effect
   configuration of the Differentiated Services (diffserv) subsystem and
   the instance-specific information that would include such details as
   the parameters for all the queues associated with each interface in a
   system.  This essentially provides an interface for configuring
   differentiated services at a conceptually higher layer than that of
   the Differentiated Services MIB.

Hazewinkel & Partain        Standards Track                     [Page 1]
RFC 3747       Differentiated Services Configuration MIB      April 2004

Table of Contents

   1.  The Internet-Standard Management Framework . . . . . . . . . .  2
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   3.  Other Documents. . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Relationship to other MIBs . . . . . . . . . . . . . . . . . .  3
       4.1.  The Policy-based Management MIB Module . . . . . . . . .  3
       4.2.  The Differentiated Services MIB Module . . . . . . . . .  4
   5.  The Differentiated Services Configuration MIB Module Design. .  5
   6.  Template Cloning . . . . . . . . . . . . . . . . . . . . . . .  6
       6.1.  An Approach to Template Cloning. . . . . . . . . . . . .  6
       6.2.  Example. . . . . . . . . . . . . . . . . . . . . . . . .  7
             6.2.1.  The Initial Situation. . . . . . . . . . . . . .  8
             6.2.2.  The Configuration Template . . . . . . . . . . .  9
             6.2.3.  Applying the Template. . . . . . . . . . . . . . 11
             6.2.4.  Applying the Template Using SNMP Messages. . . . 14
   7.  Managed Objects Definitions (MIB Module) . . . . . . . . . . . 15
   8.  Security Considerations. . . . . . . . . . . . . . . . . . . . 20
   9.  Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 22
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
       10.1. Normative References . . . . . . . . . . . . . . . . . . 22
       10.2. Informative References . . . . . . . . . . . . . . . . . 23
   11. Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23
   12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 24

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

2.  Introduction

   This memo defines a MIB module that can be used to convey management
   information about desired network-wide Differentiated Services based
   policy behavior.  This module is designed to integrate with the
   Differentiated Services MIB module [RFC3289] in order to provide
   template configurations for the Differentiated Services MIB module.
   The MIB module defined in this memo (the DIFFSERV-CONFIG-MIB) may be

Hazewinkel & Partain        Standards Track                     [Page 2]
RFC 3747       Differentiated Services Configuration MIB      April 2004

   used in combination with the Policy-based Management MIB module
   [PMMIBDR], but that is not a requirement.  Without the Policy-based
   Management MIB module, a management application must emulate behavior
   provided by the Policy-based Management MIB using equivalent "low-
   level" SNMP operations in normal manager/agent communication.

   Together, this memo, [RFC3289], and [PMMIBDR] represent an instance
   of an integrated architecture for both device-specific and network-
Show full document text