(file) Return to CIM_QoSService.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Network

Diff for /pegasus/Schemas/CIM231/DMTF/Network/CIM_QoSService.mof between version 1.1.2.1 and 1.1.2.2

version 1.1.2.1, 2012/01/24 13:50:20 version 1.1.2.2, 2012/02/15 17:46:37
Line 0 
Line 1 
   // Copyright (c) 2005 DMTF.  All rights reserved.
   // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
   // qualifier values to CIM Schema.</change>
   // ==================================================================
   //  CIM_QoSService
   // ==================================================================
      [Version ( "2.7.0" ),
       UMLPackagePath ( "CIM::Network::QoS" ),
       Description (
          "This is a concrete class that represents the ability to "
          "conceptualize a QoS service as a set of coordinated "
          "sub-services. This enables the network administrator to map "
          "business rules to the network, and the network designer to "
          "engineer the network such that it can provide different "
          "functions for different traffic streams. \n"
          "\n"
          "This class has two main purposes. First, it serves as a common "
          "base class for defining various sub-services that are needed "
          "to build higher-level QoS services. Second, it serves as a way "
          "to consolidate relationships between different types of QoS "
          "services and different types of ConditioningServices. \n"
          "\n"
          "For example, Gold Service may be defined as a QoSService which "
          "aggregates two other QoSServices together. Each of these "
          "\'other\' QoSServices could be DiffServServices - one "
          "representing the servicing of very high demand packets "
          "(instantiated as a DiffServService directly), and one "
          "representing the service given to most of the packets "
          "(instantiated as an AFService). The high demand "
          "DiffServService instance would use QoSConditioning SubService "
          "to aggregate together the necessary classifiers to indicate "
          "which traffic it applies to, the appropriate meters for "
          "contract limits, the marker to mark the EF PHB in the packets, "
          "and the queuing-related services. The AFService instance would "
          "similarly use QoSConditioning SubService to aggregate its "
          "classifiers, meters, the several markers used to mark the "
          "different AF PHBs in the packets, and the queuing-related "
          "services needed to deliver the packet treatment." )]
   class CIM_QoSService : CIM_Service {
   
   
   };


Legend:
Removed from v.1.1.2.1  
changed lines
  Added in v.1.1.2.2

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2