rfc2940.txt

来自「著名的RFC文档,其中有一些文档是已经翻译成中文的的.」· 文本 代码 · 共 1,516 行 · 第 1/4 页

        management of the COPS client."

    MODULE
        MANDATORY-GROUPS {
            copsDeviceStatusGroup, copsDeviceConfigGroup
        }

        OBJECT      copsClientServerConfigTcpPort
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is required only if the device supports the
            configuration of COPS server information."

        OBJECT      copsClientServerConfigPriority
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is required only if the device supports the
            configuration of COPS server information."

        OBJECT      copsClientServerConfigRowStatus
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is required only if the device supports the
            configuration of COPS server information."

        OBJECT      copsClientServerConfigRetryAlgrm
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is required only if the device supports the
            configuration of COPS server information."

        OBJECT      copsClientServerConfigRetryCount
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is required only if the device supports the
            configuration of COPS server information."




Smith                       Standards Track                    [Page 21]

RFC 2940                    COPS Client MIB                 October 2000


        OBJECT      copsClientServerConfigRetryIntvl
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is required only if the device supports the
            configuration of COPS server information."

       ::= { copsClientCompliances 1 }

END

5.  Acknowledgments

   This document describes instrumentation for the client side of the
   COPS protocol which was defined by the RSVP Admission Policy (rap)
   Working Group, now known as the Resource Allocation Protocol (rap)
   Working Group.

6.  Security Considerations

   There are a number of management objects defined in this MIB that
   have a MAX-ACCESS clause of read-create.  Such objects may be
   considered sensitive or vulnerable in some network environments.  The
   support for SET operations in a non-secure environment without proper
   protection can have a negative effect on network operations.

   SNMPv1 by itself is not a secure environment.  Even if the network
   itself is secure (for example by using IPSec), even then, there is no
   control as to who on the secure network is allowed to access and
   GET/SET (read/change/create/delete) the objects in this MIB.

   It is recommended that the implementers consider the security
   features as provided by the SNMPv3 framework.  Specifically, the use
   of the User-based Security Model [USM] and the View-based Access
   Control Model [VACM] is recommended.

   It is then a customer/user responsibility to ensure that the SNMP
   entity giving access to an instance of this MIB, is properly
   configured to give access to the objects only to those principals
   (users) that have legitimate rights to indeed GET or SET
   (change/create/delete) them.











Smith                       Standards Track                    [Page 22]

RFC 2940                    COPS Client MIB                 October 2000


7.  References

   [ARCH]        Harrington, D., Presuhn, R. and B. Wijnen, "An
                 Architecture for Describing SNMP Management
                 Frameworks", RFC 2571, April 1999.

   [V1PROTO]     Case, J., Fedor, M., Schoffstall, M. and J. Davin,
                 "Simple Network Management Protocol", STD 15, RFC 1157,
                 May 1990.

   [V1SMI]       Rose, M. and K. McCloghrie, "Structure and
                 Identification of Management Information for TCP/IP-
                 based Internets", STD 16, RFC 1155, May 1990.

   [V1CONCISE]   Rose, M. and K. McCloghrie, "Concise MIB Definitions",
                 STD 16, RFC 1212, March 1991.

   [V1TRAPS]     Rose, M., "A Convention for Defining Traps for use with
                 the SNMP", RFC 1215, March 1991.

   [V2SMI]       McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
                 J., Rose, M. and S. Waldbusser, "Structure of
                 Management Information Version 2 (SMIv2)", STD 58, RFC
                 2578, April 1999.

   [V2TC]        McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
                 J., Rose, M. and S. Waldbusser, "Textual Conventions
                 for SMIv2", STD 58, RFC 2579, April 1999.

   [V2CONFORM]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
                 J., Rose, M. and S. Waldbusser, "Conformance Statements
                 for SMIv2", STD 58, RFC 2580, April 1999.

   [V2COMMUNITY] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
                 "Introduction to Community-based SNMPv2", RFC 1901,
                 January 1996.

   [V2TRANS]     Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
                 "Transport Mappings for Version 2 of the Simple Network
                 Management Protocol (SNMPv2)", RFC 1906, January 1996.

   [V2PROTO]     Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
                 "Protocol Operations for Version 2 of the Simple
                 Network Management Protocol (SNMPv2)", RFC 1905,
                 January 1996.






Smith                       Standards Track                    [Page 23]

RFC 2940                    COPS Client MIB                 October 2000


   [V3INTRO]     Case, J., Mundy, R., Partain, D. and B. Stewart,
                 "Introduction to Version 3 of the Internet-standard
                 Network Management Framework", RFC 2570, April 1999.

   [V3MPC]       Case, J., Harrington D., Presuhn R. and B. Wijnen,
                 "Message Processing and Dispatching for the Simple
                 Network Management Protocol (SNMP)", RFC 2572, April
                 1999.

   [V3USM]       Blumenthal, U. and B. Wijnen, "The User-Based Security
                 Model (USM) for Version 3 of the Simple Network
                 Management Protocol (SNMPv3)", RFC 2574, April 1999.

   [V3APPS]      Levi, D., Meyer, P. and B. Stewart, "SNMP
                 Applications", RFC 2573, April 1999.

   [V3VACM]      Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
                 Access Control Model for the Simple Network Management
                 Protocol (SNMP)", RFC 2575, April 1999.

   [MIB2]        McCloghrie K. and M. Rose, "Management Information Base
                 for Network Management of TCP/IP-based internets", STD
                 17, RFC 1213, March 1991.

   [FRAMEWORK]   Yavatkar, R., Pendarakis, D. and Guerin, R., "A
                 Framework for Policy-based Admission Control", RFC
                 2753, January 2000.

   [COPS]        Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R.
                 and A. Sastry, "The COPS (Common Open Policy Service)
                 Protocol", RFC 2748, January 2000.

   [RSVP]        Braden, R. ed., Zhang, L., Berson, S., Herzog, S. and
                 S.  Jamin, "Resource ReSerVation Protocol (RSVP)
                 Version 1 - Functional Specification", RFC 2205,
                 September 1997.

   [COPSRSVP]    Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R.
                 and A. Sastry, "COPS Usage for RSVP", RFC 2749, January
                 2000.

   [SRVLOC]      Guttman, E., Perkins, C., Veizades, J. and M. Day,
                 "Service Location Protocol, Version 2", RFC 2608, June
                 1999.

   [ADDRESSMIB]  Daniele, M., Haberman, B., Routhier, S. and J.
                 Schoenwaelder, "Textual Conventions for Internet
                 Network Addresses", RFC 2851, June 2000.



Smith                       Standards Track                    [Page 24]

RFC 2940                    COPS Client MIB                 October 2000


   [PROCESS]     Bradner, S., "The Internet Standards Process --
                 Revision 3", BCP 9, RFC 2026, October 1996.

8.  Authors' Addresses

   Andrew Smith

   Fax:  [phone]
   Email: [e-mail]


   David Partain
   Ericsson Radio Systems
   Research and Innovation
   P.O. Box 1248
   SE-581 12 Linkoping
   Sweden

   Phone: [phone]
   EMail: [e-mail]


   John Seligson
   Nortel Networks, Inc.
   4401 Great America Parkway
   Santa Clara, CA 95054
   USA

   Phone: [phone]
   EMail: [e-mail]





















Smith                       Standards Track                    [Page 25]

RFC 2940                    COPS Client MIB                 October 2000


9.  Notices

   The IETF takes no position regarding the validity or scope of any
   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
   proprietary 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
   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.






























Smith                       Standards Track                    [Page 26]

RFC 2940                    COPS Client MIB                 October 2000


10.  Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Smith                       Standards Track                    [Page 27]