idnits 2.17.1 draft-ietf-idr-bgp4-mib-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 34) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an 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.) ** There are 4 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 906: '... the NLRI MUST NOT be made more...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1267 has weird spacing: '... There are ...' == Line 1270 has weird spacing: '...terface addre...' -- 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 (September 2003) is 7523 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'BGP' is mentioned on line 77, but not defined == Missing Reference: 'REF' is mentioned on line 1286, but not defined == Unused Reference: 'BGP4' is defined on line 1334, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 1345, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 1362, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 1366, but no explicit reference was found in the text == Unused Reference: 'RFC3415' is defined on line 1369, but no explicit reference was found in the text == Unused Reference: 'RFC3416' is defined on line 1373, but no explicit reference was found in the text == Unused Reference: 'RFC3417' is defined on line 1377, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 1383, but no explicit reference was found in the text == Unused Reference: 'RFC2576' is defined on line 1387, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'BGP4' ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 2576 (Obsoleted by RFC 3584) Summary: 7 errors (**), 0 flaws (~~), 16 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT BGP4-MIB September 2003 4 Network Working Group Editors of this version: 5 INTERNET DRAFT J. Haas 6 S. Hares 7 NextHop Technologies 8 September 2003 10 Definitions of Managed Objects 11 for the Fourth Version of Border Gateway Protocol (BGP-4) 12 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet- Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Copyright Notice 37 Copyright (C) The Internet Society (2003). All Rights Reserved. 39 Abstract 41 This memo is an extension to the SNMP MIB. The origin of this memo 42 is from RFC 1269 "Definitions of Managed Objects for the Border 43 Gateway Protocol (Version 3)", which was updated to support BGP-4 in 44 RFC 1657. This memo fixes errors introduced when the MIB was 45 converted to use the SNMPv2 SMI, as well as updates references to the 46 current SNMP framework documents. 48 This memo is intended to document deployed implementations of this 49 MIB in a historical context, provide clarifications of some items and 50 also note errors where the MIB fails to fully represent the BGP 51 protocol. Work is currently in progress to replace this MIB with a 52 new one representing the current state of the BGP protocol and its 53 extensions. 55 Distribution of this memo is unlimited. Please forward comments to 56 idr@ietf.org. 58 Table of Contents 60 1. Introduction .................................................. 3 61 2. The Internet-Standard Management Framework .................... 3 62 3. Overview ...................................................... 3 63 4. Definitions ................................................... 4 64 5. Intellectual Property ........................................ 29 65 6. Security Considerations ...................................... 30 66 7. Acknowledgements ............................................. 32 67 8. Normative References ......................................... 33 68 9. Informative References ....................................... 34 69 10. Editors' Address ............................................. 35 70 11. Full Copyright Statement ..................................... 35 72 1. Introduction 74 This memo defines a portion of the Management Information Base (MIB) 75 for use with network management protocols in the Internet community. 76 In particular, it describes managed objects used for managing the 77 Border Gateway Protocol Version 4 or lower [BGP, BGP4APP]. 79 2. The Internet-Standard Management Framework 81 For a detailed overview of the documents that describe the current 82 Internet-Standard Management Framework, please refer to section 7 of 83 RFC 3410 [RFC3410]. 85 Managed objects are accessed via a virtual information store, termed 86 the Management Information Base or MIB. MIB objects are generally 87 accessed through the Simple Network Management Protocol (SNMP). 88 Objects in the MIB are defined using the mechanisms defined in the 89 Structure of Management Information (SMI). This memo specifies a MIB 90 module that is compliant to the SMIv2, which is described in STD 58, 91 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 92 [RFC2580]. 94 3. Overview 96 These objects are used to control and manage a BGP-4 implementation. 98 Apart from a few system-wide scalar objects, this MIB is broken into 99 three tables: the BGP Peer Table, the BGP Received Path Attribute 100 Table, and the BGP-4 Received Path Attribute Table. The BGP Peer 101 Table contains information about state and current activity of 102 connections with the BGP peers. The BGP Received Path Attribute 103 Table contains path attributes received from all peers running BGP 104 version 3 or less. The BGP-4 Received Path Attribute Table contains 105 path attributes received from all BGP-4 peers. The actual attributes 106 used in determining a route are a subset of the received attribute 107 tables after local routing policy has been applied. 109 4. Definitions 111 BGP4-MIB DEFINITIONS ::= BEGIN 113 IMPORTS 114 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 115 IpAddress, Integer32, Counter32, Gauge32, mib-2 116 FROM SNMPv2-SMI 117 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 118 FROM SNMPv2-CONF; 120 bgp MODULE-IDENTITY 121 LAST-UPDATED "200309050000Z" 122 ORGANIZATION "IETF IDR Working Group" 123 CONTACT-INFO "E-mail: idr@ietf.org 125 Jeffrey Haas, Susan Hares (Editors) 126 NextHop Technologies 127 825 Victors Way 128 Suite 100 129 Ann Arbor, MI 48108-2738 130 Tel: +1 734 222-1600 131 Fax: +1 734 222-1602 132 E-mail: jhaas@nexthop.com 133 skh@nexthop.com" 135 DESCRIPTION 136 "The MIB module for the BGP-4 protocol. 138 Copyright (C) The Internet Society (2003). This version 139 of this MIB module is part of RFC yyyy; see the RFC 140 itself for full legal notices." 142 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 144 REVISION "200309050000Z" 145 DESCRIPTION 146 "Changes from RFC 1657: 148 1) Fixed the definitions of the traps to 149 make them equivalent to their initial 150 definition in RFC 1269. 151 2) Added compliance and conformance info. 152 3) Updated information for the values of 153 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, 154 bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, 155 bgp4PathAttrASPathSegement. 156 4) Added additional clarification comments where 157 needed. 158 5) Noted where objects do not fully reflect 159 the protocol as Known Issues. 160 6) Updated the DESCRIPTION for the 161 bgp4PathAttrAtomicAggregate object. 162 7) The following objects have had their DESCRIPTION 163 clause modified to remove the requirement to 164 reset the counter to zero on a transition to 165 the established state: 166 bgpPeerInUpdates, bgpPeerOutUpdates, 167 bgpPeerInTotalMessages, bgpPeerOutTotalMessages" 168 ::= { mib-2 15 } 170 bgpVersion OBJECT-TYPE 171 SYNTAX OCTET STRING (SIZE (1..255)) 172 MAX-ACCESS read-only 173 STATUS current 174 DESCRIPTION 175 "Vector of supported BGP protocol version 176 numbers. Each peer negotiates the version 177 from this vector. Versions are identified 178 via the string of bits contained within this 179 object. The first octet contains bits 0 to 180 7, the second octet contains bits 8 to 15, 181 and so on, with the most significant bit 182 referring to the lowest bit number in the 183 octet (e.g., the MSB of the first octet 184 refers to bit 0). If a bit, i, is present 185 and set, then the version (i+1) of the BGP 186 is supported." 187 ::= { bgp 1 } 189 bgpLocalAs OBJECT-TYPE 190 SYNTAX Integer32 (0..65535) 191 MAX-ACCESS read-only 192 STATUS current 193 DESCRIPTION 194 "The local autonomous system number." 195 ::= { bgp 2 } 197 -- BGP Peer table. This table contains, one entry per 198 -- BGP peer, information about the BGP peer. 200 bgpPeerTable OBJECT-TYPE 201 SYNTAX SEQUENCE OF BgpPeerEntry 202 MAX-ACCESS not-accessible 203 STATUS current 204 DESCRIPTION 205 "BGP peer table. This table contains, 206 one entry per BGP peer, information about the 207 connections with BGP peers." 208 ::= { bgp 3 } 210 bgpPeerEntry OBJECT-TYPE 211 SYNTAX BgpPeerEntry 212 MAX-ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "Entry containing information about the 216 connection with a BGP peer." 217 INDEX { bgpPeerRemoteAddr } 218 ::= { bgpPeerTable 1 } 220 BgpPeerEntry ::= SEQUENCE { 221 bgpPeerIdentifier 222 IpAddress, 223 bgpPeerState 224 INTEGER, 225 bgpPeerAdminStatus 226 INTEGER, 227 bgpPeerNegotiatedVersion 228 Integer32, 229 bgpPeerLocalAddr 230 IpAddress, 231 bgpPeerLocalPort 232 Integer32, 233 bgpPeerRemoteAddr 234 IpAddress, 235 bgpPeerRemotePort 236 Integer32, 237 bgpPeerRemoteAs 238 Integer32, 239 bgpPeerInUpdates 240 Counter32, 241 bgpPeerOutUpdates 242 Counter32, 244 bgpPeerInTotalMessages 245 Counter32, 246 bgpPeerOutTotalMessages 247 Counter32, 248 bgpPeerLastError 249 OCTET STRING, 250 bgpPeerFsmEstablishedTransitions 251 Counter32, 252 bgpPeerFsmEstablishedTime 253 Gauge32, 254 bgpPeerConnectRetryInterval 255 Integer32, 256 bgpPeerHoldTime 257 Integer32, 258 bgpPeerKeepAlive 259 Integer32, 260 bgpPeerHoldTimeConfigured 261 Integer32, 262 bgpPeerKeepAliveConfigured 263 Integer32, 264 bgpPeerMinASOriginationInterval 265 Integer32, 266 bgpPeerMinRouteAdvertisementInterval 267 Integer32, 268 bgpPeerInUpdateElapsedTime 269 Gauge32 270 } 272 bgpPeerIdentifier OBJECT-TYPE 273 SYNTAX IpAddress 274 MAX-ACCESS read-only 275 STATUS current 276 DESCRIPTION 277 "The BGP Identifier of this entry's BGP peer. 278 This entry should be 0.0.0.0 unless the 279 bgpPeerState is in the openconfirm or the 280 established state." 281 ::= { bgpPeerEntry 1 } 283 bgpPeerState OBJECT-TYPE 284 SYNTAX INTEGER { 285 idle(1), 286 connect(2), 287 active(3), 288 opensent(4), 289 openconfirm(5), 290 established(6) 291 } 292 MAX-ACCESS read-only 293 STATUS current 294 DESCRIPTION 295 "The BGP peer connection state." 296 ::= { bgpPeerEntry 2 } 298 bgpPeerAdminStatus OBJECT-TYPE 299 SYNTAX INTEGER { 300 stop(1), 301 start(2) 302 } 303 MAX-ACCESS read-write 304 STATUS current 305 DESCRIPTION 306 "The desired state of the BGP connection. 307 A transition from 'stop' to 'start' will 308 cause the BGP Start Event to be generated. 309 A transition from 'start' to 'stop' will 310 cause the BGP Stop Event to be generated. 311 This parameter can be used to restart BGP 312 peer connections. Care should be used in 313 providing write access to this object 314 without adequate authentication." 315 ::= { bgpPeerEntry 3 } 317 bgpPeerNegotiatedVersion OBJECT-TYPE 318 SYNTAX Integer32 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "The negotiated version of BGP running between 323 the two peers. 325 This entry should be zero (0) unless the 326 bgpPeerState is in the openconfirm or the 327 established state. 329 Note that legal values should be between 0 330 and 255." 331 ::= { bgpPeerEntry 4 } 333 bgpPeerLocalAddr OBJECT-TYPE 334 SYNTAX IpAddress 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "The local IP address of this entry's BGP 339 connection." 340 ::= { bgpPeerEntry 5 } 342 bgpPeerLocalPort OBJECT-TYPE 343 SYNTAX Integer32 (0..65535) 344 MAX-ACCESS read-only 345 STATUS current 346 DESCRIPTION 347 "The local port for the TCP connection between 348 the BGP peers." 349 ::= { bgpPeerEntry 6 } 351 bgpPeerRemoteAddr OBJECT-TYPE 352 SYNTAX IpAddress 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The remote IP address of this entry's BGP 357 peer." 358 ::= { bgpPeerEntry 7 } 360 bgpPeerRemotePort OBJECT-TYPE 361 SYNTAX Integer32 (0..65535) 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "The remote port for the TCP connection 366 between the BGP peers. Note that the 367 objects bgpPeerLocalAddr, 368 bgpPeerLocalPort, bgpPeerRemoteAddr and 369 bgpPeerRemotePort provide the appropriate 370 reference to the standard MIB TCP 371 connection table." 372 ::= { bgpPeerEntry 8 } 374 bgpPeerRemoteAs OBJECT-TYPE 375 SYNTAX Integer32 (0..65535) 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "The remote autonomous system number." 380 ::= { bgpPeerEntry 9 } 382 bgpPeerInUpdates OBJECT-TYPE 383 SYNTAX Counter32 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The number of BGP UPDATE messages 388 received on this connection." 389 ::= { bgpPeerEntry 10 } 391 bgpPeerOutUpdates OBJECT-TYPE 392 SYNTAX Counter32 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "The number of BGP UPDATE messages 397 transmitted on this connection." 398 ::= { bgpPeerEntry 11 } 400 bgpPeerInTotalMessages OBJECT-TYPE 401 SYNTAX Counter32 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "The total number of messages received 406 from the remote peer on this connection." 407 ::= { bgpPeerEntry 12 } 409 bgpPeerOutTotalMessages OBJECT-TYPE 410 SYNTAX Counter32 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The total number of messages transmitted to 415 the remote peer on this connection." 416 ::= { bgpPeerEntry 13 } 418 bgpPeerLastError OBJECT-TYPE 419 SYNTAX OCTET STRING (SIZE (2)) 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "The last error code and subcode seen by this 424 peer on this connection. If no error has 425 occurred, this field is zero. Otherwise, the 426 first byte of this two byte OCTET STRING 427 contains the error code, and the second byte 428 contains the subcode." 429 ::= { bgpPeerEntry 14 } 431 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 432 SYNTAX Counter32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The total number of times the BGP FSM 437 transitioned into the established state 438 for this peer." 439 ::= { bgpPeerEntry 15 } 441 bgpPeerFsmEstablishedTime OBJECT-TYPE 442 SYNTAX Gauge32 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "This timer indicates how long (in 447 seconds) this peer has been in the 448 established state or how long 449 since this peer was last in the 450 established state. It is set to zero when 451 a new peer is configured or the router is 452 booted." 453 ::= { bgpPeerEntry 16 } 455 bgpPeerConnectRetryInterval OBJECT-TYPE 456 SYNTAX Integer32 (1..65535) 457 MAX-ACCESS read-write 458 STATUS current 459 DESCRIPTION 460 "Time interval in seconds for the 461 ConnectRetry timer. The suggested value 462 for this timer is 120 seconds." 463 ::= { bgpPeerEntry 17 } 465 bgpPeerHoldTime OBJECT-TYPE 466 SYNTAX Integer32 ( 0 | 3..65535 ) 467 MAX-ACCESS read-only 468 STATUS current 469 DESCRIPTION 470 "Time interval in seconds for the Hold 471 Timer established with the peer. The 472 value of this object is calculated by this 473 BGP speaker by using the smaller of the 474 value in bgpPeerHoldTimeConfigured and the 475 Hold Time received in the OPEN message. 476 This value must be at least three seconds 477 if it is not zero (0). If the value is 478 zero (0), the Hold Timer has either not been 479 established with the peer, or, the value of 480 bgpPeerHoldTimeConfigured is zero (0)." 481 ::= { bgpPeerEntry 18 } 483 bgpPeerKeepAlive OBJECT-TYPE 484 SYNTAX Integer32 ( 0 | 1..21845 ) 485 MAX-ACCESS read-only 486 STATUS current 487 DESCRIPTION 488 "Time interval in seconds for the KeepAlive 489 timer established with the peer. The value 490 of this object is calculated by this BGP 491 speaker such that, when compared with 492 bgpPeerHoldTime, it has the same proportion 493 as what bgpPeerKeepAliveConfigured has when 494 compared with bgpPeerHoldTimeConfigured. If 495 the value of this object is zero (0), it 496 indicates that the KeepAlive timer has not 497 been established with the peer, or, the value 498 of bgpPeerKeepAliveConfigured is zero (0)." 499 ::= { bgpPeerEntry 19 } 501 bgpPeerHoldTimeConfigured OBJECT-TYPE 502 SYNTAX Integer32 ( 0 | 3..65535 ) 503 MAX-ACCESS read-write 504 STATUS current 505 DESCRIPTION 506 "Time interval in seconds for the Hold Time 507 configured for this BGP speaker with this 508 peer. This value is placed in an OPEN 509 message sent to this peer by this BGP 510 speaker, and is compared with the Hold 511 Time field in an OPEN message received 512 from the peer when determining the Hold 513 Time (bgpPeerHoldTime) with the peer. 514 This value must not be less than three 515 seconds if it is not zero (0) in which 516 case the Hold Time is NOT to be 517 established with the peer. The suggested 518 value for this timer is 90 seconds." 519 ::= { bgpPeerEntry 20 } 521 bgpPeerKeepAliveConfigured OBJECT-TYPE 522 SYNTAX Integer32 ( 0 | 1..21845 ) 523 MAX-ACCESS read-write 524 STATUS current 525 DESCRIPTION 526 "Time interval in seconds for the 527 KeepAlive timer configured for this BGP 528 speaker with this peer. The value of this 529 object will only determine the 530 KEEPALIVE messages' frequency relative to 531 the value specified in 532 bgpPeerHoldTimeConfigured; the actual 533 time interval for the KEEPALIVE messages is 534 indicated by bgpPeerKeepAlive. A 535 reasonable maximum value for this timer 536 would be configured to be one 537 third of that of 538 bgpPeerHoldTimeConfigured. 539 If the value of this object is zero (0), 540 no periodical KEEPALIVE messages are sent 541 to the peer after the BGP connection has 542 been established. The suggested value for 543 this timer is 30 seconds." 544 ::= { bgpPeerEntry 21 } 546 bgpPeerMinASOriginationInterval OBJECT-TYPE 547 SYNTAX Integer32 (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 554 seconds." 555 ::= { bgpPeerEntry 22 } 557 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 558 SYNTAX Integer32 (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 565 seconds." 566 ::= { bgpPeerEntry 23 } 568 bgpPeerInUpdateElapsedTime OBJECT-TYPE 569 SYNTAX Gauge32 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "Elapsed time in seconds since the last BGP 574 UPDATE message was received from the peer. 575 Each time bgpPeerInUpdates is incremented, 576 the value of this object is set to zero (0)." 577 ::= { bgpPeerEntry 24 } 579 bgpIdentifier OBJECT-TYPE 580 SYNTAX IpAddress 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The BGP Identifier of local system." 585 ::= { bgp 4 } 587 -- BGP Received Path Attribute Table. This table contains, 588 -- one entry per path to a network, path attributes 589 -- received from all peers running BGP version 3 or less. 590 -- This table is deprecated, having been replaced in 591 -- functionality with the bgp4PathAttrTable. 593 bgpRcvdPathAttrTable OBJECT-TYPE 594 SYNTAX SEQUENCE OF BgpPathAttrEntry 595 MAX-ACCESS not-accessible 596 STATUS deprecated 597 DESCRIPTION 598 "The BGP Received Path Attribute Table 599 contains information about paths to 600 destination networks received from all 601 peers running BGP version 3 or less." 602 ::= { bgp 5 } 604 bgpPathAttrEntry OBJECT-TYPE 605 SYNTAX BgpPathAttrEntry 606 MAX-ACCESS not-accessible 607 STATUS deprecated 608 DESCRIPTION 609 "Information about a path to a network." 610 INDEX { bgpPathAttrDestNetwork, 611 bgpPathAttrPeer } 612 ::= { bgpRcvdPathAttrTable 1 } 614 BgpPathAttrEntry ::= SEQUENCE { 615 bgpPathAttrPeer 616 IpAddress, 617 bgpPathAttrDestNetwork 618 IpAddress, 619 bgpPathAttrOrigin 620 INTEGER, 621 bgpPathAttrASPath 622 OCTET STRING, 623 bgpPathAttrNextHop 624 IpAddress, 625 bgpPathAttrInterASMetric 626 Integer32 627 } 629 bgpPathAttrPeer OBJECT-TYPE 630 SYNTAX IpAddress 631 MAX-ACCESS read-only 632 STATUS deprecated 633 DESCRIPTION 634 "The IP address of the peer where the path 635 information was learned." 636 ::= { bgpPathAttrEntry 1 } 638 bgpPathAttrDestNetwork OBJECT-TYPE 639 SYNTAX IpAddress 640 MAX-ACCESS read-only 641 STATUS deprecated 642 DESCRIPTION 643 "The address of the destination network." 644 ::= { bgpPathAttrEntry 2 } 646 bgpPathAttrOrigin OBJECT-TYPE 647 SYNTAX INTEGER { 648 igp(1),-- networks are interior 649 egp(2),-- networks learned via the 650 -- EGP protocol 651 incomplete(3) -- networks that 652 -- are learned by some other 653 -- means 654 } 655 MAX-ACCESS read-only 656 STATUS deprecated 657 DESCRIPTION 658 "The ultimate origin of the path information." 659 ::= { bgpPathAttrEntry 3 } 661 bgpPathAttrASPath OBJECT-TYPE 662 SYNTAX OCTET STRING (SIZE (2..255)) 663 MAX-ACCESS read-only 664 STATUS deprecated 665 DESCRIPTION 666 "The set of ASs that must be traversed to reach 667 the network. This object is probably best 668 represented as SEQUENCE OF INTEGER. For SMI 669 compatibility, though, it is represented as 670 OCTET STRING. Each AS is represented as a pair 671 of octets according to the following algorithm: 673 first-byte-of-pair = ASNumber / 256; 674 second-byte-of-pair = ASNumber & 255;" 675 ::= { bgpPathAttrEntry 4 } 677 bgpPathAttrNextHop OBJECT-TYPE 678 SYNTAX IpAddress 679 MAX-ACCESS read-only 680 STATUS deprecated 681 DESCRIPTION 682 "The address of the border router that should 683 be used for the destination network." 684 ::= { bgpPathAttrEntry 5 } 686 bgpPathAttrInterASMetric OBJECT-TYPE 687 SYNTAX Integer32 688 MAX-ACCESS read-only 689 STATUS deprecated 690 DESCRIPTION 691 "The optional inter-AS metric. If this 692 attribute has not been provided for this route, 693 the value for this object is 0." 694 ::= { bgpPathAttrEntry 6 } 696 -- BGP-4 Received Path Attribute Table. This table 697 -- contains, one entry per path to a network, path 698 -- attributes received from all peers running BGP-4. 700 bgp4PathAttrTable OBJECT-TYPE 701 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 702 MAX-ACCESS not-accessible 703 STATUS current 704 DESCRIPTION 705 "The BGP-4 Received Path Attribute Table 706 contains information about paths to 707 destination networks received from all 708 BGP4 peers." 709 ::= { bgp 6 } 711 bgp4PathAttrEntry OBJECT-TYPE 712 SYNTAX Bgp4PathAttrEntry 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "Information about a path to a network." 717 INDEX { bgp4PathAttrIpAddrPrefix, 718 bgp4PathAttrIpAddrPrefixLen, 719 bgp4PathAttrPeer } 720 ::= { bgp4PathAttrTable 1 } 722 Bgp4PathAttrEntry ::= SEQUENCE { 723 bgp4PathAttrPeer 724 IpAddress, 725 bgp4PathAttrIpAddrPrefixLen 726 Integer32, 727 bgp4PathAttrIpAddrPrefix 728 IpAddress, 729 bgp4PathAttrOrigin 730 INTEGER, 731 bgp4PathAttrASPathSegment 732 OCTET STRING, 733 bgp4PathAttrNextHop 734 IpAddress, 735 bgp4PathAttrMultiExitDisc 736 Integer32, 737 bgp4PathAttrLocalPref 738 Integer32, 739 bgp4PathAttrAtomicAggregate 740 INTEGER, 741 bgp4PathAttrAggregatorAS 742 Integer32, 743 bgp4PathAttrAggregatorAddr 744 IpAddress, 745 bgp4PathAttrCalcLocalPref 746 Integer32, 747 bgp4PathAttrBest 748 INTEGER, 749 bgp4PathAttrUnknown 750 OCTET STRING 751 } 753 bgp4PathAttrPeer OBJECT-TYPE 754 SYNTAX IpAddress 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "The IP address of the peer where the path 759 information was learned." 760 ::= { bgp4PathAttrEntry 1 } 762 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 763 SYNTAX Integer32 (0..32) 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "Length in bits of the IP address prefix in 768 the Network Layer Reachability 769 Information field." 770 ::= { bgp4PathAttrEntry 2 } 772 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 773 SYNTAX IpAddress 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "An IP address prefix in the Network Layer 778 Reachability Information field. This object 779 is an IP address containing the prefix with 780 length specified by 781 bgp4PathAttrIpAddrPrefixLen. 782 Any bits beyond the length specified by 783 bgp4PathAttrIpAddrPrefixLen are zeroed." 784 ::= { bgp4PathAttrEntry 3 } 786 bgp4PathAttrOrigin OBJECT-TYPE 787 SYNTAX INTEGER { 788 igp(1),-- networks are interior 789 egp(2),-- networks learned via the 790 -- EGP protocol 791 incomplete(3) -- networks that 792 -- are learned by some other 793 -- means 794 } 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "The ultimate origin of the path 799 information." 800 ::= { bgp4PathAttrEntry 4 } 802 bgp4PathAttrASPathSegment OBJECT-TYPE 803 SYNTAX OCTET STRING (SIZE (2..255)) 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "The sequence of AS path segments. Each AS 808 path segment is represented by a triple 809 . 811 The type is a 1-octet field which has two 812 possible values: 813 1 AS_SET: unordered set of ASs a 814 route in the UPDATE message 815 has traversed 817 2 AS_SEQUENCE: ordered set of ASs 818 a route in the UPDATE message 819 has traversed. 821 The length is a 1-octet field containing the 822 number of ASs in the value field. 824 The value field contains one or more AS 825 numbers, each AS is represented in the octet 826 string as a pair of octets according to the 827 following algorithm: 829 first-byte-of-pair = ASNumber / 256; 830 second-byte-of-pair = ASNumber & 255; 832 Known Issues: 833 o BGP Confederations will result in 834 a type of value of either 3 or 4. 835 o An AS Path may be longer than 255 octets. 836 This may result in this object containing 837 a truncated AS Path." 838 ::= { bgp4PathAttrEntry 5 } 840 bgp4PathAttrNextHop OBJECT-TYPE 841 SYNTAX IpAddress 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "The address of the border router that 846 should be used for the destination 847 network. This address is the nexthop 848 address received in the UPDATE packet." 849 ::= { bgp4PathAttrEntry 6 } 851 bgp4PathAttrMultiExitDisc OBJECT-TYPE 852 SYNTAX Integer32 (-1..2147483647) 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "This metric is used to discriminate 857 between multiple exit points to an 858 adjacent autonomous system. A value of -1 859 indicates the absence of this attribute. 861 Known Issues: 862 o The BGP-4 specification uses an 863 unsigned 32 bit number and thus this 864 object cannot represent the full 865 range of the protocol." 866 ::= { bgp4PathAttrEntry 7 } 868 bgp4PathAttrLocalPref OBJECT-TYPE 869 SYNTAX Integer32 (-1..2147483647) 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 "The originating BGP4 speaker's degree of 874 preference for an advertised route. A 875 value of -1 indicates the absence of this 876 attribute. 878 Known Issues: 879 o The BGP-4 specification uses an 880 unsigned 32 bit number and thus this 881 object cannot represent the full 882 range of the protocol." 883 ::= { bgp4PathAttrEntry 8 } 885 bgp4PathAttrAtomicAggregate OBJECT-TYPE 886 SYNTAX INTEGER { 887 lessSpecificRouteNotSelected(1), 888 -- Typo corrected from RFC 1657 889 lessSpecificRouteSelected(2) 890 } 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "The original text for this object was: 896 Whether or not a system has selected 897 a less specific route without 898 selecting a more specific route. 900 However, as of the current version of the BGP 901 specification, ATOMIC_AGGREGATE has been 902 deprecated. In this MIB, the value of this 903 object will be lessSpecificRouteNotSelected 904 if the ATOMIC_AGGREGATE attribute is present 905 in the Path Attributes and indicates that 906 the NLRI MUST NOT be made more specific. 908 The value should be lessSpecificRouteSelected 909 if the ATOMIC_AGGREGATE attribute is missing 910 in the Path Attributes." 911 ::= { bgp4PathAttrEntry 9 } 913 bgp4PathAttrAggregatorAS OBJECT-TYPE 914 SYNTAX Integer32 (0..65535) 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "The AS number of the last BGP4 speaker that 919 performed route aggregation. A value of 920 zero (0) indicates the absence of this 921 attribute. 923 Note that propagation of AS of zero is illegal 924 in the Internet." 925 ::= { bgp4PathAttrEntry 10 } 927 bgp4PathAttrAggregatorAddr OBJECT-TYPE 928 SYNTAX IpAddress 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The IP address of the last BGP4 speaker 933 that performed route aggregation. A 934 value of 0.0.0.0 indicates the absence 935 of this attribute." 936 ::= { bgp4PathAttrEntry 11 } 938 bgp4PathAttrCalcLocalPref OBJECT-TYPE 939 SYNTAX Integer32 (-1..2147483647) 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The degree of preference calculated by the 944 receiving BGP4 speaker for an advertised 945 route. A value of -1 indicates the 946 absence of this attribute. 948 Known Issues: 949 o The BGP-4 specification uses an 950 unsigned 32 bit number and thus this 951 object cannot represent the full 952 range of the protocol." 953 ::= { bgp4PathAttrEntry 12 } 955 bgp4PathAttrBest OBJECT-TYPE 956 SYNTAX INTEGER { 957 false(1),-- not chosen as best route 958 true(2) -- chosen as best route 959 } 960 MAX-ACCESS read-only 961 STATUS current 962 DESCRIPTION 963 "An indication of whether or not this route 964 was chosen as the best BGP4 route for this 965 destination." 966 ::= { bgp4PathAttrEntry 13 } 968 bgp4PathAttrUnknown OBJECT-TYPE 969 SYNTAX OCTET STRING (SIZE(0..255)) 970 MAX-ACCESS read-only 971 STATUS current 972 DESCRIPTION 973 "One or more path attributes not understood 974 this BGP4 speaker. 976 Path attributes are recorded in the Update Path 977 attribute format of type, length, value. 979 Size zero (0) indicates the absence of such 980 attributes. 982 Octets beyond the maximum size, if any, are not 983 recorded by this object. 985 Known Issues: 986 o Attributes understood by this speaker, but not 987 represented in this MIB, are unavailable to 988 the agent." 989 ::= { bgp4PathAttrEntry 14 } 991 -- Traps. 993 -- Note that in RFC 1657, bgpTraps was incorrectly 994 -- assigned a value of { bgp 7 } and each of the 995 -- traps had the bgpPeerRemoteAddr object inappropriately 996 -- removed from their OBJECTS clause. The following 997 -- definitions restore the semantics of the traps as 998 -- they were initially defined in RFC 1269. 1000 bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } 1002 bgpEstablishedNotification NOTIFICATION-TYPE 1003 OBJECTS { bgpPeerRemoteAddr, 1004 bgpPeerLastError, 1005 bgpPeerState } 1006 STATUS current 1007 DESCRIPTION 1008 "The BGP Established event is generated when 1009 the BGP FSM enters the ESTABLISHED state. 1011 This object deprecates bgpEstablished." 1012 ::= { bgpNotification 1 } 1014 bgpBackwardTransNotification NOTIFICATION-TYPE 1015 OBJECTS { bgpPeerRemoteAddr, 1016 bgpPeerLastError, 1017 bgpPeerState } 1018 STATUS current 1019 DESCRIPTION 1020 "The BGPBackwardTransNotification Event is 1021 generated when the BGP FSM moves from a higher 1022 numbered state to a lower numbered state. 1024 This object deprecates bgpBackwardsTransition." 1025 ::= { bgpNotification 2 } 1027 -- { bgp 7 } is deprecated 1029 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } 1031 bgpEstablished NOTIFICATION-TYPE 1032 OBJECTS { bgpPeerLastError, 1033 bgpPeerState } 1034 STATUS deprecated 1035 DESCRIPTION 1036 "The BGP Established event is generated when 1037 the BGP FSM enters the ESTABLISHED state. 1039 This object has been deprecated in favor of 1040 bgpEstablishedNotification." 1041 ::= { bgpTraps 1 } 1043 bgpBackwardTransition NOTIFICATION-TYPE 1044 OBJECTS { bgpPeerLastError, 1045 bgpPeerState } 1047 STATUS deprecated 1048 DESCRIPTION 1049 "The BGPBackwardTransition Event is generated 1050 when the BGP FSM moves from a higher numbered 1051 state to a lower numbered state. 1053 This object has been deprecated in favor of 1054 bgpBackwardTransNotification." 1055 ::= { bgpTraps 2 } 1057 -- Conformance information 1059 bgp4MIBConformance OBJECT IDENTIFIER 1060 ::= { bgp 8 } 1061 bgp4MIBCompliances OBJECT IDENTIFIER 1062 ::= { bgp4MIBConformance 1 } 1063 bgp4MIBGroups OBJECT IDENTIFIER 1064 ::= { bgp4MIBConformance 2 } 1066 -- Compliance statements 1068 bgp4MIBCompliance MODULE-COMPLIANCE 1069 STATUS current 1070 DESCRIPTION 1071 "The compliance statement for entities which 1072 implement the BGP4 mib." 1073 MODULE -- this module 1074 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 1075 bgp4MIBPeerGroup, 1076 bgp4MIBPathAttrGroup } 1077 GROUP bgp4MIBNotificationGroup 1078 DESCRIPTION 1079 "Implementation of BGP Notifications are 1080 completely optional in this MIB." 1081 ::= { bgp4MIBCompliances 1 } 1083 bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE 1084 STATUS deprecated 1085 DESCRIPTION 1086 "The compliance statement documenting deprecated 1087 objects in the BGP4 mib." 1088 MODULE -- this module 1089 GROUP bgp4MIBRcvdPathAttrGroup 1090 DESCRIPTION 1091 "Group containing objects relevant to BGP-3 1092 and earlier objects." 1093 GROUP bgp4MIBTrapGroup 1094 DESCRIPTION 1095 "Group containing TRAP objects that were 1096 improperly converted from SMIv1 in RFC 1657. 1097 The proper semantics have been restored 1098 with the objects in bgp4MIBNotificationGroup." 1099 ::= { bgp4MIBCompliances 2 } 1101 -- Units of conformance 1103 bgp4MIBGlobalsGroup OBJECT-GROUP 1104 OBJECTS { bgpVersion, 1105 bgpLocalAs, 1106 bgpIdentifier } 1107 STATUS current 1108 DESCRIPTION 1109 "A collection of objects providing 1110 information on global BGP state." 1111 ::= { bgp4MIBGroups 1 } 1113 bgp4MIBPeerGroup OBJECT-GROUP 1114 OBJECTS { bgpPeerIdentifier, 1115 bgpPeerState, 1116 bgpPeerAdminStatus, 1117 bgpPeerNegotiatedVersion, 1118 bgpPeerLocalAddr, 1119 bgpPeerLocalPort, 1120 bgpPeerRemoteAddr, 1121 bgpPeerRemotePort, 1122 bgpPeerRemoteAs, 1123 bgpPeerInUpdates, 1124 bgpPeerOutUpdates, 1125 bgpPeerInTotalMessages, 1126 bgpPeerOutTotalMessages, 1127 bgpPeerLastError, 1128 bgpPeerFsmEstablishedTransitions, 1129 bgpPeerFsmEstablishedTime, 1130 bgpPeerConnectRetryInterval, 1131 bgpPeerHoldTime, 1132 bgpPeerKeepAlive, 1133 bgpPeerHoldTimeConfigured, 1134 bgpPeerKeepAliveConfigured, 1135 bgpPeerMinASOriginationInterval, 1136 bgpPeerMinRouteAdvertisementInterval, 1137 bgpPeerInUpdateElapsedTime } 1138 STATUS current 1139 DESCRIPTION 1140 "A collection of objects for managing 1141 BGP peers." 1142 ::= { bgp4MIBGroups 2 } 1144 bgp4MIBRcvdPathAttrGroup OBJECT-GROUP 1145 OBJECTS { bgpPathAttrPeer, 1146 bgpPathAttrDestNetwork, 1147 bgpPathAttrOrigin, 1148 bgpPathAttrASPath, 1149 bgpPathAttrNextHop, 1150 bgpPathAttrInterASMetric } 1151 STATUS deprecated 1152 DESCRIPTION 1153 "A collection of objects for managing BGP-3 and 1154 earlier path entries. 1156 This conformance group is deprecated." 1157 ::= { bgp4MIBGroups 3 } 1159 bgp4MIBPathAttrGroup OBJECT-GROUP 1160 OBJECTS { bgp4PathAttrPeer, 1161 bgp4PathAttrIpAddrPrefixLen, 1162 bgp4PathAttrIpAddrPrefix, 1163 bgp4PathAttrOrigin, 1164 bgp4PathAttrASPathSegment, 1165 bgp4PathAttrNextHop, 1166 bgp4PathAttrMultiExitDisc, 1167 bgp4PathAttrLocalPref, 1168 bgp4PathAttrAtomicAggregate, 1169 bgp4PathAttrAggregatorAS, 1170 bgp4PathAttrAggregatorAddr, 1171 bgp4PathAttrCalcLocalPref, 1172 bgp4PathAttrBest, 1173 bgp4PathAttrUnknown } 1174 STATUS current 1175 DESCRIPTION 1176 "A collection of objects for managing 1177 BGP path entries." 1178 ::= { bgp4MIBGroups 4 } 1180 bgp4MIBTrapGroup NOTIFICATION-GROUP 1181 NOTIFICATIONS { bgpEstablished, 1182 bgpBackwardTransition } 1183 STATUS deprecated 1184 DESCRIPTION 1185 "A collection of notifications for signaling 1186 changes in BGP peer relationships. 1188 Obsoleted by bgp4MIBNotificationGroup" 1189 ::= { bgp4MIBGroups 5 } 1191 bgp4MIBNotificationGroup NOTIFICATION-GROUP 1192 NOTIFICATIONS { bgpEstablishedNotification, 1193 bgpBackwardTransNotification } 1194 STATUS current 1195 DESCRIPTION 1196 "A collection of notifications for signaling 1197 changes in BGP peer relationships. 1199 Obsoletes bgp4MIBNotificationGroup." 1200 ::= { bgp4MIBGroups 6 } 1202 END 1204 5. Intellectual Property 1206 The IETF takes no position regarding the validity or scope of any 1207 intellectual property or other rights that might be claimed to 1208 pertain to the implementation or use of the technology described in 1209 this document or the extent to which any license under such rights 1210 might or might not be available; neither does it represent that it 1211 has made any effort to identify any such rights. Information on the 1212 IETF's procedures with respect to rights in standards-track and 1213 standards-related documentation can be found in BCP-11. Copies of 1214 claims of rights made available for publication and any assurances of 1215 licenses to be made available, or the result of an attempt made to 1216 obtain a general license or permission for the use of such 1217 proprietary rights by implementors or users of this specification can 1218 be obtained from the IETF Secretariat. 1220 The IETF invites any interested party to bring to its attention any 1221 copyrights, patents or patent applications, or other proprietary 1222 rights which may cover technology that may be required to practice 1223 this standard. Please address the information to the IETF Executive 1224 Director. 1226 6. Security Considerations 1228 This MIB relates to a system providing inter-domain routing. As 1229 such, improper manipulation of the objects represented by this MIB 1230 may result in denial of service to a large number of end-users. 1232 There are several management objects defined in this MIB that have a 1233 MAX-ACCESS clause of read-write and/or read-create. Such objects 1234 should be considered sensitive or vulnerable in most network 1235 environments. The support for SET operations in a non-secure 1236 environment without proper protection can have a negative effect on 1237 network operations. These objects include: 1239 o bgpPeerAdminStatus 1241 Improper change of bgpPeerAdminStatus from start to stop can 1242 cause significant disruption of the connectivity to those 1243 portions of the Internet reached via the applicable remote BGP 1244 peer. 1246 o bgpPeerConnectRetryInterval 1248 Improper change of this object can cause connections to be 1249 disrupted for extremely long time periods when otherwise they 1250 would be restored in a relatively short period of time. 1252 o bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured 1254 Misconfiguration of these objects can make BGP sessions more 1255 fragile and less resilient to denial of service attacks on the 1256 inter-domain routing system. 1258 o bgpPeerMinASOriginationInterval, 1259 bgpPeerMinRouteAdvertisementInterval 1261 Misconfiguration of these objects may adversely affect global 1262 Internet convergence of the routes advertised by this BGP 1263 speaker. This may result in long-lived routing loops and 1264 blackholes for the portions of the Internet that utilize these 1265 routes." 1267 There are a number of managed objects in this MIB that 1268 contain sensitive information regarding the operation of a network. 1269 For example, a BGP peer's local and remote addresses might be 1270 sensitive for ISPs who want to keep interface addresses on routers 1271 confidential to prevent router addresses used for a denial of service 1272 attack or spoofing. 1274 Therefore, it is important in most environments to control read 1275 access to these objects and possibly to even encrypt the values of 1276 these object when sending them over the network via SNMP. 1278 SNMPv1 by itself is not a secure environment. Even if the network 1279 itself is secure (for example by using IPSec), there is still no 1280 control as to who on the secure network is allowed to access and 1281 GET/SET (read/change/create/delete) the objects in this MIB. 1283 It is recommended that the implementers consider the security 1284 features as provided by the SNMPv3 framework.[REF] Specifically, the 1285 implementation and use of the User-based Security Model [REF] and the 1286 View-based Access Control Model [REF] is recommended to provide 1287 appropriate security controls. 1289 It is then an operator/user responsibility to ensure that the SNMP 1290 entity giving access to an instance of this MIB, is properly 1291 configured to give access to the objects only to those principals 1292 (users) that have legitimate rights to indeed GET or SET 1293 (change/create/delete) them. 1295 7. Acknowledgements 1297 We would like to acknowledge the assistance of all the members of the 1298 Inter-Domain Routing Working Group, and particularly the following 1299 individuals: 1301 Yakov Rekhter, Juniper Networks 1302 Rob Coltun, Redback 1303 Guy Almes, Internet2 1304 Jeff Honig, BSDi 1305 Marshall T. Rose, Dover Beach Consulting, Inc. 1306 Dennis Ferguson, Juniper Networks 1307 Matt Mathis, PSC 1308 John Krawczyk, Bay Networks 1309 Curtis Villamizar, Avici 1310 Dave LeRoy, Pencom Systems 1311 Paul Traina, Juniper Networks 1312 Andrew Partan, MFN 1313 Robert Snyder, Cisco Systems 1314 Dimitry Haskin, Nortel 1315 Peder Chr Norgaard, Telebit Communications A/S 1316 Joel Halpern, CTO Longitude Systems, Inc. 1317 Nick Thille, RedBack Networks 1318 Bert Wijnen, Lucent 1319 Shane Wright, NextHop 1320 Mike McFadden, Riverstone Networks, Inc. 1321 Jon Saperia, JDS Consulting, Inc. 1322 Wayne Tackabury, Gold Wire Technology, Inc. 1323 Bill Fenner, AT&T Research 1324 RJ Atkinson, Extreme Networks 1326 The origin of this document is from RFC 1269 "Definitions of Managed 1327 Objects for the Border Gateway Protocol (Version 3)" written by Steve 1328 Willis and John Burruss, which was updated by John Chu to support 1329 BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of 1330 these original authors. 1332 8. Normative References 1334 [BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway 1335 Protocol 4 (BGP-4)", RFC yyyy, zzzz 2003. 1337 -- RFC Ed.: Replace yyyy with latest BGP RFC and zzzz with its 1338 -- month of publication 1340 [BGP4APP] Rekhter, Y., Gross, P., "Application of the Border 1341 Gateway Protocol in the Internet", RFC 1772, March 1995. 1343 --- XXX TODO - this document has yet to be updated. 1345 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1346 (USM) for version 3 of the Simple Network Management 1347 Protocol (SNMPv3)", RFC 2574, April 1999. 1349 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1350 Rose, M., and S. Waldbusser, "Structure of Management 1351 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1352 1999. 1354 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1355 Rose, M., and S. Waldbusser, "Textual Conventions for 1356 SMIv2", STD 58, RFC 2579, April 1999. 1358 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1359 Rose, M., and S. Waldbusser, "Conformance Statements for 1360 SMIv2", STD 58, RFC 2580, April 1999. 1362 [RFC3411] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture 1363 for Describing Simple Network Management Protocol (SNMP) 1364 Management Frameworks", RFC 3411, December 2002. 1366 [RFC3413] D. Levi, P. Meyer, B. Stewart, "Simple Network Management 1367 Protocol (SNMP) Applications", RFC 3413, December 2002. 1369 [RFC3415] B. Wijnen, R. Presuhn, K. McCloghrie, "View-based Access 1370 Control Model (VACM) for the Simple Network Management 1371 Protocol (SNMP)", RFC 3415, December 2002. 1373 [RFC3416] Presuhn, R., Editor, "Version 2 of the Protool Operations 1374 for the Simple Network Management Protocol (SNMP)", 1375 RFC 3416, December 2002. 1377 [RFC3417] Presuhn, R., Editor, "Transport Mappings for the Simple 1378 Network Management Protocol (SNMP)", RFC 3417, December 1379 2002. 1381 9. Informative References 1383 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1384 "Introduction to Community-based SNMPv2", RFC 1901, 1385 January 1996. 1387 [RFC2576] Frye, R., Levi, D., Routhier, S. and B. Wijnen, 1388 "Coexistence between Version 1, Version 2, and Version 1389 3 of the Internet-Standard Network Management Framework", 1390 RFC 2576, March 2000. 1392 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1393 "Introduction and Applicability Statements for Internet- 1394 Standard Management Framework", RFC 3410, December 2002. 1396 10. Editors' Address 1398 Jeffrey Haas, Susan Hares 1399 NextHop Technologies 1400 825 Victor's Way, Suite 100 1401 Ann Arbor, MI 48103 1402 Phone: +1 734 222-1600 1403 Fax: +1 734 222-1602 1404 Email: jhaas@nexthop.com 1405 skh@nexthop.com 1407 11. Full Copyright Statement 1409 Copyright (C) The Internet Society (2003). All Rights Reserved. 1411 This document and translations of it may be copied and furnished to 1412 others, and derivative works that comment on or otherwise explain it 1413 or assist in its implementation may be prepared, copied, published 1414 and distributed, in whole or in part, without restriction of any 1415 kind, provided that the above copyright notice and this paragraph are 1416 included on all such copies and derivative works. However, this 1417 document itself may not be modified in any way, such as by removing 1418 the copyright notice or references to the Internet Society or other 1419 Internet organizations, except as needed for the purpose of 1420 developing Internet standards in which case the procedures for 1421 copyrights defined in the Internet Standards process must be 1422 followed, or as required to translate it into languages other than 1423 English. 1425 The limited permissions granted above are perpetual and will not be 1426 revoked by the Internet Society or its successors or assigns. 1428 This document and the information contained herein is provided on an 1429 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1430 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1431 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1432 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1433 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.