idnits 2.17.1 draft-ietf-ipngwg-ipv6-icmp-mib-01.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-25) 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 (March 1997) is 9903 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 657, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 677, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 680, 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 March 1997 4 Management Information Base for IP Version 6: 5 ICMPv6 Group 7 9 Mon Mar 24 09:46:35 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. Acknowledgments .................................... 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 type is named by an OBJECT IDENTIFIER, an administratively 90 assigned name. The object type together with an object 91 instance serves to uniquely identify a specific instantiation 92 of the object. For human convenience, we often use a textual 93 string, termed the descriptor, to refer to the object type. 95 2. Overview 97 This document is the one in the series of documents that 98 define various MIB object groups for IPv6. These groups are 99 the basic unit of conformance: if the semantics of a group is 100 applicable to an implementation, then it must implement all 101 objects in that group. For example, an implementation must 102 implement the TCP group if and only if it implements the TCP 103 over IPv6 protocol. At minimum, implementations must 104 implement the IPv6 General group [8] as well as the ICMPv6 105 group defined in this document. 107 This document defines the ICMPv6 group of the IPv6 MIB. 109 3. The ICMPv6 Group 111 IPV6-ICMP-MIB DEFINITIONS ::= BEGIN 113 IMPORTS 114 MODULE-IDENTITY, OBJECT-TYPE, 115 Counter32 FROM SNMPv2-SMI 116 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 117 ipv6 FROM IPV6-TC --- [8] 118 ipv6IfEntry FROM IPV6-MIB; --- [8] 120 ipv6IcmpMIB MODULE-IDENTITY 121 LAST-UPDATED "9703212155Z" 122 ORGANIZATION "IETF IPv6 MIB Working Group" 123 CONTACT-INFO 124 " Dimitry Haskin 126 Postal: Bay Networks, Inc. 127 2 Federal St. 128 Billerica, MA 01821 129 US 131 Tel: +1-508-916-8124 132 E-mail: dhaskin@baynetworks.com 134 Steve Onishi 136 Postal: Bay Networks, Inc. 137 3 Federal Street 138 Billerica, MA 01821 139 US 141 Tel: +1-508-916-3816 142 E-mail: sonishi@baynetworks.com" 143 DESCRIPTION 144 "The MIB module for entities implementing 145 the ICMPv6." 146 ::= { ipv6 2 } 148 -- the ICMPv6 group 150 ipv6IcmpMIBObjects OBJECT IDENTIFIER ::= { ipv6IcmpMIB 1 } 151 -- Per-interface ICMPv6 statistics table 153 ipv6IfIcmpTable OBJECT-TYPE 154 SYNTAX SEQUENCE OF Ipv6IfIcmpEntry 155 MAX-ACCESS not-accessible 156 STATUS current 157 DESCRIPTION 158 "IPv6 ICMP statistics" 159 ::= { ipv6IcmpMIBObjects 1 } 161 ipv6IfIcmpEntry OBJECT-TYPE 162 SYNTAX Ipv6IfIcmpEntry 163 MAX-ACCESS not-accessible 164 STATUS current 165 DESCRIPTION 166 "An ICMPv6 statistics entry containing 167 objects at a particular IPv6 interface. 169 Note that a receiving interface is 170 the interface to which a given ICMPv6 message 171 is addressed which may not be necessarily 172 the input interface for the message. 174 Similarly, the sending interface is 175 the interface that sources a given 176 ICMP message which is usually but not 177 necessarily the output interface for the message." 178 AUGMENTS { ipv6IfEntry } 179 ::= { ipv6IfIcmpTable 1 } 181 Ipv6IfIcmpEntry ::= SEQUENCE { 182 ipv6IfIcmpInMsgs 183 Counter32 , 184 ipv6IfIcmpInErrors 185 Counter32 , 186 ipv6IfIcmpInDestUnreachs 187 Counter32 , 188 ipv6IfIcmpInAdminProhibs 189 Counter32 , 190 ipv6IfIcmpInTimeExcds 191 Counter32 , 192 ipv6IfIcmpInParmProblems 193 Counter32 , 194 ipv6IfIcmpInPktTooBigs 195 Counter32 , 197 ipv6IfIcmpInEchos 198 Counter32 , 199 ipv6IfIcmpInEchoReps 200 Counter32 , 201 ipv6IfIcmpInRouterSolicits 202 Counter32 , 203 ipv6IfIcmpInRouterAdvertisements 204 Counter32 , 205 ipv6IfIcmpInNeighborSolicits 206 Counter32 , 207 ipv6IfIcmpInNeighborAdvertisements 208 Counter32 , 209 ipv6IfIcmpInRedirects 210 Counter32 , 211 ipv6IfIcmpInGroupMembQueries 212 Counter32 , 213 ipv6IfIcmpInGroupMembResponses 214 Counter32 , 215 ipv6IfIcmpInGroupMembReductions 216 Counter32 , 217 ipv6IfIcmpOutMsgs 218 Counter32 , 219 ipv6IfIcmpOutErrors 220 Counter32 , 221 ipv6IfIcmpOutDestUnreachs 222 Counter32 , 223 ipv6IfIcmpOutAdminProhibs 224 Counter32 , 225 ipv6IfIcmpOutTimeExcds 226 Counter32 , 227 ipv6IfIcmpOutParmProblems 228 Counter32 , 229 ipv6IfIcmpOutPktTooBigs 230 Counter32 , 231 ipv6IfIcmpOutEchos 232 Counter32 , 233 ipv6IfIcmpOutEchoReplies 234 Counter32 , 235 ipv6IfIcmpOutRouterSolicits 236 Counter32 , 237 ipv6IfIcmpOutRouterAdvertisements 238 Counter32 , 239 ipv6IfIcmpOutNeighborSolicits 240 Counter32 , 241 ipv6IfIcmpOutNeighborAdvertisements 242 Counter32 , 243 ipv6IfIcmpOutRedirects 244 Counter32 , 245 ipv6IfIcmpOutGroupMembQueries 246 Counter32 , 247 ipv6IfIcmpOutGroupMembResponses 248 Counter32 , 249 ipv6IfIcmpOutGroupMembReductions 250 Counter32 251 } 253 ipv6IfIcmpInMsgs OBJECT-TYPE 254 SYNTAX Counter32 255 MAX-ACCESS read-only 256 STATUS current 257 DESCRIPTION 258 "The total number of ICMP messages received 259 by the interface which includes all those 260 counted by ipv6IfIcmpInErrors. Note that this 261 interface is the interface to which the 262 ICMP messages were addressed which may not be 263 necessarily the input interface for the messages." 264 ::= { ipv6IfIcmpEntry 1 } 266 ipv6IfIcmpInErrors OBJECT-TYPE 267 SYNTAX Counter32 268 MAX-ACCESS read-only 269 STATUS current 270 DESCRIPTION 271 "The number of ICMP messages which the interface 272 received but determined as having ICMP-specific 273 errors (bad ICMP checksums, bad length, etc.)." 274 ::= { ipv6IfIcmpEntry 2 } 276 ipv6IfIcmpInDestUnreachs OBJECT-TYPE 277 SYNTAX Counter32 278 MAX-ACCESS read-only 279 STATUS current 280 DESCRIPTION 281 "The number of ICMP Destination Unreachable 282 messages received by the interface." 283 ::= { ipv6IfIcmpEntry 3 } 285 ipv6IfIcmpInAdminProhibs OBJECT-TYPE 286 SYNTAX Counter32 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The number of ICMP destination 291 unreachable/communication administratively 292 prohibited messages received by the interface." 293 ::= { ipv6IfIcmpEntry 4 } 295 ipv6IfIcmpInTimeExcds OBJECT-TYPE 296 SYNTAX Counter32 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The number of ICMP Time Exceeded messages 301 received by the interface." 302 ::= { ipv6IfIcmpEntry 5 } 304 ipv6IfIcmpInParmProblems OBJECT-TYPE 305 SYNTAX Counter32 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The number of ICMP Parameter Problem messages 310 received by the interface." 311 ::= { ipv6IfIcmpEntry 6 } 313 ipv6IfIcmpInPktTooBigs OBJECT-TYPE 314 SYNTAX Counter32 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The number of ICMP Packet Too Big messages 319 received by the interface." 320 ::= { ipv6IfIcmpEntry 7 } 322 ipv6IfIcmpInEchos OBJECT-TYPE 323 SYNTAX Counter32 324 MAX-ACCESS read-only 325 STATUS current 326 DESCRIPTION 327 "The number of ICMP Echo (request) messages 328 received by the interface." 329 ::= { ipv6IfIcmpEntry 8 } 331 ipv6IfIcmpInEchoReps OBJECT-TYPE 332 SYNTAX Counter32 333 MAX-ACCESS read-only 334 STATUS current 335 DESCRIPTION 336 "The number of ICMP Echo Reply messages received 337 by the interface." 338 ::= { ipv6IfIcmpEntry 9 } 340 ipv6IfIcmpInRouterSolicits OBJECT-TYPE 341 SYNTAX Counter32 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The number of ICMP Router Solicit messages 346 received by the interface." 347 ::= { ipv6IfIcmpEntry 10 } 349 ipv6IfIcmpInRouterAdvertisements OBJECT-TYPE 350 SYNTAX Counter32 351 MAX-ACCESS read-only 352 STATUS current 353 DESCRIPTION 354 "The number of ICMP Router Advertisement messages 355 received by the interface." 356 ::= { ipv6IfIcmpEntry 11 } 358 ipv6IfIcmpInNeighborSolicits OBJECT-TYPE 359 SYNTAX Counter32 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The number of ICMP Neighbor Solicit messages 364 received by the interface." 365 ::= { ipv6IfIcmpEntry 12 } 367 ipv6IfIcmpInNeighborAdvertisements OBJECT-TYPE 368 SYNTAX Counter32 369 MAX-ACCESS read-only 370 STATUS current 371 DESCRIPTION 372 "The number of ICMP Neighbor Advertisement 373 messages received by the interface." 374 ::= { ipv6IfIcmpEntry 13 } 376 ipv6IfIcmpInRedirects OBJECT-TYPE 377 SYNTAX Counter32 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "The number of Redirect messages received 382 by the interface." 383 ::= { ipv6IfIcmpEntry 14 } 385 ipv6IfIcmpInGroupMembQueries OBJECT-TYPE 386 SYNTAX Counter32 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The number of ICMPv6 Group Membership Query 391 messages received by the interface." 392 ::= { ipv6IfIcmpEntry 15} 394 ipv6IfIcmpInGroupMembResponses OBJECT-TYPE 395 SYNTAX Counter32 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "The number of ICMPv6 Group Membership Response messages 400 received by the interface." 401 ::= { ipv6IfIcmpEntry 16} 403 ipv6IfIcmpInGroupMembReductions OBJECT-TYPE 404 SYNTAX Counter32 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The number of ICMPv6 Group Membership Reduction messages 409 received by the interface." 410 ::= { ipv6IfIcmpEntry 17} 412 ipv6IfIcmpOutMsgs OBJECT-TYPE 413 SYNTAX Counter32 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The total number of ICMP messages which this 418 interface attempted to send. Note that this counter 419 includes all those counted by icmpOutErrors." 420 ::= { ipv6IfIcmpEntry 18 } 422 ipv6IfIcmpOutErrors OBJECT-TYPE 423 SYNTAX Counter32 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The number of ICMP messages which this interface did 428 not send due to problems discovered within ICMP 429 such as a lack of buffers. This value should not 430 include errors discovered outside the ICMP layer 431 such as the inability of IPv6 to route the resultant 432 datagram. In some implementations there may be no 433 types of error which contribute to this counter's 434 value." 435 ::= { ipv6IfIcmpEntry 19 } 437 ipv6IfIcmpOutDestUnreachs OBJECT-TYPE 438 SYNTAX Counter32 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "The number of ICMP Destination Unreachable 443 messages sent by the interface." 444 ::= { ipv6IfIcmpEntry 20 } 446 ipv6IfIcmpOutAdminProhibs OBJECT-TYPE 447 SYNTAX Counter32 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "Number of ICMP dest unreachable/communication 452 administratively prohibited messages sent." 453 ::= { ipv6IfIcmpEntry 21 } 455 ipv6IfIcmpOutTimeExcds OBJECT-TYPE 456 SYNTAX Counter32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The number of ICMP Time Exceeded messages sent 461 by the interface." 462 ::= { ipv6IfIcmpEntry 22 } 464 ipv6IfIcmpOutParmProblems OBJECT-TYPE 465 SYNTAX Counter32 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The number of ICMP Parameter Problem messages 470 sent by the interface." 471 ::= { ipv6IfIcmpEntry 23 } 473 ipv6IfIcmpOutPktTooBigs OBJECT-TYPE 474 SYNTAX Counter32 475 MAX-ACCESS read-only 476 STATUS current 477 DESCRIPTION 478 "The number of ICMP Packet Too Big messages sent 479 by the interface." 480 ::= { ipv6IfIcmpEntry 24 } 482 ipv6IfIcmpOutEchos OBJECT-TYPE 483 SYNTAX Counter32 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "The number of ICMP Echo (request) messages sent 488 by the interface." 489 ::= { ipv6IfIcmpEntry 25 } 491 ipv6IfIcmpOutEchoReplies OBJECT-TYPE 492 SYNTAX Counter32 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "The number of ICMP Echo Reply messages sent 497 by the interface." 498 ::= { ipv6IfIcmpEntry 26 } 500 ipv6IfIcmpOutRouterSolicits OBJECT-TYPE 501 SYNTAX Counter32 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "The number of ICMP Router Solicitation messages 506 sent by the interface." 507 ::= { ipv6IfIcmpEntry 27 } 509 ipv6IfIcmpOutRouterAdvertisements OBJECT-TYPE 510 SYNTAX Counter32 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "The number of ICMP Router Advertisement messages 515 sent by the interface." 516 ::= { ipv6IfIcmpEntry 28 } 518 ipv6IfIcmpOutNeighborSolicits OBJECT-TYPE 519 SYNTAX Counter32 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "The number of ICMP Neighbor Solicitation 524 messages sent by the interface." 525 ::= { ipv6IfIcmpEntry 29 } 527 ipv6IfIcmpOutNeighborAdvertisements OBJECT-TYPE 528 SYNTAX Counter32 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "The number of ICMP Neighbor Advertisement 533 messages sent by the interface." 534 ::= { ipv6IfIcmpEntry 30 } 536 ipv6IfIcmpOutRedirects OBJECT-TYPE 537 SYNTAX Counter32 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The number of Redirect messages sent. For 542 a host, this object will always be zero, 543 since hosts do not send redirects." 544 ::= { ipv6IfIcmpEntry 31 } 546 ipv6IfIcmpOutGroupMembQueries OBJECT-TYPE 547 SYNTAX Counter32 548 MAX-ACCESS read-only 549 STATUS current 550 DESCRIPTION 551 "The number of ICMPv6 Group Membership Query 552 messages sent" 553 ::= { ipv6IfIcmpEntry 32} 555 ipv6IfIcmpOutGroupMembResponses OBJECT-TYPE 556 SYNTAX Counter32 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The number of ICMPv6 Group Membership Response 561 messages sent" 562 ::= { ipv6IfIcmpEntry 33} 564 ipv6IfIcmpOutGroupMembReductions OBJECT-TYPE 565 SYNTAX Counter32 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "The number of ICMPv6 Group Membership Reduction 570 messages sent" 571 ::= { ipv6IfIcmpEntry 34} 573 -- conformance information 575 ipv6IcmpConformance OBJECT IDENTIFIER ::= { ipv6IcmpMIB 2 } 577 ipv6IcmpCompliances 578 OBJECT IDENTIFIER ::= { ipv6IcmpConformance 1 } 579 ipv6IcmpGroups 580 OBJECT IDENTIFIER ::= { ipv6IcmpConformance 2 } 582 -- compliance statements 584 ipv6IcmpCompliance MODULE-COMPLIANCE 585 STATUS current 586 DESCRIPTION 587 "The compliance statement for SNMPv2 entities which 588 implement ICMPv6." 589 MODULE -- this module 590 MANDATORY-GROUPS { ipv6IcmpGroup } 591 ::= { ipv6IcmpCompliances 1 } 593 ipv6IcmpGroup OBJECT-GROUP 594 OBJECTS { 595 ipv6IfIcmpInMsgs, 596 ipv6IfIcmpInErrors, 597 ipv6IfIcmpInDestUnreachs, 598 ipv6IfIcmpInAdminProhibs, 599 ipv6IfIcmpInTimeExcds, 600 ipv6IfIcmpInParmProblems, 601 ipv6IfIcmpInPktTooBigs, 602 ipv6IfIcmpInEchos, 603 ipv6IfIcmpInEchoReps , 604 ipv6IfIcmpInRouterSolicits, 605 ipv6IfIcmpInRouterAdvertisements, 606 ipv6IfIcmpInNeighborSolicits, 607 ipv6IfIcmpInNeighborAdvertisements, 608 ipv6IfIcmpInRedirects, 609 ipv6IfIcmpInGroupMembQueries, 610 ipv6IfIcmpInGroupMembResponses, 611 ipv6IfIcmpInGroupMembReductions, 612 ipv6IfIcmpOutMsgs, 613 ipv6IfIcmpOutErrors, 614 ipv6IfIcmpOutDestUnreachs, 615 ipv6IfIcmpOutAdminProhibs, 616 ipv6IfIcmpOutTimeExcds, 617 ipv6IfIcmpOutParmProblems, 618 ipv6IfIcmpOutPktTooBigs, 619 ipv6IfIcmpOutEchos, 620 ipv6IfIcmpOutEchoReplies, 621 ipv6IfIcmpOutRouterSolicits, 622 ipv6IfIcmpOutRouterAdvertisements, 623 ipv6IfIcmpOutNeighborSolicits, 624 ipv6IfIcmpOutNeighborAdvertisements, 625 ipv6IfIcmpOutRedirects, 626 ipv6IfIcmpOutGroupMembQueries, 627 ipv6IfIcmpOutGroupMembResponses, 628 ipv6IfIcmpOutGroupMembReductions 629 } 630 STATUS current 631 DESCRIPTION 632 "The ICMPv6 group of objects providing information 633 specific to ICMPv6." 634 ::= { ipv6IcmpGroups 1 } 636 END 638 4. Acknowledgments 640 This document borrows from MIB works produced by IETF for 641 IPv4-based internets. 643 We would like to thanks the following people for constructive 644 and valuable comments: 645 Mike Daniele, 646 Margaret Forsythe, 647 Jean-Pierre Roch, 648 Vivek Venkatraman. 650 5. References 652 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 653 and S. Waldbusser, "Structure of Management Information 654 for Version 2 of the Simple Network Management Protocol 655 (SNMPv2)", RFC 1902, January 1996. 657 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 658 and S. Waldbusser, "Textual Conventions for Version 2 of 659 the Simple Network Management Protocol (SNMPv2)", RFC 660 1903, January 1996. 662 [3] McCloghrie, K., and M. Rose, Editors, "Management 663 Information Base for Network Management of TCP/IP-based 664 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 665 Performance Systems International, March 1991. 667 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A 668 Simple Network Management Protocol (SNMP)", STD 15, RFC 669 1157, SNMP Research, Performance Systems International, 670 MIT Lab for Computer Science, May 1990. 672 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. 673 and S. Waldbusser, "Protocol Operations for Version 2 of 674 the Simple Network Management Protocol (SNMPv2)", RFC 675 1905, January 1996. 677 [6] McCloghrie, K. and F. Kastenholz, "Evolution of the 678 Interfaces Group of MIB-II" , RFC 1573, January 1994. 680 [7] Deering, S., and R. Hinden, "Internet Protocol, Version 6 681 (IPv6) Specification", RFC 1883, December 1995. 683 [8] Haskin, D., and S. Onishi, "Management Information Base 684 for IP Version 6: Textual Conventions and General Group", 685 Work in progress. 687 6. Security Considerations 689 Certain management information defined in this MIB may be 690 considered sensitive in some network environments. 692 Therefore, authentication of received SNMP requests and 693 controlled access to management information should be employed 694 in such environments. 696 7. Authors' Address 698 Dimitry Haskin 699 Bay Networks, Inc. 700 2 Federal Street 701 Billerica, MA 01821 702 email: dhaskin@baynetworks.com 704 Steve Onishi 705 Bay Networks, Inc. 706 3 Federal Street 707 Billerica, MA 01821 708 email: sonishi@baynetworks.com