Juergen Schoenwaelder writes...
> Not really. See RFC 5590:
>
> [...] A
> tmStateReference is passed as an extra parameter in the ASIs between
> the Transport Subsystem and the Message Processing and Security
> Subsystems in order to identify the relevant cache.
>
> We pass the tmStateReference but no the detailed information the
> tmStateReference points to. See also sections 6 of RFC 5590 for all
> the details of the changes of the ASIs.
Well, if we follow that precedent, and we want to avoid modifying the ASI of the access control model, we'll need to find another place to put the "magic". Since the tmStateReference pointer is only used in a "management" channel rather than a "message flow" channel, maybe it doesn't need to affect VACM's ASI, anyway.
Any way you parse it, however, adding new functionality without modifying APIs (yes, I meant API, as in concrete implementation interface) is difficult.
