datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Multicast Source Discovery Protocol (MSDP) MIB
RFC 4624

Network Working Group                                          B. Fenner
Request for Comments: 4624                                 AT&T Research
Category: Experimental                                         D. Thaler
                                                               Microsoft
                                                            October 2006

             Multicast Source Discovery Protocol (MSDP) MIB

Status of This Memo

   This memo defines an Experimental Protocol for the Internet
   community.  It does not specify an Internet standard of any kind.
   Discussion and suggestions for improvement are requested.
   Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This memo defines an experimental 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 Multicast Source Discovery Protocol (MSDP) (RFC
   3618) speakers.

Table of Contents

   1. Introduction ....................................................2
   2. The Internet-Standard Management Framework ......................2
   3. Overview ........................................................2
   4. Definitions .....................................................3
   5. Security Considerations ........................................28
   6. IANA Considerations ............................................29
   7. Acknowledgements ...............................................30
   8. References .....................................................30
      8.1. Normative References ......................................30
      8.2. Informative References ....................................30

Fenner & Thaler               Experimental                      [Page 1]
RFC 4624                        MSDP MIB                    October 2006

1.  Introduction

   This memo defines an experimental 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 Multicast Source Discovery Protocol (MSDP) [1]
   speakers.

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

   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 [4], STD 58, RFC 2579 [5] and STD 58, RFC 2580 [6].

3.  Overview

   This MIB module contains four scalars and four tables, one
   deprecated.  The tables are:

   o  The deprecated Requests Table, containing the longest-match table
      used to determine the peer to send SA-Requests to for a given
      group.  This table is deprecated because Requests were removed
      from MSDP before it became an RFC.

   o  The Peer Table, containing information on the system's peers.

   o  The Source-Active (SA) Cache Table, containing the SA cache
      entries.

   o  The Mesh Group Table, containing the list of MSDP mesh groups to
      which this system belongs.

   This MIB module uses the IpAddress SYNTAX, making it only suitable
   for IPv4 systems.  Although the desired direction for MIBs is to use
   InetAddressType/InetAddress pairs to allow both IPv4 and IPv6 (and
   future formats as well), the MSDP protocol itself is IPv4-only, and
   the MSDP working group made an explicit decision not to create an
   IPv6 version of the protocol.

Fenner & Thaler               Experimental                      [Page 2]
RFC 4624                        MSDP MIB                    October 2006

   This MIB module is somewhat disorganized, with scalars before and
   after tables, holes in the OID space, tables with the RowStatus in
   the middle, and so on.  This is because objects were added and
   removed as necessary as the MSDP protocol evolved, and the plan was
   to renumber the whole MIB when moving to the standard mib-2 tree.
   The MSDP Working Group then changed direction, publishing the MSDP
   protocol as Experimental.  Since there were existing implementations
   using the strange object order under the experimental OID, the WG
   decided not to renumber the MIB and to publish it as experimental,

[include full document text]