idnits 2.17.1 draft-ietf-ipngwg-ipv6-icmp-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 18 has weird spacing: '... This docum...' == Line 19 has weird spacing: '...working docum...' == Line 20 has weird spacing: '...working group...' == Line 21 has weird spacing: '... groups may ...' == Line 25 has weird spacing: '...-Drafts may ...' == (37 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 1997) is 9932 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) == Unused Reference: '2' is defined on line 658, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 678, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 681, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '4') ** Obsolete normative reference: RFC 1905 (ref. '5') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1573 (ref. '6') (Obsoleted by RFC 2233) ** Obsolete normative reference: RFC 1883 (ref. '7') (Obsoleted by RFC 2460) -- Possible downref: Non-RFC (?) normative reference: ref. '8' Summary: 14 errors (**), 0 flaws (~~), 10 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft IPv6 MIB: ICMPv6 Group February 1997 4 Management Information Base for IP Version 6: 5 ICMPv6 Group 7 9 Mon Feb 3 12:06:45 EST 1997 11 Dimitry Haskin 12 Steve Onishi 14 Bay Networks, Inc. 16 Status of this Memo 18 This document is an Internet-Draft. Internet-Drafts are 19 working documents of the Internet Engineering Task Force 20 (IETF), its areas, and its working groups. Note that other 21 groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months. Internet-Drafts may be updated, replaced, or 26 obsoleted by other documents at any time. It is not 27 appropriate to use Internet-Drafts as reference material or to 28 cite them other than as a ``working draft'' or ``work in 29 progress.'' 31 To learn the current status of any Internet-Draft, please 32 check the ``1id-abstracts.txt'' listing contained in the 33 Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), 34 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 35 ds.internic.net (US East Coast), or ftp.isi.edu (US West 36 Coast). 38 Abstract 40 This document is one in the series of documents that define 41 various MIB object groups for IPv6. Specifically, the ICMPv6 42 group is defined in this document. 44 This memo defines an experimental portion of the Management 45 Information Base (MIB) for use with network management 46 protocols in the IPv6-based internets. 48 This document specifies a MIB module in a manner that is both 49 compliant to the SNMPv2 SMI, and semantically identical to the 50 peer SNMPv1 definitions. 52 Table of Contents 54 1. The SNMPv2 Network Management Framework ............. 3 55 1.1 Object Definitions ................................ 3 56 2. Overview ............................................ 4 57 3. The ICMPv6 Group .................................... 5 58 4. Acknowledgements .................................... 17 59 5. References .......................................... 17 60 6. Security Considerations ............................. 18 61 7. Authors' Addresses................................... 18 63 1. The SNMPv2 Network Management Framework 65 The SNMPv2 Network Management Framework presently consists of 66 three major components. They are: 68 o the SMI, described in RFC 1902 [1] - the mechanisms used 69 for describing and naming objects for the purpose of 70 management. 72 o the MIB-II, described in RFC 1213/STD 17 [3] - the core 73 set of managed objects for the Internet suite of 74 protocols. 76 o RFC 1157 [4] and RFC 1905 [5] which define two versions 77 of the protocol used for network access to managed 78 objects. 80 The Framework permits new objects to be defined for the 81 purpose of experimentation and evaluation. 83 1.1. Object Definitions 85 Managed objects are accessed via a virtual information store, 86 termed the Management Information Base or MIB. Objects in the 87 MIB are defined using the subset of Abstract Syntax Notation 88 One (ASN.1) defined in the SMI. In particular, each object 89 object type is named by an OBJECT IDENTIFIER, an 90 administratively assigned name. The object type together with 91 an object instance serves to uniquely identify a specific 92 instantiation of the object. For human convenience, we often 93 use a textual string, termed the descriptor, to refer to the 94 object type. 96 2. Overview 98 This document is the one in the series of documents that 99 define various MIB object groups for IPv6. These groups are 100 the basic unit of conformance: if the semantics of a group is 101 applicable to an implementation, then it must implement all 102 objects in that group. For example, an implementation must 103 implement the TCP group if and only if it implements the TCP 104 over IPv6 protocol. At minimum, implementations must 105 implement the IPv6 General group [8] as well as the ICMPv6 106 group defined in this document. 108 This document defines the ICMPv6 group of the IPv6 MIB. 110 3. The ICMPv6 Group 112 IPV6-ICMP-MIB DEFINITIONS ::= BEGIN 114 IMPORTS 115 MODULE-IDENTITY, OBJECT-TYPE, 116 Counter32 FROM SNMPv2-SMI 117 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 118 ipv6 FROM IPV6-TC --- [8] 119 ipv6IfEntry FROM IPV6-MIB; --- [8] 121 ipv6IcmpMIB MODULE-IDENTITY 122 LAST-UPDATED "9702032155Z" 123 ORGANIZATION "IETF IPv6 MIB Working Group" 124 CONTACT-INFO 125 " Dimitry Haskin 127 Postal: Bay Networks, Inc. 128 2 Federal St. 129 Billerica, MA 01821 130 US 132 Tel: +1-508-916-8124 133 E-mail: dhaskin@baynetworks.com 135 Steve Onishi 137 Postal: Bay Networks, Inc. 138 3 Federal Street 139 Billerica, MA 01821 140 US 142 Tel: +1-508-916-3816 143 E-mail: sonishi@baynetworks.com" 144 DESCRIPTION 145 "The MIB module for entities implementing 146 the ICMPv6." 147 ::= { ipv6 2 } 149 -- the ICMPv6 group 151 ipv6IcmpMIBObjects OBJECT IDENTIFIER ::= { ipv6IcmpMIB 1 } 152 -- Per-interface ICMPv6 statistics table 154 ipv6IfIcmpTable OBJECT-TYPE 155 SYNTAX SEQUENCE OF Ipv6IfIcmpEntry 156 MAX-ACCESS not-accessible 157 STATUS current 158 DESCRIPTION 159 "IPv6 ICMP statistics" 160 ::= { ipv6IcmpMIBObjects 1 } 162 ipv6IfIcmpEntry OBJECT-TYPE 163 SYNTAX Ipv6IfIcmpEntry 164 MAX-ACCESS not-accessible 165 STATUS current 166 DESCRIPTION 167 "An ICMPv6 statistics entry containing 168 objects at a particular IPv6 interface. 170 Note that a receiving interface is 171 the interface to which a given ICMPv6 message 172 is addressed which may not be necessarily 173 the input interface for the message. 175 Similarly, the sending interface is 176 the interface that sources a given 177 ICMP message which is usually but not 178 necessarily the output interface for the message." 179 AUGMENTS { ipv6IfEntry } 180 ::= { ipv6IfIcmpTable 1 } 182 Ipv6IfIcmpEntry ::= SEQUENCE { 183 ipv6IfIcmpInMsgs 184 Counter32 , 185 ipv6IfIcmpInErrors 186 Counter32 , 187 ipv6IfIcmpInDestUnreachs 188 Counter32 , 189 ipv6IfIcmpInAdminProhibs 190 Counter32 , 191 ipv6IfIcmpInTimeExcds 192 Counter32 , 193 ipv6IfIcmpInParmProblems 194 Counter32 , 195 ipv6IfIcmpInPktTooBigs 196 Counter32 , 198 ipv6IfIcmpInEchos 199 Counter32 , 200 ipv6IfIcmpInEchoReps 201 Counter32 , 202 ipv6IfIcmpInRouterSolicits 203 Counter32 , 204 ipv6IfIcmpInRouterAdvertisements 205 Counter32 , 206 ipv6IfIcmpInNeighborSolicits 207 Counter32 , 208 ipv6IfIcmpInNeighborAdvertisements 209 Counter32 , 210 ipv6IfIcmpInRedirects 211 Counter32 , 212 ipv6IfIcmpInGroupMembQueries 213 Counter32 , 214 ipv6IfIcmpInGroupMembResponses 215 Counter32 , 216 ipv6IfIcmpInGroupMembReductions 217 Counter32 , 218 ipv6IfIcmpOutMsgs 219 Counter32 , 220 ipv6IfIcmpOutErrors 221 Counter32 , 222 ipv6IfIcmpOutDestUnreachs 223 Counter32 , 224 ipv6IfIcmpOutAdminProhibs 225 Counter32 , 226 ipv6IfIcmpOutTimeExcds 227 Counter32 , 228 ipv6IfIcmpOutParmProblems 229 Counter32 , 230 ipv6IfIcmpOutPktTooBigs 231 Counter32 , 232 ipv6IfIcmpOutEchos 233 Counter32 , 234 ipv6IfIcmpOutEchoReplies 235 Counter32 , 236 ipv6IfIcmpOutRouterSolicits 237 Counter32 , 238 ipv6IfIcmpOutRouterAdvertisements 239 Counter32 , 240 ipv6IfIcmpOutNeighborSolicits 241 Counter32 , 242 ipv6IfIcmpOutNeighborAdvertisements 243 Counter32 , 244 ipv6IfIcmpOutRedirects 245 Counter32 , 246 ipv6IfIcmpOutGroupMembQueries 247 Counter32 , 248 ipv6IfIcmpOutGroupMembResponses 249 Counter32 , 250 ipv6IfIcmpOutGroupMembReductions 251 Counter32 252 } 254 ipv6IfIcmpInMsgs OBJECT-TYPE 255 SYNTAX Counter32 256 MAX-ACCESS read-only 257 STATUS current 258 DESCRIPTION 259 "The total number of ICMP messages received 260 by the interface which includes all those 261 counted by ipv6IfIcmpInErrors. Note that this 262 interface is the interface to which the 263 ICMP messages were addressed which may not be 264 necessarily the input interface for the messages." 265 ::= { ipv6IfIcmpEntry 1 } 267 ipv6IfIcmpInErrors OBJECT-TYPE 268 SYNTAX Counter32 269 MAX-ACCESS read-only 270 STATUS current 271 DESCRIPTION 272 "The number of ICMP messages which the interface 273 received but determined as having ICMP-specific 274 errors (bad ICMP checksums, bad length, etc.)." 275 ::= { ipv6IfIcmpEntry 2 } 277 ipv6IfIcmpInDestUnreachs OBJECT-TYPE 278 SYNTAX Counter32 279 MAX-ACCESS read-only 280 STATUS current 281 DESCRIPTION 282 "The number of ICMP Destination Unreachable 283 messages received by the interface." 284 ::= { ipv6IfIcmpEntry 3 } 286 ipv6IfIcmpInAdminProhibs OBJECT-TYPE 287 SYNTAX Counter32 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "The number of ICMP dest unreachable/communication 292 administratively prohibited messages received 293 by the interface." 294 ::= { ipv6IfIcmpEntry 4 } 296 ipv6IfIcmpInTimeExcds OBJECT-TYPE 297 SYNTAX Counter32 298 MAX-ACCESS read-only 299 STATUS current 300 DESCRIPTION 301 "The number of ICMP Time Exceeded messages 302 received by the interface." 303 ::= { ipv6IfIcmpEntry 5 } 305 ipv6IfIcmpInParmProblems OBJECT-TYPE 306 SYNTAX Counter32 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "The number of ICMP Parameter Problem messages 311 received by the interface." 312 ::= { ipv6IfIcmpEntry 6 } 314 ipv6IfIcmpInPktTooBigs OBJECT-TYPE 315 SYNTAX Counter32 316 MAX-ACCESS read-only 317 STATUS current 318 DESCRIPTION 319 "The number of ICMP Packet Too Big messages 320 received by the interface." 321 ::= { ipv6IfIcmpEntry 7 } 323 ipv6IfIcmpInEchos OBJECT-TYPE 324 SYNTAX Counter32 325 MAX-ACCESS read-only 326 STATUS current 327 DESCRIPTION 328 "The number of ICMP Echo (request) messages 329 received by the interface." 330 ::= { ipv6IfIcmpEntry 8 } 332 ipv6IfIcmpInEchoReps OBJECT-TYPE 333 SYNTAX Counter32 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The number of ICMP Echo Reply messages received 338 by the interface." 339 ::= { ipv6IfIcmpEntry 9 } 341 ipv6IfIcmpInRouterSolicits OBJECT-TYPE 342 SYNTAX Counter32 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The number of ICMP Router Solicit messages 347 received by the interface." 348 ::= { ipv6IfIcmpEntry 10 } 350 ipv6IfIcmpInRouterAdvertisements OBJECT-TYPE 351 SYNTAX Counter32 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The number of ICMP Router Advertisement messages 356 received by the interface." 357 ::= { ipv6IfIcmpEntry 11 } 359 ipv6IfIcmpInNeighborSolicits OBJECT-TYPE 360 SYNTAX Counter32 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The number of ICMP Neighbor Solicit messages 365 received by the interface." 366 ::= { ipv6IfIcmpEntry 12 } 368 ipv6IfIcmpInNeighborAdvertisements OBJECT-TYPE 369 SYNTAX Counter32 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The number of ICMP Neighbor Advertisement 374 messages received by the interface." 375 ::= { ipv6IfIcmpEntry 13 } 377 ipv6IfIcmpInRedirects OBJECT-TYPE 378 SYNTAX Counter32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The number of Redirect messages received 383 by the interface." 384 ::= { ipv6IfIcmpEntry 14 } 386 ipv6IfIcmpInGroupMembQueries OBJECT-TYPE 387 SYNTAX Counter32 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The number of ICMPv6 Group Membership Query 392 messages received by the interface." 393 ::= { ipv6IfIcmpEntry 15} 395 ipv6IfIcmpInGroupMembResponses OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The number of ICMPv6 Group Membership Response messages 401 received by the interface." 402 ::= { ipv6IfIcmpEntry 16} 404 ipv6IfIcmpInGroupMembReductions OBJECT-TYPE 405 SYNTAX Counter32 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "The number of ICMPv6 Group Membership Reduction messages 410 received by the interface." 411 ::= { ipv6IfIcmpEntry 17} 413 ipv6IfIcmpOutMsgs OBJECT-TYPE 414 SYNTAX Counter32 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "The total number of ICMP messages which this 419 interface attempted to send. Note that this counter 420 includes all those counted by icmpOutErrors." 421 ::= { ipv6IfIcmpEntry 18 } 423 ipv6IfIcmpOutErrors OBJECT-TYPE 424 SYNTAX Counter32 425 MAX-ACCESS read-only 426 STATUS current 427 DESCRIPTION 428 "The number of ICMP messages which this interface did 429 not send due to problems discovered within ICMP 430 such as a lack of buffers. This value should not 431 include errors discovered outside the ICMP layer 432 such as the inability of IPv6 to route the resultant 433 datagram. In some implementations there may be no 434 types of error which contribute to this counter's 435 value." 436 ::= { ipv6IfIcmpEntry 19 } 438 ipv6IfIcmpOutDestUnreachs OBJECT-TYPE 439 SYNTAX Counter32 440 MAX-ACCESS read-only 441 STATUS current 442 DESCRIPTION 443 "The number of ICMP Destination Unreachable 444 messages sent by the interface." 445 ::= { ipv6IfIcmpEntry 20 } 447 ipv6IfIcmpOutAdminProhibs OBJECT-TYPE 448 SYNTAX Counter32 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "Number of ICMP dest unreachable/communication 453 administratively prohibited messages sent." 454 ::= { ipv6IfIcmpEntry 21 } 456 ipv6IfIcmpOutTimeExcds OBJECT-TYPE 457 SYNTAX Counter32 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "The number of ICMP Time Exceeded messages sent 462 by the interface." 463 ::= { ipv6IfIcmpEntry 22 } 465 ipv6IfIcmpOutParmProblems OBJECT-TYPE 466 SYNTAX Counter32 467 MAX-ACCESS read-only 468 STATUS current 469 DESCRIPTION 470 "The number of ICMP Parameter Problem messages 471 sent by the interface." 472 ::= { ipv6IfIcmpEntry 23 } 474 ipv6IfIcmpOutPktTooBigs OBJECT-TYPE 475 SYNTAX Counter32 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The number of ICMP Packet Too Big messages sent 480 by the interface." 481 ::= { ipv6IfIcmpEntry 24 } 483 ipv6IfIcmpOutEchos OBJECT-TYPE 484 SYNTAX Counter32 485 MAX-ACCESS read-only 486 STATUS current 487 DESCRIPTION 488 "The number of ICMP Echo (request) messages sent 489 by the interface." 490 ::= { ipv6IfIcmpEntry 25 } 492 ipv6IfIcmpOutEchoReplies OBJECT-TYPE 493 SYNTAX Counter32 494 MAX-ACCESS read-only 495 STATUS current 496 DESCRIPTION 497 "The number of ICMP Echo Reply messages sent 498 by the interface." 499 ::= { ipv6IfIcmpEntry 26 } 501 ipv6IfIcmpOutRouterSolicits OBJECT-TYPE 502 SYNTAX Counter32 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The number of ICMP Router Solicitation messages 507 sent by the interface." 508 ::= { ipv6IfIcmpEntry 27 } 510 ipv6IfIcmpOutRouterAdvertisements OBJECT-TYPE 511 SYNTAX Counter32 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The number of ICMP Router Advertisement messages 516 sent by the interface." 517 ::= { ipv6IfIcmpEntry 28 } 519 ipv6IfIcmpOutNeighborSolicits OBJECT-TYPE 520 SYNTAX Counter32 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The number of ICMP Neighbor Solicitation 525 messages sent by the interface." 526 ::= { ipv6IfIcmpEntry 29 } 528 ipv6IfIcmpOutNeighborAdvertisements OBJECT-TYPE 529 SYNTAX Counter32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "The number of ICMP Neighbor Advertisement 534 messages sent by the interface." 535 ::= { ipv6IfIcmpEntry 30 } 537 ipv6IfIcmpOutRedirects OBJECT-TYPE 538 SYNTAX Counter32 539 MAX-ACCESS read-only 540 STATUS current 541 DESCRIPTION 542 "The number of Redirect messages sent. For 543 a host, this object will always be zero, 544 since hosts do not send redirects." 545 ::= { ipv6IfIcmpEntry 31 } 547 ipv6IfIcmpOutGroupMembQueries OBJECT-TYPE 548 SYNTAX Counter32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "The number of ICMPv6 Group Membership Query 553 messages sent" 554 ::= { ipv6IfIcmpEntry 32} 556 ipv6IfIcmpOutGroupMembResponses OBJECT-TYPE 557 SYNTAX Counter32 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "The number of ICMPv6 Group Membership Response 562 messages sent" 563 ::= { ipv6IfIcmpEntry 33} 565 ipv6IfIcmpOutGroupMembReductions OBJECT-TYPE 566 SYNTAX Counter32 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "The number of ICMPv6 Group Membership Reduction 571 messages sent" 572 ::= { ipv6IfIcmpEntry 34} 574 -- conformance information 576 ipv6IcmpConformance OBJECT IDENTIFIER ::= { ipv6IcmpMIB 2 } 578 ipv6IcmpCompliances 579 OBJECT IDENTIFIER ::= { ipv6IcmpConformance 1 } 580 ipv6IcmpGroups 581 OBJECT IDENTIFIER ::= { ipv6IcmpConformance 2 } 583 -- compliance statements 585 ipv6IcmpCompliance MODULE-COMPLIANCE 586 STATUS current 587 DESCRIPTION 588 "The compliance statement for SNMPv2 entities which 589 implement ICMPv6." 590 MODULE -- this module 591 MANDATORY-GROUPS { ipv6IcmpGroup } 592 ::= { ipv6IcmpCompliances 1 } 594 ipv6IcmpGroup OBJECT-GROUP 595 OBJECTS { 596 ipv6IfIcmpInMsgs, 597 ipv6IfIcmpInErrors, 598 ipv6IfIcmpInDestUnreachs, 599 ipv6IfIcmpInAdminProhibs, 600 ipv6IfIcmpInTimeExcds, 601 ipv6IfIcmpInParmProblems, 602 ipv6IfIcmpInPktTooBigs, 603 ipv6IfIcmpInEchos, 604 ipv6IfIcmpInEchoReps , 605 ipv6IfIcmpInRouterSolicits, 606 ipv6IfIcmpInRouterAdvertisements, 607 ipv6IfIcmpInNeighborSolicits, 608 ipv6IfIcmpInNeighborAdvertisements, 609 ipv6IfIcmpInRedirects, 610 ipv6IfIcmpInGroupMembQueries, 611 ipv6IfIcmpInGroupMembResponses, 612 ipv6IfIcmpInGroupMembReductions, 613 ipv6IfIcmpOutMsgs, 614 ipv6IfIcmpOutErrors, 615 ipv6IfIcmpOutDestUnreachs, 616 ipv6IfIcmpOutAdminProhibs, 617 ipv6IfIcmpOutTimeExcds, 618 ipv6IfIcmpOutParmProblems, 619 ipv6IfIcmpOutPktTooBigs, 620 ipv6IfIcmpOutEchos, 621 ipv6IfIcmpOutEchoReplies, 622 ipv6IfIcmpOutRouterSolicits, 623 ipv6IfIcmpOutRouterAdvertisements, 624 ipv6IfIcmpOutNeighborSolicits, 625 ipv6IfIcmpOutNeighborAdvertisements, 626 ipv6IfIcmpOutRedirects, 627 ipv6IfIcmpOutGroupMembQueries, 628 ipv6IfIcmpOutGroupMembResponses, 629 ipv6IfIcmpOutGroupMembReductions 630 } 631 STATUS current 632 DESCRIPTION 633 "The ICMPv6 group of objects providing information 634 specific to ICMPv6." 635 ::= { ipv6IcmpGroups 1 } 637 END 639 4. Acknowledgements 641 This document borrows from MIB works produced by IETF for 642 IPv4-based internets. 644 We would like to thanks the following people for constructive 645 and valuable comments: 646 Mike Daniele, 647 Margaret Forsythe, 648 Jean-Pierre Roch, 649 Vivek Venkatraman. 651 5. References 653 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 654 and S. Waldbusser, "Structure of Management Information 655 for Version 2 of the Simple Network Management Protocol 656 (SNMPv2)", RFC 1902, January 1996. 658 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 659 and S. Waldbusser, "Textual Conventions for Version 2 of 660 the Simple Network Management Protocol (SNMPv2)", RFC 661 1903, January 1996. 663 [3] McCloghrie, K., and M. Rose, Editors, "Management 664 Information Base for Network Management of TCP/IP-based 665 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 666 Performance Systems International, March 1991. 668 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A 669 Simple Network Management Protocol (SNMP)", STD 15, RFC 670 1157, SNMP Research, Performance Systems International, 671 MIT Lab for Computer Science, May 1990. 673 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. 674 and S. Waldbusser, "Protocol Operations for Version 2 of 675 the Simple Network Management Protocol (SNMPv2)", RFC 676 1905, January 1996. 678 [6] McCloghrie, K. and F. Kastenholz, "Evolution of the 679 Interfaces Group of MIB-II" , RFC 1573, January 1994. 681 [7] Deering, S., and R. Hinden, "Internet Protocol, Version 6 682 (IPv6) Specification", RFC 1883, December 1995. 684 [8] Haskin, D., and S. Onishi, "Management Information Base 685 for IP Version 6: Textual Conventions and General Group", 686 Work in progress. 688 6. Security Considerations 690 Certain management information defined in this MIB may be 691 considered sensitive in some network environments. 693 Therefore, authentication of received SNMP requests and 694 controlled access to management information should be employed 695 in such environments. 697 7. Authors' Address 699 Dimitry Haskin 700 Bay Networks, Inc. 701 2 Federal Street 702 Billerica, MA 01821 703 email: dhaskin@baynetworks.com 705 Steve Onishi 706 Bay Networks, Inc. 707 3 Federal Street 708 Billerica, MA 01821 709 email: sonishi@baynetworks.com