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