If we really want to optimize for cases with
shared path, we could do so by allowing more complex nested TLVs.
[Weiming]Do you mean multiple path-data TLVs in one OpTLV? If is, I agree
well.
It helps well for multiple Attributes, but helps little to save Attribute IDs.
Note that because we allow references to full tables and structures which
make full SNMP OID references so expensive are less of an issue in our work.
[Weiming] Sorry, I can not catch it well. Could you explain a little more?
thanks.
As a minor point, note that getting / setting multiple elements can be done
by sending multiple target selection TLVs.
[Weiming] This is even more expensive, which means we are repeating LFB class
and LFB instance ID as well as Attribute ID.
Thank you.
Weiming
