ObsoletedPROPOSED STANDARDIETF stream

RFC 2096: IP Forwarding Table MIB

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4292.

Current document in this lineage: RFC 4292IP Forwarding Table MIB

In plain English — editorial summary, not part of the RFC

This memo defines an update to RFC 1354. The significant difference between this MIB and RFC 1354 is the recognition (explicitly discussed but by consensus left to future work) that CIDR routes may have the same network number but different network masks. [STANDARDS-TRACK]

Document record

Document ID
RFC2096
Published
January 1997
Authors
F. Baker
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
21
Also known as
Obsoletes:
RFC 1354
Obsoleted by:
RFC 4292

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 1354 (1992)
  2. RFC 2096 (1997)
  3. RFC 4292 (2006)

Read the full history of IP Forwarding Table MIB

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/2096-ip-forwarding-table-mib