idnits 2.17.1 draft-ietf-idr-bgp4-mib-04.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: ---------------------------------------------------------------------------- ** 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 6 months document validity -- 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 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. 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 (February 1999) is 9201 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: 20 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Hares 3 INTERNET DRAFT Merit 4 J. Johnson 5 RedBack Networks 6 S. Willis 7 Argon Networks 8 J. Burruss 9 WinData 10 J. Chu 11 IBM Corporation 12 February 1999 14 Definitions of Managed Objects 16 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.txt 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 Mechanisms for describing and naming objects and events for 74 the purpose of management. The first version of this 75 Structure of Management Information (SMI) is called SMIv1 and 76 described in RFC 1155 [4], RFC 1212 [5] and RFC 1215 [6]. The 77 second version, called SMIv2, is described in RFC 1902 [7], 78 RFC 1903 [8] and RFC 1904 [9]. 80 o Message protocols for transferring management information. 81 The first version of the SNMP message protocol is called 82 SNMPv1 and described in RFC 1157 [10]. A second version of 83 the SNMP message protocol, which is not an Internet standards 84 track protocol, is called SNMPv2c and described in RFC 1901 85 [11] and RFC 1906 [12]. The third version of the message 86 protocol is called SNMPv3 and described in RFC 1906 [12], RFC 87 2272 [13] and RFC 2274 [14]. 89 o Protocol operations for accessing management information. The 90 first set of protocol operations and associated PDU formats 91 is described in RFC 1157 [10]. A second set of protocol 92 operations and associated PDU formats is described in RFC 93 1905 [15]. 95 o A set of fundamental applications described in RFC 2273 [16] 96 and the view-based access control mechanism described in RFC 97 2275 [17]. 99 Managed objects are accessed via a virtual information store, termed 100 the Management Information Base or MIB. Objects in the MIB are 101 defined using the mechanisms defined in the SMI. 103 This memo specifies a MIB module that is compliant to the SMIv2. A 104 MIB conforming to the SMIv1 can be produced through the appropriate 105 translations. The resulting translated MIB must be semantically 106 equivalent, except where objects or events are omitted because no 107 translation is possible (use of Counter64). Some machine readable 108 information in SMIv2 will be converted into textual descriptions in 109 SMIv1 during the translation process. However, this loss of machine 110 readable information is not considered to change the semantics of the 111 MIB. 113 3. Object Definitions 115 Managed objects are accessed via a virtual information store, termed 116 the Management Information Base or MIB. Objects in the MIB are 117 defined using the subset of Abstract Syntax Notation One (ASN.1) 118 defined in the SMI. In particular, each object type is named by an 119 OBJECT IDENTIFIER, an administratively assigned name. The object 120 type together with an object instance serves to uniquely identify a 121 specific instantiation of the object. For human convenience, we 122 often use a textual string, termed the descriptor, to refer to the 123 object type. 125 4. 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 5. 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 "9902100000Z" 153 ORGANIZATION "IETF IDR Working Group" 154 CONTACT-INFO "E-mail: idr@merit.net 156 Susan Hares (Editor) 157 Merit Network 158 4251 Plymouth Road 159 Suite C 160 Ann Arbor, MI 48105-2785 161 Tel: +1 734 936 2095 162 Fax: +1 734 647 3185 163 E-mail: skh@merit.edu 165 Jeff Johnson (Editor) 166 RedBack Networks, Inc. 167 1389 Moffett Park Drive 168 Sunnyvale, CA 94089-1134 169 Tel: +1 408 548 3516 170 Fax: +1 408 548 3599 171 E-mail: jeff@redback.com" 172 DESCRIPTION 173 "The MIB module for BGP-4." 174 REVISION "9902100000Z" 175 DESCRIPTION 176 "Corrected duplicate OBJECT IDENTIFIER 177 assignment in the conformance information." 178 REVISION "9601080000Z" 179 DESCRIPTION 180 "1) Fixed the definitions of the traps to 181 make them equivalent to their initial 182 definition in RFC 1269. 183 2) Added compliance and conformance info." 184 ::= { mib-2 15 } 186 bgpVersion OBJECT-TYPE 187 SYNTAX OCTET STRING (SIZE (1..255)) 188 MAX-ACCESS read-only 189 STATUS current 190 DESCRIPTION 191 "Vector of supported BGP protocol version 192 numbers. Each peer negotiates the version 193 from this vector. Versions are identified 194 via the string of bits contained within this 195 object. The first octet contains bits 0 to 196 7, the second octet contains bits 8 to 15, 197 and so on, with the most significant bit 198 referring to the lowest bit number in the 199 octet (e.g., the MSB of the first octet 200 refers to bit 0). If a bit, i, is present 201 and set, then the version (i+1) of the BGP 202 is supported." 203 ::= { bgp 1 } 205 bgpLocalAs OBJECT-TYPE 206 SYNTAX INTEGER (0..65535) 207 MAX-ACCESS read-only 208 STATUS current 209 DESCRIPTION 210 "The local autonomous system number." 211 ::= { bgp 2 } 213 -- BGP Peer table. This table contains, one entry per BGP 214 -- peer, information about the BGP peer. 216 bgpPeerTable OBJECT-TYPE 217 SYNTAX SEQUENCE OF BgpPeerEntry 218 MAX-ACCESS not-accessible 219 STATUS current 220 DESCRIPTION 221 "BGP peer table. This table contains, 222 one entry per BGP peer, information about the 223 connections with BGP peers." 224 ::= { bgp 3 } 226 bgpPeerEntry OBJECT-TYPE 227 SYNTAX BgpPeerEntry 228 MAX-ACCESS not-accessible 229 STATUS current 230 DESCRIPTION 231 "Entry containing information about the 232 connection with a BGP peer." 233 INDEX { bgpPeerRemoteAddr } 234 ::= { bgpPeerTable 1 } 236 BgpPeerEntry ::= SEQUENCE { 237 bgpPeerIdentifier 238 IpAddress, 239 bgpPeerState 240 INTEGER, 241 bgpPeerAdminStatus 242 INTEGER, 243 bgpPeerNegotiatedVersion 244 Integer32, 245 bgpPeerLocalAddr 246 IpAddress, 247 bgpPeerLocalPort 248 INTEGER, 249 bgpPeerRemoteAddr 250 IpAddress, 251 bgpPeerRemotePort 252 INTEGER, 253 bgpPeerRemoteAs 254 INTEGER, 255 bgpPeerInUpdates 256 Counter32, 257 bgpPeerOutUpdates 258 Counter32, 259 bgpPeerInTotalMessages 260 Counter32, 261 bgpPeerOutTotalMessages 262 Counter32, 263 bgpPeerLastError 264 OCTET STRING, 265 bgpPeerFsmEstablishedTransitions 266 Counter32, 267 bgpPeerFsmEstablishedTime 268 Gauge32, 269 bgpPeerConnectRetryInterval 270 INTEGER, 271 bgpPeerHoldTime 272 INTEGER, 273 bgpPeerKeepAlive 274 INTEGER, 275 bgpPeerHoldTimeConfigured 276 INTEGER, 277 bgpPeerKeepAliveConfigured 278 INTEGER, 279 bgpPeerMinASOriginationInterval 280 INTEGER, 281 bgpPeerMinRouteAdvertisementInterval 282 INTEGER, 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 ::= { bgpPeerEntry 1 } 295 bgpPeerState OBJECT-TYPE 296 SYNTAX INTEGER { 297 idle(1), 298 connect(2), 299 active(3), 300 opensent(4), 301 openconfirm(5), 302 established(6) 303 } 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "The BGP peer connection state." 308 ::= { bgpPeerEntry 2 } 310 bgpPeerAdminStatus OBJECT-TYPE 311 SYNTAX INTEGER { 312 stop(1), 313 start(2) 314 } 315 MAX-ACCESS read-write 316 STATUS current 317 DESCRIPTION 318 "The desired state of the BGP connection. A 319 transition from 'stop' to 'start' will cause 320 the BGP Start Event to be generated. A 321 transition from 'start' to 'stop' will cause 322 the BGP Stop Event to be generated. This 323 parameter can be used to restart BGP peer 324 connections. Care should be used in providing 325 write access to this object without adequate 326 authentication." 327 ::= { bgpPeerEntry 3 } 329 bgpPeerNegotiatedVersion OBJECT-TYPE 330 SYNTAX Integer32 331 MAX-ACCESS read-only 332 STATUS current 333 DESCRIPTION 334 "The negotiated version of BGP running between 335 the two peers." 336 ::= { bgpPeerEntry 4 } 338 bgpPeerLocalAddr OBJECT-TYPE 339 SYNTAX IpAddress 340 MAX-ACCESS read-only 341 STATUS current 342 DESCRIPTION 343 "The local IP address of this entry's BGP 344 connection." 345 ::= { bgpPeerEntry 5 } 347 bgpPeerLocalPort OBJECT-TYPE 348 SYNTAX INTEGER (0..65535) 349 MAX-ACCESS read-only 350 STATUS current 351 DESCRIPTION 352 "The local port for the TCP connection between 353 the BGP peers." 354 ::= { bgpPeerEntry 6 } 356 bgpPeerRemoteAddr OBJECT-TYPE 357 SYNTAX IpAddress 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The remote IP address of this entry's BGP 362 peer." 363 ::= { bgpPeerEntry 7 } 365 bgpPeerRemotePort OBJECT-TYPE 366 SYNTAX INTEGER (0..65535) 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "The remote port for the TCP connection between 371 the BGP peers. Note that the objects 372 bgpPeerLocalAddr, bgpPeerLocalPort, 373 bgpPeerRemoteAddr and bgpPeerRemotePort 374 provide the appropriate reference to the 375 standard MIB TCP connection table." 376 ::= { bgpPeerEntry 8 } 378 bgpPeerRemoteAs OBJECT-TYPE 379 SYNTAX INTEGER (0..65535) 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "The remote autonomous system number." 384 ::= { bgpPeerEntry 9 } 386 bgpPeerInUpdates OBJECT-TYPE 387 SYNTAX Counter32 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The number of BGP UPDATE messages received on 392 this connection. This object should be 393 initialized to zero (0) when the connection is 394 established." 395 ::= { bgpPeerEntry 10 } 397 bgpPeerOutUpdates OBJECT-TYPE 398 SYNTAX Counter32 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "The number of BGP UPDATE messages transmitted 403 on this connection. This object should be 404 initialized to zero (0) when the connection is 405 established." 406 ::= { bgpPeerEntry 11 } 408 bgpPeerInTotalMessages OBJECT-TYPE 409 SYNTAX Counter32 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The total number of messages received from the 414 remote peer on this connection. This object 415 should be initialized to zero when the 416 connection is established." 417 ::= { bgpPeerEntry 12 } 419 bgpPeerOutTotalMessages OBJECT-TYPE 420 SYNTAX Counter32 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The total number of messages transmitted to 425 the remote peer on this connection. This object 426 should be initialized to zero when the 427 connection is established." 428 ::= { bgpPeerEntry 13 } 430 bgpPeerLastError OBJECT-TYPE 431 SYNTAX OCTET STRING (SIZE (2)) 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The last error code and subcode seen by this 436 peer on this connection. If no error has 437 occurred, this field is zero. Otherwise, the 438 first byte of this two byte OCTET STRING 439 contains the error code, and the second byte 440 contains the subcode." 441 ::= { bgpPeerEntry 14 } 443 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 444 SYNTAX Counter32 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The total number of times the BGP FSM 449 transitioned into the established state." 450 ::= { bgpPeerEntry 15 } 452 bgpPeerFsmEstablishedTime OBJECT-TYPE 453 SYNTAX Gauge32 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "This timer indicates how long (in seconds) this 458 peer has been in the Established state or how long 459 since this peer was last in the Established state. 460 It is set to zero when a new peer is configured or 461 the router is booted." 462 ::= { bgpPeerEntry 16 } 464 bgpPeerConnectRetryInterval OBJECT-TYPE 465 SYNTAX INTEGER (1..65535) 466 MAX-ACCESS read-write 467 STATUS current 468 DESCRIPTION 469 "Time interval in seconds for the ConnectRetry 470 timer. The suggested value for this timer is 471 120 seconds." 472 ::= { bgpPeerEntry 17 } 474 bgpPeerHoldTime OBJECT-TYPE 475 SYNTAX INTEGER ( 0 | 3..65535 ) 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "Time interval in seconds for the Hold Timer 480 established with the peer. The value of this 481 object is calculated by this BGP speaker by 482 using the smaller of the value in 483 bgpPeerHoldTimeConfigured and the Hold Time 484 received in the OPEN message. This value 485 must be at lease three seconds if it is not 486 zero (0) in which case the Hold Timer has 487 not been established with the peer, or, the 488 value of bgpPeerHoldTimeConfigured is zero (0)." 489 ::= { bgpPeerEntry 18 } 491 bgpPeerKeepAlive OBJECT-TYPE 492 SYNTAX INTEGER ( 0 | 1..21845 ) 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "Time interval in seconds for the KeepAlive 497 timer established with the peer. The value of 498 this object is calculated by this BGP speaker 499 such that, when compared with bgpPeerHoldTime, 500 it has the same proportion as what 501 bgpPeerKeepAliveConfigured has when compared 502 with bgpPeerHoldTimeConfigured. If the value 503 of this object is zero (0), it indicates that 504 the KeepAlive timer has not been established 505 with the peer, or, the value of 506 bgpPeerKeepAliveConfigured is zero (0)." 507 ::= { bgpPeerEntry 19 } 509 bgpPeerHoldTimeConfigured OBJECT-TYPE 510 SYNTAX INTEGER ( 0 | 3..65535 ) 511 MAX-ACCESS read-write 512 STATUS current 513 DESCRIPTION 514 "Time interval in seconds for the Hold Time 515 configured for this BGP speaker with this peer. 516 This value is placed in an OPEN message sent to 517 this peer by this BGP speaker, and is compared 518 with the Hold Time field in an OPEN message 519 received from the peer when determining the Hold 520 Time (bgpPeerHoldTime) with the peer. This value 521 must not be less than three seconds if it is not 522 zero (0) in which case the Hold Time is NOT to be 523 established with the peer. The suggested value for 524 this timer is 90 seconds." 525 ::= { bgpPeerEntry 20 } 527 bgpPeerKeepAliveConfigured OBJECT-TYPE 528 SYNTAX INTEGER ( 0 | 1..21845 ) 529 MAX-ACCESS read-write 530 STATUS current 531 DESCRIPTION 532 "Time interval in seconds for the KeepAlive timer 533 configured for this BGP speaker with this peer. 534 The value of this object will only determine the 535 KEEPALIVE messages' frequency relative to the value 536 specified in bgpPeerHoldTimeConfigured; the actual 537 time interval for the KEEPALIVE messages is 538 indicated by bgpPeerKeepAlive. A reasonable 539 maximum value for this timer would be configured to 540 be one third of that of bgpPeerHoldTimeConfigured. 541 If the value of this object is zero (0), no 542 periodical KEEPALIVE messages are sent to the peer 543 after the BGP connection has been established. The 544 suggested value for this timer is 30 seconds." 545 ::= { bgpPeerEntry 21 } 547 bgpPeerMinASOriginationInterval OBJECT-TYPE 548 SYNTAX INTEGER (1..65535) 549 MAX-ACCESS read-write 550 STATUS current 551 DESCRIPTION 552 "Time interval in seconds for the 553 MinASOriginationInterval timer. 554 The suggested value for this timer is 15 seconds." 555 ::= { bgpPeerEntry 22 } 557 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 558 SYNTAX INTEGER (1..65535) 559 MAX-ACCESS read-write 560 STATUS current 561 DESCRIPTION 562 "Time interval in seconds for the 563 MinRouteAdvertisementInterval timer. 564 The suggested value for this timer is 30 seconds." 565 ::= { bgpPeerEntry 23 } 567 bgpPeerInUpdateElapsedTime OBJECT-TYPE 568 SYNTAX Gauge32 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "Elapsed time in seconds since the last BGP 573 UPDATE message was received from the peer. 574 Each time bgpPeerInUpdates is incremented, 575 the value of this object is set to zero (0)." 576 ::= { bgpPeerEntry 24 } 578 bgpIdentifier OBJECT-TYPE 579 SYNTAX IpAddress 580 MAX-ACCESS read-only 581 STATUS current 582 DESCRIPTION 583 "The BGP Identifier of local system." 584 ::= { bgp 4 } 586 -- Received Path Attribute Table. This table contains, 587 -- one entry per path to a network, path attributes 588 -- received from all peers running BGP version 3 or less. 589 -- This table is obsolete, having been replaced in 590 -- functionality with the bgp4PathAttrTable. 592 bgpRcvdPathAttrTable OBJECT-TYPE 593 SYNTAX SEQUENCE OF BgpPathAttrEntry 594 MAX-ACCESS not-accessible 595 STATUS obsolete 596 DESCRIPTION 597 "The BGP Received Path Attribute Table contains 598 information about paths to destination networks 599 received from all peers running BGP version 3 or 600 less." 601 ::= { bgp 5 } 603 bgpPathAttrEntry OBJECT-TYPE 604 SYNTAX BgpPathAttrEntry 605 MAX-ACCESS not-accessible 606 STATUS obsolete 607 DESCRIPTION 608 "Information about a path to a network." 609 INDEX { bgpPathAttrDestNetwork, 610 bgpPathAttrPeer } 611 ::= { bgpRcvdPathAttrTable 1 } 613 BgpPathAttrEntry ::= SEQUENCE { 614 bgpPathAttrPeer 615 IpAddress, 616 bgpPathAttrDestNetwork 617 IpAddress, 618 bgpPathAttrOrigin 619 INTEGER, 620 bgpPathAttrASPath 621 OCTET STRING, 622 bgpPathAttrNextHop 623 IpAddress, 624 bgpPathAttrInterASMetric 625 Integer32 626 } 628 bgpPathAttrPeer OBJECT-TYPE 629 SYNTAX IpAddress 630 MAX-ACCESS read-only 631 STATUS obsolete 632 DESCRIPTION 633 "The IP address of the peer where the path 634 information was learned." 635 ::= { bgpPathAttrEntry 1 } 637 bgpPathAttrDestNetwork OBJECT-TYPE 638 SYNTAX IpAddress 639 MAX-ACCESS read-only 640 STATUS obsolete 641 DESCRIPTION 642 "The address of the destination network." 643 ::= { bgpPathAttrEntry 2 } 645 bgpPathAttrOrigin OBJECT-TYPE 646 SYNTAX INTEGER { 647 igp(1),-- networks are interior 648 egp(2),-- networks learned via EGP 649 incomplete(3) -- undetermined 650 } 651 MAX-ACCESS read-only 652 STATUS obsolete 653 DESCRIPTION 654 "The ultimate origin of the path information." 655 ::= { bgpPathAttrEntry 3 } 657 bgpPathAttrASPath OBJECT-TYPE 658 SYNTAX OCTET STRING (SIZE (2..255)) 659 MAX-ACCESS read-only 660 STATUS obsolete 661 DESCRIPTION 662 "The set of ASs that must be traversed to reach 663 the network. This object is probably best 664 represented as SEQUENCE OF INTEGER. For SMI 665 compatibility, though, it is represented as 666 OCTET STRING. Each AS is represented as a pair 667 of octets according to the following algorithm: 669 first-byte-of-pair = ASNumber / 256; 670 second-byte-of-pair = ASNumber & 255;" 671 ::= { bgpPathAttrEntry 4 } 673 bgpPathAttrNextHop OBJECT-TYPE 674 SYNTAX IpAddress 675 MAX-ACCESS read-only 676 STATUS obsolete 677 DESCRIPTION 678 "The address of the border router that should 679 be used for the destination network." 680 ::= { bgpPathAttrEntry 5 } 682 bgpPathAttrInterASMetric OBJECT-TYPE 683 SYNTAX Integer32 684 MAX-ACCESS read-only 685 STATUS obsolete 686 DESCRIPTION 687 "The optional inter-AS metric. If this 688 attribute has not been provided for this route, 689 the value for this object is 0." 690 ::= { bgpPathAttrEntry 6 } 692 -- BGP-4 Received Path Attribute Table. This table contains, 693 -- one entry per path to a network, path attributes 694 -- received from all peers running BGP-4. 696 bgp4PathAttrTable OBJECT-TYPE 697 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 698 MAX-ACCESS not-accessible 699 STATUS current 700 DESCRIPTION 701 "The BGP-4 Received Path Attribute Table contains 702 information about paths to destination networks 703 received from all BGP4 peers." 704 ::= { bgp 6 } 706 bgp4PathAttrEntry OBJECT-TYPE 707 SYNTAX Bgp4PathAttrEntry 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "Information about a path to a network." 712 INDEX { bgp4PathAttrIpAddrPrefix, 713 bgp4PathAttrIpAddrPrefixLen, 714 bgp4PathAttrPeer } 715 ::= { bgp4PathAttrTable 1 } 717 Bgp4PathAttrEntry ::= SEQUENCE { 718 bgp4PathAttrPeer 719 IpAddress, 720 bgp4PathAttrIpAddrPrefixLen 721 INTEGER, 722 bgp4PathAttrIpAddrPrefix 723 IpAddress, 724 bgp4PathAttrOrigin 725 INTEGER, 726 bgp4PathAttrASPathSegment 727 OCTET STRING, 728 bgp4PathAttrNextHop 729 IpAddress, 730 bgp4PathAttrMultiExitDisc 731 INTEGER, 732 bgp4PathAttrLocalPref 733 INTEGER, 734 bgp4PathAttrAtomicAggregate 735 INTEGER, 736 bgp4PathAttrAggregatorAS 737 INTEGER, 738 bgp4PathAttrAggregatorAddr 739 IpAddress, 740 bgp4PathAttrCalcLocalPref 741 INTEGER, 742 bgp4PathAttrBest 743 INTEGER, 744 bgp4PathAttrUnknown 745 OCTET STRING 746 } 748 bgp4PathAttrPeer OBJECT-TYPE 749 SYNTAX IpAddress 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "The IP address of the peer where the path 754 information was learned." 755 ::= { bgp4PathAttrEntry 1 } 757 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 758 SYNTAX INTEGER (0..32) 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "Length in bits of the IP address prefix in the 763 Network Layer Reachability Information field." 764 ::= { bgp4PathAttrEntry 2 } 766 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 767 SYNTAX IpAddress 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "An IP address prefix in the Network Layer 772 Reachability Information field. This object 773 is an IP address containing the prefix with 774 length specified by bgp4PathAttrIpAddrPrefixLen. 775 Any bits beyond the length specified by 776 bgp4PathAttrIpAddrPrefixLen are zeroed." 777 ::= { bgp4PathAttrEntry 3 } 779 bgp4PathAttrOrigin OBJECT-TYPE 780 SYNTAX INTEGER { 781 igp(1),-- networks are interior 782 egp(2),-- networks learned via EGP 783 incomplete(3) -- undetermined 784 } 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "The ultimate origin of the path information." 789 ::= { bgp4PathAttrEntry 4 } 791 bgp4PathAttrASPathSegment OBJECT-TYPE 792 SYNTAX OCTET STRING (SIZE (2..255)) 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The sequence of AS path segments. Each AS 797 path segment is represented by a triple 798 . 800 The type is a 1-octet field which has two 801 possible values: 802 1 AS_SET: unordered set of ASs a 803 route in the UPDATE message 804 has traversed 806 2 AS_SEQUENCE: ordered set of ASs 807 a route in the UPDATE message 808 has traversed. 810 The length is a 1-octet field containing the 811 number of ASs in the value field. 813 The value field contains one or more AS 814 numbers, each AS is represented in the octet 815 string as a pair of octets according to the 816 following algorithm: 818 first-byte-of-pair = ASNumber / 256; 819 second-byte-of-pair = ASNumber & 255;" 820 ::= { bgp4PathAttrEntry 5 } 822 bgp4PathAttrNextHop OBJECT-TYPE 823 SYNTAX IpAddress 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "The address of the border router that should 828 be used for the destination network." 829 ::= { bgp4PathAttrEntry 6 } 831 bgp4PathAttrMultiExitDisc OBJECT-TYPE 832 SYNTAX INTEGER (-1..2147483647) 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "This metric is used to discriminate between 837 multiple exit points to an adjacent autonomous 838 system. A value of -1 indicates the absence of 839 this attribute." 840 ::= { bgp4PathAttrEntry 7 } 842 bgp4PathAttrLocalPref OBJECT-TYPE 843 SYNTAX INTEGER (-1..2147483647) 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION 847 "The originating BGP4 speaker's degree of 848 preference for an advertised route. A value of 849 -1 indicates the absence of this attribute." 850 ::= { bgp4PathAttrEntry 8 } 852 bgp4PathAttrAtomicAggregate OBJECT-TYPE 853 SYNTAX INTEGER { 854 lessSpecificRrouteNotSelected(1), 855 lessSpecificRouteSelected(2) 856 } 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "Whether or not a system has selected 861 a less specific route without selecting a 862 more specific route." 863 ::= { bgp4PathAttrEntry 9 } 865 bgp4PathAttrAggregatorAS OBJECT-TYPE 866 SYNTAX INTEGER (0..65535) 867 MAX-ACCESS read-only 868 STATUS current 869 DESCRIPTION 870 "The AS number of the last BGP4 speaker that 871 performed route aggregation. A value of zero (0) 872 indicates the absence of this attribute." 873 ::= { bgp4PathAttrEntry 10 } 875 bgp4PathAttrAggregatorAddr OBJECT-TYPE 876 SYNTAX IpAddress 877 MAX-ACCESS read-only 878 STATUS current 879 DESCRIPTION 880 "The IP address of the last BGP4 speaker that 881 performed route aggregation. A value of 882 0.0.0.0 indicates the absence of this attribute." 883 ::= { bgp4PathAttrEntry 11 } 885 bgp4PathAttrCalcLocalPref OBJECT-TYPE 886 SYNTAX INTEGER (-1..2147483647) 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "The degree of preference calculated by the 891 receiving BGP4 speaker for an advertised route. 892 A value of -1 indicates the absence of this 893 attribute." 894 ::= { bgp4PathAttrEntry 12 } 896 bgp4PathAttrBest OBJECT-TYPE 897 SYNTAX INTEGER { 898 false(1),-- not chosen as best route 899 true(2) -- chosen as best route 900 } 901 MAX-ACCESS read-only 902 STATUS current 903 DESCRIPTION 904 "An indication of whether or not this route 905 was chosen as the best BGP4 route." 906 ::= { bgp4PathAttrEntry 13 } 908 bgp4PathAttrUnknown OBJECT-TYPE 909 SYNTAX OCTET STRING (SIZE(0..255)) 910 MAX-ACCESS read-only 911 STATUS current 912 DESCRIPTION 913 "One or more path attributes not understood 914 by this BGP4 speaker. Size zero (0) indicates 915 the absence of such attribute(s). Octets 916 beyond the maximum size, if any, are not 917 recorded by this object." 918 ::= { bgp4PathAttrEntry 14 } 920 -- Traps. 922 -- note that in RFC 1657, bgpTraps was incorrectly 923 -- assigned a value of { bgp 7 }, and each of the 924 -- traps had the bgpPeerRemoteAddr object inappropriately 925 -- removed from their OBJECTS clause. The following 926 -- definitions restore the semantics of the traps as 927 -- they were initially defined in RFC 1269. 929 -- { bgp 7 } is unused 931 bgpTraps OBJECT IDENTIFIER ::= { bgp 0 } 933 bgpEstablished NOTIFICATION-TYPE 934 OBJECTS { bgpPeerRemoteAddr, 935 bgpPeerLastError, 936 bgpPeerState } 937 STATUS current 938 DESCRIPTION 939 "The BGP Established event is generated when 940 the BGP FSM enters the ESTABLISHED state." 941 ::= { bgpTraps 1 } 943 bgpBackwardTransition NOTIFICATION-TYPE 944 OBJECTS { bgpPeerRemoteAddr, 945 bgpPeerLastError, 946 bgpPeerState } 947 STATUS current 948 DESCRIPTION 949 "The BGPBackwardTransition Event is generated 950 when the BGP FSM moves from a higher numbered 951 state to a lower numbered state." 952 ::= { bgpTraps 2 } 954 -- conformance information 956 bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 } 957 bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 } 958 bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 } 960 -- compliance statements 962 bgpMIBCompliance MODULE-COMPLIANCE 963 STATUS current 964 DESCRIPTION 965 "The compliance statement for entities which 966 implement the BGP4 mib." 967 MODULE -- this module 968 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 969 bgp4MIBPeerGroup, 970 bgp4MIBPathAttrGroup, 971 bgp4MIBNotificationGroup } 972 ::= { bgpMIBCompliances 1 } 974 -- units of conformance 976 bgp4MIBGlobalsGroup OBJECT-GROUP 977 OBJECTS { bgpVersion, 978 bgpLocalAs, 979 bgpIdentifier } 980 STATUS current 981 DESCRIPTION 982 "A collection of objects providing information 983 on global BGP state." 984 ::= { bgpMIBGroups 1 } 986 bgp4MIBPeerGroup OBJECT-GROUP 987 OBJECTS { bgpPeerIdentifier, 988 bgpPeerState, 989 bgpPeerAdminStatus, 990 bgpPeerNegotiatedVersion, 991 bgpPeerLocalAddr, 992 bgpPeerLocalPort, 993 bgpPeerRemoteAddr, 994 bgpPeerRemotePort, 995 bgpPeerRemoteAs, 996 bgpPeerInUpdates, 997 bgpPeerOutUpdates, 998 bgpPeerInTotalMessages, 999 bgpPeerOutTotalMessages, 1000 bgpPeerLastError, 1001 bgpPeerFsmEstablishedTransitions, 1002 bgpPeerFsmEstablishedTime, 1003 bgpPeerConnectRetryInterval, 1004 bgpPeerHoldTime, 1005 bgpPeerKeepAlive, 1006 bgpPeerHoldTimeConfigured, 1007 bgpPeerKeepAliveConfigured, 1008 bgpPeerMinASOriginationInterval, 1009 bgpPeerMinRouteAdvertisementInterval, 1010 bgpPeerInUpdateElapsedTime } 1011 STATUS current 1012 DESCRIPTION 1013 "A collection of objects for managing 1014 BGP peers." 1015 ::= { bgpMIBGroups 2 } 1017 bgp4MIBRcvdPathAttrGroup OBJECT-GROUP 1018 OBJECTS { bgpPathAttrPeer, 1019 bgpPathAttrDestNetwork, 1020 bgpPathAttrOrigin, 1021 bgpPathAttrASPath, 1022 bgpPathAttrNextHop, 1023 bgpPathAttrInterASMetric } 1024 STATUS obsolete 1025 DESCRIPTION 1026 "A collection of objects for managing BGP 1027 path entries. 1029 This conformance group is obsolete, 1030 replaced by bgp4MIBPathAttrGroup." 1031 ::= { bgpMIBGroups 3 } 1033 bgp4MIBPathAttrGroup OBJECT-GROUP 1034 OBJECTS { bgp4PathAttrPeer, 1035 bgp4PathAttrIpAddrPrefixLen, 1036 bgp4PathAttrIpAddrPrefix, 1037 bgp4PathAttrOrigin, 1038 bgp4PathAttrASPathSegment, 1039 bgp4PathAttrNextHop, 1040 bgp4PathAttrMultiExitDisc, 1041 bgp4PathAttrLocalPref, 1042 bgp4PathAttrAtomicAggregate, 1043 bgp4PathAttrAggregatorAS, 1044 bgp4PathAttrAggregatorAddr, 1045 bgp4PathAttrCalcLocalPref, 1046 bgp4PathAttrBest, 1047 bgp4PathAttrUnknown } 1048 STATUS current 1049 DESCRIPTION 1050 "A collection of objects for managing 1051 BGP path entries." 1052 ::= { bgpMIBGroups 4 } 1054 bgp4MIBNotificationGroup NOTIFICATION-GROUP 1055 NOTIFICATIONS { bgpEstablished, 1056 bgpBackwardTransition } 1057 STATUS current 1058 DESCRIPTION 1059 "A collection of notifications for signaling 1060 changes in BGP peer relationships." 1061 ::= { bgpMIBGroups 5 } 1063 END 1065 6. Intellectual Property 1067 The IETF takes no position regarding the validity or scope of any 1068 intellectual property or other rights that might be claimed to 1069 pertain to the implementation or use of the technology described in 1070 this document or the extent to which any license under such rights 1071 might or might not be available; neither does it represent that it 1072 has made any effort to identify any such rights. Information on the 1073 IETF's procedures with respect to rights in standards-track and 1074 standards-related documentation can be found in BCP-11. Copies of 1075 claims of rights made available for publication and any assurances of 1076 licenses to be made available, or the result of an attempt made to 1077 obtain a general license or permission for the use of such 1078 proprietary rights by implementors or users of this specification can 1079 be obtained from the IETF Secretariat. 1081 7. Acknowledgements 1083 We would like to acknowledge the assistance of all the members of the 1084 Inter-Domain Routing Working Group, and particularly the following 1085 individuals: 1087 Yakov Rekhter, cisco Systems 1088 Rob Coltun, Fore 1089 Guy Almes, ANS 1090 Jeff Honig, Cornell Theory Center 1091 Marshall T. Rose, Dover Beach Consulting, Inc. 1092 Dennis Ferguson, Juniper Networks 1093 Mike Mathis, PSC 1094 John Krawczyk, Bay Networks 1095 Curtis Villamizar, ANS 1096 Dave LeRoy, Pencom Systems 1097 Paul Traina, Juniper Networks 1098 Andrew Partan, UUNET 1099 Robert Snyder, cisco Systems 1100 Dimitry Haskin, Bay Networks 1101 Peder Chr Norgaard, Telebit Communications A/S 1102 Joel Halpern, NewBridge 1103 Nick Thille, RedBack Networks 1104 Bert Wijnen, IBM 1106 The origin of this document is from RFC 1269 "Definitions of Managed 1107 Objects for the Border Gateway Protocol (Version 3)" written by Steve 1108 Willis and John Burruss, which was updated by John Chu to support 1109 BGP-4 in RFC 1657. The editors wishes to acknowledge the fine work 1110 of these original authors. 1112 8. References 1114 [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC 1115 1771, March 1995. 1117 [2] Rekhter, Y., Gross, P., "Application of the Border Gateway 1118 Protocol in the Internet", RFC 1772, March 1995. 1120 [3] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1121 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1122 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1123 January 1998 1125 [4] Rose, M., and K. McCloghrie, "Structure and Identification of 1126 Management Information for TCP/IP-based Internets", RFC 1155, 1127 Performance Systems International, Hughes LAN Systems, May 1990 1129 [5] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1130 1212, Performance Systems International, Hughes LAN Systems, 1131 March 1991 1133 [6] M. Rose, "A Convention for Defining Traps for use with the 1134 SNMP", RFC 1215, Performance Systems International, March 1991 1136 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1137 "Structure of Management Information for Version 2 of the Simple 1138 Network Management Protocol (SNMPv2)", RFC 1902, SNMP 1139 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, 1140 Inc., International Network Services, January 1996. 1142 [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1143 Conventions for Version 2 of the Simple Network Management 1144 Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco 1145 Systems, Inc., Dover Beach Consulting, Inc., International 1146 Network Services, January 1996. 1148 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1149 "Conformance Statements for Version 2 of the Simple Network 1150 Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 1151 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1152 Network Services, January 1996. 1154 [10] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1155 Network Management Protocol", RFC 1157, SNMP Research, 1156 Performance Systems International, Performance Systems 1157 International, MIT Laboratory for Computer Science, May 1990. 1159 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1160 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 1161 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1162 Inc., International Network Services, January 1996. 1164 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1165 "Transport Mappings for Version 2 of the Simple Network 1166 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 1167 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1168 Network Services, January 1996. 1170 [13] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1171 Processing and Dispatching for the Simple Network Management 1172 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron 1173 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1174 January 1998. 1176 [14] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1177 for version 3 of the Simple Network Management Protocol 1178 (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. 1180 [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1181 Operations for Version 2 of the Simple Network Management 1182 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 1183 Systems, Inc., Dover Beach Consulting, Inc., International 1184 Network Services, January 1996. 1186 [16] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1187 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1188 Systems, January 1998 1190 [17] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1191 Control Model (VACM) for the Simple Network Management Protocol 1192 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, 1193 Inc., Cisco Systems, Inc., January 1998 1195 9. Security Considerations 1197 There are a number of management objects defined in this MIB that 1198 have a MAX-ACCESS clause of read-write: 1199 bgpPeerAdminStatus 1200 bgpPeerConnectRetryInterval 1201 bgpPeerHoldTimeConfigured 1202 bgpPeerKeepAliveConfigured 1203 bgpPeerMinASOriginationInterval 1204 bgpPeerMinRouteAdvertisementInterval 1206 These objects should be considered sensitive or vulnerable in most 1207 network environments. The support for SET operations in a non-secure 1208 environment without proper protection can have a negative effect on 1209 network operations. Incorrect configuration of these parameters may 1210 cause BGP peer connections to terminate early or to send more routes 1211 under a flapping condition. 1213 There are a number of managed objects in this MIB that may be 1214 considered to contain sensitive information in the operation of a 1215 network. For example, a BGP peer's local and remote addresses may be 1216 sensitive for ISPs who want to keep interface addresses on routers 1217 confidential to prevent router addresses used for a denial of service 1218 attack or spoofing. 1220 Therefore, it may be important in some environments to control read 1221 access to these objects and possibly to even encrypt the values of 1222 these object when sending them over the network via SNMP. Not all 1223 versions of SNMP provide features for such a secure environment. 1225 SNMPv1 by itself is not a secure environment. Even if the network 1226 itself is secure (for example by using IPSec), even then, there is no 1227 control as to who on the secure network is allowed to access and 1228 GET/SET (read/change/create/delete) the objects in this MIB. 1230 It is recommended that the implementers consider the security 1231 features as provided by the SNMPv3 framework. Specifically, the use 1232 of the User-based Security Model RFC 2274 [14] and the View-based 1233 Access Control Model RFC 2275 [17] is recommended. 1235 It is then a customer/user responsibility to ensure that the SNMP 1236 entity giving access to an instance of this MIB, is properly 1237 configured to give access to the objects only to those principals 1238 (users) that have legitimate rights to indeed GET or SET 1239 (change/create/delete) them. 1241 10. Authors' Address 1243 Susan Hares 1244 Merit Network, Inc. 1245 4251 Plymouth Road 1246 Suite C 1247 Ann Arbor, MI 48105-2785 1248 Phone: +1 734 936 2095 1249 Fax: +1 734 647 3185 1250 Email: skh@merit.edu 1252 Jeff Johnson 1253 RedBack Networks, Inc. 1254 1389 Moffett Park Drive 1255 Sunnyvale, CA 94089 1256 Phone: +1 408 548 3516 1257 Email: jeff@redback.com 1259 Steve Willis 1260 Argon Networks 1261 25 Porter Road 1262 Littleton, MA 01450 1263 Phone: +1 508 486 0665 1264 Fax: +1 508 486 9379 1265 Email: swills@argon.com 1267 John Burruss 1268 Windata Inc. 1269 543 Great Road 1270 Littleton MA 01460 1271 Phone: +1 508 952 0170 1272 Email: jburruss@windata.com 1274 John Chu 1275 IBM Corporation 1276 P.O.Box 704 1277 Yorktown Heights, NY 10598 1278 Phone: +1 914 784 7839 1279 Email: jychu@watson.ibm.com 1281 11. Full Copyright Statement 1283 Copyright (C) The Internet Society (1999). All Rights Reserved. 1285 This document and translations of it may be copied and furnished to 1286 others, and derivative works that comment on or otherwise explain it 1287 or assist in its implementation may be prepared, copied, published 1288 and distributed, in whole or in part, without restriction of any 1289 kind, provided that the above copyright notice and this paragraph are 1290 included on all such copies and derivative works. However, this 1291 document itself may not be modified in any way, such as by removing 1292 the copyright notice or references to the Internet Society or other 1293 Internet organizations, except as needed for the purpose of 1294 developing Internet standards in which case the procedures for 1295 copyrights defined in the Internet Standards process must be 1296 followed, or as required to translate it into languages other than 1297 English. 1299 The limited permissions granted above are perpetual and will not be 1300 revoked by the Internet Society or its successors or assigns. 1302 This document and the information contained herein is provided on an 1303 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1304 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1305 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1306 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1307 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.