idnits 2.17.1 draft-ietf-svrloc-slp-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (21 November 1997) is 9653 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 82 looks like a reference -- Missing reference section? '2' on line 85 looks like a reference -- Missing reference section? '3' on line 88 looks like a reference -- Missing reference section? '4' on line 88 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 2 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Service Location Working Group Pete St. Pierre 2 INTERNET DRAFT Sun Microsystems 3 21 November 1997 5 SNMP MIB for SLP Directory Agents 6 draft-ietf-svrloc-slp-mib-00.txt 8 Status of This Memo 10 This document is a submission by the Service Location Working Group 11 of the Internet Engineering Task Force (IETF). Comments should be 12 submitted to the srvloc@corp.home.net mailing list. 14 Distribution of this memo is unlimited. 16 This document is an Internet-Draft. Internet-Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its areas, 18 and its working groups. Note that other groups may also distribute 19 working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at 23 any time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as ``work in progress.'' 26 To learn the current status of any Internet-Draft, please check 27 the ``1id-abstracts.txt'' listing contained in the Internet-Drafts 28 Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (North 29 Europe), ftp.nis.garr.it (South Europe), munnari.oz.au (Pacific Rim), 30 ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 32 Abstract 34 This memo defines a Management Information Base (MIB) for the Service 35 Location Protocol (SLP). The MIB describes the statistics and alerts 36 required to allow management of Service Location Protocol enabled 37 entities. The SLP MIB conforms to the Structure of Management 38 Information (SMI), as described in RFC 1902. It is intended for use 39 with the Simple Network Management Protocol, version 2. 41 Contents 43 Status of This Memo i 45 Abstract i 47 1. Overview 1 49 2. The SNMPv2 Network Management Framework 1 51 3. Object Definitions 2 52 3.1. Configuration Group . . . . . . . . . . . . . . . . . . . 2 53 3.2. Request Statistics Group . . . . . . . . . . . . . . . . 2 54 3.3. Scoped Request Table . . . . . . . . . . . . . . . . . . 2 55 3.4. Last Processed Request . . . . . . . . . . . . . . . . . 3 56 3.5. Alerts . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4. Definitions 3 60 5. Acknowledgments 14 62 6. References 14 64 1. Overview 66 The Service Location Protocol provides a scalable framework for 67 the discovery and selection of network services. Using this 68 protocol, computers using the Internet no longer need so much static 69 configuration of network services for network based applications. 71 The SLP MIB describes a set of attributes for managing the deployment 72 of SLP directory agents. SLP directory agents that implement this 73 MIB can be monitored to determine the usefulness of configured 74 scopes, frequency of error conditions, and various mis-configuration 75 and performance issues. 77 2. The SNMPv2 Network Management Framework 79 The SNMPv2 Network Management Framework presently consists of three 80 major components. They are: 82 - the SMI, described in RFC 1902 [1] - the mechanisms used for 83 describing and naming objects for the purpose of management. 85 - the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects 86 for the Internet suite of protocols. 88 - the protocol, STD 15, RFC 1157 [3] and/or RFC 1905 [4], - the 89 protocol for accessing managed objects. 91 The Framework permits new objects to be defined for the purpose of 92 experimentation and evaluation. 94 3. Object Definitions 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. Objects in the MIB are 98 defined using the subset of Abstract Syntax Notation One (ASN.1) 99 defined in the SMI. In particular, each object type is named by an 100 OBJECT IDENTIFIER, an administratively assigned name. The object 101 type together with an object instance serves to uniquely identify 102 a specific instantiation of the object. For human convenience, we 103 often use a textual string, termed the descriptor, to refer to the 104 object type. 106 3.1. Configuration Group 108 The first group defined in the SLP MIB is a configuration group. 109 This group describes the current operating parameters of an SLP 110 enabled entity. The elements included in this group describe how the 111 entity loaded its configuration parameters, as well as the operating 112 values. This includes the list of known scopes, multicast TTL and 113 how long the entity has been operating. 115 3.2. Request Statistics Group 117 The request statistics group collects statistics about the overall 118 operation of a Service Location Protocol directory agent. Statistics 119 are collected across all scopes this entity is configured to operate 120 within. The attributes in this group track both incomming request 121 statistics as well as outgoing replies and any errors the two 122 operations may generate. 124 3.3. Scoped Request Table 126 The request statistics group, described in the previous section, 127 provides a high level view of a directory agent's operation. In 128 order to manage deployment of multiple directory agents the SLP MIB 129 provides a ``scope indexed'' table of request activity. This table 130 is needed to determine which scopes may be overloading an agent, 131 making them good candidates for deploying on alternate directory 132 agents, elsewhere in the network. 134 3.4. Last Processed Request 136 The last processed request group contains information about the last 137 request that has been processed by a directory agent. This group 138 is needed to provide accurate information when an error occurs. It 139 may be used directly by network managers, though it is designed 140 for inclusion within error reports, as discussed in the following 141 section. 143 3.5. Alerts 145 Only one alert is currently defined. This alert is generated when a 146 directory agent is unable to correctly parse an incomming request. 147 After a parse error has occurred, an event notification is generated, 148 containing information about the originator and type of the offending 149 request, assuming they can be determined. 151 4. Definitions 153 SLP-MIB DEFINITIONS ::= BEGIN 155 IMPORTS 156 MODULE-IDENTITY, 157 NOTIFICATION-TYPE, 158 OBJECT-TYPE, 159 Integer32 160 FROM SNMPv2-SMI 161 DisplayString, 162 TimeStamp, 163 DateAndTime 164 TEXTUAL-CONVENTION 165 FROM SNMPv2-TC 166 MODULE-COMPLIANCE, 167 OBJECT-GROUP, 168 NOTIFICATION-GROUP 169 FROM SNMPv2-CONF; 171 slpMib MODULE-IDENTITY 172 LAST-UPDATED "9711140000Z" -- Nov 14, 1997" 173 ORGANIZATION "IETF SLP Working Group" 174 CONTACT-INFO "Pete St. Pierre 175 Postal: Sun Microsystems, Inc 176 901 San Antonio Ave 177 Palo Alto, CA 94303 178 U.S.A. 179 Phone: +1 650 786-5790 180 E-mail: Pete.StPierre@Eng.Sun.COM" 181 DESCRIPTION 182 "The MIB module describing the 183 management of SLP Directory Agents" 184 ::= { mib-2 TBD } 186 -- Textual conventions 187 -- In the next version, broadcast type (broadcast, multicast, 188 -- unicast), should be defined here. 190 -- SLP Directory Agent Mib objects definitions 192 slpDAMibObjects OBJECT IDENTIFIER ::= { slpMib 1 } 194 -- The slpDAConfigGroup describes the basic characteristics 195 -- of the directory agent. The group contains contact 196 -- information, in addition to the operational characteristics. 198 slpDAConfigGroup OBJECT-GROUP 199 OBJECTS { 200 slpOperator, 201 slpBootSrc, 202 slpBootHost, 203 slpUpTime, 204 slpKnownScopes, 205 slpBcastType, 206 slpMulticastTTL 207 } 208 STATUS current 209 DESCRIPTION 210 "This groups contains the basic SLP DA operational 211 parameters." 212 ::= { slpDAMibObjects 1 } 214 -- Who is responsible for this DA? 215 slpOperator OBJECT-TYPE 216 SYNTAX DisplayString 217 MAX-ACCESS read-write 218 STATUS current 219 DESCRIPTION 220 "THe name of the person responsible for the 221 configuration and operation of this Directory Agent" 222 ::= { slpDAConfigGroup 1 } 224 -- Was the configuration info from DHCP or a local file? 225 slpBootSrc OBJECT-TYPE 226 SYNTAX INTEGER { 227 dhcp(1), 228 static(2) 229 } 230 MAX-ACCESS read-only 231 STATUS current 232 DESCRIPTION 233 "The mechanism used to load the current runtime 234 configuration information." 235 ::= { slpDAConfigGroup 2 } 237 -- What is the address of the machine where the config file is 238 -- located. If the information came from a configuration file 239 -- the address should be 127.0.0.1 240 slpBootHost OBJECT-TYPE 241 SYNTAX IpAddress 242 MAX-ACCESS read-only 243 STATUS current 244 DESCRIPTION 245 "The location from where the current runtime 246 configuration information was loaded." 247 ::= { slpDAConfigGroup 3 } 249 slpUpTime OBJECT-TYPE 250 SYNTAX TimeTicks 251 MAX-ACCESS read-only 252 STATUS current 253 DESCRIPTION 254 "The time, in hundreths of a second, since the 255 SLP DA was last initialized" 256 ::= { slpDAConfigGroup 4 } 258 slpKnownScopes OBJECT-TYPE 259 SYNTAX SET OF DisplayString 260 MAX-ACCESS read-write 261 STATUS current 262 DESCRIPTION 263 "This is a list of the scopes a DA knows about. 264 Only registrations and requests within these 265 scopes will be handled by this DA" 266 ::= { slpDAConfigGroup 5 } 268 slpBcastType OBJECT-TYPE 269 SYNTAX INTEGER { 270 broadcast(1), 271 multicast(2), 272 both(3) 274 } 275 MAX-ACCESS read-only 276 STATUS current 277 DESCRIPTION 278 "This attribute indicates whether a DA has been 279 configured to respond to broadcast, multicast or 280 both types of requests." 281 ::= { slpDAConfigGroup 6 } 283 slpMulticastTTL OBJECT-TYPE 284 SYNTAX INTEGER 285 MAX-ACCESS read-only 286 STATUS current 287 DESCRIPTION 288 "The multicast TTL defines the domain within 289 which this SLP DA will send DAAdverts and other 290 multicast messages." 291 ::= { slpDAConfigGroup 7 } 293 -- The slpReqStatsGroup contains statistics about the requests 294 -- that have been processed. These statistics are totals, not 295 -- broken down by scope or other criteria. 297 slpReqStatsGroup OBJECT-GROUP 298 OBJECTS { 299 slpUnicastReqCount, 300 slpBroadcastReqCount, 301 slpMultiacstReqCount, 302 slpDiscoveryReqCount, 303 slpZeroMatchCount, 304 slpTCPRequestCount, 305 slpTCPReplyCount, 306 slpUDPReqCount, 307 slpUDPReplyCount 308 } 309 STATUS current 310 DESCRIPTION 311 "This group contains statistics related to 312 a DA handling various types of requests." 313 ::= { slpDAMibObjects 2 } 315 slpUnicastReqCount OBJECT-TYPE 316 SYNTAX Unsigned32 317 MAX-ACCESS read-only 318 STATUS current 319 DESCRIPTION 320 "The number of requests that have been 321 received by this DA via unicast" 322 ::= { slpReqStatsGroup 1 } 323 slpBroadcastReqCount OBJECT-TYPE 324 SYNTAX Unsigned32 325 MAX-ACCESS read-only 326 STATUS current 327 DESCRIPTION 328 "The number of request that have been 329 received by this DA via broadcast" 330 ::= { slpReqStatsGroup 2 } 332 slpMulticastReqCount OBJECT-TYPE 333 SYNTAX Unsigned32 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The number of request that have been 338 received by this DA via multicast" 339 ::= { slpReqStatsGroup 3 } 341 slpDiscoveryReqCount OBJECT-TYPE 342 SYNTAX Unsigned32 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The number of DA discovery requests 347 seen by this DA" 348 ::= { slpReqStatsGroup 4 } 350 slpZeroMatchCount OBJECT-TYPE 351 SYNTAX Unsigned32 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The number of times a process request 356 resulted in zero matching entries." 357 ::= { slpReqStatsGroup 5 } 359 slpTCPReqCount OBJECT-TYPE 360 SYNTAX Unsigned32 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The total number of requests received 365 via TCP" 366 ::= { slpReqStatsGroup 6 } 368 slpTCPReplyCount OBJECT-TYPE 369 SYNTAX Unsigned32 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The total number of replied generated 374 via TCP" 375 ::= { slpReqStatsGroup 7 } 377 slpUDPReqCount OBJECT-TYPE 378 SYNTAX Unsigned32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The total number of requests received 383 via UDP" 384 ::= { slpReqStatsGroup 8 } 386 slpUDPReplyCount OBJECT-TYPE 387 SYNTAX Unsigned32 388 MAX-ACCESS read-only 389 STATUS current 390 DESCRIPTION 391 "The total number of replied generated 392 via UDP" 393 ::= { slpReqStatsGroup 9 } 395 -- The slpReqTable provides information similar to the 396 -- slpReqStatsGroup, but the table is indexed by scope. 397 -- this allows for monitoring DAs according to their 398 -- configured scopes. 400 slpReqTable OBJECT-TYPE 401 SYNTAX SEQUENCE of slpReqEntry 402 MAX-ACCESS not-accessible 403 STATUS current 404 DESCRIPTION 405 "A table representing request statistics, 406 broken down by the scope for which they 407 were received" 408 ::= { slpDAMibObjects 3 } 410 slpReqEntry OBJECT-TYPE 411 SYNTAX SlpReqEntry 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "A row in the scoped request table" 416 INDEX { slpReqScope } 417 ::= { slpReqTable 1} 419 SlpReqEntry SEQUENCE { 420 slpReqScope DisplayString, 421 slpReqBcast Unsigned32, 422 slpReqMcast Unsigned32, 423 slpReqUcast Unsigned32, 424 slpReqSrv Unsigned32, 425 slpReqAttr Unsigned32, 426 slpReqType Unsigned32, 427 slpReqDA Unsigned32, 428 slpReqTCP Unsigned32, 429 slpReqUDP Unsigned32, 430 slpReqNoMatch Unsigned32 431 } 433 slpReqScope OBJECT-TYPE 434 SYNTAX DisplayString 435 MAX-ACCESS read-only 436 STATUS current 437 DESCRIPTION 438 "The scope that applies to these statistics" 439 ::= { slpReqEntry 1 } 441 slpReqBcast OBJECT-TYPE 442 SYNTAX Unsigned32 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "The number of requests in this scope that 447 were received via broadcast" 448 ::= { slpReqEntry 2 } 450 -- Some implementations may have difficulty distinguishing 451 -- between multicast and broadcast packets that have been 452 -- received. 454 slpReqMcast OBJECT-TYPE 455 SYNTAX Unsigned32 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION 459 "The number of requests in this scope that 460 were received via multicast" 461 ::= { slpReqEntry 3 } 463 slpReqUcast OBJECT-TYPE 464 SYNTAX Unsigned32 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The number of requests in this scope that 469 were received via unicast" 470 ::= { slpReqEntry 4 } 472 slpReqSrv OBJECT-TYPE 473 SYNTAX Unsigned32 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The number of service requests received for 478 this scope" 479 ::= { slpReqEntry 5 } 481 slpReqAttr OBJECT-TYPE 482 SYNTAX Unsigned32 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "The number of attribute requests received" 487 ::= { slpReqEntry 6 } 489 slpReqType OBJECT-TYPE 490 SYNTAX Unsigned32 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The number of service type requests received" 495 ::= { slpReqEntry 7 } 497 slpReqDA OBJECT-TYPE 498 SYNTAX Unsigned32 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "The number of DA discovery requests received" 503 ::= { slpReqEntry 8 } 505 slpReqTCP OBJECT-TYPE 506 SYNTAX Unsigned32 507 MAX-ACCESS read-only 508 STATUS current 509 DESCRIPTION 510 "The number of requests in this scope received 511 via TCP" 512 ::= { slpReqEntry 9 } 514 slpReqUDP OBJECT-TYPE 515 SYNTAX Unsigned32 516 MAX-ACCESS read-only 517 STATUS current 518 DESCRIPTION 519 "The number of requests in this scope received 520 via UDP" 521 ::= { slpReqEntry 10 } 523 slpReqNoMatch OBJECT-TYPE 524 SYNTAX Unsigned32 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "The number of requests received in this scope 529 which produced no matching service URLs" 530 ::= { slpReqEntry 11 } 532 -- This group contains information about the last request 533 -- procesed. An administrator may use this group to sample 534 -- times between a request and the prior request. It is also 535 -- used as the source for attributes in a Parse Error 536 -- notification. 538 slpDALastReqGroup OBJECT-GROUP 539 OBJECTS { 540 slpLastReqType, 541 slpLastReqFrom, 542 slpLastReqScope, 543 slpLastReqError, 544 slpLastReqTime, 545 slpLastReqETime 546 STATUS current 547 DESCRIPTION 548 "This groups contains information about the 549 last request that was processed" 550 ::= { slpDAMibObjects 4 } 552 slpLastReqType OBJECT-TYPE 553 SYNTAX INTEGER { 554 service (1), 555 service type(2), 556 DA discovery(3), 557 attribute(4) 558 } 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "The type of request processed" 563 ::= { slpDALastReq 1 } 565 slpLastReqFrom OBJECT-TYPE 566 SYNTAX IpAddress 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "The address of the UA that made the last 571 request" 572 ::= { slpDALastReq 2 } 574 slpLastReqScope OBJECT-TYPE 575 SYNTAX SET OF DisplayString 576 MAX-ACCESS read-write 577 STATUS current 578 DESCRIPTION 579 "The list of scopes provided with this 580 request" 581 ::= { slpDALastReq 3 } 583 slpLastReqError OBJECT-TYPE 584 SYNTAX INTEGER { 585 parse(1), 586 authentication(2), 587 no match(2), 588 none(3) 589 } 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "Any error generated while processing 594 this request" 595 ::= { slpDALastReq 4 } 597 slpLastReqTime OBJECT-TYPE 598 SYNTAX DateAndTime 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The Date and Time this request was 603 processed" 604 ::= { slpDALastReq 5 } 606 slpLastReqTime OBJECT-TYPE 607 SYNTAX TimeTicks 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "The time, in hundreths of a second, since the 612 last request was processed" 613 ::= { slpDALastReq 6 } 615 -- How many errors of each category has the DA received. 617 -- Some errors should actually generate alerts 618 -- since they indicate the UA making the request may be 619 -- malfunctioning. 621 slpDAEventGroup NOTIFICATION-GROUP 622 NOTIFICATIONS { slpDAParseError } 623 STATUS current 624 DESCRIPTION 625 "The list of notifications (traps) that an 626 SLP DA may generate" 627 ::= { slpDAMibObjects 5 } 629 slpDAParseError NOTIFICATION-TYPE 630 OBJECTS { slpLastReqType, slpLastReqFrom 631 slpLastReqScope, slpLastReqError } 632 STATUS current 633 DESCRIPTION 634 "The SLP DA could not correctly parse a 635 request." 636 ::= { slpDAEventGroup 0 1 } 638 -- Compliance statements 639 slpCompliances OBJECT IDENTIFIER ::= { slpMib 2 } 641 slpBasicCompliance MODULE-COMPLIANCE 642 STATUS current 643 DESCRIPTION 644 "The compliance statement for SNMPv2 entities 645 which implement the basic elements of the SLP 646 MIB for monitoring SLP directory agents" 647 MODULE -- this module 648 MANDATORY-GROUPS{ slpDAConfigGroup, 649 slpDALastReqGroup, 650 slpDAEventGroup } 651 ::= { slpCompliances 1 } 653 slpFullCompliance MODULE-COMPLIANCE 654 STATUS current 655 DESCRIPTION 656 "The compliance statement for SNMPv2 entities 657 which implement the basic elements of the SLP 658 MIB for monitoring SLP directory agents" 659 MODULE -- this module 660 MANDATORY-GROUPS{ slpDAConfigGroup, 661 slpDALastReqGroup, 662 slpReqStatsGroup, 663 slpReqTable, 664 slpDAEventGroup } 665 ::= slpCompliances 2 667 END 669 5. Acknowledgments 671 This document is a product of the Service Location Working group. 673 A special thanks to Erik Guttman for his prompting to begin this 674 task, as well as frequent feedback and suggestions during the MIB 675 development process. 677 6. References 679 [1]SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 680 S. Waldbusser, "Structure of Management Information for Version 2 681 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 682 January 1996. 684 [2]McCloghrie, K., and M. Rose, Editors, "Management Information 685 Base for Network Management of TCP/IP-based internets: MIB-II", 686 STD 17, RFC 1213, Hughes LAN Systems, Performance Systems 687 International, March 1991. 689 [3]Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple 690 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 691 Research, Performance Systems International, MIT Lab for Computer 692 Science, May 1990. 694 [4]SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and 695 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 696 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 698 [5]J. Veizades, E. Guttman, C. Perkins, and S. Kaplan. "Service 699 Location Protocol", RFC 2165. June 1997. 701 Full Copyright Statement 703 Copyright (C) The Internet Society (1997). All Rights Reserved. 705 This document and translations of it may be copied and furnished to 706 others, and derivative works that comment on or otherwise explain it 707 or assist in its implementation may be prepared, copied, published 708 and distributed, in whole or in part, without restriction of any 709 kind, provided that the above copyright notice and this paragraph 710 are included on all such copies and derivative works. However, 711 this document itself may not be modified in any way, such as by 712 removing the copyright notice or references to the Internet Society 713 or other Internet organizations, except as needed for the purpose 714 of developing Internet standards in which case the procedures 715 for copyrights defined in the Internet Standards process must be 716 followed, or as required to translate it into languages other than 717 English. 719 The limited permissions granted above are perpetual and will not be 720 revoked by the Internet Society or its successors or assigns. 722 This document and the information contained herein is provided on an 723 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 724 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 725 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 726 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 727 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 729 Authors' Addresses 731 Questions about this memo can be directed to: 733 Pete St. Pierre 734 Sun Microsystems 735 901 San Antonio Avenue 736 Palo Alto, CA 94303 737 USA 738 Phone: +1 415 786-5790 739 email: Pete.StPierre@Eng.Sun.COM