idnits 2.17.1 draft-ietf-rap-cops-client-mib-02.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: ---------------------------------------------------------------------------- ** 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. ** The document is more than 15 pages and seems to lack a Table of Contents. == 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 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 26 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([V2SMI]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 606 has weird spacing: '...ulative since...' -- 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 (March 2000) is 8808 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: 'USM' is mentioned on line 1082, but not defined == Missing Reference: 'VACM' is mentioned on line 1083, but not defined == Unused Reference: 'ASN1' is defined on line 1166, but no explicit reference was found in the text == Unused Reference: 'ASN1BER' is defined on line 1172, but no explicit reference was found in the text == Unused Reference: 'ADDRESSMIB' is defined on line 1204, but no explicit reference was found in the text == Unused Reference: 'PROCESS' is defined on line 1210, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. 'ARCH') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'V1PROTO') ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'V1TRAPS') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'V2COMMUNITY') ** Obsolete normative reference: RFC 1906 (ref. 'V2TRANS') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1905 (ref. 'V2PROTO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2570 (ref. 'V3INTRO') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2572 (ref. 'V3MPC') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. 'V3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2573 (ref. 'V3APPS') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. 'V3VACM') (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1BER' ** Downref: Normative reference to an Informational RFC: RFC 2753 (ref. 'FRAMEWORK') -- Possible downref: Non-RFC (?) normative reference: ref. 'ADDRESSMIB' Summary: 20 errors (**), 0 flaws (~~), 9 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft A. Smith 2 Expires September 2000 Extreme Networks 3 draft-ietf-rap-cops-client-mib-02.txt D. Partain 4 Ericsson 5 J. Seligson 6 Nortel Networks 7 March 2000 9 Definitions of Managed Objects for Common Open Policy Service (COPS) 10 Protocol Clients 12 Status of this Memo 14 This document is an Internet Draft and is in full conformance with all 15 provisions of Section 10 of RFC2026. Internet Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its Areas, and 17 its Working Groups. Note that other groups may also distribute working 18 documents as Internet Drafts. 20 Internet Drafts are draft documents valid for a maximum of six months. 21 Internet Drafts may be updated, replaced, or obsoleted by other 22 documents at any time. It is not appropriate to use Internet Drafts as 23 reference material or to cite them other than as a "working draft" or 24 "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This document is a product of the IETF's RSVP Admission Policy Working 33 Group. Copyright (C) The Internet Society (2000). All Rights Reserved. 35 Abstract 37 This memo defines a portion of the Management Information Base (MIB) for 38 use with network management protocols in TCP/IP based internets. In 39 particular it defines objects for managing a client of the Common Open 40 Policy Service (COPS) protocol. 42 This memo includes a MIB module in a manner that is compliant to the 43 SNMPv2 SMI [V2SMI]. 45 1. The SNMP Management Framework 47 The SNMP Management Framework presently consists of five major 48 components: 50 o An overall architecture, described in an Architecture for 51 Describing SNMP Management Frameworks [ARCH]. 53 o Mechanisms for describing and naming objects and events for the 54 purpose of management. The first version of this Structure of 55 Management Information (SMI) is called SMIv1 and described in 56 RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC 1215 57 [V1TRAPS]. The second version, called SMIv2, is described in 58 STD 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58, 59 RFC 2580 [V2CONFORM]. 61 o Message protocols for transferring management information. The 62 first version of the SNMP message protocol is called SNMPv1 and 63 described in STD 15, RFC 1157 [V1PROTO]. A second version of 64 the SNMP message protocol, which is not an Internet standards 65 track protocol, is called SNMPv2c and described in RFC 1901 66 [V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the 67 message protocol is called SNMPv3 and described in RFC1906 68 [V2TRANS], Message Processing and Dispatching [V3MPC] and User- 69 based Scurity Model [V3USM]. 71 o Protocol operations for accessing management information. The 72 first set of protocol operations and associated PDU formats is 73 described in STD 15, RFC 1157 [V1PROTO]. A second set of 74 protocol operations and associated PDU formats is described in 75 RFC 1905 [V2PROTO]. 77 o A set of fundamental applications described in SNMPv3 78 Applications [V3APPS] and the view-based access control 79 mechanism described in View-based Access Control Model [V3VACM]. 81 A more detailed introduction to the current SNMP Management Framework 82 can be found in RFC 2570 [V3INTRO]. 84 Managed objects are accessed via a virtual information store, termed the 85 Management Information Base or MIB. Objects in the MIB are defined 86 using the mechanisms defined in the SMI. 88 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 89 conforming to the SMIv1 can be produced through the appropriate 90 translations. The resulting translated MIB must be semantically 91 equivalent, except where objects or events are omitted because no 92 translation is possible (use of Counter64). Some machine readable 93 information in SMIv2 will be converted into textual descriptions in 94 SMIv1 during the translation process. However, this loss of machine 95 readable information is not considered to change the semantics of the 96 MIB. 98 2. Overview 100 The COPS protocol [COPS] is a client-server protocol intended for the 101 communication of policy requests and decisions between a Policy 102 Enforcement Point (PEP) and a Policy Decision Point (PDP). The PEP acts 103 as a COPS client in this scenario. The model for policy out-sourcing, 104 of which the COPS protocol provides one part, is described in 105 [FRAMEWORK]. 107 2.1. Scope 109 This MIB is intended to provide management of the important features of 110 a COPS protocol client module. It does not provide management for a COPS 111 server - this is outside the scope of the current memo. It provides for 112 monitoring of status and protocol statistics, as well as for 113 configuration of the client, in particular for telling it where to 114 locate its servers. Other mechanisms for achieving this function without 115 SNMP configuration might include use of the Service Location Protocol 116 [SRVLOC] although this is outside the scope of this memo and are not 117 specified by the COPS protocol itself. 119 This MIB also does not provide management of specific COPS client-types 120 e.g. for use with the RSVP protocol [RSVP][COPSRSVP]. 122 3. Structure of COPS Client MIB 124 Objects in this MIB are arranged into groups. Each group is organized 125 as a set of related objects. The overall structure is described below. 127 3.1. copsClientCapabilitiesGroup 129 This group contains objects that represent COPS protocol 130 capabilities implemented by this COPS client. 132 3.2. copsClientStatusGroup 134 This group contains objects that indicate the current status of 135 connection(s) to COPS servers, including per-server protocol 136 statistics. It maintains last-known statistics for all of the 137 servers with which the client has ever been connected since agent 138 restart. 140 3.3. copsConfigGroup 142 This group contains objects that allow for configuration of COPS 143 server addresses and the order to which connections should be 144 attempted. It contains a table of per-server objects as well as 145 scalars for configuration of the retry algorithm to be used by a 146 client to obtain a connection to an appropriate server. 148 3.4. Textual Conventions 150 The datatypes CopsClientState, CopsServerEntryType, CopsErrorCode, 151 CopsTcpPort and CopsAuthType are used as textual conventions in 152 this document. These textual conventions have NO effect on either 153 the syntax nor the semantics of any managed object. Objects 154 defined using these conventions are always encoded by means of the 155 rules that define their primitive type. Hence, no changes to the 156 SMI or the SNMP are necessary to accommodate these textual 157 conventions which are adopted merely for the convenience of 158 readers. 160 3.5. Relationship to Other MIBs 162 3.5.1. Relationship to the 'system' group 164 This MIB contains definitions for a single COPS protocol client 165 represented by a single SNMP agent and instance of the MIB-2 system 166 group [MIB2]. It does not address the case of multiple co-located 167 COPS protocol clients. 169 4. Editorial information 171 172 4.1. Open Issues resolved in this draft 174 (10) Configuration parameters for the retry algorithm are too limiting 175 on implementations (no such algorithm was specified by the COPS 176 protocol itself). DONE - objects which were per-server are now 177 scalars; a possibly-configurable object is added to select/indicate 178 the retry algorithm in use with round-robin, sequential and other 179 as values. 181 (11) copsClientServerConfigRetryCount should be unsigned: DONE - changed 182 from Integer32 to Unsigned32. 184 4.2. Open Issues resolved in previous drafts 186 (1) When should per-server counters (e.g. copsClientServerInPkts) be 187 zeroed? Resolution: see issue (3). 189 (2) Addressing of server tables by IP Address is frowned on: should 190 this be indexed by a client-determined small integer? DONE - added 191 InetEndpoint indices as recommended by draft-ops-endpoint- 192 mib-00.txt. 194 (3) Should error stats be maintained per-server or is global 195 sufficient? If per-server then see also issue #1. Resolution: 196 everything is per-server but not zero'ed on reconnect. 198 (4) Add object to show current security in use. DONE - 199 copsClientServerSecurityMode. 201 (5) Do we need to be able to configure the security mode for client to 202 attempt to use to talk to COPS server? DONE - added configuration 203 object as an index to server configuration table. Added some more 204 capabilities too. 206 (6) Add TCP port number to all tables. DONE - copsClientServerTcpPort, 207 copsClientServerConfigTcpPort. 209 (7) Add server retry configuration. DONE - 210 copsClientServerConfigRetryCount, 211 copsClientServerConfigRetryInterval 213 (8) Add COPS protocol version number capabilities object. DONE - 214 copsClientCapabilities. 216 (9) Added error counters and capabilities associated with security. 218 5. Definitions for COPS Client MIB 220 COPS-CLIENT-MIB DEFINITIONS ::= BEGIN 222 -- ------------------------------------------------------------- 223 -- ------------------------------------------------------------- 225 IMPORTS 226 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, Unsigned32 227 FROM SNMPv2-SMI 228 TimeStamp, TimeInterval, RowStatus, TEXTUAL-CONVENTION 229 FROM SNMPv2-TC 230 MODULE-COMPLIANCE, OBJECT-GROUP 231 FROM SNMPv2-CONF 232 InetAddressType, InetAddress 233 FROM INET-ADDRESS-MIB; 235 -- REFERENCE 236 -- "The COPS (Common Open Policy Service) Protocol RFC 2748 238 copsClientMIB MODULE-IDENTITY 239 LAST-UPDATED "200003100000Z" 240 ORGANIZATION "IETF RSVP Admission Policy Working Group" 241 CONTACT-INFO 242 " Andrew Smith (WG co-chair) 243 Phone: +1 408 579 2821 244 Email: andrew@extremenetworks.com 246 Mark Stevens (WG co-chair) 247 Phone: +1 978 287 9102 248 Email: markstevens@lucent.com 250 Editor: Andrew Smith 251 Phone: +1 408 579 2821 252 Email: andrew@extremenetworks.com 254 Editor: David Partain 255 Phone: +46 13 28 41 44 256 Email: David.Partain@ericsson.com 258 Editor: John Seligson 259 Phone: +1 408 495 2992 260 Email: jseligso@nortelnetworks.com" 262 DESCRIPTION 263 "The COPS Client MIB module" 265 REVISION "200003100000Z" 266 DESCRIPTION "This version published as 267 draft-ietf-rap-cops-client-mib-03." 269 ::= { xxx 1 } 271 copsClientMIBObjects OBJECT IDENTIFIER ::= { copsClientMIB 1 } 273 -- ------------------------------------------------------------- 274 -- Textual Conventions 275 -- ------------------------------------------------------------- 277 CopsClientState ::= TEXTUAL-CONVENTION 278 STATUS current 279 DESCRIPTION 280 "A value indicating the state of a COPS client." 281 SYNTAX INTEGER { 282 copsClientInvalid(1), -- default state. 283 copsClientTcpconnected(2), -- TCP connection up but COPS 284 -- not yet open. 285 copsClientAuthenticating(3), -- TCP connection up but still 286 -- authenticating. 287 copsClientSecAccepted(4), -- connection authenticated. 288 copsClientAccepted(5), -- COPS server accepted client. 289 copsClientTimingout(6) -- Keepalive timer has expired, 290 -- client is in process of tearing 291 -- down connection. 292 } 294 CopsServerEntryType ::= TEXTUAL-CONVENTION 295 STATUS current 296 DESCRIPTION 297 "A value indicating how a COPS server entry came into existence." 298 SYNTAX INTEGER { 299 copsServerStatic(1), -- configured by manager 300 copsServerRedirect(2) -- notified by COPS server 301 } 303 CopsErrorCode ::= TEXTUAL-CONVENTION 304 STATUS current 305 DESCRIPTION 306 "A value describing a COPS protocol error. Codes are identical to 307 those used by the COPS protocol itself." 308 SYNTAX INTEGER { 309 errorOther(0), -- none of the below 310 errorBadHandle(1), 311 errorInvalidHandleReference(2), 312 errorBadMessageFormat(3), 313 errorUnableToProcess(4), 314 errorMandatoryClientSiMissing(5), 315 errorUnsupportedClientType(6), 316 errorMandatoryCopsObjectMissing(7), 317 errorClientFailure(8), 318 errorCommunicationFailure(9), 319 errorUnspecified(10), -- client-type specific subcode 320 errorShuttingDown(11), 321 errorRedirectToPreferredServer(12), 322 errorUnknownCopsObject(13), 323 errorAuthenticationFailure(14), 324 errorAuthenticationMissing(15) 325 } 326 -- REFERENCE 327 -- "COPS section 2.2.8" 329 CopsTcpPort ::= TEXTUAL-CONVENTION 330 STATUS current 331 DESCRIPTION 332 "A value indicating a TCP protocol port number." 333 SYNTAX INTEGER (0..65535) 335 CopsAuthType ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION 338 "A value indicating a type of security authentication mechanism." 339 SYNTAX INTEGER { 340 authNone(0), 341 authOther(1), 342 authIpSecAh(2), 343 authIpSecEsp(3), 344 authTls(4), 345 authCopsIntegrity(5) 346 } 348 -- ------------------------------------------------------------- 350 copsClientCapabilitiesGroup OBJECT IDENTIFIER 351 ::= { copsClientMIBObjects 1 } 353 -- ------------------------------------------------------------- 354 -- 355 -- Capabilities of the COPS client to connect to a COPS server: 356 -- 357 copsClientCapabilities OBJECT-TYPE 358 SYNTAX BITS { 359 copsClientVersion1(0), -- supports version1 of COPS protocol 360 copsClientAuthIpSecAh(1) , -- supports IP-SEC Authentication 361 copsClientAuthIpSecEsp(2), -- supports IP-SEC Encryption 362 copsClientAuthTls(3), -- supports Transport-Layer Security 363 copsClientAuthInteg(4) -- supports COPS Integrity 364 } 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "A list of the optional capabilities that this COPS client 369 supports." 370 ::= { copsClientCapabilitiesGroup 1 } 372 -- ------------------------------------------------------------- 374 copsClientStatusGroup OBJECT IDENTIFIER ::= { copsClientMIBObjects 2 } 376 -- ------------------------------------------------------------- 377 -- 378 -- Current status of COPS server connections, all read-only. 379 -- 381 copsClientServerCurrentTable OBJECT-TYPE 382 SYNTAX SEQUENCE OF CopsClientServerCurrentEntry 383 MAX-ACCESS not-accessible 384 STATUS current 385 DESCRIPTION 386 "A table of information regarding COPS servers as seen from the 387 point of view of a COPS client. This table contains entries 388 for both statically-configured and dynamically-learned servers 389 (from a PDP Redirect operation). One entry exists in this table 390 for each COPS Client-Type served by the COPS server. In addition, 391 an entry will exist with copsClientServerClientType 0 (zero) 392 representing information about the underlying connection itself: 393 this is consistent with the COPS specification which reserves 394 this value for this purpose." 395 ::= { copsClientStatusGroup 1 } 397 copsClientServerCurrentEntry OBJECT-TYPE 398 SYNTAX CopsClientServerCurrentEntry 399 MAX-ACCESS not-accessible 400 STATUS current 401 DESCRIPTION 402 "A set of information regarding a single COPS server serving 403 a single COPS Client-Type from the point of view of a COPS 404 client." 405 INDEX { copsClientServerAddressType, copsClientServerAddress, 406 copsClientServerClientType } 407 ::= { copsClientServerCurrentTable 1 } 409 CopsClientServerCurrentEntry ::= 410 SEQUENCE { 411 copsClientServerAddressType InetAddressType, 412 copsClientServerAddress InetAddress, 413 copsClientServerClientType INTEGER, 414 copsClientServerTcpPort CopsTcpPort, 415 copsClientServerType CopsServerEntryType, 416 copsClientServerAuthType CopsAuthType, 417 copsClientServerLastConnAttempt TimeStamp, 418 copsClientState CopsClientState, 419 copsClientServerKeepaliveTime TimeInterval, 420 copsClientServerAccountingTime TimeInterval, 421 copsClientInPkts Counter32, 422 copsClientOutPkts Counter32, 423 copsClientInErrs Counter32, 424 copsClientLastError CopsErrorCode, 425 copsClientTcpConnectAttempts Counter32, 426 copsClientTcpConnectFailures Counter32, 427 copsClientOpenAttempts Counter32, 428 copsClientOpenFailures Counter32, 429 copsClientErrUnsupportClienttype Counter32, 430 copsClientErrUnsupportedVersion Counter32, 431 copsClientErrLengthMismatch Counter32, 432 copsClientErrUnknownOpcode Counter32, 433 copsClientErrUnknownCnum Counter32, 434 copsClientErrBadCtype Counter32, 435 copsClientErrBadSends Counter32, 436 copsClientErrWrongObjects Counter32, 437 copsClientErrWrongOpcode Counter32, 438 copsClientKaTimedoutClients Counter32, 439 copsClientErrAuthFailures Counter32, 440 copsClientErrAuthMissing Counter32 441 } 443 copsClientServerAddressType OBJECT-TYPE 444 SYNTAX InetAddressType 445 MAX-ACCESS not-accessible 446 STATUS current 447 DESCRIPTION 448 "The type of address in copsClientServerAddress." 449 ::= { copsClientServerCurrentEntry 1 } 451 copsClientServerAddress OBJECT-TYPE 452 SYNTAX InetAddress 453 MAX-ACCESS not-accessible 454 STATUS current 455 DESCRIPTION 456 "The IPv4, IPv6 or DNS address of a COPS Server. Note that, 457 since this is an index to the table, the DNS name must be 458 short enough to fit into the maximum length of indices allowed 459 by the management protocol in use." 460 REFERENCE 461 "COPS section 2.3" 462 ::= { copsClientServerCurrentEntry 2 } 464 copsClientServerClientType OBJECT-TYPE 465 SYNTAX INTEGER (0..65535) 466 MAX-ACCESS not-accessible 467 STATUS current 468 DESCRIPTION 469 "The COPS protocol Client-Type for which this entry 470 applies. Multiple Client-Types can be served by a single 471 COPS server. The value 0 (zero) indicates that this 472 entry contains information about the underlying connection 473 itself." 474 REFERENCE 475 "COPS section 6, IANA" 476 ::= { copsClientServerCurrentEntry 3 } 478 copsClientServerTcpPort OBJECT-TYPE 479 SYNTAX CopsTcpPort 480 MAX-ACCESS read-only 481 STATUS current 482 DESCRIPTION 483 "The TCP port number on the COPS server to which the 484 client should connect." 485 ::= { copsClientServerCurrentEntry 4 } 487 copsClientServerType OBJECT-TYPE 488 SYNTAX CopsServerEntryType 489 MAX-ACCESS read-only 490 STATUS current 491 DESCRIPTION 492 "Indicator of the source of this COPS server information. 493 COPS servers may be configured by network management 494 into copsClientServerConfigTable and appear in this entry 495 with type copsServerStatic(1). Alternatively, the may be 496 notified from another COPS server by means of the COPS 497 PDP-Redirect mechanism and appear as copsServerRedirect(2)." 498 ::= { copsClientServerCurrentEntry 5 } 500 copsClientServerAuthType OBJECT-TYPE 501 SYNTAX CopsAuthType 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "Indicator of the current security mode in use between 506 client and this COPS server." 507 ::= { copsClientServerCurrentEntry 6 } 509 copsClientServerLastConnAttempt OBJECT-TYPE 510 SYNTAX TimeStamp 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "Timestamp of the last time that this client attempted to 515 connect to this COPS server." 516 ::= { copsClientServerCurrentEntry 7 } 518 copsClientState OBJECT-TYPE 519 SYNTAX CopsClientState 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "The state of the connection and COPS protocol with respect 524 to this COPS server." 525 ::= { copsClientServerCurrentEntry 8 } 527 copsClientServerKeepaliveTime OBJECT-TYPE 528 SYNTAX TimeInterval 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "The value of the COPS protocol Keepalive timeout, in 533 centiseconds, currently in use by this client, as 534 specified by this COPS server in the Client-Accept operation. 535 A value of zero indicates no keepalive activity is expected." 536 REFERENCE 537 "COPS section 3.7, 4.4" 538 ::= { copsClientServerCurrentEntry 9 } 540 copsClientServerAccountingTime OBJECT-TYPE 541 SYNTAX TimeInterval 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "The value of the COPS protocol Accounting timeout, in 546 centiseconds, currently in use by this client, as specified 547 by the COPS server in the Client-Accept operation. A value 548 of zero indicates no accounting activity is to be performed." 549 REFERENCE 550 "COPS section 3.7" 551 ::= { copsClientServerCurrentEntry 10 } 553 copsClientInPkts OBJECT-TYPE 554 SYNTAX Counter32 555 MAX-ACCESS read-only 556 STATUS current 557 DESCRIPTION 558 "A count of the total number of COPS packets that this client has 559 received from this COPS server marked for this Client-Type. This 560 value is cumulative since agent restart and is not zeroed on new 561 connections." 562 ::= { copsClientServerCurrentEntry 11 } 564 copsClientOutPkts OBJECT-TYPE 565 SYNTAX Counter32 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "A count of the total number of COPS packets that this client has 570 sent to this COPS server marked for this Client-Type. This value 571 is cumulative since agent restart and is not zeroed on new 572 connections." 573 ::= { copsClientServerCurrentEntry 12 } 575 copsClientInErrs OBJECT-TYPE 576 SYNTAX Counter32 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "A count of the total number of COPS packets that this client has 581 received from this COPS server marked for this Client-Type that 582 contained errors in syntax. This value is cumulative since agent 583 restart and is not zeroed on new connections." 584 ::= { copsClientServerCurrentEntry 13 } 586 copsClientLastError OBJECT-TYPE 587 SYNTAX CopsErrorCode 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "The code contained in the last COPS protocol Error Object 592 received by this client from this COPS server marked for this 593 Client-Type. This value is not zeroed on COPS Client-Open 594 operations." 595 REFERENCE 596 "COPS section 2.2.8" 597 ::= { copsClientServerCurrentEntry 14 } 599 copsClientTcpConnectAttempts OBJECT-TYPE 600 SYNTAX Counter32 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "A count of the number of times that this COPS client has tried 605 to open an TCP connection to a COPS server. This value is 606 cumulative since agent restart and is not zeroed on new 607 connections. This value is only valid for Client-Type 0." 608 ::= { copsClientServerCurrentEntry 15 } 610 copsClientTcpConnectFailures OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "A count of the number of times that this COPS client has failed 616 to open an TCP connection to a COPS server. This value is 617 cumulative since agent restart and is not zeroed on new 618 connections. This value is only valid for Client-Type 0." 619 ::= { copsClientServerCurrentEntry 16 } 621 copsClientOpenAttempts OBJECT-TYPE 622 SYNTAX Counter32 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "A count of the number of times that this COPS client has tried 627 to perform a COPS Client-Open to a COPS server for this 628 Client-Type. This value is cumulative since agent restart and is 629 not zeroed on new connections." 630 ::= { copsClientServerCurrentEntry 17 } 632 copsClientOpenFailures OBJECT-TYPE 633 SYNTAX Counter32 634 MAX-ACCESS read-only 635 STATUS current 636 DESCRIPTION 637 "A count of the number of times that this COPS client has failed 638 to perform a COPS Client-Open to a COPS server for this 639 Client-Type. This value is cumulative since agent restart and is 640 not zeroed on new connections." 641 ::= { copsClientServerCurrentEntry 18 } 643 copsClientErrUnsupportClienttype OBJECT-TYPE 644 SYNTAX Counter32 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "A count of the total number of COPS packets that this client has 649 received from COPS servers that referred to Client-Types that are 650 unsupported by this client. This value is cumulative 651 since agent restart and is not zeroed on new connections. This 652 value is only valid for Client-Type 0." 653 ::= { copsClientServerCurrentEntry 19 } 655 copsClientErrUnsupportedVersion OBJECT-TYPE 656 SYNTAX Counter32 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "A count of the total number of COPS packets that this client 661 has received from COPS servers marked for this Client-Type that 662 had a COPS protocol Version number that is unsupported by this 663 client. This value is cumulative since agent restart and is not 664 zeroed on new connections." 665 ::= { copsClientServerCurrentEntry 20 } 667 copsClientErrLengthMismatch OBJECT-TYPE 668 SYNTAX Counter32 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "A count of the total number of COPS packets that this client has 673 received from COPS servers marked for this Client-Type that had a 674 COPS protocol Message Length that did not match the actual 675 received packet. This value is cumulative since agent restart and 676 is not zeroed on new connections." 677 ::= { copsClientServerCurrentEntry 21 } 679 copsClientErrUnknownOpcode OBJECT-TYPE 680 SYNTAX Counter32 681 MAX-ACCESS read-only 682 STATUS current 683 DESCRIPTION 684 "A count of the total number of COPS packets that this client has 685 received from COPS servers marked for this Client-Type that had a 686 COPS protocol Op Code that was unrecognised by this client. This 687 value is cumulative since agent restart and is not zeroed on new 688 connections." 689 ::= { copsClientServerCurrentEntry 22 } 691 copsClientErrUnknownCnum OBJECT-TYPE 692 SYNTAX Counter32 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "A count of the total number of COPS packets that this client has 697 received from COPS servers marked for this Client-Type that 698 contained a COPS protocol object C-Num that was unrecognised by 699 this client. This value is cumulative since agent restart and is 700 not zeroed on new connections." 701 ::= { copsClientServerCurrentEntry 23 } 703 copsClientErrBadCtype OBJECT-TYPE 704 SYNTAX Counter32 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "A count of the total number of COPS packets that this client has 709 received from COPS servers marked for this Client-Type that 710 contained a COPS protocol object C-Type that was not defined for 711 the C-Nums known by this client. This value is cumulative since 712 agent restart and is not zeroed on new connections." 714 ::= { copsClientServerCurrentEntry 24 } 716 copsClientErrBadSends OBJECT-TYPE 717 SYNTAX Counter32 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "A count of the total number of COPS packets that this client 722 attempted to send to COPS servers marked for this Client-Type 723 that resulted in a transmit error. This value is cumulative 724 since agent restart and is not zeroed on new connections." 725 ::= { copsClientServerCurrentEntry 25 } 727 copsClientErrWrongObjects OBJECT-TYPE 728 SYNTAX Counter32 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "A count of the total number of COPS packets that this client 733 has received from COPS servers marked for this Client-Type that 734 did not contain a permitted set of COPS protocol objects. This 735 value is cumulative since agent restart and is not zeroed on new 736 connections." 737 ::= { copsClientServerCurrentEntry 26 } 739 copsClientErrWrongOpcode OBJECT-TYPE 740 SYNTAX Counter32 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "A count of the total number of COPS packets that this client has 745 received from COPS servers marked for this Client-Type that had a 746 COPS protocol Op Code that should not have been sent to a COPS 747 client e.g. Open-Requests. This value is cumulative since agent 748 restart and is not zeroed on new connections." 749 ::= { copsClientServerCurrentEntry 27 } 751 copsClientKaTimedoutClients OBJECT-TYPE 752 SYNTAX Counter32 753 MAX-ACCESS read-only 754 STATUS current 755 DESCRIPTION 756 "A count of the total number of times that this client has 757 been shut down for this Client-Type by COPS servers that had 758 detected a COPS protocol Keepalive timeout. This value is 759 cumulative since agent restart and is not zeroed on new 760 connections." 761 ::= { copsClientServerCurrentEntry 28 } 763 copsClientErrAuthFailures OBJECT-TYPE 764 SYNTAX Counter32 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "A count of the total number of times that this client has 769 received a COPS packet marked for this Client-Type which 770 could not be authenticated using the authentication mechanism 771 used by this client." 772 ::= { copsClientServerCurrentEntry 29 } 774 copsClientErrAuthMissing OBJECT-TYPE 775 SYNTAX Counter32 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "A count of the total number of times that this client has 780 received a COPS packet marked for this Client-Type which did not 781 contain authentication information." 782 ::= { copsClientServerCurrentEntry 30 } 784 -- ------------------------------------------------------------- 786 copsClientConfigGroup OBJECT IDENTIFIER ::= { copsClientMIBObjects 3 } 788 -- ------------------------------------------------------------- 790 copsClientServerConfigTable OBJECT-TYPE 791 SYNTAX SEQUENCE OF CopsClientServerConfigEntry 792 MAX-ACCESS not-accessible 793 STATUS current 794 DESCRIPTION 795 "Table of possible COPS servers to try to connect to in order 796 of copsClientServerConfigPriority. There may be multiple 797 entries in this table for the same server and client-type which 798 specify different security mechanisms: these mechanisms will 799 be attempted by the client in the priority order given. Note 800 that a server learned by means of PDPRedirect always takes 801 priority over any of these configured entries." 802 ::= { copsClientConfigGroup 1 } 804 copsClientServerConfigEntry OBJECT-TYPE 805 SYNTAX CopsClientServerConfigEntry 806 MAX-ACCESS not-accessible 807 STATUS current 808 DESCRIPTION 809 "A set of configuration information regarding a single 810 COPS server from the point of view of a COPS client." 811 INDEX { copsClientServerConfigAddrType, 812 copsClientServerConfigAddress, 813 copsClientServerConfigClientType, 814 copsClientServerConfigAuthType } 815 ::= { copsClientServerConfigTable 1 } 817 CopsClientServerConfigEntry ::= 818 SEQUENCE { 819 copsClientServerConfigAddrType InetAddressType, 820 copsClientServerConfigAddress InetAddress, 821 copsClientServerConfigClientType INTEGER, 822 copsClientServerConfigAuthType CopsAuthType, 823 copsClientServerConfigTcpPort CopsTcpPort, 824 copsClientServerConfigPriority Integer32, 825 copsClientServerConfigRowStatus RowStatus 826 } 828 copsClientServerConfigAddrType OBJECT-TYPE 829 SYNTAX InetAddressType 830 MAX-ACCESS not-accessible 831 STATUS current 832 DESCRIPTION 833 "The type of address in copsClientServerConfigAddress." 834 ::= { copsClientServerConfigEntry 1 } 836 copsClientServerConfigAddress OBJECT-TYPE 837 SYNTAX InetAddress 838 MAX-ACCESS not-accessible 839 STATUS current 840 DESCRIPTION 841 "The IPv4, IPv6 or DNS address of a COPS Server. Note that, 842 since this is an index to the table, the DNS name must be 843 short enough to fit into the maximum length of indices allowed 844 by the management protocol in use." 845 REFERENCE 846 "COPS section 2.3" 847 ::= { copsClientServerConfigEntry 2 } 849 copsClientServerConfigClientType OBJECT-TYPE 850 SYNTAX INTEGER (0..65535) 851 MAX-ACCESS not-accessible 852 STATUS current 853 DESCRIPTION 854 "The COPS protocol Client-Type for which this entry 855 applies and for which this COPS server is capable 856 of serving. Multiple Client-Types can be served by a 857 single COPS server." 858 REFERENCE 859 "COPS section 6, IANA" 860 ::= { copsClientServerConfigEntry 3 } 862 copsClientServerConfigAuthType OBJECT-TYPE 863 SYNTAX CopsAuthType 864 MAX-ACCESS not-accessible 865 STATUS current 866 DESCRIPTION 867 "The type of authentication mechanism for this COPS client 868 to request when negotiating security at the start of a 869 connection to a COPS server." 870 REFERENCE 871 "COPS section 4." 872 ::= { copsClientServerConfigEntry 4 } 874 copsClientServerConfigTcpPort OBJECT-TYPE 875 SYNTAX CopsTcpPort 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "The TCP port number on the COPS server to which the 880 client should connect." 881 ::= { copsClientServerConfigEntry 5 } 883 copsClientServerConfigPriority OBJECT-TYPE 884 SYNTAX Integer32 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "The priority of this entry relative to other entries. 889 COPS client will attempt to contact COPS servers for the 890 appropriate Client-Type. Higher numbers are tried first. The 891 order to be used amongst server entries with the same priority 892 is undefined. COPS servers that are notified to the client using 893 the COPS protocol PDP-Redirect mechanism are always used in 894 preference to any entries in this table." 895 ::= { copsClientServerConfigEntry 6 } 897 copsClientServerConfigRowStatus OBJECT-TYPE 898 SYNTAX RowStatus 899 MAX-ACCESS read-create 900 STATUS current 901 DESCRIPTION 902 "State of this entry in the table." 903 ::= { copsClientServerConfigEntry 7 } 905 copsClientServerConfigRetryAlgrm OBJECT-TYPE 906 SYNTAX INTEGER { 907 other(1), 908 sequential(2), 909 roundRobin(3) 910 } 911 MAX-ACCESS read-write 912 STATUS current 913 DESCRIPTION 914 "The algorithm by which the client should retry when it 915 fails to connect to a COPS server." 916 DEFVAL { sequential } 917 ::= { copsClientConfigGroup 2 } 919 copsClientServerConfigRetryCount OBJECT-TYPE 920 SYNTAX Unsigned32 921 MAX-ACCESS read-write 922 STATUS current 923 DESCRIPTION 924 "A retry count for use by the retry algorithm. Each retry 925 algorithm needs to specify how it uses this value. 927 For the 'sequential(2)' algorithm, this value is the 928 number of times the client should retry to connect 929 to one COPS server before moving on to another. 931 For the 'roundRobin(3)' algorithm, this value is not used." 932 DEFVAL { 1 } 933 ::= { copsClientConfigGroup 3 } 935 copsClientServerConfigRetryIntvl OBJECT-TYPE 936 SYNTAX TimeInterval 937 UNITS "centi-seconds" 938 MAX-ACCESS read-write 939 STATUS current 940 DESCRIPTION 941 "A retry interval for use by the retry algorithm. Each retry 942 algorithm needs to specify how it uses this value. 944 For the 'sequential(2)' algorithm, this value is the time to 945 wait between retries of a connection to the same COPS server. 947 For the 'roundRobin(3)' algorithm, the client always attempts 948 to connect to each Server in turn, until one succeeds or they 949 all fail; if they all fail, then the client waits for the value 950 of this interval before restarting the algorithm." 951 DEFVAL { 1000 } 952 ::= { copsClientConfigGroup 4 } 954 -- ------------------------------------------------------------- 955 -- Conformance Information 956 -- ------------------------------------------------------------- 958 copsClientConformance OBJECT IDENTIFIER ::= { copsClientMIB 2 } 960 copsClientGroups OBJECT IDENTIFIER ::= { copsClientConformance 1 } 961 copsClientCompliances OBJECT IDENTIFIER ::= { copsClientConformance 2 } 963 -- ------------------------------------------------------------- 964 -- units of conformance 965 -- ------------------------------------------------------------- 967 copsDeviceStatusGroup OBJECT-GROUP 968 OBJECTS { 969 copsClientCapabilities, 970 copsClientServerTcpPort, copsClientServerType, 971 copsClientServerAuthType, copsClientServerLastConnAttempt, 972 copsClientState, copsClientServerKeepaliveTime, 973 copsClientServerAccountingTime, copsClientInPkts, 974 copsClientOutPkts, copsClientInErrs, copsClientLastError, 975 copsClientTcpConnectAttempts, copsClientTcpConnectFailures, 976 copsClientOpenAttempts, copsClientOpenFailures, 977 copsClientErrUnsupportClienttype, 978 copsClientErrUnsupportedVersion, copsClientErrLengthMismatch, 979 copsClientErrUnknownOpcode, copsClientErrUnknownCnum, 980 copsClientErrBadCtype, copsClientErrBadSends, 981 copsClientErrWrongObjects, copsClientErrWrongOpcode, 982 copsClientKaTimedoutClients 984 } 985 STATUS current 986 DESCRIPTION 987 "A collection of objects for monitoring the status of 988 connections to COPS servers and statistics for a COPS client." 989 ::= { copsClientGroups 1 } 991 copsDeviceConfigGroup OBJECT-GROUP 992 OBJECTS { 993 copsClientServerConfigTcpPort, copsClientServerConfigPriority, 994 copsClientServerConfigRowStatus, 995 copsClientServerConfigRetryAlgrm, 996 copsClientServerConfigRetryCount, 997 copsClientServerConfigRetryIntvl 998 } 999 STATUS current 1000 DESCRIPTION 1001 "A collection of objects for configuring COPS server 1002 information." 1003 ::= { copsClientGroups 2 } 1005 -- ------------------------------------------------------------- 1006 -- compliance statements 1007 -- ------------------------------------------------------------- 1009 copsClientCompliance MODULE-COMPLIANCE 1010 STATUS current 1011 DESCRIPTION 1012 "The compliance statement for device support of 1013 management of the COPS client." 1015 MODULE 1016 MANDATORY-GROUPS { 1017 copsDeviceStatusGroup, copsDeviceConfigGroup 1018 } 1020 OBJECT copsClientServerConfigTcpPort 1021 MIN-ACCESS read-only 1022 DESCRIPTION 1023 "Write access is required only if the device supports the 1024 configuration of COPS server information." 1026 OBJECT copsClientServerConfigPriority 1027 MIN-ACCESS read-only 1028 DESCRIPTION 1029 "Write access is required only if the device supports the 1030 configuration of COPS server information." 1032 OBJECT copsClientServerConfigRowStatus 1033 MIN-ACCESS read-only 1034 DESCRIPTION 1035 "Write access is required only if the device supports the 1036 configuration of COPS server information." 1038 OBJECT copsClientServerConfigRetryAlgrm 1039 MIN-ACCESS read-only 1040 DESCRIPTION 1041 "Write access is required only if the device supports the 1042 configuration of COPS server information." 1044 OBJECT copsClientServerConfigRetryCount 1045 MIN-ACCESS read-only 1046 DESCRIPTION 1047 "Write access is required only if the device supports the 1048 configuration of COPS server information." 1050 OBJECT copsClientServerConfigRetryIntvl 1051 MIN-ACCESS read-only 1052 DESCRIPTION 1053 "Write access is required only if the device supports the 1054 configuration of COPS server information." 1056 ::= { copsClientCompliances 1 } 1058 END 1060 6. Acknowledgments 1062 This document describes instrumentation for the client side of the COPS 1063 protocol which was defined by the RSVP Admission Policy (rap) Working 1064 Group, now known as the Resource Allocation Protocol (rap) Working 1065 Group. 1067 7. Security Considerations 1069 There are a number of management objects defined in this MIB that have a 1070 MAX-ACCESS clause of read-create. Such objects may be considered 1071 sensitive or vulnerable in some network environments. The support for 1072 SET operations in a non-secure environment without proper protection can 1073 have a negative effect on network operations. 1075 SNMPv1 by itself is not a secure environment. Even if the network 1076 itself is secure (for example by using IPSec), even then, there is no 1077 control as to who on the secure network is allowed to access and GET/SET 1078 (read/change/create/delete) the objects in this MIB. 1080 It is recommended that the implementers consider the security features 1081 as provided by the SNMPv3 framework. Specifically, the use of the User- 1082 based Security Model [USM] and the View-based Access Control Model 1083 [VACM] is recommended. 1085 It is then a customer/user responsibility to ensure that the SNMP entity 1086 giving access to an instance of this MIB, is properly configured to give 1087 access to the objects only to those principals (users) that have 1088 legitimate rights to indeed GET or SET (change/create/delete) them. 1090 8. References 1092 [ARCH] 1093 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1094 Describing SNMP Management Frameworks", RFC 2571, April 1999 1096 [V1PROTO] 1097 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 1098 Management Protocol", STD 15, RFC 1157, May 1990. 1100 [V1SMI] 1101 Rose, M., and K. McCloghrie, "Structure and Identification of 1102 Management Information for TCP/IP-based Internets", STD 16, RFC 1103 1155, May 1990 1105 [V1CONCISE] 1106 Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1107 1212, March 1991 1109 [V1TRAPS] 1110 M. Rose, "A Convention for Defining Traps for use with the SNMP", 1111 RFC 1215, March 1991 1113 [V2SMI] 1114 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1115 and S. Waldbusser, "Structure of Management Information Version 2 1116 (SMIv2)", STD 58, RFC 2578, April 1999. 1118 [V2TC] 1119 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1120 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1121 2579, April 1999. 1123 [V2CONFORM] 1124 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1125 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1126 2580, April 1999. 1128 [V2COMMUNITY] 1129 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction 1130 to Community-based SNMPv2", RFC 1901, January 1996. 1132 [V2TRANS] 1133 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 1134 Mappings for Version 2 of the Simple Network Management Protocol 1135 (SNMPv2)", RFC 1906, January 1996. 1137 [V2PROTO] 1138 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol 1139 Operations for Version 2 of the Simple Network Management Protocol 1140 (SNMPv2)", RFC 1905, January 1996. 1142 [V3INTRO] 1143 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to 1144 Version 3 of the Internet-standard Network Management Framework", 1145 RFC 2570, April 1999. 1147 [V3MPC] 1148 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1149 Processing and Dispatching for the Simple Network Management 1150 Protocol (SNMP)", RFC 2572, April 1999. 1152 [V3USM] 1153 Blumenthal, U. and B. Wijnen, "The User-Based Security Model (USM) 1154 for Version 3 of the Simple Network Management Protocol (SNMPv3)", 1155 RFC 2574, April 1999. 1157 [V3APPS] 1158 Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, 1159 April 1999. 1161 [V3VACM] 1162 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1163 Control Model for the Simple Network Management Protocol (SNMP)", 1164 RFC 2575, April 1999. 1166 [ASN1] 1167 Information processing systems - Open Systems Interconnection - 1168 Specification of Abstract Syntax Notation One (ASN.1), 1169 International Organization for Standardization, International 1170 Standard 8824, December 1987. 1172 [ASN1BER] 1173 Information processing systems - Open Systems Interconnection - 1174 Specification of Basic Encoding Rules for Abstract Notation One 1175 (ASN.1), International Organization for Standardization, 1176 International Standard 8825, December 1987. 1178 [MIB2] 1179 McCloghrie K., and M. Rose, Editors, "Management Information Base 1180 for Network Management of TCP/IP-based internets", STD 17, RFC 1181 1213, March 1991. 1183 [FRAMEWORK] 1184 Yavatkar, R., Pendarakis, D. and Guerin, R., "A Framework for 1185 Policy-based Admission Control", RFC 2753, January 2000. 1187 [COPS] 1188 Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry, 1189 A., "The COPS (Common Open Policy Service) Protocol", RFC 2748, 1190 January 2000. 1192 [RSVP] 1193 Braden, R. ed. et al., "Resource ReSerVation Protocol (RSVP) 1194 Version 1 - Functional Specification", RFC 2205, September 1997. 1196 [COPSRSVP] 1197 Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry, 1198 A., "COPS Usage for RSVP", RFC 2749, January 2000. 1200 [SRVLOC] 1201 Guttman, E., Perkins, C., Veizades, J., Day, M., "Service Location 1202 Protocol, Version 2", RFC 2608, June 1999. 1204 [ADDRESSMIB] 1205 Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder, 1206 "Textual Conventions for Internet Network Addresses", Internet 1207 Draft, February 2000. http://www.ietf.org/internet-drafts/draft- 1208 ops-endpoint-mib-07.txt 1210 [PROCESS] 1211 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 1212 RFC 2026, October 1996. 1214 9. Authors' Addresses 1216 Andrew Smith 1217 Extreme Networks 1218 3585 Monroe St. 1219 Santa Clara CA 95051 1220 USA 1221 Phone: +1 408 579 2821 1222 EMail: andrew@extremenetworks.com 1224 David Partain 1225 Ericsson Radio Systems 1226 Research and Innovation 1227 P.O. Box 1248 1228 SE-581 12 Linkoping 1229 Sweden 1230 Phone: +46 13 28 41 44 1231 EMail: David.Partain@ericsson.com 1233 John Seligson 1234 Nortel Networks, Inc. 1235 4401 Great America Parkway 1236 Santa Clara, CA 95054 1237 USA 1238 Phone: +1 408 495 2992 1239 EMail: jseligso@nortelnetworks.com 1241 10. Notices 1243 The IETF takes no position regarding the validity or scope of any 1244 intellectual property or other rights that might be claimed to pertain 1245 to the implementation or use of the technology described in this 1246 document or the extent to which any license under such rights might or 1247 might not be available; neither does it represent that it has made any 1248 effort to identify any such rights. Information on the IETF's 1249 procedures with respect to rights in standards-track and standards- 1250 related documentation can be found in BCP-11. Copies of claims of 1251 rights made available for publication and any assurances of licenses to 1252 be made available, or the result of an attempt made to obtain a general 1253 license or permission for the use of such propritary rights by 1254 implementors or users of this specification can be obtained from the 1255 IETF Secretariat. 1257 The IETF invites any interested party to bring to its attention any 1258 copyrights, patents or patent applications, or other proprietary rights 1259 which may cover technology that may be required to practice this 1260 standard. Please address the information to the IETF Executive 1261 Director. 1263 11. Full Copyright 1265 Copyright (C) The Internet Society (2000). All Rights Reserved. 1267 This document and translations of it may be copied and furnished 1268 to others, and derivative works that comment on or otherwise 1269 explain it or assist in its implmentation may be prepared, copied, 1270 published and distributed, in whole or in part, without 1271 restriction of any kind, provided that the above copyright notice 1272 and this paragraph are included on all such copies and derivative 1273 works. However, this document itself may not be modified in any 1274 way, such as by removing the copyright notice or references to the 1275 Internet Society or other Internet organizations, except as needed 1276 for the purpose of developing Internet standards in which case the 1277 procedures for copyrights defined in the Internet Standards 1278 process must be followed, or as required to translate it into 1279 languages other than English. 1281 The limited permissions granted above are perpetual and will not 1282 be revoked by the Internet Society or its successors or assigns. 1284 This document and the information contained herein is provided on 1285 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1286 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1287 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1288 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1289 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.