rfcrfc2788.txt

本程序为在linux下实现FTP传输文件的实现

“为网络服务应用和连接，支持网络服务监视MIB的RFC2788应用的兼容状态。“
       MODULE
         MANDATORY-GROUPS {applRFC2788Group, assocRFC2788Group}
       ::= {applCompliances 6}
   -- Units of conformance
   applRFC1565Group OBJECT-GROUP
       OBJECTS {
         applName, applVersion, applUptime, applOperStatus,
         applLastChange, applInboundAssociations,
         applOutboundAssociations, applAccumulatedInboundAssociations,
         applAccumulatedOutboundAssociations, applLastInboundActivity,
         applLastOutboundActivity, applRejectedInboundAssociations,
         applFailedOutboundAssociations}
       STATUS obsolete
描述
“表示提供基本网络服务应用监视的对象集。这个初始化集在RFC1565中给以了定义。“
       ::= {applGroups 7}
   assocRFC1565Group OBJECT-GROUP
       OBJECTS {
         assocRemoteApplication, assocApplicationProtocol,
         assocApplicationType, assocDuration}
       STATUS obsolete
描述
“表示提供基本网络服务应用连接监视的对象集。这个初始化集在RFC1565中给以了定义。
“
       ::= {applGroups 2}
   applRFC2248Group OBJECT-GROUP
       OBJECTS {
         applName, applVersion, applUptime, applOperStatus,
         applLastChange, applInboundAssociations,
         applOutboundAssociations, applAccumulatedInboundAssociations,
         applAccumulatedOutboundAssociations, applLastInboundActivity,
         applLastOutboundActivity, applRejectedInboundAssociations,
         applFailedOutboundAssociations, applDescription, applURL}
       STATUS deprecated
描述
“表示提供基本网络服务应用监视的对象集。这个初始化集在RFC2248中给以了定义；注
意少了applDirectoryName。“
       ::= {applGroups 3}
   assocRFC2248Group OBJECT-GROUP
       OBJECTS {
         assocRemoteApplication, assocApplicationProtocol,
         assocApplicationType, assocDuration}
       STATUS deprecated
描述
“表示提供基本网络服务应用连接监视的对象集。这个初始化集在RFC2248中给以了定义；
注意少了applDirectoryName。“
       ::= {applGroups 4}
   applRFC2788Group OBJECT-GROUP
       OBJECTS {
         applName, applDirectoryName, applVersion, applUptime,
         applOperStatus, applLastChange, applInboundAssociations,
         applOutboundAssociations, applAccumulatedInboundAssociations,
         applAccumulatedOutboundAssociations, applLastInboundActivity,
         applLastOutboundActivity, applRejectedInboundAssociations,
         applFailedOutboundAssociations, applDescription, applURL}
       STATUS current
描述
“表示提供基本网络服务应用监视的对象集。这个初始化集在RFC2788中给以了定义；它
增加了RFC2248少掉的applDirectoryName。“
 ::= {applGroups 5}
   assocRFC2788Group OBJECT-GROUP
       OBJECTS {
         assocRemoteApplication, assocApplicationProtocol,
         assocApplicationType, assocDuration}
STATUS current
描述
“表示提供网络服务应用连接基本监视的对象集合。它是RFC2788的相关组。”
       ::= {applGroups 6}
形如“applTCPProtaID 端口）的OID是用作基本TCP协议对于基于UDP协议没有相关的
形式因为没有付以OID.在每种情况下，端口依照这个协议所用的首要端口数。例如，假设
没有OID指派给SMTP，applTcpProtolID 25的OID可以用，因为SMTP是基于TCP的协
议用25端口作为首要端口。”
   applTCPProtoID OBJECT IDENTIFIER ::= {application 4}
   applUDPProtoID OBJECT IDENTIFIER ::= {application 5}
   END
5.从RFC2248的变化
这次修订更正了在RFC2248中关于网络服务MIB结构的一些微小技术错误。另外，
applName,appVersion,appDescription域从DisplayString 该到SnmpAdminStrings中。RFC1779
已经更新成RFC22543,相应的增加了有UTF-8字符系列的区分名字能力。“
6. 致谢
这个文档是邮件和目录管理（MADMAN）工作组的产品。它基于前面S.Kille, T.  
Lenggenhager, D. Partain, and W. Yeong设计的MIB。电子邮件协会TSC委员会提供器件和对
RFC1565的一些更新使有了这个目前的版本。
9.  参考资料
   [1]  Grillo, P. and S. Waldbusser, "Host Resources MIB", RFC 1514,
        September 1993.

   [2]  Krupczak, C. and J. Saperia, "Definitions of System-Level
        Managed Objects for Applications", RFC 2287, February 1998.

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

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

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

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

   [7]  McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of
        Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
        April 1999.

   [8]  McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual
        Conventions for SMIv2", STD 58, RFC 2579, April 1999.

   [9]  McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance
        Statements for SMIv2", STD 58, RFC 2580, April 1999.

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

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

   [12] 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.

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

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

   [15] 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.

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

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

   [18] Wahl, M., Kille, S. and T.Howes, "Lightweight Directory Access
        Protocol (v3): UTF-8 String Representation of Distinguished
        Names", RFC 2253, December 1997.

   [19] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC
        2156, January 1998.

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

   [21] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL
        Scheme", RFC 2368, July 1998.

   [22] Freed, N. and S. Kille, "Network Services Monitoring MIB", RFC
        2248, January 1998.

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

   [29] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD
        8, RFC 854, RFC 855, May 1983.

8.  安全考虑
	在MIB中没有管理对象定义成有最大访问权限如读写和/或读创建。所以，如果MIB
正确的执行，入侵者通过直接SNMP设置操作改变或创建MIB的任何管理对象是不可能的。
	但是，这个MIB不提供给定主机关于应用的存在性，类型，设置的被动信息，这些信
息可能显示一些攻击隐患。对后，MIB信息提供可以用作分析网络流量。
SNMPv1自身不是一个安全环境。即使如果它自身是安全的（如用IPSec）,假使那样那么没
有控制能够在网络上允许连通或GET/SET（read/change/create/delete）在MIB中的信息。
	极力被推荐的具有安全特性的应用为SNMPv3.特别的，基本用户安全模型RFC2574[14]
和基于观点连接控制模型RFC2575[17]是推荐使用的。
	保证SNMP提供连通MIB是客户/用户的责任，应该配置成只有给那些合法用户有权实
际Get或Set信息。
9.  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
   MessagingDirect Ltd.
   The Dome, The Square
   Richmond TW9 1DT
   UK

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

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.


RFC2788 Network Services Monitoring MIB                      网络服务监视MIB


1
RFC文档中文翻译计划