Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management
RFC 4036

 
Document Type RFC - Proposed Standard (April 2005; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4036 (Proposed Standard)
Telechat date
Responsible AD Bert Wijnen
Send notices to <Richard_Woundy@cable.comcast.com>, <jf.mule@cablelabs.com>
Network Working Group                                          W. Sawyer
Request for Comments: 4036                                    April 2005
Category: Standards Track

                    Management Information Base for
        Data Over Cable Service Interface Specification (DOCSIS)
       Cable Modem Termination Systems for Subscriber Management

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines a set of managed objects for Simple Network
   Management Protocol (SNMP)-based management of Data-over-Cable
   Service Interface Specification (DOCSIS)-compliant Cable Modem
   Termination Systems.  These managed objects facilitate protection of
   the cable network from misuse by subscribers.  The Differentiated
   Services MIB (RFC 3289) provides the filtering functions needed here,
   making use of classification items defined in this specification.

Table of Contents

   1.  The Internet-Standard Management Framework....................  2
   2.  Conventions...................................................  2
   3.  Overview......................................................  2
       3.1.  Structure of the MIB....................................  4
             3.1.1.  docsSubMgtFilterGroupTable......................  4
             3.1.2.  IPv4 Compliance.................................  5
       3.2.  Management Requirements.................................  5
             3.2.1.  Interaction with DOCSIS Provisioning for CPE
                     Address Control.................................  6
             3.2.2.  Interaction with DOCSIS Provisioning for
                     Filtering.......................................  6
             3.2.3.  Distinguishing Modem from Subscriber Traffic....  7

Sawyer                      Standards Track                     [Page 1]
RFC 4036            DOCSIS Subscriber Management MIB          April 2005

       3.3.  Relationship to the Differentiated Services MIB
             [RFC3289]...............................................  7
             3.3.1.  Using the Filter Group to Extend Packet
                     Classification..................................  8
             3.3.2.  Interface Usage.................................  8
       3.4.  Filtering and the Tiny Fragment Attack..................  9
   4.  Definitions...................................................  9
   5.  Acknowledgements.............................................. 23
   6.  IANA Considerations........................................... 23
   7.  Normative References.......................................... 23
   8.  Informative References........................................ 24
   9.  Security Considerations....................................... 25
   Author's Address.................................................. 26
   Full Copyright Statement.......................................... 27

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

2.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].

3.  Overview

   This MIB module provides a set of objects required for the management
   of DOCSIS Cable Modem Termination Systems (CMTS).  The specification
   is derived in part from the operational model described in the DOCSIS
Show full document text