idnits 2.17.00 (12 Aug 2021) /tmp/idnits35313/draft-ietf-ipngwg-mld-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 13 longer pages, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 4 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([RFC2119], [RFC2710]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (January 2001) is 7789 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 2119' is mentioned on line 43, but not defined == Unused Reference: 'RFC2119' is defined on line 591, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 17 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPNGWG Working Group B. Haberman 2 Internet Draft Nortel Networks 3 draft-ietf-ipngwg-mld-mib-04.txt R. Worzella 4 July 2000 IBM 5 Expires January 2001 7 IP Version 6 Management Information Base for 8 The Multicast Listener Discovery Protocol 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. Internet-Drafts are draft documents valid for a maximum of 19 six months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet- Drafts 21 as reference material or to cite them other than as "work in 22 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 Abstract 32 This document defines an experimental portion of the Management 33 Information Base (MIB) for use with network management protocols in 34 Internet Protocol Version 6 internets. Specifically, this document 35 is the MIB module that defines managed objects for implementations of 36 the Multicast Listener Discovery Protocol [RFC2710]. 38 Terminology 40 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 41 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 42 this document are to be interpreted as described in [RFC 2119]. 44 1. The SNMP Management Framework 46 Haberman, Worzella 1 47 The SNMP Management Framework presently consists of five major 48 components: 50 An overall architecture, described in RFC 2571 [RFC2571]. 52 Mechanisms for describing and naming objects and events for the 53 purpose of management. The first version of this Structure of 54 Management Information (SMI) is called SMIv1 and described in STD 55 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 56 [RFC1215]. The second version, called SMIv2, is described in STD 58, 57 RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580[RFC2580]. 59 Message protocols for transferring management information. The first 60 version of the SNMP message protocol is called SNMPv1 and described 61 in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message 62 protocol, which is not an Internet standards track protocol, is 63 called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 64 [RFC1906]. The third version of the message protocol is called 65 SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and 66 RFC 2574 [RFC2574]. 68 Protocol operations for accessing management information. The first 69 set of protocol operations and associated PDU formats is described 70 in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations 71 and associated PDU formats is described in RFC 1905 [RFC1905]. 73 A set of fundamental applications described in RFC 2573[RFC2573] and 74 the view-based access control mechanism described in RFC 2575 75 [RFC2575]. 77 A more detailed introduction to the current SNMP Management 78 Framework can be found in RFC 2570 [RFC2570]. 80 Managed objects are accessed via a virtual information store, termed 81 the Management Information Base or MIB. Objects in the MIB are 82 defined using the mechanisms defined in the SMI. 84 This memo specifies a MIB module that is compliant to the SMIv2. A 85 MIB conforming to the SMIv1 can be produced through the appropriate 86 translations. The resulting translated MIB must be semantically 87 equivalent, except where objects or events are omitted because no 88 translation is possible (use of Counter64). Some machine-readable 89 information in SMIv2 will be converted into textual descriptions in 90 SMIv1 during the translation process. However, this loss of machine- 91 readable information is not considered to change the semantics of 92 the MIB. 94 2. Overview 96 This MIB module contains two tables: 98 Haberman, Worzella 2 99 1.The MLD Interface Table, which contains one row for each 100 interface on which MLD is enabled. 102 2.The MLD Cache Table which contains one row for each IPv6 103 Multicast group for which there are members on a particular 104 interface. 106 Both tables are intended to be implemented by hosts and routers. 107 Some objects in each table apply to routers only. 109 3. Definitions 111 IPV6-MLD-MIB DEFINITIONS ::= BEGIN 113 IMPORTS 114 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32, 115 Unsigned32, TimeTicks, mib-2 FROM SNMPv2-SMI 116 RowStatus, TruthValue FROM SNMPv2-TC 117 Ipv6Address, Ipv6IfIndexOrZero, 118 Ipv6IfIndex FROM IPV6-TC 119 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 121 mldMIB MODULE-IDENTITY 122 LAST-UPDATED "200007051000Z" 123 ORGANIZATION "IETF IPNGWG Working Group." 124 CONTACT-INFO 125 " Brian Haberman 126 Nortel Networks 127 4309 Emperor Blvd. 128 Durham, NC 27703 129 USA 131 Phone: +1 919 992 4439 132 e-mail: haberman@nortelnetworks.com" 133 DESCRIPTION 134 "The MIB module for MLD Management." 135 REVISION "200007051000Z" 136 DESCRIPTION 137 "Initial version, published as RFC XXXX." 138 ::= { mib-2 xx } 139 -- NOTE TO RFC EDITOR: When this document is published as 140 -- an RFC, replace xx with IANA-assigned value and delete 141 -- this comment. 143 mldMIBObjects OBJECT IDENTIFIER ::= { mldMIB 1 } 145 Haberman, Worzella 3 146 -- 147 -- The MLD Interface Table 148 -- 150 mldInterfaceTable OBJECT-TYPE 151 SYNTAX SEQUENCE OF MldInterfaceEntry 152 MAX-ACCESS not-accessible 153 STATUS current 154 DESCRIPTION 155 "The (conceptual) table listing the interfaces on which 156 MLD is enabled." 157 ::= { mldMIBObjects 1 } 159 mldInterfaceEntry OBJECT-TYPE 160 SYNTAX MldInterfaceEntry 161 MAX-ACCESS not-accessible 162 STATUS current 163 DESCRIPTION 164 "An entry (conceptual row) representing an interface on 165 which MLD is enabled." 166 INDEX { mldInterfaceIfIndex } 167 ::= { mldInterfaceTable 1 } 169 MldInterfaceEntry ::= SEQUENCE { 170 mldInterfaceIfIndex Ipv6IfIndex, 171 mldInterfaceQueryInterval Unsigned32, 172 mldInterfaceStatus RowStatus, 173 mldInterfaceVersion Unsigned32, 174 mldInterfaceQuerier Ipv6Address, 175 mldInterfaceQueryMaxResponseDelay Unsigned32, 176 mldInterfaceJoins Counter32, 177 mldInterfaceGroups Gauge32, 178 mldInterfaceRobustness Unsigned32, 179 mldInterfaceLastListenQueryIntvl Unsigned32, 180 mldInterfaceProxyIfIndex Ipv6IfIndexOrZero, 181 mldInterfaceQuerierUpTime TimeTicks, 182 mldInterfaceQuerierExpiryTime TimeTicks 183 } 185 mldInterfaceIfIndex OBJECT-TYPE 187 SYNTAX Ipv6IfIndex 188 MAX-ACCESS not-accessible 189 STATUS current 190 DESCRIPTION 191 "The internetwork-layer interface value of the interface 192 for which MLD is enabled." 193 ::= { mldInterfaceEntry 1 } 195 mldInterfaceQueryInterval OBJECT-TYPE 196 SYNTAX Unsigned32 197 UNITS "seconds" 199 Haberman, Worzella 4 200 MAX-ACCESS read-create 201 STATUS current 202 DESCRIPTION 203 "The frequency at which MLD Host-Query packets are 204 transmitted on this interface." 205 DEFVAL { 125 } 206 ::= { mldInterfaceEntry 2 } 208 mldInterfaceStatus OBJECT-TYPE 209 SYNTAX RowStatus 210 MAX-ACCESS read-create 211 STATUS current 212 DESCRIPTION 213 "The activation of a row enables MLD on the interface. 214 The destruction of a row disables MLD on the interface." 215 ::= { mldInterfaceEntry 3 } 217 mldInterfaceVersion OBJECT-TYPE 218 SYNTAX Unsigned32 219 MAX-ACCESS read-create 220 STATUS current 221 DESCRIPTION 222 "The version of MLD which is running on this interface. 223 This object is a place holder to allow for new versions 224 of MLD to be introduced. Version 1 of MLD is defined 225 in RFC 2710." 226 DEFVAL { 1 } 227 ::= { mldInterfaceEntry 4 } 229 mldInterfaceQuerier OBJECT-TYPE 230 SYNTAX Ipv6Address 231 MAX-ACCESS read-only 232 STATUS current 233 DESCRIPTION 234 "The address of the MLD Querier on the IPv6 subnet to 235 which this interface is attached." 236 ::= { mldInterfaceEntry 5 } 238 mldInterfaceQueryMaxResponseDelay OBJECT-TYPE 239 SYNTAX Unsigned32 240 UNITS "seconds" 241 MAX-ACCESS read-create 242 STATUS current 243 DESCRIPTION 244 "The maximum query response time advertised in MLD 245 queries on this interface." 246 DEFVAL { 10 } 247 ::= { mldInterfaceEntry 6 } 249 mldInterfaceJoins OBJECT-TYPE 250 SYNTAX Counter32 251 MAX-ACCESS read-only 253 Haberman, Worzella 5 254 STATUS current 255 DESCRIPTION 256 "The number of times a group membership has been added on 257 this interface; that is, the number of times an entry for 258 this interface has been added to the Cache Table. This 259 object gives an indication of the amount of MLD activity 260 over time." 261 ::= { mldInterfaceEntry 7 } 263 mldInterfaceGroups OBJECT-TYPE 264 SYNTAX Gauge32 265 MAX-ACCESS read-only 266 STATUS current 267 DESCRIPTION 268 "The current number of entries for this interface in the 269 Cache Table." 270 ::= { mldInterfaceEntry 8 } 272 mldInterfaceRobustness OBJECT-TYPE 273 SYNTAX Unsigned32 274 MAX-ACCESS read-create 275 STATUS current 276 DESCRIPTION 277 "The Robustness Variable allows tuning for the expected 278 packet loss on a subnet. If a subnet is expected to be 279 lossy, the Robustness Variable may be increased. MLD is 280 robust to (Robustness Variable-1) packet losses. The 281 discussion of the Robustness Variable is in Section 7.1 282 of RFC 2710." 283 DEFVAL { 2 } 284 ::= { mldInterfaceEntry 9 } 286 mldInterfaceLastListenQueryIntvl OBJECT-TYPE 287 SYNTAX Unsigned32 288 UNITS "seconds" 289 MAX-ACCESS read-create 290 STATUS current 291 DESCRIPTION 292 "The Last Member Query Interval is the Max Response 293 Delay inserted into Group-Specific Queries sent in 294 response to Leave Group messages, and is also the amount 295 of time between Group-Specific Query messages. This 296 value may be tuned to modify the leave latency of the 297 network. A reduced value results in reduced time to 298 detect the loss of the last member of a group." 299 DEFVAL { 1 } 300 ::= { mldInterfaceEntry 10 } 302 mldInterfaceProxyIfIndex OBJECT-TYPE 303 SYNTAX Ipv6IfIndexOrZero 304 MAX-ACCESS read-create 305 STATUS current 307 Haberman, Worzella 6 308 DESCRIPTION 309 "Some devices implement a form of MLD proxying whereby 310 memberships learned on the interface represented by this 311 row, cause MLD Multicast Listener Reports to be sent on 312 the interface whose ifIndex value is given by this 313 object. Such a device would implement mldRouterMIBGroup 314 only on its router interfaces (those interfaces with 315 non-zero mldInterfaceProxyIfIndex). Typically, the 316 value of this object is 0, indicating that no proxying 317 is being done." 318 DEFVAL { 0 } 319 ::= { mldInterfaceEntry 11 } 321 mldInterfaceQuerierUpTime OBJECT-TYPE 322 SYNTAX TimeTicks 323 MAX-ACCESS read-only 324 STATUS current 325 DESCRIPTION 326 "The time since mldInterfaceQuerier was last changed." 327 ::= { mldInterfaceEntry 12 } 329 mldInterfaceQuerierExpiryTime OBJECT-TYPE 330 SYNTAX TimeTicks 331 MAX-ACCESS read-only 332 STATUS current 333 DESCRIPTION 334 "The time remaining before the Other Querier Present 335 Timer expires. If the local system is the querier, 336 the value of this object is zero." 337 ::= { mldInterfaceEntry 13 } 339 -- 340 -- The MLD Cache Table 341 -- 343 mldCacheTable OBJECT-TYPE 344 SYNTAX SEQUENCE OF MldCacheEntry 345 MAX-ACCESS not-accessible 346 STATUS current 347 DESCRIPTION 348 "The (conceptual) table listing the IPv6 multicast 349 groups for which there are members on a particular 350 interface." 351 ::= { mldMIBObjects 2 } 353 mldCacheEntry OBJECT-TYPE 354 SYNTAX MldCacheEntry 355 MAX-ACCESS not-accessible 356 STATUS current 357 DESCRIPTION 358 "An entry (conceptual row) in the mldCacheTable." 360 Haberman, Worzella 7 361 INDEX { mldCacheAddress, mldCacheIfIndex } 362 ::= { mldCacheTable 1 } 364 MldCacheEntry ::= SEQUENCE { 365 mldCacheAddress Ipv6Address, 366 mldCacheIfIndex Ipv6IfIndex, 367 mldCacheSelf TruthValue, 368 mldCacheLastReporter Ipv6Address, 369 mldCacheUpTime TimeTicks, 370 mldCacheExpiryTime TimeTicks, 371 mldCacheStatus RowStatus 372 } 374 mldCacheAddress OBJECT-TYPE 375 SYNTAX Ipv6Address 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "The IPv6 multicast group address for which this entry 380 contains information." 381 ::= { mldCacheEntry 1 } 383 mldCacheIfIndex OBJECT-TYPE 384 SYNTAX Ipv6IfIndex 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "The internetwork-layer interface for which this entry 389 contains information for an IPv6 multicast group 390 address." 391 ::= { mldCacheEntry 2 } 393 mldCacheSelf OBJECT-TYPE 394 SYNTAX TruthValue 395 MAX-ACCESS read-create 396 STATUS current 397 DESCRIPTION 398 "An indication of whether the local system is a member of 399 this group address on this interface." 400 DEFVAL { true } 401 ::= { mldCacheEntry 3 } 403 mldCacheLastReporter OBJECT-TYPE 404 SYNTAX Ipv6Address 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The IPv6 address of the source of the last membership 409 report received for this IPv6 Multicast group address on 410 this interface. If no membership report has been 411 received, this object has the value 0::0." 412 ::= { mldCacheEntry 4 } 414 Haberman, Worzella 8 415 mldCacheUpTime OBJECT-TYPE 416 SYNTAX TimeTicks 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "The time elapsed since this entry was created." 421 ::= { mldCacheEntry 5 } 423 mldCacheExpiryTime OBJECT-TYPE 424 SYNTAX TimeTicks 425 MAX-ACCESS read-only 426 STATUS current 427 DESCRIPTION 428 "The minimum amount of time remaining before this entry 429 will be aged out. A value of 0 indicates that the entry 430 is only present because mldCacheSelf is true and that if 431 the router left the group, this entry would be aged out 432 immediately. Note that some implementations may process 433 Membership Reports from the local system in the same way 434 as reports from other hosts, so a value of 0 is not 435 required." 436 ::= { mldCacheEntry 6 } 438 mldCacheStatus OBJECT-TYPE 439 SYNTAX RowStatus 440 MAX-ACCESS read-create 441 STATUS current 442 DESCRIPTION 443 "The status of this row, by which new entries may be 444 created, or existing entries deleted from this table." 445 ::= { mldCacheEntry 7 } 447 -- conformance information 449 mldMIBConformance 450 OBJECT IDENTIFIER ::= { mldMIB 2 } 451 mldMIBCompliances 452 OBJECT IDENTIFIER ::= { mldMIBConformance 1 } 453 mldMIBGroups 454 OBJECT IDENTIFIER ::= { mldMIBConformance 2 } 456 -- compliance statements 458 mldHostMIBCompliance MODULE-COMPLIANCE 459 STATUS current 460 DESCRIPTION 461 "The compliance statement for hosts running MLD and 462 implementing the MLD MIB." 463 MODULE -- this module 465 Haberman, Worzella 9 466 MANDATORY-GROUPS { mldBaseMIBGroup, 467 mldHostMIBGroup 468 } 470 OBJECT mldInterfaceStatus 471 MIN-ACCESS read-only 472 DESCRIPTION 473 "Write access is not required." 475 ::= { mldMIBCompliances 1 } 477 mldRouterMIBCompliance MODULE-COMPLIANCE 478 STATUS current 479 DESCRIPTION 480 "The compliance statement for routers running MLD and 481 implementing the MLD MIB." 482 MODULE -- this module 483 MANDATORY-GROUPS { mldBaseMIBGroup, 484 mldRouterMIBGroup 485 } 487 OBJECT mldInterfaceStatus 488 MIN-ACCESS read-only 489 DESCRIPTION 490 "Write access is not required." 492 ::= { mldMIBCompliances 2 } 494 -- units of conformance 496 mldBaseMIBGroup OBJECT-GROUP 497 OBJECTS { mldCacheSelf, 498 mldCacheStatus, mldInterfaceStatus 499 } 500 STATUS current 501 DESCRIPTION 502 "The basic collection of objects providing management of 503 MLD. The mldBaseMIBGroup is designed to allow for the 504 manager creation and deletion of MLD cache entries." 505 ::= { mldMIBGroups 1 } 507 mldRouterMIBGroup OBJECT-GROUP 508 OBJECTS { mldCacheUpTime, mldCacheExpiryTime, 509 mldInterfaceQueryInterval, 510 mldInterfaceJoins, mldInterfaceGroups, 511 mldCacheLastReporter, 512 mldInterfaceQuerierUpTime, 513 mldInterfaceQuerierExpiryTime, 514 mldInterfaceQuerier, 515 mldInterfaceVersion, 516 mldInterfaceQueryMaxResponseDelay, 518 Haberman, Worzella 10 519 mldInterfaceRobustness, 520 mldInterfaceLastListenQueryIntvl 521 } 522 STATUS current 523 DESCRIPTION 524 "A collection of additional objects for management of MLD 525 in routers." 526 ::= { mldMIBGroups 2 } 528 mldHostMIBGroup OBJECT-GROUP 529 OBJECTS { mldInterfaceQuerier 530 } 531 STATUS current 532 DESCRIPTION 533 "A collection of additional objects for management of MLD 534 in hosts." 535 ::= { mldMIBGroups 3 } 537 mldProxyMIBGroup OBJECT-GROUP 538 OBJECTS { mldInterfaceProxyIfIndex } 539 STATUS current 540 DESCRIPTION 541 "A collection of additional objects for management of MLD 542 proxy devices." 543 ::= { mldMIBGroups 4 } 545 END 547 Security Considerations 549 This MIB contains readable objects whose values provide information 550 related to multicast sessions. Some of these objects could contain 551 sensitive information. In particular, the mldCacheSelf and 552 mldCacheLastReporter could be used to identify machines which are 553 listening to a given group address. There are also a number of 554 objects that have a MAX-ACCESS clause of read-write and/or read- 555 create, which allow an administrator to configure MLD in the router. 557 While unauthorized access to the readable objects is relatively 558 innocuous, unauthorized access to the write-able objects could cause 559 a denial of service. Hence, the support of SET operations in a non- 560 secure environment without proper protection can have a negative 561 effect on network operations. 563 SNMPv1 by itself is such an insecure environment. Even if the 564 network itself is secure (for example by using IPSec), even then, 565 there is no control as to who on the network is allowed to access and 566 SET (change/create/delete) the objects in this MIB. 568 Haberman, Worzella 11 569 It is recommended that the implementers consider the security 570 features as provided by the SNMPv3 framework. Specifically, the use 571 of the User-based Security Model RFC 2574 [RFC2574] and the View- 572 based Access Control Model RFC 2575 [RFC2575] is recommended. 574 It is then a customer/user responsibility to ensure that the SNMP 575 entity giving access to this MIB, is properly configured to give 576 access to those objects only to those principals (users) that have 577 legitimate rights to access them. 579 Acknowledgements 581 This MIB module is based on the IGMP MIB authored by Keith 582 McCloghrie, Dino Farinacci, and Dave Thaler. It was updated based on 583 feedback from the IPNGWG working group, Bert Wijnen, Peder Norgaard, 584 and extensive comments from Juergen Schoenwaelder. 586 References 588 [RFC2710] S. Deering, W. Fenner, B. Haberman, "Multicast Listener 589 Discovery (MLD) for IPv6", RFC 2710, October 1999. 591 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 592 Requirement Levels", RFC 2119, BCP14, March 1997. 594 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 595 Architecture for Describing SNMP Management 596 Frameworks", RFC 2571, April 1999. 598 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 599 Identification of Management Information for TCP/IP- 600 based Internets", STD 16, RFC 1155, May 1990. 602 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 603 STD 16, RFC 1212, March 1991. 605 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 606 the SNMP", RFC 1215, March 1991. 608 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 609 J., Rose, M., and S. Waldbusser, "Structure of 610 Management Information Version 2 (SMIv2)", STD 58, RFC 611 2578, April 1999. 613 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 614 J., Rose, M., and S. Waldbusser, "Textual Conventions 615 for SMIv2", STD 58, RFC 2579, April 1999. 617 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 618 J., Rose, M., and S. Waldbusser, "Conformance 620 Haberman, Worzella 12 621 Statements for SMIv2", STD 58, RFC 2580, April 1999. 623 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 624 "Simple Network Management Protocol", STD 15, RFC 1157, 625 May 1990. 627 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 628 "Introduction to Community-based SNMPv2", RFC 1901, 629 January 1996. 631 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 632 "Transport Mappings for Version 2 of the Simple Network 633 Management Protocol (SNMPv2)", RFC 1906, January 1996. 635 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 636 "Message Processing and Dispatching for the Simple 637 Network Management Protocol (SNMP)", RFC 2572, April 638 1999. 640 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 641 Model (USM) for version 3 of the Simple Network 642 Management Protocol (SNMPv3)", RFC 2574, April 1999. 644 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 645 "Protocol Operations for Version 2 of the Simple 646 Network Management Protocol (SNMPv2)", RFC 1905, 647 January 1996. 649 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 650 Applications", RFC 2573, April 1999. 652 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 653 Access Control Model (VACM) for the Simple Network 654 Management Protocol (SNMP)", RFC 2575, April 1999. 656 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 657 "Introduction to Version 3 of the Internet-standard 658 Network Management Framework", RFC 2570, April 1999. 660 Authors' Addresses 662 Brian Haberman 663 Nortel Networks 664 4309 Emperor Blvd. 665 Suite 200 666 Durham, NC 27703 667 USA 669 +1-919-992-4439 670 haberman@nortelnetworks.com 672 Haberman, Worzella 13 673 Randy Worzella 674 IBM Corporation 675 800 Park Office Drive 676 Research Triangle Park, NC 27709 677 USA 679 +1-919-254-2202 680 worzella@us.ibm.com 682 Full Copyright Statement 684 Copyright (C) The Internet Society (2000). All Rights Reserved. 686 This document and translations of it may be copied and furnished to 687 others, and derivative works that comment on or otherwise explain it 688 or assist in its implementation may be prepared, copied, published 689 and distributed, in whole or in part, without restriction of any 690 kind, provided that the above copyright notice and this paragraph are 691 included on all such copies and derivative works. However, this 692 document itself may not be modified in any way, such as by removing 693 the copyright notice or references to the Internet Society or other 694 Internet organizations, except as needed for the purpose of 695 developing Internet standards in which case the procedures for 696 copyrights defined in the Internet Standards process must be 697 followed, or as required to translate it into languages other than 698 English. 700 The limited permissions granted above are perpetual and will not be 701 revoked by the Internet Society or its successors or assigns. 703 This document and the information contained herein is provided on an 704 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 705 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 706 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 707 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 708 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 710 Haberman, Worzella 14