< draft-ops-smiv2-conf-00.txt   draft-ops-smiv2-conf-01.txt >
Network Working Group Document Editors: Network Working Group Editors of this version:
Internet Draft Keith McCloghrie Internet Draft K. McCloghrie
Cisco Systems Cisco Systems
David Perkins D. Perkins
Desktalk Systems & SNMPinfo Desktalk Systems & SNMPinfo
Juergen Schoenwaelder J. Schoenwaelder
TU Braunschweig TU Braunschweig
31 October 1998 Authors of previous version:
J. Case
SNMP Research
K. McCloghrie
Cisco Systems
M. Rose
First Virtual Holdings
S. Waldbusser
International Network Services
30 January 1999
Conformance Statements for SMIv2 Conformance Statements for SMIv2
draft-ops-smiv2-conf-00.txt draft-ops-smiv2-conf-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as ``work in progress.'' or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the To view the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow ``1id-abstracts.txt'' listing contained in an Internet-Drafts Shadow
Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), Directory, see http://www.ietf.org/shadow.html.
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Acknowledgements
This document is a revision of significant previous work by the four
major contributors:
Jeffrey D. Case (SNMP Research, case@snmp.com)
Keith McCloghrie (Cisco Systems, kzm@cisco.com)
Marshall T. Rose (First Virtual Holdings, mrose@dbc.mtview.ca.us)
Steven Waldbusser (International Network Services, stevew@uni.ins.com)
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
1. Introduction 1. Introduction
Management information is viewed as a collection of managed objects, Management information is viewed as a collection of managed objects,
residing in a virtual information store, termed the Management residing in a virtual information store, termed the Management
Information Base (MIB). Collections of related objects are defined in Information Base (MIB). Collections of related objects are defined in
MIB modules. These modules are written using an adapted subset of OSI's MIB modules. These modules are written using an adapted subset of OSI's
Abstract Syntax Notation One, ASN.1 (1988) [1], termed the Structure of Abstract Syntax Notation One, ASN.1 (1988) [1], termed the Structure of
Management Information (SMI) [2]. Management Information (SMI) [2].
skipping to change at page 3, line 5 skipping to change at page 3, line 5
It is the purpose of this document to define the notation used for these It is the purpose of this document to define the notation used for these
purposes. purposes.
1.1. A Note on Terminology 1.1. A Note on Terminology
For the purpose of exposition, the original Structure of Management For the purpose of exposition, the original Structure of Management
Information, as described in RFCs 1156 (STD 16), 1212 (STD 16), and RFC Information, as described in RFCs 1156 (STD 16), 1212 (STD 16), and RFC
1215, is termed the SMI version 1 (SMIv1). The current version of the 1215, is termed the SMI version 1 (SMIv1). The current version of the
Structure of Management Information is termed SMI version 2 (SMIv2). Structure of Management Information is termed SMI version 2 (SMIv2).
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
2. Definitions 2. Definitions
SNMPv2-CONF DEFINITIONS ::= BEGIN SNMPv2-CONF DEFINITIONS ::= BEGIN
IMPORTS ObjectName, NotificationName, ObjectSyntax IMPORTS ObjectName, NotificationName, ObjectSyntax
FROM SNMPv2-SMI; FROM SNMPv2-SMI;
-- definitions for conformance groups -- definitions for conformance groups
skipping to change at page 4, line 4 skipping to change at page 4, line 4
| "deprecated" | "deprecated"
| "obsolete" | "obsolete"
ReferPart ::= ReferPart ::=
"REFERENCE" Text "REFERENCE" Text
| empty | empty
-- a character string as defined in [2] -- a character string as defined in [2]
Text ::= value(IA5String) Text ::= value(IA5String)
END END
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
-- more definitions for conformance groups -- more definitions for conformance groups
NOTIFICATION-GROUP MACRO ::= NOTIFICATION-GROUP MACRO ::=
BEGIN BEGIN
TYPE NOTATION ::= TYPE NOTATION ::=
NotificationsPart NotificationsPart
"STATUS" Status "STATUS" Status
"DESCRIPTION" Text "DESCRIPTION" Text
ReferPart ReferPart
skipping to change at page 5, line 4 skipping to change at page 5, line 4
| "deprecated" | "deprecated"
| "obsolete" | "obsolete"
ReferPart ::= ReferPart ::=
"REFERENCE" Text "REFERENCE" Text
| empty | empty
-- a character string as defined in [2] -- a character string as defined in [2]
Text ::= value(IA5String) Text ::= value(IA5String)
END END
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
-- definitions for compliance statements -- definitions for compliance statements
MODULE-COMPLIANCE MACRO ::= MODULE-COMPLIANCE MACRO ::=
BEGIN BEGIN
TYPE NOTATION ::= TYPE NOTATION ::=
"STATUS" Status "STATUS" Status
"DESCRIPTION" Text "DESCRIPTION" Text
ReferPart ReferPart
ModulePart ModulePart
skipping to change at page 5, line 30 skipping to change at page 5, line 31
"current" "current"
| "deprecated" | "deprecated"
| "obsolete" | "obsolete"
ReferPart ::= ReferPart ::=
"REFERENCE" Text "REFERENCE" Text
| empty | empty
ModulePart ::= ModulePart ::=
Modules Modules
| empty
Modules ::= Modules ::=
Module Module
| Modules Module | Modules Module
Module ::= Module ::=
-- name of module -- -- name of module --
"MODULE" ModuleName "MODULE" ModuleName
MandatoryPart MandatoryPart
CompliancePart CompliancePart
ModuleName ::= ModuleName ::=
-- identifier must start with uppercase letter -- identifier must start with uppercase letter
identifier ModuleIdentifier identifier ModuleIdentifier
-- must not be empty unless contained -- must not be empty unless contained
-- in MIB Module -- in MIB Module
| empty | empty
ModuleIdentifier ::= ModuleIdentifier ::=
value(OBJECT IDENTIFIER) value(OBJECT IDENTIFIER)
| empty | empty
MandatoryPart ::= MandatoryPart ::=
"MANDATORY-GROUPS" "{" Groups "}"
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
"MANDATORY-GROUPS" "{" Groups "}"
| empty | empty
Groups ::= Groups ::=
Group Group
| Groups "," Group | Groups "," Group
Group ::= Group ::=
value(OBJECT IDENTIFIER) value(OBJECT IDENTIFIER)
CompliancePart ::= CompliancePart ::=
Compliances Compliances
skipping to change at page 7, line 5 skipping to change at page 7, line 5
WriteSyntaxPart ::= "WRITE-SYNTAX" Syntax WriteSyntaxPart ::= "WRITE-SYNTAX" Syntax
| empty | empty
Syntax ::= -- Must be one of the following: Syntax ::= -- Must be one of the following:
-- a base type (or its refinement), -- a base type (or its refinement),
-- a textual convention (or its refinement), or -- a textual convention (or its refinement), or
-- a BITS pseudo-type -- a BITS pseudo-type
type type
| "BITS" "{" NamedBits "}" | "BITS" "{" NamedBits "}"
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
NamedBits ::= NamedBit NamedBits ::= NamedBit
| NamedBits "," NamedBit | NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative NamedBit ::= identifier "(" number ")" -- number is nonnegative
AccessPart ::= AccessPart ::=
"MIN-ACCESS" Access "MIN-ACCESS" Access
| empty | empty
Access ::= Access ::=
"not-accessible" "not-accessible"
| "accessible-for-notify" | "accessible-for-notify"
| "read-only" | "read-only"
| "read-write" | "read-write"
| "read-create" | "read-create"
-- a character string as defined in [2] -- a character string as defined in [2]
Text ::= value(IA5String) Text ::= value(IA5String)
END END
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
-- definitions for capabilities statements -- definitions for capabilities statements
AGENT-CAPABILITIES MACRO ::= AGENT-CAPABILITIES MACRO ::=
BEGIN BEGIN
TYPE NOTATION ::= TYPE NOTATION ::=
"PRODUCT-RELEASE" Text "PRODUCT-RELEASE" Text
"STATUS" Status "STATUS" Status
"DESCRIPTION" Text "DESCRIPTION" Text
ReferPart ReferPart
skipping to change at page 9, line 5 skipping to change at page 9, line 5
identifier ModuleIdentifier identifier ModuleIdentifier
ModuleIdentifier ::= ModuleIdentifier ::=
value(OBJECT IDENTIFIER) value(OBJECT IDENTIFIER)
| empty | empty
Groups ::= Groups ::=
Group Group
| Groups "," Group | Groups "," Group
Group ::= Group ::=
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
value(OBJECT IDENTIFIER) value(OBJECT IDENTIFIER)
VariationPart ::= VariationPart ::=
Variations Variations
| empty | empty
Variations ::= Variations ::=
Variation Variation
| Variations Variation | Variations Variation
skipping to change at page 10, line 5 skipping to change at page 10, line 5
-- a textual convention (or its refinement), or -- a textual convention (or its refinement), or
-- a BITS pseudo-type -- a BITS pseudo-type
type type
| "BITS" "{" NamedBits "}" | "BITS" "{" NamedBits "}"
NamedBits ::= NamedBit NamedBits ::= NamedBit
| NamedBits "," NamedBit | NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative NamedBit ::= identifier "(" number ")" -- number is nonnegative
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
AccessPart ::= AccessPart ::=
"ACCESS" Access "ACCESS" Access
| empty | empty
Access ::= Access ::=
"not-implemented" "not-implemented"
-- only "not-implemented" for notifications -- only "not-implemented" for notifications
| "accessible-for-notify" | "accessible-for-notify"
| "read-only" | "read-only"
skipping to change at page 11, line 4 skipping to change at page 11, line 4
BitNames ::= BitName BitNames ::= BitName
| BitNames "," BitName | BitNames "," BitName
BitName ::= identifier BitName ::= identifier
-- a character string as defined in [2] -- a character string as defined in [2]
Text ::= value(IA5String) Text ::= value(IA5String)
END END
END END
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
3. Mapping of the OBJECT-GROUP macro 3. Mapping of the OBJECT-GROUP macro
For conformance purposes, it is useful to define a collection of related For conformance purposes, it is useful to define a collection of related
managed objects. The OBJECT-GROUP macro is used to define each such managed objects. The OBJECT-GROUP macro is used to define each such
collection of related objects. It should be noted that the expansion of collection of related objects. It should be noted that the expansion of
the OBJECT-GROUP macro is something which conceptually happens during the OBJECT-GROUP macro is something which conceptually happens during
implementation and not during run-time. implementation and not during run-time.
To "implement" an object, an agent must return a reasonably accurate To "implement" an object, an agent must return a reasonably accurate
value for management protocol retrieval operations; similarly, if the value for management protocol retrieval operations; similarly, if the
object is writable, then in response to a management protocol set object is writable, then in response to a management protocol set
operation, an agent must accordingly be able to reasonably influence the operation, an agent must accordingly be able to reasonably influence the
underlying managed entity. If an agent can not implement an object, the underlying managed entity. If an agent can not implement an object, the
management protocol provides for it to return an exception or error, management protocol provides for it to return an exception or error,
e.g, noSuchObject [4]. Under no circumstances shall an agent return a e.g, noSuchObject [4]. Under no circumstances shall an agent return a
value for objects which it does not implement -- it must always return value for objects which it does not implement -- it must always return
the appropriate exception or error, as described in the protocol the appropriate exception or error, as described in the protocol
specification [4]. specification [4].
Note that the OBJECT-GROUP macro itself provide no conformance Note that the OBJECT-GROUP macro itself provides no conformance
information. Rather, conformance information is specified through the information. Rather, conformance information is specified through the
inclusion of defined groups in a MODULE-COMPLIANCE macro. inclusion of defined groups in a MODULE-COMPLIANCE macro.
3.1. Mapping of the OBJECTS clause 3.1. Mapping of the OBJECTS clause
The OBJECTS clause, which must be present, is used to specify each The OBJECTS clause, which must be present, is used to specify each
object contained in the conformance group. Each of the specified object contained in the conformance group. Each of the specified
objects must be defined in the same information module as the OBJECT- objects must be defined in the same information module as the OBJECT-
GROUP macro appears, and must have a MAX-ACCESS clause value of GROUP macro appears, and must have a MAX-ACCESS clause value of
"accessible-for-notify", "read-only", "read-write", or "read-create". "accessible-for-notify", "read-only", "read-write", or "read-create".
skipping to change at page 12, line 5 skipping to change at page 12, line 5
MAX-ACCESS clause other than "not-accessible" be contained in at least MAX-ACCESS clause other than "not-accessible" be contained in at least
one object group. This avoids the common error of adding a new object one object group. This avoids the common error of adding a new object
to an information module and forgetting to add the new object to a to an information module and forgetting to add the new object to a
group. group.
3.2. Mapping of the STATUS clause 3.2. Mapping of the STATUS clause
The STATUS clause, which must be present, indicates whether this The STATUS clause, which must be present, indicates whether this
definition is current or historic. definition is current or historic.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
The value "current" means that the definition is current and valid. The The value "current" means that the definition is current and valid. The
value "obsolete" means the definition is obsolete and the group should value "obsolete" means the definition is obsolete and the group should
no longer be used for defining conformance. While the value no longer be used for defining conformance. While the value
"deprecated" also indicates an obsolete definition, it permits "deprecated" also indicates an obsolete definition, it permits
new/continued use of conformance definitions using this group. new/continued use of conformance definitions using this group.
3.3. Mapping of the DESCRIPTION clause 3.3. Mapping of the DESCRIPTION clause
The DESCRIPTION clause, which must be present, contains a textual The DESCRIPTION clause, which must be present, contains a textual
skipping to change at page 13, line 4 skipping to change at page 13, line 4
3.4. Mapping of the REFERENCE clause 3.4. Mapping of the REFERENCE clause
The REFERENCE clause, which need not be present, contains a textual The REFERENCE clause, which need not be present, contains a textual
cross-reference to some other document, either another information cross-reference to some other document, either another information
module which defines a related assignment, or some other document which module which defines a related assignment, or some other document which
provides additional information relevant to this definition. provides additional information relevant to this definition.
3.5. Mapping of the OBJECT-GROUP value 3.5. Mapping of the OBJECT-GROUP value
The value of an invocation of the OBJECT-GROUP macro is the name of the The value of an invocation of the OBJECT-GROUP macro is the name of the
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
group, which is an OBJECT IDENTIFIER, an administratively assigned name. group, which is an OBJECT IDENTIFIER, an administratively assigned name.
3.6. Usage Example 3.6. Usage Example
The SNMP Group [3] is described: The SNMP Group [3] is described:
snmpGroup OBJECT-GROUP snmpGroup OBJECT-GROUP
OBJECTS { snmpInPkts, OBJECTS { snmpInPkts,
snmpInBadVersions, snmpInBadVersions,
skipping to change at page 14, line 5 skipping to change at page 14, line 5
"A collection of objects providing basic instrumentation and "A collection of objects providing basic instrumentation and
control of an agent." control of an agent."
::= { snmpMIBGroups 8 } ::= { snmpMIBGroups 8 }
According to this invocation, the conformance group named According to this invocation, the conformance group named
{ snmpMIBGroups 8 } { snmpMIBGroups 8 }
contains 7 objects. contains 7 objects.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
4. Mapping of the NOTIFICATION-GROUP macro 4. Mapping of the NOTIFICATION-GROUP macro
For conformance purposes, it is useful to define a collection of For conformance purposes, it is useful to define a collection of
notifications. The NOTIFICATION-GROUP macro serves this purpose. It notifications. The NOTIFICATION-GROUP macro serves this purpose. It
should be noted that the expansion of the NOTIFICATION-GROUP macro is should be noted that the expansion of the NOTIFICATION-GROUP macro is
something which conceptually happens during implementation and not something which conceptually happens during implementation and not
during run-time. during run-time.
4.1. Mapping of the NOTIFICATIONS clause 4.1. Mapping of the NOTIFICATIONS clause
skipping to change at page 15, line 4 skipping to change at page 15, line 4
The DESCRIPTION clause, which must be present, contains a textual The DESCRIPTION clause, which must be present, contains a textual
definition of the group, along with a description of any relations to definition of the group, along with a description of any relations to
other groups. Note that generic compliance requirements should not be other groups. Note that generic compliance requirements should not be
stated in this clause. However, implementation relationships between stated in this clause. However, implementation relationships between
this group and other groups may be defined in this clause. this group and other groups may be defined in this clause.
4.4. Mapping of the REFERENCE clause 4.4. Mapping of the REFERENCE clause
The REFERENCE clause, which need not be present, contains a textual The REFERENCE clause, which need not be present, contains a textual
cross-reference to some other document, either another information cross-reference to some other document, either another information
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
module which defines a related assignment, or some other document which module which defines a related assignment, or some other document which
provides additional information relevant to this definition. provides additional information relevant to this definition.
4.5. Mapping of the NOTIFICATION-GROUP value 4.5. Mapping of the NOTIFICATION-GROUP value
The value of an invocation of the NOTIFICATION-GROUP macro is the name The value of an invocation of the NOTIFICATION-GROUP macro is the name
of the group, which is an OBJECT IDENTIFIER, an administratively of the group, which is an OBJECT IDENTIFIER, an administratively
assigned name. assigned name.
skipping to change at page 16, line 5 skipping to change at page 16, line 5
"The two notifications which an agent is required to "The two notifications which an agent is required to
implement." implement."
::= { snmpMIBGroups 7 } ::= { snmpMIBGroups 7 }
According to this invocation, the conformance group named According to this invocation, the conformance group named
{ snmpMIBGroups 7 } { snmpMIBGroups 7 }
contains 2 notifications. contains 2 notifications.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
5. Mapping of the MODULE-COMPLIANCE macro 5. Mapping of the MODULE-COMPLIANCE macro
The MODULE-COMPLIANCE macro is used to convey a minimum set of The MODULE-COMPLIANCE macro is used to convey a minimum set of
requirements with respect to implementation of one or more MIB modules. requirements with respect to implementation of one or more MIB modules.
It should be noted that the expansion of the MODULE-COMPLIANCE macro is It should be noted that the expansion of the MODULE-COMPLIANCE macro is
something which conceptually happens during implementation and not something which conceptually happens during implementation and not
during run-time. during run-time.
A requirement on all "standard" MIB modules is that a corresponding A requirement on all "standard" MIB modules is that a corresponding
skipping to change at page 17, line 5 skipping to change at page 17, line 5
information which would otherwise be communicated in any ASN.1 information which would otherwise be communicated in any ASN.1
commentary annotations associated with the statement. commentary annotations associated with the statement.
5.3. Mapping of the REFERENCE clause 5.3. Mapping of the REFERENCE clause
The REFERENCE clause, which need not be present, contains a textual The REFERENCE clause, which need not be present, contains a textual
cross-reference to some other document, either another information cross-reference to some other document, either another information
module which defines a related assignment, or some other document which module which defines a related assignment, or some other document which
provides additional information relevant to this definition. provides additional information relevant to this definition.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
5.4. Mapping of the MODULE clause 5.4. Mapping of the MODULE clause
The MODULE clause, which must be present, is repeatedly used to name The MODULE clause, which must be present, is repeatedly used to name
each MIB module for which compliance requirements are being specified. each MIB module for which compliance requirements are being specified.
Each MIB module is named by its module name, and optionally, by its Each MIB module is named by its module name, and optionally, by its
associated OBJECT IDENTIFIER as well. The module name can be omitted associated OBJECT IDENTIFIER as well. The module name can be omitted
when the MODULE-COMPLIANCE invocation occurs inside a MIB module, to when the MODULE-COMPLIANCE invocation occurs inside a MIB module, to
refer to the encompassing MIB module. refer to the encompassing MIB module.
skipping to change at page 18, line 5 skipping to change at page 18, line 5
be absent from the correspondent MANDATORY-GROUPS clause. be absent from the correspondent MANDATORY-GROUPS clause.
Conditionally mandatory groups include those which are mandatory only if Conditionally mandatory groups include those which are mandatory only if
a particular protocol is implemented, or only if another group is a particular protocol is implemented, or only if another group is
implemented. A GROUP clause's DESCRIPTION specifies the conditions implemented. A GROUP clause's DESCRIPTION specifies the conditions
under which the group is conditionally mandatory. under which the group is conditionally mandatory.
A group which is named in neither a MANDATORY-GROUPS clause nor a GROUP A group which is named in neither a MANDATORY-GROUPS clause nor a GROUP
clause, is unconditionally optional for compliance to the MIB module. clause, is unconditionally optional for compliance to the MIB module.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
5.4.3. Mapping of the OBJECT clause 5.4.3. Mapping of the OBJECT clause
The OBJECT clause, which need not be present, is repeatedly used to The OBJECT clause, which need not be present, is repeatedly used to
specify each MIB object for which compliance has a refined requirement specify each MIB object for which compliance has a refined requirement
with respect to the MIB module definition. The MIB object must be with respect to the MIB module definition. The MIB object must be
present in one of the conformance groups named in the correspondent present in one of the conformance groups named in the correspondent
MANDATORY-GROUPS clause or GROUP clauses. MANDATORY-GROUPS clause or GROUP clauses.
By definition, each object specified in an OBJECT clause follows a By definition, each object specified in an OBJECT clause follows a
skipping to change at page 19, line 5 skipping to change at page 19, line 5
5.4.3.3. Mapping of the MIN-ACCESS clause 5.4.3.3. Mapping of the MIN-ACCESS clause
The MIN-ACCESS clause, which need not be present, is used to define the The MIN-ACCESS clause, which need not be present, is used to define the
minimal level of access for the object named in the correspondent OBJECT minimal level of access for the object named in the correspondent OBJECT
clause. If this clause is absent, the minimal level of access is the clause. If this clause is absent, the minimal level of access is the
same as the maximal level specified in the correspondent invocation of same as the maximal level specified in the correspondent invocation of
the OBJECT-TYPE macro. If present, this clause must not specify a the OBJECT-TYPE macro. If present, this clause must not specify a
greater level of access than is specified in the correspondent greater level of access than is specified in the correspondent
invocation of the OBJECT-TYPE macro. invocation of the OBJECT-TYPE macro.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
The level of access for certain types of objects is fixed according to The level of access for certain types of objects is fixed according to
their syntax definition. These types include: conceptual tables and their syntax definition. These types include: conceptual tables and
rows, auxiliary objects, and objects with the syntax of Counter32, rows, auxiliary objects, and objects with the syntax of Counter32,
Counter64 (and possibly, certain types of textual conventions). A MIN- Counter64 (and possibly, certain types of textual conventions). A MIN-
ACCESS clause should not be present for such objects. ACCESS clause should not be present for such objects.
An implementation is compliant if the level of access it provides is An implementation is compliant if the level of access it provides is
greater or equal to the minimal level in the MODULE-COMPLIANCE macro and greater or equal to the minimal level in the MODULE-COMPLIANCE macro and
less or equal to the maximal level in the OBJECT-TYPE macro. less or equal to the maximal level in the OBJECT-TYPE macro.
skipping to change at page 20, line 5 skipping to change at page 20, line 5
a textual description of the conditions under which the group is a textual description of the conditions under which the group is
conditionally mandatory or unconditionally optional. conditionally mandatory or unconditionally optional.
5.5. Mapping of the MODULE-COMPLIANCE value 5.5. Mapping of the MODULE-COMPLIANCE value
The value of an invocation of the MODULE-COMPLIANCE macro is an OBJECT The value of an invocation of the MODULE-COMPLIANCE macro is an OBJECT
IDENTIFIER. As such, this value may be authoritatively used when IDENTIFIER. As such, this value may be authoritatively used when
referring to the compliance statement embodied by that invocation of the referring to the compliance statement embodied by that invocation of the
macro. macro.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
5.6. Usage Example 5.6. Usage Example
The compliance statement contained in the (hypothetical) XYZv2-MIB might The compliance statement contained in the (hypothetical) XYZv2-MIB might
be: be:
xyzMIBCompliance MODULE-COMPLIANCE xyzMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for XYZv2 entities which implement "The compliance statement for XYZv2 entities which implement
skipping to change at page 21, line 5 skipping to change at page 21, line 5
statement named statement named
{ xyzMIBCompliances 1 } { xyzMIBCompliances 1 }
a system must implement the XYZv2-MIB's xyzSystemGroup, xyzStatsGroup, a system must implement the XYZv2-MIB's xyzSystemGroup, xyzStatsGroup,
xyzTrapGroup, and xyzSetGroup object conformance groups, as well as the xyzTrapGroup, and xyzSetGroup object conformance groups, as well as the
xyzBasicNotificationsGroup notifications group. Furthermore, if the xyzBasicNotificationsGroup notifications group. Furthermore, if the
XYZv2 entity also implements XYZv1, then it must also support the XYZv2 entity also implements XYZv1, then it must also support the
XYZv1Group group, if compliance is to be claimed. XYZv1Group group, if compliance is to be claimed.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
6. Mapping of the AGENT-CAPABILITIES macro 6. Mapping of the AGENT-CAPABILITIES macro
The AGENT-CAPABILITIES macro is used to convey a set of capabilities The AGENT-CAPABILITIES macro is used to convey a set of capabilities
present in an agent. It should be noted that the expansion of the present in an agent. It should be noted that the expansion of the
AGENT-CAPABILITIES macro is something which conceptually happens during AGENT-CAPABILITIES macro is something which conceptually happens during
implementation and not during run-time. implementation and not during run-time.
When a MIB module is written, it is divided into units of conformance When a MIB module is written, it is divided into units of conformance
termed groups. If an agent claims to implement a group, then it must termed groups. If an agent claims to implement a group, then it must
skipping to change at page 22, line 5 skipping to change at page 22, line 5
variations with respect to OBJECT-TYPE and NOTIFICATION-TYPE macros in variations with respect to OBJECT-TYPE and NOTIFICATION-TYPE macros in
MIB modules, NOT with respect to MODULE-COMPLIANCE macros in compliance MIB modules, NOT with respect to MODULE-COMPLIANCE macros in compliance
statements. statements.
6.1. Mapping of the PRODUCT-RELEASE clause 6.1. Mapping of the PRODUCT-RELEASE clause
The PRODUCT-RELEASE clause, which must be present, contains a textual The PRODUCT-RELEASE clause, which must be present, contains a textual
description of the product release which includes this set of description of the product release which includes this set of
capabilities. capabilities.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
6.2. Mapping of the STATUS clause 6.2. Mapping of the STATUS clause
The STATUS clause, which must be present, indicates whether this The STATUS clause, which must be present, indicates whether this
definition is current ("current") or historic ("obsolete"). definition is current or historic.
The value "current" means that the definition is current and valid. The
value "obsolete" means the definition is obsolete and this capabilities
statement is no longer in use.
6.3. Mapping of the DESCRIPTION clause 6.3. Mapping of the DESCRIPTION clause
The DESCRIPTION clause, which must be present, contains a textual The DESCRIPTION clause, which must be present, contains a textual
description of this set of capabilities. description of this set of capabilities.
6.4. Mapping of the REFERENCE clause 6.4. Mapping of the REFERENCE clause
The REFERENCE clause, which need not be present, contains a textual The REFERENCE clause, which need not be present, contains a textual
cross-reference to some other document, either another information cross-reference to some other document, either another information
skipping to change at page 22, line 34 skipping to change at page 22, line 38
6.5. Mapping of the SUPPORTS clause 6.5. Mapping of the SUPPORTS clause
The SUPPORTS clause, which need not be present, is repeatedly used to The SUPPORTS clause, which need not be present, is repeatedly used to
name each MIB module for which the agent claims a complete or partial name each MIB module for which the agent claims a complete or partial
implementation. Each MIB module is named by its module name, and implementation. Each MIB module is named by its module name, and
optionally, by its associated OBJECT IDENTIFIER (as registered by the optionally, by its associated OBJECT IDENTIFIER (as registered by the
MODULE-IDENTITY macro, see [2]) as well. MODULE-IDENTITY macro, see [2]) as well.
6.5.1. Mapping of the INCLUDES clause 6.5.1. Mapping of the INCLUDES clause
The INCLUDES clause, which must be present for each use of the SUPPORTS The INCLUDES clause, which must follow each and every use of the
clause, is used to name each MIB group associated with the SUPPORTS SUPPORTS clause, is used to name each MIB group associated with the
clause, which the agent claims to implement. SUPPORTS clause, which the agent claims to implement.
6.5.2. Mapping of the VARIATION clause 6.5.2. Mapping of the VARIATION clause
The VARIATION clause, which need not be present, is repeatedly used to The VARIATION clause, which need not be present, is repeatedly used to
name each object or notification which the agent implements in some name each object or notification which the agent implements in some
variant or refined fashion with respect to the correspondent invocation variant or refined fashion with respect to the correspondent invocation
Draft Conformance Statements for SMIv2 Jaunuary 1999
of the OBJECT-TYPE or NOTIFICATION-TYPE macro. of the OBJECT-TYPE or NOTIFICATION-TYPE macro.
Note that the variation concept is meant for generic implementation Note that the variation concept is meant for generic implementation
restrictions, e.g., if the variation for an object depends on the values restrictions, e.g., if the variation for an object depends on the values
Draft Conformance Statements for SMIv2 October 1998
of other objects, then this should be noted in the appropriate of other objects, then this should be noted in the appropriate
DESCRIPTION clause. DESCRIPTION clause.
By definition, each object specified in a VARIATION clause follows a By definition, each object specified in a VARIATION clause follows a
SUPPORTS clause which names the information module in which that object SUPPORTS clause which names the information module in which that object
is defined. Therefore, the use of an IMPORTS statement, to specify from is defined. Therefore, the use of an IMPORTS statement, to specify from
where such objects are imported, is redundant and is not required in an where such objects are imported, is redundant and is not required in an
information module. information module.
6.5.2.1. Mapping of the SYNTAX clause 6.5.2.1. Mapping of the SYNTAX clause
skipping to change at page 23, line 42 skipping to change at page 24, line 5
enumerations are currently supported. enumerations are currently supported.
6.5.2.2. Mapping of the WRITE-SYNTAX clause 6.5.2.2. Mapping of the WRITE-SYNTAX clause
The WRITE-SYNTAX clause, which need not be present, is used to provide a The WRITE-SYNTAX clause, which need not be present, is used to provide a
refined SYNTAX for the object named in the correspondent VARIATION refined SYNTAX for the object named in the correspondent VARIATION
clause when instances of that object are written. clause when instances of that object are written.
Consult Section 9 of [2] for more information on refined syntax. Consult Section 9 of [2] for more information on refined syntax.
Draft Conformance Statements for SMIv2 Jaunuary 1999
6.5.2.3. Mapping of the ACCESS clause 6.5.2.3. Mapping of the ACCESS clause
The ACCESS clause, which need not be present, is used to indicate the The ACCESS clause, which need not be present, is used to indicate the
agent provides less than the maximal level of access to the object or agent provides less than the maximal level of access to the object or
notification named in the correspondent VARIATION clause. notification named in the correspondent VARIATION clause.
Draft Conformance Statements for SMIv2 October 1998
The only value applicable to notifications is "not-implemented". The only value applicable to notifications is "not-implemented".
The value "not-implemented" indicates the agent does not implement the The value "not-implemented" indicates the agent does not implement the
object or notification, and in the ordering of possible values is object or notification, and in the ordering of possible values is
equivalent to "not-accessible". equivalent to "not-accessible".
The value "write-only" is provided solely for backward compatibility, The value "write-only" is provided solely for backward compatibility,
and shall not be used for newly-defined object types. In the ordering and shall not be used for newly-defined object types. In the ordering
of possible values, "write-only" is less than "not-accessible". of possible values, "write-only" is less than "not-accessible".
skipping to change at page 24, line 43 skipping to change at page 25, line 5
correspondent VARIATION clause is a conceptual row, i.e., has a syntax correspondent VARIATION clause is a conceptual row, i.e., has a syntax
which resolves to a SEQUENCE containing columnar objects. The objects which resolves to a SEQUENCE containing columnar objects. The objects
named in the value of this clause usually will refer to columnar objects named in the value of this clause usually will refer to columnar objects
in that row. However, objects unrelated to the conceptual row may also in that row. However, objects unrelated to the conceptual row may also
be specified. be specified.
All objects which are named in the CREATION-REQUIRES clause for a All objects which are named in the CREATION-REQUIRES clause for a
conceptual row, and which are columnar objects of that row, must have an conceptual row, and which are columnar objects of that row, must have an
access level of "read-create". access level of "read-create".
Draft Conformance Statements for SMIv2 Jaunuary 1999
6.5.2.5. Mapping of the DEFVAL clause 6.5.2.5. Mapping of the DEFVAL clause
The DEFVAL clause, which need not be present, is used to provide a The DEFVAL clause, which need not be present, is used to provide a
alternate DEFVAL value for the object named in the correspondent alternate DEFVAL value for the object named in the correspondent
VARIATION clause. The semantics of this value are identical to those of VARIATION clause. The semantics of this value are identical to those of
the OBJECT-TYPE macro's DEFVAL clause. the OBJECT-TYPE macro's DEFVAL clause.
Draft Conformance Statements for SMIv2 October 1998
6.5.2.6. Mapping of the DESCRIPTION clause 6.5.2.6. Mapping of the DESCRIPTION clause
The DESCRIPTION clause, which must be present for each use of the The DESCRIPTION clause, which must be present for each use of the
VARIATION clause, contains a textual description of the variant or VARIATION clause, contains a textual description of the variant or
refined implementation of the object or notification. refined implementation of the object or notification.
6.6. Mapping of the AGENT-CAPABILITIES value 6.6. Mapping of the AGENT-CAPABILITIES value
The value of an invocation of the AGENT-CAPABILITIES macro is an OBJECT The value of an invocation of the AGENT-CAPABILITIES macro is an OBJECT
IDENTIFIER, which names the value of sysORID [3] for which this IDENTIFIER, which names the value of sysORID [3] for which this
skipping to change at page 25, line 43 skipping to change at page 26, line 5
DESCRIPTION "A coldStart trap is generated on all DESCRIPTION "A coldStart trap is generated on all
reboots." reboots."
SUPPORTS IF-MIB SUPPORTS IF-MIB
INCLUDES { ifGeneralGroup, ifPacketGroup } INCLUDES { ifGeneralGroup, ifPacketGroup }
VARIATION ifAdminStatus VARIATION ifAdminStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION "Unable to set test mode on 4BSD." DESCRIPTION "Unable to set test mode on 4BSD."
Draft Conformance Statements for SMIv2 Jaunuary 1999
VARIATION ifOperStatus VARIATION ifOperStatus
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION "Information limited on 4BSD." DESCRIPTION "Information limited on 4BSD."
SUPPORTS IP-MIB SUPPORTS IP-MIB
INCLUDES { ipGroup, icmpGroup } INCLUDES { ipGroup, icmpGroup }
Draft Conformance Statements for SMIv2 October 1998
VARIATION ipDefaultTTL VARIATION ipDefaultTTL
SYNTAX INTEGER (255..255) SYNTAX INTEGER (255..255)
DESCRIPTION "Hard-wired on 4BSD." DESCRIPTION "Hard-wired on 4BSD."
VARIATION ipInAddrErrors VARIATION ipInAddrErrors
ACCESS not-implemented ACCESS not-implemented
DESCRIPTION "Information not available on 4BSD." DESCRIPTION "Information not available on 4BSD."
VARIATION ipNetToMediaEntry VARIATION ipNetToMediaEntry
CREATION-REQUIRES { ipNetToMediaPhysAddress } CREATION-REQUIRES { ipNetToMediaPhysAddress }
skipping to change at page 26, line 43 skipping to change at page 27, line 5
DESCRIPTION "Conceptual row creation is supported." DESCRIPTION "Conceptual row creation is supported."
::= { acmeAgents 1 } ::= { acmeAgents 1 }
According to this invocation, an agent with a sysORID value of According to this invocation, an agent with a sysORID value of
{ acmeAgents 1 } { acmeAgents 1 }
supports objects defined in six MIB modules. supports objects defined in six MIB modules.
Draft Conformance Statements for SMIv2 Jaunuary 1999
>From SNMPv2-MIB, five conformance groups are supported. >From SNMPv2-MIB, five conformance groups are supported.
>From IF-MIB, the ifGeneralGroup and ifPacketGroup groups are supported. >From IF-MIB, the ifGeneralGroup and ifPacketGroup groups are supported.
However, the objects ifAdminStatus and ifOperStatus have a restricted However, the objects ifAdminStatus and ifOperStatus have a restricted
syntax. syntax.
>From IP-MIB, all objects in the ipGroup and icmpGroup are supported >From IP-MIB, all objects in the ipGroup and icmpGroup are supported
except ipInAddrErrors, while ipDefaultTTL has a restricted range, and except ipInAddrErrors, while ipDefaultTTL has a restricted range, and
Draft Conformance Statements for SMIv2 October 1998
when creating a new instance in the ipNetToMediaTable, the set-request when creating a new instance in the ipNetToMediaTable, the set-request
must create an instance of ipNetToMediaPhysAddress. must create an instance of ipNetToMediaPhysAddress.
>From TCP-MIB, the tcpGroup is supported except that tcpConnState is >From TCP-MIB, the tcpGroup is supported except that tcpConnState is
available only for reading. available only for reading.
>From UDP-MIB, the udpGroup is fully supported. >From UDP-MIB, the udpGroup is fully supported.
>From the EVAL-MIB, all the objects contained in the functionsGroup and >From the EVAL-MIB, all the objects contained in the functionsGroup and
expressionsGroup conformance groups are supported, without variation. expressionsGroup conformance groups are supported, without variation.
In addition, creation of new instances in the expr table is supported, In addition, creation of new instances in the expr table is supported,
and requires both of the objects: evalString and evalStatus, to be and requires both of the objects: evalString and evalStatus, to be
assigned a value. assigned a value.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
7. Extending an Information Module 7. Extending an Information Module
As experience is gained with a published information module, it may be As experience is gained with a published information module, it may be
desirable to revise that information module. desirable to revise that information module.
Section 10 of [2] defines the rules for extending an information module. Section 10 of [2] defines the rules for extending an information module.
The remainder of this section defines how conformance groups, compliance The remainder of this section defines how conformance groups, compliance
statements, and capabilities statements may be extended. statements, and capabilities statements may be extended.
skipping to change at page 29, line 4 skipping to change at page 29, line 4
(4) Any editorial change. (4) Any editorial change.
It is not necessary to change the STATUS value of a conformance group It is not necessary to change the STATUS value of a conformance group
when the status of a member of the group is changed. when the status of a member of the group is changed.
7.2. Compliance Definitions 7.2. Compliance Definitions
It may be desirable to revise the definition of a compliance definition It may be desirable to revise the definition of a compliance definition
(MODULE-COMPLIANCE) after experience is gained with it. However, (MODULE-COMPLIANCE) after experience is gained with it. However,
changes are not allowed if they cause the requirements specified by the changes are not allowed if they cause the requirements specified by the
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
original definition to be different from the requirements of the updated original definition to be different from the requirements of the updated
definition. Such changes can only be accommodated by defining a new definition. Such changes can only be accommodated by defining a new
compliance definition with a new descriptor and a new OBJECT IDENTIFIER compliance definition with a new descriptor and a new OBJECT IDENTIFIER
value. value.
The following revisions are allowed: The following revisions are allowed:
(1) A STATUS clause value of "current" may be revised as "deprecated" (1) A STATUS clause value of "current" may be revised as "deprecated"
or "obsolete". Similarly, a STATUS clause value of "deprecated" or "obsolete". Similarly, a STATUS clause value of "deprecated"
skipping to change at page 30, line 5 skipping to change at page 30, line 5
(1) A STATUS clause value of "current" may be revised as "obsolete". (1) A STATUS clause value of "current" may be revised as "obsolete".
When making such a change, the DESCRIPTION clause should be updated When making such a change, the DESCRIPTION clause should be updated
to explain the rationale. to explain the rationale.
(2) A REFERENCE clause may be added or updated. (2) A REFERENCE clause may be added or updated.
(3) Clarifications and additional information may be included in the (3) Clarifications and additional information may be included in the
DESCRIPTION clause(s). DESCRIPTION clause(s).
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
(4) Any editorial change. (4) Any editorial change.
It is not necessary to change the STATUS value of a capabilities It is not necessary to change the STATUS value of a capabilities
definition due to a change in the STATUS value of a definition it definition due to a change in the STATUS value of a definition it
references. references.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
8. Security Considerations 8. Security Considerations
This document defines the means to define conformance requirements for This document defines the means to define conformance requirements for
implementing on documents describing management information. This implementing on documents describing management information. This
method of defining conformance requirements has no security impact on method of defining conformance requirements has no security impact on
the Internet. the Internet.
9. Editors' Addresses 9. Editors' Addresses
skipping to change at page 32, line 5 skipping to change at page 32, line 5
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
Juergen Schoenwaelder Juergen Schoenwaelder
TU Braunschweig TU Braunschweig
Bueltenweg 74/75 Bueltenweg 74/75
38106 Braunschweig 38106 Braunschweig
Germany Germany
Phone: +49 531 391-3283 Phone: +49 531 391-3283
Email: schoenw@ibr.cs.tu-bs.de Email: schoenw@ibr.cs.tu-bs.de
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
10. References 10. References
[1] Information processing systems - Open Systems Interconnection - [1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1), Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization. International International Organization for Standardization. International
Standard 8824, (December, 1987). Standard 8824, (December, 1987).
[2] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Structure of [2] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
Management Information Version 2 (SMIv2)", draft-ops-smiv2-smi- and Waldbusser, S. "Structure of Management Information Version 2
00.txt, October 1998. (SMIv2)", draft-ops-smiv2-smi-01.txt, January 1999.
[3] The SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [3] The SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
Waldbusser, S., "Management Information Base for Version 2 of the Waldbusser, S., "Management Information Base for Version 2 of the
Simple Network Management Protocol (SNMPv2)", RFC 1907, January Simple Network Management Protocol (SNMPv2)", RFC 1907, January
1996. 1996.
[4] The SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [4] The SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
Waldbusser, S., "Protocol Operations for Version 2 of the Simple Waldbusser, S., "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[5] McCloghrie, K., Perkins, D., and Schoenwaelder, J., "Textual [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
Conventions for SMIv2", draft-ops-smiv2-tc-00.txt, October 1998. and Waldbusser, S. "Textual Conventions for SMIv2", draft-ops-
smiv2-tc-01.txt, January 1999.
[6] Rose, M., and McCloghrie, K., "Structure and Identification of [6] Rose, M., and McCloghrie, K., "Structure and Identification of
Management Information for TCP/IP-based internets", STD 16, RFC Management Information for TCP/IP-based internets", STD 16, RFC
1155, May 1990. 1155, May 1990.
[7] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16, [7] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16,
RFC 1212, March 1991. RFC 1212, March 1991.
Draft Conformance Statements for SMIv2 October 1998 Draft Conformance Statements for SMIv2 Jaunuary 1999
11. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
skipping to change at page 34, line 4 skipping to change at page 34, line 4
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE." FITNESS FOR A PARTICULAR PURPOSE."
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
Table of Contents Table of Contents
1 Introduction .................................................... 2 1 Introduction .................................................... 2
1.1 A Note on Terminology ......................................... 2 1.1 A Note on Terminology ......................................... 2
2 Definitions ..................................................... 3 2 Definitions ..................................................... 3
2.1 The OBJECT-GROUP macro ........................................ 3 2.1 The OBJECT-GROUP macro ........................................ 3
2.2 The NOTIFICATION-GROUP macro .................................. 4 2.2 The NOTIFICATION-GROUP macro .................................. 4
2.3 The MODULE-COMPLIANCE macro ................................... 5 2.3 The MODULE-COMPLIANCE macro ................................... 5
2.4 The AGENT-CAPABILITIES macro .................................. 8 2.4 The AGENT-CAPABILITIES macro .................................. 8
skipping to change at page 35, line 4 skipping to change at page 35, line 4
5.4.4 Mapping of the DESCRIPTION clause ........................... 19 5.4.4 Mapping of the DESCRIPTION clause ........................... 19
5.5 Mapping of the MODULE-COMPLIANCE value ........................ 19 5.5 Mapping of the MODULE-COMPLIANCE value ........................ 19
5.6 Usage Example ................................................. 20 5.6 Usage Example ................................................. 20
6 Mapping of the AGENT-CAPABILITIES macro ......................... 21 6 Mapping of the AGENT-CAPABILITIES macro ......................... 21
6.1 Mapping of the PRODUCT-RELEASE clause ......................... 21 6.1 Mapping of the PRODUCT-RELEASE clause ......................... 21
6.2 Mapping of the STATUS clause .................................. 22 6.2 Mapping of the STATUS clause .................................. 22
6.3 Mapping of the DESCRIPTION clause ............................. 22 6.3 Mapping of the DESCRIPTION clause ............................. 22
6.4 Mapping of the REFERENCE clause ............................... 22 6.4 Mapping of the REFERENCE clause ............................... 22
6.5 Mapping of the SUPPORTS clause ................................ 22 6.5 Mapping of the SUPPORTS clause ................................ 22
6.5.1 Mapping of the INCLUDES clause .............................. 22 6.5.1 Mapping of the INCLUDES clause .............................. 22
Draft Conformance Statements for SMIv2 October 1998
Draft Conformance Statements for SMIv2 Jaunuary 1999
6.5.2 Mapping of the VARIATION clause ............................. 22 6.5.2 Mapping of the VARIATION clause ............................. 22
6.5.2.1 Mapping of the SYNTAX clause .............................. 23 6.5.2.1 Mapping of the SYNTAX clause .............................. 23
6.5.2.2 Mapping of the WRITE-SYNTAX clause ........................ 23 6.5.2.2 Mapping of the WRITE-SYNTAX clause ........................ 23
6.5.2.3 Mapping of the ACCESS clause .............................. 23 6.5.2.3 Mapping of the ACCESS clause .............................. 24
6.5.2.4 Mapping of the CREATION-REQUIRES clause ................... 24 6.5.2.4 Mapping of the CREATION-REQUIRES clause ................... 24
6.5.2.5 Mapping of the DEFVAL clause .............................. 24 6.5.2.5 Mapping of the DEFVAL clause .............................. 25
6.5.2.6 Mapping of the DESCRIPTION clause ......................... 25 6.5.2.6 Mapping of the DESCRIPTION clause ......................... 25
6.6 Mapping of the AGENT-CAPABILITIES value ....................... 25 6.6 Mapping of the AGENT-CAPABILITIES value ....................... 25
6.7 Usage Example ................................................. 25 6.7 Usage Example ................................................. 25
7 Extending an Information Module ................................. 28 7 Extending an Information Module ................................. 28
7.1 Conformance Groups ............................................ 28 7.1 Conformance Groups ............................................ 28
7.2 Compliance Definitions ........................................ 28 7.2 Compliance Definitions ........................................ 28
7.3 Capabilities Definitions ...................................... 29 7.3 Capabilities Definitions ...................................... 29
8 Security Considerations ......................................... 31 8 Security Considerations ......................................... 31
9 Editors' Addresses .............................................. 31 9 Editors' Addresses .............................................. 31
10 References ..................................................... 32 10 References ..................................................... 32
 End of changes. 59 change blocks. 
77 lines changed or deleted 90 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/