idnits 2.17.1 draft-ietf-idr-bgp4-mib-08.txt: ** The Abstract section seems to be numbered 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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 63 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction 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.) ** There are 94 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 2 instances of too long lines in the document, the longest one being 4 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 == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 25 has weird spacing: '... This docum...' == Line 29 has weird spacing: '...), its areas...' == Line 30 has weird spacing: '...ups may also ...' == Line 34 has weird spacing: '...ents at any...' == Line 35 has weird spacing: '...e. It is i...' == (89 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 (November 2001) is 8192 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) -- Missing reference section? 'BGP' on line 72 looks like a reference -- Missing reference section? 'BGPAPPL' on line 72 looks like a reference -- Missing reference section? 'RFC2571' on line 1260 looks like a reference -- Missing reference section? 'RFC1155' on line 1264 looks like a reference -- Missing reference section? 'RFC1212' on line 1268 looks like a reference -- Missing reference section? 'RFC1215' on line 1271 looks like a reference -- Missing reference section? 'RFC2578' on line 1274 looks like a reference -- Missing reference section? 'RFC2579' on line 1279 looks like a reference -- Missing reference section? 'RFC2580' on line 1283 looks like a reference -- Missing reference section? 'RFC1157' on line 1287 looks like a reference -- Missing reference section? 'RFC1901' on line 1290 looks like a reference -- Missing reference section? 'RFC1906' on line 1294 looks like a reference -- Missing reference section? 'RFC2572' on line 1298 looks like a reference -- Missing reference section? 'RFC2574' on line 1302 looks like a reference -- Missing reference section? 'RFC1905' on line 1306 looks like a reference -- Missing reference section? 'RFC2573' on line 1310 looks like a reference -- Missing reference section? 'RFC2575' on line 1313 looks like a reference -- Missing reference section? 'RFC2570' on line 1317 looks like a reference -- Missing reference section? 'BGP4' on line 1254 looks like a reference -- Missing reference section? 'BGP4APP' on line 1257 looks like a reference -- Missing reference section? '14' on line 1359 looks like a reference -- Missing reference section? '17' on line 1360 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 10 warnings (==), 24 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT BGP4-MIB November 2001 4 Network Working Group Editors of this version: 5 INTERNET DRAFT J. Haas 6 NextHop 7 S. Hares 8 NextHop 9 Authors of previous version: 10 S. Willis 11 Argon Networks 12 J. Burruss 13 WinData 14 Editor of previous version: 15 J. Chu 16 Cosine 17 November 2001 19 Definitions of Managed Objects 20 for the Fourth Version of Border Gateway Protocol (BGP-4) 21 23 1. Status of this Memo 25 This document is an Internet-Draft and is in full conformance with 26 all provisions of Section 10 of RFC 2026. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF), its areas, and its working groups. Note that 30 other groups may also distribute working documents as Internet- 31 Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet- Drafts as reference 36 material or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts. 41 The list of Internet-Draft Shadow Directories can be accessed at 42 http://www.ietf.org/shadow.html. 44 2. Copyright Notice 46 Copyright (C) The Internet Society (1999). All Rights Reserved. 48 3. Abstract 50 This memo is an extension to the SNMP MIB. The origin of this memo 51 is from RFC 1269 "Definitions of Managed Objects for the Border 52 Gateway Protocol (Version 3)", which was updated to support BGP-4 in 53 RFC 1657. This memo fixes errors introduced when the MIB was 54 converted to use the SNMPv2 SMI, as well as updates references to the 55 current SNMP framework documents. 57 This memo is intended to document deployed implementations of this 58 MIB in a historical context, provide clarifications of some items and 59 also note errors where the MIB fails to fully represent the BGP 60 protocol. Work is currently in progress to replace this MIB with a 61 new one representing the current state of the BGP protocol and its 62 extensions. 64 Distribution of this memo is unlimited. Please forward comments to 65 idr@merit.net. 67 4. Introduction 69 This memo defines a portion of the Management Information Base (MIB) 70 for use with network management protocols in the Internet community. 71 In particular, it describes managed objects used for managing the 72 Border Gateway Protocol Version 4 or lower [BGP, BGPAPPL]. 74 5. The SNMP Management Framework 76 The SNMP Management Framework presently consists of five major 77 components: 79 -- An overall architecture, described in RFC 2571 [RFC2571]. 81 -- Mechanisms for describing and naming objects and events for the 82 purpose of management. The first version of this Structure of 83 Management Information (SMI) is called SMIv1 and described in 84 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 85 1215 [RFC1215]. The second version, called SMIv2, is described 86 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 87 STD 58, RFC 2580 [RFC2580]. 89 -- Message protocols for transferring management information. The 90 first version of the SNMP message protocol is called SNMPv1 and 91 described in STD 15, RFC 1157 [RFC1157]. A second version of 92 the SNMP message protocol, which is not an Internet standards 93 track protocol, is called SNMPv2c and described in RFC 1901 94 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 95 message protocol is called SNMPv3 and described in RFC 1906 96 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 98 -- Protocol operations for accessing management information. The 99 first set of protocol operations and associated PDU formats is 100 described in STD 15, RFC 1157 [RFC1157]. A second set of 101 protocol operations and associated PDU formats is described in 102 RFC 1905 [RFC1905]. 104 -- A set of fundamental applications described in RFC 2573 105 [RFC2573] and the view-based access control mechanism described 106 in RFC 2575 [RFC2575]. 108 A more detailed introduction to the current SNMP Management Framework 109 can be found in RFC 2570 [RFC2570]. 111 Managed objects are accessed via a virtual information store, termed 112 the Management Information Base or MIB. Objects in the MIB are 113 defined using the mechanisms defined in the SMI. 115 This memo specifies a MIB module that is compliant to the SMIv2. A 116 MIB conforming to the SMIv1 can be produced through the appropriate 117 translations. The resulting translated MIB must be semantically 118 equivalent, except where objects or events are omitted because no 119 translation is possible (use of Counter64). Some machine readable 120 information in SMIv2 will be converted into textual descriptions in 121 SMIv1 during the translation process. However, this loss of machine 122 readable information is not considered to change the semantics of the 123 MIB. 125 6. Overview 127 These objects are used to control and manage a BGP-4 implementation. 129 Apart from a few system-wide scalar objects, this MIB is broken into 130 three tables: the BGP Peer Table, the BGP Received Path Attribute 131 Table, and the BGP-4 Received Path Attribute Table. The BGP Peer 132 Table contains information about state and current activity of 133 connections with the BGP peers. The Received Path Attribute Table 134 contains path attributes received from all peers running BGP version 135 3 or less. The BGP-4 Received Path Attribute Table contains path 136 attributes received from all BGP-4 peers. The actual attributes used 137 in determining a route are a subset of the received attribute tables 138 after local routing policy has been applied. 140 7. Definitions 142 BGP4-MIB DEFINITIONS ::= BEGIN 144 IMPORTS 145 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 146 IpAddress, Integer32, Counter32, Gauge32, mib-2 147 FROM SNMPv2-SMI 148 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 149 FROM SNMPv2-CONF; 151 bgp MODULE-IDENTITY 152 LAST-UPDATED "200111030000Z" 153 ORGANIZATION "IETF IDR Working Group" 154 CONTACT-INFO "E-mail: idr@merit.net 156 Jeff Haas, Sue Hares (Editor) 157 517 W. William Street 158 Ann Arbor, MI 48103-4943 159 Tel: +1 734 973-2200 160 Fax: +1 734 615-3241 161 E-mail: jhaas@nexthop.com 162 skh@nexthop.com" 164 DESCRIPTION 165 "The MIB module for the BGP-4 protocol. 167 Changes since RFC 1657: 169 1) Fixed the definitions of the traps to 170 make them equivalent to their initial 171 definition in RFC 1269. 172 2) Added compliance and conformance info. 173 3) Updated for latest BGP information 174 draft-ietf-idr-bgp4-15.txt for value of 175 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, 176 bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc, 177 bgp4PathAttrASPathSegement. 178 4) Added additional clarification commments where 179 needed. 180 5) Noted where objects do not fully reflect 181 the protocol as Known Issues." 182 ::= { mib-2 15 } 184 bgpVersion OBJECT-TYPE 185 SYNTAX OCTET STRING (SIZE (1..255)) 186 MAX-ACCESS read-only 187 STATUS current 188 DESCRIPTION 189 "Vector of supported BGP protocol version 190 numbers. Each peer negotiates the version 191 from this vector. Versions are identified 192 via the string of bits contained within this 193 object. The first octet contains bits 0 to 194 7, the second octet contains bits 8 to 15, 195 and so on, with the most significant bit 196 referring to the lowest bit number in the 197 octet (e.g., the MSB of the first octet 198 refers to bit 0). If a bit, i, is present 199 and set, then the version (i+1) of the BGP 200 is supported." 201 ::= { bgp 1 } 203 bgpLocalAs OBJECT-TYPE 204 SYNTAX Integer32 (0..65535) 205 MAX-ACCESS read-only 206 STATUS current 207 DESCRIPTION 208 "The local autonomous system number." 209 ::= { bgp 2 } 211 -- BGP Peer table. This table contains, one entry per 212 -- BGP peer, information about the BGP peer. 214 bgpPeerTable OBJECT-TYPE 215 SYNTAX SEQUENCE OF BgpPeerEntry 216 MAX-ACCESS not-accessible 217 STATUS current 218 DESCRIPTION 219 "BGP peer table. This table contains, 220 one entry per BGP peer, information about the 221 connections with BGP peers." 222 ::= { bgp 3 } 224 bgpPeerEntry OBJECT-TYPE 225 SYNTAX BgpPeerEntry 226 MAX-ACCESS not-accessible 227 STATUS current 228 DESCRIPTION 229 "Entry containing information about the 230 connection with a BGP peer." 231 INDEX { bgpPeerRemoteAddr } 232 ::= { bgpPeerTable 1 } 234 BgpPeerEntry ::= SEQUENCE { 235 bgpPeerIdentifier 236 IpAddress, 237 bgpPeerState 238 INTEGER, 239 bgpPeerAdminStatus 240 INTEGER, 241 bgpPeerNegotiatedVersion 242 Integer32, 243 bgpPeerLocalAddr 244 IpAddress, 245 bgpPeerLocalPort 246 Integer32, 247 bgpPeerRemoteAddr 248 IpAddress, 249 bgpPeerRemotePort 250 Integer32, 251 bgpPeerRemoteAs 252 Integer32, 253 bgpPeerInUpdates 254 Counter32, 255 bgpPeerOutUpdates 256 Counter32, 257 bgpPeerInTotalMessages 258 Counter32, 259 bgpPeerOutTotalMessages 260 Counter32, 261 bgpPeerLastError 262 OCTET STRING, 263 bgpPeerFsmEstablishedTransitions 264 Counter32, 265 bgpPeerFsmEstablishedTime 266 Gauge32, 267 bgpPeerConnectRetryInterval 268 Integer32, 269 bgpPeerHoldTime 270 Integer32, 271 bgpPeerKeepAlive 272 Integer32, 274 bgpPeerHoldTimeConfigured 275 Integer32, 276 bgpPeerKeepAliveConfigured 277 Integer32, 278 bgpPeerMinASOriginationInterval 279 Integer32, 280 bgpPeerMinRouteAdvertisementInterval 281 Integer32, 282 bgpPeerInUpdateElapsedTime 283 Gauge32 284 } 286 bgpPeerIdentifier OBJECT-TYPE 287 SYNTAX IpAddress 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "The BGP Identifier of this entry's BGP peer. 292 This entry should be 0.0.0.0 unless the 293 bgpPeerState is in the openconfirm or the 294 established state." 295 ::= { bgpPeerEntry 1 } 297 bgpPeerState OBJECT-TYPE 298 SYNTAX INTEGER { 299 idle(1), 300 connect(2), 301 active(3), 302 opensent(4), 303 openconfirm(5), 304 established(6) 305 } 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The BGP peer connection state." 310 ::= { bgpPeerEntry 2 } 312 bgpPeerAdminStatus OBJECT-TYPE 313 SYNTAX INTEGER { 314 stop(1), 315 start(2) 316 } 317 MAX-ACCESS read-write 318 STATUS current 319 DESCRIPTION 320 "The desired state of the BGP connection. 321 A transition from 'stop' to 'start' will 322 cause the BGP Start Event to be generated. 323 A transition from 'start' to 'stop' will 324 cause the BGP Stop Event to be generated. 325 This parameter can be used to restart BGP 326 peer connections. Care should be used in 327 providing write access to this object 328 without adequate authentication." 329 ::= { bgpPeerEntry 3 } 331 bgpPeerNegotiatedVersion OBJECT-TYPE 332 SYNTAX Integer32 (0..255) 333 MAX-ACCESS read-only 334 STATUS current 335 DESCRIPTION 336 "The negotiated version of BGP running between 337 the two peers. 339 This entry should be zero (0) unless the 340 bgpPeerState is in the openconfirm or the 341 established state." 342 ::= { bgpPeerEntry 4 } 344 bgpPeerLocalAddr OBJECT-TYPE 345 SYNTAX IpAddress 346 MAX-ACCESS read-only 347 STATUS current 348 DESCRIPTION 349 "The local IP address of this entry's BGP 350 connection." 351 ::= { bgpPeerEntry 5 } 353 bgpPeerLocalPort OBJECT-TYPE 354 SYNTAX Integer32 (0..65535) 355 MAX-ACCESS read-only 356 STATUS current 357 DESCRIPTION 358 "The local port for the TCP connection between 359 the BGP peers." 360 ::= { bgpPeerEntry 6 } 362 bgpPeerRemoteAddr OBJECT-TYPE 363 SYNTAX IpAddress 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The remote IP address of this entry's BGP 368 peer." 369 ::= { bgpPeerEntry 7 } 371 bgpPeerRemotePort OBJECT-TYPE 372 SYNTAX Integer32 (0..65535) 373 MAX-ACCESS read-only 374 STATUS current 375 DESCRIPTION 376 "The remote port for the TCP connection 377 between the BGP peers. Note that the 378 objects bgpPeerLocalAddr, 379 bgpPeerLocalPort, bgpPeerRemoteAddr and 380 bgpPeerRemotePort provide the appropriate 381 reference to the standard MIB TCP 382 connection table." 383 ::= { bgpPeerEntry 8 } 385 bgpPeerRemoteAs OBJECT-TYPE 386 SYNTAX Integer32 (0..65535) 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The remote autonomous system number." 391 ::= { bgpPeerEntry 9 } 393 bgpPeerInUpdates OBJECT-TYPE 394 SYNTAX Counter32 395 MAX-ACCESS read-only 396 STATUS current 397 DESCRIPTION 398 "The number of BGP UPDATE messages 399 received on this connection. This object 400 should be initialized to zero (0) when the 401 connection is established. The value of this 402 object, when not in the established state, 403 is undefined." 404 ::= { bgpPeerEntry 10 } 406 bgpPeerOutUpdates OBJECT-TYPE 407 SYNTAX Counter32 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The number of BGP UPDATE messages 412 transmitted on this connection. This 413 object should be initialized to zero (0) 414 when the connection is established. The 415 value of this object, when not in the 416 established state, is undefined." 417 ::= { bgpPeerEntry 11 } 419 bgpPeerInTotalMessages OBJECT-TYPE 420 SYNTAX Counter32 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The total number of messages received 425 from the remote peer on this connection. 426 This object should be initialized to zero 427 when the connection is established. The 428 value of this object, when not in the 429 established state, is undefined." 430 ::= { bgpPeerEntry 12 } 432 bgpPeerOutTotalMessages OBJECT-TYPE 433 SYNTAX Counter32 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "The total number of messages transmitted to 438 the remote peer on this connection. This 439 object should be initialized to zero when 440 the connection is established. The 441 value of this object, when not in the 442 established state, is undefined." 443 ::= { bgpPeerEntry 13 } 445 bgpPeerLastError OBJECT-TYPE 446 SYNTAX OCTET STRING (SIZE (2)) 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The last error code and subcode seen by this 451 peer on this connection. If no error has 452 occurred, this field is zero. Otherwise, the 453 first byte of this two byte OCTET STRING 454 contains the error code, and the second byte 455 contains the subcode." 456 ::= { bgpPeerEntry 14 } 458 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 459 SYNTAX Counter32 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION 463 "The total number of times the BGP FSM 464 transitioned into the established state 465 for this peer." 466 ::= { bgpPeerEntry 15 } 468 bgpPeerFsmEstablishedTime OBJECT-TYPE 469 SYNTAX Gauge32 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "This timer indicates how long (in 474 seconds) this peer has been in the 475 established state or how long 476 since this peer was last in the 477 established state. It is set to zero when 478 a new peer is configured or the router is 479 booted." 480 ::= { bgpPeerEntry 16 } 482 bgpPeerConnectRetryInterval OBJECT-TYPE 483 SYNTAX Integer32 (1..65535) 484 MAX-ACCESS read-write 485 STATUS current 486 DESCRIPTION 487 "Time interval in seconds for the 488 ConnectRetry timer. The suggested value 489 for this timer is 120 seconds." 490 ::= { bgpPeerEntry 17 } 492 bgpPeerHoldTime OBJECT-TYPE 493 SYNTAX Integer32 ( 0 | 3..65535 ) 494 MAX-ACCESS read-only 495 STATUS current 496 DESCRIPTION 497 "Time interval in seconds for the Hold 498 Timer established with the peer. The 499 value of this object is calculated by this 500 BGP speaker by using the smaller of the 501 value in bgpPeerHoldTimeConfigured and the 502 Hold Time received in the OPEN message. 503 This value must be at lease three seconds 504 if it is not zero (0). If the value is 505 zero (0), the Hold Timer has either not been 506 established with the peer, or, the value of 507 bgpPeerHoldTimeConfigured is zero (0)." 508 ::= { bgpPeerEntry 18 } 510 bgpPeerKeepAlive OBJECT-TYPE 511 SYNTAX Integer32 ( 0 | 1..21845 ) 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "Time interval in seconds for the KeepAlive 516 timer established with the peer. The value 517 of this object is calculated by this BGP 518 speaker such that, when compared with 519 bgpPeerHoldTime, it has the same proportion 520 as what bgpPeerKeepAliveConfigured has when 521 compared with bgpPeerHoldTimeConfigured. If 522 the value of this object is zero (0), it 523 indicates that the KeepAlive timer has not 524 been established with the peer, or, the value 525 of bgpPeerKeepAliveConfigured is zero (0)." 526 ::= { bgpPeerEntry 19 } 528 bgpPeerHoldTimeConfigured OBJECT-TYPE 529 SYNTAX Integer32 ( 0 | 3..65535 ) 530 MAX-ACCESS read-write 531 STATUS current 532 DESCRIPTION 533 "Time interval in seconds for the Hold Time 534 configured for this BGP speaker with this 535 peer. This value is placed in an OPEN 536 message sent to this peer by this BGP 537 speaker, and is compared with the Hold 538 Time field in an OPEN message received 539 from the peer when determining the Hold 540 Time (bgpPeerHoldTime) with the peer. 542 This value must not be less than three 543 seconds if it is not zero (0) in which 544 case the Hold Time is NOT to be 545 established with the peer. The suggested 546 value for this timer is 90 seconds." 547 ::= { bgpPeerEntry 20 } 549 bgpPeerKeepAliveConfigured OBJECT-TYPE 550 SYNTAX Integer32 ( 0 | 1..21845 ) 551 MAX-ACCESS read-write 552 STATUS current 553 DESCRIPTION 554 "Time interval in seconds for the 555 KeepAlive timer configured for this BGP 556 speaker with this peer. The value of this 557 object will only determine the 558 KEEPALIVE messages' frequency relative to 559 the value specified in 560 bgpPeerHoldTimeConfigured; the actual 561 time interval for the KEEPALIVE messages is 562 indicated by bgpPeerKeepAlive. A 563 reasonable maximum value for this timer 564 would be configured to be one 565 third of that of 566 bgpPeerHoldTimeConfigured. 567 If the value of this object is zero (0), 568 no periodical KEEPALIVE messages are sent 569 to the peer after the BGP connection has 570 been established. The suggested value for 571 this timer is 30 seconds." 572 ::= { bgpPeerEntry 21 } 574 bgpPeerMinASOriginationInterval OBJECT-TYPE 575 SYNTAX Integer32 (1..65535) 576 MAX-ACCESS read-write 577 STATUS current 578 DESCRIPTION 579 "Time interval in seconds for the 580 MinASOriginationInterval timer. 581 The suggested value for this timer is 15 582 seconds." 583 ::= { bgpPeerEntry 22 } 585 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 586 SYNTAX Integer32 (1..65535) 587 MAX-ACCESS read-write 588 STATUS current 589 DESCRIPTION 590 "Time interval in seconds for the 591 MinRouteAdvertisementInterval timer. 592 The suggested value for this timer is 30 593 seconds." 594 ::= { bgpPeerEntry 23 } 596 bgpPeerInUpdateElapsedTime OBJECT-TYPE 597 SYNTAX Gauge32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "Elapsed time in seconds since the last BGP 602 UPDATE message was received from the peer. 603 Each time bgpPeerInUpdates is incremented, 604 the value of this object is set to zero (0)." 605 ::= { bgpPeerEntry 24 } 607 bgpIdentifier OBJECT-TYPE 608 SYNTAX IpAddress 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "The BGP Identifier of local system." 613 ::= { bgp 4 } 615 -- Received Path Attribute Table. This table contains, 616 -- one entry per path to a network, path attributes 617 -- received from all peers running BGP version 3 or less. 618 -- This table is obsolete, having been replaced in 619 -- functionality with the bgp4PathAttrTable. 621 bgpRcvdPathAttrTable OBJECT-TYPE 622 SYNTAX SEQUENCE OF BgpPathAttrEntry 623 MAX-ACCESS not-accessible 624 STATUS obsolete 625 DESCRIPTION 626 "The BGP Received Path Attribute Table 627 contains information about paths to 628 destination networks received from all 629 peers running BGP version 3 or less." 630 ::= { bgp 5 } 632 bgpPathAttrEntry OBJECT-TYPE 633 SYNTAX BgpPathAttrEntry 634 MAX-ACCESS not-accessible 635 STATUS obsolete 636 DESCRIPTION 637 "Information about a path to a network." 638 INDEX { bgpPathAttrDestNetwork, 639 bgpPathAttrPeer } 640 ::= { bgpRcvdPathAttrTable 1 } 642 BgpPathAttrEntry ::= SEQUENCE { 643 bgpPathAttrPeer 644 IpAddress, 645 bgpPathAttrDestNetwork 646 IpAddress, 647 bgpPathAttrOrigin 648 INTEGER, 649 bgpPathAttrASPath 650 OCTET STRING, 651 bgpPathAttrNextHop 652 IpAddress, 653 bgpPathAttrInterASMetric 654 Integer32 655 } 657 bgpPathAttrPeer OBJECT-TYPE 658 SYNTAX IpAddress 659 MAX-ACCESS read-only 660 STATUS obsolete 661 DESCRIPTION 662 "The IP address of the peer where the path 663 information was learned." 664 ::= { bgpPathAttrEntry 1 } 666 bgpPathAttrDestNetwork OBJECT-TYPE 667 SYNTAX IpAddress 668 MAX-ACCESS read-only 669 STATUS obsolete 670 DESCRIPTION 671 "The address of the destination network." 672 ::= { bgpPathAttrEntry 2 } 674 bgpPathAttrOrigin OBJECT-TYPE 675 SYNTAX INTEGER { 676 igp(1),-- networks are interior 677 egp(2),-- networks learned via the 678 -- EGP protocol 679 incomplete(3) -- networks that 680 -- are learned by some other 681 -- means 682 } 683 MAX-ACCESS read-only 684 STATUS obsolete 685 DESCRIPTION 686 "The ultimate origin of the path information." 687 ::= { bgpPathAttrEntry 3 } 689 bgpPathAttrASPath OBJECT-TYPE 690 SYNTAX OCTET STRING (SIZE (2..255)) 691 MAX-ACCESS read-only 692 STATUS obsolete 693 DESCRIPTION 694 "The set of ASs that must be traversed to reach 695 the network. This object is probably best 696 represented as SEQUENCE OF INTEGER. For SMI 697 compatibility, though, it is represented as 698 OCTET STRING. Each AS is represented as a pair 699 of octets according to the following algorithm: 701 first-byte-of-pair = ASNumber / 256; 702 second-byte-of-pair = ASNumber & 255;" 703 ::= { bgpPathAttrEntry 4 } 705 bgpPathAttrNextHop OBJECT-TYPE 706 SYNTAX IpAddress 707 MAX-ACCESS read-only 708 STATUS obsolete 709 DESCRIPTION 710 "The address of the border router that should 711 be used for the destination network." 712 ::= { bgpPathAttrEntry 5 } 714 bgpPathAttrInterASMetric OBJECT-TYPE 715 SYNTAX Integer32 716 MAX-ACCESS read-only 717 STATUS obsolete 718 DESCRIPTION 719 "The optional inter-AS metric. If this 720 attribute has not been provided for this route, 721 the value for this object is 0." 722 ::= { bgpPathAttrEntry 6 } 724 -- BGP-4 Received Path Attribute Table. This table 725 -- contains, one entry per path to a network, path 726 -- attributes received from all peers running BGP-4. 728 bgp4PathAttrTable OBJECT-TYPE 729 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 730 MAX-ACCESS not-accessible 731 STATUS current 732 DESCRIPTION 733 "The BGP-4 Received Path Attribute Table 734 contains information about paths to 735 destination networks received from all 736 BGP4 peers." 737 ::= { bgp 6 } 739 bgp4PathAttrEntry OBJECT-TYPE 740 SYNTAX Bgp4PathAttrEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "Information about a path to a network." 745 INDEX { bgp4PathAttrIpAddrPrefix, 746 bgp4PathAttrIpAddrPrefixLen, 747 bgp4PathAttrPeer } 748 ::= { bgp4PathAttrTable 1 } 750 Bgp4PathAttrEntry ::= SEQUENCE { 751 bgp4PathAttrPeer 752 IpAddress, 753 bgp4PathAttrIpAddrPrefixLen 754 Integer32, 755 bgp4PathAttrIpAddrPrefix 756 IpAddress, 757 bgp4PathAttrOrigin 758 INTEGER, 759 bgp4PathAttrASPathSegment 760 OCTET STRING, 761 bgp4PathAttrNextHop 762 IpAddress, 763 bgp4PathAttrMultiExitDisc 764 Integer32, 765 bgp4PathAttrLocalPref 766 Integer32, 767 bgp4PathAttrAtomicAggregate 768 INTEGER, 769 bgp4PathAttrAggregatorAS 770 Integer32, 771 bgp4PathAttrAggregatorAddr 772 IpAddress, 773 bgp4PathAttrCalcLocalPref 774 Integer32, 775 bgp4PathAttrBest 776 INTEGER, 777 bgp4PathAttrUnknown 778 OCTET STRING 779 } 781 bgp4PathAttrPeer OBJECT-TYPE 782 SYNTAX IpAddress 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "The IP address of the peer where the path 787 information was learned." 788 ::= { bgp4PathAttrEntry 1 } 790 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 791 SYNTAX Integer32 (0..32) 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "Length in bits of the IP address prefix in 796 the Network Layer Reachability 797 Information field." 798 ::= { bgp4PathAttrEntry 2 } 800 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 801 SYNTAX IpAddress 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "An IP address prefix in the Network Layer 806 Reachability Information field. This object 807 is an IP address containing the prefix with 808 length specified by 809 bgp4PathAttrIpAddrPrefixLen. 810 Any bits beyond the length specified by 811 bgp4PathAttrIpAddrPrefixLen are zeroed." 812 ::= { bgp4PathAttrEntry 3 } 814 bgp4PathAttrOrigin OBJECT-TYPE 815 SYNTAX INTEGER { 816 igp(1),-- networks are interior 817 egp(2),-- networks learned via the 818 -- EGP protocol 819 incomplete(3) -- networks that 820 -- are learned by some other 821 -- means 822 } 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "The ultimate origin of the path 827 information." 828 ::= { bgp4PathAttrEntry 4 } 830 bgp4PathAttrASPathSegment OBJECT-TYPE 831 SYNTAX OCTET STRING (SIZE (2..255)) 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "The sequence of AS path segments. Each AS 836 path segment is represented by a triple 837 . 839 The type is a 1-octet field which has two 840 possible values: 841 1 AS_SET: unordered set of ASs a 842 route in the UPDATE message 843 has traversed 845 2 AS_SEQUENCE: ordered set of ASs 846 a route in the UPDATE message 847 has traversed. 849 The length is a 1-octet field containing the 850 number of ASs in the value field. 852 The value field contains one or more AS 853 numbers, each AS is represented in the octet 854 string as a pair of octets according to the 855 following algorithm: 857 first-byte-of-pair = ASNumber / 256; 858 second-byte-of-pair = ASNumber & 255; 860 Known Issues: 861 o BGP Confederations will result in 862 a type of value of either 3 or 4. 863 o An AS Path may be longer than 255 octets. 864 This may result in this object containing 865 a truncated AS Path." 866 ::= { bgp4PathAttrEntry 5 } 868 bgp4PathAttrNextHop OBJECT-TYPE 869 SYNTAX IpAddress 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 "The address of the border router that 874 should be used for the destination 875 network. This address is the nexthop 876 address received in the UPDATE packet." 877 ::= { bgp4PathAttrEntry 6 } 879 bgp4PathAttrMultiExitDisc OBJECT-TYPE 880 SYNTAX Integer32 (-1..2147483647) 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "This metric is used to discriminate 885 between multiple exit points to an 886 adjacent autonomous system. A value of -1 887 indicates the absence of this attribute. 889 Known Issues: 890 o The BGP-4 specification uses an 891 unsigned 32 bit number and thus this 892 object cannot represent the full 893 range of the protocol." 894 ::= { bgp4PathAttrEntry 7 } 896 bgp4PathAttrLocalPref OBJECT-TYPE 897 SYNTAX Integer32 (-1..2147483647) 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION 901 "The originating BGP4 speaker's degree of 902 preference for an advertised route. A 903 value of -1 indicates the absence of this 904 attribute. 906 Known Issues: 907 o The BGP-4 specification uses an 908 unsigned 32 bit number and thus this 909 object cannot represent the full 910 range of the protocol." 911 ::= { bgp4PathAttrEntry 8 } 913 bgp4PathAttrAtomicAggregate OBJECT-TYPE 914 SYNTAX INTEGER { 915 lessSpecificRouteNotSelected(1), 916 lessSpecificRouteSelected(2) 917 } 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "Whether or not a system has selected 922 a less specific route without 923 selecting a more specific route." 924 ::= { bgp4PathAttrEntry 9 } 926 bgp4PathAttrAggregatorAS OBJECT-TYPE 927 SYNTAX Integer32 (0..65535) 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "The AS number of the last BGP4 speaker that 932 performed route aggregation. A value of 933 zero (0) indicates the absence of this 934 attribute." 935 ::= { bgp4PathAttrEntry 10 } 937 bgp4PathAttrAggregatorAddr OBJECT-TYPE 938 SYNTAX IpAddress 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "The IP address of the last BGP4 speaker 943 that performed route aggregation. A 944 value of 0.0.0.0 indicates the absence 945 of this attribute. 947 Note propagation of AS of zero is illegal in 948 the Internet." 949 ::= { bgp4PathAttrEntry 11 } 951 bgp4PathAttrCalcLocalPref OBJECT-TYPE 952 SYNTAX Integer32 (-1..2147483647) 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "The degree of preference calculated by the 957 receiving BGP4 speaker for an advertised 958 route. A value of -1 indicates the 959 absence of this attribute. 961 Known Issues: 962 o The BGP-4 specification uses an 963 unsigned 32 bit number and thus this 964 object cannot represent the full 965 range of the protocol." 966 ::= { bgp4PathAttrEntry 12 } 968 bgp4PathAttrBest OBJECT-TYPE 969 SYNTAX INTEGER { 970 false(1),-- not chosen as best route 971 true(2) -- chosen as best route 972 } 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "An indication of whether or not this route 977 was chosen as the best BGP4 route for this 978 destination." 979 ::= { bgp4PathAttrEntry 13 } 981 bgp4PathAttrUnknown OBJECT-TYPE 982 SYNTAX OCTET STRING (SIZE(0..255)) 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "One or more path attributes not understood 987 this BGP4 speaker. 989 Path attributes are recorded in the Update Path 990 attribute format of type, length, value. 992 Size zero (0) indicates the absence of such 993 attributes. 995 Octets beyond the maximum size, if any, are not 996 recorded by this object. 998 Known Issues: 999 o Attributes understood by this speaker, but not 1000 represented in this MIB, are unavailable to 1001 the agent." 1002 ::= { bgp4PathAttrEntry 14 } 1004 -- Traps. 1006 -- note that in RFC 1657, bgpTraps was incorrectly 1007 -- assigned a value of { bgp 7 }, and each of the 1008 -- traps had the bgpPeerRemoteAddr object inappropriately 1009 -- removed from their OBJECTS clause. The following 1010 -- definitions restore the semantics of the traps as 1011 -- they were initially defined in RFC 1269. 1013 bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } 1015 bgpEstablishedNotification NOTIFICATION-TYPE 1016 OBJECTS { bgpPeerRemoteAddr, 1017 bgpPeerLastError, 1018 bgpPeerState } 1019 STATUS current 1020 DESCRIPTION 1021 "The BGP Established event is generated when 1022 the BGP FSM enters the ESTABLISHED state. 1024 This object obsoletes bgpEstablished." 1025 ::= { bgpNotification 1 } 1027 bgpBackwardTransNotification NOTIFICATION-TYPE 1028 OBJECTS { bgpPeerRemoteAddr, 1029 bgpPeerLastError, 1030 bgpPeerState } 1031 STATUS current 1032 DESCRIPTION 1033 "The BGPBackwardTransNotification Event is 1034 generated when the BGP FSM moves from a higher 1035 numbered state to a lower numbered state. 1037 This object obsoletes bgpBackwardsTransition." 1038 ::= { bgpNotification 2 } 1040 -- { bgp 7 } is obsoleted 1042 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } 1044 bgpEstablished NOTIFICATION-TYPE 1045 OBJECTS { bgpPeerRemoteAddr, 1046 bgpPeerLastError, 1047 bgpPeerState } 1048 STATUS obsolete 1049 DESCRIPTION 1050 "The BGP Established event is generated when 1051 the BGP FSM enters the ESTABLISHED state. 1053 This object has been obsoleted in favor of 1054 bgpEstablishedNotification." 1055 ::= { bgpTraps 1 } 1057 bgpBackwardTransition NOTIFICATION-TYPE 1058 OBJECTS { bgpPeerRemoteAddr, 1059 bgpPeerLastError, 1060 bgpPeerState } 1061 STATUS current 1062 DESCRIPTION 1063 "The BGPBackwardTransition Event is generated 1064 when the BGP FSM moves from a higher numbered 1065 state to a lower numbered state. 1067 This object has been obsoleted in favor of 1068 bgpBackwardTransNotification." 1069 ::= { bgpTraps 2 } 1071 -- conformance information 1073 bgpMIBConformance OBJECT IDENTIFIER 1074 ::= { bgp 8 } 1076 bgpMIBCompliances OBJECT IDENTIFIER 1077 ::= { bgpMIBConformance 1 } 1078 bgpMIBGroups OBJECT IDENTIFIER 1079 ::= { bgpMIBConformance 2 } 1081 -- compliance statements 1083 bgpMIBCompliance MODULE-COMPLIANCE 1084 STATUS current 1085 DESCRIPTION 1086 "The compliance statement for entities which 1087 implement the BGP4 mib." 1088 MODULE -- this module 1089 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 1090 bgp4MIBPeerGroup, 1091 bgp4MIBPathAttrGroup, 1092 bgp4MIBNotificationGroup, 1093 bgp4MIBNewNotificationGroup } 1094 ::= { bgpMIBCompliances 1 } 1096 -- units of conformance 1098 bgp4MIBGlobalsGroup OBJECT-GROUP 1099 OBJECTS { bgpVersion, 1100 bgpLocalAs, 1101 bgpIdentifier } 1102 STATUS current 1103 DESCRIPTION 1104 "A collection of objects providing 1105 information on global BGP state." 1106 ::= { bgpMIBGroups 1 } 1108 bgp4MIBPeerGroup OBJECT-GROUP 1109 OBJECTS { bgpPeerIdentifier, 1110 bgpPeerState, 1111 bgpPeerAdminStatus, 1112 bgpPeerNegotiatedVersion, 1113 bgpPeerLocalAddr, 1114 bgpPeerLocalPort, 1115 bgpPeerRemoteAddr, 1116 bgpPeerRemotePort, 1117 bgpPeerRemoteAs, 1118 bgpPeerInUpdates, 1119 bgpPeerOutUpdates, 1120 bgpPeerInTotalMessages, 1121 bgpPeerOutTotalMessages, 1122 bgpPeerLastError, 1123 bgpPeerFsmEstablishedTransitions, 1124 bgpPeerFsmEstablishedTime, 1125 bgpPeerConnectRetryInterval, 1126 bgpPeerHoldTime, 1127 bgpPeerKeepAlive, 1128 bgpPeerHoldTimeConfigured, 1129 bgpPeerKeepAliveConfigured, 1130 bgpPeerMinASOriginationInterval, 1131 bgpPeerMinRouteAdvertisementInterval, 1132 bgpPeerInUpdateElapsedTime } 1133 STATUS current 1134 DESCRIPTION 1135 "A collection of objects for managing 1136 BGP peers." 1137 ::= { bgpMIBGroups 2 } 1139 bgp4MIBRcvdPathAttrGroup OBJECT-GROUP 1140 OBJECTS { bgpPathAttrPeer, 1141 bgpPathAttrDestNetwork, 1142 bgpPathAttrOrigin, 1143 bgpPathAttrASPath, 1144 bgpPathAttrNextHop, 1145 bgpPathAttrInterASMetric } 1146 STATUS obsolete 1147 DESCRIPTION 1148 "A collection of objects for managing BGP 1149 path entries. 1151 This conformance group is obsolete, 1152 replaced by bgp4MIBPathAttrGroup." 1153 ::= { bgpMIBGroups 3 } 1155 bgp4MIBPathAttrGroup OBJECT-GROUP 1156 OBJECTS { bgp4PathAttrPeer, 1157 bgp4PathAttrIpAddrPrefixLen, 1158 bgp4PathAttrIpAddrPrefix, 1159 bgp4PathAttrOrigin, 1160 bgp4PathAttrASPathSegment, 1161 bgp4PathAttrNextHop, 1162 bgp4PathAttrMultiExitDisc, 1163 bgp4PathAttrLocalPref, 1164 bgp4PathAttrAtomicAggregate, 1165 bgp4PathAttrAggregatorAS, 1166 bgp4PathAttrAggregatorAddr, 1167 bgp4PathAttrCalcLocalPref, 1168 bgp4PathAttrBest, 1169 bgp4PathAttrUnknown } 1170 STATUS current 1171 DESCRIPTION 1172 "A collection of objects for managing 1173 BGP path entries." 1174 ::= { bgpMIBGroups 4 } 1176 bgp4MIBNotificationGroup NOTIFICATION-GROUP 1177 NOTIFICATIONS { bgpEstablished, 1178 bgpBackwardTransition } 1179 STATUS obsolete 1180 DESCRIPTION 1181 "A collection of notifications for signaling 1182 changes in BGP peer relationships. 1184 Obsoleted by bgp4MIBNewNotificationGroup" 1185 ::= { bgpMIBGroups 5 } 1187 bgp4MIBNewNotificationGroup NOTIFICATION-GROUP 1188 NOTIFICATIONS { bgpEstablishedNotification, 1189 bgpBackwardTransNotification } 1190 STATUS current 1191 DESCRIPTION 1192 "A collection of notifications for signaling 1193 changes in BGP peer relationships. 1195 Obsoletes bgp4MIBNotificationGroup." 1196 ::= { bgpMIBGroups 6 } 1198 END 1200 8. Intellectual Property 1202 The IETF takes no position regarding the validity or scope of any 1203 intellectual property or other rights that might be claimed to 1204 pertain to the implementation or use of the technology described in 1205 this document or the extent to which any license under such rights 1206 might or might not be available; neither does it represent that it 1207 has made any effort to identify any such rights. Information on the 1208 IETF's procedures with respect to rights in standards-track and 1209 standards-related documentation can be found in BCP-11. Copies of 1210 claims of rights made available for publication and any assurances of 1211 licenses to be made available, or the result of an attempt made to 1212 obtain a general license or permission for the use of such 1213 proprietary rights by implementors or users of this specification can 1214 be obtained from the IETF Secretariat. 1216 9. Acknowledgements 1218 We would like to acknowledge the assistance of all the members of the 1219 Inter-Domain Routing Working Group, and particularly the following 1220 individuals: 1222 Yakov Rekhter, Juniper Networks 1223 Rob Coltun, Redback 1224 Guy Almes, Internet2 1225 Jeff Honig, BSDi 1226 Marshall T. Rose, Dover Beach Consulting, Inc. 1227 Dennis Ferguson, Juniper Networks 1228 Mike Mathis, PSC 1229 John Krawczyk, Bay Networks 1230 Curtis Villamizar, Avici 1231 Dave LeRoy, Pencom Systems 1232 Paul Traina, Juniper Networks 1233 Andrew Partan, MFN 1234 Robert Snyder, cisco Systems 1235 Dimitry Haskin, Nortel 1236 Peder Chr Norgaard, Telebit Communications A/S 1237 Joel Halpern, CTO Longitude Systems, Inc. 1238 Nick Thille, RedBack Networks 1239 Bert Wijnen, Lucent 1240 Shane Wright, NextHop 1241 Mike McFadden, Riverstone Networks, Inc. 1242 Jon Saperia, JDS Consulting, Inc. 1243 Wayne Tackabury, Gold Wire Technology, Inc. 1244 Bill Fenner, AT&T Research 1246 The origin of this document is from RFC 1269 "Definitions of Managed 1247 Objects for the Border Gateway Protocol (Version 3)" written by Steve 1248 Willis and John Burruss, which was updated by John Chu to support 1249 BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of 1250 these original authors. 1252 10. References 1254 [BGP4] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC 1255 1771, March 1995. 1257 [BGP4APP] Rekhter, Y., Gross, P., "Application of the Border Gateway 1258 Protocol in the Internet", RFC 1772, March 1995. 1260 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1261 for Describing SNMP Management Frameworks", RFC 2571, April 1262 1999. 1264 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1265 of Management Information for TCP/IP-based Internets", STD 1266 16, RFC 1155, May 1990. 1268 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1269 16, RFC 1212, March 1991. 1271 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1272 SNMP", RFC 1215, March 1991. 1274 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1275 Rose, M., and S. Waldbusser, "Structure of Management 1276 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1277 1999. 1279 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1280 Rose, M., and S. Waldbusser, "Textual Conventions for 1281 SMIv2", STD 58, RFC 2579, April 1999. 1283 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1284 Rose, M., and S. Waldbusser, "Conformance Statements for 1285 SMIv2", STD 58, RFC 2580, April 1999. 1287 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1288 Network Management Protocol", STD 15, RFC 1157, May 1990. 1290 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1291 "Introduction to Community-based SNMPv2", RFC 1901, January 1292 1996. 1294 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1295 "Transport Mappings for Version 2 of the Simple Network 1296 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1298 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1299 Processing and Dispatching for the Simple Network Management 1300 Protocol (SNMP)", RFC 2572, April 1999. 1302 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1303 (USM) for version 3 of the Simple Network Management 1304 Protocol (SNMPv3)", RFC 2574, April 1999. 1306 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1307 "Protocol Operations for Version 2 of the Simple Network 1308 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1310 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1311 RFC 2573, April 1999. 1313 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1314 Access Control Model (VACM) for the Simple Network 1315 Management Protocol (SNMP)", RFC 2575, April 1999. 1317 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1318 "Introduction to Version 3 of the Internet-standard Network 1319 Management Framework", RFC 2570, April 1999. 1321 11. Security Considerations 1323 There are a number of management objects defined in this MIB that 1324 have a MAX-ACCESS clause of read-write: 1326 bgpPeerAdminStatus 1327 bgpPeerConnectRetryInterval 1328 bgpPeerHoldTimeConfigured 1329 bgpPeerKeepAliveConfigured 1330 bgpPeerMinASOriginationInterval 1331 bgpPeerMinRouteAdvertisementInterval 1333 These objects should be considered sensitive or vulnerable in most 1334 network environments. The support for SET operations in a non-secure 1335 environment without proper protection can have a negative effect on 1336 network operations. Incorrect configuration of these parameters may 1337 cause BGP peer connections to terminate early or to send more routes 1338 under a flapping condition. 1340 There are a number of managed objects in this MIB that may be 1341 considered to contain sensitive information in the operation of a 1342 network. For example, a BGP peer's local and remote addresses may be 1343 sensitive for ISPs who want to keep interface addresses on routers 1344 confidential to prevent router addresses used for a denial of service 1345 attack or spoofing. 1347 Therefore, it may be important in some environments to control read 1348 access to these objects and possibly to even encrypt the values of 1349 these object when sending them over the network via SNMP. Not all 1350 versions of SNMP provide features for such a secure environment. 1352 SNMPv1 by itself is not a secure environment. Even if the network 1353 itself is secure (for example by using IPSec), even then, there is no 1354 control as to who on the secure network is allowed to access and 1355 GET/SET (read/change/create/delete) the objects in this MIB. 1357 It is recommended that the implementers consider the security 1358 features as provided by the SNMPv3 framework. Specifically, the use 1359 of the User-based Security Model RFC 2274 [14] and the View-based 1360 Access Control Model RFC 2275 [17] is recommended. 1362 It is then a customer/user responsibility to ensure that the SNMP 1363 entity giving access to an instance of this MIB, is properly 1364 configured to give access to the objects only to those principals 1365 (users) that have legitimate rights to indeed GET or SET 1366 (change/create/delete) them. 1368 12. Editors Address 1370 Jeff Haas, Sue Hares 1371 NextHop Technologies 1372 825 Victor's Way, Suite 100 1373 Ann Arbor, MI 48103 1374 Phone: +1 734 222-1600 1375 Fax: +1 734 222-1602 1376 Email: jhaas@nexthop.com 1377 skh@nexthop.com 1379 13. Full Copyright Statement 1381 Copyright (C) The Internet Society (1999). All Rights Reserved. 1383 This document and translations of it may be copied and furnished to 1384 others, and derivative works that comment on or otherwise explain it 1385 or assist in its implementation may be prepared, copied, published 1386 and distributed, in whole or in part, without restriction of any 1387 kind, provided that the above copyright notice and this paragraph are 1388 included on all such copies and derivative works. However, this 1389 document itself may not be modified in any way, such as by removing 1390 the copyright notice or references to the Internet Society or other 1391 Internet organizations, except as needed for the purpose of 1392 developing Internet standards in which case the procedures for 1393 copyrights defined in the Internet Standards process must be 1394 followed, or as required to translate it into languages other than 1395 English. 1397 The limited permissions granted above are perpetual and will not be 1398 revoked by the Internet Society or its successors or assigns. 1400 This document and the information contained herein is provided on an 1401 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1402 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1403 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1404 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1405 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1407 Table of Contents 1409 1. Status of this Memo .............................................. 1 1411 2. Copyright Notice ................................................. 2 1413 3. Abstract ......................................................... 2 1415 4. Introduction ..................................................... 2 1417 5. The SNMP Management Framework .................................... 2 1419 6. Overview ......................................................... 3 1421 7. Definitions ...................................................... 5 1423 8. Intellectual Property ........................................... 28 1425 9. Acknowledgements ................................................ 29 1427 10. References ...................................................... 30 1429 11. Security Considerations ......................................... 32 1431 12. Editors Address ................................................. 33 1433 13. Full Copyright Statement ........................................ 33 1435 i