idnits 2.17.1 draft-ietf-mboned-msdp-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1390. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1369. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1376. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1382. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 38), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 38. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** 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 148: '... value MUST be 60....' RFC 2119 keyword, line 680: '...ection 5.1 says it MUST be 60 seconds....' 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 (July 2004) is 7224 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) -- Looks like a reference, but probably isn't: 'SG-State-Period' on line 288 -- Looks like a reference, but probably isn't: 'SA-Advertisement-Timer' on line 679 -- Looks like a reference, but probably isn't: 'ConnectRetry-period' on line 688 -- Looks like a reference, but probably isn't: 'HoldTime-Period' on line 700 -- Looks like a reference, but probably isn't: 'KeepAlive-Period' on line 715 ** Downref: Normative reference to an Experimental RFC: RFC 3618 (ref. '1') Summary: 11 errors (**), 0 flaws (~~), 2 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 MBONED Working Group Bill Fenner 2 INTERNET-DRAFT AT&T Research 3 Expires: January 2005 Dave Thaler 4 Microsoft 5 July 2004 7 Multicast Source Discovery protocol MIB 8 10 Status of this Document 12 By submitting this Internet-Draft, I certify that any applicable patent 13 or other IPR claims of which I am aware have been disclosed, or will be 14 disclosed, and any of which I become aware will be disclosed, in 15 accordance with RFC 3668. 17 Internet-Drafts are working documents of the Internet Engineering Task 18 Force (IETF), its areas, and its working groups. Note that other groups 19 may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference material 24 or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This document is a product of the MBONED Working Group. Comments should 33 be addressed to the authors, or the mailing list at 34 mboned@lists.uoregon.edu. 36 Copyright Notice 38 Copyright (C) The Internet Society (2004). All Rights Reserved. 40 Abstract 42 This memo defines an experimental portion of the Management Information 43 Base (MIB) for use with network management protocols in the Internet 44 community. In particular, it describes managed objects used for 45 managing Multicast Source Discovery Protocol (MSDP) [1] speakers. 47 Table of Contents 49 1. The The Internet-Standard Management Framework. . . . . . . . . . 2 50 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 2 51 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 52 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 5. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 54 6. Security Considerations . . . . . . . . . . . . . . . . . . . . . 27 55 7. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . 28 56 8. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . . 28 57 9. Normative References. . . . . . . . . . . . . . . . . . . . . . . 28 58 9.1. Informative References . . . . . . . . . . . . . . . . . . . . 29 59 10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 29 61 1. The The Internet-Standard Management Framework 63 For a detailed overview of the documents that describe the current 64 Internet-Standard Management Framework, please refer to section 7 of RFC 65 3410 [7]. 67 Managed objects are accessed via a virtual information store, termed the 68 Management Information Base or MIB. MIB objects are generally accessed 69 through the Simple Network Management Protocol (SNMP). Objects in the 70 MIB are defined using the mechanisms defined in the Structure of 71 Management Information (SMI). This memo specifies a MIB module that is 72 compliant to the SMIv2, which is described in STD 58, RFC 2578 [4], STD 73 58, RFC 2579 [5] and STD 58, RFC 2580 [6]. 75 2. Revision History 77 A record of changes which will be removed before publication. 79 11 July 2004 81 Renamed to draft-ietf-mboned-msdp-mib-00. 83 Fixed spec references and defaults for msdpPeerHoldTimeConfigured, 84 msdpPeerKeepAliveConfigured and msdpPeerConnectRetryInterval, as 85 pointed out by Ketan Talaulikar. 87 Deprecated all objects related to SA-Requests and notifications, 88 since RFC 3618 doesn't have either one. As pointed out by Ketan 89 Talaulikar. 91 Clarified that msdpSACachePeerLearnedFrom should be 0.0.0.0 on the 92 originator. From Mike Davison. 94 Removed msdpSAStatePeriod. I couldn't figure out what it's for; at 95 best it should be SG State Period, but that's already 96 msdpCacheLifetime. From Mike Davison. 98 17 October 2003 100 Undid most of the hard work since draft -03, which is the only 101 implementation I was able to find by querying the MSDP mailing 102 list. 104 29 May 2003 106 Republished with no changes. How did it get to be almost 2 years? 108 18 July 2001 110 Since the INET-ADDRESS-MIB relaxed restrictions on InetAddressType, 111 remove msdpPeerLocalAddressType, rename msdpSACacheGroupAddrType to 112 msdpCacheAddrType, remove msdpCacheSourceAddrType, 113 msdpSACacheOriginRPType, msdpSACachePeerLearnedFromType, 114 msdpSACacheRPFPeerType. 116 Updated the DESCRIPTION of msdpRequestsTable to describe exactly 117 how it is used. 119 Added msdpPeerDiscontinuityTime. 121 Changed msdpPeerFsmEstablishedTime to a TimeStamp instead of a 122 counting number of seconds. 124 Changed msdpPeerInMessageElapsedTime to msdpPeerInMessageTime and 125 changed it to a TimeStamp. 127 Added msdpMeshGroupTable. 129 Updated conformance information. 131 1 March 2001 133 Added msdpPeerIfIndex. 135 Converted all IpAddress items to InetAddressType/InetAddress pairs. 136 This bigtime violates RFC2578's rules about MIB evolution, so take 137 extra care when implementing this change. 139 Added msdpRequestsPriority, in order to allow configuration of 140 multiple peers to whom Requests will be sent. Note that this 141 violates RFC2578's rules about MIB evolution, so take extra care 142 when implementing this change. 144 Removed DEFVAL on scalars, since it should only be needed for table 145 row creation. 147 Removed msdpPeerSAAdvPeriod, since the spec changed to say its 148 value MUST be 60. 150 Added none(0) to msdpPeerEncapsulationType enumeration XXX is this 151 OK? should it be 4? 153 Removed msdpPeerEncapsulationState since the encapsulation 154 "negotiation" was removed from the spec. 156 Added msdpRPAddress to specify the RP address to use when sourcing 157 SA messages. 159 Added msdpSACacheSourcePrefix to msdpSACacheTable, and added it to 160 the INDEX. Note that this violates RFC2578's rules about MIB 161 evolution, so take extra care when implementing this change. 163 Completely renumbered the MIB, removing the extra level of 164 msdpMIBobjects and creating an msdpScalars group to contain all 165 scalars. Note that this violates RFC2578's rules about MIB 166 evolution, so take extra care when implementing this change. 168 16 December 1999 170 Added msdpSAHoldDownPeriod, msdpPeerEncapsulationState, 171 msdpPeerEncapsulationType, msdpPeerConnectionAttempts, 172 msdpPeerInNotifications, msdpPeerOutNotifications, and 173 msdpLastError 175 Removed msdpPeerConfigMethod, since this has disappeared from the 176 spec. 178 Renamed the states in msdpPeerState to go with the state machine in 179 the spec. 181 Added msdpPeerLocalPort and msdpPeerRemotePort in order to provide 182 full information about the TCP connection in use. I'd like to 183 reorder the Peer Table but that can wait until the MIB gets 184 published as an RFC in order to only change things like that once. 186 Added msdpSACacheOriginRP as an INDEX to the msdpSACacheTable. 187 Note that this violates RFC2578's rules about MIB evolution, so 188 take extra care when implementing this change. 190 25 June 1999 192 Renamed to DRAFT-MSDP-MIB. It will be renamed back to MSDP-MIB 193 when it gets renumbered under mib-2, in order to avoid module 194 naming problems. 196 Turned msdpSendRequestsTo into a table in order to handle 197 administratively scoped groups with different RP's. 199 27 May 1999 201 Added IANA-assigned experimental OID 203 Added msdpSendRequestsTo and msdpPeerProcessRequestsFrom to 204 configure MSDP SA-Request/Response processing. 206 Added msdpPeerDataTtl to allow TTL scoping of data packets 207 forwarded across MSDP peerings. 209 Renumbered msdpSACacheInDataPackets and further items in 210 msdpSACacheTable, to eliminate duplicate OIDs 212 20 April 1999 214 initial version. 216 3. Overview 218 XXX This needs to be updated. 220 This MIB module contains three scalars and three tables. The tables 221 are: 223 o the Requests Table, containing the longest-match table used to 224 determine the peer to send SA-Requests to for a given group; 226 o the Peer Table, containing information on the peers; and 228 o the Source-Active Cache Table, containing the SA cache entries. 230 4. Definitions 232 -- 233 -- 234 DRAFT-MSDP-MIB DEFINITIONS ::= BEGIN 236 IMPORTS 237 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 238 experimental, Counter32, Gauge32, TimeTicks, Integer32, 239 IpAddress 240 FROM SNMPv2-SMI 241 RowStatus, TruthValue, TimeStamp, DisplayString 242 FROM SNMPv2-TC 243 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 244 FROM SNMPv2-CONF; 246 msdpMIB MODULE-IDENTITY 247 LAST-UPDATED "200407120000Z" 248 ORGANIZATION "IETF MBONED Working Group" 249 CONTACT-INFO 250 "Bill Fenner 251 75 Willow Road 252 Menlo Park, CA 94025 253 Phone: +1 650 867 6073 254 E-mail: fenner@research.att.com 256 Dave Thaler 257 One Microsoft Way 258 Redmond, WA 98052 259 Phone: +1 425 703 8835 260 Email: dthaler@microsoft.com" 261 DESCRIPTION 262 "An experimental MIB module for MSDP Management. 264 Copyright (C) The Internet Society 2004. This version of 265 this MIB module is part of RFC XXXX; see the RFC itself for 266 full legal notices." 267 ::= { experimental 92 } 269 msdpMIBobjects OBJECT IDENTIFIER ::= { msdpMIB 1 } 271 msdp OBJECT IDENTIFIER ::= { msdpMIBobjects 1 } 273 msdpEnabled OBJECT-TYPE 274 SYNTAX TruthValue 275 MAX-ACCESS read-write 276 STATUS current 277 DESCRIPTION 278 "The state of MSDP on this MSDP speaker - globally enabled or 279 disabled." 280 ::= { msdp 1 } 282 msdpCacheLifetime OBJECT-TYPE 283 SYNTAX TimeTicks 284 MAX-ACCESS read-write 285 STATUS current 286 DESCRIPTION 287 "The lifetime given to SA cache entries when created or 288 refreshed. This is the [SG-State-Period] in the MSDP spec. 289 A value of 0 means no SA caching is done by this MSDP 290 speaker." 291 REFERENCE "RFC 3618 section 5.3" 292 ::= { msdp 2 } 294 msdpNumSACacheEntries OBJECT-TYPE 295 SYNTAX Gauge32 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The total number of entries in the SA Cache table." 300 ::= { msdp 3 } 302 -- 303 -- The spec doesn't define SA-Hold-Down-Period any more. 304 -- msdpSAHoldDownPeriod OBJECT-TYPE 305 -- ::= { msdp 9 } 307 -- It's not clear what this was supposed to refer to. 308 -- msdpSAStatePeriod OBJECT-TYPE 309 -- ::= { msdp 10 } 311 msdpRPAddress OBJECT-TYPE 312 SYNTAX IpAddress 313 MAX-ACCESS read-write 314 STATUS current 315 DESCRIPTION 316 "The RP address used when sourcing MSDP SA messages. May be 317 0.0.0.0 on non-RP's." 318 ::= { msdp 11 } 320 -- 321 -- The MSDP Requests table 322 -- SA Requests were removed from the MSDP spec, so this entire table 323 -- is deprecated. 325 msdpRequestsTable OBJECT-TYPE 326 SYNTAX SEQUENCE OF MsdpRequestsEntry 327 MAX-ACCESS not-accessible 328 STATUS deprecated 329 DESCRIPTION 330 "The (conceptual) table listing group ranges and MSDP peers 331 used when deciding where to send an SA Request message when 332 required. If SA Requests are not enabled, this table may be 333 empty. 335 In order to choose a peer to whom to send an SA Request for 336 a given group G, the subset of entries in this table whose 337 (msdpRequestsPeerType, msdpRequestsPeer) tuple represents a 338 peer whose msdpPeerState is established are examined. The 339 set is further reduced by examining only those entries for 340 which msdpPeerRequestsGroupAddressType equals the address 341 type of G, and the entries with the highest value of 342 msdpRequestsGroupPrefix are considered, where the group G 343 falls within the range described by the combination of 344 msdpRequestsGroup and msdpRequestsGroupPrefix. (This 345 sequence is commonly known as a 'longest-match' lookup.) 347 Finally, if multiple entries remain, the entry with the 348 lowest value of msdpRequestsPriority is chosen. The SA 349 Request message is sent to the peer described by this row." 350 ::= { msdp 4 } 352 msdpRequestsEntry OBJECT-TYPE 353 SYNTAX MsdpRequestsEntry 354 MAX-ACCESS not-accessible 355 STATUS deprecated 356 DESCRIPTION 357 "An entry (conceptual row) representing a group range used 358 when deciding where to send an SA Request message." 359 INDEX { msdpRequestsGroupAddress, msdpRequestsGroupMask } 360 ::= { msdpRequestsTable 1 } 362 MsdpRequestsEntry ::= SEQUENCE { 363 msdpRequestsGroupAddress IpAddress, 364 msdpRequestsGroupMask IpAddress, 365 msdpRequestsPeer IpAddress, 366 msdpRequestsStatus RowStatus 367 } 369 msdpRequestsGroupAddress OBJECT-TYPE 370 SYNTAX IpAddress 371 MAX-ACCESS not-accessible 372 STATUS deprecated 373 DESCRIPTION 374 "The group address that, when combined with the mask in this 375 entry, represents the group range to which this row 376 applies." 377 ::= { msdpRequestsEntry 1 } 379 msdpRequestsGroupMask OBJECT-TYPE 380 SYNTAX IpAddress 381 MAX-ACCESS not-accessible 382 STATUS deprecated 383 DESCRIPTION 384 "The mask that, when combined with the group address in this 385 entry, represents the group range to which this row 386 applies." 387 ::= { msdpRequestsEntry 2 } 389 msdpRequestsPeer OBJECT-TYPE 390 SYNTAX IpAddress 391 MAX-ACCESS read-create 392 STATUS deprecated 393 DESCRIPTION 394 "The peer to which MSDP SA Requests for groups matching this 395 entry's group range will be sent. This object combined with 396 msdpRequestsPeerType must match the INDEX of a row in the 397 msdpPeerTable, and to be considered, this peer's 398 msdpPeerState must be established." 399 ::= { msdpRequestsEntry 3 } 401 msdpRequestsStatus OBJECT-TYPE 402 SYNTAX RowStatus 403 MAX-ACCESS read-create 404 STATUS deprecated 405 DESCRIPTION 406 "The status of this row, by which new rows may be added to 407 the table or old rows may be deleted." 408 ::= { msdpRequestsEntry 4 } 410 -- 411 -- The MSDP Peer table 412 -- 414 msdpPeerTable OBJECT-TYPE 415 SYNTAX SEQUENCE OF MsdpPeerEntry 416 MAX-ACCESS not-accessible 417 STATUS current 418 DESCRIPTION 419 "The (conceptual) table listing the MSDP speaker's peers." 420 ::= { msdp 5 } 422 msdpPeerEntry OBJECT-TYPE 423 SYNTAX MsdpPeerEntry 424 MAX-ACCESS not-accessible 425 STATUS current 426 DESCRIPTION 427 "An entry (conceptual row) representing an MSDP peer." 428 INDEX { msdpPeerRemoteAddress } 429 ::= { msdpPeerTable 1 } 431 MsdpPeerEntry ::= SEQUENCE { 432 msdpPeerRemoteAddress IpAddress, 433 msdpPeerState INTEGER, 434 msdpPeerRPFFailures Counter32, 435 msdpPeerInSAs Counter32, 436 msdpPeerOutSAs Counter32, 437 msdpPeerInSARequests Counter32, 438 msdpPeerOutSARequests Counter32, 439 msdpPeerInSAResponses Counter32, 440 msdpPeerOutSAResponses Counter32, 441 msdpPeerInControlMessages Counter32, 442 msdpPeerOutControlMessages Counter32, 443 msdpPeerInDataPackets Counter32, 444 msdpPeerOutDataPackets Counter32, 445 msdpPeerFsmEstablishedTransitions Counter32, 446 msdpPeerFsmEstablishedTime TimeTicks, 447 msdpPeerInMessageTime TimeTicks, 448 msdpPeerLocalAddress IpAddress, 449 msdpPeerConnectRetryInterval Integer32, 450 msdpPeerHoldTimeConfigured Integer32, 451 msdpPeerKeepAliveConfigured Integer32, 452 msdpPeerDataTtl Integer32, 453 msdpPeerProcessRequestsFrom TruthValue, 454 msdpPeerStatus RowStatus, 455 msdpPeerRemotePort Integer32, 456 msdpPeerLocalPort Integer32, 457 msdpPeerEncapsulationType INTEGER, 458 msdpPeerConnectionAttempts Counter32, 459 msdpPeerInNotifications Counter32, 460 msdpPeerOutNotifications Counter32, 461 msdpPeerLastError OCTET STRING, 462 msdpPeerDiscontinuityTime TimeStamp 463 } 465 msdpPeerRemoteAddress OBJECT-TYPE 466 SYNTAX IpAddress 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "The address of the remote MSDP peer." 471 ::= { msdpPeerEntry 1 } 473 -- dunno what happened to 2. 475 msdpPeerState OBJECT-TYPE 476 SYNTAX INTEGER { 477 inactive(1), 478 listen(2), 479 connecting(3), 480 established(4), 481 disabled(5) 482 } 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "The state of the MSDP TCP connection with this peer." 487 ::= { msdpPeerEntry 3 } 489 msdpPeerRPFFailures OBJECT-TYPE 490 SYNTAX Counter32 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The number of SA messages received from this peer which 495 failed the Peer-RPF check. 497 Discontinuities in the value of this counter can occur at 498 re-initialization of the management system, and at other 499 times as indicated by the value of 500 msdpPeerDiscontinuityTime." 501 ::= { msdpPeerEntry 4 } 503 msdpPeerInSAs OBJECT-TYPE 504 SYNTAX Counter32 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "The number of MSDP SA messages received on this connection. 510 Discontinuities in the value of this counter can occur at 511 re-initialization of the management system, and at other 512 times as indicated by the value of 513 msdpPeerDiscontinuityTime." 514 ::= { msdpPeerEntry 5 } 516 msdpPeerOutSAs OBJECT-TYPE 517 SYNTAX Counter32 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The number of MSDP SA messages transmitted on this 522 connection. 524 Discontinuities in the value of this counter can occur at 525 re-initialization of the management system, and at other 526 times as indicated by the value of 527 msdpPeerDiscontinuityTime." 528 ::= { msdpPeerEntry 6 } 530 msdpPeerInSARequests OBJECT-TYPE 531 SYNTAX Counter32 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "The number of MSDP SA-Request messages received on this 536 connection. 538 Discontinuities in the value of this counter can occur at 539 re-initialization of the management system, and at other 540 times as indicated by the value of 541 msdpPeerDiscontinuityTime." 542 ::= { msdpPeerEntry 7 } 544 msdpPeerOutSARequests OBJECT-TYPE 545 SYNTAX Counter32 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "The number of MSDP SA-Request messages transmitted on this 550 connection. 552 Discontinuities in the value of this counter can occur at 553 re-initialization of the management system, and at other 554 times as indicated by the value of 555 msdpPeerDiscontinuityTime." 556 ::= { msdpPeerEntry 8 } 558 msdpPeerInSAResponses OBJECT-TYPE 559 SYNTAX Counter32 560 MAX-ACCESS read-only 561 STATUS current 562 DESCRIPTION 563 "The number of MSDP SA-Response messages received on this 564 connection. 566 Discontinuities in the value of this counter can occur at 567 re-initialization of the management system, and at other 568 times as indicated by the value of 569 msdpPeerDiscontinuityTime." 570 ::= { msdpPeerEntry 9 } 572 msdpPeerOutSAResponses OBJECT-TYPE 573 SYNTAX Counter32 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "The number of MSDP SA Response messages transmitted on this 578 TCP connection. 580 Discontinuities in the value of this counter can occur at 581 re-initialization of the management system, and at other 582 times as indicated by the value of 583 msdpPeerDiscontinuityTime." 584 ::= { msdpPeerEntry 10 } 586 msdpPeerInControlMessages OBJECT-TYPE 587 SYNTAX Counter32 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "The total number of MSDP messages received on this TCP 592 connection. 594 Discontinuities in the value of this counter can occur at 595 re-initialization of the management system, and at other 596 times as indicated by the value of 597 msdpPeerDiscontinuityTime." 598 ::= { msdpPeerEntry 11 } 600 msdpPeerOutControlMessages OBJECT-TYPE 601 SYNTAX Counter32 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The total number of MSDP messages transmitted on this TCP 606 connection. 608 Discontinuities in the value of this counter can occur at 609 re-initialization of the management system, and at other 610 times as indicated by the value of 611 msdpPeerDiscontinuityTime." 612 ::= { msdpPeerEntry 12 } 614 msdpPeerInDataPackets OBJECT-TYPE 615 SYNTAX Counter32 616 MAX-ACCESS read-only 617 STATUS current 618 DESCRIPTION 619 "The total number of encapsulated data packets received from 620 this peer. 622 Discontinuities in the value of this counter can occur at 623 re-initialization of the management system, and at other 624 times as indicated by the value of 625 msdpPeerDiscontinuityTime." 626 ::= { msdpPeerEntry 13 } 628 msdpPeerOutDataPackets OBJECT-TYPE 629 SYNTAX Counter32 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "The total number of encapsulated data packets sent to this 634 peer. 636 Discontinuities in the value of this counter can occur at 637 re-initialization of the management system, and at other 638 times as indicated by the value of 639 msdpPeerDiscontinuityTime." 640 ::= { msdpPeerEntry 14 } 642 msdpPeerFsmEstablishedTransitions OBJECT-TYPE 643 SYNTAX Counter32 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "The total number of times the MSDP FSM transitioned into the 648 established state." 649 ::= { msdpPeerEntry 15 } 651 msdpPeerFsmEstablishedTime OBJECT-TYPE 652 SYNTAX TimeTicks 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "This timestamp is set to the value of sysUpTime when a peer 657 transitions into or out of the Established state. It is set 658 to zero when the MSDP speaker is booted." 659 ::= { msdpPeerEntry 16 } 661 msdpPeerInMessageTime OBJECT-TYPE 662 SYNTAX TimeTicks 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "The sysUpTime value when the last MSDP message was received 667 from the peer. It is set to zero when the MSDP speaker is 668 booted." 669 ::= { msdpPeerEntry 17 } 671 msdpPeerLocalAddress OBJECT-TYPE 672 SYNTAX IpAddress 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "The local IP address of this entry's MSDP connection." 677 ::= { msdpPeerEntry 18 } 679 -- msdpPeerSAAdvPeriod ([SA-Advertisement-Timer]) has been removed. 680 -- RFC 3618 section 5.1 says it MUST be 60 seconds. 682 msdpPeerConnectRetryInterval OBJECT-TYPE 683 SYNTAX Integer32 (1..65535) 684 UNITS "seconds" 685 MAX-ACCESS read-create 686 STATUS current 687 DESCRIPTION 688 "Time interval in seconds for the [ConnectRetry-period] for 689 this peer." 690 REFERENCE "RFC 3618 section 5.6" 691 DEFVAL { 30 } 692 ::= { msdpPeerEntry 20 } 694 msdpPeerHoldTimeConfigured OBJECT-TYPE 695 SYNTAX Integer32 (0|3..65535) 696 UNITS "seconds" 697 MAX-ACCESS read-create 698 STATUS current 699 DESCRIPTION 700 "Time interval in seconds for the [HoldTime-Period] 701 configured for this MSDP speaker with this peer. If the 702 value of this object is zero (0), the MSDP connection is 703 never torn down due to the absence of messages from the 704 peer." 705 REFERENCE "RFC 3618 section 5.4" 706 DEFVAL { 75 } 707 ::= { msdpPeerEntry 21 } 709 msdpPeerKeepAliveConfigured OBJECT-TYPE 710 SYNTAX Integer32 (0|1..21845) 711 UNITS "seconds" 712 MAX-ACCESS read-create 713 STATUS current 714 DESCRIPTION 715 "Time interval in seconds for the [KeepAlive-Period] 716 configured for this MSDP speaker with this peer. If the 717 value of this object is zero (0), no periodic KEEPALIVE 718 messages are sent to the peer after the MSDP connection has 719 been established." 720 REFERENCE "RFC 3618 section 5.5" 721 DEFVAL { 60 } 722 ::= { msdpPeerEntry 22 } 724 msdpPeerDataTtl OBJECT-TYPE 725 SYNTAX Integer32 (0..255) 726 MAX-ACCESS read-create 727 STATUS current 728 DESCRIPTION 729 "The minimum TTL a packet is required to have before it may 730 be forwarded using SA encapsulation to this peer." 731 ::= { msdpPeerEntry 23 } 733 msdpPeerProcessRequestsFrom OBJECT-TYPE 734 SYNTAX TruthValue 735 MAX-ACCESS read-create 736 STATUS deprecated 737 DESCRIPTION 738 "This object indicates whether or not to process MSDP SA 739 Request messages from this peer. If True(1), MSDP SA 740 Request messages from this peer are processed and replied to 741 (if appropriate) with SA Response messages. If False(2), 742 MSDP SA Request messages from this peer are silently 743 ignored. It defaults to False when msdpCacheLifetime is 0 744 and True when msdpCacheLifetime is non-0. 746 This object is deprecated because MSDP SA Requests were 747 removed from the MSDP specification." 748 ::= { msdpPeerEntry 24 } 750 msdpPeerStatus OBJECT-TYPE 751 SYNTAX RowStatus 752 MAX-ACCESS read-create 753 STATUS current 754 DESCRIPTION 755 "The RowStatus object by which peers can be added and 756 deleted. A transition to 'active' will cause the MSDP Start 757 Event to be generated. A transition out of the 'active' 758 state will cause the MSDP Stop Event to be generated. Care 759 should be used in providing write access to this object 760 without adequate authentication." 761 ::= { msdpPeerEntry 25 } 763 msdpPeerRemotePort OBJECT-TYPE 764 SYNTAX Integer32 (0..65535) 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "The remote port for the TCP connection between the MSDP 769 peers." 770 ::= { msdpPeerEntry 26 } 772 msdpPeerLocalPort OBJECT-TYPE 773 SYNTAX Integer32 (0..65535) 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "The local port for the TCP connection between the MSDP 778 peers." 779 ::= { msdpPeerEntry 27 } 781 -- msdpPeerEncapsulationState has been removed 782 -- because there is no longer an encapsulation 783 -- state machine. 785 msdpPeerEncapsulationType OBJECT-TYPE 786 SYNTAX INTEGER { 787 none(0), 788 tcp(1) 789 } 790 MAX-ACCESS read-create 791 STATUS current 792 DESCRIPTION 793 "The encapsulation in use when encapsulating data in SA 794 messages to this peer." 795 ::= { msdpPeerEntry 29 } 797 msdpPeerConnectionAttempts OBJECT-TYPE 798 SYNTAX Counter32 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "The number of times the state machine has transitioned from 803 inactive to connecting." 804 ::= { msdpPeerEntry 30 } 806 msdpPeerInNotifications OBJECT-TYPE 807 SYNTAX Counter32 808 MAX-ACCESS read-only 809 STATUS deprecated 810 DESCRIPTION 811 "The number of MSDP Notification messages received from this 812 peer. 814 This object is deprecated because MSDP Notifications have 815 been removed from the spec." 816 ::= { msdpPeerEntry 31 } 818 msdpPeerOutNotifications OBJECT-TYPE 819 SYNTAX Counter32 820 MAX-ACCESS read-only 821 STATUS deprecated 822 DESCRIPTION 823 "The number of MSDP Notification messages transmitted to this 824 peer. 826 This object is deprecated because MSDP Notifications have 827 been removed from the spec." 828 ::= { msdpPeerEntry 32 } 830 msdpPeerLastError OBJECT-TYPE 831 SYNTAX OCTET STRING (SIZE (2)) 832 MAX-ACCESS read-only 833 STATUS deprecated 834 DESCRIPTION 835 "The last error code and subcode received via Notification 836 from this peer. If no error has occurred, this field is 837 zero. Otherwise, the first byte of this two byte OCTET 838 STRING contains the O-bit and error code, and the second 839 byte contains the subcode. 841 This object is deprecated because MSDP Notifications have 842 been removed from the spec." 843 DEFVAL { '0000'h } 844 ::= { msdpPeerEntry 33 } 846 msdpPeerDiscontinuityTime OBJECT-TYPE 847 SYNTAX TimeStamp 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION 851 "The value of sysUpTime on the most recent occasion at which 852 one or more of this entry's counters suffered a 853 discontinuity. See the DESCRIPTION of each object to see if 854 it is expected to have discontinuities. These 855 discontinuities may occur at peer connection establishment. 857 If no such discontinuities have occurred since the last 858 reinitialization of the local management subsystem, then 859 this object contains a zero value." 860 ::= { msdpPeerEntry 34 } 862 -- 863 -- The MSDP Source-Active Cache table 864 -- 866 msdpSACacheTable OBJECT-TYPE 867 SYNTAX SEQUENCE OF MsdpSACacheEntry 868 MAX-ACCESS not-accessible 869 STATUS current 870 DESCRIPTION 871 "The (conceptual) table listing the MSDP SA advertisements 872 currently in the MSDP speaker's cache." 873 ::= { msdp 6 } 875 msdpSACacheEntry OBJECT-TYPE 876 SYNTAX MsdpSACacheEntry 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "An entry (conceptual row) representing an MSDP SA 881 advertisement. The INDEX to this table includes 882 msdpSACacheOriginRP for diagnosing incorrect MSDP 883 advertisements; normally a Group and Source pair would be 884 unique." 885 INDEX { msdpSACacheGroupAddr, msdpSACacheSourceAddr, 886 msdpSACacheOriginRP } 887 ::= { msdpSACacheTable 1 } 889 MsdpSACacheEntry ::= SEQUENCE { 890 msdpSACacheGroupAddr IpAddress, 891 msdpSACacheSourceAddr IpAddress, 892 msdpSACacheOriginRP IpAddress, 893 msdpSACachePeerLearnedFrom IpAddress, 894 msdpSACacheRPFPeer IpAddress, 895 msdpSACacheInSAs Counter32, 896 msdpSACacheInDataPackets Counter32, 897 msdpSACacheUpTime TimeTicks, 898 msdpSACacheExpiryTime TimeTicks, 899 msdpSACacheStatus RowStatus 900 } 902 msdpSACacheGroupAddr OBJECT-TYPE 903 SYNTAX IpAddress 904 MAX-ACCESS not-accessible 905 STATUS current 906 DESCRIPTION 907 "The group address of the SA Cache entry." 908 ::= { msdpSACacheEntry 1 } 910 msdpSACacheSourceAddr OBJECT-TYPE 911 SYNTAX IpAddress 912 MAX-ACCESS not-accessible 913 STATUS current 914 DESCRIPTION 915 "The source address of the SA Cache entry." 916 ::= { msdpSACacheEntry 2 } 918 msdpSACacheOriginRP OBJECT-TYPE 919 SYNTAX IpAddress 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "The RP of the SA Cache entry. This field is in the INDEX in 924 order to catch multiple RP's advertising the same source and 925 group." 926 ::= { msdpSACacheEntry 3 } 928 msdpSACachePeerLearnedFrom OBJECT-TYPE 929 SYNTAX IpAddress 930 MAX-ACCESS read-only 931 STATUS current 932 DESCRIPTION 933 "The peer from which this SA Cache entry was last accepted. 934 This address must correspond to the msdpPeerRemoteAddress 935 value for a row in the MSDP Peer Table. This should be 936 0.0.0.0 on the router that originated the entry." 937 ::= { msdpSACacheEntry 4 } 939 msdpSACacheRPFPeer OBJECT-TYPE 940 SYNTAX IpAddress 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "The peer from which an SA message corresponding to this 945 cache entry would be accepted (i.e. the RPF peer for 946 msdpSACacheOriginRP). This may be different than 947 msdpSACachePeerLearnedFrom if this entry was created by an 948 MSDP SA-Response. This address must correspond to the 949 msdpPeerRemoteAddress value for a row in the MSDP Peer 950 Table, or may be 0.0.0.0 if no RPF peer exists." 951 ::= { msdpSACacheEntry 5 } 953 msdpSACacheInSAs OBJECT-TYPE 954 SYNTAX Counter32 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "The number of MSDP SA messages received relevant to this 959 cache entry. This object must be initialized to zero when 960 creating a cache entry." 961 ::= { msdpSACacheEntry 6 } 963 msdpSACacheInDataPackets OBJECT-TYPE 964 SYNTAX Counter32 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "The number of MSDP encapsulated data packets received 969 relevant to this cache entry. This object must be 970 initialized to zero when creating a cache entry." 971 ::= { msdpSACacheEntry 7 } 973 msdpSACacheUpTime OBJECT-TYPE 974 SYNTAX TimeTicks 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "The time since this entry was placed in the SA cache." 979 ::= { msdpSACacheEntry 8 } 981 msdpSACacheExpiryTime OBJECT-TYPE 982 SYNTAX TimeTicks 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "The time remaining before this entry will expire from the SA 987 cache." 988 ::= { msdpSACacheEntry 9 } 990 msdpSACacheStatus OBJECT-TYPE 991 SYNTAX RowStatus 992 MAX-ACCESS read-write 993 STATUS current 994 DESCRIPTION 995 "The status of this row in the table. The only allowable 996 actions are to retrieve the status, which will be `active', 997 or to set the status to `destroy' in order to remove this 998 entry from the cache." 999 ::= { msdpSACacheEntry 10 } 1001 -- 1002 -- MSDP Mesh Group Membership table 1003 -- 1005 msdpMeshGroupTable OBJECT-TYPE 1006 SYNTAX SEQUENCE OF MsdpMeshGroupEntry 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "The (conceptual) table listing MSDP Mesh Group 1011 configuration." 1012 ::= { msdp 12 } 1014 msdpMeshGroupEntry OBJECT-TYPE 1015 SYNTAX MsdpMeshGroupEntry 1016 MAX-ACCESS not-accessible 1017 STATUS current 1018 DESCRIPTION 1019 "An entry (conceptual row) repesenting a peer in an MSDP Mesh 1020 Group." 1021 INDEX { msdpMeshGroupName, msdpMeshGroupPeerAddress } 1022 ::= { msdpMeshGroupTable 1 } 1024 MsdpMeshGroupEntry ::= SEQUENCE { 1025 msdpMeshGroupName DisplayString, 1026 msdpMeshGroupPeerAddress IpAddress, 1027 msdpMeshGroupStatus RowStatus 1028 } 1030 msdpMeshGroupName OBJECT-TYPE 1031 SYNTAX DisplayString (SIZE(1..64)) 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "The name of the mesh group." 1036 ::= { msdpMeshGroupEntry 1 } 1038 msdpMeshGroupPeerAddress OBJECT-TYPE 1039 SYNTAX IpAddress 1040 MAX-ACCESS not-accessible 1041 STATUS current 1042 DESCRIPTION 1043 "A peer address that is a member of the mesh group with name 1044 msdpMeshGroupName. The msdpMeshGroupPeerAddress must match 1045 a row in the msdpPeerTable." 1046 ::= { msdpMeshGroupEntry 2 } 1048 msdpMeshGroupStatus OBJECT-TYPE 1049 SYNTAX RowStatus 1050 MAX-ACCESS read-create 1051 STATUS current 1052 DESCRIPTION 1053 "This entry's status, by which new entries may be added to 1054 the table and old entries deleted." 1055 ::= { msdpMeshGroupEntry 3 } 1057 -- Traps 1059 msdpTraps OBJECT IDENTIFIER ::= { msdp 0 } 1061 msdpEstablished NOTIFICATION-TYPE 1062 OBJECTS { msdpPeerFsmEstablishedTransitions } 1063 STATUS current 1064 DESCRIPTION 1065 "The MSDP Established event is generated when the MSDP FSM 1066 enters the ESTABLISHED state." 1067 ::= { msdpTraps 1 } 1069 msdpBackwardTransition NOTIFICATION-TYPE 1070 OBJECTS { msdpPeerState } 1071 STATUS current 1072 DESCRIPTION 1073 "The MSDPBackwardTransition Event is generated when the MSDP 1074 FSM moves from a higher numbered state to a lower numbered 1075 state." 1076 ::= { msdpTraps 2 } 1078 -- conformance information 1080 msdpMIBConformance OBJECT IDENTIFIER ::= { msdp 8 } 1081 msdpMIBCompliances OBJECT IDENTIFIER ::= { msdpMIBConformance 1 } 1082 msdpMIBGroups OBJECT IDENTIFIER ::= { msdpMIBConformance 2 } 1084 -- compliance statements 1086 msdpMIBCompliance MODULE-COMPLIANCE 1087 STATUS deprecated 1088 DESCRIPTION 1089 "The compliance statement for entities which implement the 1090 MSDP MIB." 1091 MODULE -- this module 1092 MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup, 1093 msdpMIBNotificationGroup } 1095 GROUP msdpMIBEncapsulationGroup 1096 DESCRIPTION 1097 "This group is mandatory if MSDP encapsulation interfaces are 1098 not given their own interface index numbers." 1099 GROUP msdpMIBSACacheGroup 1100 DESCRIPTION 1101 "This group is mandatory if the MSDP speaker has the ability 1102 to cache SA messages." 1103 GROUP msdpMIBRequestsGroup 1104 DESCRIPTION 1105 "This group is mandatory if the MSDP speaker has the ability 1106 to send SA-Request messages and parse SA-Response 1107 messages." 1108 GROUP msdpMIBRPGroup 1109 DESCRIPTION 1110 "This group is mandatory if the MSDP speaker sources (as 1111 opposed to forwards) MSDP messages." 1112 GROUP msdpMIBMeshGroupGroup 1113 DESCRIPTION 1114 "This group is mandatory if the MSDP speaker can participate 1115 in MSDP Mesh Groups." 1117 ::= { msdpMIBCompliances 1 } 1119 msdpMIBCompliance2 MODULE-COMPLIANCE 1120 STATUS deprecated 1121 DESCRIPTION 1122 "The compliance statement for entities which implement the 1123 MSDP MIB." 1124 MODULE -- this module 1125 MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup2, 1126 msdpMIBSACacheGroup, msdpMIBEncapsulationGroup } 1127 GROUP msdpMIBRPGroup 1128 DESCRIPTION 1129 "This group is mandatory if the MSDP speaker sources (as 1130 opposed to forwards) MSDP messages." 1131 GROUP msdpMIBMeshGroupGroup 1132 DESCRIPTION 1133 "This group is mandatory if the MSDP speaker can participate 1134 in MSDP Mesh Groups." 1135 ::= { msdpMIBCompliances 2 } 1137 -- units of conformance 1139 msdpMIBGlobalsGroup OBJECT-GROUP 1140 OBJECTS { msdpEnabled } 1141 STATUS current 1142 DESCRIPTION 1143 "A collection of objects providing information on global MSDP 1144 state." 1145 ::= { msdpMIBGroups 1 } 1147 msdpMIBPeerGroup OBJECT-GROUP 1148 OBJECTS { msdpPeerRPFFailures, 1149 msdpPeerState, msdpPeerInSAs, msdpPeerOutSAs, 1150 msdpPeerInSARequests, msdpPeerOutSARequests, 1151 msdpPeerInSAResponses, msdpPeerOutSAResponses, 1152 msdpPeerInNotifications, msdpPeerOutNotifications, 1153 msdpPeerInControlMessages, msdpPeerOutControlMessages, 1154 msdpPeerFsmEstablishedTransitions, 1155 msdpPeerFsmEstablishedTime, 1156 msdpPeerLocalAddress, 1157 msdpPeerRemotePort, msdpPeerLocalPort, 1158 msdpPeerConnectRetryInterval, 1159 msdpPeerHoldTimeConfigured, 1160 msdpPeerKeepAliveConfigured, 1161 msdpPeerInMessageTime, 1162 msdpPeerProcessRequestsFrom, 1163 msdpPeerConnectionAttempts, 1164 msdpPeerLastError, 1165 msdpPeerStatus, 1166 msdpPeerDiscontinuityTime 1167 } 1168 STATUS deprecated 1169 DESCRIPTION 1170 "A collection of objects for managing MSDP peers." 1171 ::= { msdpMIBGroups 2 } 1173 msdpMIBEncapsulationGroup OBJECT-GROUP 1174 OBJECTS { msdpPeerInDataPackets, msdpPeerOutDataPackets, 1175 msdpPeerDataTtl, 1176 msdpPeerEncapsulationType 1177 } 1178 STATUS current 1179 DESCRIPTION 1180 "A collection of objects for managing encapsulations if the 1181 MSDP encapsulation interfaces are not given interface 1182 indices." 1183 ::= { msdpMIBGroups 3 } 1185 msdpMIBSACacheGroup OBJECT-GROUP 1186 OBJECTS { msdpCacheLifetime, msdpNumSACacheEntries, 1187 msdpSACachePeerLearnedFrom, 1188 msdpSACacheRPFPeer, msdpSACacheInSAs, 1189 msdpSACacheInDataPackets, 1190 msdpSACacheUpTime, msdpSACacheExpiryTime, 1191 msdpSACacheStatus } 1192 STATUS current 1193 DESCRIPTION 1194 "A collection of objects for managing MSDP SA cache entries." 1195 ::= { msdpMIBGroups 4 } 1197 msdpMIBNotificationGroup NOTIFICATION-GROUP 1198 NOTIFICATIONS { msdpEstablished, 1199 msdpBackwardTransition } 1200 STATUS current 1201 DESCRIPTION 1202 "A collection of notifications for signaling changes in MSDP 1203 peer relationships." 1204 ::= { msdpMIBGroups 5 } 1206 msdpMIBRequestsGroup OBJECT-GROUP 1207 OBJECTS { msdpRequestsPeer, msdpRequestsStatus } 1208 STATUS deprecated 1209 DESCRIPTION 1210 "A collection of objects for managing MSDP Request 1211 transmission." 1212 ::= { msdpMIBGroups 6 } 1214 msdpMIBRPGroup OBJECT-GROUP 1215 OBJECTS { msdpRPAddress } 1216 STATUS current 1217 DESCRIPTION 1218 "A collection of objects for MSDP speakers that source MSDP 1219 messages." 1220 ::= { msdpMIBGroups 7 } 1222 msdpMIBMeshGroupGroup OBJECT-GROUP 1223 OBJECTS { msdpMeshGroupStatus } 1224 STATUS current 1225 DESCRIPTION 1226 "A collection of objects for MSDP speakers that can 1227 participate in MSDP mesh groups." 1228 ::= { msdpMIBGroups 8 } 1230 msdpMIBPeerGroup2 OBJECT-GROUP 1231 OBJECTS { msdpPeerRPFFailures, 1232 msdpPeerState, msdpPeerInSAs, msdpPeerOutSAs, 1233 msdpPeerInSARequests, msdpPeerOutSARequests, 1234 msdpPeerInSAResponses, msdpPeerOutSAResponses, 1235 msdpPeerInControlMessages, msdpPeerOutControlMessages, 1236 msdpPeerFsmEstablishedTransitions, 1237 msdpPeerFsmEstablishedTime, 1238 msdpPeerLocalAddress, 1239 msdpPeerRemotePort, msdpPeerLocalPort, 1240 msdpPeerConnectRetryInterval, 1241 msdpPeerHoldTimeConfigured, 1242 msdpPeerKeepAliveConfigured, 1243 msdpPeerInMessageTime, 1244 msdpPeerConnectionAttempts, 1245 msdpPeerStatus, 1246 msdpPeerDiscontinuityTime 1247 } 1248 STATUS current 1249 DESCRIPTION 1250 "A collection of objects for managing MSDP peers." 1251 ::= { msdpMIBGroups 9 } 1253 END 1255 5. Open Issues 1257 The Backwards Transition notification won't trigger on established -> 1258 disabled. Is that desired? 1260 Is the RowStatus object in the SACache appropriate? (e.g. used to flush 1261 potentially bad state) 1263 Are there any other variables appropriate for configuring/managing mesh 1264 groups? 1266 Is the msdpRPAddress useful? Per-peer? Remove it completely? 1268 Should we use IpAddress (since RFC 3618 is v4-only) or 1269 InetAddressType/InetAddress? 1271 6. Security Considerations 1273 There are a number of management objects defined in this MIB that have a 1274 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 1275 considered sensitive or vulnerable in some network environments. The 1276 support for SET operations in a non-secure environment without proper 1277 protection can have a negative effect on network operations. 1279 There are a number of managed objects in this MIB that may contain 1280 sensitive information. These are: 1282 -- XXX fill this in 1284 It is thus important to control even GET access to these objects and 1285 possibly to even encrypt the values of these object when sending them 1286 over the network via SNMP. Not all versions of SNMP provide features 1287 for such a secure environment. 1289 SNMPv1 by itself is not a secure environment. Even if the network 1290 itself is secure (for example by using IPSec), even then, there is no 1291 control as to who on the secure network is allowed to access and GET/SET 1292 (read/change/create/delete) the objects in this MIB. 1294 It is recommended that the implementers consider the security features 1295 as provided by the SNMPv3 framework. Specifically, the use of the User- 1296 based Security Model RFC 3414 [2] and the View-based Access Control 1297 Model RFC 3415 [3] is recommended. 1299 It is then a customer/user responsibility to ensure that the SNMP entity 1300 giving access to an instance of this MIB, is properly configured to give 1301 access to the objects only to those principals (users) that have 1302 legitimate rights to indeed GET or SET (change/create/delete) them. 1304 7. Acknowledgements 1306 Tom Pusateri and Billy Ng both provided valuable input on early versions 1307 of this draft. It was completed based upon feedback from Mike Davison 1308 and Ketan Talaulikar. 1310 8. Authors' Addresses 1312 Bill Fenner 1313 75 Willow Road 1314 Menlo Park, CA 94025 1315 Phone: +1 650 867 6073 1316 EMail: fenner@research.att.com 1318 Dave Thaler 1319 Microsoft Corporation 1320 One Microsoft Way 1321 Redmond, WA 98052-6399 1322 Phone: +1 425 703 8835 1323 EMail: dthaler@microsoft.com 1325 9. Normative References 1327 [1] Fenner, B. and D. Meyer, editors, "Multicast Source Discovery 1328 Protocol (MSDP)", RFC 3618, October 2003. 1330 [2] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for 1331 version 3 of the Simple Network Management Protocol (SNMPv3)", STD 1332 62, RFC 3414, December 2002. 1334 [3] Wijnen, B., Preshun, R. and K. McCloghrie, "View-based Access 1335 Control Model (VACM) for the Simple Network Management Protocol 1336 (SNMP)", STD 62, RFC 3415, December 2002. 1338 [4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1339 and S. Waldbusser, "Structure of Management Information Version 2 1340 (SMIv2)", STD 58, RFC 2578, April 1999. 1342 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1343 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1344 2579, April 1999. 1346 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1347 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1348 2580, April 1999. 1350 9.1. Informative References 1352 [7] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 1353 Applicability Statements for Internet-Standard Management 1354 Framework", RFC 3410, December 2002. 1356 10. Full Copyright Statement 1358 Copyright (C) The Internet Society (2004). This document is subject to 1359 the rights, licenses and restrictions contained in BCP 78, and except as 1360 set forth therein, the authors retain all their rights. 1362 The IETF takes no position regarding the validity or scope of any 1363 Intellectual Property Rights or other rights that might be claimed to 1364 pertain to the implementation or use of the technology described in this 1365 document or the extent to which any license under such rights might or 1366 might not be available; nor does it represent that it has made any 1367 independent effort to identify any such rights. Information on the 1368 procedures with respect to rights in RFC documents can be found in BCP 1369 78 and BCP 79. 1371 Copies of IPR disclosures made to the IETF Secretariat and any 1372 assurances of licenses to be made available, or the result of an attempt 1373 made to obtain a general license or permission for the use of such 1374 proprietary rights by implementers or users of this specification can be 1375 obtained from the IETF on-line IPR repository at 1376 http://www.ietf.org/ipr. 1378 The IETF invites any interested party to bring to its attention any 1379 copyrights, patents or patent applications, or other proprietary rights 1380 that may cover technology that may be required to implement this 1381 standard. Please address the information to the IETF at ietf- 1382 ipr@ietf.org. 1384 This document and the information contained herein are provided on an 1385 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 1386 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1387 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1388 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1389 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1390 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.