snmp version-specific behavior in draft-ietf-ipcdn-pktc-mtamib-04.txt

Hi -

In draft-ietf-ipcdn-pktc-mtamib-04.txt there are several OBJECT-TYPEs
whose current DESCRIPTIONs will cause implementation difficulties
in RFC 2741 (AgentX) environments.  Specifically, pktcMtaDevProvConfigKey,
pktcMtaDevProvSolicitedKeyTimeout, pktcMtaDevProvUnsolicitedKeyMaxTimeout,
pktcMtaDevProvUnsolicitedKeyNomTimeout,  and
pktcMtaDevProvUnsolicitedKeyMaxRetries, all require special
errors to be generated depending on the "provisioning mode",
which appears to be the protocol used to access the object instance.

AgentX provides no way for a subagent to know what protocol version
was used to transport a request, so this kind of specification effectively
precludes implementation in those environments.

I would strongly suggest that it would make more sense to remove these
statements about the implementation of access control policy from the
OBJECT-TYPE descriptions, and put the material in the security
considerations section where it belongs.

In any case, the mandated behavior should be identical to that
which would be encountered if access had been denied due to access
control, whether using VACM or some other access control model.

Randy