idnits 2.17.1 draft-ietf-idr-bgp4-mib-06.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: ---------------------------------------------------------------------------- ** 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 31 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 32 pages 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 20 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** There are 5 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (Februrary 2001) is 8526 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) ** Obsolete normative reference: RFC 1771 (ref. '1') (Obsoleted by RFC 4271) ** Obsolete normative reference: RFC 2271 (ref. '3') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '6') ** Obsolete normative reference: RFC 1902 (ref. '7') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '8') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '9') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '10') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '11') ** Obsolete normative reference: RFC 1906 (ref. '12') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '13') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '14') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '15') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '16') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '17') (Obsoleted by RFC 2575) Summary: 22 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT BGP4-MIB Februrary 2001 4 Network Working Group S. Hares 5 INTERNET DRAFT NextHop 6 J. Haas 7 NextHop 8 S. Willis 9 Argon Networks 10 J. Burruss 11 WinData 12 J. Chu 13 Cosine 14 February 2000 16 Definitions of Managed Objects 17 for the Fourth Version of Border Gateway Protocol (BGP-4) 18 20 Status of this Memo 22 This document is an Internet-Draft and is in full conformance with 23 all provisions of Section 10 of RFC 2026. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet- Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 Copyright Notice 43 Copyright (C) The Internet Society (1999). All Rights Reserved. 45 Abstract 47 This memo is an extension to the SNMP MIB. It specifies an IAB 48 standards track protocol for the Internet community, and requests 49 discussion and suggestions for improvements. The origin of this memo 50 is from RFC 1269 "Definitions of Managed Objects for the Border 51 Gateway Protocol (Version 3)", which was updated to support BGP-4 in 52 RFC 1657. This memo fixes errors introduced when the MIB was 53 converted to use the SNMPv2 SMI, as well as updates references to the 54 current SNMP framework documents. 56 Distribution of this memo is unlimited. Please forward comments to 57 idr@merit.net. 59 1. Introduction 61 This memo defines a portion of the Management Information Base (MIB) 62 for use with network management protocols in the Internet community. 63 In particular, it describes managed objects used for managing the 64 Border Gateway Protocol Version 4 or lower [1, 2]. 66 2. The SNMP Network Management Framework 68 The SNMP Management Framework presently consists of five major 69 components: 71 +o An overall architecture, described in RFC 2271 [3]. 73 +o bgp Mechanisms for describing and naming objects and events for 74 the purpose of management. The first version of this Structure 75 of Management Information (SMI) is called SMIv1 and described in 76 RFC 1155 [4], RFC 1212 [5] and RFC 1215 [6]. The second version, 77 called SMIv2, is described in RFC 1902 [7], RFC 1903 [8] and RFC 78 1904 [9]. 80 +o Message protocols for transferring management information. The 81 first version of the SNMP message protocol is called SNMPv1 and 82 described in RFC 1157 [10]. A second version of the SNMP message 83 protocol, which is not an Internet standards track protocol, is 84 called SNMPv2c and described in RFC 1901 [11] and RFC 1906 [12]. 85 The third version of the message protocol is called SNMPv3 and 86 described in RFC 1906 [12], RFC 2272 [13] and RFC 2274 [14]. 88 +o Protocol operations for accessing management information. The 89 first set of protocol operations and associated PDU formats is 90 described in RFC 1157 [10]. A second set of protocol operations 91 and associated PDU formats is described in RFC 1905 [15]. 93 +o A set of fundamental applications described in RFC 2273 [16] and 94 the view-based access control mechanism described in RFC 2275 95 [17]. 97 This memo specifies a MIB module that is compliant to the SMIv2. A 98 MIB conforming to the SMIv1 can be produced through the appropriate 99 translations. The resulting translated MIB must be semantically 100 equivalent, except where objects or events are omitted because no 101 translation is possible (use of Counter64). Some machine readable 102 information in SMIv2 will be converted into textual descriptions in 103 SMIv1 during the translation process. However, this loss of machine 104 readable information is not considered to change the semantics of the 105 MIB. 107 3. Object Definitions 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. Objects in the MIB are 111 defined using the subset of Abstract Syntax Notation One (ASN.1) 112 defined in the SMI. In particular, each object type is named by an 113 OBJECT IDENTIFIER, an administratively assigned name. The object 114 type together with an object instance serves to uniquely identify a 115 specific instantiation of the object. For human convenience, we 116 often use a textual string, termed the descriptor, to refer to the 117 object type. 119 4. Overview 121 These objects are used to control and manage a BGP-4 implementation. 123 Apart from a few system-wide scalar objects, this MIB is broken into 124 three tables: the BGP Peer Table, the BGP Received Path Attribute 125 Table, and the BGP-4 Received Path Attribute Table. The BGP Peer 126 Table contains information about state and current activity of 127 connections with the BGP peers. The Received Path Attribute Table 128 contains path attributes received from all peers running BGP version 129 3 or less. The BGP-4 Received Path Attribute Table contains path 130 attributes received from all BGP-4 peers. The actual attributes used 131 in determining a route are a subset of the received attribute tables 132 after local routing policy has been applied. 134 5. Definitions 136 BGP4-MIB DEFINITIONS ::= BEGIN 138 IMPORTS 139 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 140 IpAddress, Integer32, Counter32, Gauge32, mib-2 141 FROM SNMPv2-SMI 142 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 143 FROM SNMPv2-CONF; 145 bgp MODULE-IDENTITY 146 LAST-UPDATED "0012100000Z" 147 ORGANIZATION "IETF IDR Working Group" 148 CONTACT-INFO "E-mail: idr@merit.net 150 Susan Hares (Editor) 151 517 W. William Street 152 Ann Arbor, MI 48103-4943 153 Tel: +1 734 973-2200 154 Fax: +1 734 615-3241 155 E-mail: skh@nexthop.com" 157 DESCRIPTION 158 "Cleanup to conform with draft-12 of BGP. 159 Updated semantics of MED and localpref. 160 Adjusted sizes of objects to match draft. 161 Changed the semantics of bgp4PathAttrUnknown." 162 REVISION "200102240000Z" 163 DESCRIPTION 164 "The MIB module for BGP-4." 165 REVISION "0012100000Z" 166 DESCRIPTION 167 "Corrected duplicate OBJECT IDENTIFIER 168 assignment in the conformance information." 169 REVISION "9601080000Z" 170 DESCRIPTION 171 "1) Fixed the definitions of the traps to 172 make them equivalent to their initial 173 definition in RFC 1269. 174 2) Added compliance and conformance info. 175 3) Updated for latest BGP information 176 draft-ietf-idr-bgp4-10.txt for value of 177 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, 178 bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc, 179 bgp4PathAttrASPathSegement." 181 ::= { mib-2 15 } 183 bgpVersion OBJECT-TYPE 184 SYNTAX OCTET STRING (SIZE (1..32)) 185 MAX-ACCESS read-only 186 STATUS current 187 DESCRIPTION 188 "Vector of supported BGP protocol version 189 numbers. Each peer negotiates the version 190 from this vector. Versions are identified 191 via the string of bits contained within this 192 object. The first octet contains bits 0 to 193 7, the second octet contains bits 8 to 15, 194 and so on, with the most significant bit 195 referring to the lowest bit number in the 196 octet (e.g., the MSB of the first octet 197 refers to bit 0). If a bit, i, is present 198 and set, then the version (i+1) of the BGP 199 is supported." 200 ::= { bgp 1 } 202 bgpLocalAs OBJECT-TYPE 203 SYNTAX INTEGER (0..65535) 204 MAX-ACCESS read-only 205 STATUS current 206 DESCRIPTION 207 "The local autonomous system number." 208 ::= { bgp 2 } 210 -- BGP Peer table. This table contains, one entry per BGP 211 -- peer, information about the BGP peer. 213 bgpPeerTable OBJECT-TYPE 214 SYNTAX SEQUENCE OF BgpPeerEntry 215 MAX-ACCESS not-accessible 216 STATUS current 217 DESCRIPTION 218 "BGP peer table. This table contains, 219 one entry per BGP peer, information about the 220 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 INTEGER, 247 bgpPeerRemoteAddr 248 IpAddress, 249 bgpPeerRemotePort 250 INTEGER, 251 bgpPeerRemoteAs 252 INTEGER, 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 INTEGER, 269 bgpPeerHoldTime 270 INTEGER, 271 bgpPeerKeepAlive 272 INTEGER, 273 bgpPeerHoldTimeConfigured 274 INTEGER, 275 bgpPeerKeepAliveConfigured 276 INTEGER, 277 bgpPeerMinASOriginationInterval 278 INTEGER, 279 bgpPeerMinRouteAdvertisementInterval 280 INTEGER, 281 bgpPeerInUpdateElapsedTime 282 Gauge32 283 } 285 bgpPeerIdentifier OBJECT-TYPE 286 SYNTAX IpAddress 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The BGP Identifier of this entry's BGP peer." 291 ::= { bgpPeerEntry 1 } 293 bgpPeerState OBJECT-TYPE 294 SYNTAX INTEGER { 295 idle(1), 296 connect(2), 297 active(3), 298 opensent(4), 299 openconfirm(5), 300 established(6) 301 } 302 MAX-ACCESS read-only 303 STATUS current 304 DESCRIPTION 305 "The BGP peer connection state." 306 ::= { bgpPeerEntry 2 } 308 bgpPeerAdminStatus OBJECT-TYPE 309 SYNTAX INTEGER { 310 stop(1), 311 start(2) 312 } 314 MAX-ACCESS read-write 315 STATUS current 316 DESCRIPTION 317 "The desired state of the BGP connection. A 318 transition from 'stop' to 'start' will cause 319 the BGP Start Event to be generated. A 320 transition from 'start' to 'stop' will cause 321 the BGP Stop Event to be generated. This 322 parameter can be used to restart BGP peer 323 connections. Care should be used in providing 324 write access to this object without adequate 325 authentication." 326 ::= { bgpPeerEntry 3 } 328 bgpPeerNegotiatedVersion OBJECT-TYPE 329 SYNTAX INTEGER (1..255) 330 MAX-ACCESS read-only 331 STATUS current 332 DESCRIPTION 333 "The negotiated version of BGP running between 334 the two peers." 335 ::= { bgpPeerEntry 4 } 337 bgpPeerLocalAddr OBJECT-TYPE 338 SYNTAX IpAddress 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "The local IP address of this entry's BGP 343 connection." 344 ::= { bgpPeerEntry 5 } 346 bgpPeerLocalPort OBJECT-TYPE 347 SYNTAX INTEGER (0..65535) 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The local port for the TCP connection between 352 the BGP peers." 353 ::= { bgpPeerEntry 6 } 355 bgpPeerRemoteAddr OBJECT-TYPE 356 SYNTAX IpAddress 357 MAX-ACCESS read-only 358 STATUS current 359 DESCRIPTION 360 "The remote IP address of this entry's BGP 361 peer." 362 ::= { bgpPeerEntry 7 } 364 bgpPeerRemotePort OBJECT-TYPE 365 SYNTAX INTEGER (0..65535) 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "The remote port for the TCP connection between 370 the BGP peers. Note that the objects 371 bgpPeerLocalAddr, bgpPeerLocalPort, 372 bgpPeerRemoteAddr and bgpPeerRemotePort 373 provide the appropriate reference to the 374 standard MIB TCP connection table." 375 ::= { bgpPeerEntry 8 } 377 bgpPeerRemoteAs OBJECT-TYPE 378 SYNTAX INTEGER (0..65535) 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The remote autonomous system number." 383 ::= { bgpPeerEntry 9 } 385 bgpPeerInUpdates OBJECT-TYPE 386 SYNTAX Counter32 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The number of BGP UPDATE messages received on 391 this connection. This object should be 392 initialized to zero (0) when the connection is 393 established." 394 ::= { bgpPeerEntry 10 } 396 bgpPeerOutUpdates OBJECT-TYPE 397 SYNTAX Counter32 398 MAX-ACCESS read-only 399 STATUS current 400 DESCRIPTION 401 "The number of BGP UPDATE messages transmitted 402 on this connection. This object should be 403 initialized to zero (0) when the connection is 404 established." 405 ::= { bgpPeerEntry 11 } 407 bgpPeerInTotalMessages OBJECT-TYPE 408 SYNTAX Counter32 409 MAX-ACCESS read-only 410 STATUS current 411 DESCRIPTION 412 "The total number of messages received from the 413 remote peer on this connection. This object 414 should be initialized to zero when the 415 connection is established." 416 ::= { bgpPeerEntry 12 } 418 bgpPeerOutTotalMessages OBJECT-TYPE 419 SYNTAX Counter32 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "The total number of messages transmitted to 424 the remote peer on this connection. This object 425 should be initialized to zero when the 426 connection is established." 427 ::= { bgpPeerEntry 13 } 429 bgpPeerLastError OBJECT-TYPE 430 SYNTAX OCTET STRING (SIZE (2)) 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "The last error code and subcode seen by this 435 peer on this connection. If no error has 436 occurred, this field is zero. Otherwise, the 437 first byte of this two byte OCTET STRING 438 contains the error code, and the second byte 439 contains the subcode." 440 ::= { bgpPeerEntry 14 } 442 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 443 SYNTAX Counter32 444 MAX-ACCESS read-only 445 STATUS current 446 DESCRIPTION 447 "The total number of times the BGP FSM 448 transitioned into the established state." 449 ::= { bgpPeerEntry 15 } 451 bgpPeerFsmEstablishedTime OBJECT-TYPE 452 SYNTAX Gauge32 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "This timer indicates how long (in seconds) this 457 peer has been in the Established state or how long 458 since this peer was last in the Established state. 459 It is set to zero when a new peer is configured or 460 the router is booted." 461 ::= { bgpPeerEntry 16 } 463 bgpPeerConnectRetryInterval OBJECT-TYPE 464 SYNTAX INTEGER (1..65535) 465 MAX-ACCESS read-write 466 STATUS current 467 DESCRIPTION 468 "Time interval in seconds for the ConnectRetry 469 timer. The suggested value for this timer is 470 120 seconds." 471 ::= { bgpPeerEntry 17 } 473 bgpPeerHoldTime OBJECT-TYPE 474 SYNTAX INTEGER ( 0 | 3..65535 ) 475 MAX-ACCESS read-only 476 STATUS current 477 DESCRIPTION 478 "Time interval in seconds for the Hold Timer 479 established with the peer. The value of this 480 object is calculated by this BGP speaker by 481 using the smaller of the value in 482 bgpPeerHoldTimeConfigured and the Hold Time 483 received in the OPEN message. This value 484 must be at lease three seconds if it is not 485 zero (0) in which case the Hold Timer has 486 not been established with the peer, or, the 487 value of bgpPeerHoldTimeConfigured is zero (0)." 488 ::= { bgpPeerEntry 18 } 490 bgpPeerKeepAlive OBJECT-TYPE 491 SYNTAX INTEGER ( 0 | 1..21845 ) 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "Time interval in seconds for the KeepAlive 496 timer established with the peer. The value of 497 this object is calculated by this BGP speaker 498 such that, when compared with bgpPeerHoldTime, 499 it has the same proportion as what 500 bgpPeerKeepAliveConfigured has when compared 501 with bgpPeerHoldTimeConfigured. If the value 502 of this object is zero (0), it indicates that 503 the KeepAlive timer has not been established 504 with the peer, or, the value of 505 bgpPeerKeepAliveConfigured is zero (0)." 506 ::= { bgpPeerEntry 19 } 508 bgpPeerHoldTimeConfigured OBJECT-TYPE 509 SYNTAX INTEGER ( 0 | 3..65535 ) 510 MAX-ACCESS read-write 511 STATUS current 512 DESCRIPTION 513 "Time interval in seconds for the Hold Time 514 configured for this BGP speaker with this peer. 515 This value is placed in an OPEN message sent to 516 this peer by this BGP speaker, and is compared 517 with the Hold Time field in an OPEN message 518 received from the peer when determining the Hold 519 Time (bgpPeerHoldTime) with the peer. This value 520 must not be less than three seconds if it is not 521 zero (0) in which case the Hold Time is NOT to be 522 established with the peer. The suggested value for 523 this timer is 90 seconds." 524 ::= { bgpPeerEntry 20 } 526 bgpPeerKeepAliveConfigured OBJECT-TYPE 527 SYNTAX INTEGER ( 0 | 1..21845 ) 528 MAX-ACCESS read-write 529 STATUS current 530 DESCRIPTION 531 "Time interval in seconds for the KeepAlive timer 532 configured for this BGP speaker with this peer. 533 The value of this object will only determine the 534 KEEPALIVE messages' frequency relative to the value 535 specified in bgpPeerHoldTimeConfigured; the actual 536 time interval for the KEEPALIVE messages is 537 indicated by bgpPeerKeepAlive. A reasonable 538 maximum value for this timer would be configured to 539 be one third of that of bgpPeerHoldTimeConfigured. 540 If the value of this object is zero (0), no 541 periodical KEEPALIVE messages are sent to the peer 542 after the BGP connection has been established. The 543 suggested value for this timer is 30 seconds." 544 ::= { bgpPeerEntry 21 } 546 bgpPeerMinASOriginationInterval OBJECT-TYPE 547 SYNTAX INTEGER (1..65535) 548 MAX-ACCESS read-write 549 STATUS current 550 DESCRIPTION 551 "Time interval in seconds for the 552 MinASOriginationInterval timer. 553 The suggested value for this timer is 15 seconds." 554 ::= { bgpPeerEntry 22 } 556 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 557 SYNTAX INTEGER (1..65535) 558 MAX-ACCESS read-write 559 STATUS current 560 DESCRIPTION 561 "Time interval in seconds for the 562 MinRouteAdvertisementInterval timer. 563 The suggested value for this timer is 30 seconds." 564 ::= { bgpPeerEntry 23 } 566 bgpPeerInUpdateElapsedTime OBJECT-TYPE 567 SYNTAX Gauge32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "Elapsed time in seconds since the last BGP 572 UPDATE message was received from the peer. 573 Each time bgpPeerInUpdates is incremented, 574 the value of this object is set to zero (0)." 575 ::= { bgpPeerEntry 24 } 577 bgpIdentifier OBJECT-TYPE 578 SYNTAX IpAddress 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "The BGP Identifier of local system." 583 ::= { bgp 4 } 585 -- Received Path Attribute Table. This table contains, 586 -- one entry per path to a network, path attributes 587 -- received from all peers running BGP version 3 or less. 588 -- This table is obsolete, having been replaced in 589 -- functionality with the bgp4PathAttrTable. 591 bgpRcvdPathAttrTable OBJECT-TYPE 592 SYNTAX SEQUENCE OF BgpPathAttrEntry 593 MAX-ACCESS not-accessible 594 STATUS obsolete 595 DESCRIPTION 596 "The BGP Received Path Attribute Table contains 597 information about paths to destination networks 598 received from all peers running BGP version 3 or 599 less." 600 ::= { bgp 5 } 602 bgpPathAttrEntry OBJECT-TYPE 603 SYNTAX BgpPathAttrEntry 604 MAX-ACCESS not-accessible 605 STATUS obsolete 606 DESCRIPTION 607 "Information about a path to a network." 608 INDEX { bgpPathAttrDestNetwork, 609 bgpPathAttrPeer } 610 ::= { bgpRcvdPathAttrTable 1 } 612 BgpPathAttrEntry ::= SEQUENCE { 613 bgpPathAttrPeer 614 IpAddress, 615 bgpPathAttrDestNetwork 616 IpAddress, 617 bgpPathAttrOrigin 618 INTEGER, 619 bgpPathAttrASPath 620 OCTET STRING, 621 bgpPathAttrNextHop 622 IpAddress, 623 bgpPathAttrInterASMetric 624 Integer32 625 } 627 bgpPathAttrPeer OBJECT-TYPE 628 SYNTAX IpAddress 629 MAX-ACCESS read-only 630 STATUS obsolete 631 DESCRIPTION 632 "The IP address of the peer where the path 633 information was learned." 634 ::= { bgpPathAttrEntry 1 } 636 bgpPathAttrDestNetwork OBJECT-TYPE 637 SYNTAX IpAddress 638 MAX-ACCESS read-only 639 STATUS obsolete 640 DESCRIPTION 641 "The address of the destination network." 642 ::= { bgpPathAttrEntry 2 } 644 bgpPathAttrOrigin OBJECT-TYPE 645 SYNTAX Integer32 { 646 igp(1),-- networks are interior 647 egp(2),-- networks learned via EGP 648 incomplete(3) -- undetermined 649 } 650 MAX-ACCESS read-only 651 STATUS obsolete 652 DESCRIPTION 653 "The ultimate origin of the path information." 654 ::= { bgpPathAttrEntry 3 } 656 bgpPathAttrASPath OBJECT-TYPE 657 SYNTAX OCTET STRING (SIZE (2..255)) 658 MAX-ACCESS read-only 659 STATUS obsolete 660 DESCRIPTION 661 "The set of ASs that must be traversed to reach 662 the network. This object is probably best 663 represented as SEQUENCE OF INTEGER. For SMI 664 compatibility, though, it is represented as 665 OCTET STRING. Each AS is represented as a pair 666 of octets according to the following algorithm: 668 first-byte-of-pair = ASNumber / 256; 669 second-byte-of-pair = ASNumber & 255;" 670 ::= { bgpPathAttrEntry 4 } 672 bgpPathAttrNextHop OBJECT-TYPE 673 SYNTAX IpAddress 674 MAX-ACCESS read-only 675 STATUS obsolete 676 DESCRIPTION 677 "The address of the border router that should 678 be used for the destination network." 679 ::= { bgpPathAttrEntry 5 } 681 bgpPathAttrInterASMetric OBJECT-TYPE 682 SYNTAX Integer32 683 MAX-ACCESS read-only 684 STATUS obsolete 685 DESCRIPTION 686 "The optional inter-AS metric. If this 687 attribute has not been provided for this route, 688 the value for this object is 0." 689 ::= { bgpPathAttrEntry 6 } 691 -- BGP-4 Received Path Attribute Table. This table contains, 692 -- one entry per path to a network, path attributes 693 -- received from all peers running BGP-4. 695 bgp4PathAttrTable OBJECT-TYPE 696 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "The BGP-4 Received Path Attribute Table contains 701 information about paths to destination networks 702 received from all BGP4 peers." 703 ::= { bgp 6 } 705 bgp4PathAttrEntry OBJECT-TYPE 706 SYNTAX Bgp4PathAttrEntry 707 MAX-ACCESS not-accessible 708 STATUS current 709 DESCRIPTION 710 "Information about a path to a network." 711 INDEX { bgp4PathAttrIpAddrPrefix, 712 bgp4PathAttrIpAddrPrefixLen, 713 bgp4PathAttrPeer } 714 ::= { bgp4PathAttrTable 1 } 716 Bgp4PathAttrEntry ::= SEQUENCE { 717 bgp4PathAttrPeer 718 IpAddress, 719 bgp4PathAttrIpAddrPrefixLen 720 Integer32, 721 bgp4PathAttrIpAddrPrefix 722 IpAddress, 723 bgp4PathAttrOrigin 724 Integer32, 725 bgp4PathAttrASPathSegment 726 OCTET STRING, 727 bgp4PathAttrNextHop 728 IpAddress, 729 bgp4PathAttrMultiExitDisc 730 Integer32, 731 bgp4PathAttrLocalPref 732 Integer32, 733 bgp4PathAttrAtomicAggregate 734 Integer32, 735 bgp4PathAttrAggregatorAS 736 Integer32, 737 bgp4PathAttrAggregatorAddr 738 IpAddress, 739 bgp4PathAttrCalcLocalPref 740 Integer32, 741 bgp4PathAttrBest 742 Integer32, 743 bgp4PathAttrUnknown 744 OCTET STRING 745 } 747 bgp4PathAttrPeer OBJECT-TYPE 748 SYNTAX IpAddress 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The IP address of the peer where the path 753 information was learned." 754 ::= { bgp4PathAttrEntry 1 } 756 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 757 SYNTAX INTEGER (0..32) 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "Length in bits of the IP address prefix in the 762 Network Layer Reachability Information field." 763 ::= { bgp4PathAttrEntry 2 } 765 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 766 SYNTAX IpAddress 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "An IP address prefix in the Network Layer 771 Reachability Information field. This object 772 is an IP address containing the prefix with 773 length specified by bgp4PathAttrIpAddrPrefixLen. 774 Any bits beyond the length specified by 775 bgp4PathAttrIpAddrPrefixLen are zeroed." 776 ::= { bgp4PathAttrEntry 3 } 778 bgp4PathAttrOrigin OBJECT-TYPE 779 SYNTAX INTEGER { 780 igp(1),-- networks are interior 781 egp(2),-- networks learned via EGP 782 incomplete(3) -- undetermined 783 } 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The ultimate origin of the path information." 788 ::= { bgp4PathAttrEntry 4 } 790 bgp4PathAttrASPathSegment OBJECT-TYPE 791 SYNTAX OCTET STRING (SIZE (0..4096)) 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "The sequence of AS path segments. Each AS 796 path segment is represented by a triple 797 . 799 The type is a 1-octet field which has two 800 possible values: 801 1 AS_SET: unordered set of ASs a 802 route in the UPDATE message 803 has traversed 805 2 AS_SEQUENCE: ordered set of ASs 806 a route in the UPDATE message 807 has traversed. 809 The length is a 1-octet field containing the 810 number of ASs in the value field. 812 The value field contains one or more AS 813 numbers, each AS is represented in the octet 814 string as a pair of octets according to the 815 following algorithm: 817 first-byte-of-pair = ASNumber / 256; 818 second-byte-of-pair = ASNumber & 255;" 819 ::= { bgp4PathAttrEntry 5 } 821 bgp4PathAttrNextHop OBJECT-TYPE 822 SYNTAX IpAddress 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "The address of the border router that should 827 be used for the destination network. This 828 address is the nexthop address received in 829 the UPDATE packet." 830 ::= { bgp4PathAttrEntry 6 } 832 bgp4PathAttrMultiExitDisc OBJECT-TYPE 833 SYNTAX Integer32 (0..4294967295) 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "This metric is used to discriminate between 838 multiple exit points to an adjacent autonomous 839 system. A value of -1 (4294967295) indicates 840 the absence of this attribute. 842 Note that this precludes the representation of 843 the maximum value for this attribute. Previously 844 the variable held only 2^31 bits of information 845 which covered only half the allowed values 846 and reserved -1 for not present." 847 ::= { bgp4PathAttrEntry 7 } 849 bgp4PathAttrLocalPref OBJECT-TYPE 850 SYNTAX Integer32 (0..4294967295) 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The originating BGP4 speaker's degree of 855 preference for an advertised route. A value of 856 -1 (4294967295) indicates the absence of this 857 attribute. 859 Note that this precludes the representation of 860 the maximum value for this attribute. Previously 861 the variable held only 2^31 bits of information 862 which covered only half the allowed values 863 and reserved -1 for not present." 864 ::= { bgp4PathAttrEntry 8 } 866 bgp4PathAttrAtomicAggregate OBJECT-TYPE 867 SYNTAX INTEGER { 868 lessSpecificRouteNotSelected(1), 869 lessSpecificRouteSelected(2) 870 } 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "Whether or not a system has selected 875 a less specific route without selecting a 876 more specific route." 877 ::= { bgp4PathAttrEntry 9 } 879 bgp4PathAttrAggregatorAS OBJECT-TYPE 880 SYNTAX INTEGER (0..65535) 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "The AS number of the last BGP4 speaker that 885 performed route aggregation. A value of zero (0) 886 indicates the absence of this attribute." 887 ::= { bgp4PathAttrEntry 10 } 889 bgp4PathAttrAggregatorAddr OBJECT-TYPE 890 SYNTAX IpAddress 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "The IP address of the last BGP4 speaker that 895 performed route aggregation. A value of 896 0.0.0.0 indicates the absence of this attribute. 897 Note propagation of AS of zero is illegal in 898 internet." 899 ::= { bgp4PathAttrEntry 11 } 901 bgp4PathAttrCalcLocalPref OBJECT-TYPE 902 SYNTAX Integer32 (0..4294967295) 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The degree of preference calculated by the 907 receiving BGP4 speaker for an advertised route. 908 A value of -1 (4294967295) indicates the absence of this 909 attribute. 911 Note that this precludes the representation of 912 the maximum value for this attribute. Previously 913 the variable held only 2^31 bits of information 914 which covered only half the allowed values 915 and reserved -1 for not present." 916 ::= { bgp4PathAttrEntry 12 } 918 bgp4PathAttrBest OBJECT-TYPE 919 SYNTAX Integer32 { 920 false(1),-- not chosen as best route 921 true(2) -- chosen as best route 922 } 923 MAX-ACCESS read-only 924 STATUS current 925 DESCRIPTION 926 "An indication of whether or not this route 927 was chosen as the best BGP4 route." 928 ::= { bgp4PathAttrEntry 13 } 930 bgp4PathAttrUnknown OBJECT-TYPE 931 SYNTAX OCTET STRING (SIZE(0..4096)) 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "One or more path attributes not understood 936 by the base BGP-4 document. 938 Path attributes are recorded in the Update 939 Path attribute format of type, length, value. 940 Size zero (0) indicates the absence of such 941 attribute(s). Octets beyond the maximum size, 942 if any, are not recorded by this object. " 943 ::= { bgp4PathAttrEntry 14 } 945 -- Traps. 947 -- note that in RFC 1657, bgpTraps was incorrectly 948 -- assigned a value of { bgp 7 }, and each of the 949 -- traps had the bgpPeerRemoteAddr object inappropriately 950 -- removed from their OBJECTS clause. The following 951 -- definitions restore the semantics of the traps as 952 -- they were initially defined in RFC 1269. 954 -- { bgp 7 } is unused 956 bgpTraps OBJECT IDENTIFIER ::= { bgp 0 } 958 bgpEstablished NOTIFICATION-TYPE 959 OBJECTS { bgpPeerRemoteAddr, 960 bgpPeerLastError, 961 bgpPeerState } 962 STATUS current 963 DESCRIPTION 964 "The BGP Established event is generated when 965 the BGP FSM enters the ESTABLISHED state." 966 ::= { bgpTraps 1 } 968 bgpBackwardTransition NOTIFICATION-TYPE 969 OBJECTS { bgpPeerRemoteAddr, 970 bgpPeerLastError, 971 bgpPeerState } 972 STATUS current 973 DESCRIPTION 974 "The BGPBackwardTransition Event is generated 975 when the BGP FSM moves from a higher numbered 976 state to a lower numbered state." 977 ::= { bgpTraps 2 } 979 -- conformance information 981 bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 } 982 bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 } 983 bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 } 985 -- compliance statements 987 bgpMIBCompliance MODULE-COMPLIANCE 988 STATUS current 989 DESCRIPTION 990 "The compliance statement for entities which 991 implement the BGP4 mib." 992 MODULE -- this module 993 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 994 bgp4MIBPeerGroup, 995 bgp4MIBPathAttrGroup, 996 bgp4MIBNotificationGroup } 997 ::= { bgpMIBCompliances 1 } 999 -- units of conformance 1001 bgp4MIBGlobalsGroup OBJECT-GROUP 1002 OBJECTS { bgpVersion, 1003 bgpLocalAs, 1004 bgpIdentifier } 1005 STATUS current 1006 DESCRIPTION 1007 "A collection of objects providing information 1008 on global BGP state." 1009 ::= { bgpMIBGroups 1 } 1011 bgp4MIBPeerGroup OBJECT-GROUP 1012 OBJECTS { bgpPeerIdentifier, 1013 bgpPeerState, 1014 bgpPeerAdminStatus, 1015 bgpPeerNegotiatedVersion, 1016 bgpPeerLocalAddr, 1017 bgpPeerLocalPort, 1018 bgpPeerRemoteAddr, 1019 bgpPeerRemotePort, 1020 bgpPeerRemoteAs, 1021 bgpPeerInUpdates, 1022 bgpPeerOutUpdates, 1023 bgpPeerInTotalMessages, 1024 bgpPeerOutTotalMessages, 1025 bgpPeerLastError, 1026 bgpPeerFsmEstablishedTransitions, 1027 bgpPeerFsmEstablishedTime, 1028 bgpPeerConnectRetryInterval, 1029 bgpPeerHoldTime, 1030 bgpPeerKeepAlive, 1031 bgpPeerHoldTimeConfigured, 1032 bgpPeerKeepAliveConfigured, 1033 bgpPeerMinASOriginationInterval, 1034 bgpPeerMinRouteAdvertisementInterval, 1035 bgpPeerInUpdateElapsedTime } 1036 STATUS current 1037 DESCRIPTION 1038 "A collection of objects for managing 1039 BGP peers." 1040 ::= { bgpMIBGroups 2 } 1042 bgp4MIBRcvdPathAttrGroup OBJECT-GROUP 1043 OBJECTS { bgpPathAttrPeer, 1044 bgpPathAttrDestNetwork, 1045 bgpPathAttrOrigin, 1046 bgpPathAttrASPath, 1047 bgpPathAttrNextHop, 1048 bgpPathAttrInterASMetric } 1049 STATUS obsolete 1050 DESCRIPTION 1051 "A collection of objects for managing BGP 1052 path entries. 1054 This conformance group is obsolete, 1055 replaced by bgp4MIBPathAttrGroup." 1056 ::= { bgpMIBGroups 3 } 1058 bgp4MIBPathAttrGroup OBJECT-GROUP 1059 OBJECTS { bgp4PathAttrPeer, 1060 bgp4PathAttrIpAddrPrefixLen, 1061 bgp4PathAttrIpAddrPrefix, 1062 bgp4PathAttrOrigin, 1063 bgp4PathAttrASPathSegment, 1064 bgp4PathAttrNextHop, 1065 bgp4PathAttrMultiExitDisc, 1066 bgp4PathAttrLocalPref, 1067 bgp4PathAttrAtomicAggregate, 1068 bgp4PathAttrAggregatorAS, 1069 bgp4PathAttrAggregatorAddr, 1070 bgp4PathAttrCalcLocalPref, 1071 bgp4PathAttrBest, 1072 bgp4PathAttrUnknown } 1073 STATUS current 1074 DESCRIPTION 1075 "A collection of objects for managing 1076 BGP path entries." 1077 ::= { bgpMIBGroups 4 } 1079 bgp4MIBNotificationGroup NOTIFICATION-GROUP 1080 NOTIFICATIONS { bgpEstablished, 1081 bgpBackwardTransition } 1082 STATUS current 1083 DESCRIPTION 1084 "A collection of notifications for signaling 1085 changes in BGP peer relationships." 1086 ::= { bgpMIBGroups 5 } 1088 END 1090 6. Intellectual Property 1092 The IETF takes no position regarding the validity or scope of any 1093 intellectual property or other rights that might be claimed to 1094 pertain to the implementation or use of the technology described in 1095 this document or the extent to which any license under such rights 1096 might or might not be available; neither does it represent that it 1097 has made any effort to identify any such rights. Information on the 1098 IETF's procedures with respect to rights in standards-track and 1099 standards-related documentation can be found in BCP-11. Copies of 1100 claims of rights made available for publication and any assurances of 1101 licenses to be made available, or the result of an attempt made to 1102 obtain a general license or permission for the use of such 1103 proprietary rights by implementors or users of this specification can 1104 be obtained from the IETF Secretariat. 1106 7. Acknowledgements 1108 We would like to acknowledge the assistance of all the members of the 1109 Inter-Domain Routing Working Group, and particularly the following 1110 individuals: 1112 Yakov Rekhter, cisco Systems 1113 Rob Coltun, Redback 1114 Guy Almes, Internet2 1115 Jeff Honig, Cornell Theory Center 1116 Marshall T. Rose, Dover Beach Consulting, Inc. 1117 Dennis Ferguson, Juniper Networks 1118 Mike Mathis, PSC 1119 John Krawczyk, Bay Networks 1120 Curtis Villamizar, Avici 1121 Dave LeRoy, Pencom Systems 1122 Paul Traina, Juniper Networks 1123 Andrew Partan, MFS 1124 Robert Snyder, cisco Systems 1125 Dimitry Haskin, Nortel 1126 Peder Chr Norgaard, Telebit Communications A/S 1127 Joel Halpern, CTO Longitude Systems, Inc. 1128 Nick Thille, RedBack Networks 1129 Bert Wijnen, IBM 1130 Shane Wright, NextHop 1132 The origin of this document is from RFC 1269 "Definitions of Managed 1133 Objects for the Border Gateway Protocol (Version 3)" written by Steve 1134 Willis and John Burruss, which was updated by John Chu to support 1135 BGP-4 in RFC 1657. The editors wishes to acknowledge the fine work 1136 of these original authors. 1138 8. References 1140 [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC 1141 1771, March 1995. 1143 [2] Rekhter, Y., Gross, P., "Application of the Border Gateway 1144 Protocol in the Internet", RFC 1772, March 1995. 1146 [3] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1147 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1148 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1149 January 1998 1151 [4] Rose, M., and K. McCloghrie, "Structure and Identification of 1152 Management Information for TCP/IP-based Internets", RFC 1155, 1153 Performance Systems International, Hughes LAN Systems, May 1990 1155 [5] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1156 1212, Performance Systems International, Hughes LAN Systems, 1157 March 1991 1159 [6] M. Rose, "A Convention for Defining Traps for use with the 1160 SNMP", RFC 1215, Performance Systems International, March 1991 1162 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1163 "Structure of Management Information for Version 2 of the Simple 1164 Network Management Protocol (SNMPv2)", RFC 1902, SNMP 1165 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, 1166 Inc., International Network Services, January 1996. 1168 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1169 Conventions for Version 2 of the Simple Network Management 1170 Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco 1171 Systems, Inc., Dover Beach Consulting, Inc., International 1172 Network Services, January 1996. 1174 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1175 "Conformance Statements for Version 2 of the Simple Network 1176 Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 1177 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1178 Network Services, January 1996. 1180 [10] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1181 Network Management Protocol", RFC 1157, SNMP Research, 1182 Performance Systems International, Performance Systems 1183 International, MIT Laboratory for Computer Science, May 1990. 1185 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1186 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 1187 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1188 Inc., International Network Services, January 1996. 1190 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1191 "Transport Mappings for Version 2 of the Simple Network 1192 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 1193 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1194 Network Services, January 1996. 1196 [13] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1197 Processing and Dispatching for the Simple Network Management 1198 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron 1199 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1200 January 1998. 1202 [14] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1203 for version 3 of the Simple Network Management Protocol 1204 (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. 1206 [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1207 Operations for Version 2 of the Simple Network Management 1208 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 1209 Systems, Inc., Dover Beach Consulting, Inc., International 1210 Network Services, January 1996. 1212 [16] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1213 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1214 Systems, January 1998 1216 [17] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1217 Control Model (VACM) for the Simple Network Management Protocol 1218 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, 1219 Inc., Cisco Systems, Inc., January 1998 1221 9. Security Considerations 1223 There are a number of management objects defined in this MIB that 1224 have a MAX-ACCESS clause of read-write: 1226 bgpPeerAdminStatus 1227 bgpPeerConnectRetryInterval 1228 bgpPeerHoldTimeConfigured 1229 bgpPeerKeepAliveConfigured 1230 bgpPeerMinASOriginationInterval 1231 bgpPeerMinRouteAdvertisementInterval 1233 These objects should be considered sensitive or vulnerable in most 1234 network environments. The support for SET operations in a non-secure 1235 environment without proper protection can have a negative effect on 1236 network operations. Incorrect configuration of these parameters may 1237 cause BGP peer connections to terminate early or to send more routes 1238 under a flapping condition. 1240 There are a number of managed objects in this MIB that may be 1241 considered to contain sensitive information in the operation of a 1242 network. For example, a BGP peer's local and remote addresses may be 1243 sensitive for ISPs who want to keep interface addresses on routers 1244 confidential to prevent router addresses used for a denial of service 1245 attack or spoofing. 1247 Therefore, it may be important in some environments to control read 1248 access to these objects and possibly to even encrypt the values of 1249 these object when sending them over the network via SNMP. Not all 1250 versions of SNMP provide features for such a secure environment. 1252 SNMPv1 by itself is not a secure environment. Even if the network 1253 itself is secure (for example by using IPSec), even then, there is no 1254 control as to who on the secure network is allowed to access and 1255 GET/SET (read/change/create/delete) the objects in this MIB. 1257 It is recommended that the implementers consider the security 1258 features as provided by the SNMPv3 framework. Specifically, the use 1259 of the User-based Security Model RFC 2274 [14] and the View-based 1260 Access Control Model RFC 2275 [17] is recommended. 1262 It is then a customer/user responsibility to ensure that the SNMP 1263 entity giving access to an instance of this MIB, is properly 1264 configured to give access to the objects only to those principals 1265 (users) that have legitimate rights to indeed GET or SET 1266 (change/create/delete) them. 1268 10. Authors' Address 1270 Susan Hares 1271 NextHop Technologies 1272 517 Williams 1273 Ann Arbor, MI 48103-4943 1274 Phone: +1 734 936 2095 1275 Fax: +1 734 615-3241 1276 Email: skh@nexthop.com 1278 Jeff Johnson 1279 RedBack Networks, Inc. 1280 1389 Moffett Park Drive 1281 Sunnyvale, CA 94089 1282 Phone: +1 408 548 3516 1283 Email: jeff@redback.com 1285 Steve Willis 1286 Argon Networks 1287 25 Porter Road 1288 Littleton, MA 01450 1289 Phone: +1 508 486 0665 1290 Fax: +1 508 486 9379 1291 Email: swills@argon.com 1293 John Burruss 1294 Windata Inc. 1295 543 Great Road 1296 Littleton MA 01460 1297 Phone: +1 508 952 0170 1298 Email: jburruss@windata.com 1300 John Chu 1301 Cosine Communications 1302 1200 Bridge Parkway 1303 Redwood City, CA 94065 1304 Phone: 650-637-4780 1305 Email: jchu@cosinecom.com 1307 11. Full Copyright Statement 1309 Copyright (C) The Internet Society (1999). All Rights Reserved. 1311 This document and translations of it may be copied and furnished to 1312 others, and derivative works that comment on or otherwise explain it 1313 or assist in its implementation may be prepared, copied, published 1314 and distributed, in whole or in part, without restriction of any 1315 kind, provided that the above copyright notice and this paragraph are 1316 included on all such copies and derivative works. However, this 1317 document itself may not be modified in any way, such as by removing 1318 the copyright notice or references to the Internet Society or other 1319 Internet organizations, except as needed for the purpose of 1320 developing Internet standards in which case the procedures for 1321 copyrights defined in the Internet Standards process must be 1322 followed, or as required to translate it into languages other than 1323 English. 1325 The limited permissions granted above are perpetual and will not be 1326 revoked by the Internet Society or its successors or assigns. 1328 This document and the information contained herein is provided on an 1329 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1330 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1331 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1332 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1333 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.