idnits 2.17.1 draft-ietf-msdp-mib-08.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([2]), 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 126: '... value MUST be 60....' RFC 2119 keyword, line 666: '...ection ___ 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 (October 2003) is 7491 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: 'SA-State-Period' on line 262 -- Looks like a reference, but probably isn't: 'ConnectRetry-period' on line 674 -- Looks like a reference, but probably isn't: 'HoldTime-Period' on line 686 -- Looks like a reference, but probably isn't: 'KeepAlive-Period' on line 698 == Unused Reference: '1' is defined on line 1278, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1825 (ref. '1') (Obsoleted by RFC 2401) == Outdated reference: A later version (-20) exists of draft-ietf-msdp-spec-01 ** Downref: Normative reference to an Experimental draft: draft-ietf-msdp-spec (ref. '2') ** Downref: Normative reference to an Informational RFC: RFC 3410 (ref. '6') Summary: 10 errors (**), 0 flaws (~~), 4 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 MSDP Working Group Bill Fenner 2 INTERNET-DRAFT AT&T Research 3 Expires: April 2004 Dave Thaler 4 Microsoft 5 October 2003 7 Multicast Source Discovery protocol MIB 8 10 Status of this Document 12 This document is an Internet-Draft and is in full conformance with all 13 provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF), its areas, and its working groups. Note that other groups 17 may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference material 22 or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This document is a product of the MSDP Working Group. Comments should 31 be addressed to the authors, or the mailing list at msdp@network- 32 services.uoregon.edu. 34 Copyright Notice 36 Copyright (C) The Internet Society (2003). All Rights Reserved. 38 Abstract 40 This memo defines an experimental portion of the Management Information 41 Base (MIB) for use with network management protocols in the Internet 42 community. In particular, it describes managed objects used for 43 managing Multicast Source Discovery Protocol (MSDP) [2] speakers. 45 Table of Contents 47 1. The The Internet-Standard Management Framework. . . . . . . . . . 2 48 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 2 49 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 50 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 51 5. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 52 6. Security Considerations . . . . . . . . . . . . . . . . . . . . . 26 53 7. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . 27 54 8. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 55 9. Full Copyright Statement. . . . . . . . . . . . . . . . . . . . . 28 56 10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 28 58 1. The The Internet-Standard Management Framework 60 For a detailed overview of the documents that describe the current 61 Internet-Standard Management Framework, please refer to section 7 of RFC 62 3410 [6]. 64 Managed objects are accessed via a virtual information store, termed the 65 Management Information Base or MIB. MIB objects are generally accessed 66 through the Simple Network Management Protocol (SNMP). Objects in the 67 MIB are defined using the mechanisms defined in the Structure of 68 Management Information (SMI). This memo specifies a MIB module that is 69 compliant to the SMIv2, which is described in STD 58, RFC 2578 [3], STD 70 58, RFC 2579 [4] and STD 58, RFC 2580 [5]. 72 2. Revision History 74 A record of changes which will be removed before publication. 76 17 October 2003 78 Undid most of the hard work since draft -03, which is the only 79 implementation I was able to find by querying the MSDP mailing 80 list. 82 29 May 2003 84 Republished with no changes. How did it get to be almost 2 years? 86 18 July 2001 88 Since the INET-ADDRESS-MIB relaxed restrictions on InetAddressType, 89 remove msdpPeerLocalAddressType, rename msdpSACacheGroupAddrType to 90 msdpCacheAddrType, remove msdpCacheSourceAddrType, 91 msdpSACacheOriginRPType, msdpSACachePeerLearnedFromType, 92 msdpSACacheRPFPeerType. 94 Updated the DESCRIPTION of msdpRequestsTable to describe exactly 95 how it is used. 97 Added msdpPeerDiscontinuityTime. 99 Changed msdpPeerFsmEstablishedTime to a TimeStamp instead of a 100 counting number of seconds. 102 Changed msdpPeerInMessageElapsedTime to msdpPeerInMessageTime and 103 changed it to a TimeStamp. 105 Added msdpMeshGroupTable. 107 Updated conformance information. 109 1 March 2001 111 Added msdpPeerIfIndex. 113 Converted all IpAddress items to InetAddressType/InetAddress pairs. 114 This bigtime violates RFC2578's rules about MIB evolution, so take 115 extra care when implementing this change. 117 Added msdpRequestsPriority, in order to allow configuration of 118 multiple peers to whom Requests will be sent. Note that this 119 violates RFC2578's rules about MIB evolution, so take extra care 120 when implementing this change. 122 Removed DEFVAL on scalars, since it should only be needed for table 123 row creation. 125 Removed msdpPeerSAAdvPeriod, since the spec changed to say its 126 value MUST be 60. 128 Added none(0) to msdpPeerEncapsulationType enumeration XXX is this 129 OK? should it be 4? 131 Removed msdpPeerEncapsulationState since the encapsulation 132 "negotiation" was removed from the spec. 134 Added msdpRPAddress to specify the RP address to use when sourcing 135 SA messages. 137 Added msdpSACacheSourcePrefix to msdpSACacheTable, and added it to 138 the INDEX. Note that this violates RFC2578's rules about MIB 139 evolution, so take extra care when implementing this change. 141 Completely renumbered the MIB, removing the extra level of 142 msdpMIBobjects and creating an msdpScalars group to contain all 143 scalars. Note that this violates RFC2578's rules about MIB 144 evolution, so take extra care when implementing this change. 146 16 December 1999 148 Added msdpSAHoldDownPeriod, msdpPeerEncapsulationState, 149 msdpPeerEncapsulationType, msdpPeerConnectionAttempts, 150 msdpPeerInNotifications, msdpPeerOutNotifications, and 151 msdpLastError 153 Removed msdpPeerConfigMethod, since this has disappeared from the 154 spec. 156 Renamed the states in msdpPeerState to go with the state machine in 157 the spec. 159 Added msdpPeerLocalPort and msdpPeerRemotePort in order to provide 160 full information about the TCP connection in use. I'd like to 161 reorder the Peer Table but that can wait until the MIB gets 162 published as an RFC in order to only change things like that once. 164 Added msdpSACacheOriginRP as an INDEX to the msdpSACacheTable. 165 Note that this violates RFC2578's rules about MIB evolution, so 166 take extra care when implementing this change. 168 25 June 1999 170 Renamed to DRAFT-MSDP-MIB. It will be renamed back to MSDP-MIB 171 when it gets renumbered under mib-2, in order to avoid module 172 naming problems. 174 Turned msdpSendRequestsTo into a table in order to handle 175 administratively scoped groups with different RP's. 177 27 May 1999 179 Added IANA-assigned experimental OID 181 Added msdpSendRequestsTo and msdpPeerProcessRequestsFrom to 182 configure MSDP SA-Request/Response processing. 184 Added msdpPeerDataTtl to allow TTL scoping of data packets 185 forwarded across MSDP peerings. 187 Renumbered msdpSACacheInDataPackets and further items in 188 msdpSACacheTable, to eliminate duplicate OIDs 190 20 April 1999 192 initial version. 194 3. Overview 196 This MIB module contains three scalars and three tables. The tables 197 are: 199 o the Requests Table, containing the longest-match table used to 200 determine the peer to send SA-Requests to for a given group; 202 o the Peer Table, containing information on the peers; and 204 o the Source-Active Cache Table, containing the SA cache entries. 206 4. Definitions 208 -- 209 -- 210 DRAFT-MSDP-MIB DEFINITIONS ::= BEGIN 212 IMPORTS 213 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 214 experimental, Counter32, Gauge32, TimeTicks, Integer32, 215 IpAddress 216 FROM SNMPv2-SMI 217 RowStatus, TruthValue, TimeStamp, DisplayString 218 FROM SNMPv2-TC 219 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 220 FROM SNMPv2-CONF 221 InterfaceIndexOrZero 222 FROM IF-MIB; 224 msdpMIB MODULE-IDENTITY 225 LAST-UPDATED "200310170000Z" 226 ORGANIZATION "IETF MSDP Working Group" 227 CONTACT-INFO 228 "Bill Fenner 229 75 Willow Road 230 Menlo Park, CA 94025 231 Phone: +1 650 867 6073 232 E-mail: fenner@research.att.com 234 Dave Thaler 235 One Microsoft Way 236 Redmond, WA 98052 237 Phone: +1 425 703 8835 238 Email: dthaler@microsoft.com" 239 DESCRIPTION 240 "An experimental MIB module for MSDP Management." 241 ::= { experimental 92 } 243 msdpMIBobjects OBJECT IDENTIFIER ::= { msdpMIB 1 } 245 msdp OBJECT IDENTIFIER ::= { msdpMIBobjects 1 } 247 msdpEnabled OBJECT-TYPE 248 SYNTAX TruthValue 249 MAX-ACCESS read-write 250 STATUS current 251 DESCRIPTION 252 "The state of MSDP on this MSDP speaker - globally enabled or 253 disabled." 254 ::= { msdp 1 } 256 msdpCacheLifetime OBJECT-TYPE 257 SYNTAX TimeTicks 258 MAX-ACCESS read-write 259 STATUS current 260 DESCRIPTION 261 "The lifetime given to SA cache entries when created or 262 refreshed. This is the [SA-State-Period] in the MSDP spec. 263 A value of 0 means no SA caching is done by this MSDP 264 speaker." 265 ::= { msdp 2 } 267 msdpNumSACacheEntries OBJECT-TYPE 268 SYNTAX Gauge32 269 MAX-ACCESS read-only 270 STATUS current 271 DESCRIPTION 272 "The total number of entries in the SA Cache table." 273 ::= { msdp 3 } 275 msdpSAHoldDownPeriod OBJECT-TYPE 276 SYNTAX Integer32 (1..2147483647) 277 UNITS "seconds" 278 MAX-ACCESS read-only 279 STATUS current 280 DESCRIPTION 281 "The number of seconds in the MSDP SA Hold-down period." 282 ::= { msdp 9 } 284 msdpSAStatePeriod OBJECT-TYPE 285 SYNTAX Integer32 (1..2147483647) 286 UNITS "seconds" 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The number of seconds in the MSDP SA State period." 291 ::= { msdp 10 } 293 msdpRPAddress OBJECT-TYPE 294 SYNTAX IpAddress 295 MAX-ACCESS read-write 296 STATUS current 297 DESCRIPTION 298 "The RP address used when sourcing MSDP SA messages. May be 299 a zero length string on non-RP's or when the PIM RP address 300 is correct." 301 ::= { msdp 11 } 303 --- 304 --- The MSDP Requests table 305 --- 307 msdpRequestsTable OBJECT-TYPE 308 SYNTAX SEQUENCE OF MsdpRequestsEntry 309 MAX-ACCESS not-accessible 310 STATUS current 311 DESCRIPTION 312 "The (conceptual) table listing group ranges and MSDP peers 313 used when deciding where to send an SA Request message when 314 required. If SA Requests are not enabled, this table may be 315 empty. 317 In order to choose a peer to whom to send an SA Request for 318 a given group G, the subset of entries in this table whose 319 (msdpRequestsPeerType, msdpRequestsPeer) tuple represents a 320 peer whose msdpPeerState is established are examined. The 321 set is further reduced by examining only those entries for 322 which msdpPeerRequestsGroupAddressType equals the address 323 type of G, and the entries with the highest value of 324 msdpRequestsGroupPrefix are considered, where the group G 325 falls within the range described by the combination of 326 msdpRequestsGroup and msdpRequestsGroupPrefix. (This 327 sequence is commonly known as a 'longest-match' lookup.) 329 Finally, if multiple entries remain, the entry with the 330 lowest value of msdpRequestsPriority is chosen. The SA 331 Request message is sent to the peer described by this row." 332 ::= { msdp 4 } 334 msdpRequestsEntry OBJECT-TYPE 335 SYNTAX MsdpRequestsEntry 336 MAX-ACCESS not-accessible 337 STATUS current 338 DESCRIPTION 339 "An entry (conceptual row) representing a group range used 340 when deciding where to send an SA Request message." 341 INDEX { msdpRequestsGroupAddress, msdpRequestsGroupMask } 342 ::= { msdpRequestsTable 1 } 344 MsdpRequestsEntry ::= SEQUENCE { 345 msdpRequestsGroupAddress IpAddress, 346 msdpRequestsGroupMask IpAddress, 347 msdpRequestsPeer IpAddress, 348 msdpRequestsStatus RowStatus 349 } 351 msdpRequestsGroupAddress OBJECT-TYPE 352 SYNTAX IpAddress 353 MAX-ACCESS not-accessible 354 STATUS current 355 DESCRIPTION 356 "The group address that, when combined with the mask in this 357 entry, represents the group range to which this row 358 applies." 359 ::= { msdpRequestsEntry 1 } 361 msdpRequestsGroupMask OBJECT-TYPE 362 SYNTAX IpAddress 363 MAX-ACCESS not-accessible 364 STATUS current 365 DESCRIPTION 366 "The mask that, when combined with the group address in this 367 entry, represents the group range to which this row 368 applies." 369 ::= { msdpRequestsEntry 2 } 371 msdpRequestsPeer OBJECT-TYPE 372 SYNTAX IpAddress 373 MAX-ACCESS read-create 374 STATUS current 375 DESCRIPTION 376 "The peer to which MSDP SA Requests for groups matching this 377 entry's group range will be sent. This object combined with 378 msdpRequestsPeerType must match the INDEX of a row in the 379 msdpPeerTable, and to be considered, this peer's 380 msdpPeerState must be established." 381 ::= { msdpRequestsEntry 3 } 383 msdpRequestsStatus OBJECT-TYPE 384 SYNTAX RowStatus 385 MAX-ACCESS read-create 386 STATUS current 387 DESCRIPTION 388 "The status of this row, by which new rows may be added to 389 the table or old rows may be deleted." 390 ::= { msdpRequestsEntry 4 } 392 --- 393 --- The MSDP Peer table 394 --- 396 msdpPeerTable OBJECT-TYPE 397 SYNTAX SEQUENCE OF MsdpPeerEntry 398 MAX-ACCESS not-accessible 399 STATUS current 400 DESCRIPTION 401 "The (conceptual) table listing the MSDP speaker's peers." 402 ::= { msdp 5 } 404 msdpPeerEntry OBJECT-TYPE 405 SYNTAX MsdpPeerEntry 406 MAX-ACCESS not-accessible 407 STATUS current 408 DESCRIPTION 409 "An entry (conceptual row) representing an MSDP peer." 410 INDEX { msdpPeerRemoteAddress } 411 ::= { msdpPeerTable 1 } 413 MsdpPeerEntry ::= SEQUENCE { 414 msdpPeerRemoteAddress IpAddress, 415 msdpPeerState INTEGER, 416 msdpPeerRPFFailures Counter32, 417 msdpPeerInSAs Counter32, 418 msdpPeerOutSAs Counter32, 419 msdpPeerInSARequests Counter32, 420 msdpPeerOutSARequests Counter32, 421 msdpPeerInSAResponses Counter32, 422 msdpPeerOutSAResponses Counter32, 423 msdpPeerInControlMessages Counter32, 424 msdpPeerOutControlMessages Counter32, 425 msdpPeerInDataPackets Counter32, 426 msdpPeerOutDataPackets Counter32, 427 msdpPeerFsmEstablishedTransitions Counter32, 428 msdpPeerFsmEstablishedTime Gauge32, 429 msdpPeerInMessageElapsedTime Gauge32, 430 msdpPeerLocalAddress IpAddress, 431 msdpPeerConnectRetryInterval Integer32, 432 msdpPeerHoldTimeConfigured Integer32, 433 msdpPeerKeepAliveConfigured Integer32, 434 msdpPeerDataTtl Integer32, 435 msdpPeerProcessRequestsFrom TruthValue, 436 msdpPeerStatus RowStatus, 437 msdpPeerRemotePort Integer32, 438 msdpPeerLocalPort Integer32, 439 msdpPeerEncapsulationType INTEGER, 440 msdpPeerConnectionAttempts Counter32, 441 msdpPeerInNotifications Counter32, 442 msdpPeerOutNotifications Counter32, 443 msdpPeerLastError OCTET STRING, 444 msdpPeerDiscontinuityTime TimeStamp 445 } 447 msdpPeerRemoteAddress OBJECT-TYPE 448 SYNTAX IpAddress 449 MAX-ACCESS not-accessible 450 STATUS current 451 DESCRIPTION 452 "The address of the remote MSDP peer." 453 ::= { msdpPeerEntry 1 } 455 -- dunno what happened to 2. 457 msdpPeerState OBJECT-TYPE 458 SYNTAX INTEGER { 459 inactive(1), 460 listen(2), 461 connecting(3), 462 established(4), 463 disabled(5) 464 } 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The state of the MSDP TCP connection with this peer." 469 ::= { msdpPeerEntry 3 } 471 msdpPeerRPFFailures OBJECT-TYPE 472 SYNTAX Counter32 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The number of SA messages received from this peer which 477 failed the Peer-RPF check. 479 Discontinuities in the value of this counter can occur at 480 re-initialization of the management system, and at other 481 times as indicated by the value of 482 msdpPeerDiscontinuityTime." 483 ::= { msdpPeerEntry 4 } 485 msdpPeerInSAs OBJECT-TYPE 486 SYNTAX Counter32 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The number of MSDP SA messages received on this connection. 492 Discontinuities in the value of this counter can occur at 493 re-initialization of the management system, and at other 494 times as indicated by the value of 495 msdpPeerDiscontinuityTime." 496 ::= { msdpPeerEntry 5 } 498 msdpPeerOutSAs OBJECT-TYPE 499 SYNTAX Counter32 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The number of MSDP SA messages transmitted on this 504 connection. 506 Discontinuities in the value of this counter can occur at 507 re-initialization of the management system, and at other 508 times as indicated by the value of 509 msdpPeerDiscontinuityTime." 510 ::= { msdpPeerEntry 6 } 512 msdpPeerInSARequests OBJECT-TYPE 513 SYNTAX Counter32 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "The number of MSDP SA-Request messages received on this 518 connection. 520 Discontinuities in the value of this counter can occur at 521 re-initialization of the management system, and at other 522 times as indicated by the value of 523 msdpPeerDiscontinuityTime." 524 ::= { msdpPeerEntry 7 } 526 msdpPeerOutSARequests OBJECT-TYPE 527 SYNTAX Counter32 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "The number of MSDP SA-Request messages transmitted on this 532 connection. 534 Discontinuities in the value of this counter can occur at 535 re-initialization of the management system, and at other 536 times as indicated by the value of 537 msdpPeerDiscontinuityTime." 538 ::= { msdpPeerEntry 8 } 540 msdpPeerInSAResponses OBJECT-TYPE 541 SYNTAX Counter32 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "The number of MSDP SA-Response messages received on this 546 connection. 548 Discontinuities in the value of this counter can occur at 549 re-initialization of the management system, and at other 550 times as indicated by the value of 551 msdpPeerDiscontinuityTime." 552 ::= { msdpPeerEntry 9 } 554 msdpPeerOutSAResponses OBJECT-TYPE 555 SYNTAX Counter32 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION 559 "The number of MSDP SA Response messages transmitted on this 560 TCP connection. 562 Discontinuities in the value of this counter can occur at 563 re-initialization of the management system, and at other 564 times as indicated by the value of 565 msdpPeerDiscontinuityTime." 566 ::= { msdpPeerEntry 10 } 568 msdpPeerInControlMessages OBJECT-TYPE 569 SYNTAX Counter32 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The total number of MSDP messages received on this TCP 574 connection. 576 Discontinuities in the value of this counter can occur at 577 re-initialization of the management system, and at other 578 times as indicated by the value of 579 msdpPeerDiscontinuityTime." 580 ::= { msdpPeerEntry 11 } 582 msdpPeerOutControlMessages OBJECT-TYPE 583 SYNTAX Counter32 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "The total number of MSDP messages transmitted on this TCP 588 connection. 590 Discontinuities in the value of this counter can occur at 591 re-initialization of the management system, and at other 592 times as indicated by the value of 593 msdpPeerDiscontinuityTime." 594 ::= { msdpPeerEntry 12 } 596 msdpPeerInDataPackets OBJECT-TYPE 597 SYNTAX Counter32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "The total number of encapsulated data packets received from 602 this peer. 604 Discontinuities in the value of this counter can occur at 605 re-initialization of the management system, and at other 606 times as indicated by the value of 607 msdpPeerDiscontinuityTime." 608 ::= { msdpPeerEntry 13 } 610 msdpPeerOutDataPackets OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The total number of encapsulated data packets sent to this 616 peer. 618 Discontinuities in the value of this counter can occur at 619 re-initialization of the management system, and at other 620 times as indicated by the value of 621 msdpPeerDiscontinuityTime." 622 ::= { msdpPeerEntry 14 } 624 msdpPeerFsmEstablishedTransitions OBJECT-TYPE 625 SYNTAX Counter32 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "The total number of times the MSDP FSM transitioned into the 630 established state." 631 ::= { msdpPeerEntry 15 } 633 msdpPeerFsmEstablishedTime OBJECT-TYPE 634 SYNTAX Gauge32 635 UNITS "seconds" 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "This timer indicates how long (in seconds) this peer has 640 been in the Established state or how long since this peer 641 was last in the Established state. It is set to zero when a 642 new peer is configured or the MSDP speaker is booted." 643 ::= { msdpPeerEntry 16 } 645 msdpPeerInMessageElapsedTime OBJECT-TYPE 646 SYNTAX Gauge32 647 UNITS "seconds" 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "Elapsed time in seconds since the last MSDP message was 652 received from the peer. Each time msdpPeerInControlMessages 653 is incremented, the value of this object is set to zero (0). 654 It is also set to zero when the MSDP speaker is booted." 655 ::= { msdpPeerEntry 17 } 657 msdpPeerLocalAddress OBJECT-TYPE 658 SYNTAX IpAddress 659 MAX-ACCESS read-create 660 STATUS current 661 DESCRIPTION 662 "The local IP address of this entry's MSDP connection." 663 ::= { msdpPeerEntry 18 } 665 -- msdpPeerSAAdvPeriod has been removed 666 -- RFC 3618 section ___ says it MUST be 60 seconds. 668 msdpPeerConnectRetryInterval OBJECT-TYPE 669 SYNTAX Integer32 (1..65535) 670 UNITS "seconds" 671 MAX-ACCESS read-create 672 STATUS current 673 DESCRIPTION 674 "Time interval in seconds for the [ConnectRetry-period] for 675 this peer." 676 REFERENCE "RFC 3618 section 8.7" 677 DEFVAL { 120 } 678 ::= { msdpPeerEntry 20 } 680 msdpPeerHoldTimeConfigured OBJECT-TYPE 681 SYNTAX Integer32 (0|3..65535) 682 UNITS "seconds" 683 MAX-ACCESS read-create 684 STATUS current 685 DESCRIPTION 686 "Time interval in seconds for the [HoldTime-Period] 687 configured for this MSDP speaker with this peer." 688 REFERENCE "RFC 3618 section 8.5" 689 DEFVAL { 90 } 690 ::= { msdpPeerEntry 21 } 692 msdpPeerKeepAliveConfigured OBJECT-TYPE 693 SYNTAX Integer32 (0|1..21845) 694 UNITS "seconds" 695 MAX-ACCESS read-create 696 STATUS current 697 DESCRIPTION 698 "Time interval in seconds for the [KeepAlive-Period] 699 configured for this MSDP speaker with this peer. A 700 reasonable maximum value for this timer would be configured 701 to be one third of that of msdpPeerHoldTimeConfigured. If 702 the value of this object is zero (0), no periodic KEEPALIVE 703 messages are sent to the peer after the MSDP connection has 704 been established." 705 REFERENCE "RFC 3618 section 8.6" 706 DEFVAL { 30 } 707 ::= { msdpPeerEntry 22 } 709 msdpPeerDataTtl OBJECT-TYPE 710 SYNTAX Integer32 (0..255) 711 MAX-ACCESS read-create 712 STATUS current 713 DESCRIPTION 714 "The minimum TTL a packet is required to have before it may 715 be forwarded using SA encapsulation to this peer." 716 ::= { msdpPeerEntry 23 } 718 msdpPeerProcessRequestsFrom OBJECT-TYPE 719 SYNTAX TruthValue 720 MAX-ACCESS read-create 721 STATUS current 722 DESCRIPTION 723 "This object indicates whether or not to process MSDP SA 724 Request messages from this peer. If True(1), MSDP SA 725 Request messages from this peer are processed and replied to 726 (if appropriate) with SA Response messages. If False(2), 727 MSDP SA Request messages from this peer are silently 728 ignored. It defaults to False when msdpCacheLifetime is 0 729 and True when msdpCacheLifetime is non-0." 730 ::= { msdpPeerEntry 24 } 732 msdpPeerStatus OBJECT-TYPE 733 SYNTAX RowStatus 734 MAX-ACCESS read-create 735 STATUS current 736 DESCRIPTION 737 "The RowStatus object by which peers can be added and 738 deleted. A transition to 'active' will cause the MSDP Start 739 Event to be generated. A transition out of the 'active' 740 state will cause the MSDP Stop Event to be generated. Care 741 should be used in providing write access to this object 742 without adequate authentication." 743 ::= { msdpPeerEntry 25 } 745 msdpPeerRemotePort OBJECT-TYPE 746 SYNTAX Integer32 (0..65535) 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The remote port for the TCP connection between the MSDP 751 peers." 752 ::= { msdpPeerEntry 26 } 754 msdpPeerLocalPort OBJECT-TYPE 755 SYNTAX Integer32 (0..65535) 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "The local port for the TCP connection between the MSDP 760 peers." 762 ::= { msdpPeerEntry 27 } 764 -- msdpPeerEncapsulationState has been removed 765 -- because there is no longer an encapsulation 766 -- state machine. 768 msdpPeerEncapsulationType OBJECT-TYPE 769 SYNTAX INTEGER { 770 none(0), 771 tcp(1) 772 } 773 MAX-ACCESS read-create 774 STATUS current 775 DESCRIPTION 776 "The encapsulation in use when encapsulating data in SA 777 messages to this peer." 778 ::= { msdpPeerEntry 29 } 780 msdpPeerConnectionAttempts OBJECT-TYPE 781 SYNTAX Counter32 782 MAX-ACCESS read-only 783 STATUS current 784 DESCRIPTION 785 "The number of times the state machine has transitioned from 786 inactive to connecting." 787 ::= { msdpPeerEntry 30 } 789 msdpPeerInNotifications OBJECT-TYPE 790 SYNTAX Counter32 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "The number of MSDP Notification messages received from this 795 peer." 796 ::= { msdpPeerEntry 31 } 798 msdpPeerOutNotifications OBJECT-TYPE 799 SYNTAX Counter32 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "The number of MSDP Notification messages transmitted to this 804 peer." 805 ::= { msdpPeerEntry 32 } 807 msdpPeerLastError OBJECT-TYPE 808 SYNTAX OCTET STRING (SIZE (2)) 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION 812 "The last error code and subcode received via Notification 813 from this peer. If no error has occurred, this field is 814 zero. Otherwise, the first byte of this two byte OCTET 815 STRING contains the O-bit and error code, and the second 816 byte contains the subcode." 817 REFERENCE "RFC 3618 section 16.2.5 and 17" 818 DEFVAL { '0000'h } 819 ::= { msdpPeerEntry 33 } 821 msdpPeerDiscontinuityTime OBJECT-TYPE 822 SYNTAX TimeStamp 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "The value of sysUpTime on the most recent occasion at which 827 one or more of this entry's counters suffered a 828 discontinuity. See the DESCRIPTION of each object to see if 829 it is expected to have discontinuities. These 830 discontinuities may occur at peer connection establishment. 832 If no such discontinuities have occurred since the last 833 reinitialization of the local management subsystem, then 834 this object contains a zero value." 835 ::= { msdpPeerEntry 34 } 837 --- 838 --- The MSDP Source-Active Cache table 839 --- 841 msdpSACacheTable OBJECT-TYPE 842 SYNTAX SEQUENCE OF MsdpSACacheEntry 843 MAX-ACCESS not-accessible 844 STATUS current 845 DESCRIPTION 846 "The (conceptual) table listing the MSDP SA advertisements 847 currently in the MSDP speaker's cache." 848 ::= { msdp 6 } 850 msdpSACacheEntry OBJECT-TYPE 851 SYNTAX MsdpSACacheEntry 852 MAX-ACCESS not-accessible 853 STATUS current 854 DESCRIPTION 855 "An entry (conceptual row) representing an MSDP SA 856 advertisement. The INDEX to this table includes 857 msdpSACacheOriginRP for diagnosing incorrect MSDP 858 advertisements; normally a Group and Source pair would be 859 unique." 860 INDEX { msdpSACacheGroupAddr, msdpSACacheSourceAddr, 861 msdpSACacheOriginRP } 862 ::= { msdpSACacheTable 1 } 864 MsdpSACacheEntry ::= SEQUENCE { 865 msdpSACacheGroupAddr IpAddress, 866 msdpSACacheSourceAddr IpAddress, 867 msdpSACacheOriginRP IpAddress, 868 msdpSACachePeerLearnedFrom IpAddress, 869 msdpSACacheRPFPeer IpAddress, 870 msdpSACacheInSAs Counter32, 871 msdpSACacheInDataPackets Counter32, 872 msdpSACacheUpTime TimeTicks, 873 msdpSACacheExpiryTime TimeTicks, 874 msdpSACacheStatus RowStatus 875 } 877 msdpSACacheGroupAddr OBJECT-TYPE 878 SYNTAX IpAddress 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "The group address of the SA Cache entry." 883 ::= { msdpSACacheEntry 1 } 885 msdpSACacheSourceAddr OBJECT-TYPE 886 SYNTAX IpAddress 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "The source address of the SA Cache entry." 891 ::= { msdpSACacheEntry 2 } 893 msdpSACacheOriginRP OBJECT-TYPE 894 SYNTAX IpAddress 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "The RP of the SA Cache entry. This field is in the INDEX in 899 order to catch multiple RP's advertising the same source and 900 group." 901 ::= { msdpSACacheEntry 3 } 903 msdpSACachePeerLearnedFrom OBJECT-TYPE 904 SYNTAX IpAddress 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "The peer from which this SA Cache entry was last accepted. 909 This address must correspond to the msdpPeerRemoteAddress 910 value for a row in the MSDP Peer Table." 911 ::= { msdpSACacheEntry 4 } 913 msdpSACacheRPFPeer OBJECT-TYPE 914 SYNTAX IpAddress 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "The peer from which an SA message corresponding to this 919 cache entry would be accepted (i.e. the RPF peer for 920 msdpSACacheOriginRP). This may be different than 921 msdpSACachePeerLearnedFrom if this entry was created by an 922 MSDP SA-Response. This address must correspond to the 923 msdpPeerRemoteAddress value for a row in the MSDP Peer 924 Table, or may be 0.0.0.0 if no RPF peer exists." 925 ::= { msdpSACacheEntry 5 } 927 msdpSACacheInSAs OBJECT-TYPE 928 SYNTAX Counter32 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The number of MSDP SA messages received relevant to this 933 cache entry. This object must be initialized to zero when 934 creating a cache entry." 935 ::= { msdpSACacheEntry 6 } 937 msdpSACacheInDataPackets OBJECT-TYPE 938 SYNTAX Counter32 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "The number of MSDP encapsulated data packets received 943 relevant to this cache entry. This object must be 944 initialized to zero when creating a cache entry." 945 ::= { msdpSACacheEntry 7 } 947 msdpSACacheUpTime OBJECT-TYPE 948 SYNTAX TimeTicks 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "The time since this entry was placed in the SA cache." 954 ::= { msdpSACacheEntry 8 } 956 msdpSACacheExpiryTime OBJECT-TYPE 957 SYNTAX TimeTicks 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "The time remaining before this entry will expire from the SA 962 cache." 963 ::= { msdpSACacheEntry 9 } 965 msdpSACacheStatus OBJECT-TYPE 966 SYNTAX RowStatus 967 MAX-ACCESS read-write 968 STATUS current 969 DESCRIPTION 970 "The status of this row in the table. The only allowable 971 actions are to retrieve the status, which will be `active', 972 or to set the status to `destroy' in order to remove this 973 entry from the cache." 974 ::= { msdpSACacheEntry 10 } 976 -- 977 -- MSDP Mesh Group Membership table 978 -- 980 msdpMeshGroupTable OBJECT-TYPE 981 SYNTAX SEQUENCE OF MsdpMeshGroupEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "The (conceptual) table listing MSDP Mesh Group 986 configuration." 987 ::= { msdp 12 } 989 msdpMeshGroupEntry OBJECT-TYPE 990 SYNTAX MsdpMeshGroupEntry 991 MAX-ACCESS not-accessible 992 STATUS current 993 DESCRIPTION 994 "An entry (conceptual row) repesenting a peer in an MSDP Mesh 995 Group." 996 INDEX { msdpMeshGroupName, msdpMeshGroupPeerAddress } 997 ::= { msdpMeshGroupTable 1 } 999 MsdpMeshGroupEntry ::= SEQUENCE { 1000 msdpMeshGroupName DisplayString, 1001 msdpMeshGroupPeerAddress IpAddress, 1002 msdpMeshGroupStatus RowStatus 1003 } 1005 msdpMeshGroupName OBJECT-TYPE 1006 SYNTAX DisplayString (SIZE(1..64)) 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "The name of the mesh group." 1011 ::= { msdpMeshGroupEntry 1 } 1013 msdpMeshGroupPeerAddress OBJECT-TYPE 1014 SYNTAX IpAddress 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "A peer address that is a member of the mesh group with name 1019 msdpMeshGroupName. The msdpMeshGroupPeerAddress must match 1020 a row in the msdpPeerTable." 1021 ::= { msdpMeshGroupEntry 2 } 1023 msdpMeshGroupStatus OBJECT-TYPE 1024 SYNTAX RowStatus 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "This entry's status, by which new entries may be added to 1029 the table and old entries deleted." 1030 ::= { msdpMeshGroupEntry 3 } 1032 -- Traps 1034 msdpTraps OBJECT IDENTIFIER ::= { msdp 0 } 1036 msdpEstablished NOTIFICATION-TYPE 1037 OBJECTS { msdpPeerFsmEstablishedTransitions } 1038 STATUS current 1039 DESCRIPTION 1040 "The MSDP Established event is generated when the MSDP FSM 1041 enters the ESTABLISHED state." 1042 ::= { msdpTraps 1 } 1044 msdpBackwardTransition NOTIFICATION-TYPE 1045 OBJECTS { msdpPeerState } 1046 STATUS current 1047 DESCRIPTION 1048 "The MSDPBackwardTransition Event is generated when the MSDP 1049 FSM moves from a higher numbered state to a lower numbered 1050 state." 1051 ::= { msdpTraps 2 } 1053 -- conformance information 1055 msdpMIBConformance OBJECT IDENTIFIER ::= { msdp 8 } 1056 msdpMIBCompliances OBJECT IDENTIFIER ::= { msdpMIBConformance 1 } 1057 msdpMIBGroups OBJECT IDENTIFIER ::= { msdpMIBConformance 2 } 1059 -- compliance statements 1061 msdpMIBCompliance MODULE-COMPLIANCE 1062 STATUS current 1063 DESCRIPTION 1064 "The compliance statement for entities which implement the 1065 MSDP MIB." 1066 MODULE -- this module 1067 MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup, 1068 msdpMIBNotificationGroup } 1070 GROUP msdpMIBEncapsulationGroup 1071 DESCRIPTION 1072 "This group is mandatory if MSDP encapsulation interfaces are 1073 not given their own interface index numbers." 1074 GROUP msdpMIBSACacheGroup 1075 DESCRIPTION 1076 "This group is mandatory if the MSDP speaker has the ability 1077 to cache SA messages." 1078 GROUP msdpMIBRequestsGroup 1079 DESCRIPTION 1080 "This group is mandatory if the MSDP speaker has the ability 1081 to send SA-Request messages and parse SA-Response 1082 messages." 1083 GROUP msdpMIBRPGroup 1084 DESCRIPTION 1085 "This group is mandatory if the MSDP speaker sources (as 1086 opposed to forwards) MSDP messages." 1087 GROUP msdpMIBMeshGroupGroup 1088 DESCRIPTION 1089 "This group is mandatory if the MSDP speaker can participate 1090 in MSDP Mesh Groups." 1092 ::= { msdpMIBCompliances 1 } 1094 -- units of conformance 1095 msdpMIBGlobalsGroup OBJECT-GROUP 1096 OBJECTS { msdpEnabled } 1097 STATUS current 1098 DESCRIPTION 1099 "A collection of objects providing information on global MSDP 1100 state." 1101 ::= { msdpMIBGroups 1 } 1103 msdpMIBPeerGroup OBJECT-GROUP 1104 OBJECTS { msdpPeerRPFFailures, 1105 msdpPeerState, msdpPeerInSAs, msdpPeerOutSAs, 1106 msdpPeerInSARequests, msdpPeerOutSARequests, 1107 msdpPeerInSAResponses, msdpPeerOutSAResponses, 1108 msdpPeerInNotifications, msdpPeerOutNotifications, 1109 msdpPeerInControlMessages, msdpPeerOutControlMessages, 1110 msdpPeerFsmEstablishedTransitions, 1111 msdpPeerFsmEstablishedTime, 1112 msdpPeerLocalAddress, 1113 msdpPeerRemotePort, msdpPeerLocalPort, 1114 msdpPeerConnectRetryInterval, 1115 msdpPeerHoldTimeConfigured, 1116 msdpPeerKeepAliveConfigured, 1117 msdpPeerInMessageTime, 1118 msdpPeerProcessRequestsFrom, 1119 msdpPeerConnectionAttempts, 1120 msdpPeerLastError, 1121 msdpPeerIfIndex, 1122 msdpPeerStatus, 1123 msdpPeerDiscontinuityTime 1124 } 1125 STATUS current 1126 DESCRIPTION 1127 "A collection of objects for managing MSDP peers." 1128 ::= { msdpMIBGroups 2 } 1130 msdpMIBEncapsulationGroup OBJECT-GROUP 1131 OBJECTS { msdpPeerInDataPackets, msdpPeerOutDataPackets, 1132 msdpPeerDataTtl, 1133 msdpPeerEncapsulationType 1134 } 1135 STATUS current 1136 DESCRIPTION 1137 "A collection of objects for managing encapsulations if the 1138 MSDP encapsulation interfaces are not given interface 1139 indices." 1140 ::= { msdpMIBGroups 3 } 1142 msdpMIBSACacheGroup OBJECT-GROUP 1143 OBJECTS { msdpCacheLifetime, msdpNumSACacheEntries, 1144 msdpSAHoldDownPeriod, msdpSAStatePeriod, 1145 msdpSACachePeerLearnedFrom, 1146 msdpSACacheRPFPeer, msdpSACacheInSAs, 1147 msdpSACacheInDataPackets, 1148 msdpSACacheUpTime, msdpSACacheExpiryTime, 1149 msdpSACacheStatus } 1150 STATUS current 1151 DESCRIPTION 1152 "A collection of objects for managing MSDP SA cache entries." 1153 ::= { msdpMIBGroups 4 } 1155 msdpMIBNotificationGroup NOTIFICATION-GROUP 1156 NOTIFICATIONS { msdpEstablished, 1157 msdpBackwardTransition } 1158 STATUS current 1159 DESCRIPTION 1160 "A collection of notifications for signaling changes in MSDP 1161 peer relationships." 1162 ::= { msdpMIBGroups 5 } 1164 msdpMIBRequestsGroup OBJECT-GROUP 1165 OBJECTS { msdpRequestsPeerType, msdpRequestsPeer, msdpRequestsStatus } 1166 STATUS current 1167 DESCRIPTION 1168 "A collection of objects for managing MSDP Request 1169 transmission." 1170 ::= { msdpMIBGroups 6 } 1172 msdpMIBRPGroup OBJECT-GROUP 1173 OBJECTS { msdpRPAddressType, msdpRPAddress } 1174 STATUS current 1175 DESCRIPTION 1176 "A collection of objects for MSDP speakers that source MSDP 1177 messages." 1178 ::= { msdpMIBGroups 7 } 1180 msdpMIBMeshGroupGroup OBJECT-GROUP 1181 OBJECTS { msdpMeshGroupStatus } 1182 STATUS current 1183 DESCRIPTION 1184 "A collection of objects for MSDP speakers that can 1185 participate in MSDP mesh groups." 1186 ::= { msdpMIBGroups 8 } 1188 END 1189 5. Open Issues 1191 We need Components to describe multiple instances of MSDP in the same 1192 box (similar to the PIM MIB) 1194 Need a static RPF-peer table (see spec, section 14.3) 1196 Do we need an msdpPeerLastErrorSent, too, for what notification I last 1197 sent to this peer? 1199 The Backwards Transition notification won't trigger on established -> 1200 disabled. Is that desired? 1202 A table to express policy was suggested on the MSDP mailing list. More 1203 discussion is required before including this in the MIB. (Some of the 1204 more discussion: other than filtering announcements at an RP, policy in 1205 MSDP == black holes; policy should be in MBGP) 1207 An OID for control of encapsulation (e.g. SA-encapsulate the first N 1208 packets sent to this group?) was suggested, although it might be more 1209 appropriate to be a table for fine-grained control. 1211 Is the RowStatus object in the SACache appropriate? (e.g. used to flush 1212 potentially bad state) 1214 Should there be a mechanism to describe alternate methods of RPF? (e.g. 1215 statically configured peer address and RP address lists - could be a 1216 table indexed by peer address and RP address with a value of 1217 accept/deny) One or more MSDP default-peers? 1219 Is it appropriate to use names to distinguish mesh groups? 1221 Are there any other variables appropriate for configuring/managing mesh 1222 groups? 1224 Should the UDP port used for encapsulation be in the Peer table? 1226 6. Security Considerations 1228 There are a number of management objects defined in this MIB that have a 1229 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 1230 considered sensitive or vulnerable in some network environments. The 1231 support for SET operations in a non-secure environment without proper 1232 protection can have a negative effect on network operations. 1234 There are a number of managed objects in this MIB that may contain 1235 sensitive information. These are: 1237 -- XXX fill this in 1239 It is thus important to control even GET access to these objects and 1240 possibly to even encrypt the values of these object when sending them 1241 over the network via SNMP. Not all versions of SNMP provide features 1242 for such a secure environment. 1244 SNMPv1 by itself is not a secure environment. Even if the network 1245 itself is secure (for example by using IPSec), even then, there is no 1246 control as to who on the secure network is allowed to access and GET/SET 1247 (read/change/create/delete) the objects in this MIB. 1249 It is recommended that the implementers consider the security features 1250 as provided by the SNMPv3 framework. Specifically, the use of the User- 1251 based Security Model RFC 2574 [] and the View-based Access Control Model 1252 RFC 2575 [] is recommended. 1254 It is then a customer/user responsibility to ensure that the SNMP entity 1255 giving access to an instance of this MIB, is properly configured to give 1256 access to the objects only to those principals (users) that have 1257 legitimate rights to indeed GET or SET (change/create/delete) them. 1259 7. Acknowledgements 1261 Tom Pusateri and Billy Ng both provided valuable input on this draft. 1263 Bill Fenner 1264 75 Willow Road 1265 Menlo Park, CA 94025 1266 Phone: +1 650 867 6073 1267 EMail: fenner@research.att.com 1269 Dave Thaler 1270 Microsoft Corporation 1271 One Microsoft Way 1272 Redmond, WA 98052-6399 1273 Phone: +1 425 703 8835 1274 EMail: dthaler@microsoft.com 1276 8. References 1278 [1] R. Atkinson. "Security architecture for the internet protocol", RFC 1279 1825, August 1995. 1281 [2] Farinacci, D., Rekhter, Y., Lothberg, P., Kilmer, H., and J. Hall, 1282 "Multicast Source Discovery Protocol (MSDP)", draft-ietf-msdp- 1283 spec-01.txt, March 1999. 1285 [3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1286 and S. Waldbusser, "Structure of Management Information Version 2 1287 (SMIv2)", STD 58, RFC 2578, April 1999. 1289 [4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1290 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1291 2579, April 1999. 1293 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1294 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1295 2580, April 1999. 1297 [6] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 1298 Applicability Statements for Internet-Standard Management 1299 Framework", RFC 3410, December 2002. 1301 9. Full Copyright Statement 1303 10. Full Copyright Statement 1305 Copyright (C) The Internet Society (2003). All Rights Reserved. 1307 This document and translations of it may be copied and furnished to 1308 others, and derivative works that comment on or otherwise explain it or 1309 assist in its implementation may be prepared, copied, published and 1310 distributed, in whole or in part, without restriction of any kind, 1311 provided that the above copyright notice and this paragraph are included 1312 on all such copies and derivative works. However, this document itself 1313 may not be modified in any way, such as by removing the copyright notice 1314 or references to the Internet Society or other Internet organizations, 1315 except as needed for the purpose of developing Internet standards in 1316 which case the procedures for copyrights defined in the Internet 1317 Standards process must be followed, or as required to translate it into 1318 languages other than English. 1320 The limited permissions granted above are perpetual and will not be 1321 revoked by the Internet Society or its successors or assigns. 1323 This document and the information contained herein is provided on an "AS 1324 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1325 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1326 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1327 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1328 FITNESS FOR A PARTICULAR PURPOSE.