idnits 2.17.1 draft-ietf-idr-bgp4-mib-09.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 -- 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 1 longer page, the longest (page 34) being 60 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 2 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** There are 4 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 "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 1261 has weird spacing: '... There are ...' == Line 1264 has weird spacing: '...terface addre...' == Line 1268 has weird spacing: '...ents to contr...' == Line 1269 has weird spacing: '... access to t...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 2002) is 8077 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: 'BGP' is mentioned on line 72, but not defined == Missing Reference: 'BGPAPPL' is mentioned on line 72, but not defined == Missing Reference: 'REF' is mentioned on line 1280, but not defined == Unused Reference: 'BGP4' is defined on line 1328, but no explicit reference was found in the text == Unused Reference: 'BGP4APP' is defined on line 1331, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1771 (ref. 'BGP4') (Obsoleted by RFC 4271) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 22 errors (**), 0 flaws (~~), 13 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT BGP4-MIB March 2002 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 March 2002 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 "200203010000Z" 153 ORGANIZATION "IETF IDR Working Group" 154 CONTACT-INFO "E-mail: idr@merit.net 156 Jeff Haas, Sue Hares (Editors) 157 825 Victors Way 158 Suite 100 159 Ann Arbor, MI 48108-2738 160 Tel: +1 734 222-1600 161 Fax: +1 734 222-1602 162 E-mail: jhaas@nexthop.com 163 skh@nexthop.com" 165 DESCRIPTION 166 "The MIB module for the BGP-4 protocol. 168 Changes since RFC 1657: 170 1) Fixed the definitions of the traps to 171 make them equivalent to their initial 172 definition in RFC 1269. 173 2) Added compliance and conformance info. 174 3) Updated for latest BGP information 175 draft-ietf-idr-bgp4-17.txt for value of 176 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, 177 bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, 178 bgp4PathAttrASPathSegement. 179 4) Added additional clarification commments where 180 needed. 181 5) Noted where objects do not fully reflect 182 the protocol as Known Issues." 183 ::= { mib-2 15 } 185 bgpVersion OBJECT-TYPE 186 SYNTAX OCTET STRING (SIZE (1..255)) 187 MAX-ACCESS read-only 188 STATUS current 189 DESCRIPTION 190 "Vector of supported BGP protocol version 191 numbers. Each peer negotiates the version 192 from this vector. Versions are identified 193 via the string of bits contained within this 194 object. The first octet contains bits 0 to 195 7, the second octet contains bits 8 to 15, 196 and so on, with the most significant bit 197 referring to the lowest bit number in the 198 octet (e.g., the MSB of the first octet 199 refers to bit 0). If a bit, i, is present 200 and set, then the version (i+1) of the BGP 201 is supported." 202 ::= { bgp 1 } 204 bgpLocalAs OBJECT-TYPE 205 SYNTAX Integer32 (0..65535) 206 MAX-ACCESS read-only 207 STATUS current 208 DESCRIPTION 209 "The local autonomous system number." 210 ::= { bgp 2 } 212 -- BGP Peer table. This table contains, one entry per 213 -- BGP peer, information about the BGP peer. 215 bgpPeerTable OBJECT-TYPE 216 SYNTAX SEQUENCE OF BgpPeerEntry 217 MAX-ACCESS not-accessible 218 STATUS current 219 DESCRIPTION 220 "BGP peer table. This table contains, 221 one entry per BGP peer, information about the 222 connections with BGP peers." 223 ::= { bgp 3 } 225 bgpPeerEntry OBJECT-TYPE 226 SYNTAX BgpPeerEntry 227 MAX-ACCESS not-accessible 228 STATUS current 229 DESCRIPTION 230 "Entry containing information about the 231 connection with a BGP peer." 232 INDEX { bgpPeerRemoteAddr } 233 ::= { bgpPeerTable 1 } 235 BgpPeerEntry ::= SEQUENCE { 236 bgpPeerIdentifier 237 IpAddress, 238 bgpPeerState 239 INTEGER, 240 bgpPeerAdminStatus 241 INTEGER, 242 bgpPeerNegotiatedVersion 243 Integer32, 244 bgpPeerLocalAddr 245 IpAddress, 246 bgpPeerLocalPort 247 Integer32, 248 bgpPeerRemoteAddr 249 IpAddress, 250 bgpPeerRemotePort 251 Integer32, 252 bgpPeerRemoteAs 253 Integer32, 254 bgpPeerInUpdates 255 Counter32, 256 bgpPeerOutUpdates 257 Counter32, 258 bgpPeerInTotalMessages 259 Counter32, 260 bgpPeerOutTotalMessages 261 Counter32, 262 bgpPeerLastError 263 OCTET STRING, 264 bgpPeerFsmEstablishedTransitions 265 Counter32, 266 bgpPeerFsmEstablishedTime 267 Gauge32, 268 bgpPeerConnectRetryInterval 269 Integer32, 270 bgpPeerHoldTime 271 Integer32, 272 bgpPeerKeepAlive 273 Integer32, 274 bgpPeerHoldTimeConfigured 275 Integer32, 277 bgpPeerKeepAliveConfigured 278 Integer32, 279 bgpPeerMinASOriginationInterval 280 Integer32, 281 bgpPeerMinRouteAdvertisementInterval 282 Integer32, 283 bgpPeerInUpdateElapsedTime 284 Gauge32 285 } 287 bgpPeerIdentifier OBJECT-TYPE 288 SYNTAX IpAddress 289 MAX-ACCESS read-only 290 STATUS current 291 DESCRIPTION 292 "The BGP Identifier of this entry's BGP peer. 293 This entry should be 0.0.0.0 unless the 294 bgpPeerState is in the openconfirm or the 295 established state." 296 ::= { bgpPeerEntry 1 } 298 bgpPeerState OBJECT-TYPE 299 SYNTAX INTEGER { 300 idle(1), 301 connect(2), 302 active(3), 303 opensent(4), 304 openconfirm(5), 305 established(6) 306 } 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "The BGP peer connection state." 311 ::= { bgpPeerEntry 2 } 313 bgpPeerAdminStatus OBJECT-TYPE 314 SYNTAX INTEGER { 315 stop(1), 316 start(2) 317 } 318 MAX-ACCESS read-write 319 STATUS current 320 DESCRIPTION 321 "The desired state of the BGP connection. 323 A transition from 'stop' to 'start' will 324 cause the BGP Start Event to be generated. 325 A transition from 'start' to 'stop' will 326 cause the BGP Stop Event to be generated. 327 This parameter can be used to restart BGP 328 peer connections. Care should be used in 329 providing write access to this object 330 without adequate authentication." 331 ::= { bgpPeerEntry 3 } 333 bgpPeerNegotiatedVersion OBJECT-TYPE 334 SYNTAX Integer32 (0..255) 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "The negotiated version of BGP running between 339 the two peers. 341 This entry should be zero (0) unless the 342 bgpPeerState is in the openconfirm or the 343 established state." 344 ::= { bgpPeerEntry 4 } 346 bgpPeerLocalAddr OBJECT-TYPE 347 SYNTAX IpAddress 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The local IP address of this entry's BGP 352 connection." 353 ::= { bgpPeerEntry 5 } 355 bgpPeerLocalPort OBJECT-TYPE 356 SYNTAX Integer32 (0..65535) 357 MAX-ACCESS read-only 358 STATUS current 359 DESCRIPTION 360 "The local port for the TCP connection between 361 the BGP peers." 362 ::= { bgpPeerEntry 6 } 364 bgpPeerRemoteAddr OBJECT-TYPE 365 SYNTAX IpAddress 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "The remote IP address of this entry's BGP 370 peer." 371 ::= { bgpPeerEntry 7 } 373 bgpPeerRemotePort OBJECT-TYPE 374 SYNTAX Integer32 (0..65535) 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The remote port for the TCP connection 379 between the BGP peers. Note that the 380 objects bgpPeerLocalAddr, 381 bgpPeerLocalPort, bgpPeerRemoteAddr and 382 bgpPeerRemotePort provide the appropriate 383 reference to the standard MIB TCP 384 connection table." 385 ::= { bgpPeerEntry 8 } 387 bgpPeerRemoteAs OBJECT-TYPE 388 SYNTAX Integer32 (0..65535) 389 MAX-ACCESS read-only 390 STATUS current 391 DESCRIPTION 392 "The remote autonomous system number." 393 ::= { bgpPeerEntry 9 } 395 bgpPeerInUpdates OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The number of BGP UPDATE messages 401 received on this connection. This object 402 should be initialized to zero (0) when the 403 connection is established. The value of this 404 object, when not in the established state, 405 is undefined." 406 ::= { bgpPeerEntry 10 } 408 bgpPeerOutUpdates OBJECT-TYPE 409 SYNTAX Counter32 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The number of BGP UPDATE messages 414 transmitted on this connection. This 415 object should be initialized to zero (0) 416 when the connection is established. The 417 value of this object, when not in the 418 established state, is undefined." 419 ::= { bgpPeerEntry 11 } 421 bgpPeerInTotalMessages OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The total number of messages received 427 from the remote peer on this connection. 428 This object should be initialized to zero 429 when the connection is established. The 430 value of this object, when not in the 431 established state, is undefined." 432 ::= { bgpPeerEntry 12 } 434 bgpPeerOutTotalMessages OBJECT-TYPE 435 SYNTAX Counter32 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The total number of messages transmitted to 440 the remote peer on this connection. This 441 object should be initialized to zero when 442 the connection is established. The 443 value of this object, when not in the 444 established state, is undefined." 445 ::= { bgpPeerEntry 13 } 447 bgpPeerLastError OBJECT-TYPE 448 SYNTAX OCTET STRING (SIZE (2)) 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The last error code and subcode seen by this 453 peer on this connection. If no error has 454 occurred, this field is zero. Otherwise, the 455 first byte of this two byte OCTET STRING 456 contains the error code, and the second byte 457 contains the subcode." 458 ::= { bgpPeerEntry 14 } 460 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 461 SYNTAX Counter32 462 MAX-ACCESS read-only 463 STATUS current 464 DESCRIPTION 465 "The total number of times the BGP FSM 466 transitioned into the established state 467 for this peer." 468 ::= { bgpPeerEntry 15 } 470 bgpPeerFsmEstablishedTime OBJECT-TYPE 471 SYNTAX Gauge32 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "This timer indicates how long (in 476 seconds) this peer has been in the 477 established state or how long 478 since this peer was last in the 479 established state. It is set to zero when 480 a new peer is configured or the router is 481 booted." 482 ::= { bgpPeerEntry 16 } 484 bgpPeerConnectRetryInterval OBJECT-TYPE 485 SYNTAX Integer32 (1..65535) 486 MAX-ACCESS read-write 487 STATUS current 488 DESCRIPTION 489 "Time interval in seconds for the 490 ConnectRetry timer. The suggested value 491 for this timer is 120 seconds." 492 ::= { bgpPeerEntry 17 } 494 bgpPeerHoldTime OBJECT-TYPE 495 SYNTAX Integer32 ( 0 | 3..65535 ) 496 MAX-ACCESS read-only 497 STATUS current 498 DESCRIPTION 499 "Time interval in seconds for the Hold 500 Timer established with the peer. The 501 value of this object is calculated by this 502 BGP speaker by using the smaller of the 503 value in bgpPeerHoldTimeConfigured and the 504 Hold Time received in the OPEN message. 505 This value must be at lease three seconds 506 if it is not zero (0). If the value is 507 zero (0), the Hold Timer has either not been 508 established with the peer, or, the value of 509 bgpPeerHoldTimeConfigured is zero (0)." 510 ::= { bgpPeerEntry 18 } 512 bgpPeerKeepAlive OBJECT-TYPE 513 SYNTAX Integer32 ( 0 | 1..21845 ) 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "Time interval in seconds for the KeepAlive 518 timer established with the peer. The value 519 of this object is calculated by this BGP 520 speaker such that, when compared with 521 bgpPeerHoldTime, it has the same proportion 522 as what bgpPeerKeepAliveConfigured has when 523 compared with bgpPeerHoldTimeConfigured. If 524 the value of this object is zero (0), it 525 indicates that the KeepAlive timer has not 526 been established with the peer, or, the value 527 of bgpPeerKeepAliveConfigured is zero (0)." 528 ::= { bgpPeerEntry 19 } 530 bgpPeerHoldTimeConfigured OBJECT-TYPE 531 SYNTAX Integer32 ( 0 | 3..65535 ) 532 MAX-ACCESS read-write 533 STATUS current 534 DESCRIPTION 535 "Time interval in seconds for the Hold Time 536 configured for this BGP speaker with this 537 peer. This value is placed in an OPEN 538 message sent to this peer by this BGP 539 speaker, and is compared with the Hold 540 Time field in an OPEN message received 541 from the peer when determining the Hold 542 Time (bgpPeerHoldTime) with the peer. 543 This value must not be less than three 544 seconds if it is not zero (0) in which 545 case the Hold Time is NOT to be 546 established with the peer. The suggested 547 value for this timer is 90 seconds." 548 ::= { bgpPeerEntry 20 } 550 bgpPeerKeepAliveConfigured OBJECT-TYPE 551 SYNTAX Integer32 ( 0 | 1..21845 ) 552 MAX-ACCESS read-write 553 STATUS current 554 DESCRIPTION 555 "Time interval in seconds for the 556 KeepAlive timer configured for this BGP 557 speaker with this peer. The value of this 558 object will only determine the 559 KEEPALIVE messages' frequency relative to 560 the value specified in 561 bgpPeerHoldTimeConfigured; the actual 562 time interval for the KEEPALIVE messages is 563 indicated by bgpPeerKeepAlive. A 564 reasonable maximum value for this timer 565 would be configured to be one 566 third of that of 567 bgpPeerHoldTimeConfigured. 568 If the value of this object is zero (0), 569 no periodical KEEPALIVE messages are sent 570 to the peer after the BGP connection has 571 been established. The suggested value for 572 this timer is 30 seconds." 573 ::= { bgpPeerEntry 21 } 575 bgpPeerMinASOriginationInterval OBJECT-TYPE 576 SYNTAX Integer32 (1..65535) 577 MAX-ACCESS read-write 578 STATUS current 579 DESCRIPTION 580 "Time interval in seconds for the 581 MinASOriginationInterval timer. 582 The suggested value for this timer is 15 583 seconds." 584 ::= { bgpPeerEntry 22 } 586 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 587 SYNTAX Integer32 (1..65535) 588 MAX-ACCESS read-write 589 STATUS current 590 DESCRIPTION 591 "Time interval in seconds for the 592 MinRouteAdvertisementInterval timer. 593 The suggested value for this timer is 30 594 seconds." 595 ::= { bgpPeerEntry 23 } 597 bgpPeerInUpdateElapsedTime OBJECT-TYPE 598 SYNTAX Gauge32 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "Elapsed time in seconds since the last BGP 603 UPDATE message was received from the peer. 604 Each time bgpPeerInUpdates is incremented, 605 the value of this object is set to zero (0)." 606 ::= { bgpPeerEntry 24 } 608 bgpIdentifier OBJECT-TYPE 609 SYNTAX IpAddress 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The BGP Identifier of local system." 614 ::= { bgp 4 } 616 -- Received Path Attribute Table. This table contains, 617 -- one entry per path to a network, path attributes 618 -- received from all peers running BGP version 3 or less. 619 -- This table is obsolete, having been replaced in 620 -- functionality with the bgp4PathAttrTable. 622 bgpRcvdPathAttrTable OBJECT-TYPE 623 SYNTAX SEQUENCE OF BgpPathAttrEntry 624 MAX-ACCESS not-accessible 625 STATUS obsolete 626 DESCRIPTION 627 "The BGP Received Path Attribute Table 628 contains information about paths to 629 destination networks received from all 630 peers running BGP version 3 or less." 631 ::= { bgp 5 } 633 bgpPathAttrEntry OBJECT-TYPE 634 SYNTAX BgpPathAttrEntry 635 MAX-ACCESS not-accessible 636 STATUS obsolete 637 DESCRIPTION 638 "Information about a path to a network." 639 INDEX { bgpPathAttrDestNetwork, 640 bgpPathAttrPeer } 641 ::= { bgpRcvdPathAttrTable 1 } 643 BgpPathAttrEntry ::= SEQUENCE { 644 bgpPathAttrPeer 645 IpAddress, 646 bgpPathAttrDestNetwork 647 IpAddress, 648 bgpPathAttrOrigin 649 INTEGER, 650 bgpPathAttrASPath 651 OCTET STRING, 652 bgpPathAttrNextHop 653 IpAddress, 654 bgpPathAttrInterASMetric 655 Integer32 656 } 658 bgpPathAttrPeer OBJECT-TYPE 659 SYNTAX IpAddress 660 MAX-ACCESS read-only 661 STATUS obsolete 662 DESCRIPTION 663 "The IP address of the peer where the path 664 information was learned." 665 ::= { bgpPathAttrEntry 1 } 667 bgpPathAttrDestNetwork OBJECT-TYPE 668 SYNTAX IpAddress 669 MAX-ACCESS read-only 670 STATUS obsolete 671 DESCRIPTION 672 "The address of the destination network." 673 ::= { bgpPathAttrEntry 2 } 675 bgpPathAttrOrigin OBJECT-TYPE 676 SYNTAX INTEGER { 677 igp(1),-- networks are interior 678 egp(2),-- networks learned via the 679 -- EGP protocol 680 incomplete(3) -- networks that 681 -- are learned by some other 682 -- means 683 } 684 MAX-ACCESS read-only 685 STATUS obsolete 686 DESCRIPTION 687 "The ultimate origin of the path information." 688 ::= { bgpPathAttrEntry 3 } 690 bgpPathAttrASPath OBJECT-TYPE 691 SYNTAX OCTET STRING (SIZE (2..255)) 692 MAX-ACCESS read-only 693 STATUS obsolete 694 DESCRIPTION 695 "The set of ASs that must be traversed to reach 696 the network. This object is probably best 697 represented as SEQUENCE OF INTEGER. For SMI 698 compatibility, though, it is represented as 699 OCTET STRING. Each AS is represented as a pair 700 of octets according to the following algorithm: 702 first-byte-of-pair = ASNumber / 256; 703 second-byte-of-pair = ASNumber & 255;" 704 ::= { bgpPathAttrEntry 4 } 706 bgpPathAttrNextHop OBJECT-TYPE 707 SYNTAX IpAddress 708 MAX-ACCESS read-only 709 STATUS obsolete 710 DESCRIPTION 711 "The address of the border router that should 712 be used for the destination network." 713 ::= { bgpPathAttrEntry 5 } 715 bgpPathAttrInterASMetric OBJECT-TYPE 716 SYNTAX Integer32 717 MAX-ACCESS read-only 718 STATUS obsolete 719 DESCRIPTION 720 "The optional inter-AS metric. If this 721 attribute has not been provided for this route, 722 the value for this object is 0." 724 ::= { bgpPathAttrEntry 6 } 726 -- BGP-4 Received Path Attribute Table. This table 727 -- contains, one entry per path to a network, path 728 -- attributes received from all peers running BGP-4. 730 bgp4PathAttrTable OBJECT-TYPE 731 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 732 MAX-ACCESS not-accessible 733 STATUS current 734 DESCRIPTION 735 "The BGP-4 Received Path Attribute Table 736 contains information about paths to 737 destination networks received from all 738 BGP4 peers." 739 ::= { bgp 6 } 741 bgp4PathAttrEntry OBJECT-TYPE 742 SYNTAX Bgp4PathAttrEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "Information about a path to a network." 747 INDEX { bgp4PathAttrIpAddrPrefix, 748 bgp4PathAttrIpAddrPrefixLen, 749 bgp4PathAttrPeer } 750 ::= { bgp4PathAttrTable 1 } 752 Bgp4PathAttrEntry ::= SEQUENCE { 753 bgp4PathAttrPeer 754 IpAddress, 755 bgp4PathAttrIpAddrPrefixLen 756 Integer32, 757 bgp4PathAttrIpAddrPrefix 758 IpAddress, 759 bgp4PathAttrOrigin 760 INTEGER, 761 bgp4PathAttrASPathSegment 762 OCTET STRING, 763 bgp4PathAttrNextHop 764 IpAddress, 765 bgp4PathAttrMultiExitDisc 766 Integer32, 768 bgp4PathAttrLocalPref 769 Integer32, 770 bgp4PathAttrAtomicAggregate 771 INTEGER, 772 bgp4PathAttrAggregatorAS 773 Integer32, 774 bgp4PathAttrAggregatorAddr 775 IpAddress, 776 bgp4PathAttrCalcLocalPref 777 Integer32, 778 bgp4PathAttrBest 779 INTEGER, 780 bgp4PathAttrUnknown 781 OCTET STRING 782 } 784 bgp4PathAttrPeer OBJECT-TYPE 785 SYNTAX IpAddress 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "The IP address of the peer where the path 790 information was learned." 791 ::= { bgp4PathAttrEntry 1 } 793 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 794 SYNTAX Integer32 (0..32) 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "Length in bits of the IP address prefix in 799 the Network Layer Reachability 800 Information field." 801 ::= { bgp4PathAttrEntry 2 } 803 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 804 SYNTAX IpAddress 805 MAX-ACCESS read-only 806 STATUS current 807 DESCRIPTION 808 "An IP address prefix in the Network Layer 809 Reachability Information field. This object 810 is an IP address containing the prefix with 811 length specified by 812 bgp4PathAttrIpAddrPrefixLen. 814 Any bits beyond the length specified by 815 bgp4PathAttrIpAddrPrefixLen are zeroed." 816 ::= { bgp4PathAttrEntry 3 } 818 bgp4PathAttrOrigin OBJECT-TYPE 819 SYNTAX INTEGER { 820 igp(1),-- networks are interior 821 egp(2),-- networks learned via the 822 -- EGP protocol 823 incomplete(3) -- networks that 824 -- are learned by some other 825 -- means 826 } 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "The ultimate origin of the path 831 information." 832 ::= { bgp4PathAttrEntry 4 } 834 bgp4PathAttrASPathSegment OBJECT-TYPE 835 SYNTAX OCTET STRING (SIZE (2..255)) 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The sequence of AS path segments. Each AS 840 path segment is represented by a triple 841 . 843 The type is a 1-octet field which has two 844 possible values: 845 1 AS_SET: unordered set of ASs a 846 route in the UPDATE message 847 has traversed 849 2 AS_SEQUENCE: ordered set of ASs 850 a route in the UPDATE message 851 has traversed. 853 The length is a 1-octet field containing the 854 number of ASs in the value field. 856 The value field contains one or more AS 857 numbers, each AS is represented in the octet 858 string as a pair of octets according to the 859 following algorithm: 861 first-byte-of-pair = ASNumber / 256; 862 second-byte-of-pair = ASNumber & 255; 864 Known Issues: 865 o BGP Confederations will result in 866 a type of value of either 3 or 4. 867 o An AS Path may be longer than 255 octets. 868 This may result in this object containing 869 a truncated AS Path." 870 ::= { bgp4PathAttrEntry 5 } 872 bgp4PathAttrNextHop OBJECT-TYPE 873 SYNTAX IpAddress 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "The address of the border router that 878 should be used for the destination 879 network. This address is the nexthop 880 address received in the UPDATE packet." 881 ::= { bgp4PathAttrEntry 6 } 883 bgp4PathAttrMultiExitDisc OBJECT-TYPE 884 SYNTAX Integer32 (-1..2147483647) 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "This metric is used to discriminate 889 between multiple exit points to an 890 adjacent autonomous system. A value of -1 891 indicates the absence of this attribute. 893 Known Issues: 894 o The BGP-4 specification uses an 895 unsigned 32 bit number and thus this 896 object cannot represent the full 897 range of the protocol." 898 ::= { bgp4PathAttrEntry 7 } 900 bgp4PathAttrLocalPref OBJECT-TYPE 901 SYNTAX Integer32 (-1..2147483647) 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "The originating BGP4 speaker's degree of 906 preference for an advertised route. A 907 value of -1 indicates the absence of this 908 attribute. 910 Known Issues: 911 o The BGP-4 specification uses an 912 unsigned 32 bit number and thus this 913 object cannot represent the full 914 range of the protocol." 915 ::= { bgp4PathAttrEntry 8 } 917 bgp4PathAttrAtomicAggregate OBJECT-TYPE 918 SYNTAX INTEGER { 919 lessSpecificRouteNotSelected(1), 920 lessSpecificRouteSelected(2) 921 } 922 MAX-ACCESS read-only 923 STATUS current 924 DESCRIPTION 925 "Whether or not a system has selected 926 a less specific route without 927 selecting a more specific route." 928 ::= { bgp4PathAttrEntry 9 } 930 bgp4PathAttrAggregatorAS OBJECT-TYPE 931 SYNTAX Integer32 (0..65535) 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "The AS number of the last BGP4 speaker that 936 performed route aggregation. A value of 937 zero (0) indicates the absence of this 938 attribute." 939 ::= { bgp4PathAttrEntry 10 } 941 bgp4PathAttrAggregatorAddr OBJECT-TYPE 942 SYNTAX IpAddress 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "The IP address of the last BGP4 speaker 947 that performed route aggregation. A 948 value of 0.0.0.0 indicates the absence 949 of this attribute. 951 Note propagation of AS of zero is illegal in 952 the Internet." 953 ::= { bgp4PathAttrEntry 11 } 955 bgp4PathAttrCalcLocalPref OBJECT-TYPE 956 SYNTAX Integer32 (-1..2147483647) 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "The degree of preference calculated by the 961 receiving BGP4 speaker for an advertised 962 route. A value of -1 indicates the 963 absence of this attribute. 965 Known Issues: 966 o The BGP-4 specification uses an 967 unsigned 32 bit number and thus this 968 object cannot represent the full 969 range of the protocol." 970 ::= { bgp4PathAttrEntry 12 } 972 bgp4PathAttrBest OBJECT-TYPE 973 SYNTAX INTEGER { 974 false(1),-- not chosen as best route 975 true(2) -- chosen as best route 976 } 977 MAX-ACCESS read-only 978 STATUS current 979 DESCRIPTION 980 "An indication of whether or not this route 981 was chosen as the best BGP4 route for this 982 destination." 983 ::= { bgp4PathAttrEntry 13 } 985 bgp4PathAttrUnknown OBJECT-TYPE 986 SYNTAX OCTET STRING (SIZE(0..255)) 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "One or more path attributes not understood 991 this BGP4 speaker. 993 Path attributes are recorded in the Update Path 994 attribute format of type, length, value. 996 Size zero (0) indicates the absence of such 997 attributes. 999 Octets beyond the maximum size, if any, are not 1000 recorded by this object. 1002 Known Issues: 1003 o Attributes understood by this speaker, but not 1004 represented in this MIB, are unavailable to 1005 the agent." 1006 ::= { bgp4PathAttrEntry 14 } 1008 -- Traps. 1010 -- note that in RFC 1657, bgpTraps was incorrectly 1011 -- assigned a value of { bgp 7 }, and each of the 1012 -- traps had the bgpPeerRemoteAddr object inappropriately 1013 -- removed from their OBJECTS clause. The following 1014 -- definitions restore the semantics of the traps as 1015 -- they were initially defined in RFC 1269. 1017 bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } 1019 bgpEstablishedNotification NOTIFICATION-TYPE 1020 OBJECTS { bgpPeerRemoteAddr, 1021 bgpPeerLastError, 1022 bgpPeerState } 1023 STATUS current 1024 DESCRIPTION 1025 "The BGP Established event is generated when 1026 the BGP FSM enters the ESTABLISHED state. 1028 This object obsoletes bgpEstablished." 1029 ::= { bgpNotification 1 } 1031 bgpBackwardTransNotification NOTIFICATION-TYPE 1032 OBJECTS { bgpPeerRemoteAddr, 1033 bgpPeerLastError, 1034 bgpPeerState } 1035 STATUS current 1036 DESCRIPTION 1037 "The BGPBackwardTransNotification Event is 1038 generated when the BGP FSM moves from a higher 1039 numbered state to a lower numbered state. 1041 This object obsoletes bgpBackwardsTransition." 1042 ::= { bgpNotification 2 } 1044 -- { bgp 7 } is obsoleted 1046 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } 1048 bgpEstablished NOTIFICATION-TYPE 1049 OBJECTS { bgpPeerRemoteAddr, 1050 bgpPeerLastError, 1051 bgpPeerState } 1052 STATUS obsolete 1053 DESCRIPTION 1054 "The BGP Established event is generated when 1055 the BGP FSM enters the ESTABLISHED state. 1057 This object has been obsoleted in favor of 1058 bgpEstablishedNotification." 1059 ::= { bgpTraps 1 } 1061 bgpBackwardTransition NOTIFICATION-TYPE 1062 OBJECTS { bgpPeerRemoteAddr, 1063 bgpPeerLastError, 1064 bgpPeerState } 1065 STATUS current 1066 DESCRIPTION 1067 "The BGPBackwardTransition Event is generated 1068 when the BGP FSM moves from a higher numbered 1069 state to a lower numbered state. 1071 This object has been obsoleted in favor of 1072 bgpBackwardTransNotification." 1073 ::= { bgpTraps 2 } 1075 -- conformance information 1077 bgpMIBConformance OBJECT IDENTIFIER 1078 ::= { bgp 8 } 1079 bgpMIBCompliances OBJECT IDENTIFIER 1080 ::= { bgpMIBConformance 1 } 1082 bgpMIBGroups OBJECT IDENTIFIER 1083 ::= { bgpMIBConformance 2 } 1085 -- compliance statements 1087 bgpMIBCompliance MODULE-COMPLIANCE 1088 STATUS current 1089 DESCRIPTION 1090 "The compliance statement for entities which 1091 implement the BGP4 mib." 1092 MODULE -- this module 1093 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 1094 bgp4MIBPeerGroup, 1095 bgp4MIBPathAttrGroup, 1096 bgp4MIBNotificationGroup, 1097 bgp4MIBNewNotificationGroup } 1098 ::= { bgpMIBCompliances 1 } 1100 -- units of conformance 1102 bgp4MIBGlobalsGroup OBJECT-GROUP 1103 OBJECTS { bgpVersion, 1104 bgpLocalAs, 1105 bgpIdentifier } 1106 STATUS current 1107 DESCRIPTION 1108 "A collection of objects providing 1109 information on global BGP state." 1110 ::= { bgpMIBGroups 1 } 1112 bgp4MIBPeerGroup OBJECT-GROUP 1113 OBJECTS { bgpPeerIdentifier, 1114 bgpPeerState, 1115 bgpPeerAdminStatus, 1116 bgpPeerNegotiatedVersion, 1117 bgpPeerLocalAddr, 1118 bgpPeerLocalPort, 1119 bgpPeerRemoteAddr, 1120 bgpPeerRemotePort, 1121 bgpPeerRemoteAs, 1122 bgpPeerInUpdates, 1123 bgpPeerOutUpdates, 1124 bgpPeerInTotalMessages, 1125 bgpPeerOutTotalMessages, 1126 bgpPeerLastError, 1127 bgpPeerFsmEstablishedTransitions, 1128 bgpPeerFsmEstablishedTime, 1129 bgpPeerConnectRetryInterval, 1130 bgpPeerHoldTime, 1131 bgpPeerKeepAlive, 1132 bgpPeerHoldTimeConfigured, 1133 bgpPeerKeepAliveConfigured, 1134 bgpPeerMinASOriginationInterval, 1135 bgpPeerMinRouteAdvertisementInterval, 1136 bgpPeerInUpdateElapsedTime } 1137 STATUS current 1138 DESCRIPTION 1139 "A collection of objects for managing 1140 BGP peers." 1141 ::= { bgpMIBGroups 2 } 1143 bgp4MIBRcvdPathAttrGroup OBJECT-GROUP 1144 OBJECTS { bgpPathAttrPeer, 1145 bgpPathAttrDestNetwork, 1146 bgpPathAttrOrigin, 1147 bgpPathAttrASPath, 1148 bgpPathAttrNextHop, 1149 bgpPathAttrInterASMetric } 1150 STATUS obsolete 1151 DESCRIPTION 1152 "A collection of objects for managing BGP 1153 path entries. 1155 This conformance group is obsolete, 1156 replaced by bgp4MIBPathAttrGroup." 1157 ::= { bgpMIBGroups 3 } 1159 bgp4MIBPathAttrGroup OBJECT-GROUP 1160 OBJECTS { bgp4PathAttrPeer, 1161 bgp4PathAttrIpAddrPrefixLen, 1162 bgp4PathAttrIpAddrPrefix, 1163 bgp4PathAttrOrigin, 1164 bgp4PathAttrASPathSegment, 1165 bgp4PathAttrNextHop, 1166 bgp4PathAttrMultiExitDisc, 1167 bgp4PathAttrLocalPref, 1168 bgp4PathAttrAtomicAggregate, 1169 bgp4PathAttrAggregatorAS, 1170 bgp4PathAttrAggregatorAddr, 1171 bgp4PathAttrCalcLocalPref, 1172 bgp4PathAttrBest, 1173 bgp4PathAttrUnknown } 1174 STATUS current 1175 DESCRIPTION 1176 "A collection of objects for managing 1177 BGP path entries." 1178 ::= { bgpMIBGroups 4 } 1180 bgp4MIBNotificationGroup NOTIFICATION-GROUP 1181 NOTIFICATIONS { bgpEstablished, 1182 bgpBackwardTransition } 1183 STATUS obsolete 1184 DESCRIPTION 1185 "A collection of notifications for signaling 1186 changes in BGP peer relationships. 1188 Obsoleted by bgp4MIBNewNotificationGroup" 1189 ::= { bgpMIBGroups 5 } 1191 bgp4MIBNewNotificationGroup NOTIFICATION-GROUP 1192 NOTIFICATIONS { bgpEstablishedNotification, 1193 bgpBackwardTransNotification } 1194 STATUS current 1195 DESCRIPTION 1196 "A collection of notifications for signaling 1197 changes in BGP peer relationships. 1199 Obsoletes bgp4MIBNotificationGroup." 1200 ::= { bgpMIBGroups 6 } 1202 END 1204 8. Intellectual Property 1206 The IETF takes no position regarding the validity or scope of any 1207 intellectual property or other rights that might be claimed to 1208 pertain to the implementation or use of the technology described in 1209 this document or the extent to which any license under such rights 1210 might or might not be available; neither does it represent that it 1211 has made any effort to identify any such rights. Information on the 1212 IETF's procedures with respect to rights in standards-track and 1213 standards-related documentation can be found in BCP-11. Copies of 1214 claims of rights made available for publication and any assurances of 1215 licenses to be made available, or the result of an attempt made to 1216 obtain a general license or permission for the use of such 1217 proprietary rights by implementors or users of this specification can 1218 be obtained from the IETF Secretariat. 1220 9. Security Considerations 1222 This MIB relates to a system providing inter-domain routing. As 1223 such, improper manipulation of the objects represented by this MIB 1224 may result in denial of service to a large number of end-users. 1226 There are several management objects defined in this MIB that have a 1227 MAX-ACCESS clause of read-write and/or read-create. Such objects 1228 should be considered sensitive or vulnerable in most network 1229 environments. The support for SET operations in a non-secure 1230 environment without proper protection can have a negative effect on 1231 network operations. These objects include: 1233 +o bgpPeerAdminStatus 1235 Improper change of bgpPeerAdminStatus from start to stop can 1236 cause significant disruption of the connectivity to those 1237 portions of the Internet reached via the applicable remote BGP 1238 peer. 1240 +o bgpPeerConnectRetryInterval 1242 Improper change of this object can cause connections to be 1243 disrupted for extremely long time periods when otherwise they 1244 would be restored in a relatively short period of time. 1246 +o bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured 1248 Misconfiguration of thse objects can make BGP sessions more 1249 fragile and less resilient to denial of service attacks on the 1250 inter-domain routing system. 1252 +o bgpPeerMinASOriginationInterval, 1253 bgpPeerMinRouteAdvertisementInterval 1255 Misconfiguration of these objects may adversely affect global 1256 Internet convergence of the routes advertised by this BGP 1257 speaker. This may result in long-lived routing loops and 1258 blackholes for the portions of the Internet that utilize these 1259 routes." 1261 There are a number of managed objects in this MIB that 1262 contain sensitive information regarding the operation of a network. 1263 For example, a BGP peer's local and remote addresses might be 1264 sensitive for ISPs who want to keep interface addresses on routers 1265 confidential to prevent router addresses used for a denial of service 1266 attack or spoofing. 1268 Therefore, it is important in most environments to control read 1269 access to these objects and possibly to even encrypt the values of 1270 these object when sending them over the network via SNMP. 1272 SNMPv1 by itself is not a secure environment. Even if the network 1273 itself is secure (for example by using IPSec), there is still no 1274 control as to who on the secure network is allowed to access and 1275 GET/SET (read/change/create/delete) the objects in this MIB. 1277 It is recommended that the implementers consider the security 1278 features as provided by the SNMPv3 framework.[REF] Specifically, the 1279 implementation and use of the User-based Security Model [REF] and the 1280 View-based Access Control Model [REF] is recommended to provide 1281 appropriate security controls. 1283 It is then an operator/user responsibility to ensure that the SNMP 1284 entity giving access to an instance of this MIB, is properly 1285 configured to give access to the objects only to those principals 1286 (users) that have legitimate rights to indeed GET or SET 1287 (change/create/delete) them. 1289 10. Acknowledgements 1291 We would like to acknowledge the assistance of all the members of the 1292 Inter-Domain Routing Working Group, and particularly the following 1293 individuals: 1295 Yakov Rekhter, Juniper Networks 1296 Rob Coltun, Redback 1297 Guy Almes, Internet2 1298 Jeff Honig, BSDi 1299 Marshall T. Rose, Dover Beach Consulting, Inc. 1300 Dennis Ferguson, Juniper Networks 1301 Mike Mathis, PSC 1302 John Krawczyk, Bay Networks 1303 Curtis Villamizar, Avici 1304 Dave LeRoy, Pencom Systems 1305 Paul Traina, Juniper Networks 1306 Andrew Partan, MFN 1307 Robert Snyder, cisco Systems 1308 Dimitry Haskin, Nortel 1309 Peder Chr Norgaard, Telebit Communications A/S 1310 Joel Halpern, CTO Longitude Systems, Inc. 1311 Nick Thille, RedBack Networks 1312 Bert Wijnen, Lucent 1313 Shane Wright, NextHop 1314 Mike McFadden, Riverstone Networks, Inc. 1315 Jon Saperia, JDS Consulting, Inc. 1316 Wayne Tackabury, Gold Wire Technology, Inc. 1317 Bill Fenner, AT&T Research 1318 RJ Atkinson, Extreme Networks 1320 The origin of this document is from RFC 1269 "Definitions of Managed 1321 Objects for the Border Gateway Protocol (Version 3)" written by Steve 1322 Willis and John Burruss, which was updated by John Chu to support 1323 BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of 1324 these original authors. 1326 11. References 1328 [BGP4] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC 1329 1771, March 1995. 1331 [BGP4APP] Rekhter, Y., Gross, P., "Application of the Border Gateway 1332 Protocol in the Internet", RFC 1772, March 1995. 1334 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1335 for Describing SNMP Management Frameworks", RFC 2571, April 1336 1999. 1338 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1339 of Management Information for TCP/IP-based Internets", STD 1340 16, RFC 1155, May 1990. 1342 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1343 16, RFC 1212, March 1991. 1345 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1346 SNMP", RFC 1215, March 1991. 1348 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1349 Rose, M., and S. Waldbusser, "Structure of Management 1350 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1351 1999. 1353 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1354 Rose, M., and S. Waldbusser, "Textual Conventions for 1355 SMIv2", STD 58, RFC 2579, April 1999. 1357 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1358 Rose, M., and S. Waldbusser, "Conformance Statements for 1359 SMIv2", STD 58, RFC 2580, April 1999. 1361 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1362 Network Management Protocol", STD 15, RFC 1157, May 1990. 1364 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1365 "Introduction to Community-based SNMPv2", RFC 1901, January 1366 1996. 1368 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1369 "Transport Mappings for Version 2 of the Simple Network 1370 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1372 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1373 Processing and Dispatching for the Simple Network Management 1374 Protocol (SNMP)", RFC 2572, April 1999. 1376 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1377 (USM) for version 3 of the Simple Network Management 1378 Protocol (SNMPv3)", RFC 2574, April 1999. 1380 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1381 "Protocol Operations for Version 2 of the Simple Network 1382 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1384 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1385 RFC 2573, April 1999. 1387 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1388 Access Control Model (VACM) for the Simple Network 1389 Management Protocol (SNMP)", RFC 2575, April 1999. 1391 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1392 "Introduction to Version 3 of the Internet-standard Network 1393 Management Framework", RFC 2570, April 1999. 1395 12. Editors Address 1397 Jeff Haas, Sue Hares 1398 NextHop Technologies 1399 825 Victor's Way, Suite 100 1400 Ann Arbor, MI 48103 1401 Phone: +1 734 222-1600 1402 Fax: +1 734 222-1602 1403 Email: jhaas@nexthop.com 1404 skh@nexthop.com 1406 13. Full Copyright Statement 1408 Copyright (C) The Internet Society (1999). All Rights Reserved. 1410 This document and translations of it may be copied and furnished to 1411 others, and derivative works that comment on or otherwise explain it 1412 or assist in its implementation may be prepared, copied, published 1413 and distributed, in whole or in part, without restriction of any 1414 kind, provided that the above copyright notice and this paragraph are 1415 included on all such copies and derivative works. However, this 1416 document itself may not be modified in any way, such as by removing 1417 the copyright notice or references to the Internet Society or other 1418 Internet organizations, except as needed for the purpose of 1419 developing Internet standards in which case the procedures for 1420 copyrights defined in the Internet Standards process must be 1421 followed, or as required to translate it into languages other than 1422 English. 1424 The limited permissions granted above are perpetual and will not be 1425 revoked by the Internet Society or its successors or assigns. 1427 This document and the information contained herein is provided on an 1428 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1429 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1430 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1431 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1432 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.