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