IP Version 6 Management Information Base for The Multicast Listener Discovery Protocol
RFC 3019

Document Type RFC - Proposed Standard (January 2001; No errata)
Obsoleted by RFC 5519
Authors Brian Haberman  , Randy Worzella 
Last updated 2013-03-02
Stream Internet Engineering Task Force (IETF)
Formats plain text html pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3019 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        B. Haberman
Request for Comments: 3019                               Nortel Networks
Category: Standards Track                                    R. Worzella
                                                            January 2001

             IP Version 6 Management Information Base for
               The Multicast Listener Discovery Protocol

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 (2001).  All Rights Reserved.


   This document defines a portion of the Management Information Base
   (MIB) for use with network management protocols in Internet Protocol
   Version 6 internets.  Specifically, this document is the MIB module
   that defines managed objects for implementations of the Multicast
   Listener Discovery Protocol [RFC2710].


   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in [RFC2119].

1. The SNMP Management Framework

   The SNMP Management Framework presently consists of five major

   An overall architecture, described in RFC 2571 [RFC2571].

   Mechanisms for describing and naming objects and events for the
   purpose of management.  The first version of this Structure of
   Management Information (SMI) is called SMIv1 and described in STD 16,

Haberman & Worzella         Standards Track                     [Page 1]
RFC 3019                      MIB for MLD                   January 2001

   RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
   [RFC1215].  The second version, called SMIv2, is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580

   Message protocols for transferring management information.  The first
   version of the SNMP message protocol is called SNMPv1 and described
   in STD 15, RFC 1157 [RFC1157].  A second version of the SNMP message
   protocol, which is not an Internet standards track protocol, is
   called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906
   [RFC1906].  The third version of the message protocol is called
   SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and
   RFC 2574 [RFC2574].

   Protocol operations for accessing management information.  The first
   set of protocol operations and associated PDU formats is described in
   STD 15, RFC 1157 [RFC1157].  A second set of protocol operations and
   associated PDU formats is described in RFC 1905 [RFC1905].

   A set of fundamental applications described in RFC 2573 [RFC2573] and
   the view-based access control mechanism described in RFC 2575

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [RFC2570].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2.  A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations.  The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64).  Some machine-readable
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process.  However, this loss of
   machine-readable information is not considered to change the
   semantics of the MIB.

2. Overview

   This MIB module contains two tables:

      1. The MLD Interface Table, which contains one row for each
         interface on which MLD is enabled.

Haberman & Worzella         Standards Track                     [Page 2]
RFC 3019                      MIB for MLD                   January 2001

      2. The MLD Cache Table which contains one row for each IPv6
         Multicast group for which there are members on a particular

   Both tables are intended to be implemented by hosts and routers. Some
   objects in each table apply to routers only.

3. Definitions


       MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
       Unsigned32, TimeTicks, mib-2     FROM SNMPv2-SMI
       RowStatus, TruthValue            FROM SNMPv2-TC
       InetAddressIPv6             FROM INET-ADDRESS-MIB
       InterfaceIndex, InterfaceIndexOrZero
Show full document text