idnits 2.17.1 draft-ietf-ospf-cidr-route-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 27 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** 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 123 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 131 has weird spacing: '...current ipFor...' == Line 159 has weird spacing: '...oute to a pa...' == Line 212 has weird spacing: '... entry with ...' == Line 218 has weird spacing: '...icit or other...' == Line 219 has weird spacing: '...nstance of t...' == (118 more instances...) -- 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 (March 1995) is 10635 days in the past. Is this intentional? 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: '1' is defined on line 938, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 944, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 949, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 955, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 960, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 963, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 969, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '2') ** Obsolete normative reference: RFC 1448 (ref. '3') (Obsoleted by RFC 1905) ** Obsolete normative reference: RFC 1443 (ref. '6') (Obsoleted by RFC 1903) ** Obsolete normative reference: RFC 1354 (ref. '7') (Obsoleted by RFC 2096) Summary: 17 errors (**), 0 flaws (~~), 15 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 draft IP Forwarding Table MIB March 1995 4 IP Forwarding Table MIB 6 Fri Mar 24 11:17:22 PST 1995 7 draft-ietf-ospf-cidr-route-mib-05.txt 9 Fred Baker 10 Cisco Systems 11 fred@cisco.com 13 Status of this Memo 15 This document is an Internet Draft. Internet Drafts are 16 working documents of the Internet Engineering Task Force 17 (IETF), its Areas, and its Working Groups. Note that other 18 groups may also distribute working documents as Internet 19 Drafts. 21 Internet Drafts are valid for a maximum of six months and may 22 be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet Drafts as reference 24 material or to cite them other than as a "work in progress". 26 draft IP Forwarding Table MIB March 1995 28 1. Introduction 30 This memo defines an update to RFC 1354, "IP Forwarding Table 31 MIB", for Classless Inter-Domain Routing (CIDR). That 32 document was developed by the Router Requirements Working 33 Group as an update to RFC 1213's ipRouteTable, with the 34 display of multiple routes as a primary objective. The 35 significant difference between this MIB and RFC 1354 is the 36 recognition (explicitly discussed but by consensus left to 37 future work) that CIDR routes may have the same network number 38 but different network masks. 40 draft IP Forwarding Table MIB March 1995 42 2. The SNMPv2 Network Management Framework 44 The SNMPv2 Network Management Framework consists of four major 45 components. They are: 47 o RFC 1441 which defines the SMI, the mechanisms used for 48 describing and naming objects for the purpose of 49 management. 51 o RFC 1213 defines MIB-II, the core set of managed objects 52 for the Internet suite of protocols. 54 o RFC 1445 which defines the administrative and other 55 architectural aspects of the framework. 57 o RFC 1448 which defines the protocol used for network 58 access to managed objects. 60 The Framework permits new objects to be defined for the 61 purpose of experimentation and evaluation. 63 2.1. Object Definitions 65 Managed objects are accessed via a virtual information store, 66 termed the Management Information Base or MIB. Objects in the 67 MIB are defined using the subset of Abstract Syntax Notation 68 One (ASN.1) defined in the SMI. In particular, each object 69 object type is named by an OBJECT IDENTIFIER, an 70 administratively assigned name. The object type together with 71 an object instance serves to uniquely identify a specific 72 instantiation of the object. For human convenience, we often 73 use a textual string, termed the descriptor, to refer to the 74 object type. 76 draft IP Forwarding Table MIB March 1995 78 3. Overview 80 The MIB consists of two tables and two global objects. 82 (1) The object ipForwardNumber indicates the number of 83 current routes. This is primarily to avoid having to 84 read the table in order to determine this number. 86 (2) The ipForwardTable updates the RFC 1213 ipRouteTable to 87 display multipath IP Routes. This is in turn obsoleted 88 by the ipCidrRouteTable. 90 (3) The ipCidrRouteTable updates the RFC 1213 ipRouteTable to 91 display multipath IP Routes having the same network 92 number but differing network masks. 94 draft IP Forwarding Table MIB March 1995 96 4. Definitions 98 IP-FORWARD-MIB DEFINITIONS ::= BEGIN 100 IMPORTS 101 MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Integer32, Gauge32 102 FROM SNMPv2-SMI 103 RowStatus 104 FROM SNMPv2-TC 105 ip 106 FROM RFC1213-MIB 107 MODULE-COMPLIANCE, OBJECT-GROUP 108 FROM SNMPv2-CONF; 110 ipForward MODULE-IDENTITY 111 LAST-UPDATED "9503241117Z" -- Fri Mar 24 11:17:22 PST 1995 112 ORGANIZATION "IETF OSPF Working Group" 113 CONTACT-INFO 114 " Fred Baker 115 Postal: Cisco Systems 116 519 Lado Drive 117 Santa Barbara, California 93111 119 Phone: +1 805 681 0115 120 Email: fred@cisco.com 121 " 122 DESCRIPTION 123 "The MIB module for the display of CIDR multipath IP Routes." 124 ::= { ip 24 } 126 ipForwardNumber OBJECT-TYPE 127 SYNTAX Gauge32 128 MAX-ACCESS read-only 129 STATUS obsolete 130 DESCRIPTION 131 "The number of current ipForwardTable entries 132 that are not invalid." 133 ::= { ipForward 1 } 135 -- IP Forwarding Table 137 -- The IP Forwarding Table obsoletes and replaces the ipRoute 138 -- Table current in MIB-I and MIB-II. It adds knowledge of 139 -- the autonomous system of the next hop, multiple next hop 140 -- support, and policy routing support. 142 draft IP Forwarding Table MIB March 1995 144 ipForwardTable OBJECT-TYPE 145 SYNTAX SEQUENCE OF IpForwardEntry 146 MAX-ACCESS not-accessible 147 STATUS obsolete 148 DESCRIPTION 149 "This entity's IP Routing table." 150 REFERENCE 151 "RFC 1213 Section 6.6, The IP Group" 152 ::= { ipForward 2 } 154 ipForwardEntry OBJECT-TYPE 155 SYNTAX IpForwardEntry 156 MAX-ACCESS not-accessible 157 STATUS obsolete 158 DESCRIPTION 159 "A particular route to a particular destina- 160 tion, under a particular policy." 161 INDEX { 162 ipForwardDest, 163 ipForwardProto, 164 ipForwardPolicy, 165 ipForwardNextHop 166 } 167 ::= { ipForwardTable 1 } 169 IpForwardEntry ::= 170 SEQUENCE { 171 ipForwardDest 172 IpAddress, 173 ipForwardMask 174 IpAddress, 175 ipForwardPolicy 176 Integer32, 177 ipForwardNextHop 178 IpAddress, 179 ipForwardIfIndex 180 Integer32, 181 ipForwardType 182 INTEGER, 183 ipForwardProto 184 INTEGER, 185 ipForwardAge 186 Integer32, 187 ipForwardInfo 188 OBJECT IDENTIFIER, 190 draft IP Forwarding Table MIB March 1995 192 ipForwardNextHopAS 193 Integer32, 194 ipForwardMetric1 195 Integer32, 196 ipForwardMetric2 197 Integer32, 198 ipForwardMetric3 199 Integer32, 200 ipForwardMetric4 201 Integer32, 202 ipForwardMetric5 203 Integer32 204 } 206 ipForwardDest OBJECT-TYPE 207 SYNTAX IpAddress 208 MAX-ACCESS read-only 209 STATUS obsolete 210 DESCRIPTION 211 "The destination IP address of this route. An 212 entry with a value of 0.0.0.0 is considered a 213 default route. 215 This object may not take a Multicast (Class D) 216 address value. 218 Any assignment (implicit or otherwise) of an 219 instance of this object to a value x must be 220 rejected if the bitwise logical-AND of x with 221 the value of the corresponding instance of the 222 ipForwardMask object is not equal to x." 223 ::= { ipForwardEntry 1 } 225 ipForwardMask OBJECT-TYPE 226 SYNTAX IpAddress 227 MAX-ACCESS read-create 228 STATUS obsolete 229 DESCRIPTION 230 "Indicate the mask to be logical-ANDed with the 231 destination address before being compared to 232 the value in the ipForwardDest field. For 233 those systems that do not support arbitrary 234 subnet masks, an agent constructs the value of 235 the ipForwardMask by reference to the IP Ad- 236 dress Class. 238 draft IP Forwarding Table MIB March 1995 240 Any assignment (implicit or otherwise) of an 241 instance of this object to a value x must be 242 rejected if the bitwise logical-AND of x with 243 the value of the corresponding instance of the 244 ipForwardDest object is not equal to ipForward- 245 Dest." 246 DEFVAL { '00000000'h } -- 0.0.0.0 247 ::= { ipForwardEntry 2 } 249 -- The following convention is included for specification 250 -- of TOS Field contents. At this time, the Host Requirements 251 -- and the Router Requirements documents disagree on the width 252 -- of the TOS field. This mapping describes the Router 253 -- Requirements mapping, and leaves room to widen the TOS field 254 -- without impact to fielded systems. 256 ipForwardPolicy OBJECT-TYPE 257 SYNTAX Integer32 258 MAX-ACCESS read-only 259 STATUS obsolete 260 DESCRIPTION 261 "The general set of conditions that would cause 262 the selection of one multipath route (set of 263 next hops for a given destination) is referred 264 to as 'policy'. 266 Unless the mechanism indicated by ipForwardPro- 267 to specifies otherwise, the policy specifier is 268 the IP TOS Field. The encoding of IP TOS is as 269 specified by the following convention. Zero 270 indicates the default path if no more specific 271 policy applies. 273 +-----+-----+-----+-----+-----+-----+-----+-----+ 274 | | | | 275 | PRECEDENCE | TYPE OF SERVICE | 0 | 276 | | | | 277 +-----+-----+-----+-----+-----+-----+-----+-----+ 279 IP TOS IP TOS 280 Field Policy Field Policy 281 Contents Code Contents Code 282 0 0 0 0 ==> 0 0 0 0 1 ==> 2 283 0 0 1 0 ==> 4 0 0 1 1 ==> 6 284 0 1 0 0 ==> 8 0 1 0 1 ==> 10 286 draft IP Forwarding Table MIB March 1995 288 0 1 1 0 ==> 12 0 1 1 1 ==> 14 289 1 0 0 0 ==> 16 1 0 0 1 ==> 18 290 1 0 1 0 ==> 20 1 0 1 1 ==> 22 291 1 1 0 0 ==> 24 1 1 0 1 ==> 26 292 1 1 1 0 ==> 28 1 1 1 1 ==> 30 294 Protocols defining 'policy' otherwise must ei- 295 ther define a set of values which are valid for 296 this object or must implement an integer- 297 instanced policy table for which this object's 298 value acts as an index." 299 ::= { ipForwardEntry 3 } 301 ipForwardNextHop OBJECT-TYPE 302 SYNTAX IpAddress 303 MAX-ACCESS read-only 304 STATUS obsolete 305 DESCRIPTION 306 "On remote routes, the address of the next sys- 307 tem en route; Otherwise, 0.0.0.0." 308 ::= { ipForwardEntry 4 } 310 ipForwardIfIndex OBJECT-TYPE 311 SYNTAX Integer32 312 MAX-ACCESS read-create 313 STATUS obsolete 314 DESCRIPTION 315 "The ifIndex value which identifies the local 316 interface through which the next hop of this 317 route should be reached." 318 DEFVAL { 0 } 319 ::= { ipForwardEntry 5 } 321 ipForwardType OBJECT-TYPE 322 SYNTAX INTEGER { 323 other (1), -- not specified by this MIB 324 invalid (2), -- logically deleted 325 local (3), -- local interface 326 remote (4) -- remote destination 327 } 328 MAX-ACCESS read-create 329 STATUS obsolete 330 DESCRIPTION 331 "The type of route. Note that local(3) refers 332 to a route for which the next hop is the final 334 draft IP Forwarding Table MIB March 1995 336 destination; remote(4) refers to a route for 337 which the next hop is not the final destina- 338 tion. 340 Setting this object to the value invalid(2) has 341 the effect of invalidating the corresponding 342 entry in the ipForwardTable object. That is, 343 it effectively disassociates the destination 344 identified with said entry from the route iden- 345 tified with said entry. It is an 346 implementation-specific matter as to whether 347 the agent removes an invalidated entry from the 348 table. Accordingly, management stations must 349 be prepared to receive tabular information from 350 agents that corresponds to entries not current- 351 ly in use. Proper interpretation of such en- 352 tries requires examination of the relevant ip- 353 ForwardType object." 354 DEFVAL { invalid } 355 ::= { ipForwardEntry 6 } 357 ipForwardProto OBJECT-TYPE 358 SYNTAX INTEGER { 359 other (1), -- not specified 360 local (2), -- local interface 361 netmgmt (3), -- static route 362 icmp (4), -- result of ICMP Redirect 364 -- the following are all dynamic 365 -- routing protocols 366 egp (5), -- Exterior Gateway Protocol 367 ggp (6), -- Gateway-Gateway Protocol 368 hello (7), -- FuzzBall HelloSpeak 369 rip (8), -- Berkeley RIP or RIP-II 370 is_is (9), -- Dual IS-IS 371 es_is (10), -- ISO 9542 372 ciscoIgrp (11), -- Cisco IGRP 373 bbnSpfIgp (12), -- BBN SPF IGP 374 ospf (13), -- Open Shortest Path First 375 bgp (14), -- Border Gateway Protocol 376 idpr (15) -- InterDomain Policy Routing 377 } 378 MAX-ACCESS read-only 379 STATUS obsolete 380 DESCRIPTION 382 draft IP Forwarding Table MIB March 1995 384 "The routing mechanism via which this route was 385 learned. Inclusion of values for gateway rout- 386 ing protocols is not intended to imply that 387 hosts should support those protocols." 388 ::= { ipForwardEntry 7 } 390 ipForwardAge OBJECT-TYPE 391 SYNTAX Integer32 392 MAX-ACCESS read-only 393 STATUS obsolete 394 DESCRIPTION 395 "The number of seconds since this route was 396 last updated or otherwise determined to be 397 correct. Note that no semantics of `too old' 398 can be implied except through knowledge of the 399 routing protocol by which the route was 400 learned." 401 DEFVAL { 0 } 402 ::= { ipForwardEntry 8 } 404 ipForwardInfo OBJECT-TYPE 405 SYNTAX OBJECT IDENTIFIER 406 MAX-ACCESS read-create 407 STATUS obsolete 408 DESCRIPTION 409 "A reference to MIB definitions specific to the 410 particular routing protocol which is responsi- 411 ble for this route, as determined by the value 412 specified in the route's ipForwardProto value. 413 If this information is not present, its value 414 should be set to the OBJECT IDENTIFIER { 0 0 }, 415 which is a syntactically valid object identif- 416 ier, and any implementation conforming to ASN.1 417 and the Basic Encoding Rules must be able to 418 generate and recognize this value." 419 ::= { ipForwardEntry 9 } 421 ipForwardNextHopAS OBJECT-TYPE 422 SYNTAX Integer32 423 MAX-ACCESS read-create 424 STATUS obsolete 425 DESCRIPTION 426 "The Autonomous System Number of the Next Hop. 427 When this is unknown or not relevant to the 428 protocol indicated by ipForwardProto, zero." 430 draft IP Forwarding Table MIB March 1995 432 DEFVAL { 0 } 433 ::= { ipForwardEntry 10 } 435 ipForwardMetric1 OBJECT-TYPE 436 SYNTAX Integer32 437 MAX-ACCESS read-create 438 STATUS obsolete 439 DESCRIPTION 440 "The primary routing metric for this route. 441 The semantics of this metric are determined by 442 the routing-protocol specified in the route's 443 ipForwardProto value. If this metric is not 444 used, its value should be set to -1." 445 DEFVAL { -1 } 446 ::= { ipForwardEntry 11 } 448 ipForwardMetric2 OBJECT-TYPE 449 SYNTAX Integer32 450 MAX-ACCESS read-create 451 STATUS obsolete 452 DESCRIPTION 453 "An alternate routing metric for this route. 454 The semantics of this metric are determined by 455 the routing-protocol specified in the route's 456 ipForwardProto value. If this metric is not 457 used, its value should be set to -1." 458 DEFVAL { -1 } 459 ::= { ipForwardEntry 12 } 461 ipForwardMetric3 OBJECT-TYPE 462 SYNTAX Integer32 463 MAX-ACCESS read-create 464 STATUS obsolete 465 DESCRIPTION 466 "An alternate routing metric for this route. 467 The semantics of this metric are determined by 468 the routing-protocol specified in the route's 469 ipForwardProto value. If this metric is not 470 used, its value should be set to -1." 471 DEFVAL { -1 } 472 ::= { ipForwardEntry 13 } 474 ipForwardMetric4 OBJECT-TYPE 475 SYNTAX Integer32 476 MAX-ACCESS read-create 478 draft IP Forwarding Table MIB March 1995 480 STATUS obsolete 481 DESCRIPTION 482 "An alternate routing metric for this route. 483 The semantics of this metric are determined by 484 the routing-protocol specified in the route's 485 ipForwardProto value. If this metric is not 486 used, its value should be set to -1." 487 DEFVAL { -1 } 488 ::= { ipForwardEntry 14 } 490 ipForwardMetric5 OBJECT-TYPE 491 SYNTAX Integer32 492 MAX-ACCESS read-create 493 STATUS obsolete 494 DESCRIPTION 495 "An alternate routing metric for this route. 496 The semantics of this metric are determined by 497 the routing-protocol specified in the route's 498 ipForwardProto value. If this metric is not 499 used, its value should be set to -1." 500 DEFVAL { -1 } 501 ::= { ipForwardEntry 15 } 503 draft IP Forwarding Table MIB March 1995 505 ipCidrRouteNumber OBJECT-TYPE 506 SYNTAX Gauge32 507 MAX-ACCESS read-only 508 STATUS current 509 DESCRIPTION 510 "The number of current ipCidrRouteTable entries 511 that are not invalid." 512 ::= { ipForward 3 } 514 -- IP CIDR Route Table 516 -- The IP CIDR Route Table obsoletes and replaces the ipRoute 517 -- Table current in MIB-I and MIB-II and the IP Forwarding Table. 518 -- It adds knowledge of the autonomous system of the next hop, 519 -- multiple next hops, and policy routing, and Classless 520 -- Inter-Domain Routing. 522 ipCidrRouteTable OBJECT-TYPE 523 SYNTAX SEQUENCE OF IpCidrRouteEntry 524 MAX-ACCESS not-accessible 525 STATUS current 526 DESCRIPTION 527 "This entity's IP Routing table." 528 REFERENCE 529 "RFC 1213 Section 6.6, The IP Group" 530 ::= { ipForward 4 } 532 ipCidrRouteEntry OBJECT-TYPE 533 SYNTAX IpCidrRouteEntry 534 MAX-ACCESS not-accessible 535 STATUS current 536 DESCRIPTION 537 "A particular route to a particular destina- 538 tion, under a particular policy." 539 INDEX { 540 ipCidrRouteDest, 541 ipCidrRouteMask, 542 ipCidrRouteTos, 543 ipCidrRouteNextHop 544 } 545 ::= { ipCidrRouteTable 1 } 547 IpCidrRouteEntry ::= 548 SEQUENCE { 549 ipCidrRouteDest 551 draft IP Forwarding Table MIB March 1995 553 IpAddress, 554 ipCidrRouteMask 555 IpAddress, 556 ipCidrRouteTos 557 Integer32, 558 ipCidrRouteNextHop 559 IpAddress, 560 ipCidrRouteIfIndex 561 Integer32, 562 ipCidrRouteType 563 INTEGER, 564 ipCidrRouteProto 565 INTEGER, 566 ipCidrRouteAge 567 Integer32, 568 ipCidrRouteInfo 569 OBJECT IDENTIFIER, 570 ipCidrRouteNextHopAS 571 Integer32, 572 ipCidrRouteMetric1 573 Integer32, 574 ipCidrRouteMetric2 575 Integer32, 576 ipCidrRouteMetric3 577 Integer32, 578 ipCidrRouteMetric4 579 Integer32, 580 ipCidrRouteMetric5 581 Integer32, 582 ipCidrRouteStatus 583 RowStatus 584 } 586 ipCidrRouteDest OBJECT-TYPE 587 SYNTAX IpAddress 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "The destination IP address of this route. 593 This object may not take a Multicast (Class D) 594 address value. 596 Any assignment (implicit or otherwise) of an 597 instance of this object to a value x must be 599 draft IP Forwarding Table MIB March 1995 601 rejected if the bitwise logical-AND of x with 602 the value of the corresponding instance of the 603 ipCidrRouteMask object is not equal to x." 604 ::= { ipCidrRouteEntry 1 } 606 ipCidrRouteMask OBJECT-TYPE 607 SYNTAX IpAddress 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "Indicate the mask to be logical-ANDed with the 612 destination address before being compared to 613 the value in the ipCidrRouteDest field. For 614 those systems that do not support arbitrary 615 subnet masks, an agent constructs the value of 616 the ipCidrRouteMask by reference to the IP Ad- 617 dress Class. 619 Any assignment (implicit or otherwise) of an 620 instance of this object to a value x must be 621 rejected if the bitwise logical-AND of x with 622 the value of the corresponding instance of the 623 ipCidrRouteDest object is not equal to ipCidrRoute- 624 Dest." 625 ::= { ipCidrRouteEntry 2 } 627 -- The following convention is included for specification 628 -- of TOS Field contents. At this time, the Host Requirements 629 -- and the Router Requirements documents disagree on the width 630 -- of the TOS field. This mapping describes the Router 631 -- Requirements mapping, and leaves room to widen the TOS field 632 -- without impact to fielded systems. 634 ipCidrRouteTos OBJECT-TYPE 635 SYNTAX Integer32 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The policy specifier is the IP TOS Field. The encoding 640 of IP TOS is as specified by the following convention. 641 Zero indicates the default path if no more specific 642 policy applies. 644 +-----+-----+-----+-----+-----+-----+-----+-----+ 645 | | | | 647 draft IP Forwarding Table MIB March 1995 649 | PRECEDENCE | TYPE OF SERVICE | 0 | 650 | | | | 651 +-----+-----+-----+-----+-----+-----+-----+-----+ 653 IP TOS IP TOS 654 Field Policy Field Policy 655 Contents Code Contents Code 656 0 0 0 0 ==> 0 0 0 0 1 ==> 2 657 0 0 1 0 ==> 4 0 0 1 1 ==> 6 658 0 1 0 0 ==> 8 0 1 0 1 ==> 10 659 0 1 1 0 ==> 12 0 1 1 1 ==> 14 660 1 0 0 0 ==> 16 1 0 0 1 ==> 18 661 1 0 1 0 ==> 20 1 0 1 1 ==> 22 662 1 1 0 0 ==> 24 1 1 0 1 ==> 26 663 1 1 1 0 ==> 28 1 1 1 1 ==> 30" 664 ::= { ipCidrRouteEntry 3 } 666 ipCidrRouteNextHop OBJECT-TYPE 667 SYNTAX IpAddress 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "On remote routes, the address of the next sys- 672 tem en route; Otherwise, 0.0.0.0." 673 ::= { ipCidrRouteEntry 4 } 675 ipCidrRouteIfIndex OBJECT-TYPE 676 SYNTAX Integer32 677 MAX-ACCESS read-create 678 STATUS current 679 DESCRIPTION 680 "The ifIndex value which identifies the local 681 interface through which the next hop of this 682 route should be reached." 683 DEFVAL { 0 } 684 ::= { ipCidrRouteEntry 5 } 686 ipCidrRouteType OBJECT-TYPE 687 SYNTAX INTEGER { 688 other (1), -- not specified by this MIB 689 reject (2), -- route which discards traffic 690 local (3), -- local interface 691 remote (4) -- remote destination 692 } 693 MAX-ACCESS read-create 695 draft IP Forwarding Table MIB March 1995 697 STATUS current 698 DESCRIPTION 699 "The type of route. Note that local(3) refers 700 to a route for which the next hop is the final 701 destination; remote(4) refers to a route for 702 which the next hop is not the final destina- 703 tion. 705 Routes which do not result in traffic forwarding or 706 rejection should not be displayed even if the 707 implementation keeps them stored internally. 709 reject (2) refers to a route which, if matched, discards 710 the message as unreachable. This is used in some 711 protocols as a means of correctly aggregating routes." 712 ::= { ipCidrRouteEntry 6 } 714 ipCidrRouteProto OBJECT-TYPE 715 SYNTAX INTEGER { 716 other (1), -- not specified 717 local (2), -- local interface 718 netmgmt (3), -- static route 719 icmp (4), -- result of ICMP Redirect 721 -- the following are all dynamic 722 -- routing protocols 723 egp (5), -- Exterior Gateway Protocol 724 ggp (6), -- Gateway-Gateway Protocol 725 hello (7), -- FuzzBall HelloSpeak 726 rip (8), -- Berkeley RIP or RIP-II 727 is_is (9), -- Dual IS-IS 728 es_is (10), -- ISO 9542 729 ciscoIgrp (11), -- Cisco IGRP 730 bbnSpfIgp (12), -- BBN SPF IGP 731 ospf (13), -- Open Shortest Path First 732 bgp (14), -- Border Gateway Protocol 733 idpr (15) -- InterDomain Policy Routing 734 } 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "The routing mechanism via which this route was 739 learned. Inclusion of values for gateway rout- 740 ing protocols is not intended to imply that 741 hosts should support those protocols." 743 draft IP Forwarding Table MIB March 1995 745 ::= { ipCidrRouteEntry 7 } 747 ipCidrRouteAge OBJECT-TYPE 748 SYNTAX Integer32 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The number of seconds since this route was 753 last updated or otherwise determined to be 754 correct. Note that no semantics of `too old' 755 can be implied except through knowledge of the 756 routing protocol by which the route was 757 learned." 758 DEFVAL { 0 } 759 ::= { ipCidrRouteEntry 8 } 761 ipCidrRouteInfo OBJECT-TYPE 762 SYNTAX OBJECT IDENTIFIER 763 MAX-ACCESS read-create 764 STATUS current 765 DESCRIPTION 766 "A reference to MIB definitions specific to the 767 particular routing protocol which is responsi- 768 ble for this route, as determined by the value 769 specified in the route's ipCidrRouteProto value. 770 If this information is not present, its value 771 should be set to the OBJECT IDENTIFIER { 0 0 }, 772 which is a syntactically valid object identif- 773 ier, and any implementation conforming to ASN.1 774 and the Basic Encoding Rules must be able to 775 generate and recognize this value." 776 ::= { ipCidrRouteEntry 9 } 778 ipCidrRouteNextHopAS OBJECT-TYPE 779 SYNTAX Integer32 780 MAX-ACCESS read-create 781 STATUS current 782 DESCRIPTION 783 "The Autonomous System Number of the Next Hop. 784 When this is unknown or not relevant to the 785 protocol indicated by ipCidrRouteProto, zero." 786 DEFVAL { 0 } 787 ::= { ipCidrRouteEntry 10 } 789 ipCidrRouteMetric1 OBJECT-TYPE 791 draft IP Forwarding Table MIB March 1995 793 SYNTAX Integer32 794 MAX-ACCESS read-create 795 STATUS current 796 DESCRIPTION 797 "The primary routing metric for this route. 798 The semantics of this metric are determined by 799 the routing-protocol specified in the route's 800 ipCidrRouteProto value. If this metric is not 801 used, its value should be set to -1." 802 DEFVAL { -1 } 803 ::= { ipCidrRouteEntry 11 } 805 ipCidrRouteMetric2 OBJECT-TYPE 806 SYNTAX Integer32 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "An alternate routing metric for this route. 811 The semantics of this metric are determined by 812 the routing-protocol specified in the route's 813 ipCidrRouteProto value. If this metric is not 814 used, its value should be set to -1." 815 DEFVAL { -1 } 816 ::= { ipCidrRouteEntry 12 } 818 ipCidrRouteMetric3 OBJECT-TYPE 819 SYNTAX Integer32 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "An alternate routing metric for this route. 824 The semantics of this metric are determined by 825 the routing-protocol specified in the route's 826 ipCidrRouteProto value. If this metric is not 827 used, its value should be set to -1." 828 DEFVAL { -1 } 829 ::= { ipCidrRouteEntry 13 } 831 ipCidrRouteMetric4 OBJECT-TYPE 832 SYNTAX Integer32 833 MAX-ACCESS read-create 834 STATUS current 835 DESCRIPTION 836 "An alternate routing metric for this route. 837 The semantics of this metric are determined by 839 draft IP Forwarding Table MIB March 1995 841 the routing-protocol specified in the route's 842 ipCidrRouteProto value. If this metric is not 843 used, its value should be set to -1." 844 DEFVAL { -1 } 845 ::= { ipCidrRouteEntry 14 } 847 ipCidrRouteMetric5 OBJECT-TYPE 848 SYNTAX Integer32 849 MAX-ACCESS read-create 850 STATUS current 851 DESCRIPTION 852 "An alternate routing metric for this route. 853 The semantics of this metric are determined by 854 the routing-protocol specified in the route's 855 ipCidrRouteProto value. If this metric is not 856 used, its value should be set to -1." 857 DEFVAL { -1 } 858 ::= { ipCidrRouteEntry 15 } 860 ipCidrRouteStatus OBJECT-TYPE 861 SYNTAX RowStatus 862 MAX-ACCESS read-create 863 STATUS current 864 DESCRIPTION 865 "The row status variable, used according to 866 row installation and removal conventions." 867 ::= { ipCidrRouteEntry 16 } 869 draft IP Forwarding Table MIB March 1995 871 -- conformance information 873 ipForwardConformance OBJECT IDENTIFIER ::= { ipForward 5 } 875 ipForwardGroups OBJECT IDENTIFIER ::= { ipForwardConformance 1 } 876 ipForwardCompliances OBJECT IDENTIFIER ::= { ipForwardConformance 2 } 878 -- compliance statements 880 ipForwardCompliance MODULE-COMPLIANCE 881 STATUS current 882 DESCRIPTION 883 "The compliance statement for SNMPv2 entities 884 which implement the ipForward MIB." 886 MODULE -- this module 887 MANDATORY-GROUPS { ipForwardCidrRouteGroup } 889 ::= { ipForwardCompliances 1 } 891 draft IP Forwarding Table MIB March 1995 893 -- units of conformance 895 ipForwardMultiPathGroup OBJECT-GROUP 896 OBJECTS { ipForwardNumber, 897 ipForwardDest, ipForwardMask, ipForwardPolicy, 898 ipForwardNextHop, ipForwardIfIndex, ipForwardType, 899 ipForwardProto, ipForwardAge, ipForwardInfo, 900 ipForwardNextHopAS, 901 ipForwardMetric1, ipForwardMetric2, ipForwardMetric3, 902 ipForwardMetric4, ipForwardMetric5 903 } 904 STATUS obsolete 905 DESCRIPTION 906 "IP Multipath Route Table." 907 ::= { ipForwardGroups 2 } 909 ipForwardCidrRouteGroup OBJECT-GROUP 910 OBJECTS { ipCidrRouteNumber, 911 ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, 912 ipCidrRouteNextHop, ipCidrRouteIfIndex, ipCidrRouteType, 913 ipCidrRouteProto, ipCidrRouteAge, ipCidrRouteInfo, 914 ipCidrRouteNextHopAS, ipCidrRouteMetric1, 915 ipCidrRouteMetric2, ipCidrRouteMetric3, 916 ipCidrRouteMetric4, ipCidrRouteMetric5, ipCidrRouteStatus 917 } 918 STATUS current 919 DESCRIPTION 920 "The CIDR Route Table." 921 ::= { ipForwardGroups 3 } 923 END 925 draft IP Forwarding Table MIB March 1995 927 5. Acknowledgements 929 This work was originally performed by the Router Requirements 930 Working Group at the request of the OSPF Working Group. This 931 update was performed under the auspices of the OSPF Working 932 Group. John Moy of Proteon Incorporated is the chair. 934 draft IP Forwarding Table MIB March 1995 936 6. References 938 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 939 "Structure of Management Information for version 2 of the 940 Simple Network Management Protocol (SNMPv2)", RFC 1442, 941 SNMP Research, Inc., Hughes LAN Systems, Dover Beach 942 Consulting, Inc., Carnegie Mellon University, April 1993. 944 [2] Galvin, J., and K. McCloghrie, "Administrative Model for 945 version 2 of the Simple Network Management Protocol 946 (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes 947 LAN Systems, April 1993. 949 [3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 950 "Protocol Operations for version 2 of the Simple Network 951 Management Protocol (SNMPv2)", RFC 1448, SNMP Research, 952 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., 953 Carnegie Mellon University, April 1993. 955 [4] McCloghrie, K., and M. Rose, "Management Information Base 956 for Network Management of TCP/IP-based internets - MIB- 957 II", STD 17, RFC 1213, Hughes LAN Systems, Performance 958 Systems International, March 1991. 960 [5] Postel, J., "Internet Protocol", STD 5, RFC 791, 961 USC/Information Sciences Institute, September 1981. 963 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 964 "Textual Conventions for version 2 of the Simple Network 965 Management Protocol (SNMPv2)", RFC 1443, SNMP Research, 966 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., 967 Carnegie Mellon University, April 1993. 969 [7] Fred Baker, "IP Forwarding Table MIB", Request for 970 Comments 1354, (July 1992). 972 draft IP Forwarding Table MIB March 1995 974 7. Security Considerations 976 Security is an objective not in this MIB view. 978 8. Author's Address 980 Fred Baker 981 Cisco Systems 982 519 Lado Drive 983 Santa Barbara, California 93111 985 Phone: +1 805 681 0115 986 Email: fred@cisco.com 988 draft IP Forwarding Table MIB March 1995 990 Table of Contents 992 1 Introduction .......................................... 2 993 2 The SNMPv2 Network Management Framework ............... 3 994 2.1 Object Definitions .................................. 3 995 3 Overview .............................................. 4 996 4 Definitions ........................................... 5 997 5 Acknowledgements ...................................... 24 998 6 References ............................................ 25 999 7 Security Considerations ............................... 26 1000 8 Author's Address ...................................... 26