datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

IPv4 Multicast Routing MIB
RFC 2932

Document type: RFC - Proposed Standard (October 2000; No errata)
Obsoleted by RFC 5132
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Document shepherd: No shepherd assigned

IESG State: RFC 2932 (Proposed Standard)
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                      K. McCloghrie
Request for Comments: 2932                                 cisco Systems
Category: Standards Track                                   D. Farinacci
                                                        Procket Networks
                                                               D. Thaler
                                                               Microsoft
                                                            October 2000

                       IPv4 Multicast Routing MIB

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

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 describes managed objects used for managing IP
   Multicast Routing for IPv4, independent of the specific multicast
   routing protocol in use.

Table of Contents

    1 Introduction .................................................  2
    2 The SNMP Management Framework ................................  2
    3 Overview .....................................................  3
    4 Definitions ..................................................  4
    5 IANA Considerations .......................................... 22
    6 Security Considerations ...................................... 22
    7 Intellectual Property Notice ................................. 23
    8 Acknowledgements ............................................. 23
    9 Authors' Addresses ........................................... 24
   10 References ................................................... 25
   11 Full Copyright Statement ..................................... 27

McCloghrie, et al.          Standards Track                     [Page 1]
RFC 2932               IPv4 Multicast Routing MIB           October 2000

1.  Introduction

   This MIB describes objects used for managing IP Multicast Routing
   [16], independent of the specific multicast routing protocol [17-21]
   in use.  Managed objects specific to particular multicast routing
   protocols are specified elsewhere.  Similarly, this MIB does not
   support management of multicast routing for other address families,
   including IPv6.  Such management may be supported by other MIBs.

2.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o    An overall architecture, described in RFC 2571 [1].

   o    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, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
        The second version, called SMIv2, is described in STD 58, RFC
        2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].

   o    Message protocols for transferring management information.  The
        first version of the SNMP message protocol is called SNMPv1 and
        described in STD 15, RFC 1157 [8].  A second version of the SNMP
        message protocol, which is not an Internet standards track
        protocol, is called SNMPv2c and described in RFC 1901 [9] and
        RFC 1906 [10].  The third version of the message protocol is
        called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and
        RFC 2574 [12].

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

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

   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.

McCloghrie, et al.          Standards Track                     [Page 2]
RFC 2932               IPv4 Multicast Routing MIB           October 2000

   This memo specifies a MIB module that is compliant to the SMIv2.  A
   MIB conforming to the SMIv1 can be produced through the appropriate

[include full document text]