idnits 2.17.1 draft-ietf-ipv6-rfc2096-update-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 35 longer pages, the longest (page 1) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) -- The abstract seems to indicate that this document obsoletes RFC2096, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1067 has weird spacing: '...ntifies the l...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 2004) is 7366 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3291' is defined on line 1778, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 1786, but no explicit reference was found in the text == Unused Reference: '2011upd' is defined on line 1789, but no explicit reference was found in the text == Unused Reference: 'RTPROTO' is defined on line 1793, but no explicit reference was found in the text == Outdated reference: A later version (-10) exists of draft-ietf-ipv6-rfc2011-update-02 -- Possible downref: Non-RFC (?) normative reference: ref. 'RTPROTO' -- Obsolete informational reference (is this intentional?): RFC 2096 (Obsoleted by RFC 4292) Summary: 2 errors (**), 0 flaws (~~), 10 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft B. Haberman 3 draft-ietf-ipv6-rfc2096-update-07.txt Caspian Networks 4 Expires: August 2004 February 2004 6 IP Forwarding Table MIB 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as Internet- 16 Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six 19 months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet-Drafts 21 as reference material or to cite them other than as "work in 22 progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This document is a product of the IPv6 MIB Revision Design Team and 30 it is a working item of the IPv6 Working Group. Comments should be 31 addressed to the editors, or to the IPv6 Working Group mailing list 32 at ipv6@ietf.org. 34 Abstract 36 This document defines a portion of the Management Information Base 37 (MIB) for use with network management protocols in the Internet 38 community. In particular, it describes managed objects related to 39 the forwarding of Internet Protocol (IP) packets in an IP version- 40 independent manner. This document obsoletes RFC 2096. 42 Copyright Notice 44 Copyright (C) The Internet Society (2004). All Rights Reserved. 46 Haberman Expires August 2004 1 47 Table of Contents 49 1 Conventions Used In This Document..............................6 50 2 The Internet-Standard Management Framework.....................6 51 3 Overview.......................................................6 52 4 Definitions....................................................8 53 5 Security Considerations.......................................32 54 6 Intellectual Property Statement...............................33 55 7 Changes from RFC 2096.........................................33 56 8 Normative References..........................................34 57 9 Informative References........................................34 58 10 Authors and Acknowledgements..................................35 59 11 Editors' Contact Information..................................35 60 12 Full Copyright Statement......................................35 62 Revision History 64 [Note to RFC Editor: Please remove prior to publication] 66 Changes from draft-ietf-ipv6-rfc2096-update-06.txt: 68 09 Feb 2004 Removed range from inetCidrRoutePfxLen 70 Clarified text in DESCRIPTION clause of 71 inetCidrRoutePfxLen and inetCidrRouteDest to exclude 72 bit-wise comparison of zone indexes 74 Changed syntax of inetCidrRouteIfIndex to 75 InterfaceIndexOrZero 77 Changes from draft-ietf-ipv6-rfc2096-update-05.txt: 79 07 Jan 2004 Corrected editor information 81 Changed mailing list information 83 Limited InetAddress objects to (ipv4, ipv6, ipv4z, 84 ipv6z) 86 Updated MODULE-IDENTITY REVISION clause to detail the 87 replacement of ipCidrRouteTable with 88 inetCidrRouteTable 90 Updated DESCRIPTION clause of ipForwardCompliance to 91 indicate the replacement of ipForwardCompliance with 92 ipForwardFullCompliance and 93 ipForwardReadOnlyCompliance 95 Added statement to DESCRIPTION clause of 96 ipForwardCidrRouteGroup pointing out its replacement 98 Haberman Expires July 2004 2 99 with inetForwardCidrRouteGroup 101 Added detail to section 3 on relationship of this MIB 102 with previous versions 104 Fixed references within DESCRIPTION clauses 106 Added SYNTAX statements to read-only OBJECTs 108 21 Jan 2004 Added clarifying text to Introduction on the usage of 109 the MIB definition 111 Enhanced Overview section to include explicit text on 112 relationship to other RFCs 114 Clarified DESCRIPTION text for inetCidrRouteDiscards 116 Added text to DESCRIPTION clause of 117 inetCidrRouteIfIndex to allow the value of 0 119 28 Jan 2004 Added range of (0..128) to inetCidrRoutePfxLen 121 Changes from draft-ietf-ipv6-rfc2096-update-04.txt: 123 28 Aug 2003 Corrected copyright statement in DESCRIPTION clause 125 Added inetCidrRouteNumber to 126 inetForwardCidrRouteGroup conformance statement 128 Removed SIZE constraints for inetCidrRouteDest and 129 inetCidrRouteNextHop 131 Added constraints statement to DESCRIPTION clause of 132 inetCidrRouteEntry 134 Added Intellectual Property section per requirements 135 of RFC 2026 137 Removed reference to RFC 2026 139 Removed ipForwardCompliance2 141 Changed definition of inetCidrRouteAge from Integer32 142 to Gauge32 144 Changes from draft-ietf-ipv6-rfc2096-update-03.txt: 146 27 Jun 2003 Updated text to DESCRIPTION of inetCidrRouteDiscards 148 Re-instated inetCidrRouteNumber 150 Added references for IF-MIB, IP-MIB, and IANA- 152 Haberman Expires July 2004 3 153 RTPROTO-MIB 155 Changed reference to RFC 2096 from normative to 156 informative 158 Added RFC editor note to remove Revision History at 159 publication time 161 Updated REVISION clause 163 Added section describing changes from RFC 2096 165 Added REVISION clause for original publication as RFC 166 1354 168 Added MIB Copyright statement to DESCRIPTION 170 Changes from draft-ietf-ipv6-rfc2096-update-02.txt: 172 16 Jan 2003 Changed lower-case 'h' to upper-case 'H' in hex 173 number. 175 Updated REVISION and LAST UPDATED dates. 176 13 Jun 2003 Changed inetCidrRouteDscp to inetCidrRoutePolicy. 178 Updated MIB Boilerplate. 179 17 Jun 2003 Added read-only compliance statement. 181 Added text to DESCRIPTION clause for 182 inetCidrRouteStatus to indicate a row cannot be 183 modified when it is active. 185 Removed numbered references from DESCRIPTION clauses. 187 Removed Unsigned32 from IMPORTS list. 189 Changed section numbers to conform with ID-nits. 191 Split references into normative/informative. 193 Updated security section. 195 Changes from draft-ietf-ipv6-rfc2096-update-01.txt: 197 02 Nov 2002 Fixed bugs that caused the MIB not to compile. 199 Changed the type of inetCidrRouteDscp to Dscp. 201 Improved the revision information. 203 Removed inetCidrRouteNumber and inetCidrRouteWeight. 205 Other editorial changes. 207 Haberman Expires July 2004 4 208 Changes from draft-ietf-ipv6-rfc-2096-update-00.txt: 210 22 Aug 2002 Minor editorial changes and clean-up 212 Changes from draft-ietf-ipngwg-rfc2096-update-00.txt: 214 27 Jun 2002 Added inetCidrRouteDscp index and inetCidrRouteWeight 215 object to the inetCidrRouteTable. 217 Restored inetCidrRouteNextHopType variable (may be 218 different from inetCidrRouteDestType, due to global 219 vs. non-global distinction in new InetAddress TCs). 221 Removed inetCidrRouteInstance object. Use to identify 222 a conceptual routing table is obviated by new 223 InetAddress types and inclusion of DSCP index. 225 Changed editor, moved author information to end, 226 several editorial changes. 228 Changed name to draft-ietf-ipv6-rfc-2096-update-*.txt 229 13 Jul 2002 Removed inetCidrRouteNextHopType. 231 Changes from draft-ops-rfc2096-update-00.txt: 233 12 Jul 2001 Renamed to IPNG working group draft 234 Added scopes to the uses of instance 235 Added inetCidrRouteDiscards to replace 236 ipRoutingDiscards 237 Fixed some remaining ipCidr*/inetCidr* confusion in 238 DESCRIPTIONs 240 Changes from first draft posted to v6mib mailing list: 242 23 Feb 2001 Updated MODULE-IDENTITY 244 Deleted inetCidrRouteTos, add inetCidrRouteInstance 245 in INDEX of inetCidrRouteTable. 247 Used InterfaceIndex, InetAddressPrefixLength and 248 InetAutonomousSystemNumber TC's, and limited the SIZE 249 of inetCidrRouteDest and inetCidrRouteNextHop 251 Updated conformance info. Added copyright and table 252 of contents. 254 Haberman Expires July 2004 5 255 1 Introduction 257 This document defines a portion of the Management Information Base 258 (MIB) for use in managing objects related to the forwarding of 259 Internet Protocol (IP) packets in an IP version-independent manner. 261 It should be noted that the MIB definition described herein does 262 not support multiple instances based on the same address family 263 type. However, it does support an instance of the MIB per address 264 family. 266 2 Conventions Used In This Document 268 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 269 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 270 this document are to be interpreted as described in RFC 2119 271 [RFC2119]. 273 3 The Internet-Standard Management Framework 275 For a detailed overview of the documents that describe the current 276 Internet-Standard Management Framework, please refer to section 7 277 of RFC 3410 [RFC3410]. 279 Managed objects are accessed via a virtual information store, 280 termed the Management Information Base or MIB. MIB objects are 281 generally accessed through the Simple Network Management Protocol 282 (SNMP). Objects in the MIB are defined using the mechanisms 283 defined in the Structure of Management Information (SMI). This 284 memo specifies a MIB module that is compliant to the SMIv2, which 285 is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 286 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 288 4 Overview 290 The MIB consists of one current table and two current global 291 objects. 293 1. The object inetCidrRouteNumber indicates the number of 294 current routes. This is primarily to avoid having to read 295 the table in order to determine this number. 297 2. The object inetCidrRouteDiscards counts the number of valid 298 routes that were discarded from inetCidrRouteTable for any 299 reason. This object replaces the ipRoutingDiscards and 300 ipv6DiscardedRoutes objects. 302 3. The inetCidrRouteTable provides the ability to display IP 303 version-independent multipath CIDR routes. 305 4.1 Relationship to other MIBs 307 Haberman Expires July 2004 6 308 This MIB definition contains several deprecated and obsolete tables 309 and objects. The following subsections describe the relationship 310 between these objects and other MIB modules. 312 4.1.1 RFC 1213 314 The ipRouteTable object was originally defined in RFC 1213. It was 315 updated by ipForwardTable in RFC 1354. 317 4.1.2 RFC 1354 319 The ipForwardTable object replaced the ipRouteTable object from RFC 320 1213. It was in turn obsoleted by the ipCidrRouteTable defined in 321 RFC 2096. 323 In addition, RFC 1354 introduced ipForwardNumber. This object 324 reflects the number of entries found in ipForwardTable. It was 325 obsoleted by ipCidrRouteNumber, defined in RFC 2096. 327 4.1.3 RFC 2096 329 In RFC 2096, the ipCidrRouteTable and ipCidrRouteNumber were 330 introduced. The ipCidrRouteTable object supports multipath IP 331 routes having the same network number but differing network masks. 332 The number of entries in that table is reflected in 333 ipCidrRouteNumber. These objects are deprecated by the definitions 334 contained in this MIB definition. 336 4.1.4 RFC 2011 and 2465 338 RFC 2011 contains the ipRoutingDiscards object which counts the 339 number of valid routes which have been removed from the 340 ipCidrRouteTable object. The corresponding ipv6DiscardedRoutes 341 object is defined in RFC 2465. These objects are deprecated in 342 favor of the version-independent object inetCidrRouteDiscards 343 defined in this MIB. 345 Haberman Expires July 2004 7 346 5 Definitions 348 IP-FORWARD-MIB DEFINITIONS ::= BEGIN 350 IMPORTS 351 MODULE-IDENTITY, OBJECT-TYPE, 352 IpAddress, Integer32, Gauge32, 353 Counter32 FROM SNMPv2-SMI 354 RowStatus FROM SNMPv2-TC 355 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 356 InterfaceIndexOrZero FROM IF-MIB 357 ip FROM IP-MIB 358 IANAipRouteProtocol FROM IANA-RTPROTO-MIB 359 InetAddress, InetAddressType, 360 InetAddressPrefixLength, 361 InetAutonomousSystemNumber FROM INET-ADDRESS-MIB; 363 ipForward MODULE-IDENTITY 364 LAST-UPDATED "200402091200Z" 365 ORGANIZATION 366 "IETF IPv6 Working Group 367 http://www.ietf.org/html.charters/ipv6-charter.html" 368 CONTACT-INFO 369 "Editor: 370 Brian Haberman 371 Caspian Networks 372 753 Bridgewater Drive 373 Sykesville, MD 21784 375 Phone: +1 410 552-1421 376 Email: brian@innovationslab.net 378 Send comments to " 379 DESCRIPTION 380 "The MIB module for the management of CIDR multipath IP 381 Routes. 383 Copyright (C) The Internet Society (2004). This version 384 of this MIB module is a part of RFC xxxx; see the RFC 385 itself for full legal notices." 386 -- RFC Ed : replace xxxx with actual RFC number & remove note 388 REVISION "200402091200Z" 389 DESCRIPTION 390 "IPv4/v6 version-independent revision. Minimal changes 391 were made to the original RFC 2096 MIB, to allow easy 392 upgrade of existing IPv4 implementations to the 393 version-independent MIB. These changes include: 395 Adding inetCidrRouteDiscards as a replacement for the 396 deprecated ipRoutingDiscards and ipv6DiscardedRoutes 397 objects. 399 Haberman Expires July 2004 8 400 Adding a new conformance statement to support the 401 implementation of the IP Forwarding MIB in a 402 read-only mode. 404 The inetCidrRouteTable replaces the IPv4-specific 405 ipCidrRouteTable, its related objects, and related 406 conformance statements. 408 Published as RFC xxxx." 409 -- RFC Ed : replace xxxx with actual RFC number & remove note 411 REVISION "199609190000Z" 412 DESCRIPTION 413 "Revised to support CIDR routes. 414 Published as RFC 2096." 416 REVISION "199207022156Z" 417 DESCRIPTION 418 "Initial version, published as RFC 1354." 419 ::= { ip 24 } 421 inetCidrRouteNumber OBJECT-TYPE 422 SYNTAX Gauge32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The number of current inetCidrRouteTable entries that 427 are not invalid." 428 ::= { ipForward 6 } 430 inetCidrRouteDiscards OBJECT-TYPE 431 SYNTAX Counter32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The number of valid route entries discarded from 436 inetCidrRouteTable. Discarded route entries do not 437 appear in inetCidrRouteTable. One possible reason for 438 discarding an entry would be to free-up buffer space 439 for other route table entries." 440 ::= { ipForward 8 } 442 -- Inet CIDR Route Table 444 -- The Inet CIDR Route Table deprecates and replaces the 445 -- ipCidrRoute Table currently in the IP Forwarding Table MIB. 446 -- It adds IP protocol independence. 448 inetCidrRouteTable OBJECT-TYPE 449 SYNTAX SEQUENCE OF InetCidrRouteEntry 450 MAX-ACCESS not-accessible 451 STATUS current 452 DESCRIPTION 453 "This entity's IP Routing table." 455 Haberman Expires July 2004 9 456 REFERENCE 457 "RFC 1213 Section 6.6, The IP Group" 458 ::= { ipForward 7 } 460 inetCidrRouteEntry OBJECT-TYPE 461 SYNTAX InetCidrRouteEntry 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "A particular route to a particular destination, under a 466 particular policy (as reflected in the 467 inetCidrRoutePolicy object). 469 Dynamically created rows will survive an agent reboot. 471 Implementers need to be aware that if the total number 472 of elements (octets or sub-identifiers) in 473 inetCidrRouteDest, inetCidrRoutePolicy, and 474 inetCidrRouteNextHop exceeds 111 then OIDs of column 475 instances in this table will have more than 128 sub- 476 identifiers and cannot be accessed using SNMPv1, 477 SNMPv2c, or SNMPv3." 478 INDEX { 479 inetCidrRouteDestType, 480 inetCidrRouteDest, 481 inetCidrRoutePfxLen, 482 inetCidrRoutePolicy, 483 inetCidrRouteNextHopType, 484 inetCidrRouteNextHop 485 } 486 ::= { inetCidrRouteTable 1 } 488 InetCidrRouteEntry ::= SEQUENCE { 489 inetCidrRouteDestType InetAddressType, 490 inetCidrRouteDest InetAddress, 491 inetCidrRoutePfxLen InetAddressPrefixLength, 492 inetCidrRoutePolicy OBJECT IDENTIFIER, 493 inetCidrRouteNextHopType InetAddressType, 494 inetCidrRouteNextHop InetAddress, 495 inetCidrRouteIfIndex InterfaceIndexOrZero, 496 inetCidrRouteType INTEGER, 497 inetCidrRouteProto IANAipRouteProtocol, 498 inetCidrRouteAge Gauge32, 499 inetCidrRouteNextHopAS InetAutonomousSystemNumber, 500 inetCidrRouteMetric1 Integer32, 501 inetCidrRouteMetric2 Integer32, 502 inetCidrRouteMetric3 Integer32, 503 inetCidrRouteMetric4 Integer32, 504 inetCidrRouteMetric5 Integer32, 505 inetCidrRouteStatus RowStatus 506 } 508 inetCidrRouteDestType OBJECT-TYPE 509 SYNTAX InetAddressType 511 Haberman Expires July 2004 10 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "The type of the inetCidrRouteDest address, as defined 516 in the InetAddress MIB. 518 Only those address types that may appear in an actual 519 routing table are allowed as values of this object." 520 REFERENCE "RFC 3291" 521 ::= { inetCidrRouteEntry 1 } 523 inetCidrRouteDest OBJECT-TYPE 524 SYNTAX InetAddress 525 MAX-ACCESS not-accessible 526 STATUS current 527 DESCRIPTION 528 "The destination IP address of this route. 530 The type of this address is determined by the value of 531 the inetCidrRouteDestType object. 533 The values for the index objects inetCidrRouteDest and 534 inetCidrRoutePfxLen must be consistent. When the value 535 of inetCidrRouteDest (excluding the zone index, if one 536 is present) is x, then the bitwise logical-AND 537 of x with the value of the mask formed from the 538 corresponding index object inetCidrRoutePfxLen MUST be 539 equal to x. If not, then the index pair is not 540 consistent and an inconsistentName error must be 541 returned on SET or CREATE requests." 543 ::= { inetCidrRouteEntry 2 } 545 inetCidrRoutePfxLen OBJECT-TYPE 546 SYNTAX InetAddressPrefixLength 547 MAX-ACCESS not-accessible 548 STATUS current 549 DESCRIPTION 550 "Indicates the number of leading one bits which form the 551 mask to be logical-ANDed with the destination address 552 before being compared to the value in the 553 inetCidrRouteDest field. 555 The values for the index objects inetCidrRouteDest and 556 inetCidrRoutePfxLen must be consistent. When the value 557 of inetCidrRouteDest (excluding the zone index, if one 558 is present) is x, then the bitwise logical-AND 559 of x with the value of the mask formed from the 560 corresponding index object inetCidrRoutePfxLen MUST be 561 equal to x. If not, then the index pair is not 562 consistent and an inconsistentName error must be 563 returned on SET or CREATE requests." 565 ::= { inetCidrRouteEntry 3 } 567 Haberman Expires July 2004 11 568 inetCidrRoutePolicy OBJECT-TYPE 569 SYNTAX OBJECT IDENTIFIER 570 MAX-ACCESS not-accessible 571 STATUS current 572 DESCRIPTION 573 "This object is an opaque object without any defined 574 semantics. Its purpose is to serve as an additional 575 index which may delineate between multiple entries to 576 the same destination. The value { 0 0 } shall be used 577 as the default value for this object." 578 ::= { inetCidrRouteEntry 4 } 580 inetCidrRouteNextHopType OBJECT-TYPE 581 SYNTAX InetAddressType 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "The type of the inetCidrRouteNextHop address, as 586 defined in the InetAddress MIB. 588 Value should be set to unknown(0) for non-remote 589 routes. 591 Only those address types that may appear in an actual 592 routing table are allowed as values of this object." 593 REFERENCE "RFC 3291" 594 ::= { inetCidrRouteEntry 5 } 596 inetCidrRouteNextHop OBJECT-TYPE 597 SYNTAX InetAddress 598 MAX-ACCESS not-accessible 599 STATUS current 600 DESCRIPTION 601 "On remote routes, the address of the next system en 602 route. For non-remote routes, a zero length string. 604 The type of this address is determined by the value of 605 the inetCidrRouteNextHopType object." 606 ::= { inetCidrRouteEntry 6 } 608 inetCidrRouteIfIndex OBJECT-TYPE 609 SYNTAX InterfaceIndexOrZero 610 MAX-ACCESS read-create 611 STATUS current 612 DESCRIPTION 613 "The ifIndex value which identifies the local interface 614 through which the next hop of this route should be 615 reached. A value of 0 is valid and represents the 616 scenario where no interface is specified." 617 ::= { inetCidrRouteEntry 7 } 619 inetCidrRouteType OBJECT-TYPE 620 SYNTAX INTEGER { 622 Haberman Expires July 2004 12 623 other (1), -- not specified by this MIB 624 reject (2), -- route which discards traffic and 625 -- returns ICMP notification 626 local (3), -- local interface 627 remote (4), -- remote destination 628 blackhole(5) -- route which discards traffic 629 -- silently 630 } 631 MAX-ACCESS read-create 632 STATUS current 633 DESCRIPTION 634 "The type of route. Note that local(3) refers to a 635 route for which the next hop is the final destination; 636 remote(4)refers to a route for which the next hop is 637 not the final destination. 639 Routes which do not result in traffic forwarding or 640 rejection should not be displayed even if the 641 implementation keeps them stored internally. 643 reject(2) refers to a route which, if matched, discards 644 the message as unreachable and returns a notification 645 (e.g. ICMP error) to the message sender. This is used 646 in some protocols as a means of correctly aggregating 647 routes. 649 blackhole(5) refers to a route which, if matched, 650 discards the message silently." 651 ::= { inetCidrRouteEntry 8 } 653 inetCidrRouteProto OBJECT-TYPE 654 SYNTAX IANAipRouteProtocol 655 MAX-ACCESS read-only 656 STATUS current 657 DESCRIPTION 658 "The routing mechanism via which this route was learned. 659 Inclusion of values for gateway routing protocols is 660 not intended to imply that hosts should support those 661 protocols." 662 ::= { inetCidrRouteEntry 9 } 664 inetCidrRouteAge OBJECT-TYPE 665 SYNTAX Gauge32 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The number of seconds since this route was last updated 670 or otherwise determined to be correct. Note that no 671 semantics of 'too old' can be implied except through 672 knowledge of the routing protocol by which the route 673 was learned." 674 ::= { inetCidrRouteEntry 10 } 676 inetCidrRouteNextHopAS OBJECT-TYPE 678 Haberman Expires July 2004 13 679 SYNTAX InetAutonomousSystemNumber 680 MAX-ACCESS read-create 681 STATUS current 682 DESCRIPTION 683 "The Autonomous System Number of the Next Hop. The 684 semantics of this object are determined by the routing- 685 protocol specified in the route's inetCidrRouteProto 686 value. When this object is unknown or not relevant its 687 value should be set to zero." 688 DEFVAL { 0 } 689 ::= { inetCidrRouteEntry 11 } 691 inetCidrRouteMetric1 OBJECT-TYPE 692 SYNTAX Integer32 693 MAX-ACCESS read-create 694 STATUS current 695 DESCRIPTION 696 "The primary routing metric for this route. The 697 semantics of this metric are determined by the routing- 698 protocol specified in the route's inetCidrRouteProto 699 value. If this metric is not used, its value should be 700 set to -1." 701 DEFVAL { -1 } 702 ::= { inetCidrRouteEntry 12 } 704 inetCidrRouteMetric2 OBJECT-TYPE 705 SYNTAX Integer32 706 MAX-ACCESS read-create 707 STATUS current 708 DESCRIPTION 709 "An alternate routing metric for this route. The 710 semantics of this metric are determined by the routing- 711 protocol specified in the route's inetCidrRouteProto 712 value. If this metric is not used, its value should be 713 set to -1." 714 DEFVAL { -1 } 715 ::= { inetCidrRouteEntry 13 } 717 inetCidrRouteMetric3 OBJECT-TYPE 718 SYNTAX Integer32 719 MAX-ACCESS read-create 720 STATUS current 721 DESCRIPTION 722 "An alternate routing metric for this route. The 723 semantics of this metric are determined by the routing- 724 protocol specified in the route's inetCidrRouteProto 725 value. If this metric is not used, its value should be 726 set to -1." 727 DEFVAL { -1 } 728 ::= { inetCidrRouteEntry 14 } 730 inetCidrRouteMetric4 OBJECT-TYPE 731 SYNTAX Integer32 732 MAX-ACCESS read-create 734 Haberman Expires July 2004 14 735 STATUS current 736 DESCRIPTION 737 "An alternate routing metric for this route. The 738 semantics of this metric are determined by the routing- 739 protocol specified in the route's inetCidrRouteProto 740 value. If this metric is not used, its value should be 741 set to -1." 742 DEFVAL { -1 } 743 ::= { inetCidrRouteEntry 15 } 745 inetCidrRouteMetric5 OBJECT-TYPE 746 SYNTAX Integer32 747 MAX-ACCESS read-create 748 STATUS current 749 DESCRIPTION 750 "An alternate routing metric for this route. The 751 semantics of this metric are determined by the routing- 752 protocol specified in the route's inetCidrRouteProto 753 value. If this metric is not used, its value should be 754 set to -1." 755 DEFVAL { -1 } 756 ::= { inetCidrRouteEntry 16 } 758 inetCidrRouteStatus OBJECT-TYPE 759 SYNTAX RowStatus 760 MAX-ACCESS read-create 761 STATUS current 762 DESCRIPTION 763 "The row status variable, used according to row 764 installation and removal conventions. 766 A row entry cannot be modified when the status is 767 marked as active(1)." 768 ::= { inetCidrRouteEntry 17 } 770 -- Conformance information 772 ipForwardConformance 773 OBJECT IDENTIFIER ::= { ipForward 5 } 775 ipForwardGroups 776 OBJECT IDENTIFIER ::= { ipForwardConformance 1 } 778 ipForwardCompliances 779 OBJECT IDENTIFIER ::= { ipForwardConformance 2 } 781 -- Compliance statements 783 ipForwardFullCompliance MODULE-COMPLIANCE 784 STATUS current 785 DESCRIPTION 786 "When this MIB is implemented for read-create, the 787 implementation can claim full compliance. 789 Haberman Expires July 2004 15 790 There are a number of INDEX objects that cannot be 791 represented in the form of OBJECT clauses in SMIv2, 792 but for which there are compliance requirements, 793 expressed in OBJECT clause form in this description: 795 -- OBJECT inetCidrRouteDestType 796 -- SYNTAX InetAddressType (ipv4(1), ipv6(2), 797 -- ipv4z(3), ipv6z(4)) 798 -- DESCRIPTION 799 -- This MIB requires support for global and 800 -- non-global ipv4 and ipv6 addresses. 801 -- 802 -- OBJECT inetCidrRouteDest 803 -- SYNTAX InetAddress (SIZE (4 | 8 | 16 | 20)) 804 -- DESCRIPTION 805 -- This MIB requires support for global and 806 -- non-global IPv4 and IPv6 addresses. 807 -- 808 -- OBJECT inetCidrRouteNextHopType 809 -- SYNTAX InetAddressType (unknown(0), ipv4(1), 810 -- ipv6(2), ipv4z(3) 811 -- ipv6z(4)) 812 -- DESCRIPTION 813 -- This MIB requires support for global and 814 -- non-global ipv4 and ipv6 addresses. 815 -- 816 -- OBJECT inetCidrRouteNextHop 817 -- SYNTAX InetAddress (SIZE (0 | 4 | 8 | 16 | 20)) 818 -- DESCRIPTION 819 -- This MIB requires support for global and 820 -- non-global IPv4 and IPv6 addresses. 821 " 823 MODULE -- this module 824 MANDATORY-GROUPS { inetForwardCidrRouteGroup } 826 OBJECT inetCidrRouteStatus 827 SYNTAX RowStatus { active(1), notInService (2) } 828 WRITE-SYNTAX RowStatus { active(1), notInService (2), 829 createAndGo(4), destroy(6) } 830 DESCRIPTION "Support for createAndWait is not required." 832 ::= { ipForwardCompliances 3 } 834 ipForwardReadOnlyCompliance MODULE-COMPLIANCE 835 STATUS current 836 DESCRIPTION 837 "When this MIB is implemented without support for read- 838 create (i.e. in read-only mode), the implementation can 839 claim read-only compliance." 840 MODULE -- this module 841 MANDATORY-GROUPS { inetForwardCidrRouteGroup } 843 OBJECT inetCidrRouteIfIndex 845 Haberman Expires July 2004 16 846 MIN-ACCESS read-only 847 DESCRIPTION 848 "Write access is not required." 850 OBJECT inetCidrRouteType 851 MIN-ACCESS read-only 852 DESCRIPTION 853 "Write access is not required." 855 OBJECT inetCidrRouteNextHopAS 856 MIN-ACCESS read-only 857 DESCRIPTION 858 "Write access is not required." 860 OBJECT inetCidrRouteMetric1 861 MIN-ACCESS read-only 862 DESCRIPTION 863 "Write access is not required." 865 OBJECT inetCidrRouteMetric2 866 MIN-ACCESS read-only 867 DESCRIPTION 868 "Write access is not required." 870 OBJECT inetCidrRouteMetric3 871 MIN-ACCESS read-only 872 DESCRIPTION 873 "Write access is not required." 875 OBJECT inetCidrRouteMetric4 876 MIN-ACCESS read-only 877 DESCRIPTION 878 "Write access is not required." 880 OBJECT inetCidrRouteMetric5 881 MIN-ACCESS read-only 882 DESCRIPTION 883 "Write access is not required." 885 OBJECT inetCidrRouteStatus 886 SYNTAX RowStatus { active(1) } 887 MIN-ACCESS read-only 888 DESCRIPTION 889 "Write access is not required." 891 ::= { ipForwardCompliances 4 } 893 -- units of conformance 895 inetForwardCidrRouteGroup OBJECT-GROUP 896 OBJECTS { inetCidrRouteDiscards, 897 inetCidrRouteIfIndex, inetCidrRouteType, 898 inetCidrRouteProto, inetCidrRouteAge, 899 inetCidrRouteNextHopAS, inetCidrRouteMetric1, 901 Haberman Expires July 2004 17 902 inetCidrRouteMetric2, inetCidrRouteMetric3, 903 inetCidrRouteMetric4, inetCidrRouteMetric5, 904 inetCidrRouteStatus, inetCidrRouteNumber 905 } 906 STATUS current 907 DESCRIPTION 908 "The IP version-independent CIDR Route Table." 909 ::= { ipForwardGroups 4 } 911 -- Deprecated Objects 913 ipCidrRouteNumber OBJECT-TYPE 914 SYNTAX Gauge32 915 MAX-ACCESS read-only 916 STATUS deprecated 917 DESCRIPTION 918 "The number of current ipCidrRouteTable entries that are 919 not invalid. This object is deprecated in favor of 920 inetCidrRouteNumber and the inetCidrRouteTable." 921 ::= { ipForward 3 } 923 -- IP CIDR Route Table 925 -- The IP CIDR Route Table obsoletes and replaces the ipRoute 926 -- Table current in MIB-I and MIB-II and the IP Forwarding Table. 927 -- It adds knowledge of the autonomous system of the next hop, 928 -- multiple next hops, and policy routing, and Classless 929 -- Inter-Domain Routing. 931 ipCidrRouteTable OBJECT-TYPE 932 SYNTAX SEQUENCE OF IpCidrRouteEntry 933 MAX-ACCESS not-accessible 934 STATUS deprecated 935 DESCRIPTION 936 "This entity's IP Routing table. This table has been 937 deprecated in favor of the IP version neutral 938 inetCidrRouteTable." 939 REFERENCE 940 "RFC 1213 Section 6.6, The IP Group" 941 ::= { ipForward 4 } 943 ipCidrRouteEntry OBJECT-TYPE 944 SYNTAX IpCidrRouteEntry 945 MAX-ACCESS not-accessible 946 STATUS deprecated 947 DESCRIPTION 948 "A particular route to a particular destination, under a 949 particular policy." 950 INDEX { 951 ipCidrRouteDest, 952 ipCidrRouteMask, 953 ipCidrRouteTos, 954 ipCidrRouteNextHop 955 } 957 Haberman Expires July 2004 18 958 ::= { ipCidrRouteTable 1 } 960 IpCidrRouteEntry ::= SEQUENCE { 961 ipCidrRouteDest IpAddress, 962 ipCidrRouteMask IpAddress, 963 ipCidrRouteTos Integer32, 964 ipCidrRouteNextHop IpAddress, 965 ipCidrRouteIfIndex Integer32, 966 ipCidrRouteType INTEGER, 967 ipCidrRouteProto INTEGER, 968 ipCidrRouteAge Integer32, 969 ipCidrRouteInfo OBJECT IDENTIFIER, 970 ipCidrRouteNextHopAS Integer32, 971 ipCidrRouteMetric1 Integer32, 972 ipCidrRouteMetric2 Integer32, 973 ipCidrRouteMetric3 Integer32, 974 ipCidrRouteMetric4 Integer32, 975 ipCidrRouteMetric5 Integer32, 976 ipCidrRouteStatus RowStatus 977 } 979 ipCidrRouteDest OBJECT-TYPE 980 SYNTAX IpAddress 981 MAX-ACCESS read-only 982 STATUS deprecated 983 DESCRIPTION 984 "The destination IP address of this route. 986 This object may not take a Multicast (Class D) address 987 value. 989 Any assignment (implicit or otherwise) of an instance 990 of this object to a value x must be rejected if the 991 bitwise logical-AND of x with the value of the 992 corresponding instance of the ipCidrRouteMask object is 993 not equal to x." 994 ::= { ipCidrRouteEntry 1 } 996 ipCidrRouteMask OBJECT-TYPE 997 SYNTAX IpAddress 998 MAX-ACCESS read-only 999 STATUS deprecated 1000 DESCRIPTION 1001 "Indicate the mask to be logical-ANDed with the 1002 destination address before being compared to the value 1003 in the ipCidrRouteDest field. For those systems that 1004 do not support arbitrary subnet masks, an agent 1005 constructs the value of the ipCidrRouteMask by 1006 reference to the IP Address Class. 1008 Any assignment (implicit or otherwise) of an instance 1009 of this object to a value x must be rejected if the 1010 bitwise logical-AND of x with the value of the 1011 corresponding instance of the ipCidrRouteDest object is 1013 Haberman Expires July 2004 19 1014 not equal to ipCidrRouteDest." 1015 ::= { ipCidrRouteEntry 2 } 1017 -- The following convention is included for specification 1018 -- of TOS Field contents. At this time, the Host Requirements 1019 -- and the Router Requirements documents disagree on the width 1020 -- of the TOS field. This mapping describes the Router 1021 -- Requirements mapping, and leaves room to widen the TOS field 1022 -- without impact to fielded systems. 1024 ipCidrRouteTos OBJECT-TYPE 1025 SYNTAX Integer32 (0..2147483647) 1026 MAX-ACCESS read-only 1027 STATUS deprecated 1028 DESCRIPTION 1029 "The policy specifier is the IP TOS Field. The encoding 1030 of IP TOS is as specified by the following convention. 1031 Zero indicates the default path if no more specific 1032 policy applies. 1034 +-----+-----+-----+-----+-----+-----+-----+-----+ 1035 | | | | 1036 | PRECEDENCE | TYPE OF SERVICE | 0 | 1037 | | | | 1038 +-----+-----+-----+-----+-----+-----+-----+-----+ 1040 IP TOS IP TOS 1041 Field Policy Field Policy 1042 Contents Code Contents Code 1043 0 0 0 0 ==> 0 0 0 0 1 ==> 2 1044 0 0 1 0 ==> 4 0 0 1 1 ==> 6 1045 0 1 0 0 ==> 8 0 1 0 1 ==> 10 1046 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1047 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1048 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1049 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1050 1 1 1 0 ==> 28 1 1 1 1 ==> 30" 1051 ::= { ipCidrRouteEntry 3 } 1053 ipCidrRouteNextHop OBJECT-TYPE 1054 SYNTAX IpAddress 1055 MAX-ACCESS read-only 1056 STATUS deprecated 1057 DESCRIPTION 1058 "On remote routes, the address of the next system en 1059 route; Otherwise, 0.0.0.0." 1060 ::= { ipCidrRouteEntry 4 } 1062 ipCidrRouteIfIndex OBJECT-TYPE 1063 SYNTAX Integer32 1064 MAX-ACCESS read-create 1065 STATUS deprecated 1066 DESCRIPTION 1067 "The ifIndex value which identifies the local interface 1069 Haberman Expires July 2004 20 1070 through which the next hop of this route should be 1071 reached." 1072 DEFVAL { 0 } 1073 ::= { ipCidrRouteEntry 5 } 1075 ipCidrRouteType OBJECT-TYPE 1076 SYNTAX INTEGER { 1077 other (1), -- not specified by this MIB 1078 reject (2), -- route which discards traffic 1079 local (3), -- local interface 1080 remote (4) -- remote destination 1081 } 1082 MAX-ACCESS read-create 1083 STATUS deprecated 1084 DESCRIPTION 1085 "The type of route. Note that local(3) refers to a 1086 route for which the next hop is the final destination; 1087 remote(4) refers to a route for which the next hop is 1088 not the final destination. 1090 Routes which do not result in traffic forwarding or 1091 rejection should not be displayed even if the 1092 implementation keeps them stored internally. 1094 reject (2) refers to a route which, if matched, 1095 discards the message as unreachable. This is used in 1096 some protocols as a means of correctly aggregating 1097 routes." 1098 ::= { ipCidrRouteEntry 6 } 1100 ipCidrRouteProto OBJECT-TYPE 1101 SYNTAX INTEGER { 1102 other (1), -- not specified 1103 local (2), -- local interface 1104 netmgmt (3), -- static route 1105 icmp (4), -- result of ICMP Redirect 1107 -- the following are all dynamic 1108 -- routing protocols 1109 egp (5), -- Exterior Gateway Protocol 1110 ggp (6), -- Gateway-Gateway Protocol 1111 hello (7), -- FuzzBall HelloSpeak 1112 rip (8), -- Berkeley RIP or RIP-II 1113 isIs (9), -- Dual IS-IS 1114 esIs (10), -- ISO 9542 1115 ciscoIgrp (11), -- Cisco IGRP 1116 bbnSpfIgp (12), -- BBN SPF IGP 1117 ospf (13), -- Open Shortest Path First 1118 bgp (14), -- Border Gateway Protocol 1119 idpr (15), -- InterDomain Policy Routing 1120 ciscoEigrp (16) -- Cisco EIGRP 1121 } 1122 MAX-ACCESS read-only 1123 STATUS deprecated 1125 Haberman Expires July 2004 21 1126 DESCRIPTION 1127 "The routing mechanism via which this route was learned. 1128 Inclusion of values for gateway routing protocols is 1129 not intended to imply that hosts should support those 1130 protocols." 1131 ::= { ipCidrRouteEntry 7 } 1133 ipCidrRouteAge OBJECT-TYPE 1134 SYNTAX Integer32 1135 MAX-ACCESS read-only 1136 STATUS deprecated 1137 DESCRIPTION 1138 "The number of seconds since this route was last updated 1139 or otherwise determined to be correct. Note that no 1140 semantics of `too old' can be implied except through 1141 knowledge of the routing protocol by which the route 1142 was learned." 1143 DEFVAL { 0 } 1144 ::= { ipCidrRouteEntry 8 } 1146 ipCidrRouteInfo OBJECT-TYPE 1147 SYNTAX OBJECT IDENTIFIER 1148 MAX-ACCESS read-create 1149 STATUS deprecated 1150 DESCRIPTION 1151 "A reference to MIB definitions specific to the 1152 particular routing protocol which is responsible for 1153 this route, as determined by the value specified in the 1154 route's ipCidrRouteProto value. If this information is 1155 not present, its value should be set to the OBJECT 1156 IDENTIFIER { 0 0 }, which is a syntactically valid 1157 object identifier, and any implementation conforming to 1158 ASN.1 and the Basic Encoding Rules must be able to 1159 generate and recognize this value." 1160 ::= { ipCidrRouteEntry 9 } 1162 ipCidrRouteNextHopAS OBJECT-TYPE 1163 SYNTAX Integer32 1164 MAX-ACCESS read-create 1165 STATUS deprecated 1166 DESCRIPTION 1167 "The Autonomous System Number of the Next Hop. The 1168 semantics of this object are determined by the routing- 1169 protocol specified in the route's ipCidrRouteProto 1170 value. When this object is unknown or not relevant its 1171 value should be set to zero." 1172 DEFVAL { 0 } 1173 ::= { ipCidrRouteEntry 10 } 1175 ipCidrRouteMetric1 OBJECT-TYPE 1176 SYNTAX Integer32 1177 MAX-ACCESS read-create 1178 STATUS deprecated 1179 DESCRIPTION 1181 Haberman Expires July 2004 22 1182 "The primary routing metric for this route. The 1183 semantics of this metric are determined by the routing- 1184 protocol specified in the route's ipCidrRouteProto 1185 value. If this metric is not used, its value should be 1186 set to -1." 1187 DEFVAL { -1 } 1188 ::= { ipCidrRouteEntry 11 } 1190 ipCidrRouteMetric2 OBJECT-TYPE 1191 SYNTAX Integer32 1192 MAX-ACCESS read-create 1193 STATUS deprecated 1194 DESCRIPTION 1195 "An alternate routing metric for this route. The 1196 semantics of this metric are determined by the routing- 1197 protocol specified in the route's ipCidrRouteProto 1198 value. If this metric is not used, its value should be 1199 set to -1." 1200 DEFVAL { -1 } 1201 ::= { ipCidrRouteEntry 12 } 1203 ipCidrRouteMetric3 OBJECT-TYPE 1204 SYNTAX Integer32 1205 MAX-ACCESS read-create 1206 STATUS deprecated 1207 DESCRIPTION 1208 "An alternate routing metric for this route. The 1209 semantics of this metric are determined by the routing- 1210 protocol specified in the route's ipCidrRouteProto 1211 value. If this metric is not used, its value should be 1212 set to -1." 1213 DEFVAL { -1 } 1214 ::= { ipCidrRouteEntry 13 } 1216 ipCidrRouteMetric4 OBJECT-TYPE 1217 SYNTAX Integer32 1218 MAX-ACCESS read-create 1219 STATUS deprecated 1220 DESCRIPTION 1221 "An alternate routing metric for this route. The 1222 semantics of this metric are determined by the routing- 1223 protocol specified in the route's ipCidrRouteProto 1224 value. If this metric is not used, its value should be 1225 set to -1." 1226 DEFVAL { -1 } 1227 ::= { ipCidrRouteEntry 14 } 1229 ipCidrRouteMetric5 OBJECT-TYPE 1230 SYNTAX Integer32 1231 MAX-ACCESS read-create 1232 STATUS deprecated 1233 DESCRIPTION 1234 "An alternate routing metric for this route. The 1235 semantics of this metric are determined by the routing- 1237 Haberman Expires July 2004 23 1238 protocol specified in the route's ipCidrRouteProto 1239 value. If this metric is not used, its value should be 1240 set to -1." 1241 DEFVAL { -1 } 1242 ::= { ipCidrRouteEntry 15 } 1244 ipCidrRouteStatus OBJECT-TYPE 1245 SYNTAX RowStatus 1246 MAX-ACCESS read-create 1247 STATUS deprecated 1248 DESCRIPTION 1249 "The row status variable, used according to row 1250 installation and removal conventions." 1251 ::= { ipCidrRouteEntry 16 } 1253 -- compliance statements 1255 ipForwardCompliance MODULE-COMPLIANCE 1256 STATUS deprecated 1257 DESCRIPTION 1258 "The compliance statement for SNMPv2 entities which 1259 implement the ipForward MIB. 1261 This compliance statement has been deprecated and 1262 replaced with ipForwardFullCompliance and 1263 ipForwardReadOnlyCompliance." 1265 MODULE -- this module 1266 MANDATORY-GROUPS { ipForwardCidrRouteGroup } 1268 ::= { ipForwardCompliances 1 } 1270 -- units of conformance 1272 ipForwardCidrRouteGroup OBJECT-GROUP 1273 OBJECTS { ipCidrRouteNumber, 1274 ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, 1275 ipCidrRouteNextHop, ipCidrRouteIfIndex, 1276 ipCidrRouteType, ipCidrRouteProto, ipCidrRouteAge, 1277 ipCidrRouteInfo,ipCidrRouteNextHopAS, 1278 ipCidrRouteMetric1, ipCidrRouteMetric2, 1279 ipCidrRouteMetric3, ipCidrRouteMetric4, 1280 ipCidrRouteMetric5, ipCidrRouteStatus 1281 } 1282 STATUS deprecated 1283 DESCRIPTION 1284 "The CIDR Route Table. 1286 This group has been deprecated and replaced with 1287 inetForwardCidrRouteGroup." 1288 ::= { ipForwardGroups 3 } 1290 Haberman Expires July 2004 24 1291 -- Obsoleted Definitions - Objects 1293 ipForwardNumber OBJECT-TYPE 1294 SYNTAX Gauge32 1295 MAX-ACCESS read-only 1296 STATUS obsolete 1297 DESCRIPTION 1298 "The number of current ipForwardTable entries that are 1299 not invalid." 1300 ::= { ipForward 1 } 1302 -- IP Forwarding Table 1304 -- The IP Forwarding Table obsoletes and replaces the ipRoute 1305 -- Table current in MIB-I and MIB-II. It adds knowledge of 1306 -- the autonomous system of the next hop, multiple next hop 1307 -- support, and policy routing support. 1309 ipForwardTable OBJECT-TYPE 1310 SYNTAX SEQUENCE OF IpForwardEntry 1311 MAX-ACCESS not-accessible 1312 STATUS obsolete 1313 DESCRIPTION 1314 "This entity's IP Routing table." 1315 REFERENCE 1316 "RFC 1213 Section 6.6, The IP Group" 1317 ::= { ipForward 2 } 1319 ipForwardEntry OBJECT-TYPE 1320 SYNTAX IpForwardEntry 1321 MAX-ACCESS not-accessible 1322 STATUS obsolete 1323 DESCRIPTION 1324 "A particular route to a particular destination, under a 1325 particular policy." 1326 INDEX { 1327 ipForwardDest, 1328 ipForwardProto, 1329 ipForwardPolicy, 1330 ipForwardNextHop 1331 } 1332 ::= { ipForwardTable 1 } 1334 IpForwardEntry ::= SEQUENCE { 1335 ipForwardDest IpAddress, 1336 ipForwardMask IpAddress, 1337 ipForwardPolicy Integer32, 1338 ipForwardNextHop IpAddress, 1339 ipForwardIfIndex Integer32, 1340 ipForwardType INTEGER, 1341 ipForwardProto INTEGER, 1342 ipForwardAge Integer32, 1343 ipForwardInfo OBJECT IDENTIFIER, 1344 ipForwardNextHopAS Integer32, 1346 Haberman Expires July 2004 25 1347 ipForwardMetric1 Integer32, 1348 ipForwardMetric2 Integer32, 1349 ipForwardMetric3 Integer32, 1350 ipForwardMetric4 Integer32, 1351 ipForwardMetric5 Integer32 1352 } 1354 ipForwardDest OBJECT-TYPE 1355 SYNTAX IpAddress 1356 MAX-ACCESS read-only 1357 STATUS obsolete 1358 DESCRIPTION 1359 "The destination IP address of this route. An entry 1360 with a value of 0.0.0.0 is considered a default route. 1362 This object may not take a Multicast (Class D) address 1363 value. 1365 Any assignment (implicit or otherwise) of an instance 1366 of this object to a value x must be rejected if the 1367 bitwise logical-AND of x with the value of the 1368 corresponding instance of the ipForwardMask object is 1369 not equal to x." 1370 ::= { ipForwardEntry 1 } 1372 ipForwardMask OBJECT-TYPE 1373 SYNTAX IpAddress 1374 MAX-ACCESS read-create 1375 STATUS obsolete 1376 DESCRIPTION 1377 "Indicate the mask to be logical-ANDed with the 1378 destination address before being compared to the value 1379 in the ipForwardDest field. For those systems that do 1380 not support arbitrary subnet masks, an agent constructs 1381 the value of the ipForwardMask by reference to the IP 1382 Address Class. 1384 Any assignment (implicit or otherwise) of an instance 1385 of this object to a value x must be rejected if the 1386 bitwise logical-AND of x with the value of the 1387 corresponding instance of the ipForwardDest object is 1388 not equal to ipForwardDest." 1389 DEFVAL { '00000000'H } -- 0.0.0.0 1390 ::= { ipForwardEntry 2 } 1392 -- The following convention is included for specification 1393 -- of TOS Field contents. At this time, the Host Requirements 1394 -- and the Router Requirements documents disagree on the width 1395 -- of the TOS field. This mapping describes the Router 1396 -- Requirements mapping, and leaves room to widen the TOS field 1397 -- without impact to fielded systems. 1399 ipForwardPolicy OBJECT-TYPE 1400 SYNTAX Integer32 (0..2147483647) 1402 Haberman Expires July 2004 26 1403 MAX-ACCESS read-only 1404 STATUS obsolete 1405 DESCRIPTION 1406 "The general set of conditions that would cause 1407 the selection of one multipath route (set of 1408 next hops for a given destination) is referred 1409 to as 'policy'. 1411 Unless the mechanism indicated by ipForwardProto 1412 specifies otherwise, the policy specifier is 1413 the IP TOS Field. The encoding of IP TOS is as 1414 specified by the following convention. Zero 1415 indicates the default path if no more specific 1416 policy applies. 1418 +-----+-----+-----+-----+-----+-----+-----+-----+ 1419 | | | | 1420 | PRECEDENCE | TYPE OF SERVICE | 0 | 1421 | | | | 1422 +-----+-----+-----+-----+-----+-----+-----+-----+ 1424 IP TOS IP TOS 1425 Field Policy Field Policy 1426 Contents Code Contents Code 1427 0 0 0 0 ==> 0 0 0 0 1 ==> 2 1428 0 0 1 0 ==> 4 0 0 1 1 ==> 6 1429 0 1 0 0 ==> 8 0 1 0 1 ==> 10 1430 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1431 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1432 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1433 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1434 1 1 1 0 ==> 28 1 1 1 1 ==> 30 1436 Protocols defining 'policy' otherwise must either 1437 define a set of values which are valid for 1438 this object or must implement an integer-instanced 1439 policy table for which this object's 1440 value acts as an index." 1441 ::= { ipForwardEntry 3 } 1443 ipForwardNextHop OBJECT-TYPE 1444 SYNTAX IpAddress 1445 MAX-ACCESS read-only 1446 STATUS obsolete 1447 DESCRIPTION 1448 "On remote routes, the address of the next system en 1449 route; Otherwise, 0.0.0.0." 1450 ::= { ipForwardEntry 4 } 1452 ipForwardIfIndex OBJECT-TYPE 1453 SYNTAX Integer32 1454 MAX-ACCESS read-create 1456 Haberman Expires July 2004 27 1457 STATUS obsolete 1458 DESCRIPTION 1459 "The ifIndex value which identifies the local interface 1460 through which the next hop of this route should be 1461 reached." 1462 DEFVAL { 0 } 1463 ::= { ipForwardEntry 5 } 1465 ipForwardType OBJECT-TYPE 1466 SYNTAX INTEGER { 1467 other (1), -- not specified by this MIB 1468 invalid (2), -- logically deleted 1469 local (3), -- local interface 1470 remote (4) -- remote destination 1471 } 1472 MAX-ACCESS read-create 1473 STATUS obsolete 1474 DESCRIPTION 1475 "The type of route. Note that local(3) refers to a 1476 route for which the next hop is the final destination; 1477 remote(4) refers to a route for which the next hop is 1478 not the final destination. 1480 Setting this object to the value invalid(2) has the 1481 effect of invalidating the corresponding entry in the 1482 ipForwardTable object. That is, it effectively 1483 disassociates the destination identified with said 1484 entry from the route identified with said entry. It is 1485 an implementation-specific matter as to whether the 1486 agent removes an invalidated entry from the table. 1487 Accordingly, management stations must be prepared to 1488 receive tabular information from agents that 1489 corresponds to entries not currently in use. Proper 1490 interpretation of such entries requires examination of 1491 the relevant ipForwardType object." 1492 DEFVAL { invalid } 1493 ::= { ipForwardEntry 6 } 1495 ipForwardProto OBJECT-TYPE 1496 SYNTAX INTEGER { 1497 other (1), -- not specified 1498 local (2), -- local interface 1499 netmgmt (3), -- static route 1500 icmp (4), -- result of ICMP Redirect 1502 -- the following are all dynamic 1503 -- routing protocols 1504 egp (5), -- Exterior Gateway Protocol 1505 ggp (6), -- Gateway-Gateway Protocol 1506 hello (7), -- FuzzBall HelloSpeak 1507 rip (8), -- Berkeley RIP or RIP-II 1508 is-is (9), -- Dual IS-IS 1509 es-is (10), -- ISO 9542 1510 ciscoIgrp (11), -- Cisco IGRP 1512 Haberman Expires July 2004 28 1513 bbnSpfIgp (12), -- BBN SPF IGP 1514 ospf (13), -- Open Shortest Path First 1515 bgp (14), -- Border Gateway Protocol 1516 idpr (15) -- InterDomain Policy Routing 1517 } 1518 MAX-ACCESS read-only 1519 STATUS obsolete 1520 DESCRIPTION 1521 "The routing mechanism via which this route was learned. 1522 Inclusion of values for gateway routing protocols is 1523 not intended to imply that hosts should support those 1524 protocols." 1525 ::= { ipForwardEntry 7 } 1527 ipForwardAge OBJECT-TYPE 1528 SYNTAX Integer32 1529 MAX-ACCESS read-only 1530 STATUS obsolete 1531 DESCRIPTION 1532 "The number of seconds since this route was last updated 1533 or otherwise determined to be correct. Note that no 1534 semantics of `too old' can be implied except through 1535 knowledge of the routing protocol by which the route 1536 was learned." 1537 DEFVAL { 0 } 1538 ::= { ipForwardEntry 8 } 1540 ipForwardInfo OBJECT-TYPE 1541 SYNTAX OBJECT IDENTIFIER 1542 MAX-ACCESS read-create 1543 STATUS obsolete 1544 DESCRIPTION 1545 "A reference to MIB definitions specific to the 1546 particular routing protocol which is responsible for 1547 this route, as determined by the value specified in the 1548 route's ipForwardProto value. If this information is 1549 not present, its value should be set to the OBJECT 1550 IDENTIFIER { 0 0 }, which is a syntactically valid 1551 object identifier, and any implementation conforming to 1552 ASN.1 and the Basic Encoding Rules must be able to 1553 generate and recognize this value." 1554 ::= { ipForwardEntry 9 } 1556 ipForwardNextHopAS OBJECT-TYPE 1557 SYNTAX Integer32 1558 MAX-ACCESS read-create 1559 STATUS obsolete 1560 DESCRIPTION 1561 "The Autonomous System Number of the Next Hop. When 1562 this is unknown or not relevant to the protocol 1563 indicated by ipForwardProto, zero." 1564 DEFVAL { 0 } 1565 ::= { ipForwardEntry 10 } 1567 Haberman Expires July 2004 29 1568 ipForwardMetric1 OBJECT-TYPE 1569 SYNTAX Integer32 1570 MAX-ACCESS read-create 1571 STATUS obsolete 1572 DESCRIPTION 1573 "The primary routing metric for this route. The 1574 semantics of this metric are determined by the routing- 1575 protocol specified in the route's ipForwardProto value. 1576 If this metric is not used, its value should be set to 1577 -1." 1578 DEFVAL { -1 } 1579 ::= { ipForwardEntry 11 } 1581 ipForwardMetric2 OBJECT-TYPE 1582 SYNTAX Integer32 1583 MAX-ACCESS read-create 1584 STATUS obsolete 1585 DESCRIPTION 1586 "An alternate routing metric for this route. The 1587 semantics of this metric are determined by the routing- 1588 protocol specified in the route's ipForwardProto value. 1589 If this metric is not used, its value should be set to 1590 -1." 1591 DEFVAL { -1 } 1592 ::= { ipForwardEntry 12 } 1594 ipForwardMetric3 OBJECT-TYPE 1595 SYNTAX Integer32 1596 MAX-ACCESS read-create 1597 STATUS obsolete 1598 DESCRIPTION 1599 "An alternate routing metric for this route. The 1600 semantics of this metric are determined by the routing- 1601 protocol specified in the route's ipForwardProto value. 1602 If this metric is not used, its value should be set to 1603 -1." 1604 DEFVAL { -1 } 1605 ::= { ipForwardEntry 13 } 1607 ipForwardMetric4 OBJECT-TYPE 1608 SYNTAX Integer32 1609 MAX-ACCESS read-create 1610 STATUS obsolete 1611 DESCRIPTION 1612 "An alternate routing metric for this route. The 1613 semantics of this metric are determined by the routing- 1614 protocol specified in the route's ipForwardProto value. 1615 If this metric is not used, its value should be set to 1616 -1." 1617 DEFVAL { -1 } 1618 ::= { ipForwardEntry 14 } 1620 ipForwardMetric5 OBJECT-TYPE 1621 SYNTAX Integer32 1623 Haberman Expires July 2004 30 1624 MAX-ACCESS read-create 1625 STATUS obsolete 1626 DESCRIPTION 1627 "An alternate routing metric for this route. The 1628 semantics of this metric are determined by the routing- 1629 protocol specified in the route's ipForwardProto value. 1630 If this metric is not used, its value should be set to 1631 -1." 1632 DEFVAL { -1 } 1633 ::= { ipForwardEntry 15 } 1635 -- Obsoleted Definitions - Groups 1636 -- compliance statements 1638 ipForwardOldCompliance MODULE-COMPLIANCE 1639 STATUS obsolete 1640 DESCRIPTION 1641 "The compliance statement for SNMP entities which 1642 implement the ipForward MIB." 1644 MODULE -- this module 1645 MANDATORY-GROUPS { ipForwardMultiPathGroup } 1647 ::= { ipForwardCompliances 2 } 1649 ipForwardMultiPathGroup OBJECT-GROUP 1650 OBJECTS { ipForwardNumber, 1651 ipForwardDest, ipForwardMask, ipForwardPolicy, 1652 ipForwardNextHop, ipForwardIfIndex, ipForwardType, 1653 ipForwardProto, ipForwardAge, ipForwardInfo, 1654 ipForwardNextHopAS, 1655 ipForwardMetric1, ipForwardMetric2, ipForwardMetric3, 1656 ipForwardMetric4, ipForwardMetric5 1657 } 1658 STATUS obsolete 1659 DESCRIPTION 1660 "IP Multipath Route Table." 1661 ::= { ipForwardGroups 2 } 1663 END 1665 Haberman Expires July 2004 31 1666 6 Security Considerations 1668 There are a number of management objects defined in this MIB module 1669 with a MAX-ACCESS clause of read-write and/or read-create. Such 1670 objects may be considered sensitive or vulnerable in some network 1671 environments. The support for SET operations in a non-secure 1672 environment without proper protection can have a negative effect on 1673 network operations. These are the tables and objects and their 1674 sensitivity/vulnerability: 1676 1. The inetCidrRouteTable contains routing and forwarding 1677 information that is critical to the operation of the network 1678 node (especially routers). Allowing unauthenticated write 1679 access to this table can compromise the validity of the 1680 forwarding information. 1682 Some of the readable objects in this MIB module (i.e., objects with 1683 a MAX-ACCESS other than not-accessible) may be considered sensitive 1684 or vulnerable in some network environments. It is thus important 1685 to control even GET and/or NOTIFY access to these objects and 1686 possibly to even encrypt the values of these objects when sending 1687 them over the network via SNMP. These are the tables and objects 1688 and their sensitivity/vulnerability: 1690 1. The inetCidrRouteTable contains routing and forwarding 1691 information that can be used to compromise a network. 1692 Specifically, this table can be used to construct a map of the 1693 network in preparation for a denial-of-service attack on the 1694 network infrastructure. 1695 2. The inetCidrRouteProto object identifies the routing protocols 1696 in use within a network. This information can be used to 1697 determine how a denial-of-service attack should be launched. 1699 SNMP versions prior to SNMPv3 did not include adequate security. 1700 Even if the network itself is secure (for example by using IPSec), 1701 even then, there is no control as to who on the secure network is 1702 allowed to access and GET/SET (read/change/create/delete) the 1703 objects in this MIB module. 1705 It is RECOMMENDED that implementers consider the security features 1706 as provided by the SNMPv3 framework (see [RFC3410], section 8), 1707 including full support for the SNMPv3 cryptographic mechanisms (for 1708 authentication and privacy). 1710 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1711 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1712 enable cryptographic security. It is then a customer/operator 1713 responsibility to ensure that the SNMP entity giving access to an 1714 instance of this MIB module is properly configured to give access 1715 to the objects only to those principals (users) that have 1716 legitimate rights to indeed GET or SET (change/create/delete) them. 1718 Haberman Expires July 2004 32 1719 7 Intellectual Property Statement 1721 The IETF takes no position regarding the validity or scope of any 1722 intellectual property or other rights that might be claimed to 1723 pertain to the implementation or use of the technology described in 1724 this document or the extent to which any license under such rights 1725 might or might not be available; neither does it represent that it 1726 has made any effort to identify any such rights. Information on 1727 the IETF's procedures with respect to rights in standards-track and 1728 standards-related documentation can be found in BCP-11. Copies of 1729 claims of rights made available for publication and any assurances 1730 of licenses to be made available, or the result of an attempt made 1731 to obtain a general license or permission for the use of such 1732 proprietary rights by implementors or users of this specification 1733 can be obtained from the IETF Secretariat. 1735 The IETF invites any interested party to bring to its attention any 1736 copyrights, patents or patent applications, or other proprietary 1737 rights which may cover technology that may be required to practice 1738 this standard. Please address the information to the IETF 1739 Executive Director. 1741 8 Changes from RFC 2096 1743 This document updates RFC 2096 in the following ways: 1745 1. Replaces ipCidrRouteTable with inetCidrRouteTable. This 1746 applies to corresponding objects and conformance statements. 1747 2. Utilized the InetAddress TC to support IP version-independent 1748 implementations of the forwarding MIB. This gives common 1749 forwarding MIB support for IPv4 and IPv6. 1750 3. Created a read-only conformance statement to support 1751 implementations that only wish to retrieve data. 1752 4. Created the inetCidrRouteDiscards object to replace the 1753 deprecated ipRoutingDiscards and ipv6DiscardedRoutes objects. 1755 The inetCidrRouteTable retains the logical structure of the 1756 ipCidrRouteTable in order to allow the easy upgrade of existing 1757 IPv4 implementations to the version-independent MIB. 1759 Haberman Expires July 2004 33 1760 9 Normative References 1762 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 1763 Requirement Levels", RFC 2119, BCP14, March 1999. 1765 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1766 Rose, M. and S. Waldbusser, "Structure of Management 1767 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1768 1999. 1770 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1771 Rose, M. and S. Waldbusser, "Textual Conventions for 1772 SMIv2", STD 58, RFC 2579, April 1999. 1774 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1775 Rose, M. and S. Waldbusser, "Conformance Statements for 1776 SMIv2", STD 58, RFC 2580, April 1999. 1778 [RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, 1779 J., "Textual Conventions for Internet Network Addresses", 1780 RFC 3291, May 2002. 1781 -- RFC Ed : An update to RFC 3291 is in the works, in the case that 1782 -- draft-ietf-ops-rfc3291bis is published before or at the same 1783 -- time as this document, please update this reference and the two 1784 -- citations in the document. Afterwards, please remove this note. 1786 [RFC2863] McCloghrie, K., and Kastenholz, F., "The Interfaces Group 1787 MIB", RFC 2863, June 2000. 1789 [2011upd] Routhier, S., "Management Information Base for the 1790 Internet Protocol (IP), 1791 draft-ietf-ipv6-rfc2011-update-02.txt, February 2003. 1793 [RTPROTO] IANA, "IP Route Protocol MIB", 1794 http://www.iana.org/assignments/ianaiprouteprotocol-mib, 1795 September 2000. 1797 10 Informative References 1799 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1800 "Introduction and Applicability Statements for Internet- 1801 Standard Management Framework", RFC 3410, December 2002. 1803 [RFC2096] Baker, F., "IP Forwarding Table MIB", RFC 2096, January 1804 1997. 1806 Haberman Expires July 2004 34 1807 11 Authors and Acknowledgements 1809 This document was based on RFC 2096 [RFC2096]. 1811 The following people provided text for this version of the 1812 document, or were authors of previous versions: 1814 Fred Baker, Cisco 1815 Bill Fenner, AT&T Research 1816 Brian Haberman, Caspian Networks 1817 Juergen Schoenwalder, TU Braunschweig 1818 Dave Thaler, Microsoft 1819 Margaret Wasserman, Thingmagic 1821 Dario Accornero, Mark Adam, Qing Li and Shawn Routhier reviewed the 1822 document and provided helpful feedback. 1824 Mike Heard provided valuable feedback as the MIB Doctor for this 1825 document. 1827 12 Editors' Contact Information 1829 Comments or questions regarding this document should be sent to: 1831 Brian Haberman 1832 Caspian Networks 1833 753 Bridgewater Drive Phone: +1 410-552-1421 1834 Sykesville, MD 21784 USA Email: brian@innovationslab.net 1836 13 Full Copyright Statement 1838 Copyright (C) The Internet Society (2004). All Rights Reserved. 1840 This document and translations of it may be copied and furnished to 1841 others, and derivative works that comment on or otherwise explain 1842 it or assist in its implementation may be prepared, copied, 1843 published and distributed, in whole or in part, without restriction 1844 of any kind, provided that the above copyright notice and this 1845 paragraph are included on all such copies and derivative works. 1846 However, this document itself may not be modified in any way, such 1847 as by removing the copyright notice or references to the Internet 1848 Society or other Internet organizations, except as needed for the 1849 purpose of developing Internet standards in which case the 1850 procedures for copyrights defined in the Internet Standards process 1851 must be followed, or as required to translate it into languages 1852 other than English. 1854 The limited permissions granted above are perpetual and will not be 1855 revoked by the Internet Society or its successors or assigns. 1857 This document and the information contained herein is provided on 1858 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1860 Haberman Expires July 2004 35 1861 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1862 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1863 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1864 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1866 Haberman Expires July 2004 36