
|
Transport Subsystem Issue#1 MUST responses go back on the same transport session? RFC3411 & MP subsystem do not require this, to allow e.g. unencrypted requests with encrypted responses to reduce overhead SNMPv3, USM, TSM use the same session based on securityStateReference Apps cannot specify transport session via ASIs Transport doesn’t know it’s a response (see#3) Proposal: keep specific to message and security models, not transport models |