tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

RFC 5132

Proposed STD
Pages: 59
Top     in Index     Prev     Next
in Group Index     Prev in Group     Next in Group     Group: MBONED

IP Multicast MIB

Part 1 of 3, p. 1 to 4
None       Next RFC Part

Obsoletes:    2932


Top       ToC       Page 1 
Network Working Group                                        D. McWalter
Request for Comments: 5132                           Data Connection Ltd
Obsoletes: 2932                                                D. Thaler
Category: Standards Track                          Microsoft Corporation
                                                              A. Kessler
                                                           Cisco Systems
                                                           December 2007


                            IP Multicast 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.

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 objects used for managing multicast
   function, independent of the specific multicast protocol(s) in use.
   This document obsoletes RFC 2932.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  History  . . . . . . . . . . . . . . . . . . . . . . . . . . .  2
   3.  The Internet-Standard Management Framework . . . . . . . . . .  2
   4.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   5.  IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . . .  4
   6.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 54
     7.1.  SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . 54
     7.2.  Writeable Objects  . . . . . . . . . . . . . . . . . . . . 54
     7.3.  Readable Objects . . . . . . . . . . . . . . . . . . . . . 55
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 55
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 55
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 56
     10.2. Informative References . . . . . . . . . . . . . . . . . . 57

Top      ToC       Page 2 
1.  Introduction

   This MIB describes objects used for managing IP multicast function,
   including IP multicast routing.  These objects are independent of the
   specific multicast routing protocol in use.  Managed objects specific
   to particular multicast protocols are defined elsewhere.

1.1.  Terminology

   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 [RFC2119].

2.  History

   This document obsoletes [RFC2932].  The MIB module defined by this
   document is a re-working of the MIB module from [RFC2932], with
   changes that include the following:

   o  This MIB module includes support for IPv6 addressing and the IPv6
      scoped address architecture.  [RFC2932] supported only IPv4.

   o  This MIB module allows several multicast protocols to perform
      routing on a single interface, where [RFC2932] assumed each
      interface supported at most one multicast routing protocol.
      Multicast routing protocols are now per-route, see
      ipMcastRouteProtocol.

   o  This MIB module includes objects that are not specific to
      multicast routing.  It allows management of multicast function on
      systems that do not perform routing, whereas [RFC2932] was
      restricted to multicast routing.

   o  This MIB module includes a table of Source-Specific Multicast
      (SSM) address ranges to which SSM semantics [RFC3569] should be
      applied.

   o  This MIB module includes a table of local applications that are
      receiving multicast data.

   o  This MIB module includes a table of multicast scope zones.

3.  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
   [RFC3410].

Top      ToC       Page 3 
   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,
   ([RFC2578], [RFC2579] and [RFC2580]).

4.  Overview

   This MIB module contains two scalars and eight tables.  The tables
   are:

   1.  The IP Multicast Interface Table, which contains multicast
       information specific to interfaces.

   2.  The IP Multicast SSM Range Table, which contains one row per
       range of multicast group addresses to which Source-Specific
       Multicast semantics [RFC3569] should be applied.

   3.  The IP Multicast Route Table, which contains multicast routing
       information for IP datagrams sent by particular sources to the IP
       multicast groups known to a system.

   4.  The IP Multicast Routing Next Hop Table, which contains
       information about next-hops for the routing of IP multicast
       datagrams.  Each entry is one of a list of next-hops on outgoing
       interfaces for particular sources sending to a particular
       multicast group address.

   5.  The IP Multicast Scope Boundary Table, which contains the
       boundaries configured for multicast scopes [RFC2365].

   6.  The IP Multicast Scope Name Table, which contains human-readable
       names for multicast scopes.

   7.  The IP Multicast Local Listener Table, which contains identifiers
       for local applications that are receiving multicast data.

   8.  The IP Multicast Zone Table, which contains an entry for each
       scope zone known to a system, and maps each zone to the multicast
       address range that is the corresponding scope.

   This MIB module uses textual conventions defined in the IF-MIB
   [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB.

Top      ToC       Page 4 
5.  IMPORTed MIB Modules and REFERENCE Clauses

   The MIB modules defined in this document IMPORTs definitions
   normatively from the following MIB modules, beyond [RFC2578],
   [RFC2579], and [RFC2580]: HCNUM-TC [RFC2856], IF-MIB [RFC2863], IANA-
   RTPROTO-MIB, SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB
   [RFC4001], and LANGTAG-TC-MIB [RFC5131].

   This MIB module also includes REFERENCE clauses that make normative
   references to Administratively Scoped IP Multicast [RFC2365],
   Unicast-Prefix-based IPv6 Multicast Addresses [RFC3306], IPv6 Scoped
   Address Architecture [RFC4007], and IPv6 Addressing Architecture
   [RFC4291].

   Finally, this MIB module makes informative references to several RFCs
   in the text of DESCRIPTION clauses, including sysApplMIB [RFC2287],
   IP-MIB [RFC4293], Source-Specific Multicast [RFC3569], Protocol
   Independent Multicast-Sparse Mode version 2 (PIM-SMv2) Protocol
   Specification [RFC4601], Bidirectional Protocol Independent Multicast
   (BIDIR-PIM) [RFC5015], and Tags for Identifying Languages [RFC4646].



(page 4 continued on part 2)

Next RFC Part