RE: Incremental state updates from PEP -> PDP in COPS-PR ?

["Bokaemper, Martin" <MBokaemper@unispherenetworks.com>]

Hi David!

> [...] The general perception has been that the request
> state information for the PEP->PDP is relatively small
> compared to the configuration decision information from
> the PDP->PEP and changes less frequently. [...]
>
> Now, if these assumptions prove not to be true in some cases, 
> there are a number of ways to deal with it.

I definitely think that this issue needs to be addressed,
since - as far as I can see - a significant number of 
cases violate that assumption, including the framework-pib
for diffserv.

> 1. Use Reports to convey the most dynamic information: 
>    Ie. Accounting information, ifindex up and down, etc. 
>    Reports do convey incremental updates in all PIBs.

Accounting RPTs can create/update information but they 
can not delete a row.
With this solution I would prefer to see two additional
report-types 'install' and 'delete' corresponding to the
DEC commands 'install' and 'delete'.

> 2. Use multiple Requests with different handles, 
>    reducing the amount of info per Request. [...]

This is the way COPS-RSVP handles 'large active state'.
My understanding of handles is, that they imply independent
object spaces. How could objects be shared between different
handles?
Sharing common objects seems to be one of the main attractions
of PIBs and COPS-PR and is an important part of the diffserv PIB.

One of the solutions you mentioned IMHO needs to get into the 
framework-PIB - or would COPS-PR itself be more appropriate?
Which option would be the best for this case?

ciao,
Martin.
--