idnits 2.17.1 draft-ietf-idr-bgp4-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-18) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** 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 1) being 1255 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 78 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 1995) is 10382 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) Summary: 12 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group S. Willis 2 INTERNET DRAFT J. Burruss 3 BayNetworks 4 J. Chu 5 (Editor) 6 IBM Corp. 7 November 1995 9 Definitions of Managed Objects 10 for the Fourth Version of Border Gateway Protocol (BGP-4) 12 14 Status of this Memo 16 This document is an Internet Draft. Internet Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its Areas, and 18 its Working Groups. Note that other groups may also distribute working 19 documents as Internet Drafts. 21 Internet Drafts are draft documents valid for a maximum of six months. 22 Internet Drafts may be updated, replaced, or obsoleted by other 23 documents at any time. It is not appropriate to use Internet Drafts as 24 reference material or to cite them other than as a "working draft" or 25 "work in progress." 27 Please check the I-D abstract listing contained in each Internet Draft 28 directory to learn the current status of this or any other Internet 29 Draft. 31 This memo is an extension to the SNMP MIB. It specifies an IAB 32 standards track protocol for the Internet community, and requests 33 discussion and suggestions for improvements. The origin of this memo is 34 from RFC 1269 "Definitions of Managed Objects for the Board Gateway 35 Protocol (Version 3)" written by the first two authors of this memo. 37 Distribution of this memo is unlimited. Please forward comments to 38 bgp@ans.net. 40 1. Introduction 42 This memo defines an experimental portion of the Management Information 43 Base (MIB) for use with network management protocols in the Internet 45 Expiration Date May 1996 [Page 1]FORMFEED 46 community. In particular, it describes managed objects used for 47 managing the Border Gateway Protocol Version 4 or lower [1, 2]. 49 2. The SNMPv2 Network Management Framework 51 The SNMPv2 Network Management Framework consists of four major 52 components. They are: 54 RFC 1442 which defines the SMI, the mechanisms used for describing 55 and naming objects for the purpose of management. 57 RFC 1213 defines MIB-II, the core set of managed objects for the 58 Internet suite of protocols. 60 RFC 1445 which defines the administrative and other architectural 61 aspects of the framework. 63 RFC 1448 which defines the protocol used for network access to 64 managed objects. 66 The Framework permits new objects to be defined for the purpose of 67 experimentation and evaluation. 69 3. Object Definitions 71 Managed objects are accessed via a virtual information store, termed the 72 Management Information Base or MIB. Objects in the MIB are defined 73 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 74 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 75 an administratively assigned name. The object type together with an 76 object instance serves to uniquely identify a specific instantiation of 77 the object. For human convenience, we often use a textual string, 78 termed the descriptor, to refer to the object type. 80 4. Overview 82 These objects are used to control and manage a BGP-4 implementation. 84 Apart from a few system-wide scalar objects, this MIB is broken into 85 three tables: the BGP Peer Table, the BGP Received Path Attribute Table, 86 and the BGP-4 Received Path Attribute Table. The BGP Peer Table 87 contains information about state and current activity of connections 89 Expiration Date May 1996 [Page 2]FORMFEED 90 with the BGP peers. The Received Path Attribute Table contains path 91 attributes received from all peers running BGP version 3 or less. The 92 BGP-4 Received Path Attribute Table contains path attributes received 93 from all BGP-4 peers. The actual attributes used in determining a route 94 are a subset of the received attribute tables after local routing policy 95 has been applied. 97 5. Definitions 99 BGP4-MIB DEFINITIONS ::= BEGIN 101 IMPORTS 102 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 103 IpAddress, Integer32, Counter32, Gauge32 104 FROM SNMPv2-SMI 105 mib-2 106 FROM RFC1213-MIB; 108 bgp MODULE-IDENTITY 109 LAST-UPDATED "9511090000Z" 110 ORGANIZATION "IETF BGP Working Group" 111 CONTACT-INFO 112 " John Chu (Editor) 113 Postal: IBM Corp. 114 P.O.Box 704 115 Yorktown Heights, NY 10598 116 US 118 Tel: +1 914 784 7839 119 Fax: +1 914 784 6205 120 E-mail: jychu@watson.ibm.com" 121 DESCRIPTION 122 "The MIB module for BGP-4." 123 ::= { mib-2 15 } 125 bgpVersion OBJECT-TYPE 126 SYNTAX OCTET STRING (SIZE (1..255)) 127 MAX-ACCESS read-only 128 STATUS current 129 DESCRIPTION 130 "Vector of supported BGP protocol version 131 numbers. Each peer negotiates the version 132 from this vector. Versions are identified 133 via the string of bits contained within this 134 object. The first octet contains bits 0 to 135 7, the second octet contains bits 8 to 15, 137 Expiration Date May 1996 [Page 3]FORMFEED 138 and so on, with the most significant bit 139 referring to the lowest bit number in the 140 octet (e.g., the MSB of the first octet 141 refers to bit 0). If a bit, i, is present 142 and set, then the version (i+1) of the BGP 143 is supported." 144 ::= { bgp 1 } 146 bgpLocalAs OBJECT-TYPE 147 SYNTAX INTEGER (0..65535) 148 MAX-ACCESS read-only 149 STATUS current 150 DESCRIPTION 151 "The local autonomous system number." 152 ::= { bgp 2 } 154 -- BGP Peer table. This table contains, one entry per BGP 155 -- peer, information about the BGP peer. 157 bgpPeerTable OBJECT-TYPE 158 SYNTAX SEQUENCE OF BgpPeerEntry 159 MAX-ACCESS not-accessible 160 STATUS current 161 DESCRIPTION 162 "BGP peer table. This table contains, 163 one entry per BGP peer, information about the 164 connections with BGP peers." 165 ::= { bgp 3 } 167 bgpPeerEntry OBJECT-TYPE 168 SYNTAX BgpPeerEntry 169 MAX-ACCESS not-accessible 170 STATUS current 171 DESCRIPTION 172 "Entry containing information about the 173 connection with a BGP peer." 174 INDEX { bgpPeerRemoteAddr } 175 ::= { bgpPeerTable 1 } 177 BgpPeerEntry ::= SEQUENCE { 178 bgpPeerIdentifier 179 IpAddress, 180 bgpPeerState 181 INTEGER, 182 bgpPeerAdminStatus 183 INTEGER, 185 Expiration Date May 1996 [Page 4]FORMFEED 186 bgpPeerNegotiatedVersion 187 Integer32, 188 bgpPeerLocalAddr 189 IpAddress, 190 bgpPeerLocalPort 191 INTEGER, 192 bgpPeerRemoteAddr 193 IpAddress, 194 bgpPeerRemotePort 195 INTEGER, 196 bgpPeerRemoteAs 197 INTEGER, 198 bgpPeerInUpdates 199 Counter32, 200 bgpPeerOutUpdates 201 Counter32, 202 bgpPeerInTotalMessages 203 Counter32, 204 bgpPeerOutTotalMessages 205 Counter32, 206 bgpPeerLastError 207 OCTET STRING, 208 bgpPeerFsmEstablishedTransitions 209 Counter32, 210 bgpPeerFsmEstablishedTime 211 Gauge32, 212 bgpPeerConnectRetryInterval 213 INTEGER, 214 bgpPeerHoldTime 215 INTEGER, 216 bgpPeerKeepAlive 217 INTEGER, 218 bgpPeerHoldTimeConfigured 219 INTEGER, 220 bgpPeerKeepAliveConfigured 221 INTEGER, 222 bgpPeerMinASOriginationInterval 223 INTEGER, 224 bgpPeerMinRouteAdvertisementInterval 225 INTEGER, 226 bgpPeerInUpdateElapsedTime 227 Gauge32 228 } 230 bgpPeerIdentifier OBJECT-TYPE 231 SYNTAX IpAddress 232 MAX-ACCESS read-only 233 STATUS current 235 Expiration Date May 1996 [Page 5]FORMFEED 236 DESCRIPTION 237 "The BGP Identifier of this entry's BGP peer." 238 ::= { bgpPeerEntry 1 } 240 bgpPeerState OBJECT-TYPE 241 SYNTAX INTEGER { 242 idle(1), 243 connect(2), 244 active(3), 245 opensent(4), 246 openconfirm(5), 247 established(6) 248 } 249 MAX-ACCESS read-only 250 STATUS current 251 DESCRIPTION 252 "The BGP peer connection state." 253 ::= { bgpPeerEntry 2 } 255 bgpPeerAdminStatus OBJECT-TYPE 256 SYNTAX INTEGER { 257 stop(1), 258 start(2) 259 } 260 MAX-ACCESS read-write 261 STATUS current 262 DESCRIPTION 263 "The desired state of the BGP connection. A 264 transition from 'stop' to 'start' will cause 265 the BGP Start Event to be generated. A 266 transition from 'start' to 'stop' will cause 267 the BGP Stop Event to be generated. This 268 parameter can be used to restart BGP peer 269 connections. Care should be used in providing 270 write access to this object without adequate 271 authentication." 272 ::= { bgpPeerEntry 3 } 274 bgpPeerNegotiatedVersion OBJECT-TYPE 275 SYNTAX Integer32 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "The negotiated version of BGP running between 280 the two peers." 281 ::= { bgpPeerEntry 4 } 283 bgpPeerLocalAddr OBJECT-TYPE 285 Expiration Date May 1996 [Page 6]FORMFEED 286 SYNTAX IpAddress 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The local IP address of this entry's BGP 291 connection." 292 ::= { bgpPeerEntry 5 } 294 bgpPeerLocalPort OBJECT-TYPE 295 SYNTAX INTEGER (0..65535) 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The local port for the TCP connection between 300 the BGP peers." 301 ::= { bgpPeerEntry 6 } 303 bgpPeerRemoteAddr OBJECT-TYPE 304 SYNTAX IpAddress 305 MAX-ACCESS read-only 306 STATUS current 307 DESCRIPTION 308 "The remote IP address of this entry's BGP 309 peer." 310 ::= { bgpPeerEntry 7 } 312 bgpPeerRemotePort OBJECT-TYPE 313 SYNTAX INTEGER (0..65535) 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The remote port for the TCP connection between 318 the BGP peers. Note that the objects 319 bgpPeerLocalAddr, bgpPeerLocalPort, 320 bgpPeerRemoteAddr and bgpPeerRemotePort 321 provide the appropriate reference to the 322 standard MIB TCP connection table." 323 ::= { bgpPeerEntry 8 } 325 bgpPeerRemoteAs OBJECT-TYPE 326 SYNTAX INTEGER (0..65535) 327 MAX-ACCESS read-only 328 STATUS current 329 DESCRIPTION 330 "The remote autonomous system number." 331 ::= { bgpPeerEntry 9 } 333 bgpPeerInUpdates OBJECT-TYPE 335 Expiration Date May 1996 [Page 7]FORMFEED 336 SYNTAX Counter32 337 MAX-ACCESS read-only 338 STATUS current 339 DESCRIPTION 340 "The number of BGP UPDATE messages received on 341 this connection. This object should be 342 initialized to zero (0) when the connection is 343 established." 344 ::= { bgpPeerEntry 10 } 346 bgpPeerOutUpdates OBJECT-TYPE 347 SYNTAX Counter32 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The number of BGP UPDATE messages transmitted 352 on this connection. This object should be 353 initialized to zero (0) when the connection is 354 established." 355 ::= { bgpPeerEntry 11 } 357 bgpPeerInTotalMessages OBJECT-TYPE 358 SYNTAX Counter32 359 MAX-ACCESS read-only 360 STATUS current 361 DESCRIPTION 362 "The total number of messages received from the 363 remote peer on this connection. This object 364 should be initialized to zero when the 365 connection is established." 366 ::= { bgpPeerEntry 12 } 368 bgpPeerOutTotalMessages OBJECT-TYPE 369 SYNTAX Counter32 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The total number of messages transmitted to 374 the remote peer on this connection. This object 375 should be initialized to zero when the 376 connection is established." 377 ::= { bgpPeerEntry 13 } 379 bgpPeerLastError OBJECT-TYPE 380 SYNTAX OCTET STRING (SIZE (2)) 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 385 Expiration Date May 1996 [Page 8]FORMFEED 386 "The last error code and subcode seen by this 387 peer on this connection. If no error has 388 occurred, this field is zero. Otherwise, the 389 first byte of this two byte OCTET STRING 390 contains the error code, and the second byte 391 contains the subcode." 392 ::= { bgpPeerEntry 14 } 394 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 395 SYNTAX Counter32 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "The total number of times the BGP FSM 400 transitioned into the established state." 401 ::= { bgpPeerEntry 15 } 403 bgpPeerFsmEstablishedTime OBJECT-TYPE 404 SYNTAX Gauge32 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "This timer indicates how long (in seconds) this 409 peer has been in the Established state or how long 410 since this peer was last in the Established state. 411 It is set to zero when a new peer is configured or 412 the router is booted." 413 ::= { bgpPeerEntry 16 } 415 bgpPeerConnectRetryInterval OBJECT-TYPE 416 SYNTAX INTEGER (1..65535) 417 MAX-ACCESS read-write 418 STATUS current 419 DESCRIPTION 420 "Time interval in seconds for the ConnectRetry 421 timer. The suggested value for this timer is 422 120 seconds." 423 ::= { bgpPeerEntry 17 } 425 bgpPeerHoldTime OBJECT-TYPE 426 SYNTAX INTEGER ( 0 | 3..65535 ) 427 MAX-ACCESS read-only 428 STATUS current 429 DESCRIPTION 430 "Time interval in seconds for the Hold Timer 431 established with the peer. The value of this 432 object is calculated by this BGP speaker by 433 using the smaller of the value in 435 Expiration Date May 1996 [Page 9]FORMFEED 436 bgpPeerHoldTimeConfigured and the Hold Time 437 received in the OPEN message. This value 438 must be at lease three seconds if it is not 439 zero (0) in which case the Hold Timer has 440 not been established with the peer, or, the 441 value of bgpPeerHoldTimeConfigured is zero (0)." 442 ::= { bgpPeerEntry 18 } 444 bgpPeerKeepAlive OBJECT-TYPE 445 SYNTAX INTEGER ( 0 | 1..21845 ) 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "Time interval in seconds for the KeepAlive 450 timer established with the peer. The value of 451 this object is calculated by this BGP speaker 452 such that, when compared with bgpPeerHoldTime, 453 it has the same proportion as what 454 bgpPeerKeepAliveConfigured has when compared 455 with bgpPeerHoldTimeConfigured. If the value 456 of this object is zero (0), it indicates that 457 the KeepAlive timer has not been established 458 with the peer, or, the value of 459 bgpPeerKeepAliveConfigured is zero (0)." 460 ::= { bgpPeerEntry 19 } 462 bgpPeerHoldTimeConfigured OBJECT-TYPE 463 SYNTAX INTEGER ( 0 | 3..65535 ) 464 MAX-ACCESS read-write 465 STATUS current 466 DESCRIPTION 467 "Time interval in seconds for the Hold Time 468 configured for this BGP speaker with this peer. 469 This value is placed in an OPEN message sent to 470 this peer by this BGP speaker, and is compared 471 with the Hold Time field in an OPEN message 472 received from the peer when determining the Hold 473 Time (bgpPeerHoldTime) with the peer. This value 474 must not be less than three seconds if it is not 475 zero (0) in which case the Hold Time is NOT to be 476 established with the peer. The suggested value for 477 this timer is 90 seconds." 478 ::= { bgpPeerEntry 20 } 480 bgpPeerKeepAliveConfigured OBJECT-TYPE 481 SYNTAX INTEGER ( 0 | 1..21845 ) 482 MAX-ACCESS read-write 483 STATUS current 485 Expiration Date May 1996 [Page 10]FORMFEED 486 DESCRIPTION 487 "Time interval in seconds for the KeepAlive timer 488 configured for this BGP speaker with this peer. 489 The value of this object will only determine the 490 KEEPALIVE messages' frequency relative to the value 491 specified in bgpPeerHoldTimeConfigured; the actual 492 time interval for the KEEPALIVE messages is 493 indicated by bgpPeerKeepAlive. A reasonable maximu 494 m 495 value for this timer would be configured to be one 496 third of that of bgpPeerHoldTimeConfigured. 497 If the value of this object is zero (0), no 498 periodical KEEPALIVE messages are sent to the peer 499 after the BGP connection has been established. The 500 suggested value for this timer is 30 seconds." 501 ::= { bgpPeerEntry 21 } 503 bgpPeerMinASOriginationInterval OBJECT-TYPE 504 SYNTAX INTEGER (1..65535) 505 MAX-ACCESS read-write 506 STATUS current 507 DESCRIPTION 508 "Time interval in seconds for the 509 MinASOriginationInterval timer. 510 The suggested value for this timer is 15 seconds." 511 ::= { bgpPeerEntry 22 } 513 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 514 SYNTAX INTEGER (1..65535) 515 MAX-ACCESS read-write 516 STATUS current 517 DESCRIPTION 518 "Time interval in seconds for the 519 MinRouteAdvertisementInterval timer. 520 The suggested value for this timer is 30 seconds." 521 ::= { bgpPeerEntry 23 } 523 bgpPeerInUpdateElapsedTime OBJECT-TYPE 524 SYNTAX Gauge32 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "Elapsed time in seconds since the last BGP 529 UPDATE message was received from the peer. 530 Each time bgpPeerInUpdates is incremented, 531 the value of this object is set to zero (0)." 532 ::= { bgpPeerEntry 24 } 534 Expiration Date May 1996 [Page 11]FORMFEED 535 bgpIdentifier OBJECT-TYPE 536 SYNTAX IpAddress 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "The BGP Identifier of local system." 541 ::= { bgp 4 } 543 -- Received Path Attribute Table. This table contains, 544 -- one entry per path to a network, path attributes 545 -- received from all peers running BGP version 3 or less. 546 -- This table is deprecated. 548 bgpRcvdPathAttrTable OBJECT-TYPE 549 SYNTAX SEQUENCE OF BgpPathAttrEntry 550 MAX-ACCESS not-accessible 551 STATUS obsolete 552 DESCRIPTION 553 "The BGP Received Path Attribute Table contains 554 information about paths to destination networks 555 received from all peers running BGP version 3 or 556 less." 557 ::= { bgp 5 } 559 bgpPathAttrEntry OBJECT-TYPE 560 SYNTAX BgpPathAttrEntry 561 MAX-ACCESS not-accessible 562 STATUS obsolete 563 DESCRIPTION 564 "Information about a path to a network." 565 INDEX { bgpPathAttrDestNetwork, 566 bgpPathAttrPeer } 567 ::= { bgpRcvdPathAttrTable 1 } 569 BgpPathAttrEntry ::= SEQUENCE { 570 bgpPathAttrPeer 571 IpAddress, 572 bgpPathAttrDestNetwork 573 IpAddress, 574 bgpPathAttrOrigin 575 INTEGER, 576 bgpPathAttrASPath 577 OCTET STRING, 578 bgpPathAttrNextHop 579 IpAddress, 580 bgpPathAttrInterASMetric 582 Expiration Date May 1996 [Page 12]FORMFEED 583 Integer32 584 } 586 bgpPathAttrPeer OBJECT-TYPE 587 SYNTAX IpAddress 588 MAX-ACCESS read-only 589 STATUS obsolete 590 DESCRIPTION 591 "The IP address of the peer where the path 592 information was learned." 593 ::= { bgpPathAttrEntry 1 } 595 bgpPathAttrDestNetwork OBJECT-TYPE 596 SYNTAX IpAddress 597 MAX-ACCESS read-only 598 STATUS obsolete 599 DESCRIPTION 600 "The address of the destination network." 601 ::= { bgpPathAttrEntry 2 } 603 bgpPathAttrOrigin OBJECT-TYPE 604 SYNTAX INTEGER { 605 igp(1),-- networks are interior 606 egp(2),-- networks learned via EGP 607 incomplete(3) -- undetermined 608 } 609 MAX-ACCESS read-only 610 STATUS obsolete 611 DESCRIPTION 612 "The ultimate origin of the path information." 613 ::= { bgpPathAttrEntry 3 } 615 bgpPathAttrASPath OBJECT-TYPE 616 SYNTAX OCTET STRING (SIZE (2..255)) 617 MAX-ACCESS read-only 618 STATUS obsolete 619 DESCRIPTION 620 "The set of ASs that must be traversed to reach 621 the network. This object is probably best 622 represented as SEQUENCE OF INTEGER. For SMI 623 compatibility, though, it is represented as 624 OCTET STRING. Each AS is represented as a pair 625 of octets according to the following algorithm: 627 first-byte-of-pair = ASNumber / 256; 628 second-byte-of-pair = ASNumber & 255;" 629 ::= { bgpPathAttrEntry 4 } 631 Expiration Date May 1996 [Page 13]FORMFEED 632 bgpPathAttrNextHop OBJECT-TYPE 633 SYNTAX IpAddress 634 MAX-ACCESS read-only 635 STATUS obsolete 636 DESCRIPTION 637 "The address of the border router that should 638 be used for the destination network." 639 ::= { bgpPathAttrEntry 5 } 641 bgpPathAttrInterASMetric OBJECT-TYPE 642 SYNTAX Integer32 643 MAX-ACCESS read-only 644 STATUS obsolete 645 DESCRIPTION 646 "The optional inter-AS metric. If this 647 attribute has not been provided for this route, 648 the value for this object is 0." 649 ::= { bgpPathAttrEntry 6 } 651 -- BGP-4 Received Path Attribute Table. This table contains, 652 -- one entry per path to a network, path attributes 653 -- received from all peers running BGP-4. 655 bgp4PathAttrTable OBJECT-TYPE 656 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 657 MAX-ACCESS not-accessible 658 STATUS current 659 DESCRIPTION 660 "The BGP-4 Received Path Attribute Table contains 661 information about paths to destination networks 662 received from all BGP4 peers." 663 ::= { bgp 6 } 665 bgp4PathAttrEntry OBJECT-TYPE 666 SYNTAX Bgp4PathAttrEntry 667 MAX-ACCESS not-accessible 668 STATUS current 669 DESCRIPTION 670 "Information about a path to a network." 671 INDEX { bgp4PathAttrIpAddrPrefix, 672 bgp4PathAttrIpAddrPrefixLen, 673 bgp4PathAttrPeer } 674 ::= { bgp4PathAttrTable 1 } 676 Bgp4PathAttrEntry ::= SEQUENCE { 677 bgp4PathAttrPeer 679 Expiration Date May 1996 [Page 14]FORMFEED 680 IpAddress, 681 bgp4PathAttrIpAddrPrefixLen 682 INTEGER, 683 bgp4PathAttrIpAddrPrefix 684 IpAddress, 685 bgp4PathAttrOrigin 686 INTEGER, 687 bgp4PathAttrASPathSegment 688 OCTET STRING, 689 bgp4PathAttrNextHop 690 IpAddress, 691 bgp4PathAttrMultiExitDisc 692 INTEGER, 693 bgp4PathAttrLocalPref 694 INTEGER, 695 bgp4PathAttrAtomicAggregate 696 INTEGER, 697 bgp4PathAttrAggregatorAS 698 INTEGER, 699 bgp4PathAttrAggregatorAddr 700 IpAddress, 701 bgp4PathAttrCalcLocalPref 702 INTEGER, 703 bgp4PathAttrBest 704 INTEGER, 705 bgp4PathAttrUnknown 706 OCTET STRING 708 } 710 bgp4PathAttrPeer OBJECT-TYPE 711 SYNTAX IpAddress 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The IP address of the peer where the path 716 information was learned." 717 ::= { bgp4PathAttrEntry 1 } 719 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 720 SYNTAX INTEGER (0..32) 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "Length in bits of the IP address prefix in the 725 Network Layer Reachability Information field." 726 ::= { bgp4PathAttrEntry 2 } 728 Expiration Date May 1996 [Page 15]FORMFEED 729 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 730 SYNTAX IpAddress 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "An IP address prefix in the Network Layer 735 Reachability Information field. This object 736 is an IP address containing the prefix with 737 length specified by bgp4PathAttrIpAddrPrefixLen. 738 Any bits beyond the length specified by 739 bgp4PathAttrIpAddrPrefixLen are zeroed." 740 ::= { bgp4PathAttrEntry 3 } 742 bgp4PathAttrOrigin OBJECT-TYPE 743 SYNTAX INTEGER { 744 igp(1),-- networks are interior 745 egp(2),-- networks learned via EGP 746 incomplete(3) -- undetermined 747 } 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 "The ultimate origin of the path information." 752 ::= { bgp4PathAttrEntry 4 } 754 bgp4PathAttrASPathSegment OBJECT-TYPE 755 SYNTAX OCTET STRING (SIZE (2..255)) 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "The sequence of AS path segments. Each AS 760 path segment is represented by a triple 761 . 763 The type is a 1-octet field which has two 764 possible values: 765 1 AS_SET: unordered set of ASs a 766 route in the UPDATE message 767 has traversed 768 2 AS_SEQUENCE: ordered set of ASs 769 a route in the UPDATE message 770 has traversed. 772 The length is a 1-octet field containing the 773 number of ASs in the value field. 775 The value field contains one or more AS 776 numbers, each AS is represented in the octet 778 Expiration Date May 1996 [Page 16]FORMFEED 779 string as a pair of octets according to the 780 following algorithm: 782 first-byte-of-pair = ASNumber / 256; 783 second-byte-of-pair = ASNumber & 255;" 784 ::= { bgp4PathAttrEntry 5 } 786 bgp4PathAttrNextHop OBJECT-TYPE 787 SYNTAX IpAddress 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The address of the border router that should 792 be used for the destination network." 793 ::= { bgp4PathAttrEntry 6 } 795 bgp4PathAttrMultiExitDisc OBJECT-TYPE 796 SYNTAX INTEGER (-1..2147483647) 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "This metric is used to discriminate between 801 multiple exit points to an adjacent autonomous 802 system. A value of -1 indicates the absence of 803 this attribute." 804 ::= { bgp4PathAttrEntry 7 } 806 bgp4PathAttrLocalPref OBJECT-TYPE 807 SYNTAX INTEGER (-1..2147483647) 808 MAX-ACCESS read-only 809 STATUS current 810 DESCRIPTION 811 "The originating BGP4 speaker's degree of 812 preference for an advertised route. A value of 813 -1 indicates the absence of this attribute." 814 ::= { bgp4PathAttrEntry 8 } 816 bgp4PathAttrAtomicAggregate OBJECT-TYPE 817 SYNTAX INTEGER { 818 lessSpecificRrouteNotSelected(1), 819 lessSpecificRouteSelected(2) 820 } 821 MAX-ACCESS read-only 822 STATUS current 823 DESCRIPTION 824 "Whether or not a system has selected 825 a less specific route without selecting a 826 more specific route." 828 Expiration Date May 1996 [Page 17]FORMFEED 829 ::= { bgp4PathAttrEntry 9 } 831 bgp4PathAttrAggregatorAS OBJECT-TYPE 832 SYNTAX INTEGER (0..65535) 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "The AS number of the last BGP4 speaker that 837 performed route aggregation. A value of zero (0) 838 indicates the absence of this attribute." 839 ::= { bgp4PathAttrEntry 10 } 841 bgp4PathAttrAggregatorAddr OBJECT-TYPE 842 SYNTAX IpAddress 843 MAX-ACCESS read-only 844 STATUS current 845 DESCRIPTION 846 "The IP address of the last BGP4 speaker that 847 performed route aggregation. A value of 848 0.0.0.0 indicates the absence of this attribute." 849 ::= { bgp4PathAttrEntry 11 } 851 bgp4PathAttrCalcLocalPref OBJECT-TYPE 852 SYNTAX INTEGER (-1..2147483647) 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "The degree of preference calculated by the 857 receiving BGP4 speaker for an advertised route. 858 A value of -1 indicates the absence of this 859 attribute." 860 ::= { bgp4PathAttrEntry 12 } 862 bgp4PathAttrBest OBJECT-TYPE 863 SYNTAX INTEGER { 864 false(1),-- not chosen as best route 865 true(2) -- chosen as best route 866 } 867 MAX-ACCESS read-only 868 STATUS current 869 DESCRIPTION 870 "An indication of whether or not this route 871 was chosen as the best BGP4 route." 872 ::= { bgp4PathAttrEntry 13 } 874 bgp4PathAttrUnknown OBJECT-TYPE 875 SYNTAX OCTET STRING (SIZE(0..255)) 876 MAX-ACCESS read-only 878 Expiration Date May 1996 [Page 18]FORMFEED 879 STATUS current 880 DESCRIPTION 881 "One or more path attributes not understood 882 by this BGP4 speaker. Size zero (0) indicates 883 the absence of such attribute(s). Octets 884 beyond the maximum size, if any, are not 885 recorded by this object." 886 ::= { bgp4PathAttrEntry 14 } 888 -- Traps. 890 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } 892 bgpEstablished NOTIFICATION-TYPE 893 OBJECTS { bgpPeerLastError, 894 bgpPeerState } 895 STATUS current 896 DESCRIPTION 897 "The BGP Established event is generated when 898 the BGP FSM enters the ESTABLISHED state." 899 ::= { bgpTraps 1 } 901 bgpBackwardTransition NOTIFICATION-TYPE 902 OBJECTS { bgpPeerLastError, 903 bgpPeerState } 904 STATUS current 905 DESCRIPTION 906 "The BGPBackwardTransition Event is generated 907 when the BGP FSM moves from a higher numbered 908 state to a lower numbered state." 909 ::= { bgpTraps 2 } 911 END 913 6. Acknowledgements 915 We would like to acknowledge the assistance of all the members of the 916 Interconnectivity Working Group, and particularly the following 917 individuals: 919 Yakov Rekhter, cisco Systems 920 Rob Coltun, Fore 921 Guy Almes, ANS 922 Jeff Honig, Cornell Theory Center 923 Marshall T. Rose, Dover Beach Consulting, Inc. 925 Expiration Date May 1996 [Page 19]FORMFEED 926 Dennis Ferguson, Ipsilon 927 Mike Mathis, PSC 928 John Krawczyk, BayNetworks 929 Curtis Villamizar, ANS 930 Dave LeRoy, Pencom Systems 931 Paul Traina, cisco Systems 932 Andrew Partan, UUNET 933 Robert Snyder, cisco Systems 934 Dimitry Haskin, BayNetworks 935 Peder Chr Norgaard, Telebit Communications A/S 936 Joel Halpern, NewBridge 938 7. References 940 [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", 941 RFC1771, March 1995 943 [2] Rekhter, Y., Gross, P., "Application of the Border 944 Gateway Protocol in the Internet", RFC1772, March 1995 946 8. Security Considerations 948 Security issues are not discussed in this memo. 950 Authors' Address 952 Steven Willis 953 BayNetworks 954 15 Crosby Drive 955 Bedford, MA 01730 957 Phone: (617) 275-2400 958 Email: swillis@baynetworks.com 960 John Burruss 961 BayNetworks 962 15 Crosby Drive 963 Bedford, MA 01730 965 Phone: (617) 275-2400 966 Email: jburruss@baynetworks.com 968 Expiration Date May 1996 [Page 20]FORMFEED 969 John Chu 970 IBM Corp. 971 P.O.Box 704 972 Yorktown Heights, NY 10598 974 Phone: (914) 784-7839 975 Email: jychu@watson.ibm.com 977 Expiration Date May 1996 [Page 21]FORMFEED