rfc2248.txt

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

    ::= {assocEntry 3}

assocApplicationType OBJECT-TYPE
    SYNTAX INTEGER {
        ua-initiator(1),
        ua-responder(2),
        peer-initiator(3),
        peer-responder(4)}
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "This indicates whether the remote application is some type of
       client making use of this network service (e.g. a Mail User
       Agent) or a server acting as a peer. Also indicated is whether



Freed & Kille               Standards Track                    [Page 13]

RFC 2248                  Network Services MIB              January 1998


       the remote end initiated an incoming connection to the network
       service or responded to an outgoing connection made by the
       local application.  MTAs and messaging gateways are
       considered to be peers for the purposes of this variable."
    ::= {assocEntry 4}

assocDuration OBJECT-TYPE
    SYNTAX TimeStamp
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
      "The value of sysUpTime at the time this association was
       started.  If this association started prior to the last
       initialization of the network subsystem, then this
       object contains a zero value."
    ::= {assocEntry 5}


-- Conformance information

applConformance OBJECT IDENTIFIER ::= {application 3}

applGroups      OBJECT IDENTIFIER ::= {applConformance 1}
applCompliances OBJECT IDENTIFIER ::= {applConformance 2}


-- Compliance statements

applCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
      "The compliance statement for SNMPv2 entities
       which implement the Network Services Monitoring MIB
       for basic monitoring of network service applications."
    MODULE  -- this module
      MANDATORY-GROUPS {applGroup}
    ::= {applCompliances 1}

assocCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
      "The compliance statement for SNMPv2 entities which
       implement the Network Services Monitoring MIB for basic
       monitoring of network service applications and their
       associations."
    MODULE  -- this module
      MANDATORY-GROUPS {applGroup, assocGroup}
    ::= {applCompliances 2}



Freed & Kille               Standards Track                    [Page 14]

RFC 2248                  Network Services MIB              January 1998


-- Units of conformance

applGroup OBJECT-GROUP
    OBJECTS {
      applName, applVersion, applUptime, applOperStatus,
      applLastChange, applInboundAssociations,
      applOutboundAssociations, applAccumulatedInboundAssociations,
      applAccumulatedOutboundAssociations, applLastInboundActivity,
      applLastOutboundActivity, applRejectedInboundAssociations,
      applFailedOutboundAssociations, applDescription, applURL}
    STATUS current
    DESCRIPTION
      "A collection of objects providing basic monitoring of
       network service applications."
    ::= {applGroups 1}


assocGroup OBJECT-GROUP
    OBJECTS {
      assocRemoteApplication, assocApplicationProtocol,
      assocApplicationType, assocDuration}
    STATUS current
    DESCRIPTION
      "A collection of objects providing basic monitoring of
       network service applications' associations."
    ::= {applGroups 2}


-- OIDs of the form {applTCPProtoID port} are intended to be used
-- for TCP-based protocols that don't have OIDs assigned by other
-- means. {applUDPProtoID port} serves the same purpose for
-- UDP-based protocols. In either case 'port' corresponds to
-- the primary port number being used by the protocol. For example,
-- assuming no other OID is assigned for SMTP, an OID of
-- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
-- protocol that uses port 25 as its primary port.

applTCPProtoID OBJECT IDENTIFIER ::= {application 4}
applUDPProtoID OBJECT IDENTIFIER ::= {application 5}

END










Freed & Kille               Standards Track                    [Page 15]

RFC 2248                  Network Services MIB              January 1998


7.  Changes made since RFC 1565

   The only changes made to this document since it was issued as RFC
   1565 [11] are the following:

    (1)   applDescription and applURL fields have been added.  These
          fields are intended to identify and describe the application.

    (2)   A number of DESCRIPTION fields have been reworded, hopefully
          making them clearer.

    (3)   The new "quiescing" state has been added to applOperStatus.

    (4)   The prose about "dynamic single threaded processes" has been
          removed -- it was simply too confusing.

    (5)   Various RFC references have been updated to refer to more
          recent versions.

    (6)   The MIB has been renamed from APPLICATION-MIB to NETWORK-
          SERVICES-MIB.  This was done because an application MIB is now
          under development within the IETF that provides very different
          functionality from this MIB.

8.  Acknowledgements

   This document is a product of the Mail and Directory Management
   (MADMAN) Working Group. It is based on an earlier MIB designed by S.
   Kille, T.  Lenggenhager, D. Partain, and W. Yeong.  The Electronic
   Mail Association's TSC committee was instrumental in  providing
   feedback on and suggesting enhancements to RFC 1565 [11] that have
   led to the present document.

9.  References

   [1]  SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
        S. Waldbusser, "Structure of Management Information for Version
        2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
        January 1996.

   [2]  SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
        S. Waldbusser, "Textual Conventions for Version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1903, January 1996.

   [3]  SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
        S. Waldbusser, "Conformance Statements for Version 2 of the
        Simple Network Management Protocol (SNMPv2)", RFC 1904, January
        1996.



Freed & Kille               Standards Track                    [Page 16]

RFC 2248                  Network Services MIB              January 1998


   [4]  SNMPv2 Working Group, 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.

   [5]  SNMPv2 Working Group, 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.

   [6]  SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
        S. Waldbusser, "Management Information Base for Version 2 of the
        Simple Network Management Protocol (SNMPv2)", RFC 1907, January
        1996.

   [7]  SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
        S. Waldbusser, "Coexistence between Version 1 and Version 2 of
        the Internet-standard Network Management Framework", RFC 1908,
        January 1996.

   [8]  Kille, S., "A String Representation of Distinguished Names", RFC
        1779, March 1995.

   [9]  Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC
        822", RFC 1327, May 1992.

   [10] Berners-Lee, T., Masinter, L. and M. McCahill, Uniform Resource
        Locators (URL)", RFC 1738, December 1994.

   [11] Freed, N., and S. Kille, "Network Services Monitoring MIB", RFC
        1565, January 1994.

10.  Security Considerations

   This MIB does not offer write access, and as such cannot be used to
   actively attack a system. However, this MIB does provide passive
   information about the existance, type, and configuration of
   applications on a given host that could potentially indicate some
   sort of vulnerability. Finally, the information MIB provides about
   network usage could be used to analyze network traffic patterns.













Freed & Kille               Standards Track                    [Page 17]

RFC 2248                  Network Services MIB              January 1998


11.  Author and Chair Addresses

   Ned Freed
   Innosoft International, Inc.
   1050 Lakes Drive
   West Covina, CA 91790
   USA

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


   Steve Kille, MADMAN WG Chair
   ISODE Consortium
   The Dome, The Square
   Richmond TW9 1DT
   UK

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






























Freed & Kille               Standards Track                    [Page 18]

RFC 2248                  Network Services MIB              January 1998


12.  Full Copyright Statement

   Copyright (C) The Internet Society (1998). 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.
























Freed & Kille               Standards Track                    [Page 19]