Network Working Group Mark Bakke INTERNET DRAFT Cisco Ira McDonald Updates: RFC 2608 High North [Target Category: Standards Track] 20 November 2001 Expires: 20 May 2002 Definitions of Managed Objects for Service Location Protocol (SLP MIB) Copyright (C) The Internet Society (2001). All Rights Reserved. Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To view the list of Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Abstract 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 and configuration of Service Location Protocol Version 2 (SLPv2) [RFC2608] directory agents (DAs), service agents (SAs), and user agents (UAs). Bakke, McDonald Expires 20 May 2002 [Page 1] Internet Draft Service Location Protocol MIB 20 November 2001 Table of Contents 1. Introduction ............................................... 3 2. SNMP Network Management Framework .......................... 3 3. Design Requirements for SLP MIB ............................ 5 3.1. General ................................................ 5 3.2. Natural Languages ...................................... 6 3.3. Text Strings ........................................... 6 3.4. Administrative Operations .............................. 6 4. Overview of SLP MIB ........................................ 8 4.1. Conformance Terminology ................................ 8 4.2. SLP Terminology ........................................ 8 4.3. Abstract Model of SLP MIB .............................. 9 4.4. Administrative Operations .............................. 11 4.5. Relationship to MIB-II (RFC 1213) ...................... 11 4.6. Relationship to SNMP Architecture MIB (RFC 2571) ....... 12 4.7. Relationship to Host Resources MIB (RFC 2790) .......... 12 4.8. Relationship to Remote Monitoring MIB (RFC 2819) ....... 12 4.9. Relationship to SLP Notifications (RFC 3082) ........... 12 5. Definition of SLP MIB ...................................... 14 5.1. Textual Conventions .................................... 15 5.2. Admin Group (Mandatory) Objects ........................ 17 5.3. Agent Group (Mandatory) Objects ........................ 20 5.4. Scope Group (Mandatory) Objects ........................ 24 5.5. Timer Group (Mandatory) Objects ........................ 27 5.6. Network Group (Mandatory) Objects ...................... 32 5.7. Interface Group (Optional) Objects ..................... 38 5.8. Address Group (Optional) Objects ....................... 41 5.9. Attribute Group (Optional) Objects ..................... 45 5.10. Counter Group (Optional) Objects ...................... 47 5.11. Trace Group (Optional) Objects ........................ 50 5.12. Alert Group (Optional) Notifications .................. 55 5.13. Conformance Statements ................................ 56 5.14. Conformance Groups .................................... 58 6. Usage Examples ............................................. 63 6.1. Start Admin Session .................................... 63 6.2. Configure SLP Directory Agent .......................... 63 6.3. Configure SLP Service Agent ............................ 63 6.4. Configure SLP User Agent ............................... 63 7. IANA Considerations ........................................ 63 8. Internationalization Considerations ........................ 64 9. Security Considerations .................................... 64 10. Acknowledgements .......................................... 66 11. References ................................................ 66 12. Authors' Addresses ........................................ 68 13. Appendix I - Issues ....................................... 69 14. Appendix X - Change Log ................................... 69 15. Full Copyright Statement .................................. 69 Bakke, McDonald Expires 20 May 2002 [Page 2] Internet Draft Service Location Protocol MIB 20 November 2001 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 and configuration of Service Location Protocol Version 2 (SLPv2) [RFC2608] directory agents (DAs), service agents (SAs), and user agents (UAs). Comments should be sent to svrloc-discuss@lists.sourceforge.net. See: 'Appendix I - Issues' [to be deleted before publication as an RFC] for a list of outstanding issues for the design of this SLP MIB. 2. SNMP Network Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in 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 first version of the SNMP message protocol is called SNMPv1 and 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 first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. Bakke, McDonald Expires 20 May 2002 [Page 3] Internet Draft Service Location Protocol MIB 20 November 2001 A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no 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. Bakke, McDonald Expires 20 May 2002 [Page 4] Internet Draft Service Location Protocol MIB 20 November 2001 3. Design Requirements for SLP MIB The SLP MIB design requirements discussed in the following sections are not conformance requirements on _implementations_ of the SLP MIB. Therefore the words must, should, and may are used below in lowercase (informative per [RFC2119] conventions). 3.1. General This section discusses some general requirements that have influenced the design of the SLP MIB. o The SLP MIB must provide SNMP interfaces to all functions required to monitor and configure SLPv2 [RFC2608] directory agents (DAs), service agents (SAs), and user agents (UAs). o The SLP MIB must be organized so that access can be controlled effectively by using the User-based Security Model [RFC2574] and the View-based Access Control Model [RFC2575] from the SNMPv3 framework. o The SLP MIB must not compromise native security in SLPv2 [RFC2608] by exposing private keys or other confidential information via SNMP. o The SLP MIB must define a core set of mandatory object groups that support most passive monitoring requirements. o The SLP MIB should define additional optional object groups that support all other features and timers of SLPv2 [RFC2608] and all of the 'net.slp' configuration properties defined in [RFC2614]. o The SLP MIB should avoid the use of SMIv2 [RFC2578] datatypes (for example, Counter64) which cannot be translated with full fidelity to SMIv1. o The SLP MIB should define MIN-ACCESS of 'read-write' for all the '...RowStatus' objects, for full fidelity translation to SMIv1. o The SLP MIB should name objects using the more readable long names of 'net.slp' configuration properties defined in [RFC2614], rather than the shorter opaque names in SLPv2 [RFC2608]. The following sections discuss selected design issues in more detail. Bakke, McDonald Expires 20 May 2002 [Page 5] Internet Draft Service Location Protocol MIB 20 November 2001 3.2. Natural Languages This section discusses human natural language requirements for the SLP MIB. o The SLP MIB must support natural language tags [RFC3066] for all human-readable text strings per [RFC2277]. o The SLP MIB must not restrict the choice of human natural language used to configure human-readable text strings per [RFC2277]. o The SLP MIB must not restrict the choice of character repertoire used to configure human-readable text strings per [RFC2277]. o The SLP MIB must support any human natural language which can be expressed in UTF-8 [RFC2279]. 3.3. Text Strings This section discusses text string requirements for the SLP MIB. o The SLP MIB must use UTF-8 [2279] for all human-readable text strings per [RFC2277] for internationalization support. o The SLP MIB must use human-readable text encodings for non-integer data (for example "slpInterfaceAddress" as dotted decimal IP address) for compatibility with SLPv2 [RFC 2608] and the 'net.slp' configuration properties defined in [RFC2614] and to facilitate script-based network management systems. 3.4. Administrative Operations This section discusses administrative operation requirements for the SLP MIB. o The SLP MIB must support dynamic row creation for all conceptual tables containing configuration data using MAX-ACCESS 'read-create'. o The SLP MIB must permit static row activation for all conceptual tables containing configuration data using MIN-ACCESS 'read-write' in the conformance macros. Bakke, McDonald Expires 20 May 2002 [Page 6] Internet Draft Service Location Protocol MIB 20 November 2001 o The SLP must support cooperative locking for a single admin session using "snmpSetSerialNo" [RFC1907] rules. o The SLP MIB must define admin scalar objects for access control to SNMP Set operations on SLP MIB objects (createRow, modifyRow, etc.). Bakke, McDonald Expires 20 May 2002 [Page 7] Internet Draft Service Location Protocol MIB 20 November 2001 4. Overview of SLP MIB The SLP MIB can be used to monitor and (optionally) to configure and diagnose SLPv2 [RFC2608] directory agents (DAs), service agents (SAs), and user agents (UAs). The SLP MIB makes no assumptions about the particular system topology of the managed SLP agents (for example, they may be distributed across several rack-mounted processors in a router). 4.1. Conformance Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 4.2. SLP Terminology The SLP MIB uses the following definitions from SLPv2 [RFC2608]: o "User Agent (UA)" A process working on the user's behalf to establish contact with some service. The UA retrieves service information from the Service Agents or Directory Agents. o "Service Agent (SA)" A process working on the behalf of one or more services to advertise the services. o "Directory Agent (DA)" A process which collects service advertisements. There can only be one DA present per given host. o "Service Type" Each type of service has a unique Service Type string. o "Naming Authority" The agency or group which catalogues given Service Types and Attributes. The default Naming Authority is IANA. o "Scope" A set of services, typically making up a logical administrative group. The SLP MIB also uses the following term defined in [RFC1738] and Bakke, McDonald Expires 20 May 2002 [Page 8] Internet Draft Service Location Protocol MIB 20 November 2001 updated in [RFC2396]: o "URL" Uniform Resource Locator. 4.3. Abstract Model of SLP MIB The Agent group is the principal object group in the abstract model defined in the SLP MIB. The Scope, Timer, Network, Interface, Address, Attribute, and Counter tables (all subordinate to "slpAgentTable") each define a high-order index object "slp...ListIndex" for linkage to the "slpAgentTable" (one-to-one or one-to-many). The Scope, Timer, Network, Interface, and Address groups also define a scalar object "slp...UseCommonList". If "true", then "slp...ListIndex" is ALWAYS "1" for every installed "slpAgentIndex" value (single shared list for all SLP agents on this managed system). If "slp...UseCommonList" is "false", then "slp...ListIndex" corresponds one-to-one to each installed "slpAgentIndex" value (separate list for each SLP agent on this managed system). Therefore, the "slpAgentTable" does not define "slp...ListIndex" objects for any subordinate table references - such references are always unambiguous and deterministic. The following page is a diagram of the abstract model of the SLP MIB. Bakke, McDonald Expires 20 May 2002 [Page 9] Internet Draft Service Location Protocol MIB 20 November 2001 |=======| |=======| |=======| | Admin | (Access) | Alert | (Traps) | Trace | (Diagnostics) |=======| |=======| |=======| INDEX { slpTraceIndex } |=======| | Agent | (One row per DA, SA, or UA configured on system) |=======| | INDEX { slpAgentIndex } | | | 0..* |===========| |...........| Scope | (One row per scope value) | |===========| | INDEX { slpScopeListIndex, | slpScopeItemIndex } | | 0..1 |===========| 0..1 (Overrides per interface) |...........| Timer |............ | |===========| : | INDEX { slpTimerListIndex } | : | : | 0..1 |===========| 0..1 (Overrides per interface) |...........| Network |........ : | |===========| : : | INDEX { slpNetworkListIndex } | : : | : : | 0..* |===========|.......: : |...........| Interface | (One row : per DA/SA/UA interface) | |===========|...........: | INDEX { slpInterfaceListIndex, | slpInterfaceItemIndex } | | 0..* |===========| |...........| Address | (One row per DA/SA address) | |===========| | INDEX { slpAddressListIndex, | slpAddressItemIndex } | | 0..* |===========| |...........| Attribute | (One row per DA/SA attribute) | |===========| | INDEX { slpAttributeListIndex, | slpAttributeItemIndex } | | 0..1 |===========| |...........| Counter | (One row per DA/SA/UA set of counters) |===========| INDEX { slpCounterListIndex } Bakke, McDonald Expires 20 May 2002 [Page 10] Internet Draft Service Location Protocol MIB 20 November 2001 4.4. Administrative Operations Implementation of the Admin group is REQUIRED for all implementations of the SLP MIB, to provide positive coordination of management station contention over the 'read-write' objects in the SLP MIB. In particular, the following scalar objects are defined: o "slpAdminSessionActive" - a boolean SLP management session state (active/inactive) o "slpAdminSessionStartTime" - a time stamp of the SLP management session start time o "slpAdminSessionLeaseTime" - a time delta until the SLP management session end time o "slpAdminSessionSerialNo" - a spin lock for starting the single supported SLP management session - a fine-grained supplement to the general SNMP spin lock "snmpSetSerialNo" [RFC1907] o "slpAdminSessionOwner" - an internationalized owner string for the SLP management session - a refinement of 'OwnerString' [RFC2819]. o "slpAdminCreateRow" - a boolean to coordinate row creation o "slpAdminDestroyRow" - a boolean to coordinate row deletion o "slpAdminModifyRow" - a boolean to coordinate row modification o "slpAdminModifyScalar" - a boolean to coordinate scalar modification o "slpAdminClearTrace" - a boolean to coordinate trace clearing 4.5. Relationship to MIB-II (RFC 1213) The SLP MIB uses the value of "sysUpTime" in the time stamp in the following objects: o "slpAdminSessionStartTime" - value of "sysUpTime" when most recent admin session started o "slpAgentLastRebootTime" - value of "sysUpTime" when this SLP agent last rebooted Bakke, McDonald Expires 20 May 2002 [Page 11] Internet Draft Service Location Protocol MIB 20 November 2001 o "slpTraceTimeStamp" - value of "sysUpTime" when this SLP message was recorded in the "slpTraceTable" See: 'TimeStamp' textual convention defined in [RFC2579]. 4.6. Relationship to SNMP Architecture MIB (RFC 2571) The SLP MIB defines all text strings with a syntax of 'SnmpAdminString' [RFC2571] which supports human-readable information in UTF-8 [RFC2279]. 4.7. Relationship to Host Resources MIB (RFC 2790) The SLP MIB supports specification of the SLP agent software for each SLP agent configured via a pointer to the 'hrSWInstalledTable' in the Host Resources MIB [RFC2790] in the following object: o "slpAgentSWInstalledIndexOrZero" - a value for "hrSWInstalledIndex" in the Host Resources MIB for this SLP agent's software 4.8. Relationship to Remote Monitoring MIB (RFC 2819) The SLP MIB defines a management session coordination object that is an internationalized form of the 'OwnerString' textual convention defined in [RFC2819]: o "slpAdminSessionOwner" - UTF-8 [RFC2279] admin session owner string See: 'OwnerString' textual convention defined in [RFC2819]. 4.9. Relationship to SLP Notifications (RFC 3082) The SLP MIB defines two SNMP notifications and one notifications control object which support equivalent functionality to that described in section 5.1 'Small Network Design' and section 6 'Subscribe Extension' of Notification and Subscription for SLP [RFC3082]: o "slpAlertRegistration" - service registration notification Bakke, McDonald Expires 20 May 2002 [Page 12] Internet Draft Service Location Protocol MIB 20 November 2001 o "slpAlertDeregistration" - service deregistration notification o "slpNetworkEnableAlertTypes" - bit-mask of enabled notifications Bakke, McDonald Expires 20 May 2002 [Page 13] Internet Draft Service Location Protocol MIB 20 November 2001 5. Definition of SLP MIB SERVICE-LOCATION-PROTOCOL-MIB DEFINITIONS ::= BEGIN -- To Do: -- 1) Use MIN-ACCESS of 'read-write' so SMIv1 translation is correct -- 2) Describe pre-allocated blocks of Scope and Address rows in -- the Usage Examples section of the main document IMPORTS MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, Counter32, Gauge32, Integer32, Unsigned32, TimeTicks, mib-2 FROM SNMPv2-SMI -- IETF RFC 2578 TEXTUAL-CONVENTION, RowStatus, TestAndIncr, TimeStamp, TruthValue FROM SNMPv2-TC -- IETF RFC 2579 MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP FROM SNMPv2-CONF -- IETF RFC 2580 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; -- IETF RFC 2571 slpMIB MODULE-IDENTITY LAST-UPDATED "200111010000Z" -- 1 November 2001 ORGANIZATION "SLP Project (at Source Forge)" CONTACT-INFO " SLP Project (at Source Forge) Email: srvloc-discuss@lists.sourceforge.net Editor: Mark Bakke Postal: Cisco Systems Inc 6450 Wedgwood Road, Suite 130 Maple Grove, MN 55311 USA Tel: +1 763-398-1000 Email: mbakke@cisco.com Editor: Ira McDonald Bakke, McDonald Expires 20 May 2002 [Page 14] Internet Draft Service Location Protocol MIB 20 November 2001 Postal: High North Inc 221 Ridge Ave Grand Marais, MI 49839 USA Tel: +1 906-494-2434 Email: imcdonald@crt.xerox.com" DESCRIPTION "The MIB module for monitoring, configuration, and management of SLP (Service Location Protocol) directory agents (DAs), service agents (SAs), and/or user agents (UAs) on managed systems." ::= { mib-2 999 } -- [to be assigned by IANA] -- [standards track module] slpMIBObjects OBJECT IDENTIFIER ::= { slpMIB 1 } slpMIBNotifications OBJECT IDENTIFIER ::= { slpMIB 2 } slpMIBConformance OBJECT IDENTIFIER ::= { slpMIB 3 } slpMIBObjectGroups OBJECT IDENTIFIER ::= { slpMIBConformance 2 } slpMIBNotifyGroups OBJECT IDENTIFIER ::= { slpMIBConformance 3 } -- -- SlpAgentType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of this SLP agent. See: 'net.slp.isDA' in SLP API (RFC 2614)." SYNTAX INTEGER { da(1), -- directory agent sa(2), -- service agent ua(3) -- user agent } SlpScopeSource ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The source (DHCP, etc) of this SLP scope or scope list. Usage: SNMP Command Generators MUST only Set a value of this type to 'static(1)' (a statically configured scope) or 'default(7)' (MUST use a fixed value of 'DEFAULT'). All other values are discovered by the SLP agent during normal operation and rows are added to the 'slpScopeTable'. See: Preference list for scope configuration in Section 2 'Introduction' in RFC 2610 bis." SYNTAX INTEGER { static(1), -- from static local config info Bakke, McDonald Expires 20 May 2002 [Page 15] Internet Draft Service Location Protocol MIB 20 November 2001 staticDA(2), -- from static local config DA dhcp(3), -- from DHCP config info dhcpDA(4), -- from DHCP config DA dynamicDA(5), -- from dynamic DA (DAAdvert) dynamicSA(6), -- from dynamic SA (SAAdvert) default(7) -- use of scope 'DEFAULT' } SlpAttributeType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of this SLP attribute. See: Section 5 'Service Attributes' in SLPv2 (RFC 2608)." SYNTAX INTEGER { attrBoolean(1), -- Boolean ('true' or 'false') attrInteger(2), -- Integer (32-bit string) attrString(3), -- String (UTF-8 string) attrOpaque(4), -- Opaque (sequence of bytes) attrKeyword(5) -- Keyword (name only, no value) } SlpMessageType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of this SLP message. See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608)." SYNTAX INTEGER { -- Abbreviation/Function-ID Message Type msgSrvRqst(1), -- Service Request msgSrvRply(2), -- Service Reply msgSrvReg(3), -- Service Registration msgSrvDeReg(4), -- Service DeRegister msgSrvAck(5), -- Service Acknowledge msgAttrRqst(6), -- Attribute Request msgAttrRply(7), -- Attribute Reply msgDAAdvert(8), -- DA Advertisement msgSrvTypeRqst(9), -- Service Type Request msgSrvTypeRply(10), -- Service Type Reply msgSAAdvert(11), -- SA Advertisement msg12(12), -- extension message type msg13(13), -- extension message type msg14(14), -- extension message type msg15(15), -- extension message type msg16(16), -- extension message type msg17(17), -- extension message type msg18(18), -- extension message type msg19(19), -- extension message type msg20(20) -- extension message type } Bakke, McDonald Expires 20 May 2002 [Page 16] Internet Draft Service Location Protocol MIB 20 November 2001 -- -- slpAdmin OBJECT IDENTIFIER ::= { slpMIBObjects 1 } -- -- Admin Session Objects -- slpAdminSessionActive OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "State of admin session - active (true) or inactive (false). See: 'ifTestStatus' in Interfaces Group MIB (RFC 2863)." ::= { slpAdmin 1 } slpAdminSessionStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of 'sysUpTime' when this admin session started. See: 'sysUpTime' in MIB-II (RFC 1213)." ::= { slpAdmin 2 } slpAdminSessionLeaseTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The delta of 'sysUpTime' until this admin session will end or has already ended (by auto-release by the managed system)." ::= { slpAdmin 3 } slpAdminSessionSerialNo OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "An advisory lock used to allow several cooperating SNMP entities, all acting as Command Generators, to coordinate their use of the SNMP Set operation in this SLP MIB, by first contending for this SLP admin session lock. This object is used for fine-grained coordination of access Bakke, McDonald Expires 20 May 2002 [Page 17] Internet Draft Service Location Protocol MIB 20 November 2001 control to the tables and scalars defined in this SLP MIB. Usage: SNMP Command Generators that perform Set operations to any object defined in this SLP MIB, MUST first acquire the SLP admin session ownership via simultaneous Set of: (a) slpAdminSessionSerialNo (session spin lock) (b) slpAdminSessionOwner (session owner) to a valid string (which causes the SNMP Command Responder to change the value of 'slpAdminSessionActive' to 'true'). SNMP Command Generators, while an SLP admin session is active, MUST simultaneously (in the same SNMP request) Set: (a) one of the boolean scalars below in this Admin group; (b) one or more target scalar or columnar objects in SLP MIB. Usage: SNMP Command Generators SHOULD release their SLP admin session ownership via simultanenous Set of: (a) slpAdminSessionSerialNo (session spin lock); (b) slpAdminSessionOwner (session owner) to an empty string; (which causes the SNMP Command Responder to change the value of 'slpAdminSessionActive' to 'false'). Usage: SNMP Command Responders that support this SLP MIB MUST enforce the above access control semantics. Usage: SNMP Command Responders MAY release SLP admin session ownership after an implementation-dependent session timeout that MUST be reported in 'slpAdminSessionLeaseTime' and SHOULD be no less than 15 minutes. See: 'ifTestId' in Interfaces Group MIB (RFC 2863), which is a fine-grained lock for interface tests. See: 'snmpSetSerialNo' in SNMPv2 MIB (RFC 1907), which is a coarse-grained lock for cooperating SNMP managers. See: User-based Security Model for SNMP (RFC 2574). See: View-based Access Control Model for SNMP (RFC 2575)." ::= { slpAdmin 4 } slpAdminSessionOwner OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-write STATUS current DESCRIPTION "Internationalized SLP admin session owner string - semantics otherwise identical to the ASCII-only 'OwnerString' in RMON MIB (RFC 2819). This object conforms to IETF Policy on Character Sets and Languages (RFC 2277). Bakke, McDonald Expires 20 May 2002 [Page 18] Internet Draft Service Location Protocol MIB 20 November 2001 See: 'OwnerString' in RMON MIB (RFC 2819). See: 'ifTestOwner' in Interfaces Group MIB (RFC 2863)." ::= { slpAdmin 5 } -- -- Admin Operation Objects -- slpAdminCreateRow OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Boolean used to authorize Set of '...RowStatus' to 'create...' in one of the conceptual tables defined in this SLP MIB." ::= { slpAdmin 6 } slpAdminDestroyRow OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Boolean used to authorize Set of '...RowStatus' to 'destroy' in one of the conceptual tables defined in this SLP MIB." ::= { slpAdmin 7 } slpAdminModifyObject OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Boolean used to authorize Set of one or more columnar objects in one of the conceptual tables defined in this SLP MIB and/or one or more scalar objects defined in this SLP MIB." ::= { slpAdmin 8 } slpAdminClearCounters OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Boolean used to clear all counter objects in 'slpCounterTable' to zero (but NOT to delete any of the conceptual rows)." ::= { slpAdmin 9 } slpAdminDeleteTraces OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current Bakke, McDonald Expires 20 May 2002 [Page 19] Internet Draft Service Location Protocol MIB 20 November 2001 DESCRIPTION "Boolean used to delete all conceptual rows in 'slpTraceTable' and to reset 'slpTraceNextTraceIndex' to '1'." ::= { slpAdmin 10 } -- -- slpAgent OBJECT IDENTIFIER ::= { slpMIBObjects 2 } slpAgentRows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpAgentTable', including any rows in 'notInService' or other inactive states." ::= { slpAgent 2 } slpAgentMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpAgentTable'." ::= { slpAgent 3 } slpAgentNextAgentIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Next available (unused) value of 'slpAgentIndex', for use with 'createAnd[Go|Wait]' in 'slpAgentRowStatus'." ::= { slpAgent 4 } slpAgentTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpAgentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for all of the SLP directory agents (DAs), service agents (SAs), or user agents (UAs) currently installed and (possibly) active on this managed system." ::= { slpAgent 1 } slpAgentEntry OBJECT-TYPE SYNTAX SlpAgentEntry MAX-ACCESS not-accessible Bakke, McDonald Expires 20 May 2002 [Page 20] Internet Draft Service Location Protocol MIB 20 November 2001 STATUS current DESCRIPTION "An entry containing SLP (Service Location Protocol) objects for one of the SLP directory agents (DAs), service agents (SAs), or user agents (UAs) currently installed and (possibly) active on this managed system." INDEX { slpAgentIndex } ::= { slpAgentTable 1 } SlpAgentEntry ::= SEQUENCE { slpAgentIndex Integer32 (1..2147483647), slpAgentRowStatus RowStatus, slpAgentSWInstalledIndexOrZero Integer32 (0..2147483647), slpAgentName SnmpAdminString (SIZE (0..64)), slpAgentType SlpAgentType, slpAgentLastRebootTime TimeStamp, slpAgentLocale SnmpAdminString (SIZE (0..64)), slpAgentLocalesSupported SnmpAdminString (SIZE (0..255)), slpAgentMessageTypesSupported SnmpAdminString (SIZE (0..255)), slpAgentExtensionsSupported SnmpAdminString (SIZE (0..255)), slpAgentSerializedRegURL SnmpAdminString (SIZE (0..255)), slpAgentTypeHint SnmpAdminString (SIZE (0..255)), slpAgentServiceTypes SnmpAdminString (SIZE (0..255)) } slpAgentIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual row in 'slpAgentTable'." ::= { slpAgentEntry 1 } slpAgentRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row in 'slpAgentTable'." ::= { slpAgentEntry 2 } slpAgentSWInstalledIndexOrZero OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of 'hrSWInstalledIndex' in the Host Resources MIB (RFC 2790) for the executable software for this SLP agent, or zero if none. Bakke, McDonald Expires 20 May 2002 [Page 21] Internet Draft Service Location Protocol MIB 20 November 2001 See: 'hrSWInstalledIndex' in Host Resources MIB (RFC 2790)." ::= { slpAgentEntry 3 } slpAgentName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-create STATUS current DESCRIPTION "The friendly locally unique name for this SLP agent, for use with remote network management scripts and GUIs For example 'daNewYork'." ::= { slpAgentEntry 4 } slpAgentType OBJECT-TYPE SYNTAX SlpAgentType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of this SLP agent (DA, SA, or UA). See: 'net.slp.isDA' in SLP API (RFC 2614)." ::= { slpAgentEntry 5 } slpAgentLastRebootTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The last stateless reboot time of this SLP agent." ::= { slpAgentEntry 6 } slpAgentLocale OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-create STATUS current DESCRIPTION "The default SLP message locale for this SLP agent, expressed as a language tag (RFC 3066). For example 'en' means 'English' and 'no-nynorsk' is one of two official versions of Norwegian. See: 'net.slp.locale' in SLP API (RFC 2614)." ::= { slpAgentEntry 7 } slpAgentLocalesSupported OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "The SLP message locales supported for this SLP agent, Bakke, McDonald Expires 20 May 2002 [Page 22] Internet Draft Service Location Protocol MIB 20 November 2001 expressed as a list of language tags (RFC 3066). For example 'en,de,fr' means 'English, German, French'. See: 'net.slp.locale' in SLP API (RFC 2614)." ::= { slpAgentEntry 8 } slpAgentMessageTypesSupported OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "The SLP message types supported for this SLP agent, expressed as a list of decimal Function-ID values (RFC 2608). For example '1,2,...' means 'SrvRqst, SrvRply, etc.'. See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608)." ::= { slpAgentEntry 9 } slpAgentExtensionsSupported OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "The SLP extensions supported for this SLP agent, expressed as a list of decimal Extension ID values (RFC 2608). For example '2,3' means 'AttributeList, VendorOpaque'. See: Section 9.1 'SLP Extensions' in SLPv2 (RFC 2608)." DEFVAL { ''H } -- no extensions supported ::= { slpAgentEntry 10 } slpAgentSerializedRegURL OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "Serialized registrations URL for this SLP agent (DA/SA only) (used for static reboot of DA or SA). See: 'net.slp.SerializedRegURL' in SLP API (RFC 2614)." DEFVAL { ''H } -- no serialized registrations ::= { slpAgentEntry 11 } slpAgentTypeHint OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "The service types to be searched by this SLP agent (UA only), expressed as a list of service types (RFC 2609). For example 'service:printer:ipp'. Bakke, McDonald Expires 20 May 2002 [Page 23] Internet Draft Service Location Protocol MIB 20 November 2001 See: 'net.slp.typeHint' in SLP API (RFC 2614)." DEFVAL { ''H } -- no service types searched ::= { slpAgentEntry 12 } slpAgentServiceTypes OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "The service types of advertised by this SLP agent (DA/SA only) For example 'service:printer:ipp'. See: 'service-types' attribute in 'service:service-agent' in IANA Registry of Service Location Templates." DEFVAL { ''H } -- no service types advertised ::= { slpAgentEntry 13 } -- -- slpScope OBJECT IDENTIFIER ::= { slpMIBObjects 3 } slpScopeRows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpScopeTable', including any rows in 'notInService' or other inactive states." ::= { slpScope 2 } slpScopeMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpScopeTable'." ::= { slpScope 3 } slpScopeNextListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Next available (unused) value of 'slpScopeListIndex', for use with 'createAnd[Go|Wait]' in 'slpScopeRowStatus'." ::= { slpScope 4 } slpScopeUseCommonList OBJECT-TYPE Bakke, McDonald Expires 20 May 2002 [Page 24] Internet Draft Service Location Protocol MIB 20 November 2001 SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If 'true', then there MUST be one list in 'slpScopeTable', with 'slpScopeListIndex' fixed at a REQUIRED value of '1', and all SLP agents installed on this managed system MUST share and use this single common list of scopes. If 'false', then there MUST be a list in 'slpScopeTable', 'slpScopeListIndex' MUST correspond to 'slpAgentIndex', for each SLP agent installed on this managed system (i.e., scope lists are disjoint and are NOT shared). Usage: Scope lists consist of one or more rows in the 'slpScopeTable' (one row per scope value) for each list. Usage: Management stations SHOULD reset the managed system when they change the value of this object with a Set operation, since the resulting configuration would otherwise be corrupted." DEFVAL { true } ::= { slpScope 5 } slpScopeTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpScopeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for scope lists on this managed system. Usage: This table sparsely augments the 'slpAgentTable' (either with one or a set of scope lists). Usage: Scope lists consist of one or more rows in the 'slpScopeTable' (one row per scope value) for each list." ::= { slpScope 1 } slpScopeEntry OBJECT-TYPE SYNTAX SlpScopeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing SLP (Service Location Protocol) objects for one scope value on this managed system." INDEX { slpScopeListIndex, slpScopeItemIndex } ::= { slpScopeTable 1 } SlpScopeEntry ::= SEQUENCE { slpScopeListIndex Integer32 (1..2147483647), Bakke, McDonald Expires 20 May 2002 [Page 25] Internet Draft Service Location Protocol MIB 20 November 2001 slpScopeItemIndex Integer32 (1..2147483647), slpScopeRowStatus RowStatus, slpScopeSource SlpScopeSource, slpScopeValue SnmpAdminString (SIZE (0..255)) } slpScopeListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual list of rows in 'slpScopeTable'. Usage: For a given value of 'slpAgentIndex', the corresponding value of 'slpScopeListIndex' is the same OR is equal to '1', according to the current value of 'slpScopeUseCommonList'." ::= { slpScopeEntry 1 } slpScopeItemIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual single row in 'slpScopeTable', subordinate to 'slpScopeListIndex'." ::= { slpScopeEntry 2 } slpScopeRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row in 'slpScopeTable'." ::= { slpScopeEntry 3 } slpScopeSource OBJECT-TYPE SYNTAX SlpScopeSource MAX-ACCESS read-create STATUS current DESCRIPTION "The source (DHCP, etc) of this SLP scope or scope list. Usage: SNMP Command Generators MUST only Set the value of this object to 'static(1)' (a statically configured scope) or 'default(7)' (MUST use a fixed value of 'DEFAULT'). All other values are discovered by the SLP agent during normal operation and rows are added to the 'slpScopeTable'. See: Preference list for scope configuration in Section 2 'Introduction' in RFC 2610 bis." ::= { slpScopeEntry 4 } Bakke, McDonald Expires 20 May 2002 [Page 26] Internet Draft Service Location Protocol MIB 20 November 2001 slpScopeValue OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "One or more scopes configured for this SLP agent (DA/SA/UA), expressed as a list of scope values (RFC 2608). Note: The default (and lowest preference) scope value for any SLP agent is the string 'DEFAULT' verbatim in uppercase, per SLPv2 (RFC 2608). See: 'net.slp.useScopes' in SLP API (RFC 2614)." DEFVAL { ''H } -- no scope configured ::= { slpScopeEntry 5 } -- -- slpTimer OBJECT IDENTIFIER ::= { slpMIBObjects 4 } slpTimerRows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpTimerTable', including any rows in 'notInService' or other inactive states." ::= { slpTimer 2 } slpTimerMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpTimerTable'." ::= { slpTimer 3 } slpTimerNextListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Next available (unused) value of 'slpTimerListIndex', for use with 'createAnd[Go|Wait]' in 'slpTimerRowStatus'." ::= { slpTimer 4 } slpTimerUseCommonList OBJECT-TYPE SYNTAX TruthValue Bakke, McDonald Expires 20 May 2002 [Page 27] Internet Draft Service Location Protocol MIB 20 November 2001 MAX-ACCESS read-write STATUS current DESCRIPTION "If 'true', then there MAY be one list in 'slpTimerTable', with 'slpTimerListIndex' fixed at a REQUIRED value of '1', and all SLP agents installed on this managed system MUST share and use this single common list of timers. If 'false', then there MAY be a list in 'slpTimerTable', 'slpTimerListIndex' MUST correspond to 'slpAgentIndex', for each SLP agent installed on this managed system (i.e., timer lists are disjoint and are NOT shared). And there MAY be additional lists in 'slpTimerTable', pointed to by 'slpInterfaceTimerListIndex', to override timer config for particular interfaces. Usage: Timer lists consist of exactly one row in the 'slpTimerTable' (one column per timer item) for each list. Usage: Management stations SHOULD reset the managed system when they change the value of this object with a Set operation, since the resulting configuration would otherwise be corrupted." DEFVAL { true } ::= { slpTimer 5 } slpTimerTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpTimerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for timer lists on this managed system. Usage: This table sparsely augments the 'slpAgentTable' (either with one or a set of timer lists). Usage: Timer lists consist of exactly one row in the 'slpTimerTable' (one column per timer item) for each list." ::= { slpTimer 1 } slpTimerEntry OBJECT-TYPE SYNTAX SlpTimerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing SLP (Service Location Protocol) objects for one timer list on this managed system." INDEX { slpTimerListIndex } ::= { slpTimerTable 1 } Bakke, McDonald Expires 20 May 2002 [Page 28] Internet Draft Service Location Protocol MIB 20 November 2001 SlpTimerEntry ::= SEQUENCE { slpTimerListIndex Integer32 (1..2147483647), slpTimerRowStatus RowStatus, slpTimerDAActiveDiscInterval Unsigned32 (0..65535), slpTimerMulticastMaximumWait Unsigned32 (0..4294967295), slpTimerDAHeartBeat Unsigned32 (0..4294967295), slpTimerCloseConnectionWait Unsigned32 (0..65535), slpTimerRandomWaitBound Unsigned32 (0..4294967295), slpTimerMulticastTimeouts SnmpAdminString (SIZE (0..64)), slpTimerDADiscoveryTimeouts SnmpAdminString (SIZE (0..64)), slpTimerDatagramTimeouts SnmpAdminString (SIZE (0..64)) } slpTimerListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual row in 'slpTimerTable'. Usage: For a given value of 'slpAgentIndex', the corresponding value of 'slpTimerListIndex' is the same OR is equal to '1', according to the current value of 'slpTimerUseCommonList'." ::= { slpTimerEntry 1 } slpTimerRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row in 'slpTimerTable'." ::= { slpTimerEntry 2 } slpTimerDAActiveDiscInterval OBJECT-TYPE SYNTAX Unsigned32 (0..65535) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The DA active discovery interval in seconds. SNMP Set of '0' (zero) disables DA active discovery (limiting DA discovery to static and DHCP configuration). See: 'CONFIG_DA_FIND' in SLPv2 (RFC 2608). See: 'net.slp.DAActiveDiscoveryInterval' in RFC 2614." DEFVAL { 900 } -- 15 minutes discovery interval ::= { slpTimerEntry 3 } slpTimerMulticastMaximumWait OBJECT-TYPE Bakke, McDonald Expires 20 May 2002 [Page 29] Internet Draft Service Location Protocol MIB 20 November 2001 SYNTAX Unsigned32 (0..4294967295) UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum time for complete multicast query in milliseconds. See: 'CONFIG_MC_MAX' in SLPv2 (RFC 2608). See: 'net.slp.MulticastMaximumWait' in SLP API (RFC2614)." DEFVAL { 15000 } -- 15 seconds max multicast wait ::= { slpTimerEntry 4 } slpTimerDAHeartBeat OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The DA hearbeat interval in seconds (for passive DA discovery by SAs). (limiting DA discovery to static and DHCP configuration). See: 'CONFIG_DA_BEAT' in SLPv2 (RFC 2608). See: 'net.slp.DAHeartBeat' in SLP API (RFC 2614)." DEFVAL { 10800 } -- 3 hours DA heartbeat interval ::= { slpTimerEntry 5 } slpTimerCloseConnectionWait OBJECT-TYPE SYNTAX Unsigned32 (0..65535) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The wait before close of idle TCP connection in seconds. See: 'CONFIG_CLOSE_CONN' in SLPv2 (RFC 2608). Note: No corresponding property in SLP API (RFC2614)." DEFVAL { 300 } -- 5 minutes idle connect wait ::= { slpTimerEntry 6 } slpTimerRandomWaitBound OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum value for all random wait timers in milliseconds. Bakke, McDonald Expires 20 May 2002 [Page 30] Internet Draft Service Location Protocol MIB 20 November 2001 See: 'CONFIG_START_WAIT', 'CONFIG_REG_PASSIVE', and 'CONFIG_REG_ACTIVE' in SLPv2 (RFC 2608). See: 'net.slp.randomWaitBound' in SLP API (RFC2614)." DEFVAL { 1000 } -- 1 second random wait bound ::= { slpTimerEntry 7 } slpTimerMulticastTimeouts OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) -- UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The ordered list of multicast reply timeouts in milliseconds, expressed as a list of 32-bit decimal timer values. See: 'CONFIG_MC_RETRY' in SLPv2 (RFC 2608). See: 'net.slp.multicastTimeouts' in SLP API (RFC2614)." DEFVAL { "3000,3000,3000,3000,3000" } ::= { slpTimerEntry 8 } slpTimerDADiscoveryTimeouts OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) -- UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The ordered list of DA discovery timeouts in milliseconds, expressed as a list of 32-bit decimal timer values. See: 'CONFIG_RETRY' in SLPv2 (RFC 2608). See: 'net.slp.DADiscoveryTimeouts' in SLP API (RFC2614)." DEFVAL { "2000,2000,2000,2000,3000,4000" } ::= { slpTimerEntry 9 } slpTimerDatagramTimeouts OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) -- UNITS "milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The ordered list of unicast datagram timeouts in milliseconds, expressed as a list of 32-bit decimal timer values. The sum of these values is equal to 'CONFIG_RETRY_MAX' in SLPv2 (which defaults to 15 seconds). See: 'CONFIG_RETRY_MAX' in SLPv2 (RFC 2608). Bakke, McDonald Expires 20 May 2002 [Page 31] Internet Draft Service Location Protocol MIB 20 November 2001 See: 'net.slp.DADiscoveryTimeouts' in SLP API (RFC2614)." DEFVAL { "2000,2000,2000,2000,3000,4000" } ::= { slpTimerEntry 10 } -- -- slpNetwork OBJECT IDENTIFIER ::= { slpMIBObjects 5 } slpNetworkRows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpNetworkTable', including any rows in 'notInService' or other inactive states." ::= { slpNetwork 2 } slpNetworkMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpNetworkTable'." ::= { slpNetwork 3 } slpNetworkNextListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Next available (unused) value of 'slpNetworkListIndex', for use with 'createAnd[Go|Wait]' in 'slpNetworkRowStatus'." ::= { slpNetwork 4 } slpNetworkUseCommonList OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If 'true', then there MUST be one list in 'slpNetworkTable', with 'slpNetworkListIndex' fixed at a REQUIRED value of '1', and all SLP agents installed on this managed system MUST share and use this single common list of network config. If 'false', then there MUST be a list in 'slpNetworkTable', 'slpNetworkListIndex' MUST correspond to 'slpAgentIndex', for each SLP agent installed on this managed system (i.e., network config lists are disjoint and are NOT shared). Bakke, McDonald Expires 20 May 2002 [Page 32] Internet Draft Service Location Protocol MIB 20 November 2001 And there MAY be additional lists in 'slpNetworkTable', pointed to by 'slpInterfaceNetworkListIndex', to override network config for particular interfaces. Usage: Network config lists consist of exactly one row in the 'slpNetworkTable' (one column per config item) for each list. Usage: Management stations SHOULD reset the managed system when they change the value of this object with a Set operation, since the resulting configuration would otherwise be corrupted." DEFVAL { true } ::= { slpNetwork 5 } slpNetworkTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpNetworkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for network config lists on this managed system. Usage: This table sparsely augments the 'slpAgentTable' (either with one or a set of network config lists). This table MAY also contain lists referenced by 'slpInterfaceNetworkListIndex', for optional override of network config per interface. Usage: Network config lists consist of exactly one row in the 'slpNetworkTable' (one column per config item) for each list." ::= { slpNetwork 1 } slpNetworkEntry OBJECT-TYPE SYNTAX SlpNetworkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing SLP (Service Location Protocol) objects for one network config list on this managed system." INDEX { slpNetworkListIndex } ::= { slpNetworkTable 1 } SlpNetworkEntry ::= SEQUENCE { slpNetworkListIndex Integer32 (1..2147483647), slpNetworkRowStatus RowStatus, slpNetworkEnableSecurity TruthValue, slpNetworkEnableAlertTypes Integer32 (0..2147483647), slpNetworkIsBroadcastOnly TruthValue, slpNetworkEnableDADiscovery TruthValue, slpNetworkPassiveDADiscovery TruthValue, slpNetworkMulticastTTL Unsigned32 (1..255), slpNetworkMTU Unsigned32 (0..65535), Bakke, McDonald Expires 20 May 2002 [Page 33] Internet Draft Service Location Protocol MIB 20 November 2001 slpNetworkMaxResults Integer32 (-1..2147483647), slpNetworkTraceDATraffic TruthValue, slpNetworkTraceMsg TruthValue, slpNetworkTraceDrop TruthValue, slpNetworkTraceReg TruthValue } slpNetworkListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual row in 'slpNetworkTable'. Usage: For a given value of 'slpAgentIndex', the corresponding value of 'slpNetworkListIndex' is the same OR is equal to '1', according to the current value of 'slpNetworkUseCommonList'." ::= { slpNetworkEntry 1 } slpNetworkRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row in 'slpNetworkTable'." ::= { slpNetworkEntry 2 } slpNetworkEnableSecurity OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable SLPv2 (RFC 2608) security for one or all SLP agents If 'true', then each validated SLPv2 security SPI value SHOULD match one configured value of 'usmUserSecurityName' (model- independent principal name) in the SNMPv3 USM MIB (RFC 2574) and the configured value of 'usmUserPublic' SHOULD contain the the named principal's public key. If 'false', then SLPv2 security (but not SNMP security) is disabled on this SLP agent. See: 'net.slp.securityEnabled' in SLP API (RFC 2614)." ::= { slpNetworkEntry 3 } slpNetworkEnableAlertTypes OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION Bakke, McDonald Expires 20 May 2002 [Page 34] Internet Draft Service Location Protocol MIB 20 November 2001 "Enable selected SNMP notifications for one or all SLP agents, via a bit-mask: 1 : alertRegistration -- 2**0 2 : alertDeregistration -- 2**1 4 : alertProtocolError -- 2**2 If a given bit is set to '1', then the specified alert MUST be emitted as an SNMP notification to all of the currently subscribed and authorized SNMP Notification Receivers, when the corresponding SLPv2 (RFC 2608) event occurs (i.e., the specified notification is permitted). If a given bit is set to '0', then the specified alert MUST NOT be emitted as an SNMP notification to any of the currently subscribed and authorized SNMP Notification Receivers, when the corresponding SLPv2 (RFC 2608) event occurs (i.e., the specified notification is throttled). Note: When used in conjunction with the Target MIB and the Notification MIB defined in SNMP Applications (RFC 2573), this object suppports equivalent functionality to that described in section 5.1 'Small Network Design' and section 6 'Subscribe Extension' of Notification and Subscription for SLP (RFC 3082) - direct notification of interested clients when each SLP SA becomes active and later inactive. See: Target/Notification MIBs in SNMP Applications (RFC2573). See: Notification and Subscription for SLP (RFC 3082). Note: No corresponding property in SLP API (RFC2614)." DEFVAL { 0 } -- throttle all notifications ::= { slpNetworkEntry 4 } slpNetworkIsBroadcastOnly OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable broadcast only network for one or all SLP agents. If 'true', SLP agent MUST send only broadcast messages. If 'false', SLP agent MAY send multicast messages. See: 'Broadcast Only' in section 14 of SLPv2 (RFC 2608). See: 'net.slp.isBroadcastOnly' in SLP API (RFC 2614)." DEFVAL { false } -- multicast allowed ::= { slpNetworkEntry 5 } slpNetworkEnableDADiscovery OBJECT-TYPE Bakke, McDonald Expires 20 May 2002 [Page 35] Internet Draft Service Location Protocol MIB 20 November 2001 SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable DA discovery for one or all SLP agents. If 'true', SLP agent MAY actively/passively discover DAs, If 'false', SLP agent MUST NOT actively/passively discover DAs, but MUST instead use only local config and DHCP config. See: 'No DA Discovery' in section 14 of SLPv2 (RFC 2608). Note: No corresponding property in SLP API (RFC2614)." DEFVAL { true } -- DA discovery allowed ::= { slpNetworkEntry 6 } slpNetworkPassiveDADiscovery OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable passive DA discovery for one or all SLP agents. If 'true', SLP agent MAY passively discover DAs, If 'false', SLP agent MUST NOT passively discover DAs. See: 'Passive DA Advertising' in SLPv2 (RFC 2608). Note: 'net.slp.passiveDADetection' in SLP API (RFC2614)." DEFVAL { true } -- passive DA discovery allowed ::= { slpNetworkEntry 7 } slpNetworkMulticastTTL OBJECT-TYPE SYNTAX Unsigned32 (1..255) UNITS "hops" MAX-ACCESS read-create STATUS current DESCRIPTION "Multicast time-to-live (hop count) for one or all SLP agents. See: 'Multicast TTL' in section 14 of SLPv2 (RFC 2608). See: 'net.slp.multicastTTL' in SLP API (RFC2614)." DEFVAL { 255 } -- maximum multicast TTL ::= { slpNetworkEntry 8 } slpNetworkMTU OBJECT-TYPE SYNTAX Unsigned32 (0..65535) UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "MTU (maximum transmission unit) for one or all SLP agents. Bakke, McDonald Expires 20 May 2002 [Page 36] Internet Draft Service Location Protocol MIB 20 November 2001 Maximum datagram size SLP agent MAY send. See: 'Path MTU' in section 6 'Use of TCP' - SLPv2 (RFC 2608). See: 'net.slp.MTU' in SLP API (RFC2614)." DEFVAL { 1400 } -- default MTU size ::= { slpNetworkEntry 9 } slpNetworkMaxResults OBJECT-TYPE SYNTAX Integer32 (-1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The max results to be requested by this SLP agent (UA only). See: 'net.slp.maxResults in SLP API (RFC 2614)." ::= { slpNetworkEntry 10 } slpNetworkTraceDATraffic OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable trace DA message traffic for one or all SLP agents. See: 'net.slp.traceDATraffic' in SLP API (RFC 2614)." DEFVAL { false } -- disable trace ::= { slpNetworkEntry 11 } slpNetworkTraceMsg OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable trace all message traffic for one or all SLP agents. See: 'net.slp.traceMsg' in SLP API (RFC 2614)." DEFVAL { false } -- disable trace ::= { slpNetworkEntry 12 } slpNetworkTraceDrop OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable trace dropped message traffic for one or all SLP agents. See: 'net.slp.traceDrop' in SLP API (RFC 2614)." DEFVAL { false } -- disable trace ::= { slpNetworkEntry 13 } Bakke, McDonald Expires 20 May 2002 [Page 37] Internet Draft Service Location Protocol MIB 20 November 2001 slpNetworkTraceReg OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Enable trace registrations/deregistrations for one or all SLP agents. See: 'net.slp.traceReg' in SLP API (RFC 2614)." DEFVAL { false } -- disable trace ::= { slpNetworkEntry 14 } -- -- slpInterface OBJECT IDENTIFIER ::= { slpMIBObjects 6 } slpInterfaceRows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpInterfaceTable', including any rows in 'notInService' or other inactive states." ::= { slpInterface 2 } slpInterfaceMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpInterfaceTable'." ::= { slpInterface 3 } slpInterfaceNextListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Next available (unused) value of 'slpInterfaceListIndex', for use with 'createAnd[Go|Wait]' in 'slpInterfaceRowStatus'." ::= { slpInterface 4 } slpInterfaceUseCommonList OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If 'true', then there MAY be one list in 'slpInterfaceTable', Bakke, McDonald Expires 20 May 2002 [Page 38] Internet Draft Service Location Protocol MIB 20 November 2001 with 'slpInterfaceListIndex' fixed at a REQUIRED value of '1', and all SLP agents installed on this managed system MUST share and use this single common list of interfaces. If 'false', then there MAY be a list in 'slpInterfaceTable', 'slpInterfaceListIndex' MUST correspond to 'slpAgentIndex', for each SLP agent installed on this managed system (i.e., interface lists are disjoint and are NOT shared). Usage: Interface lists consist of one or more rows in the 'slpInterfaceTable' (one row per interface) for each list. Usage: Management stations SHOULD reset the managed system when they change the value of this object with a Set operation, since the resulting configuration would otherwise be corrupted." DEFVAL { true } ::= { slpInterface 5 } slpInterfaceTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for interface lists on this managed system. Usage: This table sparsely augments the 'slpAgentTable' (either with one or a set of interface lists). Usage: Interface lists consist of one or more rows in the 'slpInterfaceTable' (one row per interface) for each list." ::= { slpInterface 1 } slpInterfaceEntry OBJECT-TYPE SYNTAX SlpInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing SLP (Service Location Protocol) objects for one interface on this managed system." INDEX { slpInterfaceListIndex, slpInterfaceItemIndex } ::= { slpInterfaceTable 1 } SlpInterfaceEntry ::= SEQUENCE { slpInterfaceListIndex Integer32 (1..2147483647), slpInterfaceItemIndex Integer32 (1..2147483647), slpInterfaceRowStatus RowStatus, slpInterfaceIfIndexOrZero Integer32 (0..2147483647), slpInterfaceTimerListIndex Integer32 (0..2147483647), slpInterfaceNetworkListIndex Integer32 (0..2147483647), Bakke, McDonald Expires 20 May 2002 [Page 39] Internet Draft Service Location Protocol MIB 20 November 2001 slpInterfaceAddressOrName SnmpAdminString (SIZE (0..64)) } slpInterfaceListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual list of rows in 'slpInterfaceTable'. Usage: For a given value of 'slpAgentIndex', the corresponding value of 'slpInterfaceListIndex' is the same OR is equal to '1', according to the current value of 'slpInterfaceUseCommonList'." ::= { slpInterfaceEntry 1 } slpInterfaceItemIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual single row in 'slpInterfaceTable', subordinate to 'slpInterfaceListIndex'." ::= { slpInterfaceEntry 2 } slpInterfaceRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row in 'slpInterfaceTable'." ::= { slpInterfaceEntry 3 } slpInterfaceIfIndexOrZero OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of 'ifIndex' in the 'ifTable' in MIB-II (RFC 1213) for this interface, or zero if none. See: 'ifIndex' in MIB-II (RFC 1213)." DEFVAL { 0 } -- no 'ifTable' pointer ::= { slpInterfaceEntry 4 } slpInterfaceTimerListIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of 'slpTimerListIndex' for timer config overrides for this interface, or zero if no overrides (use the value of Bakke, McDonald Expires 20 May 2002 [Page 40] Internet Draft Service Location Protocol MIB 20 November 2001 'slpInterfaceListIndex' or '1' for 'slpTimerListIndex' according to the current value of 'slpTimerUseCommonList'). See: 'slpTimerListIndex' above in this SLP MIB." DEFVAL { 0 } -- no timer config overrides ::= { slpInterfaceEntry 5 } slpInterfaceNetworkListIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of 'slpNetworkListIndex' for network config overrides for this interface, or zero if no overrides (use the value of 'slpInterfaceListIndex' or '1' for 'slpNetworkListIndex' according to the current value of 'slpNetworkUseCommonList'). See: 'slpNetworkListIndex' above in this SLP MIB." DEFVAL { 0 } -- no network config overrides ::= { slpInterfaceEntry 6 } slpInterfaceAddressOrName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-create STATUS current DESCRIPTION "Text formatted (dotted decimal) IPv4 address; or (per RFC 2373) text formatted (colon-delimited hexadecimal) IPv6 address; or a fully qualifed DNS name for this interface. For example '13.281.11.12' or '3FFE:2A00:100:7031::1'. See: IP Version 6 Addressing Architecture (RFC 2373). See: Format for Literal IPv6 Addresses in URLs (RFC 2732). See: 'net.slp.interfaces' in SLP API (RFC 2614)." ::= { slpInterfaceEntry 7 } -- -- slpAddress OBJECT IDENTIFIER ::= { slpMIBObjects 7 } slpAddressRows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpAddressTable', including any rows in 'notInService' or other inactive states." Bakke, McDonald Expires 20 May 2002 [Page 41] Internet Draft Service Location Protocol MIB 20 November 2001 ::= { slpAddress 2 } slpAddressMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpAddressTable'." ::= { slpAddress 3 } slpAddressNextListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Next available (unused) value of 'slpAddressListIndex', for use with 'createAnd[Go|Wait]' in 'slpAddressRowStatus'." ::= { slpAddress 4 } slpAddressUseCommonList OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If 'true', then there MAY be one list in 'slpAddressTable', with 'slpAddressListIndex' fixed at a REQUIRED value of '1', and all SLP agents installed on this managed system MUST share and use this single common list of DA/SA addresses. If 'false', then there MAY be a list in 'slpAddressTable', 'slpAddressListIndex' MUST correspond to 'slpAgentIndex', for each SLP agent installed on this managed system (i.e., DA/SA address lists are disjoint and are NOT shared). Usage: DA/SA Address lists consist of one or more rows in the 'slpAddressTable' (one row per DA/SA address) for each list. Usage: Management stations SHOULD reset the managed system when they change the value of this object with a Set operation, since the resulting configuration would otherwise be corrupted." DEFVAL { true } ::= { slpAddress 5 } slpAddressTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpAddressEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for remote DA/SA address lists known to this managed system. Bakke, McDonald Expires 20 May 2002 [Page 42] Internet Draft Service Location Protocol MIB 20 November 2001 Usage: This table sparsely augments the 'slpAgentTable' (either with one or a set of DA/SA address lists). Usage: DA Address lists consist of one or more rows in the 'slpAddressTable' (one row per DA address) for each list." ::= { slpAddress 1 } slpAddressEntry OBJECT-TYPE SYNTAX SlpAddressEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing SLP (Service Location Protocol) objects for one remote DA or SA address known to this managed system." INDEX { slpAddressListIndex, slpAddressItemIndex } ::= { slpAddressTable 1 } SlpAddressEntry ::= SEQUENCE { slpAddressListIndex Integer32 (1..2147483647), slpAddressItemIndex Integer32 (1..2147483647), slpAddressRowStatus RowStatus, slpAddressAgentType SlpAgentType, slpAddressSource SlpScopeSource, slpAddressOrName SnmpAdminString (SIZE (0..64)) } slpAddressListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual list of rows in 'slpAddressTable'. Usage: For a given value of 'slpAgentIndex', the corresponding value of 'slpAddressListIndex' is the same OR is equal to '1', according to the current value of 'slpAddressUseCommonList'." ::= { slpAddressEntry 1 } slpAddressItemIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual single row in 'slpAddressTable', subordinate to 'slpAddressListIndex'." ::= { slpAddressEntry 2 } slpAddressRowStatus OBJECT-TYPE SYNTAX RowStatus Bakke, McDonald Expires 20 May 2002 [Page 43] Internet Draft Service Location Protocol MIB 20 November 2001 MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row in 'slpAddressTable'." ::= { slpAddressEntry 3 } slpAddressAgentType OBJECT-TYPE SYNTAX SlpAgentType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of this remote SLP agent (DA or SA). See: 'net.slp.isDA' in SLP API (RFC 2614)." ::= { slpAddressEntry 4 } slpAddressSource OBJECT-TYPE SYNTAX SlpScopeSource MAX-ACCESS read-create STATUS current DESCRIPTION "The source (DHCP, etc) of this remote SLP agent address. Usage: SNMP Command Generators MUST only Set the value of this object to 'static(1)' (a statically configured SA) or 'staticDA(2)' (a statically configured DA). All other values are discovered by the SLP agent during normal operation and rows are added to the 'slpAddressTable'. See: 'slpScopeSource' above in this SLP MIB." ::= { slpAddressEntry 5 } slpAddressOrName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-create STATUS current DESCRIPTION "Text formatted (dotted decimal) IPv4 address; or (per RFC 2373) text formatted (colon-delimited hexadecimal) IPv6 address; or a fully qualifed DNS name for this remote SLP agent (DA or SA). For example '13.281.11.12' or '3FFE:2A00:100:7031::1'. See: IP Version 6 Addressing Architecture (RFC 2373). See: Format for Literal IPv6 Addresses in URLs (RFC 2732). See: 'net.slp.interfaces' in SLP API (RFC 2614)." ::= { slpAddressEntry 6 } -- Bakke, McDonald Expires 20 May 2002 [Page 44] Internet Draft Service Location Protocol MIB 20 November 2001 -- slpAttribute OBJECT IDENTIFIER ::= { slpMIBObjects 8 } slpAttributeRows OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpAttributeTable', including any rows in 'notInService' or other inactive states." ::= { slpAttribute 2 } slpAttributeMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpAttributeTable'." ::= { slpAttribute 3 } slpAttributeTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpAttributeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for DA or SA attribute lists on this managed system. Usage: This table sparsely augments the 'slpAgentTable' (UAs do not have attribute lists - DAs/SAs should have attribute lists with at least the SLP standard DA/SA attributes). Usage: Attribute lists consist of one or more rows in the 'slpAttributeTable' (one row per attribute) for each SLP agent. 'slpAttributeListIndex' MUST correspond to 'slpAgentIndex', for each SLP DA/SA installed on this managed system (i.e., attribute lists are disjoint and are NOT shared)." ::= { slpAttribute 1 } slpAttributeEntry OBJECT-TYPE SYNTAX SlpAttributeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing SLP (Service Location Protocol) objects for one DA or SA attribute on this managed system. See: 'net.slp.DAAttributes' and 'net.slp.SAAttributes' in SLP API (RFC 2614)." INDEX { slpAttributeListIndex, slpAttributeItemIndex } Bakke, McDonald Expires 20 May 2002 [Page 45] Internet Draft Service Location Protocol MIB 20 November 2001 ::= { slpAttributeTable 1 } SlpAttributeEntry ::= SEQUENCE { slpAttributeListIndex Integer32 (1..2147483647), slpAttributeItemIndex Integer32 (1..2147483647), slpAttributeRowStatus RowStatus, slpAttributeName SnmpAdminString (SIZE (0..64)), slpAttributeType SlpAttributeType, slpAttributeValue SnmpAdminString (SIZE (0..255)) } slpAttributeListIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual list of rows in 'slpAttributeTable'. Usage: For a given value of 'slpAgentIndex', the corresponding value of 'slpAttributeListIndex' is the same." ::= { slpAttributeEntry 1 } slpAttributeItemIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual single row in 'slpAttributeTable', subordinate to 'slpAttributeListIndex'." ::= { slpAttributeEntry 2 } slpAttributeRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row in 'slpAttributeTable'." ::= { slpAttributeEntry 3 } slpAttributeName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-create STATUS current DESCRIPTION "The name of this SLP attribute. For example 'printer-resolution-supported' in the 'service:printer' IANA registered service template. See: Section 5 'Service Attributes' in SLPv2 (RFC 2608)." ::= { slpAttributeEntry 4 } Bakke, McDonald Expires 20 May 2002 [Page 46] Internet Draft Service Location Protocol MIB 20 November 2001 slpAttributeType OBJECT-TYPE SYNTAX SlpAttributeType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of this SLP attribute. For example 'attrBoolean' for a string formatted boolean. See: Section 5 'Service Attributes' in SLPv2 (RFC 2608)." ::= { slpAttributeEntry 5 } slpAttributeValue OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this SLP attribute: a) A UTF-8 string if 'slpAttributeType' is 'attrBoolean', 'attrInteger', or 'attrString' b) an escaped string if 'slpAttributeType' is 'attrOpaque'; or c) an empty string if 'slpAttributeType' is 'attrKeyword'. See: Section 5 'Service Attributes' in SLPv2 (RFC 2608)." ::= { slpAttributeEntry 6 } -- -- slpCounter OBJECT IDENTIFIER ::= { slpMIBObjects 9 } slpCounterTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpCounterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP counter objects (instrumentation) for all of the SLP directory agents (DAs), service agents (SAs), or user agents (UAs) currently installed and (possibly) active on this managed system. Note: The object descriptors used in this table all end in plural nouns, per section 3.1 in SMIv2 (RFC 2578)." ::= { slpCounter 1 } slpCounterEntry OBJECT-TYPE SYNTAX SlpCounterEntry MAX-ACCESS not-accessible STATUS current Bakke, McDonald Expires 20 May 2002 [Page 47] Internet Draft Service Location Protocol MIB 20 November 2001 DESCRIPTION "An entry containing SLP counter objects (instrumentation) for one of the SLP directory agents (DAs), service agents (SAs), or user agents (UAs) currently installed and (possibly) active on this managed system." AUGMENTS { slpAgentEntry } ::= { slpCounterTable 1 } SlpCounterEntry ::= SEQUENCE { slpCounterIncomingBroadcastMsgs Counter32, slpCounterIncomingMulticastMsgs Counter32, slpCounterIncomingUnicastMsgs Counter32, slpCounterIncomingRequests Counter32, slpCounterDroppedRequests Counter32, slpCounterRegistrations Counter32, slpCounterDeregistrations Counter32, slpCounterParseErrors Counter32, slpCounterScopeErrors Counter32, slpCounterLanguageErrors Counter32, slpCounterAuthenticationErrors Counter32, slpCounterBusyErrors Counter32, slpCounterRegistrationErrors Counter32, slpCounterNotSupportedErrors Counter32 } slpCounterIncomingBroadcastMsgs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of incoming broadcast messages to this SLP agent." ::= { slpCounterEntry 1 } slpCounterIncomingMulticastMsgs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of incoming multicast messages to this SLP agent." ::= { slpCounterEntry 2 } slpCounterIncomingUnicastMsgs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of incoming unicast messages to this SLP agent." ::= { slpCounterEntry 3 } slpCounterIncomingRequests OBJECT-TYPE Bakke, McDonald Expires 20 May 2002 [Page 48] Internet Draft Service Location Protocol MIB 20 November 2001 SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of incoming request messages to this SLP agent." ::= { slpCounterEntry 4 } slpCounterDroppedRequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of dropped incoming requests to this SLP agent." ::= { slpCounterEntry 5 } slpCounterRegistrations OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of successful registration (SrvReg) events. See: Section 8.3 'Service Registration' SLPv2 (RFC 2608)." ::= { slpCounterEntry 6 } slpCounterDeregistrations OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of successful deregistration (SrvDeReg) events. See: Section 8.3 'Service Registration' SLPv2 (RFC 2608)." ::= { slpCounterEntry 7 } slpCounterParseErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of PARSE_ERROR errors (RFC 2608)." ::= { slpCounterEntry 8 } slpCounterScopeErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of SCOPE_NOT_SUPPORTED errors (RFC 2608)." ::= { slpCounterEntry 9 } Bakke, McDonald Expires 20 May 2002 [Page 49] Internet Draft Service Location Protocol MIB 20 November 2001 slpCounterLanguageErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of LANGUAGE_NOT_SUPPORTED errors (RFC 2608)." ::= { slpCounterEntry 10 } slpCounterAuthenticationErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of AUTHENTICATION[UNKNOWN|ABSENT|FAILED] (RFC 2608)." ::= { slpCounterEntry 11 } slpCounterBusyErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of DA_BUSY_NOW errors (RFC 2608)." ::= { slpCounterEntry 12 } slpCounterRegistrationErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of INVALID_[REGISTRATION|UPDATE] or REFRESH_REJECTED errors (RFC 2608)." ::= { slpCounterEntry 13 } slpCounterNotSupportedErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of [VER|MSG]_NOT_SUPPORTED or OPTION_NOT_UNDERSTOOD errors (RFC 2608)." ::= { slpCounterEntry 14 } -- -- slpTrace OBJECT IDENTIFIER ::= { slpMIBObjects 10 } slpTraceRows OBJECT-TYPE SYNTAX Gauge32 Bakke, McDonald Expires 20 May 2002 [Page 50] Internet Draft Service Location Protocol MIB 20 November 2001 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of rows currently instantiated in 'slpTraceTable'." ::= { slpTrace 2 } slpTraceMaxRows OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum rows concurrently supported in 'slpTraceTable'." ::= { slpTrace 3 } slpTraceNextTraceIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Next available (unused) value of 'slpTraceIndex', for use by this managed system in recording trace info." ::= { slpTrace 4 } slpTraceTable OBJECT-TYPE SYNTAX SEQUENCE OF SlpTraceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for recording SLP agent incoming/outgoing message traffic traces on this managed system. Usage: Traces are enabled by 'slpNetworkTraceDATraffic', 'slpNetworkTraceMsg', 'slpNetworkTraceDrop', and 'slpNetworkTraceReg' in the 'slpNetworkTable'. Usage: All traffic traces are merged into a single running list which is strictly temporally ordered by 'slpTraceIndex' and is timestamped in 'slpTraceTimeStamp'. Usage: When the 'slpTraceTable' reaches the maximum supported rows (see 'slpTraceMaxRows' above), then the oldest row (lowest 'slpTraceIndex' value) MUST be deleted by the SLP MIB agent to 'make room' for the next row (new highest 'slpTraceIndex'). See: 'slpAdminDeleteTraces' operation above in this SLP MIB." ::= { slpTrace 1 } slpTraceEntry OBJECT-TYPE SYNTAX SlpTraceEntry MAX-ACCESS not-accessible Bakke, McDonald Expires 20 May 2002 [Page 51] Internet Draft Service Location Protocol MIB 20 November 2001 STATUS current DESCRIPTION "A table containing SLP (Service Location Protocol) objects for one traced message on this managed system." INDEX { slpTraceIndex } ::= { slpTraceTable 1 } SlpTraceEntry ::= SEQUENCE { slpTraceIndex Integer32 (1..2147483647), slpTraceAgentIndex Integer32 (1..2147483647), slpTraceInterfaceListIndex Integer32 (0..2147483647), slpTraceTimeStamp TimeStamp, slpTraceMessageType SlpMessageType, slpTraceMessageSourceAddress SnmpAdminString (SIZE (0..64)), slpTraceMessageErrorCode Unsigned32 (0..65535), slpTraceMessageLocale SnmpAdminString (SIZE (0..64)), slpTraceMessageScopes SnmpAdminString (SIZE (0..64)), slpTraceMessageServiceTypeOrURL SnmpAdminString (SIZE (0..64)), slpTraceMessageBody SnmpAdminString (SIZE (0..255)) } slpTraceIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Ordinal of this conceptual row in 'slpTraceTable'." ::= { slpTraceEntry 1 } slpTraceAgentIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of 'slpAgentIndex' for this traced message." ::= { slpTraceEntry 2 } slpTraceInterfaceListIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The value of 'slpInterfaceListIndex' for this traced message, or zero if none." ::= { slpTraceEntry 3 } slpTraceTimeStamp OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current Bakke, McDonald Expires 20 May 2002 [Page 52] Internet Draft Service Location Protocol MIB 20 November 2001 DESCRIPTION "The value of 'sysUpTime' in MIB-II (RFC 1213) when this traced message was recorded in the 'slpTraceTable'." ::= { slpTraceEntry 4 } slpTraceMessageType OBJECT-TYPE SYNTAX SlpMessageType MAX-ACCESS read-only STATUS current DESCRIPTION "The SLP message type (Function-ID) of this traced message. See: 'slpAgentMessageTypesSupported' above in this SLP MIB. See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608)." ::= { slpTraceEntry 5 } slpTraceMessageSourceAddress OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-create STATUS current DESCRIPTION "Text formatted (dotted decimal) IPv4 address; or (per RFC 2373) text formatted (colon-delimited hexadecimal) IPv6 address. For example '13.281.11.12' or '3FFE:2A00:100:7031::1'. See: IP Version 6 Addressing Architecture (RFC 2373). See: Format for Literal IPv6 Addresses in URLs (RFC 2732). See: 'slpAddressOrName' above in this SLP MIB. See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608). See: 'net.slp.interfaces' in SLP API (RFC 2614)." ::= { slpTraceEntry 6 } slpTraceMessageErrorCode OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The SLPv2 (RFC 2608) error code for this traced message. See: Section 7 'Errors' in SLPv2 (RFC 2608)." ::= { slpTraceEntry 7 } slpTraceMessageLocale OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-create STATUS current Bakke, McDonald Expires 20 May 2002 [Page 53] Internet Draft Service Location Protocol MIB 20 November 2001 DESCRIPTION "The SLP message locale for this traced message, expressed as a language tag (RFC 3066). For example 'en' means 'English' and 'no-nynorsk' is one of two official versions of Norwegian. See: 'slpAgentLocale' and 'slpAgentLocalesSupported' above in this SLP MIB. See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608). See: 'net.slp.locale' in SLP API (RFC 2614)." ::= { slpTraceEntry 8 } slpTraceMessageScopes OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-only STATUS current DESCRIPTION "One or more scopes from this traced message, expressed as a list of scope values (RFC 2608). See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608). See: 'net.slp.useScopes' in SLP API (RFC 2614)." ::= { slpTraceEntry 9 } slpTraceMessageServiceTypeOrURL OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-only STATUS current DESCRIPTION "The service type or service URL in this traced message. For example 'service:printer:ipp'. See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608). See: 'service-types' attribute in 'service:service-agent' in IANA Registry of Service Location Templates." ::= { slpTraceEntry 10 } slpTraceMessageBody OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "The first portion of the body of this traced message, text formatted for human-readable access. See: Section 8 'Required SLP Messages' in SLPv2 (RFC 2608)." ::= { slpTraceEntry 11 } Bakke, McDonald Expires 20 May 2002 [Page 54] Internet Draft Service Location Protocol MIB 20 November 2001 -- -- slpAlertPrefix OBJECT IDENTIFIER ::= { slpMIBNotifications 0 } slpAlertRegistration NOTIFICATION-TYPE OBJECTS { slpTraceAgentIndex, slpTraceMessageSourceAddress, slpTraceMessageScopes, slpTraceMessageServiceTypeOrURL, slpTraceMessageBody } STATUS current DESCRIPTION "This SMIv2 (RFC 2578) SNMPv2/v3 notification signals a successful SLP service registration (SrvReg) event. See: Notification and Subscription for SLP (RFC 3082). See: Section 8.3 'Service Registration' SLPv2 (RFC 2608)." ::= { slpAlertPrefix 1 } slpAlertDeregistration NOTIFICATION-TYPE OBJECTS { slpTraceAgentIndex, slpTraceMessageSourceAddress, slpTraceMessageScopes, slpTraceMessageServiceTypeOrURL } STATUS current DESCRIPTION "This SMIv2 (RFC 2578) SNMPv2/v3 notification signals a successful SLP service deregistration (SrvDeReg) event. See: Notification and Subscription for SLP (RFC 3082). See: Section 8.3 'Service Registration' SLPv2 (RFC 2608)." ::= { slpAlertPrefix 2 } slpAlertProtocolError NOTIFICATION-TYPE OBJECTS { slpTraceAgentIndex, slpTraceMessageType, slpTraceMessageSourceAddress, slpTraceMessageScopes, slpTraceMessageServiceTypeOrURL, slpTraceMessageErrorCode } Bakke, McDonald Expires 20 May 2002 [Page 55] Internet Draft Service Location Protocol MIB 20 November 2001 STATUS current DESCRIPTION "This SMIv2 (RFC 2578) SNMPv2/v3 notification signals an SLPv2 (RFC 2608) protocol error. See: Section 7 'Errors' in SLPv2 (RFC 2608)." ::= { slpAlertPrefix 3 } -- -- slpMIBCompliancev1 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statements for SNMP Command Responders that implement the Service Location Protocol MIB." MODULE -- this module MANDATORY-GROUPS { slpAdminGroup, slpAgentGroup, slpScopeGroup, slpTimerGroup, slpNetworkGroup } GROUP slpInterfaceGroup DESCRIPTION "Interface Group" GROUP slpAddressGroup DESCRIPTION "Address Group" GROUP slpAttributeGroup DESCRIPTION "Attribute Group" GROUP slpCounterGroup DESCRIPTION "Counter Group" GROUP slpTraceGroup DESCRIPTION "Trace Group" GROUP slpAlertGroup DESCRIPTION "Alert Group - notifications" OBJECT slpAgentRowStatus Bakke, McDonald Expires 20 May 2002 [Page 56] Internet Draft Service Location Protocol MIB 20 November 2001 SYNTAX INTEGER { active(1), notInService(2) } MIN-ACCESS read-write DESCRIPTION "It is conformant to implement this object as read-write, and only two of the enumerated values for the 'RowStatus' textual convention need be supported." OBJECT slpScopeRowStatus SYNTAX INTEGER { active(1), notInService(2) } MIN-ACCESS read-write DESCRIPTION "It is conformant to implement this object as read-write, and only two of the enumerated values for the 'RowStatus' textual convention need be supported." OBJECT slpTimerRowStatus SYNTAX INTEGER { active(1), notInService(2) } MIN-ACCESS read-write DESCRIPTION "It is conformant to implement this object as read-write, and only two of the enumerated values for the 'RowStatus' textual convention need be supported." OBJECT slpNetworkRowStatus SYNTAX INTEGER { active(1), notInService(2) } MIN-ACCESS read-write DESCRIPTION "It is conformant to implement this object as read-write, and only two of the enumerated values for the 'RowStatus' textual convention need be supported." OBJECT slpInterfaceRowStatus SYNTAX INTEGER { active(1), notInService(2) } MIN-ACCESS read-write DESCRIPTION "It is conformant to implement this object as read-write, and only two of the enumerated values for the 'RowStatus' textual convention need be supported." OBJECT slpAddressRowStatus SYNTAX INTEGER { active(1), notInService(2) } MIN-ACCESS read-write DESCRIPTION "It is conformant to implement this object as read-write, and only two of the enumerated values for the 'RowStatus' textual convention need be supported." OBJECT slpAttributeRowStatus SYNTAX INTEGER { active(1), notInService(2) } MIN-ACCESS read-write DESCRIPTION Bakke, McDonald Expires 20 May 2002 [Page 57] Internet Draft Service Location Protocol MIB 20 November 2001 "It is conformant to implement this object as read-write, and only two of the enumerated values for the 'RowStatus' textual convention need be supported." ::= { slpMIBConformance 1 } -- -- slpAdminGroup OBJECT-GROUP OBJECTS { slpAdminSessionActive, slpAdminSessionStartTime, slpAdminSessionLeaseTime, slpAdminSessionSerialNo, slpAdminSessionOwner, slpAdminCreateRow, slpAdminDestroyRow, slpAdminModifyObject, slpAdminClearCounters, slpAdminDeleteTraces } STATUS current DESCRIPTION "The Admin object group in the SLP MIB" ::= { slpMIBObjectGroups 1 } slpAgentGroup OBJECT-GROUP OBJECTS { slpAgentRows, slpAgentMaxRows, slpAgentNextAgentIndex, slpAgentRowStatus, slpAgentSWInstalledIndexOrZero, slpAgentName, slpAgentType, slpAgentLastRebootTime, slpAgentLocale, slpAgentLocalesSupported, slpAgentMessageTypesSupported, slpAgentExtensionsSupported, slpAgentSerializedRegURL, slpAgentTypeHint, slpAgentServiceTypes } STATUS current DESCRIPTION "The Agent object group in the SLP MIB" ::= { slpMIBObjectGroups 2 } Bakke, McDonald Expires 20 May 2002 [Page 58] Internet Draft Service Location Protocol MIB 20 November 2001 slpScopeGroup OBJECT-GROUP OBJECTS { slpScopeRows, slpScopeMaxRows, slpScopeNextListIndex, slpScopeUseCommonList, slpScopeRowStatus, slpScopeSource, slpScopeValue } STATUS current DESCRIPTION "The Scope object group in the SLP MIB" ::= { slpMIBObjectGroups 3 } slpTimerGroup OBJECT-GROUP OBJECTS { slpTimerRows, slpTimerMaxRows, slpTimerNextListIndex, slpTimerUseCommonList, slpTimerRowStatus, slpTimerDAActiveDiscInterval, slpTimerMulticastMaximumWait, slpTimerDAHeartBeat, slpTimerCloseConnectionWait, slpTimerRandomWaitBound, slpTimerMulticastTimeouts, slpTimerDADiscoveryTimeouts, slpTimerDatagramTimeouts } STATUS current DESCRIPTION "The Timer object group in the SLP MIB" ::= { slpMIBObjectGroups 4 } slpNetworkGroup OBJECT-GROUP OBJECTS { slpNetworkRows, slpNetworkMaxRows, slpNetworkNextListIndex, slpNetworkUseCommonList, slpNetworkRowStatus, slpNetworkEnableSecurity, slpNetworkEnableAlertTypes, slpNetworkIsBroadcastOnly, slpNetworkEnableDADiscovery, slpNetworkPassiveDADiscovery, slpNetworkMulticastTTL, slpNetworkMTU, Bakke, McDonald Expires 20 May 2002 [Page 59] Internet Draft Service Location Protocol MIB 20 November 2001 slpNetworkMaxResults, slpNetworkTraceDATraffic, slpNetworkTraceMsg, slpNetworkTraceDrop, slpNetworkTraceReg } STATUS current DESCRIPTION "The Network object group in the SLP MIB" ::= { slpMIBObjectGroups 5 } slpInterfaceGroup OBJECT-GROUP OBJECTS { slpInterfaceRows, slpInterfaceMaxRows, slpInterfaceNextListIndex, slpInterfaceUseCommonList, slpInterfaceRowStatus, slpInterfaceIfIndexOrZero, slpInterfaceTimerListIndex, slpInterfaceNetworkListIndex, slpInterfaceAddressOrName } STATUS current DESCRIPTION "The Interface object group in the SLP MIB" ::= { slpMIBObjectGroups 6 } slpAddressGroup OBJECT-GROUP OBJECTS { slpAddressRows, slpAddressMaxRows, slpAddressNextListIndex, slpAddressUseCommonList, slpAddressRowStatus, slpAddressAgentType, slpAddressSource, slpAddressOrName } STATUS current DESCRIPTION "The Address object group in the SLP MIB" ::= { slpMIBObjectGroups 7 } slpAttributeGroup OBJECT-GROUP OBJECTS { slpAttributeRows, slpAttributeMaxRows, slpAttributeRowStatus, slpAttributeName, slpAttributeType, Bakke, McDonald Expires 20 May 2002 [Page 60] Internet Draft Service Location Protocol MIB 20 November 2001 slpAttributeValue } STATUS current DESCRIPTION "The Attribute object group in the SLP MIB" ::= { slpMIBObjectGroups 8 } slpCounterGroup OBJECT-GROUP OBJECTS { slpCounterIncomingBroadcastMsgs, slpCounterIncomingMulticastMsgs, slpCounterIncomingUnicastMsgs, slpCounterIncomingRequests, slpCounterDroppedRequests, slpCounterRegistrations, slpCounterDeregistrations, slpCounterParseErrors, slpCounterScopeErrors, slpCounterLanguageErrors, slpCounterAuthenticationErrors, slpCounterBusyErrors, slpCounterRegistrationErrors, slpCounterNotSupportedErrors } STATUS current DESCRIPTION "The Counter object group in the SLP MIB" ::= { slpMIBObjectGroups 9 } slpTraceGroup OBJECT-GROUP OBJECTS { slpTraceRows, slpTraceMaxRows, slpTraceNextTraceIndex, slpTraceAgentIndex, slpTraceInterfaceListIndex, slpTraceTimeStamp, slpTraceMessageType, slpTraceMessageSourceAddress, slpTraceMessageErrorCode, slpTraceMessageLocale, slpTraceMessageScopes, slpTraceMessageServiceTypeOrURL, slpTraceMessageBody } STATUS current DESCRIPTION "The Trace object group in the SLP MIB" ::= { slpMIBObjectGroups 10 } slpAlertGroup NOTIFICATION-GROUP Bakke, McDonald Expires 20 May 2002 [Page 61] Internet Draft Service Location Protocol MIB 20 November 2001 NOTIFICATIONS { slpAlertRegistration, slpAlertDeregistration, slpAlertProtocolError } STATUS current DESCRIPTION "The Alert notification group in the SLP MIB" ::= { slpMIBNotifyGroups 1 } END Bakke, McDonald Expires 20 May 2002 [Page 62] Internet Draft Service Location Protocol MIB 20 November 2001 6. Usage Examples 6.1. Start Admin Session [to be supplied] 6.2. Configure SLP Directory Agent [to be supplied] 6.3. Configure SLP Service Agent [to be supplied] 6.4. Configure SLP User Agent [to be supplied] 7. IANA Considerations IANA should assign a base arc in the 'mgmt' (standards track) OID tree for the objects defined in the SLP MIB. The following definitions in the SLP MIB depend on IANA registrations: o Textual convention "SlpMessageType" defines an enumeration for all of the SLPv2 [RFC2608] message types. Additional IANA registered SLPv2 message types SHOULD be documented in the next revision of this SLP MIB. This version of the SLP MIB assigns labels "msgNN" for the future SLP message types "12" through "20" for forward compatibility. o "slpAgentLocalesSupported" contains a comma-delimited list of language tags [RFC3066] which may be IANA registered. o "slpAgentMessageTypesSupported" contains a comma-delimited list of the decimal values assigned by SLPv2 [RFC2608] or assigned by IANA for the Function-ID in SLPv2 messages. o "slpAgentExtensionsSupported" contains a comma-delimited list of the decimal values assigned by SLPv2 [RFC2608] or assigned by Bakke, McDonald Expires 20 May 2002 [Page 63] Internet Draft Service Location Protocol MIB 20 November 2001 IANA for the Extension ID in SLPv2 messages. o "slpAgentServiceTypes" contains a comma-delimited list of SLP service types [RFC2609] which may be IANA registered. There are no other IANA considerations associated with the SLP MIB. 8. Internationalization Considerations The SLPv2 protocol [RFC2608] transfers all text strings in UTF-8 [RFC2279] using language tags [RFC3066]. The SLP MIB defines all text strings with a syntax of 'SnmpAdminString' [RFC2571] which supports human-readable information in UTF-8 [RFC2279]. The SLP MIB defines all text strings using language tags [RFC3066]. The SLP MIB is therefore in full conformance with the best practices in "IETF Policy on Character Sets and Languages" [RFC2277]. The SLP MIB provides access to information about the human natural languages supported by an SLP MIB implementation and the corresponding managed SLPv2 [RFC2608] protocol implementation(s). In particular, the following columnar objects are defined: o "slpAgentLocalesSupported" - a list of language tags [RFC3066] for the locales supported by each SLP agent in the "slpAgentTable" o "slpAgentLocale" - tags the text strings for each configured SLP agent in the "slpAgentTable" and "slpAttributeTable" o "slpTraceMessageLocale" - tags the text strings for each traced message recorded in the "slpTraceTable" 9. Security Considerations There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. In particular, this MIB defines the following read-create objects: o "slpNetworkEnableSecurity" - a boolean to enable SLPv2 [RFC2608] native security for a given SLPv2 agent (DA, SA, or UA) - if Bakke, McDonald Expires 20 May 2002 [Page 64] Internet Draft Service Location Protocol MIB 20 November 2001 'true' then SLPv2 SPI (Security Parameter Index) strings SHOULD be mapped directly to values of the SNMPv3 User-based Security Model MIB [RFC2574] object 'usmUserSecurityName' and the corresponding public keys SHOULD be be mapped directly to values of 'usmUserPublic' o "slpNetworkEnableAlertTypes" - a bit-mask to enable/disable the defined SNMP notifications for a given SLPv2 agent (DA, SA, or UA) There are a number of managed objects in this MIB that may contain sensitive information. These include: o "slpAdminSessionActive" - a boolean SLP management session state (active/inactive) o "slpAdminSessionOwner" - an internationalized owner string for the SLP management session - a refinement of 'OwnerString' [RFC2819]. These two objects reveal potentially sensitive information about the existence and identification of management stations and their operators. It is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [RFC2574] and the View- based Access Control Model RFC 2575 [RFC2575] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, 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. Bakke, McDonald Expires 20 May 2002 [Page 65] Internet Draft Service Location Protocol MIB 20 November 2001 10. Acknowledgements 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 the requirements for this SLP MIB for SLPv2; and Jim Muchow (Cisco) for his helpful comments on the ASN.1 structure and compliance macros in this SLP MIB. 11. References [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. [RFC1738] T. Berners-Lee, L. Masinter, M. McCahill. "Uniform Resource Locators (URL)", RFC 1738, December 1994. [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 Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [RFC1906] J. Case, K. McCloghrie, M. Rose, S. Waldbusser. "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [RFC1907] J. Case, K. McCloghrie, M. Rose, S. Waldbusser. "Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1907, January 1996. Bakke, McDonald Expires 20 May 2002 [Page 66] Internet Draft Service Location Protocol MIB 20 November 2001 [RFC2119] S. Bradner. "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. [RFC2277] H. Alvestrand. "IETF Policy on Character Sets and Languages", RFC 2277, January 1998. [RFC2279] F. Yergeau. "UTF-8, a Transformation of ISO 10646", RFC 2279, January 1998. [RFC2396] T. Berners-Lee, R. Fielding, L. Masinter. "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [RFC2570] J. Case, R. Mundy, D. Partain, B. Stewart. "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2571] B. Wijnen, D. Harrington, R. Presuhn. "An Architecture for Describing SNMP Network Management Frameworks", RFC 2571, April 1999. [RFC2572] J. Case, D. Harrington, R. Presuhn, B. Wijnen. "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2573] D. Levi, P. Meyer, B. Stewart. "SNMP Applications", RFC 2573, 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 Control Model for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [RFC2578] K. McCloghrie, D. Perkins, J. Shoenwaelder. "Structure of Management Information Version 2 (SMIv2)", RFC 2578, April 1999. [RFC2579] K. McCloghrie, D. Perkins, J. Shoenwaelder. "Textual Conventions 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. Bakke, McDonald Expires 20 May 2002 [Page 67] Internet Draft Service Location Protocol MIB 20 November 2001 [RFC2609] E. Guttman, C. Perkins, J. Kempf. "Service Templates and Service: Schemes", RFC 2609, June 1999. [RFC2610] C. Perkins, E. Guttman. "DHCP Options for Service Location Protocol", RFC 2610, June 1999. [RFC2614] J. Kempf, E. Guttman. "An API for Service Location", RFC 2614, June 1999. [RFC3059] E. Guttman. "Attribute List Extension for the Service Location Protocol", RFC 3059, February 2001. [RFC3066] H. Alvestrand. "Tags for the Identification of Languages", RFC 3066, January 2001. [RFC3082] J. Kempf, J. Goldschmidt. "Notification and Subscription for SLP", RFC 3082, March 2001. [RFC3111] E. Guttman. "Service Location Protocol Modifications for IPv6", RFC 3111, May 2001. 12. Authors' Addresses Editor: Mark Bakke Postal: Cisco Systems Inc 6450 Wedgwood Road, Suite 130 Maple Grove, MN 55311 USA Tel: +1 763-398-1000 Email: mbakke@cisco.com Editor: Ira McDonald Postal: High North Inc 221 Ridge Ave Grand Marais, MI 49839 USA Tel: +1 906-494-2434 Email: imcdonald@crt.xerox.com" Bakke, McDonald Expires 20 May 2002 [Page 68] Internet Draft Service Location Protocol MIB 20 November 2001 13. Appendix I - Issues [to be deleted before publication as an RFC] ISSUE 00-1 - Should the SLP MIB integrate with SNMPv3 USM MIB [RFC2574] for SLPv2 Security Parameter Index (SPI) configuration? ISSUE 00-2 - Which object groups in the SLP MIB should be mandatory? ISSUE 00-3 - Should the Alert (trap) group be mandatory? ISSUE 01-1 - Should the SLP MIB be extended with optional groups for Services (advertised by an SA or DA) and their Service Attributes? ISSUE 01-2 - Should the 'SlpMessageTypeTC' textual convention be changed to a simple 'Integer32 (1.255)' rather than an enumeration to avoid the need for a future IANA-maintained SLP-Types MIB? 14. Appendix X - Change Log [to be deleted before publication as an RFC] 1 November 2001 - initial version 20 November 2001 - removed sub-typing of objects in SEQUENCE clauses, per 'smilint' and section 7.1.12 'Conceptual Tables' of SMIv2 [RFC 2578] - renamed all textual conventions, suffixing 'TC' to avoid names which differ only by case, per 'smilint' warning 15. Full Copyright Statement Copyright (C) The Internet Society (2001). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included 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 or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be Bakke, McDonald Expires 20 May 2002 [Page 69] Internet Draft Service Location Protocol MIB 20 November 2001 followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." Bakke, McDonald Expires 20 May 2002 [Page 70]