Subject: [Policy] List of changes / open issues list for QDDIM-06

From: "Robert Moore" <[email-masked]>
Date: Thu, 29 Nov 2001 14:25:20 -0500

The draft:

QDDIM-06: draft-ietf-policy-qos-device-info-model-06.txt

Technical changes since QDDIM-05:

1. PreambleFilter / PreambleMarkerService generalized
   (3.8.3, 4.3.13, 4.3.34).

2. Queue / Dropper updates (3.10, 3.10.2, 4.3.30, 4.4.6).

3. HeadTailDropQueueBinding clarified (3.10, 3.10.1).

4. Cardinality change for ElementInSchedulingService
   (4.4.28).

5. QoSService moved to inherit directly from Service
   (4.2, 4.3.23).

6. AllocationPercentage property added to the
   QueueAllocation association (4.4.10).

Issues to discuss in SLC (or on the list) for QDDIM-06:

1. Global: how do we apply here the lessons learned in
   PCLS and PCIMe related to specifying agent behavior
   in response to unexpected / illegal values?  We can
   use the new property AllocationPercentage as the
   basis for discussion:

       What is the agent supposed to do if, say, two
       or more queues are each supposed to get 100%
       of a pool?  Or three queues each get 40%, and
       one gets 20%?  Or what if one queue gets 60%,
       and no value at all is supplied for the
       remaining queues?

   The goal is to strike the right balance between
   saying too much to address these cases and saying
   too little. (Andrea?)

2. It would help scalability if we had a way to represent
   reusable combinations of ClassifierElements, very
   similar to CompoundPolicyConditions, which could be
   combined to form Classifiers.  It's not clear,
   though, what the best way might be to add these to
   the QDDIM model.  (Walter)

3. Alignment of QDDIM's BufferPool class with CIM's
   StoragePool class.  (Andrea)

4. QoSService subclasses: Why would anyone create a
   DSCP=4 DiffServService?  Why wouldn't you classify
   and then process using the ConditioningServices?
   A specific example is needed since the DiffServ MIB,
   PIB and model work without these classes, and they
   appear to overlap with the ClassifierElements.
   (Andrea)

Since I'm not going to be coming to SLC, Joel will be
leading this discussion during the WG meeting.

Regards,
Bob

Bob Moore
Advanced Design and Technology
Application Integration Middleware Division
IBM Software Group
+1-919-254-4436
[email-masked]

_______________________________________________
Policy mailing list
[email-masked]
http://www1.ietf.org/mailman/listinfo/policy