IP Forwarding Table MIB
RFC 4292
| Document | Type |
RFC - Proposed Standard
(April 2006; No errata)
Obsoletes RFC 2096
|
|
|---|---|---|---|
| Author | Brian Haberman | ||
| Last updated | 2013-03-02 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 4292 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Thomas Narten | ||
| Send notices to | (None) | ||
Network Working Group B. Haberman
Request for Comments: 4292 Johns Hopkins University
Obsoletes: 2096 April 2006
Category: Standards Track
IP Forwarding Table 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 (2006).
Abstract
This document 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 related to
the forwarding of Internet Protocol (IP) packets in an IP version-
independent manner. This document obsoletes RFC 2096.
Table of Contents
1. Introduction ....................................................2
2. Conventions Used In This Document ...............................2
3. The Internet-Standard Management Framework ......................2
4. Overview ........................................................2
4.1. Relationship to Other MIBs .................................3
4.1.1. RFC 1213 ............................................3
4.1.2. RFC 1354 ............................................3
4.1.3. RFC 2096 ............................................3
4.1.4. RFC 2011 and 2465 ...................................3
5. Definitions .....................................................3
6. Security Considerations ........................................30
7. Changes from RFC 2096 ..........................................31
8. Normative References ...........................................32
9. Informative References .........................................32
10. Authors and Acknowledgements ..................................33
Haberman Standards Track [Page 1]
RFC 4292 IP Forwarding Table MIB April 2006
1. Introduction
This document defines a portion of the Management Information Base
(MIB) for use in managing objects related to the forwarding of
Internet Protocol (IP) packets in an IP version-independent manner.
It should be noted that the MIB definition described herein does not
support multiple instances based on the same address family type.
However, it does support an instance of the MIB per address family.
2. Conventions Used In This Document
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 RFC 2119 [RFC2119].
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
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].
4. Overview
The MIB consists of one current table and two current global objects.
1. The object inetCidrRouteNumber indicates the number of current
routes. This is primarily to avoid having to read the table in
order to determine this number.
2. The object inetCidrRouteDiscards counts the number of valid
routes that were discarded from inetCidrRouteTable for any
reason. This object replaces the ipRoutingDiscards and
ipv6DiscardedRoutes objects.
3. The inetCidrRouteTable provides the ability to display IP
version-independent multipath CIDR routes.
Haberman Standards Track [Page 2]
RFC 4292 IP Forwarding Table MIB April 2006
4.1. Relationship to Other MIBs
This MIB definition contains several deprecated and obsolete tables
and objects. The following subsections describe the relationship
between these objects and other MIB modules.
4.1.1. RFC 1213
The ipRouteTable object was originally defined in RFC 1213 [RFC1213].
It was updated by ipForwardTable in RFC 1354 [RFC1354].
4.1.2. RFC 1354
The ipForwardTable object replaced the ipRouteTable object from RFC
Show full document text