A new Request for Comments is now available in online RFC libraries.


        RFC 2096:

        Title:      IP Forwarding Table MIB
        Author:     F. Baker
        Date:       January 1997
        Mailbox:    fred@cisco.com
        Pages:      21
        Characters: 35930
        Updates/Obsoletes: 1354

        URL:        ftp://ds.internic.net/rfc/rfc2096.txt


This memo defines an update to RFC 1354, "IP Forwarding Table MIB",
for Classless Inter-Domain Routing (CIDR).  That document was
developed by the Router Requirements Working Group as an update to RFC
1213's ipRouteTable, with the display of multiple routes as a primary
objective.  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.  Note that this MIB obsoletes a number of
objects from RFC 1354. This document is a product of the OSPF Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute