Multicast Address Allocation MIB
RFC 3559
Document | Type | RFC - Proposed Standard (June 2003; No errata) | |
---|---|---|---|
Author | Dave Thaler | ||
Last updated | 2015-10-14 | ||
Stream | Internent 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 3559 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Allison Mankin | ||
IESG note |
A small number of final fixes were commissioned by Bert Wijnen as MIB doctor. The record of these needs to be placed somewhere. For now, contact Allison if you want them. The document is now ready for advancement. |
||
Send notices to | (None) |
Network Working Group D. Thaler Request for Comments: 3559 Microsoft Category: Standards Track June 2003 Multicast Address Allocation 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 (2003). 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 multicast address allocation. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. The Internet-Standard Management Framework . . . . . . . . . . 2 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3.1. Protocol-independent objects . . . . . . . . . . . . . . 3 3.2. Protocol-specific objects. . . . . . . . . . . . . . . . 3 4. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 32 6. Security Considerations. . . . . . . . . . . . . . . . . . . . 33 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 34 8. Intellectual Property Statement. . . . . . . . . . . . . . . . 34 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 9.1. Normative References . . . . . . . . . . . . . . . . . . 35 9.2. Informative References . . . . . . . . . . . . . . . . . 35 10. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 36 11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 37 Thaler Standards Track [Page 1] RFC 3559 Multicast Address Allocation MIB June 2003 1. Introduction This document defines a Management Information Base (MIB) module for managing multicast address allocation in a protocol-independent manner, as well as for managing specific protocols used in allocating multicast addresses. The protocol-independent objects in this MIB apply to all multicast address allocation servers (MAASs) and clients, as described in [ARCH], including those that allocate source-specific multicast addresses for the local machine. The protocol-specific objects in this MIB include objects related to the Multicast Address Dynamic Client Allocation Protocol (MADCAP) [MADCAP]. Interactions with the Multicast-scope Zone Announcement Protocol (MZAP) [MZAP] are also noted where appropriate. 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 [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]. 3. Overview The purpose of this MIB module is to provide the ability to configure and monitor the status of multicast address allocation within the local domain. Some important monitoring questions which can be answered by this MIB module include: o How full is scope X? o Who's using up the space? o Who allocated a given address A? o Are requests being met? Thaler Standards Track [Page 2] RFC 3559 Multicast Address Allocation MIB June 2003 This MIB module is divided into two primary sections: o Protocol-independent objects relevant to all multicast address allocation servers and clients. o Protocol-specific objects related to the MADCAP client-server protocol. 3.1. Protocol-independent objects The protocol-independent objects consist of one "capabilities" scalar and five tables. The tables are: o The Scope Table contains information on the multicast scopes known to a multicast address allocation server. This table allows configuring scopes, and viewing what scopes are known to the local system after being configured elsewhere.Show full document text