--- 1/draft-ietf-ipv6-rfc2096-update-05.txt 2006-02-05 00:03:40.000000000 +0100 +++ 2/draft-ietf-ipv6-rfc2096-update-06.txt 2006-02-05 00:03:40.000000000 +0100 @@ -1,16 +1,14 @@ Internet-Draft B. Haberman - Document: draft-ietf-ipv6-rfc2096-update-05.txt Caspian Networks - Expires: February 2004 M. Wasserman - Windriver - August 2003 + Document: draft-ietf-ipv6-rfc2096-update-06.txt Caspian Networks + Expires: July 2004 January 2004 IP Forwarding Table MIB Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -36,42 +34,86 @@ 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. Copyright Notice - Copyright (C) The Internet Society (2003). All Rights Reserved. + Copyright (C) The Internet Society (2004). All Rights Reserved. - Haberman, Wasserman Expires February 2004 1 + Haberman Expires July 2004 1 Table of Contents - 1 Conventions Used In This Document..............................5 - 2 The Internet-Standard Management Framework.....................5 - 3 Overview.......................................................5 - 4 Definitions....................................................7 - 5 Security Considerations.......................................30 - 6 Intellectual Property.........................................31 - 7 Changes from RFC 2096.........................................31 - 8 Normative References..........................................32 - 9 Informative References........................................32 - 10 Authors and Acknowledgements..................................33 - 11 Editors' Contact Information..................................33 - 12 Full Copyright Statement......................................33 + 1 Conventions Used In This Document..............................6 + 2 The Internet-Standard Management Framework.....................6 + 3 Overview.......................................................6 + 4 Definitions....................................................8 + 5 Security Considerations.......................................32 + 6 Intellectual Property Statement...............................33 + 7 Changes from RFC 2096.........................................33 + 8 Normative References..........................................34 + 9 Informative References........................................34 + 10 Authors and Acknowledgements..................................35 + 11 Editors' Contact Information..................................35 + 12 Full Copyright Statement......................................35 Revision History [Note to RFC Editor: Please remove prior to publication] + Changes from draft-ietf-ipv6-rfc2096-update-05.txt: + + 07 Jan 2004 Corrected editor information + + Changed mailing list information + + Limited InetAddress objects to (ipv4, ipv6, ipv4z, + ipv6z) + + Updated MODULE-IDENTITY REVISION clause to detail the + replacement of ipCidrRouteTable with + inetCidrRouteTable + + Updated DESCRIPTION clause of ipForwardCompliance to + indicate the replacement of ipForwardCompliance with + ipForwardFullCompliance and + ipForwardReadOnlyCompliance + + Added statement to DESCRIPTION clause of + ipForwardCidrRouteGroup pointing out its replacement + with inetForwardCidrRouteGroup + + Added detail to section 3 on relationship of this MIB + with previous versions + + Fixed references within DESCRIPTION clauses + + Added SYNTAX statements to read-only OBJECTs + + 21 Jan 2004 Added clarifying text to Introduction on the usage of + the MIB definition + + Enhanced Overview section to include explicit text on + + Haberman Expires July 2004 2 + relationship to other RFCs + + Clarified DESCRIPTION text for inetCidrRouteDiscards + + Added text to DESCRIPTION clause of + inetCidrRouteIfIndex to allow the value of 0 + + 28 Jan 2004 Added range of (0..128) to inetCidrRoutePfxLen + Changes from draft-ietf-ipv6-rfc2096-update-04.txt: 28 Aug 2003 Corrected copyright statement in DESCRIPTION clause Added inetCidrRouteNumber to inetForwardCidrRouteGroup conformance statement Removed SIZE constraints for inetCidrRouteDest and inetCidrRouteNextHop @@ -90,32 +132,33 @@ Changes from draft-ietf-ipv6-rfc2096-update-03.txt: 27 Jun 2003 Updated text to DESCRIPTION of inetCidrRouteDiscards Re-instated inetCidrRouteNumber Added references for IF-MIB, IP-MIB, and IANA- RTPROTO-MIB - Haberman, Wasserman Expires February 2004 2 Changed reference to RFC 2096 from normative to informative Added RFC editor note to remove Revision History at publication time Updated REVISION clause Added section describing changes from RFC 2096 Added REVISION clause for original publication as RFC + + Haberman Expires July 2004 3 1354 Added MIB Copyright statement to DESCRIPTION Changes from draft-ietf-ipv6-rfc2096-update-02.txt: 16 Jan 2003 Changed lower-case 'h' to upper-case 'H' in hex number. Updated REVISION and LAST UPDATED dates. @@ -143,34 +186,34 @@ 02 Nov 2002 Fixed bugs that caused the MIB not to compile. Changed the type of inetCidrRouteDscp to Dscp. Improved the revision information. Removed inetCidrRouteNumber and inetCidrRouteWeight. Other editorial changes. - Haberman, Wasserman Expires February 2004 3 Changes from draft-ietf-ipv6-rfc-2096-update-00.txt: 22 Aug 2002 Minor editorial changes and clean-up Changes from draft-ietf-ipngwg-rfc2096-update-00.txt: 27 Jun 2002 Added inetCidrRouteDscp index and inetCidrRouteWeight object to the inetCidrRouteTable. Restored inetCidrRouteNextHopType variable (may be different from inetCidrRouteDestType, due to global vs. non-global distinction in new InetAddress TCs). + Haberman Expires July 2004 4 Removed inetCidrRouteInstance object. Use to identify a conceptual routing table is obviated by new InetAddress types and inclusion of DSCP index. Changed editor, moved author information to end, several editorial changes. Changed name to draft-ietf-ipv6-rfc-2096-update-*.txt 13 Jul 2002 Removed inetCidrRouteNextHopType. @@ -190,149 +233,174 @@ Deleted inetCidrRouteTos, add inetCidrRouteInstance in INDEX of inetCidrRouteTable. Used InterfaceIndex, InetAddressPrefixLength and InetAutonomousSystemNumber TC's, and limited the SIZE of inetCidrRouteDest and inetCidrRouteNextHop Updated conformance info. Added copyright and table of contents. - Haberman, Wasserman Expires February 2004 4 - 1 Conventions Used In This Document + Haberman Expires July 2004 5 + 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]. - 2 The Internet-Standard Management Framework + 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]. - 3 Overview + 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. - In addition, there is one deprecated table and object, and one - obsolete table and object, representing previous revisions of this - MIB. + 4.1 Relationship to other MIBs - 1. The obsolete object ipForwardNumber represents the number of - entries in the obsolete ipForwardTable. + Haberman Expires July 2004 6 + This MIB definition contains several deprecated and obsolete tables + and objects. The following subsections describe the relationship + between these objects and other MIB modules. - 2. The obsolete ipForwardTable updates the RFC 1213 - ipRouteTable to display multipath IP Routes. This is in - turn obsoleted by the ipCidrRouteTable. + 4.1.1 RFC 1213 - 3. The deprecated object ipCidrRouteNumber represents the - number of entries in the deprecated ipCidrRouteTable. + The ipRouteTable object was originally defined in RFC 1213. It was + updated by ipForwardTable in RFC 1354. - Haberman, Wasserman Expires February 2004 5 - 4. The deprecated ipCidrRouteTable updates the RFC 1213 - ipRouteTable to display multipath IP Routes having the same - network number but differing network masks. + 4.1.2 RFC 1354 - Haberman, Wasserman Expires February 2004 6 - 4 Definitions + The ipForwardTable object replaced the ipRouteTable object from RFC + 1213. It was in turn obsoleted by the ipCidrRouteTable defined in + RFC 2096. + + In addition, RFC 1354 introduced ipForwardNumber. This object + reflects the number of entries found in ipForwardTable. It was + obsoleted by ipCidrRouteNumber, defined in RFC 2096. + + 4.1.3 RFC 2096 + + In RFC 2096, the ipCidrRouteTable and ipCidrRouteNumber were + introduced. The ipCidrRouteTable object supports multipath IP + routes having the same network number but differing network masks. + The number of entries in that table is reflected in + ipCidrRouteNumber. These objects are deprecated by the definitions + contained in this MIB definition. + + 4.1.4 RFC 2011 and 2465 + + RFC 2011 contains the ipRoutingDiscards object which counts the + number of valid routes which have been removed from the + ipCidrRouteTable object. The corresponding ipv6DiscardedRoutes + object is defined in RFC 2465. These objects are deprecated in + favor of the version-independent object inetCidrRouteDiscards + defined in this MIB. + + Haberman Expires July 2004 7 + 5 Definitions IP-FORWARD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Integer32, Gauge32, Counter32 FROM SNMPv2-SMI RowStatus FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF InterfaceIndex FROM IF-MIB ip FROM IP-MIB IANAipRouteProtocol FROM IANA-RTPROTO-MIB InetAddress, InetAddressType, InetAddressPrefixLength, InetAutonomousSystemNumber FROM INET-ADDRESS-MIB; ipForward MODULE-IDENTITY - LAST-UPDATED "200308281500Z" + LAST-UPDATED "200401281200Z" ORGANIZATION "IETF IPv6 Working Group http://www.ietf.org/html.charters/ipv6-charter.html" CONTACT-INFO "Editor: - Margaret Wasserman - Wind River - 10 Tara Blvd, Suite 330 - Nashua, NH 03062 - - Phone: +1 603 897-2067 - Email: mrw@windriver.com - Brian Haberman Caspian Networks 753 Bridgewater Drive Sykesville, MD 21784 Phone: +1 410 552-1421 Email: brian@innovationslab.net - Send comments to " - -- RFC Ed: please verify mailing list address at publication - -- and delete this note + Send comments to " DESCRIPTION "The MIB module for the management of CIDR multipath IP Routes. - Copyright (C) The Internet Society (2003). This version + Copyright (C) The Internet Society (2004). This version of this MIB module is a part of RFC xxxx; see the RFC itself for full legal notices." -- RFC Ed : replace xxxx with actual RFC number & remove note - REVISION "200308281500Z" - - Haberman, Wasserman Expires February 2004 7 + REVISION "200401281200Z" DESCRIPTION "IPv4/v6 version-independent revision. Minimal changes were made to the original RFC 2096 MIB, to allow easy upgrade of existing IPv4 implementations to the version-independent MIB. These changes include: Adding inetCidrRouteDiscards as a replacement for the deprecated ipRoutingDiscards and ipv6DiscardedRoutes objects. + Haberman Expires July 2004 8 Adding a new conformance statement to support the implementation of the IP Forwarding MIB in a read-only mode. + The inetCidrRouteTable replaces the IPv4-specific + ipCidrRouteTable, its related objects, and related + conformance statements. + Published as RFC xxxx." -- RFC Ed : replace xxxx with actual RFC number & remove note REVISION "199609190000Z" DESCRIPTION "Revised to support CIDR routes. Published as RFC 2096." REVISION "199207022156Z" DESCRIPTION @@ -346,51 +414,53 @@ DESCRIPTION "The number of current inetCidrRouteTable entries that are not invalid." ::= { ipForward 6 } inetCidrRouteDiscards OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "The number of entries in the inetCidrRouteTable which - were chosen to be discarded even though they are valid. - One possible reason for discarding such an entry could - be to free-up buffer space for other routing entries." + "The number of valid route entries discarded from + inetCidrRouteTable. Discarded route entries do not + appear in inetCidrRouteTable. One possible reason for + discarding an entry would be to free-up buffer space + for other route table entries." ::= { ipForward 8 } -- Inet CIDR Route Table -- The Inet CIDR Route Table deprecates and replaces the -- ipCidrRoute Table currently in the IP Forwarding Table MIB. -- It adds IP protocol independence. inetCidrRouteTable OBJECT-TYPE - - Haberman, Wasserman Expires February 2004 8 SYNTAX SEQUENCE OF InetCidrRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entity's IP Routing table." + + Haberman Expires July 2004 9 REFERENCE "RFC 1213 Section 6.6, The IP Group" ::= { ipForward 7 } inetCidrRouteEntry OBJECT-TYPE SYNTAX InetCidrRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A particular route to a particular destination, under a - particular policy. + particular policy (as reflected in the + inetCidrRoutePolicy object). Dynamically created rows will survive an agent reboot. Implementers need to be aware that if the total number of elements (octets or sub-identifiers) in inetCidrRouteDest, inetCidrRoutePolicy, and inetCidrRouteNextHop exceeds 111 then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3." @@ -415,132 +485,154 @@ inetCidrRouteType INTEGER, inetCidrRouteProto IANAipRouteProtocol, inetCidrRouteAge Gauge32, inetCidrRouteNextHopAS InetAutonomousSystemNumber, inetCidrRouteMetric1 Integer32, inetCidrRouteMetric2 Integer32, inetCidrRouteMetric3 Integer32, inetCidrRouteMetric4 Integer32, inetCidrRouteMetric5 Integer32, inetCidrRouteStatus RowStatus - - Haberman, Wasserman Expires February 2004 9 } inetCidrRouteDestType OBJECT-TYPE SYNTAX InetAddressType + + Haberman Expires July 2004 10 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The type of the inetCidrRouteDest address, as defined - in the InetAddress MIB [RFC3291]." + in the InetAddress MIB. + + Only those address types that may appear in an actual + routing table are allowed as values of this object." + REFERENCE "RFC 3291" ::= { inetCidrRouteEntry 1 } inetCidrRouteDest OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The destination IP address of this route. - Any assignment (implicit or otherwise) of an instance - of this object to a value x MUST be rejected if the - bitwise logical-AND of x with the value of the mask - formed from the corresponding instance of the - inetCidrRoutePfxLen object is not equal to x." + The type of this address is determined by the value of + the inetCidrRouteDestType object. + + The values for the index objects inetCidrRouteDest and + inetCidrRoutePfxLen must be consistent. When the value + of inetCidrRouteDest is x, then the bitwise logical-AND + of x with the value of the mask formed from the + corresponding index object inetCidrRoutePfxLen MUST be + equal to x. If not, then the index pair is not + consistent and an inconsistentName error must be + returned on SET or CREATE requests." ::= { inetCidrRouteEntry 2 } inetCidrRoutePfxLen OBJECT-TYPE - SYNTAX InetAddressPrefixLength + SYNTAX InetAddressPrefixLength (0..128) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the number of leading one bits which form the mask to be logical-ANDed with the destination address before being compared to the value in the inetCidrRouteDest field. - Any assignment (implicit or otherwise) of an instance - of this object to a value x MUST be rejected if the - bitwise logical-AND of the mask formed from x with the - value of the corresponding instance of the - inetCidrRouteDest object is not equal to - inetCidrRouteDest." + The values for the index objects inetCidrRouteDest and + inetCidrRoutePfxLen must be consistent. When the value + of inetCidrRouteDest is x, then the bitwise logical-AND + of x with the value of the mask formed from the + corresponding index object inetCidrRoutePfxLen MUST be + equal to x. If not, then the index pair is not + consistent and an inconsistentName error must be + returned on SET or CREATE requests." ::= { inetCidrRouteEntry 3 } inetCidrRoutePolicy OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS not-accessible + + Haberman Expires July 2004 11 STATUS current DESCRIPTION - "Represents the general set of conditions that would - cause the selection of one multipath route (set of next - hops for a given destination) over another (referred to - as policy). The value { 0 0 } shall be used for the - default policy or if no particular policy applies." + "This object is an opaque object without any defined + semantics. Its purpose is to serve as an additional + index which may delineate between multiple entries to + the same destination. The value { 0 0 } shall be used + as the default value for this object." ::= { inetCidrRouteEntry 4 } - Haberman, Wasserman Expires February 2004 10 inetCidrRouteNextHopType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "The type of the inetCidrRouteNextHop address, as - defined in the InetAddress MIB [RFC3291]. + defined in the InetAddress MIB. Value should be set to unknown(0) for non-remote - routes." + routes. + + Only those address types that may appear in an actual + routing table are allowed as values of this object." + REFERENCE "RFC 3291" ::= { inetCidrRouteEntry 5 } inetCidrRouteNextHop OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "On remote routes, the address of the next system en - route. For non-remote routes, a zero length string." + route. For non-remote routes, a zero length string. + + The type of this address is determined by the value of + the inetCidrRouteNextHopType object." ::= { inetCidrRouteEntry 6 } inetCidrRouteIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The ifIndex value which identifies the local interface through which the next hop of this route should be - reached." + reached. A value of 0 is valid and represents the + scenario where no interface is specified." ::= { inetCidrRouteEntry 7 } inetCidrRouteType OBJECT-TYPE SYNTAX INTEGER { other (1), -- not specified by this MIB reject (2), -- route which discards traffic and -- returns ICMP notification local (3), -- local interface + + Haberman Expires July 2004 12 remote (4), -- remote destination blackhole(5) -- route which discards traffic -- silently } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4)refers to a route for which the next hop is not the final destination. Routes which do not result in traffic forwarding or rejection should not be displayed even if the implementation keeps them stored internally. - Haberman, Wasserman Expires February 2004 11 reject(2) refers to a route which, if matched, discards the message as unreachable and returns a notification (e.g. ICMP error) to the message sender. This is used in some protocols as a means of correctly aggregating routes. blackhole(5) refers to a route which, if matched, discards the message silently." ::= { inetCidrRouteEntry 8 } @@ -565,38 +657,38 @@ semantics of 'too old' can be implied except through knowledge of the routing protocol by which the route was learned." ::= { inetCidrRouteEntry 10 } inetCidrRouteNextHopAS OBJECT-TYPE SYNTAX InetAutonomousSystemNumber MAX-ACCESS read-create STATUS current DESCRIPTION + + Haberman Expires July 2004 13 "The Autonomous System Number of the Next Hop. The semantics of this object are determined by the routing- protocol specified in the route's inetCidrRouteProto value. When this object is unknown or not relevant its value should be set to zero." DEFVAL { 0 } ::= { inetCidrRouteEntry 11 } inetCidrRouteMetric1 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The primary routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's inetCidrRouteProto - - Haberman, Wasserman Expires February 2004 12 value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { inetCidrRouteEntry 12 } inetCidrRouteMetric2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION @@ -621,38 +713,38 @@ DEFVAL { -1 } ::= { inetCidrRouteEntry 14 } inetCidrRouteMetric4 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing- + + Haberman Expires July 2004 14 protocol specified in the route's inetCidrRouteProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { inetCidrRouteEntry 15 } inetCidrRouteMetric5 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's inetCidrRouteProto value. If this metric is not used, its value should be set to -1." - - Haberman, Wasserman Expires February 2004 13 DEFVAL { -1 } ::= { inetCidrRouteEntry 16 } inetCidrRouteStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The row status variable, used according to row installation and removal conventions. @@ -671,44 +763,85 @@ ipForwardCompliances OBJECT IDENTIFIER ::= { ipForwardConformance 2 } -- Compliance statements ipForwardFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented for read-create, the - implementation can claim full compliance." + implementation can claim full compliance. + + There are a number of INDEX objects that cannot be + represented in the form of OBJECT clauses in SMIv2, + but for which there are compliance requirements, + expressed in OBJECT clause form in this description: + + Haberman Expires July 2004 15 + -- OBJECT inetCidrRouteDestType + -- SYNTAX InetAddressType (ipv4(1), ipv6(2), + -- ipv4z(3), ipv6z(4)) + -- DESCRIPTION + -- This MIB requires support for global and + -- non-global ipv4 and ipv6 addresses. + -- + -- OBJECT inetCidrRouteDest + -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) + -- DESCRIPTION + -- This MIB requires support for global and + -- non-global IPv4 and IPv6 addresses. + -- + -- OBJECT inetCidrRouteNextHopType + -- SYNTAX InetAddressType (unknown(0), ipv4(1), + -- ipv6(2), ipv4z(3) + -- ipv6z(4)) + -- DESCRIPTION + -- This MIB requires support for global and + -- non-global ipv4 and ipv6 addresses. + -- + -- OBJECT inetCidrRouteNextHop + -- SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20)) + -- DESCRIPTION + -- This MIB requires support for global and + -- non-global IPv4 and IPv6 addresses. + " + MODULE -- this module MANDATORY-GROUPS { inetForwardCidrRouteGroup } + + OBJECT inetCidrRouteStatus + SYNTAX RowStatus { active(1), notInService (2) } + WRITE-SYNTAX RowStatus { active(1), notInService (2), + createAndGo(4), destroy(6) } + DESCRIPTION "Support for createAndWait is not required." + ::= { ipForwardCompliances 3 } ipForwardReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "When this MIB is implemented without support for read- create (i.e. in read-only mode), the implementation can claim read-only compliance." MODULE -- this module MANDATORY-GROUPS { inetForwardCidrRouteGroup } OBJECT inetCidrRouteIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required." + Haberman Expires July 2004 16 OBJECT inetCidrRouteType MIN-ACCESS read-only DESCRIPTION - - Haberman, Wasserman Expires February 2004 14 "Write access is not required." OBJECT inetCidrRouteNextHopAS MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT inetCidrRouteMetric1 MIN-ACCESS read-only DESCRIPTION @@ -728,43 +861,45 @@ MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT inetCidrRouteMetric5 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT inetCidrRouteStatus + SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { ipForwardCompliances 4 } -- units of conformance inetForwardCidrRouteGroup OBJECT-GROUP OBJECTS { inetCidrRouteDiscards, inetCidrRouteIfIndex, inetCidrRouteType, inetCidrRouteProto, inetCidrRouteAge, inetCidrRouteNextHopAS, inetCidrRouteMetric1, inetCidrRouteMetric2, inetCidrRouteMetric3, inetCidrRouteMetric4, inetCidrRouteMetric5, inetCidrRouteStatus, inetCidrRouteNumber } + + Haberman Expires July 2004 17 STATUS current DESCRIPTION "The IP version-independent CIDR Route Table." ::= { ipForwardGroups 4 } - Haberman, Wasserman Expires February 2004 15 -- Deprecated Objects ipCidrRouteNumber OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of current ipCidrRouteTable entries that are not invalid. This object is deprecated in favor of inetCidrRouteNumber and the inetCidrRouteTable." @@ -800,26 +935,26 @@ INDEX { ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, ipCidrRouteNextHop } ::= { ipCidrRouteTable 1 } IpCidrRouteEntry ::= SEQUENCE { ipCidrRouteDest IpAddress, + + Haberman Expires July 2004 18 ipCidrRouteMask IpAddress, ipCidrRouteTos Integer32, ipCidrRouteNextHop IpAddress, ipCidrRouteIfIndex Integer32, - - Haberman, Wasserman Expires February 2004 16 ipCidrRouteType INTEGER, ipCidrRouteProto INTEGER, ipCidrRouteAge Integer32, ipCidrRouteInfo OBJECT IDENTIFIER, ipCidrRouteNextHopAS Integer32, ipCidrRouteMetric1 Integer32, ipCidrRouteMetric2 Integer32, ipCidrRouteMetric3 Integer32, ipCidrRouteMetric4 Integer32, ipCidrRouteMetric5 Integer32, @@ -856,26 +991,26 @@ reference to the IP Address Class. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipCidrRouteDest object is not equal to ipCidrRouteDest." ::= { ipCidrRouteEntry 2 } -- The following convention is included for specification + + Haberman Expires July 2004 19 -- of TOS Field contents. At this time, the Host Requirements -- and the Router Requirements documents disagree on the width -- of the TOS field. This mapping describes the Router -- Requirements mapping, and leaves room to widen the TOS field - - Haberman, Wasserman Expires February 2004 17 -- without impact to fielded systems. ipCidrRouteTos OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific @@ -913,25 +1048,24 @@ SYNTAX Integer32 MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The ifIndex value which identifies the local interface through which the next hop of this route should be reached." DEFVAL { 0 } ::= { ipCidrRouteEntry 5 } + Haberman Expires July 2004 20 ipCidrRouteType OBJECT-TYPE SYNTAX INTEGER { other (1), -- not specified by this MIB - - Haberman, Wasserman Expires February 2004 18 reject (2), -- route which discards traffic local (3), -- local interface remote (4) -- remote destination } MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is @@ -968,26 +1102,26 @@ bgp (14), -- Border Gateway Protocol idpr (15), -- InterDomain Policy Routing ciscoEigrp (16) -- Cisco EIGRP } MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those + + Haberman Expires July 2004 21 protocols." ::= { ipCidrRouteEntry 7 } ipCidrRouteAge OBJECT-TYPE - - Haberman, Wasserman Expires February 2004 19 SYNTAX Integer32 MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned." DEFVAL { 0 } @@ -1024,25 +1158,26 @@ ipCidrRouteMetric1 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The primary routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be + + Haberman Expires July 2004 22 set to -1." DEFVAL { -1 } ::= { ipCidrRouteEntry 11 } - Haberman, Wasserman Expires February 2004 20 ipCidrRouteMetric2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS deprecated DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1." @@ -1079,80 +1214,87 @@ SYNTAX Integer32 MAX-ACCESS read-create STATUS deprecated DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipCidrRouteProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } + + Haberman Expires July 2004 23 ::= { ipCidrRouteEntry 15 } ipCidrRouteStatus OBJECT-TYPE SYNTAX RowStatus - - Haberman, Wasserman Expires February 2004 21 MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The row status variable, used according to row installation and removal conventions." ::= { ipCidrRouteEntry 16 } -- compliance statements ipForwardCompliance MODULE-COMPLIANCE STATUS deprecated DESCRIPTION "The compliance statement for SNMPv2 entities which - implement the ipForward MIB." + implement the ipForward MIB. + + This compliance statement has been deprecated and + replaced with ipForwardFullCompliance and + ipForwardReadOnlyCompliance." MODULE -- this module MANDATORY-GROUPS { ipForwardCidrRouteGroup } ::= { ipForwardCompliances 1 } -- units of conformance ipForwardCidrRouteGroup OBJECT-GROUP OBJECTS { ipCidrRouteNumber, ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, ipCidrRouteNextHop, ipCidrRouteIfIndex, ipCidrRouteType, ipCidrRouteProto, ipCidrRouteAge, ipCidrRouteInfo,ipCidrRouteNextHopAS, ipCidrRouteMetric1, ipCidrRouteMetric2, ipCidrRouteMetric3, ipCidrRouteMetric4, ipCidrRouteMetric5, ipCidrRouteStatus } STATUS deprecated DESCRIPTION - "The CIDR Route Table." + "The CIDR Route Table. + + This group has been deprecated and replaced with + inetForwardCidrRouteGroup." ::= { ipForwardGroups 3 } -- Obsoleted Definitions - Objects ipForwardNumber OBJECT-TYPE SYNTAX Gauge32 + + Haberman Expires July 2004 24 MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The number of current ipForwardTable entries that are not invalid." ::= { ipForward 1 } -- IP Forwarding Table -- The IP Forwarding Table obsoletes and replaces the ipRoute -- Table current in MIB-I and MIB-II. It adds knowledge of - - Haberman, Wasserman Expires February 2004 22 -- the autonomous system of the next hop, multiple next hop -- support, and policy routing support. ipForwardTable OBJECT-TYPE SYNTAX SEQUENCE OF IpForwardEntry MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION "This entity's IP Routing table." REFERENCE @@ -1182,32 +1324,33 @@ ipForwardIfIndex Integer32, ipForwardType INTEGER, ipForwardProto INTEGER, ipForwardAge Integer32, ipForwardInfo OBJECT IDENTIFIER, ipForwardNextHopAS Integer32, ipForwardMetric1 Integer32, ipForwardMetric2 Integer32, ipForwardMetric3 Integer32, ipForwardMetric4 Integer32, + + Haberman Expires July 2004 25 ipForwardMetric5 Integer32 } ipForwardDest OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. - Haberman, Wasserman Expires February 2004 23 This object may not take a Multicast (Class D) address value. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipForwardMask object is not equal to x." ::= { ipForwardEntry 1 } @@ -1237,32 +1380,33 @@ -- of the TOS field. This mapping describes the Router -- Requirements mapping, and leaves room to widen the TOS field -- without impact to fielded systems. ipForwardPolicy OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The general set of conditions that would cause + + Haberman Expires July 2004 26 the selection of one multipath route (set of next hops for a given destination) is referred to as 'policy'. Unless the mechanism indicated by ipForwardProto specifies otherwise, the policy specifier is the IP TOS Field. The encoding of IP TOS is as specified by the following convention. Zero indicates the default path if no more specific policy applies. - Haberman, Wasserman Expires February 2004 24 +-----+-----+-----+-----+-----+-----+-----+-----+ | | | | | PRECEDENCE | TYPE OF SERVICE | 0 | | | | | +-----+-----+-----+-----+-----+-----+-----+-----+ IP TOS IP TOS Field Policy Field Policy Contents Code Contents Code 0 0 0 0 ==> 0 0 0 0 1 ==> 2 @@ -1290,33 +1434,33 @@ route; Otherwise, 0.0.0.0." ::= { ipForwardEntry 4 } ipForwardIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS obsolete DESCRIPTION "The ifIndex value which identifies the local interface through which the next hop of this route should be + + Haberman Expires July 2004 27 reached." DEFVAL { 0 } ::= { ipForwardEntry 5 } ipForwardType OBJECT-TYPE SYNTAX INTEGER { other (1), -- not specified by this MIB invalid (2), -- logically deleted local (3), -- local interface remote (4) -- remote destination } - - Haberman, Wasserman Expires February 2004 25 MAX-ACCESS read-create STATUS obsolete DESCRIPTION "The type of route. Note that local(3) refers to a route for which the next hop is the final destination; remote(4) refers to a route for which the next hop is not the final destination. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the @@ -1346,33 +1490,33 @@ ggp (6), -- Gateway-Gateway Protocol hello (7), -- FuzzBall HelloSpeak rip (8), -- Berkeley RIP or RIP-II is-is (9), -- Dual IS-IS es-is (10), -- ISO 9542 ciscoIgrp (11), -- Cisco IGRP bbnSpfIgp (12), -- BBN SPF IGP ospf (13), -- Open Shortest Path First bgp (14), -- Border Gateway Protocol idpr (15) -- InterDomain Policy Routing + + Haberman Expires July 2004 28 } MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols." ::= { ipForwardEntry 7 } ipForwardAge OBJECT-TYPE - - Haberman, Wasserman Expires February 2004 26 SYNTAX Integer32 MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned." DEFVAL { 0 } @@ -1402,33 +1546,33 @@ "The Autonomous System Number of the Next Hop. When this is unknown or not relevant to the protocol indicated by ipForwardProto, zero." DEFVAL { 0 } ::= { ipForwardEntry 10 } ipForwardMetric1 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS obsolete + + Haberman Expires July 2004 29 DESCRIPTION "The primary routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipForwardEntry 11 } ipForwardMetric2 OBJECT-TYPE SYNTAX Integer32 - - Haberman, Wasserman Expires February 2004 27 MAX-ACCESS read-create STATUS obsolete DESCRIPTION "An alternate routing metric for this route. The semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipForwardEntry 12 } @@ -1458,33 +1602,33 @@ -1." DEFVAL { -1 } ::= { ipForwardEntry 14 } ipForwardMetric5 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS obsolete DESCRIPTION "An alternate routing metric for this route. The + + Haberman Expires July 2004 30 semantics of this metric are determined by the routing- protocol specified in the route's ipForwardProto value. If this metric is not used, its value should be set to -1." DEFVAL { -1 } ::= { ipForwardEntry 15 } -- Obsoleted Definitions - Groups -- compliance statements ipForwardOldCompliance MODULE-COMPLIANCE - - Haberman, Wasserman Expires February 2004 28 STATUS obsolete DESCRIPTION "The compliance statement for SNMP entities which implement the ipForward MIB." MODULE -- this module MANDATORY-GROUPS { ipForwardMultiPathGroup } ::= { ipForwardCompliances 2 } @@ -1497,22 +1641,22 @@ ipForwardMetric1, ipForwardMetric2, ipForwardMetric3, ipForwardMetric4, ipForwardMetric5 } STATUS obsolete DESCRIPTION "IP Multipath Route Table." ::= { ipForwardGroups 2 } END - Haberman, Wasserman Expires February 2004 29 - 5 Security Considerations + Haberman Expires July 2004 31 + 6 Security Considerations There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: 1. The inetCidrRouteTable contains routing and forwarding @@ -1550,22 +1694,22 @@ authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. - Haberman, Wasserman Expires February 2004 30 - 6 Intellectual Property + Haberman Expires July 2004 32 + 7 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances @@ -1573,34 +1717,40 @@ to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. - 7 Changes from RFC 2096 + 8 Changes from RFC 2096 This document updates RFC 2096 in the following ways: - 1. Utilized the InetAddress TC to support IP version-independent + 1. Replaces ipCidrRouteTable with inetCidrRouteTable. This + applies to corresponding objects and conformance statements. + 2. Utilized the InetAddress TC to support IP version-independent implementations of the forwarding MIB. This gives common forwarding MIB support for IPv4 and IPv6. - 2. Created a read-only conformance statement to support + 3. Created a read-only conformance statement to support implementations that only wish to retrieve data. - 3. Created the inetCidrRouteDiscards object to replace the + 4. Created the inetCidrRouteDiscards object to replace the deprecated ipRoutingDiscards and ipv6DiscardedRoutes objects. - Haberman, Wasserman Expires February 2004 31 - 8 Normative References + The inetCidrRouteTable retains the logical structure of the + ipCidrRouteTable in order to allow the easy upgrade of existing + IPv4 implementations to the version-independent MIB. + + Haberman Expires July 2004 33 + 9 Normative References [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP14, March 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., @@ -1623,84 +1773,80 @@ MIB", RFC 2863, June 2000. [2011upd] Routhier, S., "Management Information Base for the Internet Protocol (IP), draft-ietf-ipv6-rfc2011-update-02.txt, February 2003. [RTPROTO] IANA, "IP Route Protocol MIB", http://www.iana.org/assignments/ianaiprouteprotocol-mib, September 2000. - 9 Informative References + 10 Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC2096] Baker, F., "IP Forwarding Table MIB", RFC 2096, January 1997. - Haberman, Wasserman Expires February 2004 32 - 10 Authors and Acknowledgements + Haberman Expires July 2004 34 + 11 Authors and Acknowledgements This document was based on RFC 2096 [RFC2096]. The following people provided text for this version of the document, or were authors of previous versions: Fred Baker, Cisco Bill Fenner, AT&T Research Brian Haberman, Caspian Networks Juergen Schoenwalder, TU Braunschweig Dave Thaler, Microsoft - Margaret Wasserman, Wind River + Margaret Wasserman, Thingmagic Dario Accornero, Mark Adam, Qing Li and Shawn Routhier reviewed the document and provided helpful feedback. Mike Heard provided valuable feedback as the MIB Doctor for this document. - 11 Editors' Contact Information + 12 Editors' Contact Information Comments or questions regarding this document should be sent to: Brian Haberman Caspian Networks 753 Bridgewater Drive Phone: +1 410-552-1421 Sykesville, MD 21784 USA Email: brian@innovationslab.net - Margaret Wasserman - Wind River - 10 Tara Blvd., Suite 330 Phone: +1 603-897-2067 - Nashua, NH 03062 USA Email: mrw@windriver.com - - 12 Full Copyright Statement + 13 Full Copyright Statement - Copyright (C) The Internet Society (2003). All Rights Reserved. + Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. - Haberman, Wasserman Expires February 2004 33 The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET + + Haberman Expires July 2004 35 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. - Haberman, Wasserman Expires February 2004 34 + Haberman Expires July 2004 36