draft-ietf-rap-cops-client-mib-03.txt   rfc2940.txt 
Internet Draft A. Smith Network Working Group A. Smith
Expires November 2000 Extreme Networks Request for Comments: 2940 Consultant
draft-ietf-rap-cops-client-mib-03.txt D. Partain Category: Standards Track D. Partain
Ericsson Ericsson
J. Seligson J. Seligson
Nortel Networks Nortel Networks
May 2000 October 2000
Definitions of Managed Objects for Common Open Policy Service (COPS) Definitions of Managed Objects for Common Open Policy Service (COPS)
Protocol Clients Protocol Clients
Status of this Memo Status of this Memo
This document is an Internet Draft and is in full conformance with all
provisions of Section 10 of RFC2026. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other
documents at any time. It is not appropriate to use Internet Drafts as
reference material or to cite them other than as a "working draft" or
"work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
To learn the current status of any Internet-Draft, please check the Copyright Notice
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
This document is a product of the IETF's RSVP Admission Policy Working Copyright (C) The Internet Society (2000). All Rights Reserved.
Group. Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP based internets. In for use with network management protocols in TCP/IP based internets.
particular it defines objects for managing a client of the Common Open In particular it defines objects for managing a client of the Common
Policy Service (COPS) protocol. Open Policy Service (COPS) protocol.
This memo includes a MIB module in a manner that is compliant to the This memo includes a MIB module in a manner that is compliant to the
SNMPv2 SMI [V2SMI]. SMIv2 [V2SMI].
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in an Architecture for o An overall architecture, described in an Architecture for
Describing SNMP Management Frameworks [ARCH]. Describing SNMP Management Frameworks [ARCH].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC 1215 STD 16, RFC 1155 [V1SMI], STD 16, RFC 1212 [V1CONCISE] and RFC
[V1TRAPS]. The second version, called SMIv2, is described in 1215 [V1TRAPS]. The second version, called SMIv2, is described
STD 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD 58, in STD 58, RFC 2578 [V2SMI], STD 58, RFC 2579 [V2TC] and STD
RFC 2580 [V2CONFORM]. 58, RFC 2580 [V2CONFORM].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [V1PROTO]. A second version of described in STD 15, RFC 1157 [V1PROTO]. A second version of
the SNMP message protocol, which is not an Internet standards the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901 track protocol, is called SNMPv2c and described in RFC 1901
[V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the [V2COMMUNITY] and RFC 1906 [V2TRANS]. The third version of the
message protocol is called SNMPv3 and described in RFC1906 message protocol is called SNMPv3 and described in RFC1906
[V2TRANS], Message Processing and Dispatching [V3MPC] and User- [V2TRANS], Message Processing and Dispatching [V3MPC] and
based Scurity Model [V3USM]. User-based Security Model [V3USM].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [V1PROTO]. A second set of described in STD 15, RFC 1157 [V1PROTO]. A second set of
protocol operations and associated PDU formats is described in protocol operations and associated PDU formats is described in
RFC 1905 [V2PROTO]. RFC 1905 [V2PROTO].
o A set of fundamental applications described in SNMPv3 o A set of fundamental applications described in SNMPv3
Applications [V3APPS] and the view-based access control Applications [V3APPS] and the view-based access control
mechanism described in View-based Access Control Model [V3VACM]. mechanism described in View-based Access Control Model
[V3VACM].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [V3INTRO]. can be found in RFC 2570 [V3INTRO].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined the Management Information Base or MIB. Objects in the MIB are
using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A
conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Overview 2. Overview
The COPS protocol [COPS] is a client-server protocol intended for the The COPS protocol [COPS] is a client-server protocol intended for the
communication of policy requests and decisions between a Policy communication of policy requests and decisions between a Policy
Enforcement Point (PEP) and a Policy Decision Point (PDP). The PEP acts Enforcement Point (PEP) and a Policy Decision Point (PDP). The PEP
as a COPS client in this scenario. The model for policy out-sourcing, acts as a COPS client in this scenario. The model for policy out-
of which the COPS protocol provides one part, is described in sourcing, of which the COPS protocol provides one part, is described
[FRAMEWORK]. in [FRAMEWORK].
2.1. Scope 2.1. Scope
This MIB is intended to provide management of the important features of This MIB is intended to provide management of the important features
a COPS protocol client module. It does not provide management for a COPS of a COPS protocol client module. It does not provide management for
server - this is outside the scope of the current memo. It provides for a COPS server - this is outside the scope of the current memo. It
monitoring of status and protocol statistics, as well as for provides for monitoring of status and protocol statistics, as well as
configuration of the client, in particular for telling it where to for configuration of the client, in particular for telling it where
locate its servers. Other mechanisms for achieving this function without to locate its servers. Other mechanisms for achieving this function
SNMP configuration might include use of the Service Location Protocol without SNMP configuration might include use of the Service Location
[SRVLOC] although this is outside the scope of this memo and are not Protocol [SRVLOC] although this is outside the scope of this memo and
specified by the COPS protocol itself. are not specified by the COPS protocol itself.
This MIB also does not provide management of specific COPS client-types This MIB also does not provide management of specific COPS client-
e.g. for use with the RSVP protocol [RSVP][COPSRSVP]. types e.g., for use with the RSVP protocol [RSVP][COPSRSVP].
3. Structure of COPS Client MIB 3. Structure of COPS Client MIB
Objects in this MIB are arranged into groups. Each group is organized Objects in this MIB are arranged into groups. Each group is
as a set of related objects. The overall structure is described below. organized as a set of related objects. The overall structure is
described below.
3.1. copsClientCapabilitiesGroup 3.1. copsClientCapabilitiesGroup
This group contains objects that represent COPS protocol This group contains objects that represent COPS protocol capabilities
capabilities implemented by this COPS client. implemented by this COPS client.
3.2. copsClientStatusGroup 3.2. copsClientStatusGroup
This group contains objects that indicate the current status of This group contains objects that indicate the current status of
connection(s) to COPS servers, including per-server protocol connection(s) to COPS servers, including per-server protocol
statistics. It maintains last-known statistics for all of the statistics. It maintains last-known statistics for all of the
servers with which the client has ever been connected since agent servers with which the client has ever been connected since agent
restart. restart.
3.3. copsConfigGroup 3.3. copsConfigGroup
This group contains objects that allow for configuration of COPS This group contains objects that allow for configuration of COPS
server addresses and the order to which connections should be server addresses and the order to which connections should be
attempted. It contains a table of per-server objects as well as attempted. It contains a table of per-server objects as well as
scalars for configuration of the retry algorithm to be used by a scalars for configuration of the retry algorithm to be used by a
client to obtain a connection to an appropriate server. client to obtain a connection to an appropriate server.
3.4. Textual Conventions 3.4. Textual Conventions
The datatypes CopsClientState, CopsServerEntryType, CopsErrorCode, The datatypes CopsClientState, CopsServerEntryType, CopsErrorCode,
CopsTcpPort and CopsAuthType are used as textual conventions in CopsTcpPort and CopsAuthType are used as textual conventions in this
this document. These textual conventions have NO effect on either document. These textual conventions have NO effect on either the
the syntax nor the semantics of any managed object. Objects syntax nor the semantics of any managed object. Objects defined
defined using these conventions are always encoded by means of the using these conventions are always encoded by means of the rules that
rules that define their primitive type. Hence, no changes to the define their primitive type. Hence, no changes to the SMI or the
SMI or the SNMP are necessary to accommodate these textual SNMP are necessary to accommodate these textual conventions which are
conventions which are adopted merely for the convenience of adopted merely for the convenience of readers.
readers.
3.5. Relationship to Other MIBs 3.5. Relationship to Other MIBs
3.5.1. Relationship to the 'system' group 3.5.1. Relationship to the 'system' group
This MIB contains definitions for a single COPS protocol client This MIB contains definitions for a single COPS protocol client
represented by a single SNMP agent and instance of the MIB-2 system represented by a single SNMP agent and instance of the MIB-2 system
group [MIB2]. It does not address the case of multiple co-located group [MIB2]. It does not address the case of multiple co-located
COPS protocol clients. COPS protocol clients.
4. Editorial information
<this section will be removed before publication>
4.1. Open Issues resolved in this draft
(10) Configuration parameters for the retry algorithm are too limiting
on implementations (no such algorithm was specified by the COPS
protocol itself). DONE - objects which were per-server are now
scalars; a possibly-configurable object is added to select/indicate
the retry algorithm in use with round-robin, sequential and other
as values.
(11) copsClientServerConfigRetryCount should be unsigned: DONE - changed
from Integer32 to Unsigned32.
4.2. Open Issues resolved in previous drafts
(1) When should per-server counters (e.g. copsClientServerInPkts) be
zeroed? Resolution: see issue (3).
(2) Addressing of server tables by IP Address is frowned on: should
this be indexed by a client-determined small integer? DONE - added
InetEndpoint indices as recommended by draft-ops-endpoint-
mib-00.txt.
(3) Should error stats be maintained per-server or is global
sufficient? If per-server then see also issue #1. Resolution:
everything is per-server but not zero'ed on reconnect.
(4) Add object to show current security in use. DONE -
copsClientServerSecurityMode.
(5) Do we need to be able to configure the security mode for client to
attempt to use to talk to COPS server? DONE - added configuration
object as an index to server configuration table. Added some more
capabilities too.
(6) Add TCP port number to all tables. DONE - copsClientServerTcpPort,
copsClientServerConfigTcpPort.
(7) Add server retry configuration. DONE -
copsClientServerConfigRetryCount,
copsClientServerConfigRetryInterval
(8) Add COPS protocol version number capabilities object. DONE -
copsClientCapabilities.
(9) Added error counters and capabilities associated with security.
5. Definitions for COPS Client MIB 4. Definitions for COPS Client MIB
COPS-CLIENT-MIB DEFINITIONS ::= BEGIN COPS-CLIENT-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32,
Unsigned32, mib-2 Unsigned32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
skipping to change at page 7, line 27 skipping to change at page 5, line 7
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
-- REFERENCE -- REFERENCE
-- "The COPS (Common Open Policy Service) Protocol RFC 2748 -- "The COPS (Common Open Policy Service) Protocol RFC 2748
copsClientMIB MODULE-IDENTITY copsClientMIB MODULE-IDENTITY
LAST-UPDATED "200005010000Z" LAST-UPDATED "200009280000Z"
ORGANIZATION "IETF RSVP Admission Policy Working Group" ORGANIZATION "IETF RSVP Admission Policy Working Group"
CONTACT-INFO CONTACT-INFO
" Andrew Smith (WG co-chair) " Andrew Smith (WG co-chair)
Phone: +1 408 579 2821 Phone: +1 408 579 2821
Email: andrew@extremenetworks.com Email: ah_smith@pacbell.net
Mark Stevens (WG co-chair) Mark Stevens (WG co-chair)
Phone: +1 978 287 9102 Phone: +1 978 287 9102
Email: markstevens@lucent.com Email: markstevens@lucent.com
Editor: Andrew Smith Editor: Andrew Smith
Phone: +1 408 579 2821 Phone: +1 408 579 2821
Email: andrew@extremenetworks.com Email: ah_smith@pacbell.net
Editor: David Partain Editor: David Partain
Phone: +46 13 28 41 44 Phone: +46 13 28 41 44
Email: David.Partain@ericsson.com Email: David.Partain@ericsson.com
Editor: John Seligson Editor: John Seligson
Phone: +1 408 495 2992 Phone: +1 408 495 2992
Email: jseligso@nortelnetworks.com" Email: jseligso@nortelnetworks.com"
DESCRIPTION DESCRIPTION
"The COPS Client MIB module" "The COPS Client MIB module"
REVISION "200005010000Z" REVISION "200009280000Z"
DESCRIPTION "This version published as RFC xxxx" DESCRIPTION "This version published as RFC 2940"
-- to be assigned by RFC-Editor
::= { mib-2 xxx } ::= { mib-2 89 }
copsClientMIBObjects OBJECT IDENTIFIER ::= { copsClientMIB 1 } copsClientMIBObjects OBJECT IDENTIFIER ::= { copsClientMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Textual Conventions -- Textual Conventions
-- ------------------------------------------------------------- -- -------------------------------------------------------------
CopsClientState ::= TEXTUAL-CONVENTION CopsClientState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 8, line 29 skipping to change at page 6, line 4
-- ------------------------------------------------------------- -- -------------------------------------------------------------
CopsClientState ::= TEXTUAL-CONVENTION CopsClientState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value indicating the state of a COPS client." "A value indicating the state of a COPS client."
SYNTAX INTEGER { SYNTAX INTEGER {
copsClientInvalid(1), -- default state. copsClientInvalid(1), -- default state.
copsClientTcpconnected(2), -- TCP connection up but COPS copsClientTcpconnected(2), -- TCP connection up but COPS
-- not yet open. -- not yet open.
copsClientAuthenticating(3), -- TCP connection up but still copsClientAuthenticating(3), -- TCP connection up but still
-- authenticating. -- authenticating.
copsClientSecAccepted(4), -- connection authenticated. copsClientSecAccepted(4), -- connection authenticated.
copsClientAccepted(5), -- COPS server accepted client. copsClientAccepted(5), -- COPS server accepted client.
copsClientTimingout(6) -- Keepalive timer has expired, copsClientTimingout(6) -- Keepalive timer has expired,
-- client is in process of tearing -- client is in process of
-- down connection. -- tearing down connection.
} }
CopsServerEntryType ::= TEXTUAL-CONVENTION CopsServerEntryType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value indicating how a COPS server entry came into existence." "A value indicating how a COPS server entry came into existence."
SYNTAX INTEGER { SYNTAX INTEGER {
copsServerStatic(1), -- configured by manager copsServerStatic(1), -- configured by manager
copsServerRedirect(2) -- notified by COPS server copsServerRedirect(2) -- notified by COPS server
} }
CopsErrorCode ::= TEXTUAL-CONVENTION CopsErrorCode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value describing a COPS protocol error. Codes are identical to "A value describing a COPS protocol error. Codes are identical
those used by the COPS protocol itself." to those used by the COPS protocol itself."
SYNTAX INTEGER { SYNTAX INTEGER {
errorOther(0), -- none of the below errorOther(0), -- none of the below
errorBadHandle(1), errorBadHandle(1),
errorInvalidHandleReference(2), errorInvalidHandleReference(2),
errorBadMessageFormat(3), errorBadMessageFormat(3),
errorUnableToProcess(4), errorUnableToProcess(4),
errorMandatoryClientSiMissing(5), errorMandatoryClientSiMissing(5),
errorUnsupportedClientType(6), errorUnsupportedClientType(6),
errorMandatoryCopsObjectMissing(7), errorMandatoryCopsObjectMissing(7),
errorClientFailure(8), errorClientFailure(8),
skipping to change at page 14, line 32 skipping to change at page 11, line 38
of zero indicates no accounting activity is to be performed." of zero indicates no accounting activity is to be performed."
REFERENCE REFERENCE
"RFC 2748 section 3.7" "RFC 2748 section 3.7"
::= { copsClientServerCurrentEntry 10 } ::= { copsClientServerCurrentEntry 10 }
copsClientInPkts OBJECT-TYPE copsClientInPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from this COPS server marked for this Client-Type. This has received from this COPS server marked for this Client-Type.
value is cumulative since agent restart and is not zeroed on new This value is cumulative since agent restart and is not zeroed
connections." on new connections."
::= { copsClientServerCurrentEntry 11 } ::= { copsClientServerCurrentEntry 11 }
copsClientOutPkts OBJECT-TYPE copsClientOutPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
sent to this COPS server marked for this Client-Type. This value has sent to this COPS server marked for this Client-Type. This
is cumulative since agent restart and is not zeroed on new value is cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 12 } ::= { copsClientServerCurrentEntry 12 }
copsClientInErrs OBJECT-TYPE copsClientInErrs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from this COPS server marked for this Client-Type that has received from this COPS server marked for this Client-Type
contained errors in syntax. This value is cumulative since agent that contained errors in syntax. This value is cumulative since
restart and is not zeroed on new connections." agent restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 13 } ::= { copsClientServerCurrentEntry 13 }
copsClientLastError OBJECT-TYPE copsClientLastError OBJECT-TYPE
SYNTAX CopsErrorCode SYNTAX CopsErrorCode
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The code contained in the last COPS protocol Error Object "The code contained in the last COPS protocol Error Object
received by this client from this COPS server marked for this received by this client from this COPS server marked for this
Client-Type. This value is not zeroed on COPS Client-Open Client-Type. This value is not zeroed on COPS Client-Open
skipping to change at page 16, line 34 skipping to change at page 13, line 34
to perform a COPS Client-Open to a COPS server for this to perform a COPS Client-Open to a COPS server for this
Client-Type. This value is cumulative since agent restart and is Client-Type. This value is cumulative since agent restart and is
not zeroed on new connections." not zeroed on new connections."
::= { copsClientServerCurrentEntry 18 } ::= { copsClientServerCurrentEntry 18 }
copsClientErrUnsupportClienttype OBJECT-TYPE copsClientErrUnsupportClienttype OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from COPS servers that referred to Client-Types that are has received from COPS servers that referred to Client-Types
unsupported by this client. This value is cumulative that are unsupported by this client. This value is cumulative
since agent restart and is not zeroed on new connections. This since agent restart and is not zeroed on new connections. This
value is not incremented for entries representing a non-zero value is not incremented for entries representing a non-zero
Client-Type." Client-Type."
::= { copsClientServerCurrentEntry 19 } ::= { copsClientServerCurrentEntry 19 }
copsClientErrUnsupportedVersion OBJECT-TYPE copsClientErrUnsupportedVersion OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 17, line 7 skipping to change at page 14, line 4
copsClientErrUnsupportedVersion OBJECT-TYPE copsClientErrUnsupportedVersion OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client "A count of the total number of COPS messages that this client
has received from COPS servers marked for this Client-Type that has received from COPS servers marked for this Client-Type that
had a COPS protocol Version number that is unsupported by this had a COPS protocol Version number that is unsupported by this
client. This value is cumulative since agent restart and is not client. This value is cumulative since agent restart and is not
zeroed on new connections." zeroed on new connections."
::= { copsClientServerCurrentEntry 20 } ::= { copsClientServerCurrentEntry 20 }
copsClientErrLengthMismatch OBJECT-TYPE copsClientErrLengthMismatch OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from COPS servers marked for this Client-Type that had a has received from COPS servers marked for this Client-Type that
COPS protocol Message Length that did not match the actual had a COPS protocol Message Length that did not match the actual
received message. This value is cumulative since agent restart and received message. This value is cumulative since agent restart
is not zeroed on new connections." and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 21 } ::= { copsClientServerCurrentEntry 21 }
copsClientErrUnknownOpcode OBJECT-TYPE copsClientErrUnknownOpcode OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from COPS servers marked for this Client-Type that had a has received from COPS servers marked for this Client-Type that
COPS protocol Op Code that was unrecognised by this client. This had a COPS protocol Op Code that was unrecognised by this
value is cumulative since agent restart and is not zeroed on new client. This value is cumulative since agent restart and is not
connections." zeroed on new connections."
::= { copsClientServerCurrentEntry 22 } ::= { copsClientServerCurrentEntry 22 }
copsClientErrUnknownCnum OBJECT-TYPE copsClientErrUnknownCnum OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from COPS servers marked for this Client-Type that has received from COPS servers marked for this Client-Type that
contained a COPS protocol object C-Num that was unrecognised by contained a COPS protocol object C-Num that was unrecognised by
this client. This value is cumulative since agent restart and is this client. This value is cumulative since agent restart and is
not zeroed on new connections." not zeroed on new connections."
::= { copsClientServerCurrentEntry 23 } ::= { copsClientServerCurrentEntry 23 }
copsClientErrBadCtype OBJECT-TYPE copsClientErrBadCtype OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from COPS servers marked for this Client-Type that has received from COPS servers marked for this Client-Type that
contained a COPS protocol object C-Type that was not defined for contained a COPS protocol object C-Type that was not defined for
the C-Nums known by this client. This value is cumulative since the C-Nums known by this client. This value is cumulative since
agent restart and is not zeroed on new connections." agent restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 24 } ::= { copsClientServerCurrentEntry 24 }
copsClientErrBadSends OBJECT-TYPE copsClientErrBadSends OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client "A count of the total number of COPS messages that this client
attempted to send to COPS servers marked for this Client-Type attempted to send to COPS servers marked for this Client-Type
that resulted in a transmit error. This value is cumulative that resulted in a transmit error. This value is cumulative
skipping to change at page 18, line 40 skipping to change at page 15, line 35
did not contain a permitted set of COPS protocol objects. This did not contain a permitted set of COPS protocol objects. This
value is cumulative since agent restart and is not zeroed on new value is cumulative since agent restart and is not zeroed on new
connections." connections."
::= { copsClientServerCurrentEntry 26 } ::= { copsClientServerCurrentEntry 26 }
copsClientErrWrongOpcode OBJECT-TYPE copsClientErrWrongOpcode OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of COPS messages that this client has "A count of the total number of COPS messages that this client
received from COPS servers marked for this Client-Type that had a has received from COPS servers marked for this Client-Type that
COPS protocol Op Code that should not have been sent to a COPS had a COPS protocol Op Code that should not have been sent to a
client e.g. Open-Requests. This value is cumulative since agent COPS client e.g. Open-Requests. This value is cumulative since
restart and is not zeroed on new connections." agent restart and is not zeroed on new connections."
::= { copsClientServerCurrentEntry 27 } ::= { copsClientServerCurrentEntry 27 }
copsClientKaTimedoutClients OBJECT-TYPE copsClientKaTimedoutClients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the total number of times that this client has "A count of the total number of times that this client has
been shut down for this Client-Type by COPS servers that had been shut down for this Client-Type by COPS servers that had
detected a COPS protocol Keepalive timeout. This value is detected a COPS protocol Keepalive timeout. This value is
skipping to change at page 25, line 43 skipping to change at page 22, line 15
OBJECT copsClientServerConfigRetryIntvl OBJECT copsClientServerConfigRetryIntvl
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is required only if the device supports the "Write access is required only if the device supports the
configuration of COPS server information." configuration of COPS server information."
::= { copsClientCompliances 1 } ::= { copsClientCompliances 1 }
END END
6. Acknowledgments 5. Acknowledgments
This document describes instrumentation for the client side of the COPS This document describes instrumentation for the client side of the
protocol which was defined by the RSVP Admission Policy (rap) Working COPS protocol which was defined by the RSVP Admission Policy (rap)
Group, now known as the Resource Allocation Protocol (rap) Working Working Group, now known as the Resource Allocation Protocol (rap)
Group. Working Group.
7. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB that have a There are a number of management objects defined in this MIB that
MAX-ACCESS clause of read-create. Such objects may be considered have a MAX-ACCESS clause of read-create. Such objects may be
sensitive or vulnerable in some network environments. The support for considered sensitive or vulnerable in some network environments. The
SET operations in a non-secure environment without proper protection can support for SET operations in a non-secure environment without proper
have a negative effect on network operations. protection can have a negative effect on network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and GET/SET control as to who on the secure network is allowed to access and
(read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security
as provided by the SNMPv3 framework. Specifically, the use of the User- features as provided by the SNMPv3 framework. Specifically, the use
based Security Model [USM] and the View-based Access Control Model of the User-based Security Model [USM] and the View-based Access
[VACM] is recommended. Control Model [VACM] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity It is then a customer/user responsibility to ensure that the SNMP
giving access to an instance of this MIB, is properly configured to give entity giving access to an instance of this MIB, is properly
access to the objects only to those principals (users) that have configured to give access to the objects only to those principals
legitimate rights to indeed GET or SET (change/create/delete) them. (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
8. References 7. References
[ARCH] [ARCH] Harrington, D., Presuhn, R. and B. Wijnen, "An
Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Architecture for Describing SNMP Management
Describing SNMP Management Frameworks", RFC 2571, April 1999 Frameworks", RFC 2571, April 1999.
[V1PROTO] [V1PROTO] Case, J., Fedor, M., Schoffstall, M. and J. Davin,
Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network "Simple Network Management Protocol", STD 15, RFC 1157,
Management Protocol", STD 15, RFC 1157, May 1990. May 1990.
[V1SMI] [V1SMI] Rose, M. and K. McCloghrie, "Structure and
Rose, M., and K. McCloghrie, "Structure and Identification of Identification of Management Information for TCP/IP-
Management Information for TCP/IP-based Internets", STD 16, RFC based Internets", STD 16, RFC 1155, May 1990.
1155, May 1990
[V1CONCISE] [V1CONCISE] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC STD 16, RFC 1212, March 1991.
1212, March 1991
[V1TRAPS] [V1TRAPS] Rose, M., "A Convention for Defining Traps for use with
M. Rose, "A Convention for Defining Traps for use with the SNMP", the SNMP", RFC 1215, March 1991.
RFC 1215, March 1991
[V2SMI] [V2SMI] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. J., Rose, M. and S. Waldbusser, "Structure of
and S. Waldbusser, "Structure of Management Information Version 2 Management Information Version 2 (SMIv2)", STD 58, RFC
(SMIv2)", STD 58, RFC 2578, April 1999. 2578, April 1999.
[V2TC] [V2TC] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. J., Rose, M. and S. Waldbusser, "Textual Conventions
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC for SMIv2", STD 58, RFC 2579, April 1999.
2579, April 1999.
[V2CONFORM] [V2CONFORM] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. J., Rose, M. and S. Waldbusser, "Conformance Statements
and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC for SMIv2", STD 58, RFC 2580, April 1999.
2580, April 1999.
[V2COMMUNITY] [V2COMMUNITY] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction "Introduction to Community-based SNMPv2", RFC 1901,
to Community-based SNMPv2", RFC 1901, January 1996. January 1996.
[V2TRANS] [V2TRANS] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport "Transport Mappings for Version 2 of the Simple Network
Mappings for Version 2 of the Simple Network Management Protocol Management Protocol (SNMPv2)", RFC 1906, January 1996.
(SNMPv2)", RFC 1906, January 1996.
[V2PROTO] [V2PROTO] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol "Protocol Operations for Version 2 of the Simple
Operations for Version 2 of the Simple Network Management Protocol Network Management Protocol (SNMPv2)", RFC 1905,
(SNMPv2)", RFC 1905, January 1996. January 1996.
[V3INTRO] [V3INTRO] Case, J., Mundy, R., Partain, D. and B. Stewart,
Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to "Introduction to Version 3 of the Internet-standard
Version 3 of the Internet-standard Network Management Framework", Network Management Framework", RFC 2570, April 1999.
RFC 2570, April 1999.
[V3MPC] [V3MPC] Case, J., Harrington D., Presuhn R. and B. Wijnen,
Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message "Message Processing and Dispatching for the Simple
Processing and Dispatching for the Simple Network Management Network Management Protocol (SNMP)", RFC 2572, April
Protocol (SNMP)", RFC 2572, April 1999. 1999.
[V3USM] [V3USM] Blumenthal, U. and B. Wijnen, "The User-Based Security
Blumenthal, U. and B. Wijnen, "The User-Based Security Model (USM) Model (USM) for Version 3 of the Simple Network
for Version 3 of the Simple Network Management Protocol (SNMPv3)", Management Protocol (SNMPv3)", RFC 2574, April 1999.
RFC 2574, April 1999.
[V3APPS] [V3APPS] Levi, D., Meyer, P. and B. Stewart, "SNMP
Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, Applications", RFC 2573, April 1999.
April 1999.
[V3VACM] [V3VACM] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Access Control Model for the Simple Network Management
Control Model for the Simple Network Management Protocol (SNMP)", Protocol (SNMP)", RFC 2575, April 1999.
RFC 2575, April 1999.
[ASN1] [MIB2] McCloghrie K. and M. Rose, "Management Information Base
Information processing systems - Open Systems Interconnection - for Network Management of TCP/IP-based internets", STD
Specification of Abstract Syntax Notation One (ASN.1), 17, RFC 1213, March 1991.
International Organization for Standardization, International
Standard 8824, December 1987.
[ASN1BER] [FRAMEWORK] Yavatkar, R., Pendarakis, D. and Guerin, R., "A
Information processing systems - Open Systems Interconnection - Framework for Policy-based Admission Control", RFC
Specification of Basic Encoding Rules for Abstract Notation One 2753, January 2000.
(ASN.1), International Organization for Standardization,
International Standard 8825, December 1987.
[MIB2] [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R.
McCloghrie K., and M. Rose, Editors, "Management Information Base and A. Sastry, "The COPS (Common Open Policy Service)
for Network Management of TCP/IP-based internets", STD 17, RFC Protocol", RFC 2748, January 2000.
1213, March 1991.
[FRAMEWORK] [RSVP] Braden, R. ed., Zhang, L., Berson, S., Herzog, S. and
Yavatkar, R., Pendarakis, D. and Guerin, R., "A Framework for S. Jamin, "Resource ReSerVation Protocol (RSVP)
Policy-based Admission Control", RFC 2753, January 2000. Version 1 - Functional Specification", RFC 2205,
September 1997.
[COPS] [COPSRSVP] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R.
Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry, and A. Sastry, "COPS Usage for RSVP", RFC 2749, January
A., "The COPS (Common Open Policy Service) Protocol", RFC 2748, 2000.
January 2000.
[RSVP] [SRVLOC] Guttman, E., Perkins, C., Veizades, J. and M. Day,
Braden, R. ed. et al., "Resource ReSerVation Protocol (RSVP) "Service Location Protocol, Version 2", RFC 2608, June
Version 1 - Functional Specification", RFC 2205, September 1997. 1999.
[COPSRSVP] [ADDRESSMIB] Daniele, M., Haberman, B., Routhier, S. and J.
Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and Sastry, Schoenwaelder, "Textual Conventions for Internet
A., "COPS Usage for RSVP", RFC 2749, January 2000. Network Addresses", RFC 2851, June 2000.
[SRVLOC] [PROCESS] Bradner, S., "The Internet Standards Process --
Guttman, E., Perkins, C., Veizades, J., Day, M., "Service Location Revision 3", BCP 9, RFC 2026, October 1996.
Protocol, Version 2", RFC 2608, June 1999.
[ADDRESSMIB] 8. Authors' Addresses
Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder,
"Textual Conventions for Internet Network Addresses", Internet
Draft, April 2000. http://www.ietf.org/internet-drafts/draft-ops-
endpoint-mib-08.txt
[PROCESS] Andrew Smith
Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9,
RFC 2026, October 1996.
9. Authors' Addresses Fax: +1 415 345 1827
Email: ah_smith@pacbell.net
Andrew Smith David Partain
Extreme Networks Ericsson Radio Systems
3585 Monroe St. Research and Innovation
Santa Clara CA 95051 P.O. Box 1248
USA SE-581 12 Linkoping
Phone: +1 408 579 2821 Sweden
EMail: andrew@extremenetworks.com
David Partain Phone: +46 13 28 41 44
Ericsson Radio Systems EMail: David.Partain@ericsson.com
Research and Innovation
P.O. Box 1248
SE-581 12 Linkoping
Sweden
Phone: +46 13 28 41 44
EMail: David.Partain@ericsson.com
John Seligson John Seligson
Nortel Networks, Inc. Nortel Networks, Inc.
4401 Great America Parkway 4401 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Phone: +1 408 495 2992
EMail: jseligso@nortelnetworks.com
10. Notices Phone: +1 408 495 2992
EMail: jseligso@nortelnetworks.com
The IETF takes no position regarding the validity or scope of any 9. Notices
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses to
be made available, or the result of an attempt made to obtain a general
license or permission for the use of such propritary rights by
implementors or users of this specification can be obtained from the
IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF takes no position regarding the validity or scope of any
copyrights, patents or patent applications, or other proprietary rights intellectual property or other rights that might be claimed to
which may cover technology that may be required to practice this pertain to the implementation or use of the technology described in
standard. Please address the information to the IETF Executive this document or the extent to which any license under such rights
Director. might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
11. Full Copyright The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
10. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished to
to others, and derivative works that comment on or otherwise others, and derivative works that comment on or otherwise explain it
explain it or assist in its implmentation may be prepared, copied, or assist in its implementation may be prepared, copied, published
published and distributed, in whole or in part, without and distributed, in whole or in part, without restriction of any
restriction of any kind, provided that the above copyright notice kind, provided that the above copyright notice and this paragraph are
and this paragraph are included on all such copies and derivative included on all such copies and derivative works. However, this
works. However, this document itself may not be modified in any document itself may not be modified in any way, such as by removing
way, such as by removing the copyright notice or references to the the copyright notice or references to the Internet Society or other
Internet Society or other Internet organizations, except as needed Internet organizations, except as needed for the purpose of
for the purpose of developing Internet standards in which case the developing Internet standards in which case the procedures for
procedures for copyrights defined in the Internet Standards copyrights defined in the Internet Standards process must be
process must be followed, or as required to translate it into followed, or as required to translate it into languages other than
languages other than English. English.
The limited permissions granted above are perpetual and will not The limited permissions granted above are perpetual and will not be
be revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on This document and the information contained herein is provided on an
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 92 change blocks. 
393 lines changed or deleted 305 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/