Management Information Base for the Internet Protocol (IP)
RFC 4293
|
Document |
Type |
|
RFC - Proposed Standard
(April 2006; Errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 4293 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Margaret Cullen
|
|
Send notices to |
|
(None)
|
Network Working Group S. Routhier, Ed.
Request for Comments: 4293 April 2006
Obsoletes: 2011, 2465, 2466
Category: Standards Track
Management Information Base
for the Internet Protocol (IP)
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 (2006).
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 implementations
of the Internet Protocol (IP) in an IP version independent manner.
This memo obsoletes RFCs 2011, 2465, and 2466.
Routhier, Ed. Standards Track [Page 1]
RFC 4293 IP MIB April 2006
Table of Contents
1. The Internet-Standard Management Framework ......................2
2. Revision History ................................................3
3. Overview ........................................................3
3.1. Multi-Stack Implementations ................................3
3.2. Discussion of Tables and Groups ............................3
3.2.1. General Objects .....................................4
3.2.2. Interface Tables ....................................4
3.2.3. IP Statistics Tables ................................4
3.2.4. Internet Address Prefix Table .......................8
3.2.5. Internet Address Table ..............................8
3.2.6. Internet Address Translation Table ..................9
3.2.7. IPv6 Scope Zone Index Table .........................9
3.2.8. Default Router Table ................................9
3.2.9. Router Advertisement Table ..........................9
3.2.10. ICMP Statistics Tables .............................9
3.2.11. Conformance and Compliance ........................10
3.2.12. Deprecated Objects ................................10
4. Updating Implementations .......................................10
4.1. Updating an Implementation of the IPv4-only IP-MIB ........11
4.2. Updating an Implementation of the IPv6-MIB ................12
5. Definitions ....................................................13
6. Previous Work .................................................116
7. References ....................................................116
7.1. Normative References .....................................116
7.2. Informative References ...................................117
8. Security Considerations .......................................118
9. Acknowledgements ..............................................120
10. Authors ......................................................120
1. 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 [9].
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 [1], STD 58, RFC 2579 [2] and STD 58, RFC 2580 [3].
Routhier, Ed. Standards Track [Page 2]
RFC 4293 IP MIB April 2006
2. Revision History
One of the primary purposes of this revision of the IP MIB is to
create a single set of objects to describe and manage IP modules in
an IP version independent manner. Where RFCs 2465 and 2466 created a
set of objects independent from RFC 2011, this document merges those
three documents into a single unified set of objects. The
ipSystemStatsTable and ipIfStatsTable tables are examples of updating
objects to be independent of IP version. Both of these tables
contain counters to reflect IP traffic statistics that originated in
much earlier MIBs and both include an IP address type in order to
separate the information based on IP version.
Another purpose of this document is to increase the manageability of
a node running IPv6 by adding new objects. Some of these tables,
Show full document text