< draft-ietf-disman-notif-log-mib-16.txt   draft-ietf-disman-notif-log-mib-17.txt >
Notification Log MIB Network Working Group Editor of this version:
Internet-Draft Ramanathan R. Kavasseri
10 March 2000 Expires April 2001 Cisco Systems, Inc.
Author of previous version:
draft-ietf-disman-notif-log-mib-16.txt Bob Stewart
12 October 2000
Bob Stewart Notification Log MIB
Cisco Systems, Inc.
Ramanathan R. Kavasseri draft-ietf-disman-notif-log-mib-17.txt
Cisco Systems, Inc.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 39 skipping to change at page 2, line ?
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments to the Distribution of this document is unlimited. Please send comments to the
Distributed Management Working Group, <disman@dorothy.BMC.com>. Distributed Management Working Group, <disman@dorothy.BMC.com>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
1. Abstract 1. Abstract
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects used for logging SNMP particular, it describes managed objects used for logging SNMP
Notifications. Notifications.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 4, line 14 skipping to change at page 4, line 14
3.1.1. SNMP Engines and Contexts 3.1.1. SNMP Engines and Contexts
There are two distinct information flows from multiple notification There are two distinct information flows from multiple notification
originators that one may log. The first is the notifications that are originators that one may log. The first is the notifications that are
received (from one or more SNMP engines) for logging as SNMP informs and received (from one or more SNMP engines) for logging as SNMP informs and
traps. The other comprises notifications delivered to an SNMP engine at traps. The other comprises notifications delivered to an SNMP engine at
the interface to the notification originator (using a notification the interface to the notification originator (using a notification
mechanism other than SNMP informs or traps). The latter information mechanism other than SNMP informs or traps). The latter information
flow (using a notification mechanism other than SNMP informs or traps) flow (using a notification mechanism other than SNMP informs or traps)
MUST be modeled as the SNMP engine (which maintains the log) sending a is modeled here as the SNMP engine (which maintains the log) sending a
notification to itself. The remainder of this section discusses the notification to itself. The remainder of this section discusses the
handling of the former information flow - notifications (received in the handling of the former information flow - notifications (received in the
form of SNMP informs or traps) from multiple SNMP engines. form of SNMP informs or traps) from multiple SNMP engines.
As described in the SNMP architecture [RFC2571], a given system may As described in the SNMP architecture [RFC2571], a given system may
support multiple SNMP engines operating independently of one another, support multiple SNMP engines operating independently of one another,
each with its own SNMP engine identification. Furthermore, within the each with its own SNMP engine identification. Furthermore, within the
purview of a given engine there may be multiple named management purview of a given engine there may be multiple named management
contexts supporting overlapping or disjoint sets of MIB objects and contexts supporting overlapping or disjoint sets of MIB objects and
Notifications. Thus, understanding a particular Notification requires Notifications. Thus, understanding a particular Notification requires
skipping to change at page 4, line 45 skipping to change at page 4, line 45
is created. Thus such checking is possible only for locally-generated is created. Thus such checking is possible only for locally-generated
Notifications, and even then only when security credentials are Notifications, and even then only when security credentials are
available. available.
For the purpose of this discussion, "security credentials" means the For the purpose of this discussion, "security credentials" means the
input values for the abstract service interface function isAccessAllowed input values for the abstract service interface function isAccessAllowed
[RFC2571] and using those credentials means conceptually using that [RFC2571] and using those credentials means conceptually using that
function to see that those credentials allow access to the MIB objects function to see that those credentials allow access to the MIB objects
in question, operating as for a Notification Originator in [RFC2573]. in question, operating as for a Notification Originator in [RFC2573].
The Notification Log MIB has the notion of a "named log." By using The Notification Log MIB has the notion of a "named log." By using log
hierarchically structured log names and view-based access control names and view-based access control [RFC2575] a network administrator
[RFC2575] a network administrator can provide different access for can provide different access for different users. When an application
different users. When an application creates a named log the security creates a named log the security credentials of the creator stay
credentials of the creator stay associated with that log. associated with that log.
Hierarchically structured names encode groupings of names within the
name string, starting from the left so that they work well with
instance-level, view-based access control [RFC2575], for example:
ops ops-admin ops-oper ops-oper-senior ops-oper-junior
Network security managers designing such a naming policy SHOULD use
punctuation (as in the example) to avoid the problem of a lower level
name inadvertently running together with the next higher level name.
A managed system with fewer resources MAY disallow the creation of named A managed system with fewer resources MAY disallow the creation of named
logs, providing only the default, null-named log. Such a log has no logs, providing only the default, null-named log. Such a log has no
implicit security credentials for Notification object access control and implicit security credentials for Notification object access control and
Notifications are put into it with no further checking. Notifications are put into it with no further checking.
When putting locally-generated Notifications into a named log, the When putting locally-generated Notifications into a named log, the
managed system MUST use the security credentials associated with that managed system MUST use the security credentials associated with that
log and MUST apply the same access control rules as described for a log and MUST apply the same access control rules as described for a
Notification Originator in [RFC2573]. Notification Originator in [RFC2573].
skipping to change at page 8, line 15 skipping to change at page 8, line 15
4. Definitions 4. Definitions
NOTIFICATION-LOG-MIB DEFINITIONS ::= BEGIN NOTIFICATION-LOG-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Unsigned32, Integer32, Unsigned32,
TimeTicks, Counter32, Counter64, TimeTicks, Counter32, Counter64,
IpAddress, Opaque, mib-2 FROM SNMPv2-SMI IpAddress, Opaque, mib-2 FROM SNMPv2-SMI
TimeStamp, DateAndTime, TimeStamp, DateAndTime,
StorageType, RowStatus FROM SNMPv2-TC StorageType, RowStatus,
TAddress, TDomain FROM SNMPv2-TC
SnmpAdminString, SnmpEngineID FROM SNMP-FRAMEWORK-MIB SnmpAdminString, SnmpEngineID FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
notificationLogMIB MODULE-IDENTITY notificationLogMIB MODULE-IDENTITY
LAST-UPDATED "200003100000Z" -- 10 March 2000 LAST-UPDATED "200010120000Z" -- 12 October 2000
ORGANIZATION "IETF Distributed Management Working Group" ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO "Ramanathan Kavasseri CONTACT-INFO "Ramanathan Kavasseri
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose CA 95134-1706. San Jose CA 95134-1706.
Phone: +1 408 527 2446 Phone: +1 408 527 2446
Email: ramk@cisco.com" Email: ramk@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for logging SNMP Notifications, that is, Traps "The MIB module for logging SNMP Notifications, that is, Traps
and Informs." and Informs."
-- Revision History -- Revision History
REVISION "200003100000Z" -- 10 March 2000 REVISION "200010120000Z" -- 12 October 2000
DESCRIPTION "Updated the DESCRIPTION of nlmLogTable,
nlmLogContextEngineID and nlmLogContextName."
REVISION "200002040000Z" -- 4 February 2000
DESCRIPTION "Updated the DESCRIPTION of nlmConfigGlobalEntryLimit
and nlmLogContextEngineID."
REVISION "9910220000Z" -- 22 October 1999
DESCRIPTION "This is the initial version of this MIB. DESCRIPTION "This is the initial version of this MIB.
Published as RFC xxxxx" Published as RFC xxxx"
::= { mib-2 xx } -- final assignment by IANA at publication time ::= { mib-2 xx } -- final assignment by IANA at publication time
notificationLogMIBObjects OBJECT IDENTIFIER ::= { notificationLogMIB 1 } notificationLogMIBObjects OBJECT IDENTIFIER ::= { notificationLogMIB 1 }
nlmConfig OBJECT IDENTIFIER ::= { notificationLogMIBObjects 1 } nlmConfig OBJECT IDENTIFIER ::= { notificationLogMIBObjects 1 }
nlmStats OBJECT IDENTIFIER ::= { notificationLogMIBObjects 2 } nlmStats OBJECT IDENTIFIER ::= { notificationLogMIBObjects 2 }
nlmLog OBJECT IDENTIFIER ::= { notificationLogMIBObjects 3 } nlmLog OBJECT IDENTIFIER ::= { notificationLogMIBObjects 3 }
-- --
-- Configuration Section -- Configuration Section
-- --
nlmConfigGlobalEntryLimit OBJECT-TYPE nlmConfigGlobalEntryLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of notification entries that may be held "The maximum number of notification entries that may be held
in nlmLogTable for all nlmLogNames added together. A particular in nlmLogTable for all nlmLogNames added together. A particular
setting does not guarantee that much data can be held. setting does not guarantee that much data can be held.
If an application changes the limit while there are If an application changes the limit while there are
skipping to change at page 16, line 9 skipping to change at page 16, line 6
entry in that log SHOULD be removed to make room for the new one. entry in that log SHOULD be removed to make room for the new one.
Before the managed system puts a locally-generated Notification Before the managed system puts a locally-generated Notification
into a non-null-named log it assures that the creator of the log into a non-null-named log it assures that the creator of the log
has access to the information in the Notification. If not it has access to the information in the Notification. If not it
does not log that Notification in that log." does not log that Notification in that log."
INDEX { nlmLogName, nlmLogIndex } INDEX { nlmLogName, nlmLogIndex }
::= { nlmLogTable 1 } ::= { nlmLogTable 1 }
NlmLogEntry ::= SEQUENCE { NlmLogEntry ::= SEQUENCE {
nlmLogIndex Unsigned32, nlmLogIndex Unsigned32,
nlmLogTime TimeStamp, nlmLogTime TimeStamp,
nlmLogDateAndTime DateAndTime, nlmLogDateAndTime DateAndTime,
nlmLogEngineID SnmpEngineID, nlmLogEngineID SnmpEngineID,
nlmLogEngineAddress IpAddress, nlmLogEngineTAddress TAddress,
nlmLogContextEngineID SnmpEngineID, nlmLogEngineTDomain TDomain,
nlmLogContextName SnmpAdminString, nlmLogContextEngineID SnmpEngineID,
nlmLogNotificationID OBJECT IDENTIFIER nlmLogContextName SnmpAdminString,
nlmLogNotificationID OBJECT IDENTIFIER
} }
nlmLogIndex OBJECT-TYPE nlmLogIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A monotonically increasing integer for the sole purpose of "A monotonically increasing integer for the sole purpose of
indexing entries within the named log. When it reaches the indexing entries within the named log. When it reaches the
maximum value, an extremely unlikely event, the agent wraps the maximum value, an extremely unlikely event, the agent wraps the
skipping to change at page 17, line 14 skipping to change at page 17, line 10
nlmLogEngineID OBJECT-TYPE nlmLogEngineID OBJECT-TYPE
SYNTAX SnmpEngineID SYNTAX SnmpEngineID
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identification of the SNMP engine at which the Notification "The identification of the SNMP engine at which the Notification
originated. originated.
If the log can contain Notifications from only one engine If the log can contain Notifications from only one engine
or the Trap is in SNMPv1 format, this object is not or the Trap is in SNMPv1 format, this object is a zero-length
instantiated." string."
::= { nlmLogEntry 4 } ::= { nlmLogEntry 4 }
nlmLogEngineAddress OBJECT-TYPE nlmLogEngineTAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX TAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP Address of the SNMP engine from which the Notification "The transport service address of the SNMP engine from which the
was received. This is used to identify the source of an SNMPv1 Notification was received, formatted according to the corresponding
trap, since an nlmLogEngineId cannot be extracted from the value of nlmLogEngineTDomain. This is used to identify the source
SNMPv1 trap pdu. of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
from the SNMPv1 trap pdu.
This object MUST always be instantiated, even if the log This object MUST always be instantiated, even if the log
can contain Notifications from only one engine. can contain Notifications from only one engine.
Please be aware that the nlmLogEngineAddress may not uniquely Please be aware that the nlmLogEngineTAddress may not uniquely
identify the SNMP engine from which the Notification was received. identify the SNMP engine from which the Notification was received.
For example, if an SNMP engine uses DHCP or NAT to obtain For example, if an SNMP engine uses DHCP or NAT to obtain
ip addresses, the address it uses may be shared with other ip addresses, the address it uses may be shared with other
network devices, and hence will not uniquely identify the network devices, and hence will not uniquely identify the
SNMP engine." SNMP engine."
::= { nlmLogEntry 5 } ::= { nlmLogEntry 5 }
nlmLogEngineTDomain OBJECT-TYPE
SYNTAX TDomain
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the kind of transport service by which a Notification was
received from an SNMP engine. nlmLogEngineTAddress contains the
transport service address of the SNMP engine from which this
Notification was received.
Possible values for this object are presently found in the
Transport Mappings for SNMPv2 document (RFC 1906 [8])."
::= { nlmLogEntry 6 }
nlmLogContextEngineID OBJECT-TYPE nlmLogContextEngineID OBJECT-TYPE
SYNTAX SnmpEngineID SYNTAX SnmpEngineID
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the Notification was received in a protocol which has a "If the Notification was received in a protocol which has a
contextEngineID element like SNMPv3, this object has that value. contextEngineID element like SNMPv3, this object has that value.
Otherwise its value is a zero-length string." Otherwise its value is a zero-length string."
::= { nlmLogEntry 6 } ::= { nlmLogEntry 7 }
nlmLogContextName OBJECT-TYPE nlmLogContextName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the SNMP MIB context from which the Notification came. "The name of the SNMP MIB context from which the Notification came.
For SNMPv1 Traps this is the community string from the Trap." For SNMPv1 Traps this is the community string from the Trap."
::= { nlmLogEntry 7 } ::= { nlmLogEntry 8 }
nlmLogNotificationID OBJECT-TYPE nlmLogNotificationID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NOTIFICATION-TYPE object identifer of the Notification that "The NOTIFICATION-TYPE object identifer of the Notification that
occurred." occurred."
::= { nlmLogEntry 8 } ::= { nlmLogEntry 9 }
-- --
-- Log Variable Table -- Log Variable Table
-- --
nlmLogVariableTable OBJECT-TYPE nlmLogVariableTable OBJECT-TYPE
SYNTAX SEQUENCE OF NlmLogVariableEntry SYNTAX SEQUENCE OF NlmLogVariableEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 18, line 46 skipping to change at page 19, line 12
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Notification log entry variable. "A Notification log entry variable.
Entries appear in this table when there are variables in Entries appear in this table when there are variables in
the varbind list of a Notification in nlmLogTable." the varbind list of a Notification in nlmLogTable."
INDEX { nlmLogName, nlmLogIndex, nlmLogVariableIndex } INDEX { nlmLogName, nlmLogIndex, nlmLogVariableIndex }
::= { nlmLogVariableTable 1 } ::= { nlmLogVariableTable 1 }
NlmLogVariableEntry ::= SEQUENCE { NlmLogVariableEntry ::= SEQUENCE {
nlmLogVariableIndex Unsigned32, nlmLogVariableIndex Unsigned32,
nlmLogVariableID OBJECT IDENTIFIER, nlmLogVariableID OBJECT IDENTIFIER,
nlmLogVariableValueType INTEGER, nlmLogVariableValueType INTEGER,
nlmLogVariableCounter32Val Counter32, nlmLogVariableCounter32Val Counter32,
nlmLogVariableUnsigned32Val Unsigned32, nlmLogVariableUnsigned32Val Unsigned32,
nlmLogVariableTimeTicksVal TimeTicks, nlmLogVariableTimeTicksVal TimeTicks,
nlmLogVariableInteger32Val Integer32, nlmLogVariableInteger32Val Integer32,
nlmLogVariableOctetStringVal OCTET STRING, nlmLogVariableOctetStringVal OCTET STRING,
nlmLogVariableIpAddressVal IpAddress, nlmLogVariableIpAddressVal IpAddress,
nlmLogVariableOidVal OBJECT IDENTIFIER, nlmLogVariableOidVal OBJECT IDENTIFIER,
nlmLogVariableCounter64Val Counter64, nlmLogVariableCounter64Val Counter64,
nlmLogVariableOpaqueVal Opaque nlmLogVariableOpaqueVal Opaque
} }
nlmLogVariableIndex OBJECT-TYPE nlmLogVariableIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A monotonically increasing integer, starting at 1 for a given "A monotonically increasing integer, starting at 1 for a given
nlmLogIndex, for indexing variables within the logged nlmLogIndex, for indexing variables within the logged
Notification." Notification."
skipping to change at page 20, line 44 skipping to change at page 21, line 10
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value when nlmLogVariableType is 'octetString'." "The value when nlmLogVariableType is 'octetString'."
::= { nlmLogVariableEntry 8 } ::= { nlmLogVariableEntry 8 }
nlmLogVariableIpAddressVal OBJECT-TYPE nlmLogVariableIpAddressVal OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value when nlmLogVariableType is 'ipAddress'." "The value when nlmLogVariableType is 'ipAddress'.
Although this seems to be unfriendly for IPv6, we
have to recognize that there are a number of older
MIBs that do contain an IPv4 format address, known
as IpAddress.
IPv6 addresses are represented using TAddress or
InetAddress, and so the underlying datatype is
OCTET STRING, and their value would be stored in
the nlmLogVariableOctetStringVal column."
::= { nlmLogVariableEntry 9 } ::= { nlmLogVariableEntry 9 }
nlmLogVariableOidVal OBJECT-TYPE nlmLogVariableOidVal OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value when nlmLogVariableType is 'objectId'." "The value when nlmLogVariableType is 'objectId'."
::= { nlmLogVariableEntry 10 } ::= { nlmLogVariableEntry 10 }
skipping to change at page 23, line 25 skipping to change at page 23, line 43
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification log statistics." "Notification log statistics."
::= { notificationLogMIBGroups 2 } ::= { notificationLogMIBGroups 2 }
notificationLogLogGroup OBJECT-GROUP notificationLogLogGroup OBJECT-GROUP
OBJECTS { OBJECTS {
nlmLogTime, nlmLogTime,
nlmLogEngineID, nlmLogEngineID,
nlmLogEngineAddress, nlmLogEngineTAddress,
nlmLogEngineTDomain,
nlmLogContextEngineID, nlmLogContextEngineID,
nlmLogContextName, nlmLogContextName,
nlmLogNotificationID, nlmLogNotificationID,
nlmLogVariableID, nlmLogVariableID,
nlmLogVariableValueType, nlmLogVariableValueType,
nlmLogVariableCounter32Val, nlmLogVariableCounter32Val,
nlmLogVariableUnsigned32Val, nlmLogVariableUnsigned32Val,
nlmLogVariableTimeTicksVal, nlmLogVariableTimeTicksVal,
nlmLogVariableInteger32Val, nlmLogVariableInteger32Val,
nlmLogVariableOctetStringVal, nlmLogVariableOctetStringVal,
nlmLogVariableIpAddressVal, nlmLogVariableIpAddressVal,
nlmLogVariableOidVal, nlmLogVariableOidVal,
nlmLogVariableCounter64Val, nlmLogVariableCounter64Val,
skipping to change at page 24, line 8 skipping to change at page 24, line 27
DESCRIPTION DESCRIPTION
"Notification log data." "Notification log data."
::= { notificationLogMIBGroups 3 } ::= { notificationLogMIBGroups 3 }
notificationLogDateGroup OBJECT-GROUP notificationLogDateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
nlmLogDateAndTime nlmLogDateAndTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Conditionally mandatory notification log data." "Conditionally mandatory notification log data.
This group is mandatory on systems that keep wall
clock date and time and should not be implemented
on systems that do not have a wall clock date."
::= { notificationLogMIBGroups 4 } ::= { notificationLogMIBGroups 4 }
END END
5. Intellectual Property 5. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any might not be available; neither does it represent that it has made any
skipping to change at page 27, line 21 skipping to change at page 28, line 5
RFC 2573, April 1999 RFC 2573, April 1999
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999 Management Protocol (SNMP)", RFC 2575, April 1999
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network "Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999 Management Framework", RFC 2570, April 1999
[RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Coexistence between Version 1 and version 2 of the
Internet-standard Network Management Framework", RFC 1903,
January 1996.
7. Security Considerations 7. Security Considerations
Security issues are discussed in Section 3.1.2. Security issues are discussed in Section 3.1.2.
8. Author's Address 8. Author's Address
Bob Stewart Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
skipping to change at page 29, line 7 skipping to change at page 29, line 7
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
U.S.A. U.S.A.
Phone: +1 408 527 2446 Phone: +1 408 527 2446
Email: ramk@cisco.com Email: ramk@cisco.com
9. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). 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 30, line 17 skipping to change at page 30, line 17
1 Abstract ........................................................ 2 1 Abstract ........................................................ 2
2 The SNMP Management Framework ................................... 2 2 The SNMP Management Framework ................................... 2
3 Overview ........................................................ 3 3 Overview ........................................................ 3
3.1 Environment ................................................... 3 3.1 Environment ................................................... 3
3.1.1 SNMP Engines and Contexts ................................... 4 3.1.1 SNMP Engines and Contexts ................................... 4
3.1.2 Security .................................................... 4 3.1.2 Security .................................................... 4
3.2 Structure ..................................................... 5 3.2 Structure ..................................................... 5
3.2.1 Configuration ............................................... 6 3.2.1 Configuration ............................................... 6
3.2.2 Statistics .................................................. 6 3.2.2 Statistics .................................................. 6
3.2.3 Log ......................................................... 6 3.2.3 Log ......................................................... 6
3.3 Example ....................................................... 7 3.3 Example ....................................................... 6
4 Definitions ..................................................... 8 4 Definitions ..................................................... 8
5 Intellectual Property ........................................... 25 5 Intellectual Property ........................................... 25
6 References ...................................................... 26 6 References ...................................................... 26
7 Security Considerations ......................................... 28 7 Security Considerations ......................................... 28
8 Author's Address ................................................ 28 8 Author's Address ................................................ 28
9 Full Copyright Statement ........................................ 29 9 Full Copyright Statement ........................................ 29
 End of changes. 29 change blocks. 
82 lines changed or deleted 89 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/