Subject: [ipcdn] subscriber management MIB: RFC3289 compliance statements

From: [email-masked]
Date: Wed, 30 Jul 2003 10:08:30 -0400

Colleagues:

Per Jean-Francois's suggestion, I'm including module compliance statements
for how docsis subscriber management uses RFC3289 in the next
internet-draft. This is a statement of which parts of 3289 must be
implemented in order to claim compliance with subscriber management. Below
are the OBJECT clauses I'm considering. They:
-- require (at minimum) only IPv4 address classification
-- require (at minimum) only Nonvolatile storage
-- carry over some RFC3289 allowances on RowStatus objects
-- require only always-drop for the algorithmic-drop table.

If you are a CMTS operator or vendor, please review these carefully.

Thank you
Wilson Sawyer

OBJECT diffServDataPathStatus  -- same as RFC3289
    SYNTAX RowStatus { active(1) }
    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
    DESCRIPTION
        "Support for createAndWait and notInService is not required."

OBJECT diffServClfrStatus  -- same as RFC3289
    SYNTAX RowStatus { active(1) }
    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
    DESCRIPTION
        "Support for createAndWait and notInService is not required."

OBJECT diffServClfrElementStatus  -- same as RFC3289
    SYNTAX RowStatus { active(1) }
    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
    DESCRIPTION
        "Support for createAndWait and notInService is not required."

OBJECT diffServMultiFieldClfrAddrType
    SYNTAX  InetAddressType { ipv4(1) }
    DESCRIPTION
        "An implementation is only required to support IPv4 addresses."

OBJECT diffServMultiFieldClfrSrcAddr
    SYNTAX  InetAddress (SIZE(4))
    DESCRIPTION
        "An implementation is only required to support IPv4 addresses."

OBJECT diffServMultiFieldClfrDstAddr
    SYNTAX  InetAddress (SIZE(4))
    DESCRIPTION
        "An implementation is only required to support IPv4 addresses."

OBJECT diffServAlgDropStatus  -- same as RFC3289
    SYNTAX RowStatus { active(1) }
    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
    DESCRIPTION
        "Support for createAndWait and notInService is not required."

OBJECT diffServDataPathStorage
    SYNTAX StorageType { nonVolatile(3) }
    DESCRIPTION
        "An implementation is only required to support nonvolatile
         storage."

OBJECT diffServClfrStorage
    SYNTAX StorageType { nonVolatile(3) }
    DESCRIPTION
        "An implementation is only required to support nonvolatile
         storage."

OBJECT diffServClfrElementStorage
    SYNTAX StorageType { nonVolatile(3) }
    DESCRIPTION
        "An implementation is only required to support nonvolatile
         storage."

OBJECT diffServMultiFieldClfrStorage
    SYNTAX StorageType { nonVolatile(3) }
    DESCRIPTION
        "An implementation is only required to support nonvolatile
         storage."

OBJECT diffServActionStorage
    SYNTAX StorageType { nonVolatile(3) }
    DESCRIPTION
        "An implementation is only required to support nonvolatile
         storage."

OBJECT diffServCountActStorage
    SYNTAX StorageType { nonVolatile(3) }
    DESCRIPTION
        "An implementation is only required to support nonvolatile
         storage."

OBJECT diffServAlgDropStorage
    SYNTAX StorageType { nonVolatile(3) }
    DESCRIPTION
        "An implementation is only required to support nonvolatile
         storage."

OBJECT diffServAlgDropType
    SYNTAX  INTEGER { alwaysDrop(5) }
    DESCRIPTION
        "For DOCSIS subscriber management, this object is
         only used to provide packet filtering. Implementations
         need not support other values of this enumeration."

_______________________________________________
IPCDN mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ipcdn