idnits 2.17.1 draft-ietf-ipngwg-rfc2096-update-00.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 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 document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 2 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 682 has weird spacing: '...ntifies the l...' -- 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 (July 2001) is 8311 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) ** Obsolete normative reference: RFC 2096 (ref. '1') (Obsoleted by RFC 4292) ** Obsolete normative reference: RFC 2571 (ref. '2') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '5') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '9') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '10') ** Obsolete normative reference: RFC 1906 (ref. '11') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '12') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '13') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '14') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '15') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '16') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '17') (Obsoleted by RFC 3410) Summary: 16 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPv6 MIB Revision Design Team Bill Fenner 2 INTERNET-DRAFT AT&T Research 3 Expires: January 2002 Brian Haberman 4 Nortel Networks 5 Juergen Schoenwalder 6 TU Braunschweig 7 Dave Thaler 8 Microsoft 9 July 2001 11 IP Forwarding Table MIB 12 draft-ietf-ipngwg-rfc2096-update-00.txt 14 Status of this Document 16 This document is an Internet-Draft and is in full conformance with all 17 provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering Task 20 Force (IETF), its areas, and its working groups. Note that other groups 21 may also distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference material 26 or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This document is a product of the IPv6 MIB Revision Design Team. 35 Comments should be addressed to the authors, or the mailing list at 36 ipng@sunroof.eng.sun.com. 38 Copyright Notice 40 Copyright (C) The Internet Society (2001). All Rights Reserved. 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) for 45 use with network management protocols in the Internet community. In 46 particular, it describes managed objects used for implementations of the 47 Internet Protocol (IP) in an IP version independent manner. 49 Table of Contents 51 1. The SNMP Management Framework . . . . . . . . . . . . . . . . . . 3 52 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 4 53 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 5. Open Issues / To Do . . . . . . . . . . . . . . . . . . . . . . . 27 56 6. Acknoledgments. . . . . . . . . . . . . . . . . . . . . . . . . . 28 57 7. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 58 8. Security Considerations . . . . . . . . . . . . . . . . . . . . . 29 59 9. Editor's Address. . . . . . . . . . . . . . . . . . . . . . . . . 30 60 10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 30 62 1. The SNMP Management Framework 64 The SNMP Management Framework presently consists of five major 65 components: 67 o An overall architecture, described in RFC 2571 [2]. 69 o Mechanisms for describing and naming objects and events for the 70 purpose of management. The first version of this Structure of 71 Management Information (SMI) is called SMIv1 and described in STD 16, 72 RFC 1155 [3], STD 16, RFC 1212 [4] and RFC 1215 [5]. The second 73 version, called SMIv2, is described in STD 58, RFC 2578 [6], STD 58, 74 RFC 2579 [7] and STD 58, RFC 2580 [8]. 76 o Message protocols for transferring management information. The first 77 version of the SNMP message protocol is called SNMPv1 and described in 78 STD 15, RFC 1157 [9]. A second version of the SNMP message protocol, 79 which is not an Internet standards track protocol, is called SNMPv2c 80 and described in RFC 1901 [10] and RFC 1906 [11]. The third version of 81 the message protocol is called SNMPv3 and described in RFC 1906 [11], 82 RFC 2572 [12] and RFC 2574 [13]. 84 o Protocol operations for accessing management information. The first 85 set of protocol operations and associated PDU formats is described in 86 STD 15, RFC 1157 [9]. A second set of protocol operations and 87 associated PDU formats is described in RFC 1905 [14]. 89 o A set of fundamental applications described in RFC 2573 [15] and the 90 view-based access control mechanism described in RFC 2575 [16]. 92 A more detailed introduction to the current SNMP Management Framework 93 can be found in RFC 2570 [17]. 95 Managed objects are accessed via a virtual information store, termed the 96 Management Information Base or MIB. Objects in the MIB are defined 97 using the mechanisms defined in the SMI. 99 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 100 conforming to the SMIv1 can be produced through the appropriate 101 translations. The resulting translated MIB must be semantically 102 equivalent, except where objects or events are omitted because no 103 translation is possible (use of Counter64). Some machine readable 104 information in SMIv2 will be converted into textual descriptions in 105 SMIv1 during the translation process. However, this loss of machine 106 readable information is not considered to change the semantics of the 107 MIB. 109 2. Revision History 111 Changes from draft-ops-rfc2096-update-00.txt: 113 12 Jul 2001 115 Renamed to IPNG working group draft 117 Added scopes to the uses of instance 119 Added inetCidrRouteDiscards to replace ipRoutingDiscards 121 Fixed some remaining ipCidr*/inetCidr* confusion in DESCRIPTIONs 123 Changes from first draft posted to v6mib mailing list: 125 23 Feb 2001 127 Update MODULE-IDENTITY 129 Delete inetCidrRouteTos, add inetCidrRouteInstance in INDEX of 130 inetCidrRouteTable. 132 Use InterfaceIndex, InetAddressPrefixLength and 133 InetAutonomousSystemNumber TC's, and limit the SIZE of 134 inetCidrRouteDest and inetCidrRouteNextHop 136 Update conformance info. 138 Added copyright and table of contents. 140 3. Overview 142 The MIB consists of one current table and two current global objects. 144 (1) The object inetCidrForwardNumber indicates the number of current 145 routes. This is primarily to avoid having to read the table in 146 order to determine this number. 148 (2) The object inetCidrForwardDiscards counts the number of routes that 149 were discarded even though they were invalid. 151 (3) The inetCidrRouteTable provides the ability to display IP version 152 independent multipath CIDR routes. 154 In addition, there is one deprecated table and object, and one obsolete 155 table and object, representing previous revisions of this MIB. 157 (1) The obsolete object ipForwardNumber represents the number of entries 158 in the obsolete ipForwardTable. 160 (2) The obsolete ipForwardTable updates the RFC 1213 ipRouteTable to 161 display multipath IP Routes. This is in turn obsoleted by the 162 ipCidrRouteTable. 164 (3) The deprecated object ipCidrRouteNumber represents the number of 165 entries in the deprecated ipCidrRouteTable. 167 (4) The deprecated ipCidrRouteTable updates the RFC 1213 ipRouteTable to 168 display multipath IP Routes having the same network number but 169 differing network masks. 171 4. Definitions 173 IP-FORWARD-MIB DEFINITIONS ::= BEGIN 175 IMPORTS 176 MODULE-IDENTITY, OBJECT-TYPE, 177 IpAddress, Integer32, Gauge32, 178 Unsigned32, Counter32 FROM SNMPv2-SMI 179 RowStatus FROM SNMPv2-TC 180 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 181 InterfaceIndex FROM IF-MIB 182 ip FROM IP-MIB 183 IANAipRouteProtocol FROM IANA-RTPROTO-MIB 184 InetAddress, InetAddressType, 185 InetAddressPrefixLength, 186 InetAutonomousSystemNumber FROM INET-ADDRESS-MIB; 188 ipForward MODULE-IDENTITY 189 LAST-UPDATED "200107130000Z" 190 ORGANIZATION "IETF IPv6 MIB Revision Team" 191 CONTACT-INFO 192 "Editor: 193 Bill Fenner 194 AT&T Labs - Research 195 75 Willow Rd 196 Menlo Park, CA 198 Phone: +1 650 330-7893 199 Email: " 200 DESCRIPTION 201 "The MIB module for the management of CIDR multipath IP 202 Routes." 203 REVISION "200107130000Z" 204 DESCRIPTION 205 "IP version neutral revision, published as RFC XXXX." 206 REVISION "9609190000Z" 207 DESCRIPTION 208 "Revised to support CIDR routes." 209 ::= { ip 24 } 211 inetCidrRouteNumber OBJECT-TYPE 212 SYNTAX Gauge32 213 MAX-ACCESS read-only 214 STATUS current 215 DESCRIPTION 216 "The number of current inetCidrRouteTable entries that are 217 not invalid." 218 ::= { ipForward 6 } 220 inetCidrRouteDiscards OBJECT-TYPE 221 SYNTAX Counter32 222 MAX-ACCESS read-only 223 STATUS current 224 DESCRIPTION 225 "The number of routing entries which were chosen to be 226 discarded even though they are valid. One possible reason 227 for discarding such an entry could be to free-up buffer 228 space for other routing entries." 229 ::= { ipForward 8 } 231 -- Inet CIDR Route Table 233 -- The Inet CIDR Route Table deprecates and replaces the ipCidrRoute 234 -- Table currently in the IP Forwarding Table MIB. 235 -- It adds IP protocol independence. 237 inetCidrRouteTable OBJECT-TYPE 238 SYNTAX SEQUENCE OF InetCidrRouteEntry 239 MAX-ACCESS not-accessible 240 STATUS current 241 DESCRIPTION 242 "This entity's IP Routing table." 243 REFERENCE 244 "RFC 1213 Section 6.6, The IP Group" 245 ::= { ipForward 7 } 247 inetCidrRouteEntry OBJECT-TYPE 248 SYNTAX InetCidrRouteEntry 249 MAX-ACCESS not-accessible 250 STATUS current 251 DESCRIPTION 252 "A particular route to a particular destination, under a 253 particular policy." 254 INDEX { 255 inetCidrRouteInstance, 256 inetCidrRouteDestType, 257 inetCidrRouteDest, 258 inetCidrRoutePfxLen, 259 inetCidrRouteNextHopType, 260 inetCidrRouteNextHop 261 } 262 ::= { inetCidrRouteTable 1 } 264 InetCidrRouteEntry ::= SEQUENCE { 265 inetCidrRouteInstance Unsigned32, 266 inetCidrRouteDestType InetAddressType, 267 inetCidrRouteDest InetAddress, 268 inetCidrRoutePfxLen InetAddressPrefixLength, 269 inetCidrRouteNextHopType InetAddressType, 270 inetCidrRouteNextHop InetAddress, 271 inetCidrRouteIfIndex InterfaceIndex, 272 inetCidrRouteType INTEGER, 273 inetCidrRouteProto IANAipRouteProtocol, 274 inetCidrRouteAge Integer32, 275 inetCidrRouteNextHopAS InetAutonomousSystemNumber, 276 inetCidrRouteMetric1 Integer32, 277 inetCidrRouteMetric2 Integer32, 278 inetCidrRouteMetric3 Integer32, 279 inetCidrRouteMetric4 Integer32, 280 inetCidrRouteMetric5 Integer32, 281 inetCidrRouteStatus RowStatus 282 } 284 inetCidrRouteInstance OBJECT-TYPE 285 SYNTAX Unsigned32 286 MAX-ACCESS not-accessible 287 STATUS current 288 DESCRIPTION 289 "The instance identifier of the (conceptual) routing table 290 containing this route. This identifier may be used to 291 represent multiple routing tables, type-of-service routing, 292 scopes, or any other use of multiple tables. 294 XXX This needs more discussion." 295 ::= { inetCidrRouteEntry 1 } 297 inetCidrRouteDestType OBJECT-TYPE 298 SYNTAX InetAddressType 299 MAX-ACCESS not-accessible 300 STATUS current 301 DESCRIPTION 302 "The type of inetCidrRouteDest. Only IPv4 and IPv6 addresses 303 are expected." 304 ::= { inetCidrRouteEntry 2 } 306 inetCidrRouteDest OBJECT-TYPE 307 SYNTAX InetAddress (SIZE(0..36)) 308 MAX-ACCESS not-accessible 309 STATUS current 310 DESCRIPTION 311 "The destination IP address of this route. 313 Any assignment (implicit or otherwise) of an instance of 314 this object to a value x must be rejected if the bitwise 315 logical-AND of x with the value of the mask formed from the 316 corresponding instance of the inetCidrRoutePfxLen object is 317 not equal to x." 318 ::= { inetCidrRouteEntry 3 } 320 inetCidrRoutePfxLen OBJECT-TYPE 321 SYNTAX InetAddressPrefixLength 322 MAX-ACCESS not-accessible 323 STATUS current 324 DESCRIPTION 325 "Indicate the number of leading one bits which form the mask 326 to be logical-ANDed with the destination address before 327 being compared to the value in the inetCidrRouteDest field. 329 Any assignment (implicit or otherwise) of an instance of 330 this object to a value x must be rejected if the bitwise 331 logical-AND of the mask formed from x with the value of the 332 corresponding instance of the inetCidrRouteDest object is 333 not equal to inetCidrRouteDest." 334 ::= { inetCidrRouteEntry 4 } 336 inetCidrRouteNextHopType OBJECT-TYPE 337 SYNTAX InetAddressType 338 MAX-ACCESS not-accessible 339 STATUS current 340 DESCRIPTION 341 "The address type of inetCidrRouteNextHop. Must be the same 342 as that of inetCidrRouteDestType, or unknown if there is no 343 next hop." 344 ::= { inetCidrRouteEntry 5 } 346 inetCidrRouteNextHop OBJECT-TYPE 347 SYNTAX InetAddress (SIZE(0..36)) 348 MAX-ACCESS not-accessible 349 STATUS current 350 DESCRIPTION 351 "On remote routes, the address of the next system en route; 352 Otherwise, a zero-length string." 353 ::= { inetCidrRouteEntry 6 } 355 inetCidrRouteIfIndex OBJECT-TYPE 356 SYNTAX InterfaceIndex 357 MAX-ACCESS read-create 358 STATUS current 359 DESCRIPTION 360 "The ifIndex value which identifies the local interface 361 through which the next hop of this route should be reached." 362 ::= { inetCidrRouteEntry 7 } 364 inetCidrRouteType OBJECT-TYPE 365 SYNTAX INTEGER { 366 other (1), -- not specified by this MIB 367 reject (2), -- route which discards traffic and 368 -- returns notification 369 local (3), -- local interface 370 remote (4), -- remote destination 371 blackhole(5) -- route which discards traffic silently 372 } 373 MAX-ACCESS read-create 374 STATUS current 375 DESCRIPTION 376 "The type of route. Note that local(3) refers to a route for 377 which the next hop is the final destination; remote(4) 378 refers to a route for which the next hop is not the final 379 destination. 381 Routes which do not result in traffic forwarding or 382 rejection should not be displayed even if the implementation 383 keeps them stored internally. 385 reject(2) refers to a route which, if matched, discards the 386 message as unreachable and returns a notification (e.g. ICMP 387 error) to the message sender. This is used in some 388 protocols as a means of correctly aggregating routes. 389 blackhole(5) refers to a route which, if matched, discards 390 the message silently." 391 ::= { inetCidrRouteEntry 8 } 393 inetCidrRouteProto OBJECT-TYPE 394 SYNTAX IANAipRouteProtocol 395 MAX-ACCESS read-only 396 STATUS current 397 DESCRIPTION 398 "The routing mechanism via which this route was learned. 399 Inclusion of values for gateway routing protocols is not 400 intended to imply that hosts should support those 401 protocols." 402 ::= { inetCidrRouteEntry 9 } 404 -- XXX new type? TimeTicks? 405 inetCidrRouteAge OBJECT-TYPE 406 SYNTAX Integer32 407 MAX-ACCESS read-only 408 STATUS current 409 DESCRIPTION 410 "The number of seconds since this route was last updated or 411 otherwise determined to be correct. Note that no semantics 412 of `too old' can be implied except through knowledge of the 413 routing protocol by which the route was learned." 414 ::= { inetCidrRouteEntry 10 } 416 inetCidrRouteNextHopAS OBJECT-TYPE 417 SYNTAX InetAutonomousSystemNumber 418 MAX-ACCESS read-create 419 STATUS current 420 DESCRIPTION 421 "The Autonomous System Number of the Next Hop. The semantics 422 of this object are determined by the routing-protocol 423 specified in the route's inetCidrRouteProto value. When this 424 object is unknown or not relevant its value should be set to 425 zero." 426 DEFVAL { 0 } 427 ::= { inetCidrRouteEntry 11 } 429 inetCidrRouteMetric1 OBJECT-TYPE 430 SYNTAX Integer32 431 MAX-ACCESS read-create 432 STATUS current 433 DESCRIPTION 434 "The primary routing metric for this route. The semantics of 435 this metric are determined by the routing-protocol specified 436 in the route's inetCidrRouteProto value. If this metric is 437 not used, its value should be set to -1." 438 DEFVAL { -1 } 439 ::= { inetCidrRouteEntry 12 } 441 inetCidrRouteMetric2 OBJECT-TYPE 442 SYNTAX Integer32 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "An alternate routing metric for this route. The semantics 447 of this metric are determined by the routing-protocol 448 specified in the route's inetCidrRouteProto value. If this 449 metric is not used, its value should be set to -1." 450 DEFVAL { -1 } 451 ::= { inetCidrRouteEntry 13 } 453 inetCidrRouteMetric3 OBJECT-TYPE 454 SYNTAX Integer32 455 MAX-ACCESS read-create 456 STATUS current 457 DESCRIPTION 458 "An alternate routing metric for this route. The semantics 459 of this metric are determined by the routing-protocol 460 specified in the route's inetCidrRouteProto value. If this 461 metric is not used, its value should be set to -1." 462 DEFVAL { -1 } 463 ::= { inetCidrRouteEntry 14 } 465 inetCidrRouteMetric4 OBJECT-TYPE 466 SYNTAX Integer32 467 MAX-ACCESS read-create 468 STATUS current 469 DESCRIPTION 470 "An alternate routing metric for this route. The semantics 471 of this metric are determined by the routing-protocol 472 specified in the route's inetCidrRouteProto value. If this 473 metric is not used, its value should be set to -1." 474 DEFVAL { -1 } 475 ::= { inetCidrRouteEntry 15 } 477 inetCidrRouteMetric5 OBJECT-TYPE 478 SYNTAX Integer32 479 MAX-ACCESS read-create 480 STATUS current 481 DESCRIPTION 482 "An alternate routing metric for this route. The semantics 483 of this metric are determined by the routing-protocol 484 specified in the route's inetCidrRouteProto value. If this 485 metric is not used, its value should be set to -1." 486 DEFVAL { -1 } 487 ::= { inetCidrRouteEntry 16 } 489 inetCidrRouteStatus OBJECT-TYPE 490 SYNTAX RowStatus 491 MAX-ACCESS read-create 492 STATUS current 493 DESCRIPTION 494 "The row status variable, used according to row installation 495 and removal conventions." 496 ::= { inetCidrRouteEntry 17 } 498 -- Conformance information 500 ipForwardConformance OBJECT IDENTIFIER ::= { ipForward 5 } 502 ipForwardGroups OBJECT IDENTIFIER ::= { ipForwardConformance 1 } 503 ipForwardCompliances OBJECT IDENTIFIER ::= { ipForwardConformance 2 } 505 -- Compliance statements 507 ipForwardCompliance2 MODULE-COMPLIANCE 508 STATUS current 509 DESCRIPTION 510 "The compliance statement for systems which have routing 511 tables. XXX is this right?" 512 MODULE -- this module 513 MANDATORY-GROUPS { inetForwardCidrRouteGroup } 514 ::= { ipForwardCompliances 3 } 516 -- units of conformance 518 inetForwardCidrRouteGroup OBJECT-GROUP 519 OBJECTS { inetCidrRouteNumber, inetCidrRouteDiscards, 520 inetCidrRouteIfIndex, inetCidrRouteType, 521 inetCidrRouteProto, inetCidrRouteAge, 522 inetCidrRouteNextHopAS, inetCidrRouteMetric1, 523 inetCidrRouteMetric2, inetCidrRouteMetric3, 524 inetCidrRouteMetric4, inetCidrRouteMetric5, inetCidrRouteStatus 525 } 526 STATUS current 527 DESCRIPTION 528 "The IP version independent CIDR Route Table." 529 ::= { ipForwardGroups 4 } 531 -- Deprecated Objects 533 ipCidrRouteNumber OBJECT-TYPE 534 SYNTAX Gauge32 535 MAX-ACCESS read-only 536 STATUS deprecated 537 DESCRIPTION 538 "The number of current ipCidrRouteTable entries that are not 539 invalid. This object is deprecated in favor of 540 inetCidrRouteNumber and the inetCidrRouteTable." 541 ::= { ipForward 3 } 543 -- IP CIDR Route Table 545 -- The IP CIDR Route Table obsoletes and replaces the ipRoute 546 -- Table current in MIB-I and MIB-II and the IP Forwarding Table. 547 -- It adds knowledge of the autonomous system of the next hop, 548 -- multiple next hops, and policy routing, and Classless 549 -- Inter-Domain Routing. 551 ipCidrRouteTable OBJECT-TYPE 552 SYNTAX SEQUENCE OF IpCidrRouteEntry 553 MAX-ACCESS not-accessible 554 STATUS deprecated 555 DESCRIPTION 556 "This entity's IP Routing table. This table has been 557 deprecated in favor of the IP version neutral 558 inetCidrRouteTable." 559 REFERENCE 560 "RFC 1213 Section 6.6, The IP Group" 561 ::= { ipForward 4 } 563 ipCidrRouteEntry OBJECT-TYPE 564 SYNTAX IpCidrRouteEntry 565 MAX-ACCESS not-accessible 566 STATUS deprecated 567 DESCRIPTION 568 "A particular route to a particular destination, under a 569 particular policy." 570 INDEX { 571 ipCidrRouteDest, 572 ipCidrRouteMask, 573 ipCidrRouteTos, 574 ipCidrRouteNextHop 575 } 576 ::= { ipCidrRouteTable 1 } 578 IpCidrRouteEntry ::= SEQUENCE { 579 ipCidrRouteDest IpAddress, 580 ipCidrRouteMask IpAddress, 581 ipCidrRouteTos Integer32, 582 ipCidrRouteNextHop IpAddress, 583 ipCidrRouteIfIndex Integer32, 584 ipCidrRouteType INTEGER, 585 ipCidrRouteProto INTEGER, 586 ipCidrRouteAge Integer32, 587 ipCidrRouteInfo OBJECT IDENTIFIER, 588 ipCidrRouteNextHopAS Integer32, 589 ipCidrRouteMetric1 Integer32, 590 ipCidrRouteMetric2 Integer32, 591 ipCidrRouteMetric3 Integer32, 592 ipCidrRouteMetric4 Integer32, 593 ipCidrRouteMetric5 Integer32, 594 ipCidrRouteStatus RowStatus 595 } 597 ipCidrRouteDest OBJECT-TYPE 598 SYNTAX IpAddress 599 MAX-ACCESS read-only 600 STATUS deprecated 601 DESCRIPTION 602 "The destination IP address of this route. 604 This object may not take a Multicast (Class D) address 605 value. 607 Any assignment (implicit or otherwise) of an instance of 608 this object to a value x must be rejected if the bitwise 609 logical-AND of x with the value of the corresponding 610 instance of the ipCidrRouteMask object is not equal to x." 611 ::= { ipCidrRouteEntry 1 } 613 ipCidrRouteMask OBJECT-TYPE 614 SYNTAX IpAddress 615 MAX-ACCESS read-only 616 STATUS deprecated 617 DESCRIPTION 618 "Indicate the mask to be logical-ANDed with the destination 619 address before being compared to the value in the 620 ipCidrRouteDest field. For those systems that do not 621 support arbitrary subnet masks, an agent constructs the 622 value of the ipCidrRouteMask by reference to the IP Address 623 Class. 625 Any assignment (implicit or otherwise) of an instance of 626 this object to a value x must be rejected if the bitwise 627 logical-AND of x with the value of the corresponding 628 instance of the ipCidrRouteDest object is not equal to 629 ipCidrRouteDest." 630 ::= { ipCidrRouteEntry 2 } 632 -- The following convention is included for specification 633 -- of TOS Field contents. At this time, the Host Requirements 634 -- and the Router Requirements documents disagree on the width 635 -- of the TOS field. This mapping describes the Router 636 -- Requirements mapping, and leaves room to widen the TOS field 637 -- without impact to fielded systems. 639 ipCidrRouteTos OBJECT-TYPE 640 SYNTAX Integer32 (0..2147483647) 641 MAX-ACCESS read-only 642 STATUS deprecated 643 DESCRIPTION 644 "The policy specifier is the IP TOS Field. The encoding 645 of IP TOS is as specified by the following convention. 646 Zero indicates the default path if no more specific 647 policy applies. 649 +-----+-----+-----+-----+-----+-----+-----+-----+ 650 | | | | 651 | PRECEDENCE | TYPE OF SERVICE | 0 | 652 | | | | 653 +-----+-----+-----+-----+-----+-----+-----+-----+ 655 IP TOS IP TOS 656 Field Policy Field Policy 657 Contents Code Contents Code 658 0 0 0 0 ==> 0 0 0 0 1 ==> 2 659 0 0 1 0 ==> 4 0 0 1 1 ==> 6 660 0 1 0 0 ==> 8 0 1 0 1 ==> 10 661 0 1 1 0 ==> 12 0 1 1 1 ==> 14 662 1 0 0 0 ==> 16 1 0 0 1 ==> 18 663 1 0 1 0 ==> 20 1 0 1 1 ==> 22 664 1 1 0 0 ==> 24 1 1 0 1 ==> 26 665 1 1 1 0 ==> 28 1 1 1 1 ==> 30" 666 ::= { ipCidrRouteEntry 3 } 668 ipCidrRouteNextHop OBJECT-TYPE 669 SYNTAX IpAddress 670 MAX-ACCESS read-only 671 STATUS deprecated 672 DESCRIPTION 673 "On remote routes, the address of the next system en route; 674 Otherwise, 0.0.0.0." 675 ::= { ipCidrRouteEntry 4 } 677 ipCidrRouteIfIndex OBJECT-TYPE 678 SYNTAX Integer32 679 MAX-ACCESS read-create 680 STATUS deprecated 681 DESCRIPTION 682 "The ifIndex value which identifies the local interface 683 through which the next hop of this route should be reached." 684 DEFVAL { 0 } 685 ::= { ipCidrRouteEntry 5 } 687 ipCidrRouteType OBJECT-TYPE 688 SYNTAX INTEGER { 689 other (1), -- not specified by this MIB 690 reject (2), -- route which discards traffic 691 local (3), -- local interface 692 remote (4) -- remote destination 693 } 694 MAX-ACCESS read-create 695 STATUS deprecated 696 DESCRIPTION 697 "The type of route. Note that local(3) refers to a route for 698 which the next hop is the final destination; remote(4) 699 refers to a route for which the next hop is not the final 700 destination. 702 Routes which do not result in traffic forwarding or 703 rejection should not be displayed even if the implementation 704 keeps them stored internally. 706 reject (2) refers to a route which, if matched, discards the 707 message as unreachable. This is used in some protocols as a 708 means of correctly aggregating routes." 709 ::= { ipCidrRouteEntry 6 } 711 ipCidrRouteProto OBJECT-TYPE 712 SYNTAX INTEGER { 713 other (1), -- not specified 714 local (2), -- local interface 715 netmgmt (3), -- static route 716 icmp (4), -- result of ICMP Redirect 718 -- the following are all dynamic 719 -- routing protocols 720 egp (5), -- Exterior Gateway Protocol 721 ggp (6), -- Gateway-Gateway Protocol 722 hello (7), -- FuzzBall HelloSpeak 723 rip (8), -- Berkeley RIP or RIP-II 724 isIs (9), -- Dual IS-IS 725 esIs (10), -- ISO 9542 726 ciscoIgrp (11), -- Cisco IGRP 727 bbnSpfIgp (12), -- BBN SPF IGP 728 ospf (13), -- Open Shortest Path First 729 bgp (14), -- Border Gateway Protocol 730 idpr (15), -- InterDomain Policy Routing 731 ciscoEigrp (16) -- Cisco EIGRP 732 } 733 MAX-ACCESS read-only 734 STATUS deprecated 735 DESCRIPTION 736 "The routing mechanism via which this route was learned. 737 Inclusion of values for gateway routing protocols is not 738 intended to imply that hosts should support those 739 protocols." 740 ::= { ipCidrRouteEntry 7 } 742 ipCidrRouteAge OBJECT-TYPE 743 SYNTAX Integer32 744 MAX-ACCESS read-only 745 STATUS deprecated 746 DESCRIPTION 747 "The number of seconds since this route was last updated or 748 otherwise determined to be correct. Note that no semantics 749 of `too old' can be implied except through knowledge of the 750 routing protocol by which the route was learned." 751 DEFVAL { 0 } 752 ::= { ipCidrRouteEntry 8 } 754 ipCidrRouteInfo OBJECT-TYPE 755 SYNTAX OBJECT IDENTIFIER 756 MAX-ACCESS read-create 757 STATUS deprecated 758 DESCRIPTION 759 "A reference to MIB definitions specific to the particular 760 routing protocol which is responsible for this route, as 761 determined by the value specified in the route's 762 ipCidrRouteProto value. If this information is not present, 763 its value should be set to the OBJECT IDENTIFIER { 0 0 }, 764 which is a syntactically valid object identifier, and any 765 implementation conforming to ASN.1 and the Basic Encoding 766 Rules must be able to generate and recognize this value." 767 ::= { ipCidrRouteEntry 9 } 769 ipCidrRouteNextHopAS OBJECT-TYPE 770 SYNTAX Integer32 771 MAX-ACCESS read-create 772 STATUS deprecated 773 DESCRIPTION 774 "The Autonomous System Number of the Next Hop. The semantics 775 of this object are determined by the routing-protocol 776 specified in the route's ipCidrRouteProto value. When this 777 object is unknown or not relevant its value should be set to 778 zero." 779 DEFVAL { 0 } 780 ::= { ipCidrRouteEntry 10 } 782 ipCidrRouteMetric1 OBJECT-TYPE 783 SYNTAX Integer32 784 MAX-ACCESS read-create 785 STATUS deprecated 786 DESCRIPTION 787 "The primary routing metric for this route. The semantics of 788 this metric are determined by the routing-protocol specified 789 in the route's ipCidrRouteProto value. If this metric is 790 not used, its value should be set to -1." 791 DEFVAL { -1 } 792 ::= { ipCidrRouteEntry 11 } 794 ipCidrRouteMetric2 OBJECT-TYPE 795 SYNTAX Integer32 796 MAX-ACCESS read-create 797 STATUS deprecated 798 DESCRIPTION 799 "An alternate routing metric for this route. The semantics 800 of this metric are determined by the routing-protocol 801 specified in the route's ipCidrRouteProto value. If this 802 metric is not used, its value should be set to -1." 803 DEFVAL { -1 } 804 ::= { ipCidrRouteEntry 12 } 806 ipCidrRouteMetric3 OBJECT-TYPE 807 SYNTAX Integer32 808 MAX-ACCESS read-create 809 STATUS deprecated 810 DESCRIPTION 811 "An alternate routing metric for this route. The semantics 812 of this metric are determined by the routing-protocol 813 specified in the route's ipCidrRouteProto value. If this 814 metric is not used, its value should be set to -1." 815 DEFVAL { -1 } 816 ::= { ipCidrRouteEntry 13 } 818 ipCidrRouteMetric4 OBJECT-TYPE 819 SYNTAX Integer32 820 MAX-ACCESS read-create 821 STATUS deprecated 822 DESCRIPTION 823 "An alternate routing metric for this route. The semantics 824 of this metric are determined by the routing-protocol 825 specified in the route's ipCidrRouteProto value. If this 826 metric is not used, its value should be set to -1." 827 DEFVAL { -1 } 828 ::= { ipCidrRouteEntry 14 } 830 ipCidrRouteMetric5 OBJECT-TYPE 831 SYNTAX Integer32 832 MAX-ACCESS read-create 833 STATUS deprecated 834 DESCRIPTION 835 "An alternate routing metric for this route. The semantics 836 of this metric are determined by the routing-protocol 837 specified in the route's ipCidrRouteProto value. If this 838 metric is not used, its value should be set to -1." 839 DEFVAL { -1 } 840 ::= { ipCidrRouteEntry 15 } 842 ipCidrRouteStatus OBJECT-TYPE 843 SYNTAX RowStatus 844 MAX-ACCESS read-create 845 STATUS deprecated 846 DESCRIPTION 847 "The row status variable, used according to row installation 848 and removal conventions." 849 ::= { ipCidrRouteEntry 16 } 851 -- compliance statements 853 ipForwardCompliance MODULE-COMPLIANCE 854 STATUS deprecated 855 DESCRIPTION 856 "The compliance statement for SNMPv2 entities which implement 857 the ipForward MIB." 859 MODULE -- this module 860 MANDATORY-GROUPS { ipForwardCidrRouteGroup } 862 ::= { ipForwardCompliances 1 } 864 -- units of conformance 866 ipForwardCidrRouteGroup OBJECT-GROUP 867 OBJECTS { ipCidrRouteNumber, 868 ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, 869 ipCidrRouteNextHop, ipCidrRouteIfIndex, ipCidrRouteType, 870 ipCidrRouteProto, ipCidrRouteAge, ipCidrRouteInfo, 871 ipCidrRouteNextHopAS, ipCidrRouteMetric1, 872 ipCidrRouteMetric2, ipCidrRouteMetric3, 873 ipCidrRouteMetric4, ipCidrRouteMetric5, ipCidrRouteStatus 874 } 875 STATUS deprecated 876 DESCRIPTION 877 "The CIDR Route Table." 878 ::= { ipForwardGroups 3 } 880 -- Obsoleted Definitions - Objects 882 ipForwardNumber OBJECT-TYPE 883 SYNTAX Gauge32 884 MAX-ACCESS read-only 885 STATUS obsolete 886 DESCRIPTION 887 "The number of current ipForwardTable entries that are not 888 invalid." 889 ::= { ipForward 1 } 891 -- IP Forwarding Table 893 -- The IP Forwarding Table obsoletes and replaces the ipRoute 894 -- Table current in MIB-I and MIB-II. It adds knowledge of 895 -- the autonomous system of the next hop, multiple next hop 896 -- support, and policy routing support. 898 ipForwardTable OBJECT-TYPE 899 SYNTAX SEQUENCE OF IpForwardEntry 900 MAX-ACCESS not-accessible 901 STATUS obsolete 902 DESCRIPTION 903 "This entity's IP Routing table." 904 REFERENCE 905 "RFC 1213 Section 6.6, The IP Group" 906 ::= { ipForward 2 } 908 ipForwardEntry OBJECT-TYPE 909 SYNTAX IpForwardEntry 910 MAX-ACCESS not-accessible 911 STATUS obsolete 912 DESCRIPTION 913 "A particular route to a particular destination, under a 914 particular policy." 915 INDEX { 916 ipForwardDest, 917 ipForwardProto, 918 ipForwardPolicy, 919 ipForwardNextHop 920 } 921 ::= { ipForwardTable 1 } 923 IpForwardEntry ::= SEQUENCE { 924 ipForwardDest IpAddress, 925 ipForwardMask IpAddress, 926 ipForwardPolicy Integer32, 927 ipForwardNextHop IpAddress, 928 ipForwardIfIndex Integer32, 929 ipForwardType INTEGER, 930 ipForwardProto INTEGER, 931 ipForwardAge Integer32, 932 ipForwardInfo OBJECT IDENTIFIER, 933 ipForwardNextHopAS Integer32, 934 ipForwardMetric1 Integer32, 935 ipForwardMetric2 Integer32, 936 ipForwardMetric3 Integer32, 937 ipForwardMetric4 Integer32, 938 ipForwardMetric5 Integer32 939 } 941 ipForwardDest OBJECT-TYPE 942 SYNTAX IpAddress 943 MAX-ACCESS read-only 944 STATUS obsolete 945 DESCRIPTION 946 "The destination IP address of this route. An entry with a 947 value of 0.0.0.0 is considered a default route. 949 This object may not take a Multicast (Class D) address 950 value. 952 Any assignment (implicit or otherwise) of an instance of 953 this object to a value x must be rejected if the bitwise 954 logical-AND of x with the value of the corresponding 955 instance of the ipForwardMask object is not equal to x." 957 ::= { ipForwardEntry 1 } 959 ipForwardMask OBJECT-TYPE 960 SYNTAX IpAddress 961 MAX-ACCESS read-create 962 STATUS obsolete 963 DESCRIPTION 964 "Indicate the mask to be logical-ANDed with the destination 965 address before being compared to the value in the 966 ipForwardDest field. For those systems that do not support 967 arbitrary subnet masks, an agent constructs the value of the 968 ipForwardMask by reference to the IP Address Class. 970 Any assignment (implicit or otherwise) of an instance of 971 this object to a value x must be rejected if the bitwise 972 logical-AND of x with the value of the corresponding 973 instance of the ipForwardDest object is not equal to 974 ipForwardDest." 975 DEFVAL { '00000000'h } -- 0.0.0.0 976 ::= { ipForwardEntry 2 } 978 -- The following convention is included for specification 979 -- of TOS Field contents. At this time, the Host Requirements 980 -- and the Router Requirements documents disagree on the width 981 -- of the TOS field. This mapping describes the Router 982 -- Requirements mapping, and leaves room to widen the TOS field 983 -- without impact to fielded systems. 985 ipForwardPolicy OBJECT-TYPE 986 SYNTAX Integer32 (0..2147483647) 987 MAX-ACCESS read-only 988 STATUS obsolete 989 DESCRIPTION 990 "The general set of conditions that would cause 991 the selection of one multipath route (set of 992 next hops for a given destination) is referred 993 to as 'policy'. 995 Unless the mechanism indicated by ipForwardProto 996 specifies otherwise, the policy specifier is 997 the IP TOS Field. The encoding of IP TOS is as 998 specified by the following convention. Zero 999 indicates the default path if no more specific 1000 policy applies. 1002 +-----+-----+-----+-----+-----+-----+-----+-----+ 1003 | | | | 1004 | PRECEDENCE | TYPE OF SERVICE | 0 | 1005 | | | | 1006 +-----+-----+-----+-----+-----+-----+-----+-----+ 1008 IP TOS IP TOS 1009 Field Policy Field Policy 1010 Contents Code Contents Code 1011 0 0 0 0 ==> 0 0 0 0 1 ==> 2 1012 0 0 1 0 ==> 4 0 0 1 1 ==> 6 1013 0 1 0 0 ==> 8 0 1 0 1 ==> 10 1014 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1015 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1016 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1017 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1018 1 1 1 0 ==> 28 1 1 1 1 ==> 30 1020 Protocols defining 'policy' otherwise must either 1021 define a set of values which are valid for 1022 this object or must implement an integer-instanced 1023 policy table for which this object's 1024 value acts as an index." 1025 ::= { ipForwardEntry 3 } 1027 ipForwardNextHop OBJECT-TYPE 1028 SYNTAX IpAddress 1029 MAX-ACCESS read-only 1030 STATUS obsolete 1031 DESCRIPTION 1032 "On remote routes, the address of the next system en route; 1033 Otherwise, 0.0.0.0." 1034 ::= { ipForwardEntry 4 } 1036 ipForwardIfIndex OBJECT-TYPE 1037 SYNTAX Integer32 1038 MAX-ACCESS read-create 1039 STATUS obsolete 1040 DESCRIPTION 1041 "The ifIndex value which identifies the local interface 1042 through which the next hop of this route should be reached." 1043 DEFVAL { 0 } 1044 ::= { ipForwardEntry 5 } 1046 ipForwardType OBJECT-TYPE 1047 SYNTAX INTEGER { 1048 other (1), -- not specified by this MIB 1049 invalid (2), -- logically deleted 1050 local (3), -- local interface 1051 remote (4) -- remote destination 1052 } 1054 MAX-ACCESS read-create 1055 STATUS obsolete 1056 DESCRIPTION 1057 "The type of route. Note that local(3) refers to a route for 1058 which the next hop is the final destination; remote(4) 1059 refers to a route for which the next hop is not the final 1060 destination. 1062 Setting this object to the value invalid(2) has the effect 1063 of invalidating the corresponding entry in the 1064 ipForwardTable object. That is, it effectively 1065 disassociates the destination identified with said entry 1066 from the route identified with said entry. It is an 1067 implementation-specific matter as to whether the agent 1068 removes an invalidated entry from the table. Accordingly, 1069 management stations must be prepared to receive tabular 1070 information from agents that corresponds to entries not 1071 currently in use. Proper interpretation of such entries 1072 requires examination of the relevant ipForwardType object." 1073 DEFVAL { invalid } 1074 ::= { ipForwardEntry 6 } 1076 ipForwardProto OBJECT-TYPE 1077 SYNTAX INTEGER { 1078 other (1), -- not specified 1079 local (2), -- local interface 1080 netmgmt (3), -- static route 1081 icmp (4), -- result of ICMP Redirect 1083 -- the following are all dynamic 1084 -- routing protocols 1085 egp (5), -- Exterior Gateway Protocol 1086 ggp (6), -- Gateway-Gateway Protocol 1087 hello (7), -- FuzzBall HelloSpeak 1088 rip (8), -- Berkeley RIP or RIP-II 1089 is-is (9), -- Dual IS-IS 1090 es-is (10), -- ISO 9542 1091 ciscoIgrp (11), -- Cisco IGRP 1092 bbnSpfIgp (12), -- BBN SPF IGP 1093 ospf (13), -- Open Shortest Path First 1094 bgp (14), -- Border Gateway Protocol 1095 idpr (15) -- InterDomain Policy Routing 1096 } 1097 MAX-ACCESS read-only 1098 STATUS obsolete 1099 DESCRIPTION 1100 "The routing mechanism via which this route was learned. 1101 Inclusion of values for gateway routing protocols is not 1102 intended to imply that hosts should support those 1103 protocols." 1104 ::= { ipForwardEntry 7 } 1106 ipForwardAge OBJECT-TYPE 1107 SYNTAX Integer32 1108 MAX-ACCESS read-only 1109 STATUS obsolete 1110 DESCRIPTION 1111 "The number of seconds since this route was last updated or 1112 otherwise determined to be correct. Note that no semantics 1113 of `too old' can be implied except through knowledge of the 1114 routing protocol by which the route was learned." 1115 DEFVAL { 0 } 1116 ::= { ipForwardEntry 8 } 1118 ipForwardInfo OBJECT-TYPE 1119 SYNTAX OBJECT IDENTIFIER 1120 MAX-ACCESS read-create 1121 STATUS obsolete 1122 DESCRIPTION 1123 "A reference to MIB definitions specific to the particular 1124 routing protocol which is responsible for this route, as 1125 determined by the value specified in the route's 1126 ipForwardProto value. If this information is not present, 1127 its value should be set to the OBJECT IDENTIFIER { 0 0 }, 1128 which is a syntactically valid object identifier, and any 1129 implementation conforming to ASN.1 and the Basic Encoding 1130 Rules must be able to generate and recognize this value." 1131 ::= { ipForwardEntry 9 } 1133 ipForwardNextHopAS OBJECT-TYPE 1134 SYNTAX Integer32 1135 MAX-ACCESS read-create 1136 STATUS obsolete 1137 DESCRIPTION 1138 "The Autonomous System Number of the Next Hop. When this is 1139 unknown or not relevant to the protocol indicated by 1140 ipForwardProto, zero." 1141 DEFVAL { 0 } 1142 ::= { ipForwardEntry 10 } 1144 ipForwardMetric1 OBJECT-TYPE 1145 SYNTAX Integer32 1146 MAX-ACCESS read-create 1147 STATUS obsolete 1148 DESCRIPTION 1149 "The primary routing metric for this route. The semantics of 1150 this metric are determined by the routing-protocol specified 1151 in the route's ipForwardProto value. If this metric is not 1152 used, its value should be set to -1." 1153 DEFVAL { -1 } 1154 ::= { ipForwardEntry 11 } 1156 ipForwardMetric2 OBJECT-TYPE 1157 SYNTAX Integer32 1158 MAX-ACCESS read-create 1159 STATUS obsolete 1160 DESCRIPTION 1161 "An alternate routing metric for this route. The semantics 1162 of this metric are determined by the routing-protocol 1163 specified in the route's ipForwardProto value. If this 1164 metric is not used, its value should be set to -1." 1165 DEFVAL { -1 } 1166 ::= { ipForwardEntry 12 } 1168 ipForwardMetric3 OBJECT-TYPE 1169 SYNTAX Integer32 1170 MAX-ACCESS read-create 1171 STATUS obsolete 1172 DESCRIPTION 1173 "An alternate routing metric for this route. The semantics 1174 of this metric are determined by the routing-protocol 1175 specified in the route's ipForwardProto value. If this 1176 metric is not used, its value should be set to -1." 1177 DEFVAL { -1 } 1178 ::= { ipForwardEntry 13 } 1180 ipForwardMetric4 OBJECT-TYPE 1181 SYNTAX Integer32 1182 MAX-ACCESS read-create 1183 STATUS obsolete 1184 DESCRIPTION 1185 "An alternate routing metric for this route. The semantics 1186 of this metric are determined by the routing-protocol 1187 specified in the route's ipForwardProto value. If this 1188 metric is not used, its value should be set to -1." 1189 DEFVAL { -1 } 1190 ::= { ipForwardEntry 14 } 1192 ipForwardMetric5 OBJECT-TYPE 1193 SYNTAX Integer32 1194 MAX-ACCESS read-create 1195 STATUS obsolete 1196 DESCRIPTION 1197 "An alternate routing metric for this route. The semantics 1198 of this metric are determined by the routing-protocol 1199 specified in the route's ipForwardProto value. If this 1200 metric is not used, its value should be set to -1." 1201 DEFVAL { -1 } 1202 ::= { ipForwardEntry 15 } 1204 -- Obsoleted Definitions - Groups 1205 -- compliance statements 1207 ipForwardOldCompliance MODULE-COMPLIANCE 1208 STATUS obsolete 1209 DESCRIPTION 1210 "The compliance statement for SNMP entities which implement 1211 the ipForward MIB." 1213 MODULE -- this module 1214 MANDATORY-GROUPS { ipForwardMultiPathGroup } 1216 ::= { ipForwardCompliances 2 } 1218 ipForwardMultiPathGroup OBJECT-GROUP 1219 OBJECTS { ipForwardNumber, 1220 ipForwardDest, ipForwardMask, ipForwardPolicy, 1221 ipForwardNextHop, ipForwardIfIndex, ipForwardType, 1222 ipForwardProto, ipForwardAge, ipForwardInfo, 1223 ipForwardNextHopAS, 1224 ipForwardMetric1, ipForwardMetric2, ipForwardMetric3, 1225 ipForwardMetric4, ipForwardMetric5 1226 } 1227 STATUS obsolete 1228 DESCRIPTION 1229 "IP Multipath Route Table." 1230 ::= { ipForwardGroups 2 } 1232 END 1234 5. Open Issues / To Do 1236 Trash this completely and start from scratch with a new MIB? 1238 The Instance Identifier can be used for IPv6 scopes, for Diffserv Code 1239 Points, or any other multi-instance purpose. How to tell what a given 1240 instance means? 1241 Any other objects from RFC 2465's ipv6RouteTable? 1243 Better wording for ipForwardCompliance2? 1245 Note: more open issues / to do items scattered in comments in MIB. 1247 6. Acknoledgments 1249 This document contains objects modified from RFC 2096 [1]. 1251 7. References 1253 [1] F. Baker, "IP Forwarding Table MIB", RFC 2096, January 1997. 1255 [2] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1256 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1258 [3] Rose, M., and K. McCloghrie, "Structure and Identification of 1259 Management Information for TCP/IP-based Internets", STD 16, RFC 1260 1155, May 1990. 1262 [4] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1263 1212, March 1991. 1265 [5] Rose, M., "A Convention for Defining Traps for use with the SNMP", 1266 RFC 1215, March 1991. 1268 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1269 and S. Waldbusser, "Structure of Management Information Version 2 1270 (SMIv2)", STD 58, RFC 2578, April 1999. 1272 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1273 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1274 2579, April 1999. 1276 [8] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1277 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1278 2580, April 1999. 1280 [9] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1281 Management Protocol", STD 15, RFC 1157, May 1990. 1283 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1284 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1286 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1287 Mappings for Version 2 of the Simple Network Management Protocol 1288 (SNMPv2)", RFC 1906, January 1996. 1290 [12] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1291 Processing and Dispatching for the Simple Network Management 1292 Protocol (SNMP)", RFC 2572, April 1999. 1294 [13] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1295 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1296 2574, April 1999. 1298 [14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1299 Operations for Version 2 of the Simple Network Management Protocol 1300 (SNMPv2)", RFC 1905, January 1996. 1302 [15] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1303 2573, April 1999. 1305 [16] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1306 Control Model (VACM) for the Simple Network Management Protocol 1307 (SNMP)", RFC 2575, April 1999. 1309 [17] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1310 Version 3 of the Internet-standard Network Management Framework", 1311 RFC 2570, April 1999. 1313 8. Security Considerations 1315 There are a number of management objects defined in this MIB that have a 1316 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 1317 considered sensitive or vulnerable in some network environments. The 1318 support for SET operations in a non-secure environment without proper 1319 protection can have a negative effect on network operations. 1321 There are a number of managed objects in this MIB that may contain 1322 sensitive information. These are: 1324 The routing table can be used to discover information about the network 1325 topology within a domain. 1327 It is thus important to control even GET access to these objects and 1328 possibly to even encrypt the values of these object when sending them 1329 over the network via SNMP. Not all versions of SNMP provide features 1330 for such a secure environment. 1332 SNMPv1 by itself is not a secure environment. Even if the network 1333 itself is secure (for example by using IPSec), even then, there is no 1334 control as to who on the secure network is allowed to access and GET/SET 1335 (read/change/create/delete) the objects in this MIB. 1337 It is recommended that the implementers consider the security features 1338 as provided by the SNMPv3 framework. Specifically, the use of the User- 1339 based Security Model RFC 2574 [13] and the View-based Access Control 1340 Model RFC 2575 [16] is recommended. 1342 It is then a customer/user responsibility to ensure that the SNMP entity 1343 giving access to an instance of this MIB, is properly configured to give 1344 access to the objects only to those principals (users) that have 1345 legitimate rights to indeed GET or SET (change/create/delete) them. 1347 9. Editor's Address 1349 Bill Fenner 1350 AT&T Labs -- Research 1351 75 Willow Rd 1352 Menlo Park, CA 94025 1353 USA 1355 Email: fenner@research.att.com 1357 10. Full Copyright Statement 1359 Copyright (C) The Internet Society (2001). All Rights Reserved. 1361 This document and translations of it may be copied and furnished to 1362 others, and derivative works that comment on or otherwise explain it or 1363 assist in its implementation may be prepared, copied, published and 1364 distributed, in whole or in part, without restriction of any kind, 1365 provided that the above copyright notice and this paragraph are included 1366 on all such copies and derivative works. However, this document itself 1367 may not be modified in any way, such as by removing the copyright notice 1368 or references to the Internet Society or other Internet organizations, 1369 except as needed for the purpose of developing Internet standards in 1370 which case the procedures for copyrights defined in the Internet 1371 Standards process must be followed, or as required to translate it into 1372 languages other than English. 1374 The limited permissions granted above are perpetual and will not be 1375 revoked by the Internet Society or its successors or assigns. 1377 This document and the information contained herein is provided on an "AS 1378 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1379 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1380 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1381 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1382 FITNESS FOR A PARTICULAR PURPOSE.