midcom-1----Page:7
1  2  3  4  5  6  7  8  9  10  11 

Issue 4: Idempotency
MidcomRuleLifetime can have idempotency failures
resulting in longer lifetime than intended
depending on SNMP retransmission timeout
in general the longer lifetime will be known by the MIDCOM agent

Solution: The total lifetime needs to be stored
either at the MIDCOM server (additional managed object)
or at the MIDCOM client (additional client state)
preference: use additional managed object in rule table

There are further idempotency problems with session index and rule index generated from session table
These will probably disappear, if the session table is replaced
PPT Version