MTA MIB draft 03 and Standalone MTA devices

Folks,

Eugene and I have been working on an update to the IPCDN MTA MIB draft. In the upcoming draft 03, we have added a module compliance statement for Standalone MTA devices.

See below the proposed text, let us know if you have any comments by Monday January 26 so that we can address them before publication.

Thanks, 
Eugene & Jean-François 
---
1/
Added new section to explain why S-MTAs deal with secure software download differently, where the normative requirements are and why we need the S-MTA compliance statement

3.6 Secure Software Download
While E-MTAs have their software upgraded by the Cable Modem according to the DOCSIS requirements, S-MTAs must implement the a specific mechanism for Secure Software Download defined in the PacketCable/IPCablecom Security specification [PKT-SP-SEC-I09-030728]. 
This mechanism provides means to verify the code upgrade using Code Verification Certificates and is modeled after the DOCSIS mechanism implemented in Cable Modems. This is the reason why the MTA MIB and the S-MTA compliance modules rely on two MIB object groups (docsBpi2CodeDownloadGroup and docsDevSoftwareGroupV2) defined in the IETF BPI Plus MIB module (DOCS-IETF-BPI2-MIB [RFCyyyy]).


2/
Added formal compliance for S-MTAs, mostly to translate the actual requirements contained in the PacketCable/IPCablecom Security specs (from 2 other IPCDN docsis mibs cablevice and bpi+ mib).

pktcMtaBasicRFCyyyySmtaCompliance MODULE-COMPLIANCE 
  
    STATUS      current 
    DESCRIPTION 
        " The compliance statement for S-MTA devices
          that implement PacketCable or IPCablecom requirements. 
          
          This compliance statement applies to S-MTA implementations
          that support PacketCable 1.3 or IPCablecom requirements, 
          which are not IPv6-capable at the time of this
          RFC publication."

   -- Unconditionally Mandatory Groups for S-MTA devices
    MODULE 
        MANDATORY-GROUPS {  
            pktcMtaGroup, 
            pktcMtaNotificationGroup
        }
    MODULE DOCS-CABLE-DEVICE-MIB
        MANDATORY-GROUPS {  
            docsDevSoftwareGroupV2  
        }
    MODULE DOCS-IETF-BPI2-MIB
        MANDATORY-GROUPS {  
            docsBpi2CodeDownloadGroup
        }
     ::= { pktcMtaCompliances 2 }