< draft-ietf-snmpv2-intro-ds-05.txt		draft-ietf-snmpv2-intro-ds-06.txt >
	Internet Draft Introduction to SNMPv2 October 1995		Internet Draft Introduction to SNMPv2 October 1995
	Introduction to Version 2 of the		Introduction to Version 2 of the
	Internet-standard Network Management Framework		Internet-standard Network Management Framework
	11 October 1995 |		18 October 1995 |
	draft-ietf-snmpv2-intro-ds-05.txt |		draft-ietf-snmpv2-intro-ds-06.txt |
	Keith McCloghrie		Keith McCloghrie
	Editor +		Editor
	Cisco Systems, Inc.		Cisco Systems, Inc.
	kzm@cisco.com		kzm@cisco.com
	Status of this Memo -		Status of this Memo
	This document is an Internet-Draft. Internet-Drafts are working		This document is an Internet-Draft. 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 learn 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 the Internet- Drafts Shadow
	Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),		Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),
	ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).		ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
	1. Introduction		1. Introduction
	The purpose of this document is to provide an overview of version 2 of		The purpose of this document is to provide an overview of version 2 of
	the Internet-standard Network Management Framework, termed the SNMP		the Internet-standard Network Management Framework, termed the SNMP
	version 2 framework (SNMPv2). The SNMPv2 framework is fully described +		version 2 framework (SNMPv2). The SNMPv2 framework is fully described
	in [6,7,8,9,10,11]. +		in [6,7,8,9,10,11]. This framework is derived from the original
	This framework is derived from the original Internet-standard Network		Internet-standard Network Management Framework (SNMPv1), which consists
	Management Framework (SNMPv1), which consists of these three documents:		of these three documents:
	RFC 1155 [1] which defines the Structure of Management Information		RFC 1155 [1] which defines the Structure of Management Information
	(SMI), the mechanisms used for describing and naming objects for		(SMI), the mechanisms used for describing and naming objects for
	the purpose of management.		the purpose of management.
	RFC 1212 [2] which defines a more concise description mechanism,		RFC 1212 [2] which defines a more concise description mechanism,
	which is wholly consistent with the SMI.		which is wholly consistent with the SMI.
	RFC 1157 [3] which defines the Simple Network Management Protocol		RFC 1157 [3] which defines the Simple Network Management Protocol
	(SNMP), the protocol used for network access to managed objects.		(SNMP), the protocol used for network access to managed objects.
	skipping to change at page 4, line 27 ¶		skipping to change at page 4, line 27 ¶
	of the rules that define their primitive type. However, textual		of the rules that define their primitive type. However, textual
	conventions often have special semantics associated with them. As such,		conventions often have special semantics associated with them. As such,
	an ASN.1 macro, TEXTUAL-CONVENTION, is used to concisely convey the		an ASN.1 macro, TEXTUAL-CONVENTION, is used to concisely convey the
	syntax and semantics of a textual convention.		syntax and semantics of a textual convention.
	2.3. Protocol Operations		2.3. Protocol Operations
	The management protocol provides for the exchange of messages which		The management protocol provides for the exchange of messages which
	convey management information between the agents and the management		convey management information between the agents and the management
	stations. The form of these messages is a message "wrapper" which		stations. The form of these messages is a message "wrapper" which
	encapsulates a Protocol Data Unit (PDU). -		encapsulates a Protocol Data Unit (PDU).
	It is the purpose of the Protocol Operations for SNMPv2 document [8] to		It is the purpose of the Protocol Operations for SNMPv2 document [8] to
	define the operations of the protocol with respect to the sending and		define the operations of the protocol with respect to the sending and
	receiving of the PDUs.		receiving of the PDUs.
	2.4. Transport Mappings		2.4. Transport Mappings
	The management protocol, version 2 of the Simple Network Management		The management protocol, version 2 of the Simple Network Management
	Protocol, may be used over a variety of protocol suites. It is the		Protocol, may be used over a variety of protocol suites. It is the
	purpose of the Transport Mappings for SNMPv2 document [9] to define how		purpose of the Transport Mappings for SNMPv2 document [9] to define how
	skipping to change at page 5, line 35 ¶		skipping to change at page 5, line 35 ¶
	CAPABILITIES, is used to concisely convey such capabilities.		CAPABILITIES, is used to concisely convey such capabilities.
	Finally, collections of related objects are grouped together to form a		Finally, collections of related objects are grouped together to form a
	unit of conformance. An ASN.1 macro, OBJECT-GROUP, is used to concisely		unit of conformance. An ASN.1 macro, OBJECT-GROUP, is used to concisely
	convey the syntax and semantics of a group.		convey the syntax and semantics of a group.
	2.7. Administrative Framework		2.7. Administrative Framework
	It is the purpose of an administrative framework to define an		It is the purpose of an administrative framework to define an
	infrastructure through which effective management can be realized in a		infrastructure through which effective management can be realized in a
	variety of configurations and environments. Specified as a part of, or |		variety of configurations and environments. Specified as a part of, or
	as extensions of, an administrative framework are security mechanisms |		as extensions of, an administrative framework are security mechanisms
	used to achieve an administratively-defined level of security for		used to achieve an administratively-defined level of security for
	protocol interactions.		protocol interactions.
	The administrative framework for SNMPv2 is the same framework as was |		The administrative framework for SNMPv2 identified in this document is |
	defined for SNMPv1 [3]. |		the same framework as was defined for SNMPv1 [3]. |
	This administrative framework associates each message with a "community"		This administrative framework associates each message with a "community" |
	as defined in [3]. Specifically, Section 3.2.5 of [3] defines the +		as defined in [3]. Use of this administrative framework with SNMP |
	concept of a community, and Section 4.1 of [3] defines the Elements of +		Version 2 is commonly known as "Community-based SNMPv2 (SNMPv2C)." |
	Procedure for generating and receiving messages. The following updates +
	apply: +
	(1) The types of access defined in Section 3.2.5 of [3] are updated by +
	[6]. +
	(2) The Elements of Procedure defined in Section 4.1 of [3] are updated +		Specifically, Section 3.2.5 of [3] defines the concept of a community,
	with the additional requirement of incrementing the relevant +		and Section 4.1 of [3] defines the Elements of Procedure for generating
	statistics counter as defined in [10]. +		and receiving messages. The following updates apply:
	(3) The requirement in the Elements of Procedure in Section 4.1 of [3] +		(1) The types of access defined in Section 3.2.5 of [3] are updated by
	that the "the source transport address that a response message is +		[6].
	sent from shall be identical to the destination transport address +
	that the original request message was sent to" is deleted, i.e., +
	the source transport address of a response message can be any +
	transport address belonging to the agent. +
	The form of a message is also taken from [3], with the exception that a |		(2) The Elements of Procedure defined in Section 4.1 of [3] are updated
	new version number is used in the message "wrapper". Use of a new |		with the additional requirement of incrementing the relevant
	version number is necessary because of SNMPv2's new PDU types [8], error |		statistics counter as defined in [10].
	codes [8], etc. With this one change, the wrapper becomes: |
			(3) The requirement in the Elements of Procedure in Section 4.1 of [3]
			that the "the source transport address that a response message is
			sent from shall be identical to the destination transport address
			that the original request message was sent to" is deleted, i.e.,
			the source transport address of a response message can be any
			transport address belonging to the agent.
			The form of a message is also taken from [3], with the exception that a
			new version number is used in the message "wrapper". Use of a new
			version number is necessary because of SNMPv2's new PDU types [8], error
			codes [8], etc. With this one change, the wrapper becomes:
	COMMUNITY-BASED-SNMPv2 DEFINITIONS ::= BEGIN		COMMUNITY-BASED-SNMPv2 DEFINITIONS ::= BEGIN
	-- top-level message		-- top-level message
	Message ::=		Message ::=
	SEQUENCE {		SEQUENCE {
	version		version
	INTEGER {		INTEGER {
	version(1) -- modified from RFC 1157		version(1) -- modified from RFC 1157
	},		},
	community -- community name		community -- community name
	OCTET STRING,		OCTET STRING,
	data -- PDUs as defined in [8] |		data -- PDUs as defined in [8]
	ANY |		ANY
	}		}
	}		}
	END		END
	Note that with this administrative framework, the +		Note that with this administrative framework, the
	'authorizationError(16)' value defined for the error-status component of +		'authorizationError(16)' value defined for the error-status component of
	an SNMPv2 PDU [8] is unused. It may, however, be used with future +		an SNMPv2 PDU [8] is unused. It may, however, be used with future
	administrative frameworks. +		administrative frameworks.
	3. Acknowledgements		3. Acknowledgements
	This document is the result of significant work by the four major		This document is the result of significant work by the four major
	contributors:		contributors:
	Jeffrey Case (SNMP Research, case@snmp.com)		Jeffrey Case (SNMP Research, case@snmp.com)
	Keith McCloghrie (Cisco Systems, kzm@cisco.com)		Keith McCloghrie (Cisco Systems, kzm@cisco.com)
	Marshall Rose (Dover Beach Consulting, mrose@dbc.mtview.ca.us)		Marshall Rose (Dover Beach Consulting, mrose@dbc.mtview.ca.us)
	Steven Waldbusser (International Network Services, stevew@uni.ins.com)		Steven Waldbusser (International Network Services, stevew@uni.ins.com)
	skipping to change at page 8, line 19 ¶		skipping to change at page 8, line 19 ¶
	1155, May 1990.		1155, May 1990.
	[2] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16,		[2] Rose, M., and McCloghrie, K., "Concise MIB Definitions", STD 16,
	RFC 1212, March 1991.		RFC 1212, March 1991.
	[3] Case, J., Fedor, M., Schoffstall, M., Davin, J., "Simple Network		[3] Case, J., Fedor, M., Schoffstall, M., Davin, J., "Simple Network
	Management Protocol", STD 15, RFC 1157, SNMP Research, Performance		Management Protocol", STD 15, RFC 1157, SNMP Research, Performance
	Systems International, MIT Laboratory for Computer Science, May		Systems International, MIT Laboratory for Computer Science, May
	1990.		1990.
	[4] McCloghrie, K., Editor, |		[4] McCloghrie, K., Editor, "Coexistence between Version 1 and Version
	"Coexistence between Version 1 and Version 2 of the Internet-		2 of the Internet-standard Network Management Framework", Internet
	standard Network Management Framework", Internet Draft, Cisco |		Draft, Cisco Systems, September 1995.
	Systems, September 1995. |
	[5] Information processing systems - Open Systems Interconnection -		[5] 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).
	[6] McCloghrie, K., Editor, |		[6] McCloghrie, K., Editor, "Structure of Management Information for
	"Structure of Management Information for Version 2 of the Simple		Version 2 of the Simple Network Management Protocol (SNMPv2)",
	Network Management Protocol (SNMPv2)", Internet Draft, Cisco |		Internet Draft, Cisco Systems, September 1995.
	Systems, September 1995. |
	[7] McCloghrie, K., Editor, |		[7] McCloghrie, K., Editor, "Textual Conventions for Version 2 of the
	"Textual Conventions for Version 2 of the Simple Network Management		Simple Network Management Protocol (SNMPv2)", Internet Draft, Cisco
	Protocol (SNMPv2)", Internet Draft, Cisco Systems, September 1995. |		Systems, September 1995.
	[8] McCloghrie, K., Editor, |		[8] McCloghrie, K., Editor, "Protocol Operations for Version 2 of the
	"Protocol Operations for Version 2 of the Simple Network Management		Simple Network Management Protocol (SNMPv2)", Internet Draft, Cisco
	Protocol (SNMPv2)", Internet Draft, Cisco Systems, September 1995. |		Systems, September 1995.
	[9] McCloghrie, K., Editor, |		[9] McCloghrie, K., Editor, "Transport Mappings for Version 2 of the
	"Transport Mappings for Version 2 of the Simple Network Management		Simple Network Management Protocol (SNMPv2)", Internet Draft, Cisco
	Protocol (SNMPv2)", Internet Draft, Cisco Systems, September 1995. |		Systems, September 1995.
	[10] McCloghrie, K., Editor, |		[10] McCloghrie, K., Editor, "Management Information Base for Version 2
	"Management Information Base for Version 2 of the Simple Network		of the Simple Network Management Protocol (SNMPv2)", Internet
	Management Protocol (SNMPv2)", Internet Draft, Cisco Systems, |		Draft, Cisco Systems, September 1995.
	September 1995. |
	[11] McCloghrie, K., Editor, |		[11] McCloghrie, K., Editor, "Conformance Statements for Version 2 of
	"Conformance Statements for Version 2 of the Simple Network		the Simple Network Management Protocol (SNMPv2)", Internet Draft,
	Management Protocol (SNMPv2)", Internet Draft, Cisco Systems, |		Cisco Systems, September 1995.
	September 1995. |
	5. Security Considerations		5. Security Considerations
	Security issues are not discussed in this memo.		Security issues are not discussed in this memo.
	6. Editor's Address		6. Editor's Address
	Keith McCloghrie -		Keith McCloghrie
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 West Tasman Drive		170 West Tasman Drive
	San Jose, CA 95134-1706		San Jose, CA 95134-1706
	US		US
	Phone: +1 408 526 5260		Phone: +1 408 526 5260
	Email: kzm@cisco.com		Email: kzm@cisco.com
	Table of Contents -		Table of Contents
	1 Introduction .................................................... 2		1 Introduction .................................................... 2
	2 Components of the SNMPv2 Framework .............................. 3		2 Components of the SNMPv2 Framework .............................. 3
	2.1 Structure of Management Information ........................... 3		2.1 Structure of Management Information ........................... 3
	2.2 Textual Conventions ........................................... 4		2.2 Textual Conventions ........................................... 4
	2.3 Protocol Operations ........................................... 4		2.3 Protocol Operations ........................................... 4
	2.4 Transport Mappings ............................................ 4		2.4 Transport Mappings ............................................ 4
	2.5 Protocol Instrumentation ...................................... 5		2.5 Protocol Instrumentation ...................................... 5
	2.6 Conformance Statements ........................................ 5		2.6 Conformance Statements ........................................ 5
	2.7 Administrative Framework ...................................... 5		2.7 Administrative Framework ...................................... 5
End of changes. 22 change blocks.
	66 lines changed or deleted		66 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/