| 1 |
<pre>Network Working Group H. Hazewinkel, Ed. |
| 2 |
Request for Comments: 3747 I.Net |
| 3 |
Category: Standards Track D. Partain, Ed. |
| 4 |
Ericsson |
| 5 |
April 2004 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">The Differentiated Services Configuration MIB</span> |
| 9 |
|
| 10 |
Status of this Memo |
| 11 |
|
| 12 |
This document specifies an Internet standards track protocol for the |
| 13 |
Internet community, and requests discussion and suggestions for |
| 14 |
improvements. Please refer to the current edition of the "Internet |
| 15 |
Official Protocol Standards" (STD 1) for the standardization state |
| 16 |
and status of this protocol. Distribution of this memo is unlimited. |
| 17 |
|
| 18 |
Copyright Notice |
| 19 |
|
| 20 |
Copyright (C) The Internet Society (2004). All Rights Reserved. |
| 21 |
|
| 22 |
Abstract |
| 23 |
|
| 24 |
This memo describes a MIB module that provides a conceptual layer |
| 25 |
between high-level "network-wide" policy definitions that effect |
| 26 |
configuration of the Differentiated Services (diffserv) subsystem and |
| 27 |
the instance-specific information that would include such details as |
| 28 |
the parameters for all the queues associated with each interface in a |
| 29 |
system. This essentially provides an interface for configuring |
| 30 |
differentiated services at a conceptually higher layer than that of |
| 31 |
the Differentiated Services MIB. |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. The Internet-Standard Management Framework . . . . . . . . . . <a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 61 |
<a href="#section-3">3</a>. Other Documents. . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 62 |
<a href="#section-4">4</a>. Relationship to other MIBs . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 63 |
<a href="#section-4.1">4.1</a>. The Policy-based Management MIB Module . . . . . . . . . <a href="#page-3">3</a> |
| 64 |
<a href="#section-4.2">4.2</a>. The Differentiated Services MIB Module . . . . . . . . . <a href="#page-4">4</a> |
| 65 |
<a href="#section-5">5</a>. The Differentiated Services Configuration MIB Module Design. . <a href="#page-5">5</a> |
| 66 |
<a href="#section-6">6</a>. Template Cloning . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 67 |
<a href="#section-6.1">6.1</a>. An Approach to Template Cloning. . . . . . . . . . . . . <a href="#page-6">6</a> |
| 68 |
<a href="#section-6.2">6.2</a>. Example. . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 69 |
<a href="#section-6.2.1">6.2.1</a>. The Initial Situation. . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 70 |
<a href="#section-6.2.2">6.2.2</a>. The Configuration Template . . . . . . . . . . . <a href="#page-9">9</a> |
| 71 |
<a href="#section-6.2.3">6.2.3</a>. Applying the Template. . . . . . . . . . . . . . <a href="#page-11">11</a> |
| 72 |
<a href="#section-6.2.4">6.2.4</a>. Applying the Template Using SNMP Messages. . . . <a href="#page-14">14</a> |
| 73 |
<a href="#section-7">7</a>. Managed Objects Definitions (MIB Module) . . . . . . . . . . . <a href="#page-15">15</a> |
| 74 |
<a href="#section-8">8</a>. Security Considerations. . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 75 |
<a href="#section-9">9</a>. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 76 |
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 77 |
<a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-22">22</a> |
| 78 |
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 79 |
<a href="#section-11">11</a>. Editors' Addresses . . . . . . . . . . . . . . . . . . . . . . <a href="#page-23">23</a> |
| 80 |
<a href="#section-12">12</a>. Full Copyright Statement . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a> |
| 81 |
|
| 82 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The Internet-Standard Management Framework</span> |
| 83 |
|
| 84 |
For a detailed overview of the documents that describe the current |
| 85 |
Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section 7 of |
| 86 |
RFC 3410</a> [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>]. |
| 87 |
|
| 88 |
Managed objects are accessed via a virtual information store, termed |
| 89 |
the Management Information Base or MIB. MIB objects are generally |
| 90 |
accessed through the Simple Network Management Protocol (SNMP). |
| 91 |
Objects in the MIB are defined using the mechanisms defined in the |
| 92 |
Structure of Management Information (SMI). This memo specifies a MIB |
| 93 |
module that is compliant to the SMIv2, which is described in STD 58, |
| 94 |
<a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC 2580</a> |
| 95 |
[<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>]. |
| 96 |
|
| 97 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Introduction</span> |
| 98 |
|
| 99 |
This memo defines a MIB module that can be used to convey management |
| 100 |
information about desired network-wide Differentiated Services based |
| 101 |
policy behavior. This module is designed to integrate with the |
| 102 |
Differentiated Services MIB module [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>] in order to provide |
| 103 |
template configurations for the Differentiated Services MIB module. |
| 104 |
The MIB module defined in this memo (the DIFFSERV-CONFIG-MIB) may be |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 111 |
|
| 112 |
|
| 113 |
used in combination with the Policy-based Management MIB module |
| 114 |
[<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>], but that is not a requirement. Without the Policy-based |
| 115 |
Management MIB module, a management application must emulate behavior |
| 116 |
provided by the Policy-based Management MIB using equivalent "low- |
| 117 |
level" SNMP operations in normal manager/agent communication. |
| 118 |
|
| 119 |
Together, this memo, [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>], and [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>] represent an instance |
| 120 |
of an integrated architecture for both device-specific and network- |
| 121 |
wide policy (configuration) management, which is fully integrated |
| 122 |
with the Internet Standard Management Framework. |
| 123 |
|
| 124 |
The Differentiated Services MIB module [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>] operates on a device |
| 125 |
level. The MIB module in this memo, the DIFFSERV-CONFIG-MIB, creates |
| 126 |
a coherent configuration management view as an umbrella over |
| 127 |
[<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>]. That is, the DIFFSERV-CONFIG-MIB provides a conceptual |
| 128 |
Application Program Interface (API) for configuration of the |
| 129 |
Differentiated Services parameters. Since the Differentiated |
| 130 |
Services MIB module is able to maintain configuration information, |
| 131 |
the DIFFSERV-CONFIG-MIB configuration API consists only of |
| 132 |
configuration template information and the start of the so-called |
| 133 |
functional datapath. |
| 134 |
|
| 135 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Other Documents</span> |
| 136 |
|
| 137 |
It is assumed that the reader is familiar with Differentiated |
| 138 |
Services ([<a href="./rfc2474" title=""Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers"">RFC2474</a>] and [<a href="./rfc2475" title=""An Architecture for Differentiated Services"">RFC2475</a>]), the Policy-based Management MIB |
| 139 |
([<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>]), and "Configuring Networks and Devices With SNMP" |
| 140 |
([<a href="./rfc3512" title=""Configuring Networks and Devices with Simple Network Management Protocol (SNMP)"">RFC3512</a>]). These documents include all of the necessary |
| 141 |
terminology for understanding this memo. However, note that use of |
| 142 |
the MIB module in this memo does not require the use of [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>]. |
| 143 |
[<a href="./rfc3512" title=""Configuring Networks and Devices with Simple Network Management Protocol (SNMP)"">RFC3512</a>] also provides an example MIB module which may help in |
| 144 |
understanding the relationship between DIFFSERV-CONFIG-MIB and the |
| 145 |
Differentiated Services MIB in [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>]. |
| 146 |
|
| 147 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Relationship to other MIBs</span> |
| 148 |
|
| 149 |
In this section, we describe the relationship of this MIB module to |
| 150 |
other MIB modules. The overall architecture used for policy |
| 151 |
configuration management is described in [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>]. |
| 152 |
|
| 153 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. The Policy-based Management MIB Module</span> |
| 154 |
|
| 155 |
[<a id="ref-PMMIBDR">PMMIBDR</a>] defines a MIB module that enables policy-based |
| 156 |
configuration management of infrastructure using the Internet |
| 157 |
Standard Management Framework. The document includes a table for |
| 158 |
configuring policies to be implemented, tables for storing the roles |
| 159 |
of elements on a particular device, a table for representing the |
| 160 |
capabilities of a device with respect to policy management, a table |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 167 |
|
| 168 |
|
| 169 |
for referencing elements affected by a policy, as well as other |
| 170 |
infrastructure. There is no requirement that [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>] be used in |
| 171 |
conjunction with the MIB module defined in this memo. |
| 172 |
|
| 173 |
See [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>] for a full description of the policy-based |
| 174 |
configuration framework it provides. |
| 175 |
|
| 176 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. The Differentiated Services MIB Module</span> |
| 177 |
|
| 178 |
The Differentiated Services MIB module [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>] provides a common |
| 179 |
set of managed objects useful for configuring Differentiated Services |
| 180 |
parameters on a Differentiated Services capable device. This is what |
| 181 |
is referred to as instance-level configuration. It is the alteration |
| 182 |
of the instance-level information in that MIB module which may be |
| 183 |
done using the objects in the MIB module defined in this memo. |
| 184 |
|
| 185 |
It is recognized that vendors may include additional managed objects |
| 186 |
in their devices (via vendor-specific MIB modules) for configuring |
| 187 |
Differentiated Services parameters. If a vendor chooses to use the |
| 188 |
objects defined in this memo for configuration, the vendor should |
| 189 |
provide additional managed objects in a similar approach as defined |
| 190 |
for the Differentiated Services MIB module. |
| 191 |
|
| 192 |
Since the managed objects of the Differentiated Services MIB |
| 193 |
[<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>] are not directly associated with an instance (interface and |
| 194 |
interface direction), the same managed objects can be used for |
| 195 |
traffic treatment configuration templates in a Differentiated |
| 196 |
Services capable device and can then be applied on multiple |
| 197 |
instances. Therefore, the tables as defined in the Differentiated |
| 198 |
Services MIB can be used directly for template configuration |
| 199 |
purposes. Those tables are: |
| 200 |
|
| 201 |
- diffServClfrTable |
| 202 |
- diffServClfrElementTable |
| 203 |
- diffServMultiFieldClfrTable |
| 204 |
- diffServMeterTable |
| 205 |
- diffServTBParamTable |
| 206 |
- diffServActionTable |
| 207 |
- diffServDscpMarkActTable |
| 208 |
- diffServCountActTable |
| 209 |
- diffServAlgDropTable |
| 210 |
- diffServRandomDropTable |
| 211 |
- diffServQTable |
| 212 |
- diffServSchedulerTable |
| 213 |
- diffServMinRateTable |
| 214 |
- diffServMaxRateTable |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 223 |
|
| 224 |
|
| 225 |
Readers familiar with the Differentiated Services MIB will notice |
| 226 |
that these are all templates. Only the diffServDataPathTable defines |
| 227 |
a managed instance for Differentiated Services traffic treatment by |
| 228 |
its indexes of the interface and its direction. This also allows the |
| 229 |
tables mentioned above to be used as a configuration template without |
| 230 |
defining anything directly related to a managed instance. |
| 231 |
|
| 232 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The Differentiated Services Configuration MIB Module Design</span> |
| 233 |
|
| 234 |
The Differentiated Services Configuration MIB module (in this memo) |
| 235 |
of the SNMP-based configuration management framework is positioned |
| 236 |
between the Policy-based Management MIB module and the instance- |
| 237 |
specific Differentiated Services MIB module as described above. |
| 238 |
|
| 239 |
The MIB module found in this memo is designed to maintain |
| 240 |
configuration templates for the Differentiated Services MIB [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>] |
| 241 |
module. The module only has a template table that describes a |
| 242 |
Differentiated Services traffic treatment by providing the starting |
| 243 |
pointer of the functional datapath. The templates represent a |
| 244 |
specific configuration of traffic treatment in a functional datapath |
| 245 |
of a Differentiated Services capable device. To avoid duplication of |
| 246 |
managed objects, the actual templates defining the functional |
| 247 |
datapath are defined in the Differentiated Services MIB module. |
| 248 |
These are also used for the management of the instances. Therefore, |
| 249 |
the implementation of the DIFFSERV-CONFIG-MIB module uses the tables |
| 250 |
defined in the Differentiated Services MIB. As soon as a |
| 251 |
configuration is made active via the POLICY-MANAGEMENT-MIB or using |
| 252 |
normal SNMP operations, the configuration defined within this MIB |
| 253 |
module will be instantiated in the DIFFSERV-MIB. |
| 254 |
|
| 255 |
Note that this is a conceptual process. That is, the configuration |
| 256 |
may not actually go through an API available in the subsystem which |
| 257 |
implements the DIFFSERV-MIB module. However, configuration via the |
| 258 |
DIFFSERV-CONFIG-MIB module will alter the same instrumentation as the |
| 259 |
DIFFSERV-MIB module whether it does it via the DIFFSERV-MIB module or |
| 260 |
not. |
| 261 |
|
| 262 |
The Differentiated Services Configuration MIB module only needs to |
| 263 |
define a starting point of a traffic treatment configuration |
| 264 |
template. This table is similar to the diffServDataPathTable |
| 265 |
[<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>]. However, it has a semantic difference in that the |
| 266 |
diffServDataPathTable is associated with an instance (interface and |
| 267 |
interface direction), whereas the diffServConfigTable in this memo is |
| 268 |
not. |
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 279 |
|
| 280 |
|
| 281 |
Unlike most MIB modules, changes to the managed objects in this MIB |
| 282 |
module do not cause a change in the external/traffic behavior of the |
| 283 |
device. This MIB module is used to set up per-hop-behavior |
| 284 |
configurations. As soon as configurations are made active via the |
| 285 |
POLICY-MANAGEMENT-MIB or SNMP operations, the configurations defined |
| 286 |
within this MIB module will be instantiated in the DIFFSERV-MIB. |
| 287 |
|
| 288 |
The only table in this MIB module is the diffServConfigTable, which |
| 289 |
provides managed objects for registering traffic treatment |
| 290 |
configurations used in differentiated services. The sole purpose of |
| 291 |
this table is to provide the starting point for a traffic treatment |
| 292 |
configuration template. The traffic treatment itself is performed by |
| 293 |
functional datapath elements [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>]. |
| 294 |
|
| 295 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Template Cloning</span> |
| 296 |
|
| 297 |
The concept of the DIFFSERV-CONFIG-MIB is based on having traffic |
| 298 |
treatment configuration templates. The templates provide a set of |
| 299 |
configuration values that provide a particular behavior, such as |
| 300 |
Expedited Forwarding traffic treatment, in the functional datapath. |
| 301 |
The template (or functional datapath) is similar to a linked list |
| 302 |
from a starting point and each (functional datapath) element is |
| 303 |
connected to the next element via the so-called next RowPointer. |
| 304 |
|
| 305 |
The moment a template is activated (instantiated) on an interface and |
| 306 |
its interface direction, the template needs to be copied/cloned, so |
| 307 |
that the template remains as a template. Note that the template is |
| 308 |
logically "locked" through the cloning process. That is, the |
| 309 |
template cannot be changed part way through the cloning process. |
| 310 |
With the exception of the indices, the cloned template will be |
| 311 |
identical to the source template. |
| 312 |
|
| 313 |
A literal copy/clone of the template is not possible, since the same |
| 314 |
indices inside the element tables cannot be re-used. The |
| 315 |
instantiation process must therefore generate a new index for each |
| 316 |
element. As a result of this, the 'NEXT' pointers also need to be |
| 317 |
updated. Otherwise, those will point to the template. |
| 318 |
|
| 319 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. An Approach to Template Cloning</span> |
| 320 |
|
| 321 |
What should a system containing Differentiated Services capabilities |
| 322 |
and Differentiated Services configuration capabilities do |
| 323 |
conceptually at the moment a template is activated on an interface? |
| 324 |
The following approach should not be considered implementation |
| 325 |
guidelines, but rather a conceptual explanation of what should be |
| 326 |
done. |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 335 |
|
| 336 |
|
| 337 |
1) Get the index of the template to be activated |
| 338 |
2) Get RowPointer (current) from |
| 339 |
diffServConfigStart.index |
| 340 |
of the diffServConfigTable |
| 341 |
3) Check if RowPointer (current) exists |
| 342 |
4) Logically "lock" the entry (current) pointed to by |
| 343 |
RowPointer so that its values are not changed part way |
| 344 |
through the cloning process. |
| 345 |
5) Copy/Clone the entry (current) pointed to by RowPointer |
| 346 |
a) Get a new index for the entry |
| 347 |
b) Configure the new entry with the values |
| 348 |
of the entry to be cloned |
| 349 |
c) Update the NEXT pointer with a new RowPointer |
| 350 |
that pointed to the previous entry that was copied |
| 351 |
part of this template |
| 352 |
6) Store RowPointer of cloned entry as (previous) in order to |
| 353 |
update the NEXT pointer with the next cloned entry. |
| 354 |
7) Get the RowPointer of the next element in the template |
| 355 |
as (current) |
| 356 |
8) If (current) RowPointer does not equal zeroDotZero go to 4 |
| 357 |
9) Logically "unlock" all the locked entries done by step 4). |
| 358 |
|
| 359 |
If a configuration/template is activated via a means other than a |
| 360 |
direct SNMP SET request, such as via the Policy-based Management MIB, |
| 361 |
the handling of the activation and potential error response code must |
| 362 |
be provided via that mechanism. If a configuration/template is |
| 363 |
activated using SNMP SET requests, an accurate error response value |
| 364 |
must be returned. For example, if a configuration/template has |
| 365 |
inconsistent values, the SNMP SET should return an error. Whether |
| 366 |
the configuration is already finished is not of direct importance, |
| 367 |
since the SNMP SET response must be accurate. On systems where the |
| 368 |
activation may take a long time, a response may be given prior to |
| 369 |
completion, but extra mechanisms must be provided to detect any |
| 370 |
errors. |
| 371 |
|
| 372 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Example</span> |
| 373 |
|
| 374 |
This section provides an example of the process described in the |
| 375 |
previous section. This example will show a Differentiated Services |
| 376 |
capable incoming (ingress) interface that only counts the traffic |
| 377 |
stream. Then, with the policy-based configuration concept as defined |
| 378 |
in this document and in [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>], a traffic marking configuration |
| 379 |
will be applied. The example will walk the reader through all of the |
| 380 |
steps involved in this process. Again, the use of [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>] is |
| 381 |
simply an example and is not required. |
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 391 |
|
| 392 |
|
| 393 |
NOTE WELL: For brevity and clarity, the example does not always |
| 394 |
show the complete entry (row) of a table. The only objects shown |
| 395 |
are those needed for creating the row pointers to the next |
| 396 |
functional datapath element or needed to provide information about |
| 397 |
the specific parameters of the functional datapath elements. The |
| 398 |
column named 'INDEX' always defines the complete index as defined |
| 399 |
for the associated entry. In some cases, this is a combined index |
| 400 |
of multiple components. Therefore, the names of the columns are |
| 401 |
omitted. |
| 402 |
|
| 403 |
Also note that the values Assured Forwarding and Expedited |
| 404 |
Forwarding are abstracted as DSCP(AF) and DSCP(EF) (respectively) |
| 405 |
or simply as AF and EF. For the actual values refer to [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>]. |
| 406 |
|
| 407 |
<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. The Initial Situation</span> |
| 408 |
|
| 409 |
The initial configuration is the existing configuration of an ingress |
| 410 |
interface. |
| 411 |
|
| 412 |
+------------------------------------------------------------+ |
| 413 |
| ingress functional datapath | |
| 414 |
| +----------+ | |
| 415 |
-->|----------->----------->| count |----------->----------->|--> |
| 416 |
| +----------+ | |
| 417 |
+------------------------------------------------------------+ |
| 418 |
|
| 419 |
This figure depicts a simple traffic treatment functional datapath |
| 420 |
for an ingress interface. The functional datapath only consists of a |
| 421 |
count action. |
| 422 |
|
| 423 |
Within the DIFFSERV-MIB, this would be instantiated as follows. Note |
| 424 |
that RowPointer objects must point to the first accessible columnar |
| 425 |
object in the conceptual row. Thus, while perhaps more instructive |
| 426 |
to use the index value for the RowPointer object's value (e.g., |
| 427 |
diffServCountActId.1) in the example, it would nonetheless be |
| 428 |
incorrect, and the first accessible columnar object has been used as |
| 429 |
should be done (e.g., diffServCountActOctets.1). |
| 430 |
|
| 431 |
diffServDataPathTable |
| 432 |
+-----------------+-----------------------------+-- |
| 433 |
| INDEX | diffServDataPathStart | |
| 434 |
+-----------------+-----------------------------+-- |
| 435 |
| ifIndex.ingress | diffServActionNext.1 | |
| 436 |
+-----------------+-----------------------------+-- |
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 447 |
|
| 448 |
|
| 449 |
diffServActionTable |
| 450 |
+-------+--------------------+-------------------------+-- |
| 451 |
| INDEX | diffServActionNext |diffServActionSpecific | |
| 452 |
+-------+--------------------+-------------------------+-- |
| 453 |
| 1 | 0.0 |diffServCountActOctets.1 | |
| 454 |
+-------+--------------------+-------------------------+-- |
| 455 |
|
| 456 |
diffServCountActTable |
| 457 |
+-------+------------------------+-- |
| 458 |
| INDEX | diffServCountActOctets | |
| 459 |
+-------+------------------------+-- |
| 460 |
| 1 | | |
| 461 |
+-------+------------------------+-- |
| 462 |
|
| 463 |
<span class="h4"><a class="selflink" id="section-6.2.2" href="#section-6.2.2">6.2.2</a>. The Configuration Template</span> |
| 464 |
|
| 465 |
The following provides an example of a policy configuration in which |
| 466 |
traffic is classified by a specific IP filter, that results in two |
| 467 |
classifiers (one for the IP filter and one for match all). Both |
| 468 |
streams are then metered, marked, and counted. This is an example of |
| 469 |
usage on the edge (an ingress interface) of a Differentiated Services |
| 470 |
domain that wants to have Expedited Forwarding and Assured Forwarding |
| 471 |
marked traffic within the Differentiated Services domain. |
| 472 |
|
| 473 |
+------------------------------------------------------------+ |
| 474 |
| ingress functional datapath | |
| 475 |
| +------------+ +-------+ +---------+ +---------+ | |
| 476 |
| | | | | | action: | | action: | | |
| 477 |
-->|-->| classifier |-->| meter |-->| mark EF |-->| count |-->|-----> |
| 478 |
| | match <IP> | | | | | | | | |
| 479 |
| +------------+ +-------+ +---------+ +---------+ | |
| 480 |
| | \ | |
| 481 |
| | \ +---------+ | |
| 482 |
| | \ | action: | |routing |
| 483 |
| | * -->| dropper | |core |
| 484 |
| | / | | | |
| 485 |
| | / +---------+ | |
| 486 |
| V / | |
| 487 |
| +------------+ +-------+ +---------+ +---------+ | |
| 488 |
| | | | | | action: | | action: | | |
| 489 |
| | classifier |-->| meter |-->| mark AF |-->| count |-->|-----> |
| 490 |
| | match all | | | | | | | | |
| 491 |
| +------------+ +-------+ +---------+ +---------+ | |
| 492 |
+------------------------------------------------------------+ |
| 493 |
|
| 494 |
This figure depicts a policy configuration for ingress traffic |
| 495 |
treatment in a Differentiated Services capable device. The |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 503 |
|
| 504 |
|
| 505 |
configuration is represented as follows in the DIFFSERV-CONFIG-MIB |
| 506 |
module and the DIFFSERV-MIB module. |
| 507 |
|
| 508 |
Note that the original (existing) traffic treatment described in |
| 509 |
6.2.1 is also in the tables. |
| 510 |
|
| 511 |
Note also that in the diffServDscpMarkActTable, DSCP(EF) represents |
| 512 |
the DSCP value for Expedited Forwarding and DSCP(AF) represents the |
| 513 |
DSCP value for Assured Forwarding. |
| 514 |
|
| 515 |
diffServConfigTable (in the MIB module in this memo) |
| 516 |
+-------+-------------------------+---------------------------+-- |
| 517 |
| INDEX | diffServConfigStart | diffServConfigDescr | |
| 518 |
+-------+-------------------------+---------------------------+-- |
| 519 |
| "foo" | diffServClfrStorage.1 | Example traffic treatment | |
| 520 |
+-------+-------------------------+---------------------------+-- |
| 521 |
|
| 522 |
diffServClfrTable |
| 523 |
+-------+---------------------+--------------------+ |
| 524 |
| INDEX | diffServClfrStorage | diffServClfrStatus | |
| 525 |
+-------+---------------------+--------------------+ |
| 526 |
| 1 | | | |
| 527 |
+-------+---------------------+--------------------+ |
| 528 |
|
| 529 |
diffServClfrElementTable (shares index with diffServClfrTable) |
| 530 |
+-------+---------------------------+-------------------------------+-- |
| 531 |
| INDEX | diffServClfrElementNext | diffServClfrElementPrecedence | |
| 532 |
+-------+---------------------------+-------------------------------+-- |
| 533 |
| 1.1 |diffServMeterSucceedNext.1 | 1 | |
| 534 |
| 1.2 |diffServMeterSucceedNext.2 | 2 | |
| 535 |
+-------+---------------------------+-------------------------------+-- |
| 536 |
|
| 537 |
diffServMeterTable |
| 538 |
+-------+--------------------------+-----------------------+-- |
| 539 |
| INDEX | diffServMeterSucceedNext |diffServMeterFailNext | |
| 540 |
+-------+--------------------------+-----------------------+-- |
| 541 |
| 1 | diffServActionNext.2 | diffServAlgDropType.1 | |
| 542 |
| 2 | diffServActionNext.3 | diffServAlgDropType.1 | |
| 543 |
+-------+--------------------------+-----------------------+-- |
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 559 |
|
| 560 |
|
| 561 |
diffServActionTable |
| 562 |
+-------+----------------------+----------------------------+-- |
| 563 |
| INDEX | diffServActionNext | diffServActionSpecific | |
| 564 |
+-------+----------------------+----------------------------+-- |
| 565 |
| 1 | 0.0 | diffServCountActOctets.1 | |
| 566 |
| 2 | diffServActionNext.4 | diffServDscpMarkActDscp.EF | |
| 567 |
| 3 | diffServActionNext.5 | diffServDscpMarkActDscp.AF | |
| 568 |
| 4 | 0.0 | diffServCountActOctets.2 | |
| 569 |
| 5 | 0.0 | diffServCountActOctets.3 | |
| 570 |
+-------+----------------------+----------------------------+-- |
| 571 |
|
| 572 |
diffServCountActTable |
| 573 |
+-------+------------------------+-- |
| 574 |
| INDEX | diffServCountActOctets | |
| 575 |
+-------+------------------------+-- |
| 576 |
| 1 | | |
| 577 |
| 2 | | |
| 578 |
| 3 | | |
| 579 |
+-------+------------------------+-- |
| 580 |
|
| 581 |
diffServAlgDropTable |
| 582 |
+-------+---------------------+-------------------------+-- |
| 583 |
| INDEX | diffServAlgDropType | diffServAlgDropSpecific | |
| 584 |
+-------+---------------------+-------------------------+-- |
| 585 |
| 1 | alwaysDrop(5) | 0.0 | |
| 586 |
+-------+---------------------+-------------------------+-- |
| 587 |
|
| 588 |
diffServDscpMarkActTable |
| 589 |
+-------------------------+ |
| 590 |
| diffServDscpMarkActDscp | |
| 591 |
+-------------------------+ |
| 592 |
| DSCP(EF) | |
| 593 |
| DSCP(AF) | |
| 594 |
+-------------------------+ |
| 595 |
|
| 596 |
<span class="h4"><a class="selflink" id="section-6.2.3" href="#section-6.2.3">6.2.3</a>. Applying the Template</span> |
| 597 |
|
| 598 |
Now we have the original ingress interface configuration and the |
| 599 |
policy configuration we want to apply to the actual interface. |
| 600 |
|
| 601 |
The example policy must provide the required Differentiated Services |
| 602 |
traffic treatment to all interfaces used by system administrators. |
| 603 |
The traffic treatment required is described in 6.2.2 above. |
| 604 |
|
| 605 |
Therefore, we have the following example policy which is configured |
| 606 |
via the POLICY-BASED-MANAGEMENT-MIB module (see [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>]): |
| 607 |
|
| 608 |
if ( roleMatch("Administrator") ) |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 615 |
|
| 616 |
|
| 617 |
then |
| 618 |
/* |
| 619 |
* The $0 gets the "element" returned from the previous |
| 620 |
* statement. the .1 at the end is the ingress interface |
| 621 |
* This sets, for example, diffServDataPathStart.3.1 to be |
| 622 |
* "diffServConfigStart.3.f.o.o" if interface 3 has the role |
| 623 |
* "Administrator". |
| 624 |
*/ |
| 625 |
setVar("diffServDataPathStart.$0.1", |
| 626 |
"diffServConfigStart.3.f.o.o", Oid) |
| 627 |
|
| 628 |
For our purposes, we only apply this on the inbound (ingress) |
| 629 |
direction of the interface. |
| 630 |
|
| 631 |
Note that although object descriptors are used in this PolicyScript |
| 632 |
example, the object identifiers must be used in the running script. |
| 633 |
For more information on policies and their syntax refer to [<a href="#ref-PMMIBDR" title=""Policy-based Management MIB"">PMMIBDR</a>]. |
| 634 |
|
| 635 |
The following tables in this section provide the cloned entries in |
| 636 |
the tables of the DIFFSERV-MIB module. All tables may have columns |
| 637 |
that contain contents or administrative objects that are not shown. |
| 638 |
These columns do not determine a function in the datapath and they |
| 639 |
are not shown for clarity of the cloning mechanism. |
| 640 |
|
| 641 |
Note that the original (existing) traffic treatment of 6.2.1 and |
| 642 |
6.2.2 are also in the tables. |
| 643 |
|
| 644 |
diffServConfigTable |
| 645 |
+-------+-------------------------+---------------------------+-- |
| 646 |
| INDEX | diffServConfigStart | diffServConfigDescr | |
| 647 |
+-------+-------------------------+---------------------------+-- |
| 648 |
| "foo" | diffServClfrStorage.1 | Example traffic treatment | |
| 649 |
+-------+-------------------------+---------------------------+-- |
| 650 |
|
| 651 |
diffServDataPathTable |
| 652 |
+-----------------+-----------------------------+-- |
| 653 |
| INDEX | diffServDataPathStart | |
| 654 |
+-----------------+-----------------------------+-- |
| 655 |
| ifIndex.ingress | diffServActionNext.2 | |
| 656 |
+-----------------+-----------------------------+-- |
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 671 |
|
| 672 |
|
| 673 |
diffServClfrTable |
| 674 |
+-------+---------------------+--------------------+ |
| 675 |
| INDEX | diffServClfrStorage | diffServClfrStatus | |
| 676 |
+-------+---------------------+--------------------+ |
| 677 |
| 1 | | | |
| 678 |
| 2 | | | |
| 679 |
+-------+---------------------+--------------------+ |
| 680 |
|
| 681 |
diffServClfrElementTable |
| 682 |
+-------+----------------------------+-------------------------------+-- |
| 683 |
| INDEX | diffServClfrElementNext | diffServClfrElementPrecedence | |
| 684 |
+-------+----------------------------+-------------------------------+-- |
| 685 |
| 1.1 | diffServMeterSucceedNext.1 | 1 | |
| 686 |
| 1.2 | diffServMeterSucceedNext.2 | 2 | |
| 687 |
| 2.3 | diffServMeterSucceedNext.3 | 1 | |
| 688 |
| 2.4 | diffServMeterSucceedNext.4 | 2 | |
| 689 |
+-------+----------------------------+-------------------------------+-- |
| 690 |
|
| 691 |
diffServMeterTable |
| 692 |
+-------+--------------------------+-----------------------+-- |
| 693 |
| INDEX | diffServMeterSucceedNext | diffServMeterFailNext | |
| 694 |
+-------+--------------------------+-----------------------+-- |
| 695 |
| 1 | diffServActionNext.2 | diffServAlgDropType.1 | |
| 696 |
| 2 | diffServActionNext.3 | diffServAlgDropType.1 | |
| 697 |
| 3 | diffServActionNext.6 | diffServAlgDropType.2 | |
| 698 |
| 4 | diffServActionNext.7 | diffServAlgDropType.2 | |
| 699 |
+-------+--------------------------+-----------------------+-- |
| 700 |
|
| 701 |
diffServActionTable |
| 702 |
+-------+----------------------+----------------------------+-- |
| 703 |
| INDEX | diffServActionNext | diffServActionSpecific | |
| 704 |
+-------+----------------------+----------------------------+-- |
| 705 |
| 1 | 0.0 | diffServCountActOctets.1 | |
| 706 |
| 2 | diffServActionNext.4 | diffServDscpMarkActDscp.EF | |
| 707 |
| 3 | diffServActionNext.5 | diffServDscpMarkActDscp.AF | |
| 708 |
| 4 | 0.0 | diffServCountActOctets.2 | |
| 709 |
| 5 | 0.0 | diffServCountActOctets.3 | |
| 710 |
| 6 | diffServActionNext.8 | diffServDscpMarkActDscp.EF | |
| 711 |
| 7 | diffServActionNext.9 | diffServDscpMarkActDscp.AF | |
| 712 |
| 8 | 0.0 | diffServCountActOctets.4 | |
| 713 |
| 9 | 0.0 | diffServCountActOctets.5 | |
| 714 |
+-------+----------------------+----------------------------+-- |
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 727 |
|
| 728 |
|
| 729 |
diffServCountActTable |
| 730 |
+-------+------------------------+-- |
| 731 |
| INDEX | diffServActCountOctets | |
| 732 |
+-------+------------------------+-- |
| 733 |
| 1 | | |
| 734 |
| 2 | | |
| 735 |
| 3 | | |
| 736 |
| 4 | | |
| 737 |
| 5 | | |
| 738 |
+-------+------------------------+-- |
| 739 |
|
| 740 |
diffServAlgDropTable |
| 741 |
+-------+---------------------+-------------------------+-- |
| 742 |
| INDEX | diffServAlgDropType | diffServAlgDropSpecific | |
| 743 |
+-------+---------------------+-------------------------+-- |
| 744 |
| 1 | alwaysDrop(5) | 0.0 | |
| 745 |
+-------+---------------------+-------------------------+-- |
| 746 |
|
| 747 |
diffServDscpMarkActTable |
| 748 |
+-------------------------+ |
| 749 |
| diffServDscpMarkActDscp | |
| 750 |
+-------------------------+ |
| 751 |
| DSCP(EF) | |
| 752 |
| DSCP(AF) | |
| 753 |
+-------------------------+ |
| 754 |
|
| 755 |
As one can see in the example, the main elements from which a |
| 756 |
functional datapath is constructed are duplicated/copied/cloned. |
| 757 |
That process is needed in order to preserve the policy configuration |
| 758 |
for reuse at a later time. |
| 759 |
|
| 760 |
It is up to the SNMP agent to keep track of which network interfaces |
| 761 |
are under policy control and which policy rules are being used. This |
| 762 |
avoids duplication of policy enforcement. How the agent does this is |
| 763 |
an implementation issue. |
| 764 |
|
| 765 |
One can see that the old functional datapath configurations stay in |
| 766 |
the MIB module tables. It is up to the SNMP agent implementation to |
| 767 |
decide whether to delete stale entries or keep them. Garbage |
| 768 |
collection of stale entries is an implementation issue. |
| 769 |
|
| 770 |
<span class="h4"><a class="selflink" id="section-6.2.4" href="#section-6.2.4">6.2.4</a>. Applying the Template Using SNMP Messages</span> |
| 771 |
|
| 772 |
In this section, the above example is explained by using SNMP |
| 773 |
communication between the SNMP "manager" and the SNMP "agent". |
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 783 |
|
| 784 |
|
| 785 |
In order to apply the template to all interfaces that have a role |
| 786 |
match of "Administrator," the SNMP manager must have a list of the |
| 787 |
roles of the interface. This means the SNMP manager must do an |
| 788 |
SNMP-SET for all those interfaces. This is expressed in the |
| 789 |
following pseudo code function. |
| 790 |
|
| 791 |
set_template_if_administrator_interface( |
| 792 |
<interface_list>, <template_name> |
| 793 |
) { |
| 794 |
template_oid = SNMP-GET("diffServConfigStart.<template_name>"); |
| 795 |
foreach interface (<ifRole_list>) { |
| 796 |
if (interface.role == "Administrator") { |
| 797 |
SNMP-SET("diffServDataPathStart.$interface.1", |
| 798 |
Oid, template_oid); |
| 799 |
} |
| 800 |
} |
| 801 |
} |
| 802 |
|
| 803 |
For example, on a system with 3 interfaces, the following list would |
| 804 |
be known to the manager. The first value indicates the interface |
| 805 |
number (ifIndex) and the second value is its role. |
| 806 |
|
| 807 |
interface_list IF_LIST = { |
| 808 |
{ 1, ... , "Administrator", ... }, |
| 809 |
{ 2, ... , "User", ... }, |
| 810 |
{ 3, ... , "Administrator", ... } } |
| 811 |
|
| 812 |
This will result in the communication between a manager and agent of |
| 813 |
1 SNMP-GET and 2 SNMP-SETs: |
| 814 |
|
| 815 |
- SNMP-GET("diffServConfigStart.3.f.o.o") |
| 816 |
- SNMP-SET("diffServDataPathStart.1.1", Oid, "diffServActionNext.1") |
| 817 |
- SNMP-SET("diffServDataPathStart.3.1", Oid, "diffServActionNext.1") |
| 818 |
|
| 819 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Managed Objects Definitions (MIB Module)</span> |
| 820 |
|
| 821 |
DIFFSERV-CONFIG-MIB DEFINITIONS ::= BEGIN |
| 822 |
IMPORTS |
| 823 |
|
| 824 |
OBJECT-TYPE, MODULE-IDENTITY, |
| 825 |
zeroDotZero, mib-2 FROM SNMPv2-SMI -- [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>] |
| 826 |
|
| 827 |
RowStatus, StorageType, |
| 828 |
RowPointer, DateAndTime FROM SNMPv2-TC -- [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] |
| 829 |
|
| 830 |
MODULE-COMPLIANCE, |
| 831 |
OBJECT-GROUP FROM SNMPv2-CONF -- [<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>] |
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 839 |
|
| 840 |
|
| 841 |
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; -- [<a href="./rfc3411" title=""An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks"">RFC3411</a>] |
| 842 |
|
| 843 |
diffServConfigMib MODULE-IDENTITY |
| 844 |
LAST-UPDATED "200401220000Z" -- 22 January 2004 |
| 845 |
ORGANIZATION "SNMPCONF WG" |
| 846 |
CONTACT-INFO |
| 847 |
"SNMPCONF Working Group |
| 848 |
<a href="http://www.ietf.org/html.charters/snmpconf-charter.html">http://www.ietf.org/html.charters/snmpconf-charter.html</a> |
| 849 |
WG mailing list: [email protected] |
| 850 |
|
| 851 |
Editors: |
| 852 |
Harrie Hazewinkel |
| 853 |
I.Net |
| 854 |
via Darwin 85 |
| 855 |
20019 - Settimo Milanese (MI) |
| 856 |
Italy |
| 857 |
EMail: [email protected] |
| 858 |
|
| 859 |
David Partain |
| 860 |
Ericsson AB |
| 861 |
P.O. Box 1248 |
| 862 |
SE-581 12 Linkoping |
| 863 |
Sweden |
| 864 |
E-mail: [email protected]" |
| 865 |
DESCRIPTION |
| 866 |
"This MIB module contains differentiated services |
| 867 |
specific managed objects to perform higher-level |
| 868 |
configuration management. This MIB allows policies |
| 869 |
to use 'templates' to instantiate Differentiated |
| 870 |
Services functional datapath configurations to |
| 871 |
be assigned (associated with an interface and |
| 872 |
direction) when a policy is activated. |
| 873 |
|
| 874 |
Copyright (C) The Internet Society (2004). This version |
| 875 |
of this MIB module is part of <a href="./rfc3747">RFC 3747</a>; see the RFC |
| 876 |
itself for full legal notices." |
| 877 |
REVISION "200401220000Z" -- 22 January 2004 |
| 878 |
DESCRIPTION |
| 879 |
"Initial version published as <a href="./rfc3747">RFC 3747</a>" |
| 880 |
::= { mib-2 108 } |
| 881 |
|
| 882 |
diffServConfigMIBObjects OBJECT IDENTIFIER ::= { diffServConfigMib 1 } |
| 883 |
diffServConfigMIBConformance OBJECT IDENTIFIER ::= |
| 884 |
{ diffServConfigMib 2 } |
| 885 |
|
| 886 |
-- |
| 887 |
-- The Differentiated Services configuration objects |
| 888 |
-- |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 895 |
|
| 896 |
|
| 897 |
diffServConfigTable OBJECT-TYPE |
| 898 |
SYNTAX SEQUENCE OF DiffServConfigEntry |
| 899 |
MAX-ACCESS not-accessible |
| 900 |
STATUS current |
| 901 |
DESCRIPTION |
| 902 |
"A table which defines the various per-hop-behaviors |
| 903 |
for which the system has default 'templates'." |
| 904 |
::= { diffServConfigMIBObjects 2 } |
| 905 |
|
| 906 |
diffServConfigEntry OBJECT-TYPE |
| 907 |
SYNTAX DiffServConfigEntry |
| 908 |
MAX-ACCESS not-accessible |
| 909 |
STATUS current |
| 910 |
DESCRIPTION |
| 911 |
"An entry defining a per-hop-behavior. Each entry in |
| 912 |
this table combines the various parameters (entries) |
| 913 |
into a specific per-hop-behavior. Entries in this |
| 914 |
table might be defined by a vendor (pre-configured) |
| 915 |
or defined by a management application." |
| 916 |
INDEX { diffServConfigId } |
| 917 |
::= { diffServConfigTable 1 } |
| 918 |
|
| 919 |
DiffServConfigEntry ::= SEQUENCE { |
| 920 |
diffServConfigId SnmpAdminString, |
| 921 |
diffServConfigDescr SnmpAdminString, |
| 922 |
diffServConfigOwner SnmpAdminString, |
| 923 |
diffServConfigLastChange DateAndTime, |
| 924 |
diffServConfigStart RowPointer, |
| 925 |
diffServConfigStorage StorageType, |
| 926 |
diffServConfigStatus RowStatus |
| 927 |
} |
| 928 |
|
| 929 |
diffServConfigId OBJECT-TYPE |
| 930 |
SYNTAX SnmpAdminString (SIZE(1..116)) |
| 931 |
MAX-ACCESS not-accessible |
| 932 |
STATUS current |
| 933 |
DESCRIPTION |
| 934 |
"A unique id for the per-hop-behavior policy for at |
| 935 |
least the SNMP agent. For ease of administration the |
| 936 |
value may be unique within an administrative domain, |
| 937 |
but this is not required. |
| 938 |
|
| 939 |
The range of up to 116 octets is chosen to stay within |
| 940 |
the SMI limit of 128 sub-identifiers in an object |
| 941 |
identifier." |
| 942 |
::= { diffServConfigEntry 1 } |
| 943 |
|
| 944 |
diffServConfigDescr OBJECT-TYPE |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 951 |
|
| 952 |
|
| 953 |
SYNTAX SnmpAdminString |
| 954 |
MAX-ACCESS read-create |
| 955 |
STATUS current |
| 956 |
DESCRIPTION |
| 957 |
"A human-readable description to identify this defined |
| 958 |
per-hop-behavior. Note that this is an SnmpAdminString, |
| 959 |
which permits UTF-8 strings. An administratively assigned |
| 960 |
identifier for a template that would be unique within |
| 961 |
an administrative domain. It is up to the management |
| 962 |
applications to agree how these are assigned within the |
| 963 |
administrative domain. Once a description, such as |
| 964 |
'EF' is assigned, that has a certain set of parameters |
| 965 |
that achieve 'EF' from box to box. Management |
| 966 |
application code or script code can then scan |
| 967 |
the table to find the proper template and then |
| 968 |
assign it." |
| 969 |
::= { diffServConfigEntry 2 } |
| 970 |
|
| 971 |
diffServConfigOwner OBJECT-TYPE |
| 972 |
SYNTAX SnmpAdminString |
| 973 |
MAX-ACCESS read-create |
| 974 |
STATUS current |
| 975 |
DESCRIPTION |
| 976 |
"The owner who created this entry." |
| 977 |
::= { diffServConfigEntry 3 } |
| 978 |
|
| 979 |
diffServConfigLastChange OBJECT-TYPE |
| 980 |
SYNTAX DateAndTime |
| 981 |
MAX-ACCESS read-only |
| 982 |
STATUS current |
| 983 |
DESCRIPTION |
| 984 |
"The date and time when this entry was last changed." |
| 985 |
::= { diffServConfigEntry 4 } |
| 986 |
|
| 987 |
diffServConfigStart OBJECT-TYPE |
| 988 |
SYNTAX RowPointer |
| 989 |
MAX-ACCESS read-create |
| 990 |
STATUS current |
| 991 |
DESCRIPTION |
| 992 |
"The pointer to a functional datapath configuration template as |
| 993 |
set up in the DIFFSERV-MIB. This RowPointer should |
| 994 |
point to an instance of one of: |
| 995 |
diffServClfrEntry |
| 996 |
diffServMeterEntry |
| 997 |
diffServActionEntry |
| 998 |
diffServAlgDropEntry |
| 999 |
diffServQEntry |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
A value of zeroDotZero in this attribute indicates no |
| 1010 |
further Diffserv treatment is performed on traffic of |
| 1011 |
this functional datapath. This also means that the |
| 1012 |
template described by this row is not defined. |
| 1013 |
|
| 1014 |
If the row pointed to does not exist, the treatment |
| 1015 |
is as if this attribute contains a value of zeroDotZero." |
| 1016 |
REFERENCE |
| 1017 |
"Differentiated Services MIB module" |
| 1018 |
DEFVAL { zeroDotZero } |
| 1019 |
::= { diffServConfigEntry 5 } |
| 1020 |
|
| 1021 |
diffServConfigStorage OBJECT-TYPE |
| 1022 |
SYNTAX StorageType |
| 1023 |
MAX-ACCESS read-create |
| 1024 |
STATUS current |
| 1025 |
DESCRIPTION |
| 1026 |
"The type of storage used for this row. |
| 1027 |
|
| 1028 |
Since an entry in this table serves as a starting |
| 1029 |
point for a configuration, it is recommended that |
| 1030 |
all entries comprising the configuration started by |
| 1031 |
diffServConfigStart follow the storage type of this |
| 1032 |
entry. Otherwise, after agent reboots a configuration |
| 1033 |
may differ. It may very well be that the agent is |
| 1034 |
not capable of detecting such changes and therefore, |
| 1035 |
the management application should verify the correct |
| 1036 |
configuration after a reboot. Rows with a StorageType |
| 1037 |
of 'permanent' do not need to allow write access to |
| 1038 |
any of the columnar objects in that row." |
| 1039 |
DEFVAL { nonVolatile } |
| 1040 |
::= { diffServConfigEntry 6 } |
| 1041 |
|
| 1042 |
diffServConfigStatus OBJECT-TYPE |
| 1043 |
SYNTAX RowStatus |
| 1044 |
MAX-ACCESS read-create |
| 1045 |
STATUS current |
| 1046 |
DESCRIPTION |
| 1047 |
"RowStatus object used for creation and deletion of |
| 1048 |
rows in this table. All writable objects in this row |
| 1049 |
may be modified at any time." |
| 1050 |
DEFVAL { notInService } |
| 1051 |
::= { diffServConfigEntry 7 } |
| 1052 |
|
| 1053 |
-- |
| 1054 |
-- MIB Compliance statements. |
| 1055 |
-- |
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
diffServConfigMIBCompliances |
| 1066 |
OBJECT IDENTIFIER ::= { diffServConfigMIBConformance 1 } |
| 1067 |
diffServConfigMIBGroups |
| 1068 |
OBJECT IDENTIFIER ::= { diffServConfigMIBConformance 2 } |
| 1069 |
|
| 1070 |
diffServConfigMIBFullCompliance MODULE-COMPLIANCE |
| 1071 |
STATUS current |
| 1072 |
DESCRIPTION |
| 1073 |
"The full compliance for this MIB module. |
| 1074 |
|
| 1075 |
For this compliance level the 'diffServMIBFullCompliance' |
| 1076 |
must be met, since this MIB module depends on it in order |
| 1077 |
to provide the configuration entries. |
| 1078 |
" |
| 1079 |
MODULE -- This module |
| 1080 |
MANDATORY-GROUPS { diffServConfigMIBConfigGroup } |
| 1081 |
|
| 1082 |
OBJECT diffServConfigStatus |
| 1083 |
SYNTAX RowStatus { active(1) } |
| 1084 |
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } |
| 1085 |
DESCRIPTION |
| 1086 |
"Support for createAndWait and notInService is not required." |
| 1087 |
|
| 1088 |
::= { diffServConfigMIBCompliances 1 } |
| 1089 |
|
| 1090 |
diffServConfigMIBConfigGroup OBJECT-GROUP |
| 1091 |
OBJECTS { diffServConfigDescr, |
| 1092 |
diffServConfigOwner, |
| 1093 |
diffServConfigLastChange, |
| 1094 |
diffServConfigStart, |
| 1095 |
diffServConfigStorage, |
| 1096 |
diffServConfigStatus |
| 1097 |
} |
| 1098 |
STATUS current |
| 1099 |
DESCRIPTION |
| 1100 |
"The per-hop-behavior Group defines the MIB objects that |
| 1101 |
describe the configuration template for the per-hop-behavior." |
| 1102 |
::= { diffServConfigMIBGroups 1 } |
| 1103 |
END |
| 1104 |
|
| 1105 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span> |
| 1106 |
|
| 1107 |
There are a number of management objects defined in this MIB module |
| 1108 |
with a MAX-ACCESS clause of read-write and/or read-create. Such |
| 1109 |
objects may be considered sensitive or vulnerable in some network |
| 1110 |
environments. The support for SET operations in a non-secure |
| 1111 |
environment without proper protection can have a negative effect on |
| 1112 |
network operations. These managed objects are: |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
- The diffServConfigDescr, diffServConfigOwner, and |
| 1122 |
diffServConfigStatus are not security sensitive since these three |
| 1123 |
objects do not affect any direct operational behavior of a |
| 1124 |
diffserv capable device. |
| 1125 |
|
| 1126 |
- Unauthorized change of the diffServConfigStart could lead to a |
| 1127 |
different configuration, and the 'changed' configuration could |
| 1128 |
lead to different traffic treatment for the diffserv capable |
| 1129 |
device than desired. |
| 1130 |
|
| 1131 |
- Unauthorized change of the diffServConfigStorage could lead to |
| 1132 |
unknown behavior of the diffserv capable device after a reboot of |
| 1133 |
the SNMP agent. This may be caused by 'not having saved changes |
| 1134 |
of the configuration' or unavailable configurations. |
| 1135 |
|
| 1136 |
In addition, the managed objects of the DIFFSERV-MIB are also |
| 1137 |
security sensitive, since unauthorized changes may cause |
| 1138 |
configuration changes. For more detail, refer to [<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>]. |
| 1139 |
|
| 1140 |
Allowing read access to objects in this MIB module is generally not |
| 1141 |
considered sensitive, as read access only provides information that a |
| 1142 |
template exists. This is due to the fact that the managed objects |
| 1143 |
that actually instantiate the template are in the DIFFSERV-MIB |
| 1144 |
[<a href="./rfc3289" title=""Management Information Base for the Differentiated Services Architecture"">RFC3289</a>]. However, in environments where the template description |
| 1145 |
(diffServConfigDescr) or owner (diffServConfigOwner) is considered |
| 1146 |
sensitive information, appropriate access control should be exercised |
| 1147 |
for these objects. |
| 1148 |
|
| 1149 |
SNMP versions prior to SNMPv3 did not include adequate security. |
| 1150 |
Even if the network itself is secure (for example by using IPSec), |
| 1151 |
there is no control as to who on the secure network is allowed to |
| 1152 |
access and GET/SET (read/change/create/delete) the objects in this |
| 1153 |
MIB module. |
| 1154 |
|
| 1155 |
It is RECOMMENDED that implementers consider the security features as |
| 1156 |
provided by the SNMPv3 framework (see <a href="./rfc3410#section-8">[RFC3410], section 8</a>), |
| 1157 |
including full support for the SNMPv3 cryptographic mechanisms (for |
| 1158 |
authentication and privacy). |
| 1159 |
|
| 1160 |
Further, deployment of SNMP versions prior to SNMPv3 is NOT |
| 1161 |
RECOMMENDED. Instead, deployment of SNMPv3 with cryptographic |
| 1162 |
security enabled is RECOMMENDED. It is then a customer/operator |
| 1163 |
responsibility to ensure that the SNMP entity giving access to an |
| 1164 |
instance of this MIB module is properly configured to give access to |
| 1165 |
the objects only to those principals (users) that have legitimate |
| 1166 |
rights to GET or SET (change/create/delete) them. |
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span> |
| 1178 |
|
| 1179 |
The editors gratefully acknowledge the significant contributions to |
| 1180 |
this work made by several members of both the SNMPCONF and DiffServ |
| 1181 |
working groups. |
| 1182 |
|
| 1183 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span> |
| 1184 |
|
| 1185 |
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span> |
| 1186 |
|
| 1187 |
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Perkins, D. and J. Schoenwaelder, |
| 1188 |
"Structure of Management Information Version 2 (SMIv2)", |
| 1189 |
STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999. |
| 1190 |
|
| 1191 |
[<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual |
| 1192 |
Conventions for SMIv2", STD 58, <a href="./rfc2579">RFC 2579</a>, April 1999. |
| 1193 |
|
| 1194 |
[<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D. and J. Schoenwaelder, |
| 1195 |
"Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>, April |
| 1196 |
1999. |
| 1197 |
|
| 1198 |
[<a id="ref-RFC3289">RFC3289</a>] Baker, F., Chan, K. and A. Smith, "Management Information |
| 1199 |
Base for the Differentiated Services Architecture", <a href="./rfc3289">RFC</a> |
| 1200 |
<a href="./rfc3289">3289</a>, May 2002. |
| 1201 |
|
| 1202 |
[<a id="ref-RFC3411">RFC3411</a>] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture |
| 1203 |
for Describing Simple Network Management Protocol (SNMP) |
| 1204 |
Management Frameworks", STD 62, <a href="./rfc3411">RFC 3411</a>, December 2002. |
| 1205 |
|
| 1206 |
|
| 1207 |
|
| 1208 |
|
| 1209 |
|
| 1210 |
|
| 1211 |
|
| 1212 |
|
| 1213 |
|
| 1214 |
|
| 1215 |
|
| 1216 |
|
| 1217 |
|
| 1218 |
|
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span> |
| 1234 |
|
| 1235 |
[<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D. and B. Stewart, |
| 1236 |
"Introduction and Applicability Statements for Internet- |
| 1237 |
Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002. |
| 1238 |
|
| 1239 |
[<a id="ref-RFC2474">RFC2474</a>] Nichols, K., Blake, S., Baker, F. and D. Black, "Definition |
| 1240 |
of the Differentiated Services Field (DS Field) in the IPv4 |
| 1241 |
and IPv6 Headers", <a href="./rfc2474">RFC 2474</a>, December 1998. |
| 1242 |
|
| 1243 |
[<a id="ref-RFC2475">RFC2475</a>] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z. and |
| 1244 |
W. Weiss, "An Architecture for Differentiated Services", |
| 1245 |
<a href="./rfc2475">RFC 2475</a>, December 1998. |
| 1246 |
|
| 1247 |
[<a id="ref-RFC3512">RFC3512</a>] MacFaden, M., Partain, D., Saperia, J. and W. Tackabury, |
| 1248 |
"Configuring Networks and Devices with Simple Network |
| 1249 |
Management Protocol (SNMP)", <a href="./rfc3512">RFC 3512</a>, April 2003. |
| 1250 |
|
| 1251 |
[<a id="ref-PMMIBDR">PMMIBDR</a>] Waldbusser, S., Saperia, J. and T. Hongal, "Policy-based |
| 1252 |
Management MIB", Work in Progress. |
| 1253 |
|
| 1254 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Editors' Addresses</span> |
| 1255 |
|
| 1256 |
Harrie Hazewinkel |
| 1257 |
I.Net |
| 1258 |
via Darwin 85 |
| 1259 |
20019 - Settimo Milanese (MI) |
| 1260 |
Italy |
| 1261 |
|
| 1262 |
EMail: [email protected] |
| 1263 |
|
| 1264 |
|
| 1265 |
David Partain |
| 1266 |
Ericsson AB |
| 1267 |
P.O. Box 1248 |
| 1268 |
SE-581 12 Linkoping |
| 1269 |
Sweden |
| 1270 |
|
| 1271 |
EMail: [email protected] |
| 1272 |
|
| 1273 |
|
| 1274 |
|
| 1275 |
|
| 1276 |
|
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Hazewinkel & Partain Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc3747">RFC 3747</a> Differentiated Services Configuration MIB April 2004</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Full Copyright Statement</span> |
| 1290 |
|
| 1291 |
Copyright (C) The Internet Society (2004). This document is subject |
| 1292 |
to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and |
| 1293 |
except as set forth therein, the authors retain all their rights. |
| 1294 |
|
| 1295 |
This document and the information contained herein are provided on an |
| 1296 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 1297 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 1298 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 1299 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 1300 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 1301 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1302 |
|
| 1303 |
Intellectual Property |
| 1304 |
|
| 1305 |
The IETF takes no position regarding the validity or scope of any |
| 1306 |
Intellectual Property Rights or other rights that might be claimed to |
| 1307 |
pertain to the implementation or use of the technology described in |
| 1308 |
this document or the extent to which any license under such rights |
| 1309 |
might or might not be available; nor does it represent that it has |
| 1310 |
made any independent effort to identify any such rights. Information |
| 1311 |
on the procedures with respect to rights in RFC documents can be |
| 1312 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 1313 |
|
| 1314 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 1315 |
assurances of licenses to be made available, or the result of an |
| 1316 |
attempt made to obtain a general license or permission for the use of |
| 1317 |
such proprietary rights by implementers or users of this |
| 1318 |
specification can be obtained from the IETF on-line IPR repository at |
| 1319 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 1320 |
|
| 1321 |
The IETF invites any interested party to bring to its attention any |
| 1322 |
copyrights, patents or patent applications, or other proprietary |
| 1323 |
rights that may cover technology that may be required to implement |
| 1324 |
this standard. Please address the information to the IETF at ietf- |
| 1325 |
[email protected]. |
| 1326 |
|
| 1327 |
Acknowledgement |
| 1328 |
|
| 1329 |
Funding for the RFC Editor function is currently provided by the |
| 1330 |
Internet Society. |
| 1331 |
|
| 1332 |
|
| 1333 |
|
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
Hazewinkel & Partain Standards Track [Page 24] |
| 1341 |
</pre> |