< draft-mcdonald-svrloc-mib-03.txt		draft-mcdonald-svrloc-mib-04.txt >
	Network Working Group Mark Bakke		Network Working Group Mark Bakke
	INTERNET DRAFT Cisco		INTERNET DRAFT Cisco
	<draft-mcdonald-svrloc-mib-03.txt> Ira McDonald		<draft-mcdonald-svrloc-mib-04.txt> Ira McDonald
	Updates: RFC 2608 High North		[Target Category: Standards Track] High North
	[Target Category: Standards Track] 1 March 2002		Expires: 27 August 2003 27 February 2003
	Expires: 1 September 2002
	Definitions of Managed Objects for		Definitions of Managed Objects for
	Service Location Protocol (SLP MIB)		Service Location Protocol (SLP MIB)
			<draft-mcdonald-svrloc-mib-04.txt>
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Copyright (C) The Internet Society (2003). All Rights Reserved.
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC 2026. Internet-Drafts are		all provisions of Section 10 of RFC 2026. Internet-Drafts are
	working documents of the Internet Engineering Task Force (IETF), its		working documents of the Internet Engineering Task Force (IETF), its
	areas, and its working groups. Note that other groups may also		areas, and its working groups. Note that other groups may also
	distribute working documents as Internet-Drafts.		distribute working 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
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	To view the list of Internet-Draft Shadow Directories, see		To view the list of Internet-Draft Shadow Directories, see
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Abstract		Abstract
	This memo defines a portion of the Management Information Base (MIB)		This memo defines a portion of the Management Information Base (MIB)
	for use with network management protocols in the Internet community.		for use with network management protocols in the Internet community.
	In particular, it defines as set of managed objects that support		In particular, it defines as set of managed objects that support
	monitoring (but not configuration) of Service Location Protocol		monitoring (but not configuration) of Service Location Protocol
	Version 2 (SLPv2) [RFC2608] [RFC3111] directory agents (DAs), service		Version 2 (SLPv2, RFC 2608, RFC 3111, RFC 3224) directory agents
	agents (SAs), and user agents (UAs).		(DAs), service agents (SAs), and user agents (UAs).
	Table of Contents		Table of Contents
	1. Introduction ............................................... 3		1. Introduction ............................................... 3
	2. SNMP Network Management Framework .......................... 3		2. The Internet-Standard Management Framework ................. 3
	3. Design Requirements for SLP MIB ............................ 4		3. Design Requirements for SLP MIB ............................ 4
	4. Overview of SLP MIB ........................................ 5		4. Overview of SLP MIB ........................................ 4
	4.1. Conformance Terminology ................................ 5		4.1. Conformance Terminology ................................ 4
	4.2. SLP Terminology ........................................ 5		4.2. SLP Terminology ........................................ 5
	4.3. Abstract Model of SLP MIB .............................. 6		4.3. Abstract Model of SLP MIB .............................. 5
	4.4. Relationship to SNMP Architecture MIB (RFC 2571) ....... 7		4.4. Relationship to SNMP Framework MIB (RFC 3411) .......... 6
	4.5. Relationship to Host Resources MIB (RFC 2790) .......... 7		4.5. Relationship to Host Resources MIB (RFC 2790) .......... 6
	5. Definition of SLP MIB ...................................... 8		5. Definition of SLP MIB ...................................... 7
	5.1. Textual Conventions .................................... 9		5.1. Textual Conventions .................................... 8
	5.2. Agent Group (Mandatory) Objects ........................ 10		5.2. Agent Group (Mandatory) Objects ........................ 9
	5.3. Scope Group (Mandatory) Objects ........................ 13		5.3. Scope Group (Mandatory) Objects ........................ 12
	5.4. Address Group (Optional) Objects ....................... 14		5.4. Address Group (Optional) Objects ....................... 13
	5.5. Attribute Group (Optional) Objects ..................... 16		5.5. Attribute Group (Optional) Objects ..................... 15
	5.6. Conformance Statements ................................. 18		5.6. Conformance Statements ................................. 17
	5.7. Conformance Groups ..................................... 18		5.7. Conformance Groups ..................................... 17
	6. IANA Considerations ........................................ 20		6. IANA Considerations ........................................ 19
	7. Internationalization Considerations ........................ 20		7. Intellectual Property ...................................... 19
	8. Security Considerations .................................... 20		8. Internationalization Considerations ........................ 19
	9. Acknowledgements ........................................... 21		9. Security Considerations .................................... 20
	10. Normative References ...................................... 21		10. Acknowledgements .......................................... 21
	11. Informative References .................................... 22		11. Normative References ...................................... 21
	12. Authors' Addresses ........................................ 23		12. Informative References .................................... 22
	13. Full Copyright Statement .................................. 24		13. Authors Addresses ......................................... 22
	14. Appendix X - Change Log ................................... 25		14. Full Copyright Statement .................................. 23
			15. Appendix X - Change Log ................................... 24
	1. Introduction		1. Introduction
	This memo defines a portion of the Management Information Base (MIB)
	for use with network management protocols in the Internet community.
	In particular, it defines as set of managed objects that support
	monitoring (but not configuration) of Service Location Protocol
	Version 2 (SLPv2) [RFC2608] [RFC3111] directory agents (DAs), service
	agents (SAs), and user agents (UAs).
	The SLP MIB supports minimal passive monitoring of SLPv2 agents for		The SLP MIB supports minimal passive monitoring of SLPv2 agents for
	network management purposes. The SLP MIB also supports (optional)		network management purposes. The SLP MIB also supports (optional)
	passive monitoring of remote SLPv2 DA and SLPv2 SA network addresses		passive monitoring of configured or discovered SLPv2 DA/SA network
	and local SLPv2 DA and SLPv2 SA agent attributes. This document is		addresses and SLPv2 DA/SA attributes.
	laid out as follows:
	o Section 2 briefly describes the SNMP network management
	framework.
	o Section 3 enumerates design requirements for the SLP MIB.
	o Section 4 provides an overview of the SLP MIB, including
	conformance terminology and SLP-specific terminology.
	o Section 5 specifies the SLP MIB in SMIv2 [RFC2578], including the
	conformance requirements for SNMP Command Responders that claim
	conformance to this document.
	o Sections 6, 7, and 8 specify IANA, internationalization, and
	security considerations.
	o Sections 9, 10, 11, 12, and 13 list acknowledgements, normative		This document is structured as follows:
	references, informative references, authors' addresses, and full
	IETF copyright statement.
	2. SNMP Network Management Framework		- Section 2 briefly describes the SNMP network management framework.
	The SNMP Management Framework presently consists of five major		- Section 3 enumerates design requirements for the SLP MIB.
	components:
	o An overall architecture, described in RFC 2571 [RFC2571].		- Section 4 provides an overview of the SLP MIB, including
			conformance terminology and SLP-specific terminology.
	o Mechanisms for describing and naming objects and events for the		- Section 5 specifies the SLP MIB in SMIv2 [RFC2578], including the
	purpose of management. The first version of this Structure of		conformance requirements for SNMP Command Responders that claim
	Management Information (SMI) is called SMIv1 and described in		conformance to this document.
	STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
	1215 [RFC1215]. The second version, called SMIv2, is described
	in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
	STD 58, RFC 2580 [RFC2580].
	o Message protocols for transferring management information. The		- Sections 6, 7, 8, and 9 specify IANA, intellectual property,
	first version of the SNMP message protocol is called SNMPv1 and		internationalization, and security considerations.
	described in STD 15, RFC 1157 [RFC1157]. A second version of
	the SNMP message protocol, which is not an Internet standards
	track protocol, is called SNMPv2c and described in RFC 1901
	[RFC1901] and RFC 1906 [RFC1906]. The third version of the
	message protocol is called SNMPv3 and described in RFC 1906
	[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
	o Protocol operations for accessing management information. The		- Sections 10, 11, 12, 13, and 14 list acknowledgements, normative
	first set of protocol operations and associated PDU formats is		references, informative references, authors' addresses, and full
	described in STD 15, RFC 1157 [RFC1157]. A second set of		IETF copyright statement.
	protocol operations and associated PDU formats is described in
	RFC 1905 [RFC1905].
	o A set of fundamental applications described in RFC 2573		2. The Internet-Standard Management Framework
	[RFC2573] and the view-based access control mechanism described
	in RFC 2575 [RFC2575].
	A more detailed introduction to the current SNMP Management Framework		For a detailed overview of the documents that describe the current
	can be found in RFC 2570 [RFC2570].		Internet-Standard Management Framework, please refer to section 7 of
			RFC 3410 [RFC3410].
	Managed objects are accessed via a virtual information store, termed		Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. Objects in the MIB are		the Management Information Base or MIB. MIB objects are generally
	defined using the mechanisms defined in the SMI.		accessed through the Simple Network Management Protocol (SNMP).
			Objects in the MIB are defined using the mechanisms defined in the
	This memo specifies a MIB module that is compliant to the SMIv2. A		Structure of Management Information (SMI). This memo specifies a MIB
	MIB conforming to the SMIv1 can be produced through the appropriate		module that is compliant to the SMIv2, which is described in STD 58,
	translations. The resulting translated MIB must be semantically		RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
	equivalent, except where objects or events are omitted because no		[RFC2580].
	translation is possible (use of Counter64). Some machine readable
	information in SMIv2 will be converted into textual descriptions in
	SMIv1 during the translation process. However, this loss of machine
	readable information is not considered to change the semantics of the
	MIB.
	3. Design Requirements for SLP MIB		3. Design Requirements for SLP MIB
	The SLP MIB design requirements listed below are _not_ conformance		The SLP MIB design requirements listed below are _not_ conformance
	requirements on _implementations_ of the SLP MIB. Therefore the		requirements on _implementations_ of the SLP MIB. Therefore the
	words must, should, and may are used below in lowercase (informative		words must, should, and may are used below in lowercase (informative
	per [RFC2119] conventions).		per [RFC2119] conventions).
	o The SLP MIB must provide an SNMP interface to monitor SLPv2		(1) The SLP MIB must provide an SNMP interface to monitor SLPv2
	[RFC2608] directory agents (DAs), service agents (SAs), and user		[RFC2608] directory agents (DAs), service agents (SAs), and user
	agents (UAs).		agents (UAs).
	o The SLP MIB must be organized so that access can be controlled		(2) The SLP MIB must be organized so that access can be controlled
	effectively by using the User-based Security Model [RFC2574] and		effectively by using the User-based Security Model [RFC2574] and
	the View-based Access Control Model [RFC2575] from the SNMPv3		the View-based Access Control Model [RFC2575] from the SNMPv3
	framework.		framework.
	o The SLP MIB must not compromise native security in SLPv2		(3) The SLP MIB must not compromise native security in SLPv2
	[RFC2608] by exposing private keys or other confidential		[RFC2608] by exposing private keys or other confidential
	information via SNMP.		information via SNMP.
	o The SLP MIB must define a core set of mandatory object groups		(4) The SLP MIB must define a core set of mandatory object groups
	that support minimal passive monitoring requirements.		that support minimal passive monitoring requirements.
	o The SLP MIB must use UTF-8 [2279] for all human-readable text		(5) The SLP MIB must use UTF-8 [2279] for all human-readable text
	strings per [RFC2277] for internationalization support.		strings per [RFC2277] for internationalization support.
	4. Overview of SLP MIB		4. Overview of SLP MIB
	The SLP MIB can be used to monitor SLPv2 [RFC2608] directory agents		The SLP MIB can be used to monitor SLPv2 [RFC2608] directory agents
	(DAs), service agents (SAs), and user agents (UAs). The SLP MIB		(DAs), service agents (SAs), and user agents (UAs). The SLP MIB
	makes no assumptions about the particular system topology of the		makes no assumptions about the particular system topology of the
	managed SLP agents (for example, they may be distributed across		managed SLP agents (for example, they may be distributed across
	several rack-mounted processors in a router).		several rack-mounted processors in a router).
	4.1. Conformance Terminology		4.1. Conformance Terminology
	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
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	4.2. SLP Terminology		4.2. SLP Terminology
	The SLP MIB uses the following definitions from SLPv2 [RFC2608]:		The SLP MIB uses the following definitions from SLPv2 [RFC2608]:
	o "User Agent (UA)"		- "User Agent (UA)"
	A process working on the user's behalf to establish contact with		A process working on the user's behalf to establish contact with
	some service. The UA retrieves service information from the		some service. The UA retrieves service information from the
	Service Agents or Directory Agents.		Service Agents or Directory Agents.
	o "Service Agent (SA)"		- "Service Agent (SA)"
	A process working on the behalf of one or more services to		A process working on the behalf of one or more services to
	advertise the services.		advertise the services.
	o "Directory Agent (DA)"		- "Directory Agent (DA)"
	A process which collects service advertisements. There can only		A process which collects service advertisements. There can only be
	be one DA present per given host.		one DA present per given host.
	o "Scope"		- "Scope"
	A set of services, typically making up a logical administrative		A set of services, typically making up a logical administrative
	group.		group.
	4.3. Abstract Model of SLP MIB		4.3. Abstract Model of SLP MIB
	The Agent group is the principal object group in the abstract model		The Agent group is the principal object group in the abstract model
	defined in the SLP MIB.		defined in the SLP MIB.
	The Scope, Address, and Attribute tables (all subordinate to		The Scope, Address, and Attribute tables (all subordinate to
	"slpAgentTable") each use a high-order index of "slpAgentIndex" for		"slpAgentTable") each use a high-order index of "slpAgentIndex" for
	linkage to the "slpAgentTable".		linkage to the "slpAgentTable".
	The following is a diagram of the abstract model of the SLP MIB.		The following is a diagram of the abstract model of the SLP MIB.
	(Mandatory)		(Mandatory)
	|===========|		|===========|
	| Agent | (One row per local DA, SA, or UA on managed system)		| Agent | (One row per DA, SA, or UA on managed system)
	|===========|		|===========|
	| INDEX { slpAgentIndex }		| INDEX { slpAgentIndex }
	|		|
	|		|
	| (Mandatory)		| (Mandatory)
	| 0..* |===========|		| 0..* |===========|
	|.............| Scope | (One row per local scope value)		|.............| Scope | (One row per scope value)
	| |===========|		| |===========|
	| INDEX { slpAgentIndex,		| INDEX { slpAgentIndex,
	| slpScopeIndex }		| slpScopeIndex }
	|		|
	| (Optional)		| (Optional)
	| 0..* |===========|		| 0..* |===========|
	|.............| Address | (One row per remote DA/SA address)		|.............| Address | (One row per remote DA/SA address)
	| |===========|		| |===========|
	| INDEX { slpAgentIndex,		| INDEX { slpAgentIndex,
	| slpAddressIndex }		| slpAddressIndex }
	|		|
	| (Optional)		| (Optional)
	| 0..* |===========|		| 0..* |===========|
	|.............| Attribute | (One row per local DA/SA attr)		|.............| Attribute | (One row per DA/SA attr)
	|===========|		|===========|
	INDEX { slpAgentIndex,		INDEX { slpAgentIndex,
	slpAttributeIndex }		slpAttributeIndex }
	4.4. Relationship to SNMP Architecture MIB (RFC 2571)		4.4. Relationship to SNMP Framework MIB (RFC 3411)
	The SLP MIB defines all text strings with a syntax of		The SLP MIB defines all text strings with a syntax of
	'SnmpAdminString' [RFC2571] which supports human-readable information		'SnmpAdminString' [RFC3411] which supports human-readable information
	in UTF-8 [RFC2279].		in UTF-8 [RFC2279].
	4.5. Relationship to Host Resources MIB (RFC 2790)		4.5. Relationship to Host Resources MIB (RFC 2790)
	The SLP MIB supports specification of the SLP agent software for each		The SLP MIB supports specification of the SLP agent software for each
	local SLP agent via a pointer to the 'hrSWInstalledTable' in the Host		managed SLP agent via a pointer to the 'hrSWInstalledTable' in the
	Resources MIB [RFC2790] in the following object:		Host Resources MIB [RFC2790] in the following object:
	o "slpAgentSWInstalledIndexOrZero" - a value for		- "slpAgentSWInstalledIndexOrZero" - a value for "hrSWInstalledIndex"
	"hrSWInstalledIndex" in the Host Resources MIB for this SLP		in the Host Resources MIB for this SLP agent's software
	agent's software
	5. Definition of SLP MIB		5. Definition of SLP MIB
	SERVICE-LOCATION-PROTOCOL-MIB DEFINITIONS ::= BEGIN		SERVICE-LOCATION-PROTOCOL-MIB DEFINITIONS ::= BEGIN
	IMPORTS		IMPORTS
	MODULE-IDENTITY,		MODULE-IDENTITY,
	OBJECT-TYPE,		OBJECT-TYPE,
	Integer32,		Integer32,
	mib-2		mib-2
	skipping to change at page 20, line 12 ¶		skipping to change at page 19, line 12 ¶
	END		END
	6. IANA Considerations		6. IANA Considerations
	IANA should assign a base arc in the 'mgmt' (standards track) OID		IANA should assign a base arc in the 'mgmt' (standards track) OID
	tree for the 'slpMIB' MODULE-IDENTITY defined in the SLP MIB.		tree for the 'slpMIB' MODULE-IDENTITY defined in the SLP MIB.
	The following definitions in the SLP MIB depend on IANA		The following definitions in the SLP MIB depend on IANA
	registrations:		registrations:
	o "slpAgentMessageTypesSupported" contains an array of the binary		- "slpAgentMessageTypesSupported" contains an array of the binary
	values assigned by SLPv2 [RFC2608] or assigned by IANA for the		values assigned by SLPv2 [RFC2608] or assigned by IANA for the
	Function-ID in SLPv2 messages.		Function-ID in SLPv2 messages.
	o "slpAgentExtensionsSupported" contains an array of the binary		- "slpAgentExtensionsSupported" contains an array of the binary
	values assigned by SLPv2 [RFC2608] or assigned by IANA for the		values assigned by SLPv2 [RFC2608] or assigned by IANA for the
	Extension ID in SLPv2 messages.		Extension ID in SLPv2 messages.
	There are no other IANA considerations associated with the SLP MIB.		There are no other IANA considerations associated with the SLP MIB.
	7. Internationalization Considerations		7. Intellectual Property
			The IETF takes no position regarding the validity or scope of any
			intellectual property or other rights that might be claimed to
			pertain to the implementation or use of the technology described in
			this 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 effort to identify any such rights. Information on the
			IETF's procedures with respect to rights in standards-track and
			standards-related documentation can be found in RFC 2028. Copies of
			claims of rights made available for publication and any assurances of
			licenses to be made available, or the result of an attempt made to
			obtain a general license or permission for the use of such
			proprietary rights by implementors or users of this specification can
			be obtained from the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights which may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
			8. Internationalization Considerations
	The SLP MIB defines all text strings with a syntax of		The SLP MIB defines all text strings with a syntax of
	'SnmpAdminString' [RFC2571] which supports human-readable information		'SnmpAdminString' [RFC3411] which supports human-readable information
	in UTF-8 [RFC2279]. The SLP MIB is therefore in full conformance		in UTF-8 [RFC2279]. The SLP MIB is therefore in full conformance
	with the best practices in "IETF Policy on Character Sets and		with the best practices in "IETF Policy on Character Sets and
	Languages" [RFC2277].		Languages" [RFC2277].
	8. Security Considerations		9. Security Considerations
	There are no management objects defined in this MIB that have a
	MAX-ACCESS clause of read-write or read-create.
	There are a number of read-only managed objects in this MIB that may
	contain sensitive information. These include:
	o "slpScopeSource" - a configuration source for an SLPv2 set of		There are no management objects defined in this MIB module that have
	services (typically an administrative group)		a MAX-ACCESS clause of read-write and/or read-create. So, if this
			MIB module is implemented correctly, then there is no risk that an
			intruder can alter or create any management objects of this MIB
			module via direct SNMP SET operations.
	o "slpScopeValue" - a string scope value for an SLPv2 set of		Some of the readable objects in this MIB module (i.e., objects with a
	services (typically an administrative group)		MAX-ACCESS other than not-accessible) may be considered sensitive or
			vulnerable in some network environments. It is thus important to
			control even GET and/or NOTIFY access to these objects and possibly
			to even encrypt the values of these objects when sending them over
			the network via SNMP. These are the tables and objects and their
			sensitivity/vulnerability:
	o "slpAddressSource" - a configuration source for an SLPv2 remote		slpAgentTable:
	directory agent (DA) or service agent (SA) address		slpAgentSWInstalledIndexOrZero - possible configuration data loss
			slpAgentName - possible configuration data loss
			slpAgentType - possible configuration data loss
			slpAgentIsBroadcastOnly - possible configuration data loss
			slpAgentActiveDADiscovery - possible configuration data loss
			slpAgentPassiveDADiscovery - possible configuration data loss
			slpAgentMessageTypesSupported - possible configuration data loss
			slpAgentExtensionsSupported - possible configuration data loss
	o "slpAddressOrName" - a string IPv4 address, IPv6 address, or DNS		slpScopeTable:
	name for an SLPv2 remote DA or SA address		slpScopeSource - possible configuration data loss
			slpScopeValue - possible configuration data loss
	These four objects reveal potentially sensitive information about the		slpAddressTable:
	existence and identification of SLPv2 infrastructure.		slpAddressAgentType - possible configuration data loss
			slpAddressSource - possible configuration data loss
			slpAddressOrName - possible configuration data loss
	It is thus important to control even GET access to these objects and		slpAttributeTable:
	possibly to even encrypt the values of these objects when sending		slpAttributeName - possible configuration data loss
	them over the network via SNMP. Not all versions of SNMP provide		slpAttributeType - possible configuration data loss
	features for such a secure environment.		slpAttributeValue - possible configuration data loss
	SNMPv1 by itself is not a secure environment. Even if the network		SNMP versions prior to SNMPv3 did not include adequate security.
	itself is secure (for example by using IPSec), even then, there is no		Even if the network itself is secure (for example by using IPSec),
	control as to who on the secure network is allowed to access and		even then, there is no control as to who on the secure network is
	GET/SET (read/change/create/delete) the objects in this MIB.		allowed to access and GET/SET (read/change/create/delete) the objects
			in this MIB module.
	It is recommended that the implementers consider the security		It is RECOMMENDED that implementers consider the security features as
	features as provided by the SNMPv3 framework. Specifically, the use		provided by the SNMPv3 framework (see [RFC3410], section 8),
	of the User-based Security Model RFC 2574 [RFC2574] and the View-		including full support for the SNMPv3 cryptographic mechanisms (for
	based Access Control Model RFC 2575 [RFC2575] is recommended.		authentication and privacy).
	It is then a customer/user responsibility to ensure that the SNMP		Further, deployment of SNMP versions prior to SNMPv3 is NOT
	entity giving access to an instance of this MIB, is properly		RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
	configured to give access to the objects only to those principals		enable cryptographic security. It is then a customer/operator
	(users) that have legitimate rights to indeed GET or SET		responsibility to ensure that the SNMP entity giving access to an
	(change/create/delete) them.		instance of this MIB module is properly configured to give access to
			the objects only to those principals (users) that have legitimate
			rights to indeed GET or SET (change/create/delete) them.
	9. Acknowledgements		10. Acknowledgements
	The editors would like to thank: Pete St. Pierre (Sun) for his		The editors would like to thank: Pete St. Pierre (Sun) for his
	original work on an SLP MIB in 1997; Erik Guttman (Sun) for compiling		original work on an SLP MIB in 1997; Erik Guttman (Sun) for compiling
	the requirements for this SLP MIB for SLPv2; Jim Muchow (Cisco) for		the requirements for this SLP MIB for SLPv2; Jim Muchow (Cisco) for
	his comments on the ASN.1 structure and compliance macros; and Bert		his comments on the ASN.1 structure and compliance macros; and Bert
	Wijnen (Lucent) for his comments on size and complexity.		Wijnen (Lucent) for his comments on size and complexity.
	10. Normative References		11. Normative References
	[RFC2119] S. Bradner. "Key words for use in RFCs to Indicate		[RFC2119] Bradner. "Key words for use in RFCs to Indicate
	Requirement Levels", RFC 2119, March 1997.		Requirement Levels", RFC 2119, March 1997.
	[RFC2277] H. Alvestrand. "IETF Policy on Character Sets and		[RFC2277] Alvestrand. "IETF Policy on Character Sets and Languages",
	Languages", RFC 2277, January 1998.		RFC 2277, January 1998.
	[RFC2279] F. Yergeau. "UTF-8, a Transformation of ISO 10646", RFC
	2279, January 1998.
	[RFC2571] B. Wijnen, D. Harrington, R. Presuhn. "An Architecture for
	Describing SNMP Network Management Frameworks", RFC 2571,
	April 1999.
	[RFC2574] U. Blumenthal, B. Wijnen. "User-based Security Model (USM)
	for version 3 of the Simple Network Management Protocol
	(SNMPv3)", RFC 2574, April 1999.
	[RFC2575] B. Wijnen, R. Presuhn, K. McCloghrie. "View-based Access		[RFC2279] Yergeau. "UTF-8, a Transformation of ISO 10646", RFC 2279,
	Control Model for the Simple Network Management Protocol		January 1998.
	(SNMP)", RFC 2575, April 1999.
	[RFC2578] K. McCloghrie, D. Perkins, J. Shoenwaelder. "Structure of		[RFC2578] McCloghrie, Perkins, Shoenwaelder. "Structure of
	Management Information Version 2 (SMIv2)", RFC 2578, April		Management Information Version 2 (SMIv2)", RFC 2578, April
	1999.		1999.
	[RFC2579] K. McCloghrie, D. Perkins, J. Shoenwaelder. "Textual		[RFC2579] McCloghrie, Perkins, Shoenwaelder. "Textual Conventions
	Conventions for SMIv2", RFC 2579, April 1999.		for SMIv2", RFC 2579, April 1999.
	[RFC2580] K. McCloghrie, D. Perkins, J. Shoenwaelder. "Conformance
	Statements for SMIv2", RFC 2580, April 1999.
	[RFC2608] E. Guttman, C. Perkins, J. Veizades, M. Day. "Service
	Location Protocol, Version 2", RFC 2608, June 1999.
	[RFC2609] E. Guttman, C. Perkins, J. Kempf. "Service Templates and		[RFC2580] McCloghrie, Perkins, Shoenwaelder. "Conformance Statements
	Service: Schemes", RFC 2609, June 1999.		for SMIv2", RFC 2580, April 1999.
	[RFC2610] C. Perkins, E. Guttman. "DHCP Options for Service Location		[RFC2608] Guttman, Perkins, Veizades, Day. "Service Location
	Protocol", RFC 2610, June 1999.		Protocol, Version 2", RFC 2608, June 1999.
	[RFC2790] S. Waldbusser, P. Grillo. "Host Resources MIB", RFC 2790,		[RFC2790] Waldbusser, Grillo. "Host Resources MIB", RFC 2790, March
	March 2000.		2000.
	[RFC3111] E. Guttman. "Service Location Protocol Modifications for		[RFC3111] Guttman. "Service Location Protocol Modifications for
	IPv6", RFC 3111, May 2001.		IPv6", RFC 3111, May 2001.
	11. Informative References		[RFC3224] Guttman. "Vendor Extensions for Service Location
			Protocol", RFC 3224, January 2002.
	[RFC1155] M. Rose, K. McCloghrie. "Structure and Identification of
	Management Information for TCP/IP-based internets" [SMIv1],
	RFC 1155, May 1990.
	[RFC1157] J. Case, M. Fedor, M. Schoffstall, C. Davin. "Simple
	Network Management Protocol (SNMP)" [SNMPv1], RFC 1157, May
	1990.
	[RFC1212] M. Rose, K. McCloghrie. "Concise MIB Definitions", RFC
	1212, March 1991.
	[RFC1213] K. McCloghrie, M. Rose. "Management Information Base for
	Network Management of TCP/IP-based internets: MIB-II", RFC
	1213, March 1991.
	[RFC1215] M. Rose. "Convention for Defining Traps for use with the
	SNMP", RFC 1215, March 1991.
	[RFC1901] J. Case, K. McCloghrie, M. Rose, S. Waldbusser.
	"Introduction to Community-based SNMPv2", RFC 1901, January
	1996.
	[RFC1905] J. Case, K. McCloghrie, M. Rose, S. Waldbusser. "Protocol		[RFC3411] Harrington, Presuhn, Wijnen. "An Architecture for
	Operations for Version 2 of the Simple Network Management		Describing SNMP Network Management Frameworks", STD 62, RFC
	Protocol (SNMPv2)", RFC 1905, January 1996.		3411, December 2002.
	[RFC1906] J. Case, K. McCloghrie, M. Rose, S. Waldbusser. "Transport		12. Informative References
	Mappings for Version 2 of the Simple Network Management
	Protocol (SNMPv2)", RFC 1906, January 1996.
	[RFC1907] J. Case, K. McCloghrie, M. Rose, S. Waldbusser.		[RFC2609] Guttman, Perkins, Kempf. "Service Templates and Service:
	"Management Information Base for Version 2 of the Simple		Schemes", RFC 2609, June 1999.
	Network Management Protocol (SNMPv2)", RFC 1907, January
	1996.
	[RFC2570] J. Case, R. Mundy, D. Partain, B. Stewart. "Introduction		[RFC2610] Perkins, Guttman. "DHCP Options for Service Location
	to Version 3 of the Internet-standard Network Management		Protocol", RFC 2610, June 1999.
	Framework", RFC 2570, April 1999.
	[RFC2572] J. Case, D. Harrington, R. Presuhn, B. Wijnen. "Message		[RFC2614] Kempf, Guttman. "An API for Service Location", RFC 2614,
	Processing and Dispatching for the Simple Network		June 1999.
	Management Protocol (SNMP)", RFC 2572, April 1999.
	[RFC2573] D. Levi, P. Meyer, B. Stewart. "SNMP Applications", RFC		[RFC3410] Case, Mundy, Partain, Stewart. "Introduction and
	2573, April 1999.		Applicability Statements for Internet Standard Management
			Framework", RFC 3410, December 2002.
	12. Authors' Addresses		13. Authors Addresses
	Editor: Mark Bakke		Editor: Mark Bakke
	Postal: Cisco Systems Inc		Postal: Cisco Systems Inc
	6450 Wedgwood Road, Suite 130		6450 Wedgwood Road, Suite 130
	Maple Grove, MN 55311		Maple Grove, MN 55311
	USA		USA
	Tel: +1 763-398-1000		Tel: +1 763-398-1000
	Email: mbakke@cisco.com		Email: mbakke@cisco.com
	Editor: Ira McDonald		Editor: Ira McDonald
	skipping to change at page 24, line 5 ¶		skipping to change at page 23, line 4 ¶
	Tel: +1 763-398-1000		Tel: +1 763-398-1000
	Email: mbakke@cisco.com		Email: mbakke@cisco.com
	Editor: Ira McDonald		Editor: Ira McDonald
	Postal: High North Inc		Postal: High North Inc
	221 Ridge Ave		221 Ridge Ave
	Grand Marais, MI 49839		Grand Marais, MI 49839
	USA		USA
	Tel: +1 906-494-2434		Tel: +1 906-494-2434
	Email: imcdonald@sharplabs.com"		Email: imcdonald@sharplabs.com"
	Usage questions and comments on this SLP MIB should be sent directly		Usage questions and comments on this SLP MIB should be sent directly
	to the editors at their above addresses (and to the SLP Project		to the editors at their above addresses (and to the SLP Project
	mailing list - see below).		mailing list - see below).
	Implementers of this specification are encouraged to join the SLP		Implementers of this specification are encouraged to join the SLP
	Project mailing list in order to participate in any discussions of		Project mailing list in order to participate in any discussions of
	clarification issues and comments.		clarification issues and comments.
	SLP Project Mailing List: svrloc-discuss@lists.sourceforge.net		SLP Project Mailing List: svrloc-discuss@lists.sourceforge.net
	To subscribe to the SLP Project mailing list, visit the web page:		To subscribe to the SLP Project mailing list, visit the web page:
	https://lists.sourceforge.net/lists/listinfo/srvloc-discuss		https://lists.sourceforge.net/lists/listinfo/srvloc-discuss
	13. Full Copyright Statement		14. Full Copyright Statement
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Copyright (C) The Internet Society (2003). 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		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
	skipping to change at page 25, line 5 ¶		skipping to change at page 24, line 5 ¶
	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		This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING		"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING		TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION		BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF		HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."		MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
	14. Appendix X - Change Log		15. Appendix X - Change Log
	[to be deleted before publication as an RFC]		[to be deleted before publication as an RFC]
			<draft-mcdonald-svrloc-mib-04.txt> 27 February 2003
			- completely replaced Internet-Standard Management Framework section,
			per request of Bert Wijnen
			- added Intellectual Property section, per request of Bert Wijnen
			- completely rewrote Security Considerations section, per request of
			Bert Wijnen
			- revised Normative References and Informative References sections,
			per request of Bert Wijnen
			- added copyright in MODULE-IDENTITY, per request of Bert Wijnen
			- added REFERENCE clauses for references, per request of Bert Wijnen
	<draft-mcdonald-svrloc-mib-03.txt> 1 March 2002		<draft-mcdonald-svrloc-mib-03.txt> 1 March 2002
	- added Normative References section, per request of RFC Editor		- added Normative References section, per request of RFC Editor
	- added Informative References section, per request of RFC Editor		- added Informative References section, per request of RFC Editor
	- revised Abstract, Introduction, and Security Considerations to		- revised Abstract, Introduction, and Security Considerations to
	state that the SLP MIB supports passive monitoring (but not		state that the SLP MIB supports passive monitoring (but not
	configuration), per concensus of SLP Project mailing list		configuration), per concensus of SLP Project mailing list
	- deleted Property group (last remaining 'read-write' objects), per		- deleted Property group (last remaining 'read-write' objects), per
	concensus of SLP Project mailing list		concensus of SLP Project mailing list
	<draft-mcdonald-svrloc-mib-02.txt> 11 February 2002		<draft-mcdonald-svrloc-mib-02.txt> 11 February 2002
End of changes. 74 change blocks.
	251 lines changed or deleted		211 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/