As per Relevance of the word standards, we have this rfc below:
Network Working Group D.
Request for Comments: 2466 S.
Category: Standards Track Bay Networks, Inc
December 1998
Management Information Base for IP Version 6:
ICMPv6
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This document is one in the series of documents that define
MIB object groups for IPv6. Specifically, the ICMPv6 group
defined in this document
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the IPv6-
internets
This document specifies a MIB module in a manner that is
compliant to the SNMPv2 SMI, and semantically identical to the
SNMPv1 definitions
Table of
1. The SNMPv2 Network Management Framework ............. 2
1.1 Object Definitions ................................ 2
2. Overview ............................................ 2
3. The ICMPv6 Group .................................... 3
4. Acknowledgments .................................... 14
5. References .......................................... 14
6. Security Considerations ............................. 15
7. Authors' Addresses................................... 15
8. Full Copyright Statement............................. 16
Haskin & Onishi Standards Track [Page 1]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
1. The SNMPv2 Network Management
The SNMPv2 Network Management Framework presently consists of
major components. They are
o the SMI, described in RFC 1902 [1] - the mechanisms used
describing and naming objects for the purpose of management
o the MIB-II, described in RFC 1213/STD 17 [3] - the core set
managed objects for the Internet suite of protocols
o RFC 1157/STD 15 [4] and RFC 1905 [5] which define two versions of
protocol used for network access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
1.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The object
together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience, we
use a textual string, termed the descriptor, to refer to the
type
2.
This document is the one in the series of documents that
various MIB object groups for IPv6. These groups are the basic unit
conformance: if the semantics of a group is applicable to
implementation, then it must implement all objects in that group.
example, an implementation must implement the TCP group if and only
it implements the TCP over IPv6 protocol. At minimum,
must implement the IPv6 General group [9] as well as the ICMPv6
defined in this document
This document defines the ICMPv6 group of the IPv6 MIB
Haskin & Onishi Standards Track [Page 2]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
3. The ICMPv6
IPV6-ICMP-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE
Counter32, mib-2 FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-
ipv6IfEntry FROM IPV6-MIB
ipv6IcmpMIB MODULE-
LAST-UPDATED "9801082155Z
ORGANIZATION "IETF IPv6 Working Group
CONTACT-
" Dimitry
Postal: Bay Networks, Inc
660 Techology Park Drive
Billerica, MA 01821
Tel: +1-978-916-8124
E-mail: dhaskin@baynetworks.
Steve
Postal: Bay Networks, Inc
3 Federal
Billerica, MA 01821
Tel: +1-978-916-3816
E-mail: sonishi@baynetworks.com
"The MIB module for entities
the ICMPv6."
::= { mib-2 56 }
-- the ICMPv6
ipv6IcmpMIBObjects OBJECT IDENTIFIER ::= { ipv6IcmpMIB 1 }
-- Per-interface ICMPv6 statistics
ipv6IfIcmpTable OBJECT-
SYNTAX SEQUENCE OF Ipv6
MAX-ACCESS not-
Haskin & Onishi Standards Track [Page 3]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
STATUS
"IPv6 ICMP statistics. This table contains
of ICMPv6 messages that are received and sourced
the entity."
::= { ipv6IcmpMIBObjects 1 }
ipv6IfIcmpEntry OBJECT-
SYNTAX Ipv6
MAX-ACCESS not-
STATUS
"An ICMPv6 statistics entry
objects at a particular IPv6 interface
Note that a receiving interface
the interface to which a given ICMPv6
is addressed which may not be
the input interface for the message
Similarly, the sending interface
the interface that sources a
ICMP message which is usually but
necessarily the output interface for the message."
AUGMENTS { ipv6IfEntry }
::= { ipv6IfIcmpTable 1 }
Ipv6IfIcmpEntry ::= SEQUENCE {
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
Haskin & Onishi Standards Track [Page 4]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32 ,
ipv6
Counter32
Haskin & Onishi Standards Track [Page 5]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
}
ipv6IfIcmpInMsgs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of ICMP messages
by the interface which includes all
counted by ipv6IfIcmpInErrors. Note that
interface is the interface to which
ICMP messages were addressed which may not
necessarily the input interface for the messages."
::= { ipv6IfIcmpEntry 1 }
ipv6IfIcmpInErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP messages which the
received but determined as having ICMP-
errors (bad ICMP checksums, bad length, etc.)."
::= { ipv6IfIcmpEntry 2 }
ipv6IfIcmpInDestUnreachs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Destination
messages received by the interface."
::= { ipv6IfIcmpEntry 3 }
ipv6IfIcmpInAdminProhibs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP
unreachable/communication
prohibited messages received by the interface."
::= { ipv6IfIcmpEntry 4 }
ipv6IfIcmpInTimeExcds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Haskin & Onishi Standards Track [Page 6]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
"The number of ICMP Time Exceeded
received by the interface."
::= { ipv6IfIcmpEntry 5 }
ipv6IfIcmpInParmProblems OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Parameter Problem
received by the interface."
::= { ipv6IfIcmpEntry 6 }
ipv6IfIcmpInPktTooBigs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Packet Too Big
received by the interface."
::= { ipv6IfIcmpEntry 7 }
ipv6IfIcmpInEchos OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Echo (request)
received by the interface."
::= { ipv6IfIcmpEntry 8 }
ipv6IfIcmpInEchoReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Echo Reply messages
by the interface."
::= { ipv6IfIcmpEntry 9 }
ipv6IfIcmpInRouterSolicits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Router Solicit
received by the interface."
Haskin & Onishi Standards Track [Page 7]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
::= { ipv6IfIcmpEntry 10 }
ipv6IfIcmpInRouterAdvertisements OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Router Advertisement
received by the interface."
::= { ipv6IfIcmpEntry 11 }
ipv6IfIcmpInNeighborSolicits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Neighbor Solicit
received by the interface."
::= { ipv6IfIcmpEntry 12 }
ipv6IfIcmpInNeighborAdvertisements OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Neighbor
messages received by the interface."
::= { ipv6IfIcmpEntry 13 }
ipv6IfIcmpInRedirects OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Redirect messages
by the interface."
::= { ipv6IfIcmpEntry 14 }
ipv6IfIcmpInGroupMembQueries OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMPv6 Group Membership
messages received by the interface."
::= { ipv6IfIcmpEntry 15}
ipv6IfIcmpInGroupMembResponses OBJECT-
Haskin & Onishi Standards Track [Page 8]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMPv6 Group Membership Response
received by the interface."
::= { ipv6IfIcmpEntry 16}
ipv6IfIcmpInGroupMembReductions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMPv6 Group Membership Reduction
received by the interface."
::= { ipv6IfIcmpEntry 17}
ipv6IfIcmpOutMsgs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The total number of ICMP messages which
interface attempted to send. Note that this
includes all those counted by icmpOutErrors."
::= { ipv6IfIcmpEntry 18 }
ipv6IfIcmpOutErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP messages which this interface
not send due to problems discovered within
such as a lack of buffers. This value should
include errors discovered outside the ICMP
such as the inability of IPv6 to route the
datagram. In some implementations there may be
types of error which contribute to this counter'
value."
::= { ipv6IfIcmpEntry 19 }
ipv6IfIcmpOutDestUnreachs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Destination
Haskin & Onishi Standards Track [Page 9]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
messages sent by the interface."
::= { ipv6IfIcmpEntry 20 }
ipv6IfIcmpOutAdminProhibs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Number of ICMP dest unreachable/
administratively prohibited messages sent."
::= { ipv6IfIcmpEntry 21 }
ipv6IfIcmpOutTimeExcds OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Time Exceeded messages
by the interface."
::= { ipv6IfIcmpEntry 22 }
ipv6IfIcmpOutParmProblems OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Parameter Problem
sent by the interface."
::= { ipv6IfIcmpEntry 23 }
ipv6IfIcmpOutPktTooBigs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Packet Too Big messages
by the interface."
::= { ipv6IfIcmpEntry 24 }
ipv6IfIcmpOutEchos OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Echo (request) messages
by the interface."
::= { ipv6IfIcmpEntry 25 }
Haskin & Onishi Standards Track [Page 10]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
ipv6IfIcmpOutEchoReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Echo Reply messages
by the interface."
::= { ipv6IfIcmpEntry 26 }
ipv6IfIcmpOutRouterSolicits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Router Solicitation
sent by the interface."
::= { ipv6IfIcmpEntry 27 }
ipv6IfIcmpOutRouterAdvertisements OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Router Advertisement
sent by the interface."
::= { ipv6IfIcmpEntry 28 }
ipv6IfIcmpOutNeighborSolicits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Neighbor
messages sent by the interface."
::= { ipv6IfIcmpEntry 29 }
ipv6IfIcmpOutNeighborAdvertisements OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMP Neighbor
messages sent by the interface."
::= { ipv6IfIcmpEntry 30 }
ipv6IfIcmpOutRedirects OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
Haskin & Onishi Standards Track [Page 11]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
STATUS
"The number of Redirect messages sent.
a host, this object will always be zero
since hosts do not send redirects."
::= { ipv6IfIcmpEntry 31 }
ipv6IfIcmpOutGroupMembQueries OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMPv6 Group Membership
messages sent."
::= { ipv6IfIcmpEntry 32}
ipv6IfIcmpOutGroupMembResponses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMPv6 Group Membership
messages sent."
::= { ipv6IfIcmpEntry 33}
ipv6IfIcmpOutGroupMembReductions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of ICMPv6 Group Membership
messages sent."
::= { ipv6IfIcmpEntry 34}
-- conformance
ipv6IcmpConformance OBJECT IDENTIFIER ::= { ipv6IcmpMIB 2 }
ipv6
OBJECT IDENTIFIER ::= { ipv6IcmpConformance 1 }
ipv6
OBJECT IDENTIFIER ::= { ipv6IcmpConformance 2 }
-- compliance
ipv6IcmpCompliance MODULE-
STATUS
Haskin & Onishi Standards Track [Page 12]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
"The compliance statement for SNMPv2 entities
implement ICMPv6."
MODULE -- this
MANDATORY-GROUPS { ipv6IcmpGroup }
::= { ipv6IcmpCompliances 1 }
ipv6IcmpGroup OBJECT-
OBJECTS {
ipv6IfIcmpInMsgs
ipv6IfIcmpInErrors
ipv6IfIcmpInDestUnreachs
ipv6IfIcmpInAdminProhibs
ipv6IfIcmpInTimeExcds
ipv6IfIcmpInParmProblems
ipv6IfIcmpInPktTooBigs
ipv6IfIcmpInEchos
ipv6IfIcmpInEchoReplies
ipv6IfIcmpInRouterSolicits
ipv6IfIcmpInRouterAdvertisements
ipv6IfIcmpInNeighborSolicits
ipv6IfIcmpInNeighborAdvertisements
ipv6IfIcmpInRedirects
ipv6IfIcmpInGroupMembQueries
ipv6IfIcmpInGroupMembResponses
ipv6IfIcmpInGroupMembReductions
ipv6IfIcmpOutMsgs
ipv6IfIcmpOutErrors
ipv6IfIcmpOutDestUnreachs
ipv6IfIcmpOutAdminProhibs
ipv6IfIcmpOutTimeExcds
ipv6IfIcmpOutParmProblems
ipv6IfIcmpOutPktTooBigs
ipv6IfIcmpOutEchos
ipv6IfIcmpOutEchoReplies
ipv6IfIcmpOutRouterSolicits
ipv6IfIcmpOutRouterAdvertisements
ipv6IfIcmpOutNeighborSolicits
ipv6IfIcmpOutNeighborAdvertisements
ipv6IfIcmpOutRedirects
ipv6IfIcmpOutGroupMembQueries
ipv6IfIcmpOutGroupMembResponses
ipv6
}
STATUS
"The ICMPv6 group of objects providing
specific to ICMPv6."
Haskin & Onishi Standards Track [Page 13]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
::= { ipv6IcmpGroups 1 }
4.
This document borrows from MIB works produced by IETF for IPv4-
internets
We would like to thanks the following people for constructive
valuable comments
Mike Daniele
Margaret Forsythe
Jean-Pierre Roch
Juergen Schoenwaelder
Vivek Venkatraman
5.
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
and S. Waldbusser, "Structure of Management Information
Version 2 of the Simple Network Management Protocol (SNMPv2)",
RFC 1902, January 1996.
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S
Waldbusser, "Textual Conventions for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[3] McCloghrie, K., and M. Rose, Editors, "Management
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, March 1991.
[4] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "A
Network Management Protocol (SNMP)", STD 15, RFC 1157, May 1990.
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S
Waldbusser, "Protocol Operations for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[6] McCloghrie, K. and F. Kastenholz, "Evolution of the
Group of MIB-II", RFC 1573, January 1994.
[7] Deering, S. and R. Hinden, Editors, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
Haskin & Onishi Standards Track [Page 14]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
[8] Conta, A. and S. Deering, "Internet Control Message
(ICMPv6) for the Internet Protocol Version 6 (IPv6)
Specification", RFC 2463, December 1998.
[9] Haskin, D., and S. Onishi, "Management Information Base for
Version 6: Textual Conventions and General Group", RFC 2465,
December 1998.
6. Security
Certain management information defined in this MIB may be
sensitive in some network environments
Therefore, authentication of received SNMP requests and
access to management information should be employed in
environments
7. Authors'
Dimitry
Bay Networks, Inc
600 Technology Park
Billerica, MA 01821
EMail: dhaskin@baynetworks.
Steve
Bay Networks, Inc
3 Federal
Billerica, MA 01821
EMail: sonishi@baynetworks.
Haskin & Onishi Standards Track [Page 15]
RFC 2466 IPv6 MIB: ICMPv6 Group December 1998
8. Full Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Haskin & Onishi Standards Track [Page 16]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
