RAQMON PDU Notification Objects - Table or Scalar?

I would like to query the WG on another issue that surfaced visibly during the latest round of discussions. One of the more visible problems of the SNMP Notifications transport is the need of fragmentation if the number of objects in one notification leads to the maximum PDU size being exceeded. To reduce this probability, a more compact notifications format would help. Currently the notification objects are organized in raqmonDsNotificationTable which is indexed by the objects that characterize a session and subsession (raqmonDSRC, raqmonRCN, raqmonPeerAddrType, raqmonPeerAddr). This is not too efficient, and if a maximum PDU or close to a maximum PDU needs to be set, the limit may be exceeded, especially for ipv6 addresses in the peer. In the past I supported the table format because the indices characterize the session in a unique manner and because possible extensions can be written in the future simply like extensions of this table by later RAQMON users.  Right now it looks like avoiding fragmentation became a bigger concern. The proposal I would like the WG to consider is to replace the raqmonDsNotificationTable with a group of scalars, and make the present four index objects the mandatory objects in the notifications. 

Opinions?     

Regards,

Dan

_______________________________________________
RMONMIB mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/rmonmib