ipcdn-0----Page:31
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
|
Status of MTA MIB draft 06 Draft 04 reviewed by MIB doctor Dave Thaler http://www1.ietf.org/mail-archive/web/ipcdn/current/msg01325.html Drafts 05 and 06 address all MIB doctor comments Main Technical Changes in Draft 06 pktcMtaDevErrorOid table and entry objects: Clarified what behavior of the agent is when max errors > 1024 per IETF #61 and list consensus Defined new “TooManyErrorOID” in pktcMtaDevErrorsTooManyErrors to have a mechanism to indicated that too many errors have been encountered without relying on human readable string (to allow internationalization and easier machine processing of such errors) Updated pktcMtaDevProvConfigKey description to be more specific on privacy algorithms Open issues in draft 06 raised by preliminary AD review Objects pktcMtaDevProvUnsolicitedKeyMaxTimeout and pktcMtaDevProvUnsolicitedKeyNomTimeout are read-only but descriptions invoke setting value pktcMtaDevProvKerbRealmName and pktcMtaDevRealmName syntax (also raised by Randy Presuhn) content MUST be uppercase ASCII => change syntax to DisplayString Value ranges for { pktcMtaDevRealmAvailSlot, pktcMtaDevRealmIndex} and {pktcMtaDevCmsAvailSlot , pktcMtaDevCmsIndex} are out of sync, is this a problem? pktcMtaNotifications object notification OID pktcMtaBasicCompliance and pktcMtaBasicSmtaCompliance MODULE-COMPLIANCE: contain object clauses with descriptions to only require ipv4 compliance but the object syntax is still loose => need to strengthen the syntax clauses to match what the description says For objects that refer to FQDNs, should we specify when such FQDNs are supposed to be resolved Next step: Update draft and complete AD review |